[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] corrupt library (failed inode signature validation)

From: Aaron Bentley
Subject: Re: [Gnu-arch-users] corrupt library (failed inode signature validation)
Date: Tue, 31 Aug 2004 10:29:07 -0400
User-agent: Mozilla Thunderbird 0.5 (X11/20040309)

Haakon Riiser wrote:

Haakon Riiser wrote:

The revision library is located on a local filesystem, while the
archive is accessed via NFS.  Is this configuration a problem?

That should be fine, I use archives over NFS with a local revlib
at home a lot.  Archives over NFS are never a problem, in fact...
did you mean that the checked-out project tree was over NFS?

No, just the repository.  The working copy (and the revision
library) is on a local reiser3 filesystem.  Btw, I access the
repository via sftp, and the sftp-server has my home directory
on NFS, but the fact that sftp is also involved shouldn't make
any difference, right?

Option 1: Your revision library really is being corrupted. The easiest way for this to happen is if you're doing get --link, and using tools that don't break hard links. But anything (except tla) altering files in your revlib is bad news.

Option 2: Your revision library is fine, but the signature data is changing. This can happen if you copy the files, or touch the files, or possibly with some update/sync utilities.

The values tracked by revision libraries are:
mtime, size, inode.  Pre-1.2.1, device number was tracked too.

Any mismatch between the values and the actual files will cause the corruption message. You can generate a tla 1.2.1 sig like this:
stat --format="ino=%i:mtime=%Y:size=%s"

You can generate a < 1.2.1 sig like this
stat --format="dev=%d:ino=%i:mtime=%Y:size=%s"



Aaron Bentley
Director of Technology
Panometrics, Inc.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]