vxquota can fail to turn on if files have large UID's
| Article:TECH199682 | | | Created: 2012-11-13 | | | Updated: 2012-11-14 | | | Article URL http://www.symantec.com/docs/TECH199682 |
Problem
In previous version of vxfs uid's for user nobody would be set as 4294967294. With fsdb the uid of the file would be translated to "-2"
bash-3.00# echo "999fset.48389i" | fsdb -F vxfs /dev/vx/rdsk/testdg/testvol
Error
when mounting the filesystem with -o quota the following error will occur.
bash-3.00# mount -F vxfs -o quota /dev/vx/dsk/testdg/testvol /test/
UX:vxfs mount: ERROR: V-3-21301: VX_QUOTAON failed on quota file "/test/quotas"
the filesystem will still mount but quota's will fail when reporting on them.
bash-3.00# /opt/VRTS/bin/vxquotaon -v /test
UX:vxfs vxquotaon: ERROR: V-3-22210: /test: unexpected error 5 while changing quota state
Environment
Solaris 10 X86
Cause
Files having large UID's due to stale entries from previous versions.
Solution
To find the files having the large UID's:
# find /<mount-point> -user 4294967294 -print
Confirm the large UID's on the output from above:
# ls -n <file>
Change the UID on the file:
# chown nobody <file>
Example
find /test -user 4294967294 -print
bash-3.00# /opt/VRTS/bin/vxquotaon -v /test
UX:vxfs vxquotaon: INFO: V-3-23548: /test: user quotas turned on
UX:vxfs vxquotaon: INFO: V-3-23430: /test: group quotas turned on
|
|
| Description | Files having large UID's can cause vxquota to fail. |
Article URL http://www.symantec.com/docs/TECH199682
Terms of use for this information are found in Legal Notices
Thank you.