> On Oct 8, 2015, at 7:33 AM, Götz Waschk <[email protected]> wrote: > > I have a quota problem on a file system upgraded from Lustre 1.8 to > 2.5.3. The number of inodes reported by lfs getquota is obviously > wrong: > > # ls -l > insgesamt 3064024 > drwxr-sr-x 3 u248 icecube 1830912 28. Aug 2014 Callisto > drwxr-sr-x 2 u248 icecube 2301952 26. Aug 2014 CameraOutput > -rw-r--r-- 1 u248 icecube 21542 1. Aug 2014 LogCallistoM1_026202_.log > -rw-r--r-- 1 u248 icecube 439316480 15. Aug 2014 logs25000_35000.tar.gz > -rw-r--r-- 1 u248 icecube 224972800 18. Aug 2014 logs35000_40000.tar.gz > -rw-r--r-- 1 u248 icecube 225146880 28. Aug 2014 logscal40k-45k.tar.gz > -rw-r--r-- 1 u248 icecube 1122981634 28. Jul 2014 > Pr_za05to36_4_027617_ct1_w0.rfl > -rw-r--r-- 1 u248 icecube 1120948234 28. Jul 2014 > Pr_za05to36_4_027617_ct2_w0.rfl > # lfs quota -u u248 . > Disk quotas for user u248 (uid 20056): > Filesystem kbytes quota limit grace files quota limit grace > . 4709669648 0 0 - 1 0 > 0 - > > > Is this a known bug?
Not sure if this is a known bug. Have you tried regenerating the quota data? I have had to do this a few times on some OSTs. -- Rick Mohr Senior HPC System Administrator National Institute for Computational Sciences http://www.nics.tennessee.edu _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
