Inodes Vanishing
I recently installed CA eTrustAntivirus v7.1 for Solaris on a Solaris 8 test box. After the installion and reboot, when I run a ufsdump on the volume it's installed in I get the following error:
DUMP: Warning - directory at inode `83' vanished!
DUMP: Warning - directory at inode `8143' vanished!
DUMP: Warning - directory at inode `16278' vanished!
DUMP: Warning - directory at inode `24422' vanished!
DUMP: Warning - directory at inode `56933' vanished!
DUMP: Warning - directory at inode `81298' vanished!
DUMP: Warning - directory at inode `97625' vanished!
DUMP: Warning - directory at inode `349598' vanished!
DUMP: Warning - directory at inode `365778' vanished!
DUMP: Warning - directory at inode `382038' vanished!
Does anyone know what this means? Or how to fix it. I"ve since removed the Antivirus software in hopes of fixing it, but it hasn't worked. The only thing that seems to work is running 'fsck' on the volume, but when you access the volume and run another backup - the errors are back.
THanks,
Nick
[1125 byte] By [
PEIGIC] at [2007-11-25 23:16:05]
# 1
While most of the time it will work okay, ufsdump is not guaranteed to work on a filesystem that is mounted for writing. What you are seeing is likely caused by changes to the filesystem while it is running. This does not indicate any problem with the filesystem.
In fact, running 'fsck' on a mounted filesystem would be far more likely to cause problems than fix them.
Just as a test, can you unmount this filesystem and run ufsdump on it then? Also, if you want to fsck it, that would be an okay time to do so.
--
Darren
# 3
It's probably the AV stuff creating and removing directories during the dump...
You could ignore the warnings. ufsdump does two passes through the filesystem. One grabs all the inodes, the other grabs the information from it. If the file disappears between the passes, then it complains. I don't know how ufsrestore would handle the dump. It would probably either not restore the directory (no problem), or it would leave an empty directory there (maybe not a problem).
Or you could change to something other than ufsdump. Something that ran the filesystem like tar/star/Netbackup/Networker might not have the same issue.
--
Darren
