You don't really have a choice unless you happen to have a file system guru on staff who enjoys playing with fsdb :)
Generally speaking fsck will recover things well though like in all complex systems there are spectacular exceptions. Judging on small number of errors it's showing in the output below I'd say you chances of a good clean fsck are excellent. If the system is absolutely critical and going to backups is an option, you may want to consider that. You should also investigate the source of the corruption and address that. Cheers, - Mike.Myers <at> nwdc.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ketan Patel Sent: Tuesday, July 24, 2007 10:08 AM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] Volume Corrupted Gurus, Fsck on a corrupted volume displays following message: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> # mount /backup UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/localdg/localdg_vol01 is corrupted. needs checking [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> # fsck -F vxfs -n /dev/vx/rdsk/localdg/localdg_vol01 pass0 - checking structural files pass1 - checking inode sanity and blocks pass2 - checking directory linkage pass3 - checking reference counts pass4 - checking resource maps au 7572 emap incorrect - fix? (ynq)n au 7572 summary incorrect - fix? (ynq)n fileset 1 iau 0 summary incorrect - fix? (ynq)n OK to clear log? (ynq)n sanity checks/updates have not been completed - restart? (ynq)n Shall I go ahead with fsck? Will it cause me lose my data? Ketan _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
