Re: [Veritas-vx] Not able to resize the Volume

2008-08-11 Thread Luke Francis, Aju
Make sure that the file system does not have any snapshot file system mounted on it also attempt the resize when the file system has less of a load on it. If it continues to fail with errno 16 then unmount the file system, perform fsck -o full, remount, and try again. Cheers, Aju

Re: [Veritas-vx] Not able to resize the Volume

2008-08-11 Thread Scott Kaiser
In addition to snapshot, errno 16 can be caused if the fullfsck flag is set. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luke Francis, Aju Sent: Monday, August 11, 2008 4:55 AM To: Praveent T M; veritas-vx@mailman.eng.auburn.edu Subject: Re:

[Veritas-vx] Veritas flag meanings?

2008-08-11 Thread Myers, Mike
Folks, We've starting (probably with VxFS 5.0) seeing that newly created Veritas file systems (eg. just ran mkfs -F vxfs /dev/vx/rdsk/rootdg/junk2) have a flag bit set: # vxassist make junk 1g # mkfs -F vxfs /dev/vx/rdsk/rootdg/junk version 7 layout

[Veritas-vx] How to tell the utilization state of a cache object?

2008-08-11 Thread Jon Stanley
How can I tell how utilized a cache object is? I know that I can do 'vxsnap print' and take a look at %DIRTY and %VALID and get an idea, but is there some command that will tell me how much data is in cache at a given time? Here's the setup (SF 4.1MP4 on Linux): # vxprint Disk group: datadg TY