[Veritas-vx] enable quota on big vxfs filesystem

[Carl E. Ma]

Hello all,

I thought enabling user quota is straight forward. Here is what I did to enable the vxfs quota on a 1.8T user home filesystem(95% usage). We are using vxfs 4.1 MP2RP4 on solaris 9.

1.$vxupgrade -o quota -n 6 /export/home
..
##this took about one hour to finish
..

2.$mount -F vxfs -o remount,quota /dev/vx/dsk/dg1/homevol /export/home
..
##this keeps running for 6 hours and whole system is almost hang. Each vx command takes about 15 minutes to get output; truss doesn't show much process activity while there is still disk activity

3. since step 2 can't finish within maintenance window, I have to reboot server to get rid of the pending mount process

My questions are:
.is there any potential problem since I stopped the mount before its ending
.should I use "vxquotaon /export/home" instead of "mount" to enable quota on this filesystem? My understanding that "vxquotaon" may not significantly downgrade filesystem performance so badly.
.how much time I should expect to get quota enabled on such a big,almost full filesystem? I read some benchmarks that it may need 10 minutes for every million inodes. There are 1,890,000,000 inodes on this filesystem. so it will take "1890*10/60=315 hours"!!!

Any inputs?

Thanks in advance,

carl

[Robinson, Greg]

UNCLASSIFIED

Hi Carl,

This is normal behaviour for a very large filesystem. We had a similar
experience for our 1.2TB home drive filesystem. The issue lies in that
veritas needs to traverse the entire filesystem in order to calculate
the quotas.

There is nothing you can do, other than have a very large maintenance
window (or smaller filesystems which we are planning to impliment).

Greg.

-----Original Message-----
From: veritas-vx-***@mailman.eng.auburn.edu
[mailto:veritas-vx-***@mailman.eng.auburn.edu] On Behalf Of Carl E.
Ma
Sent: Monday, 12 July 2010 12:29 PM
To: veritas-***@mailman.eng.auburn.edu
Cc: ***@yahoo.ca
Subject: [Veritas-vx] enable quota on big vxfs filesystem

Hello all,

I thought enabling user quota is straight forward. Here is what I did to
enable the vxfs quota on a 1.8T user home filesystem(95% usage). We are
using vxfs 4.1 MP2RP4 on solaris 9.

1.$vxupgrade -o quota -n 6 /export/home
..
##this took about one hour to finish
..

2.$mount -F vxfs -o remount,quota /dev/vx/dsk/dg1/homevol /export/home
..
##this keeps running for 6 hours and whole system is almost hang. Each
vx command takes about 15 minutes to get output; truss doesn't show much
process activity while there is still disk activity

3. since step 2 can't finish within maintenance window, I have to reboot
server to get rid of the pending mount process

My questions are:
.is there any potential problem since I stopped the mount before its
ending
.should I use "vxquotaon /export/home" instead of "mount" to enable
quota on this filesystem? My understanding that "vxquotaon" may not
significantly downgrade filesystem performance so badly.
.how much time I should expect to get quota enabled on such a
big,almost full filesystem? I read some benchmarks that it may need 10
minutes for every million inodes. There are 1,890,000,000 inodes on this
filesystem. so it will take "1890*10/60=315 hours"!!!

Any inputs?

Thanks in advance,

carl


_______________________________________________
Veritas-vx maillist - Veritas-***@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

IMPORTANT: This email remains the property of the Department of Defence
and is subject to the jurisdiction of section 70 of the Crimes Act 1914.
If you have received this email in error, you are requested to contact
the sender and delete the email.