On Thursday, July 27, 2006 09:19:12 AM -0400 Derrick J Brashear
<[EMAIL PROTECTED]> wrote:
On Thu, 27 Jul 2006, Deon George wrote:
(The salvage log shows the following:
07/27/2006 14:16:29 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager
/vicepa 536870915 -tmpdir /tmp/afs)
07/27/2006 14:16:29 Found 0 link count file
/vicepa/AFSIDat/1/1+++U/+/+/20+++s91. ... (MANY LINES HERE)
...
07/27/2006 14:16:29 1 nVolumesInInodeFile 28
07/27/2006 14:16:29 SALVAGING VOLUME 536870915.
07/27/2006 14:16:29 root.cell (536870915) updated 07/23/2006 17:13
07/27/2006 14:16:29 totalInodes 6
07/27/2006 14:16:29 Found 2 orphaned files and directories (approx. 2 KB)
07/27/2006 14:16:29 Salvaged root.cell (536870915): 2 files, 2 blocks
Is there anyway I can salvage this volume, or is my only hope to destroy
it and start again?
I'm running OpenAFS 1.4.1 on RHEL4.
There are clearly more than 2 orphans here, but, it would probably be
easier to delete and recreate the volume. The real issue is how it got
corrupted in the first place.
The things with zero link counts don't qualify as orphans. The inodes get
deleted, and then the vnodes get deleted, and then the directory entries
get deleted (if any).
Well, except that IIRC, the current code doesn't actually _delete_ the
files with zero link counts; it just completely ignores them.
-- Jeff
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
