Legacy BlueArc

quota command from centos

Discussion created by Legacy BlueArc on Feb 3, 2011
Branched to a new discussion

Originally posted by: kohlerr

 

 

 

Hi all,

 

I was wondering if anyone got different behaviors when using the quota command in centos 5.4 or 5.5.

 

Titan 2200 version 6.1.1684.23

 

Here's the easiest reproduceable error:

 

Goal: view a quota of another user from centos.

 

Problem: quota username returns quota correct but has the first user's filesystem path.

 

Environment: centos 5.5, we will only mount nfs home directories coming from one virtual volume, no others are mounted. These are user quotas with hard limits in the virtual volume.

 

Reproduceable: yes

 

Steps:

1.) Be root and make sure no home directories are mounted from the titan.

2.) ls /home/user1

3.) quota user1

     Returns a correct ouput:

Disk quotas for user user1 (uid ####):

     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace

titan:/sas_pool/staff/user1

                2042496       0 6291456          274410       0       0     

4.) ls /home/user2

5.) quota user2

     Has the correct quota for user2 but filesystem path is wrong, still says user1:

 

 

Disk quotas for user user2 (uid ###):

     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace

titan:/sas_pool/staff/user1

                2802784       0 6291456          274410       0       0    

6.) I can keep ls/quota more users on the same virtual volume and they will all output the correct quota amounts for each user, but the filesystem column has the first user1 still.

 

 

 

 

Has anyone seen this or can reproduce it?

 

Thanks!

Ryan

Outcomes