Actually, our layout is RAID 0+1. All we want to is add the extra
capacity of 2 disks per mirror by growing the filesystem. There is only
one filesystem on the RAID.
Thanks,
Richard
-Original Message-
From: Doug Hughes [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:53 PM
Jaehne, Richard S wrote:
Actually, our layout is RAID 0+1. All we want to is add the extra
capacity of 2 disks per mirror by growing the filesystem. There is only
one filesystem on the RAID.
Thanks,
In that case, (as long as you aren't adding in a hidden layer of LUN
redirection in
Actually, our layout is RAID 0+1. All we want to is add the extra
capacity of 2 disks per mirror by growing the filesystem. There is only
one filesystem on the RAID.
Without specific details (like 'vxprint -ht vol' and the way the array
is configured and presented to the host), it's going to
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
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
[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
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.
