[Lustre-discuss] quota persistence over filesystem shutdown
Guy Coates
gmpc at sanger.ac.uk
Wed May 21 09:32:22 PDT 2008
Hi all,
I have run into a problem with the quota system not being re-activated over a
filesystem shutdown.
I initially activated quotas on the lustre filesystem by running:
#quotacheck ug /mnt/data1
and then setting a user quota with:
#lfs -u gmpc 307200 309200 10000 11000 /mnt/data1
quota-ing works as expected. If I umount and remount the filesystem on the
clients, the quota information and behaviour is preserved.
However, if I un-mount the clients and then restart the MDS/OSTs, the quota
system is not active once the filesystem is remounted on the client:
# lfs quota -u gmpc /mnt/data1
Disk quotas for user gmpc (uid xxxx):
Filesystem kbytes quota limit grace files quota limit grace
quota failed: No such process
If I run:
#lfs quotaon /mnt/data1
on the client, the quota system is re-activated and everything works as expected.
# lfs quota -u gmpc /mnt/data1
Disk quotas for user gmpc (uid 10795):
Filesystem kbytes quota limit grace files quota limit grace
/mnt/data1 58308 307200 309200 1302 10000 11000
data1-MDT0000_UUID
432 0 102400 1302 0 5000
data1-OST0000_UUID
3272 0 102400
data1-OST0001_UUID
50500 0 102400
data1-OST0002_UUID
2052* 0 1
data1-OST0003_UUID
2052* 0 1
I am running lustre 1.6.4.3 / kernel 2.6.18 on debian ia32. The lquota module
has been loaded, and there are no error messages being generated on the
client/ost/mds.
Cheers,
Guy
--
Dr. Guy Coates, Informatics System Group
The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK
Tel: +44 (0)1223 834244 x 6925
Fax: +44 (0)1223 496802
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
More information about the lustre-discuss
mailing list