[Veritas-vx] Volume Corrupted

2007-07-24 Thread Ketan Patel
Gurus, Fsck on a corrupted volume displays following message: [EMAIL PROTECTED] # mount /backup UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/localdg/localdg_vol01 is corrupted. needs checking [EMAIL PROTECTED] # fsck -F vxfs -n /dev/vx/rdsk/localdg/localdg_vol01 pass0 - checking structural

Re: [Veritas-vx] Volume Corrupted

2007-07-24 Thread Myers, Mike
- 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

Re: [Veritas-vx] Volume Corrupted

2007-07-24 Thread Darren Dunham
[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

Re: [Veritas-vx] Volume Corrupted

2007-07-24 Thread Ketan Patel
App team requested more space on /backup. Allocated 300 gigs more to localdg. While expanding both the volume and its fs using vxresize (my colleague fired it from VEA), it just got hung. The probable reason might be - fsadm requires some free space in the background to carry out the expansion.