Just as an FYI my preferred order for fscks
# fsck -F vxfs /dev/vx/rdsk/DG_name/VOL_name
Intent LOG ONLY replay
# fsck -F vxfs -o full,nolog -n /dev/vx/rdsk/DG_name/VOL_name
FILE SYSTEM AND METADATA STRUCTURES ONLY - NO INTENT LOG - a LOOK at what will
happen remembering there ARE
Greg
I am not sure that is ever going to work - but there are some things to
look at. In CDS format (Unix) the private region is at the beginning of
disk on the whole disk partition ( 65536 blocks in VxVM Ver 5.x, 2048
blocks in VxVM 4.x ).
# vxdisk list c3t50060E80004372C0d25s2
public:
Colin
OK - I see you are using enclosure naming - and BTW - the /dev/vx/dmp
/dev/vx/dmp are just the same as disks BUT with the added provision of
DMP to keep the device online.
How many paths to these devices
# vxdmpadm getsubpaths
or
# vxdisk path
If a CLARiiON , and if only 2 paths
Martin
Some things to look at - are the read_ahead VxFS tuning - this is
optimised to sequential reads. Other VxFS tunables are here
http://support.veritas.com/docs/344352 The usual one is max_direct_iosz
for performance. Also you could vxtrace the volume plex subdisk
operations while the
It works
#umount /mnt
#mount -F vxfs /dev/vx/dsk/testdg/vols /mnt
#vxquot /mnt
/dev/vx/rdsk/testdg/vols:
USERS
11266 root
4096 adm
4096 bin
4096 cstynes
4096 gdm
4096 daemon
4096 joe
4096 listen
