advfs directory corruption

[GeorgeT]

One of our systems didn't unmount one of its advfs filesystems when it went down. The unfortunate side affect of this is the fact that the system was in the midst of doing a directory update. Now I've got a file that has a directory entry (with "inode&quot but the "inode" no longer exists in the file system metadata. I'm looking for a tool similar to fsdb to allow me to null the inode reference within the directory.

This is a 1000A running on 4.0F/BL014.

 

[trunix]

I am not too familiar with DEC unix, but I would normally use fsck to repair a corrupt file system. Have you tried this ?

 

[GeorgeT]

advfs does not have an fsck utility. There is a verify utility that can be run but I have not had it actually fix anything in the past (you're supposed to be able to recover or delete lost files). I am looking for a utility (like fsdb) that I can run that will allow me to update the directory and null out the inode id (the inode being referenced does not really exist).

 

[funkyd]

"verify" is the correct utility to run with AdvFS. If you are looking to delete the file that lacks the directory entry, you can use "verify -d [domain]". If it is the root_domain, you must also specify "-r".

HTH

- Funky D

 

[GeorgeT]

verify doesn't fix bogus directory entries. It will take care of "lost" files that it finds - files that exist without directory entries by either removing or creating links for them depending on the flag specified.