(sorry if this is a dupe, but it looks like my mails aren''t posting to
the list)
Hello Folks,
A while back we accidentally started a 1.8.x cluster up with 2.x software (a
git command was missed setting it to the 1_8 branch). During that work, we
attempted to enable quotas on 2 file systems (generated the initial file, etc).
Once we realized our mistake, we back-rev''d to the 1.8.x train and most
everything went back smoothly except for quotas. Now whenever we attempt any
quota related commands, we get ioctl errors. For example:
[root at lrc-xfer ~]# lfs quota -u jwhite /clusterfs/vulcan/pscratch
Unexpected quotactl error: Inappropriate ioctl for device
Disk quotas for user jwhite (uid 40227):
Filesystem kbytes quota limit grace files quota limit grace
/clusterfs/vulcan/pscratch
[0] [0] [0] - [0] [0] [0] -
Some errors happened when getting quota info. Some devices may be not working or
deactivated. The data in "[]" is inaccurate.
[root at lrc-xfer ~]#
Does anyone know of a way to kick the quota internals to reset themselves and
initialize under the 1.8.x setup?
----------------
John White
HPC Systems Engineer
(510) 486-7307
One Cyclotron Rd, MS: 50C-3209C
Lawrence Berkeley National Lab
Berkeley, CA 94720
Hi John, My understanding is if your quota files are broken, and lfs quotacheck isn''t working, you can take a downtime and remount all the devices as ldiskfs and delete the lquota files, which should look something like: -rw-r--r-- 1 root root 6144 Jul 20 09:05 lquota_v2.group -rw-r--r-- 1 root root 6144 Jul 20 09:05 lquota_v2.user Then you shoule be able to run lfs quotacheck again. Of course, mounting as ldiskfs is dangerous, but I think the risk of this operation is not so high. I would make sure any crucial data is backed up. - Kit On 6/28/2012 1:23 PM, John White wrote:> (sorry if this is a dupe, but it looks like my mails aren''t posting to the list) > > Hello Folks, > A while back we accidentally started a 1.8.x cluster up with 2.x software (a git command was missed setting it to the 1_8 branch). During that work, we attempted to enable quotas on 2 file systems (generated the initial file, etc). Once we realized our mistake, we back-rev''d to the 1.8.x train and most everything went back smoothly except for quotas. Now whenever we attempt any quota related commands, we get ioctl errors. For example: > [root at lrc-xfer ~]# lfs quota -u jwhite /clusterfs/vulcan/pscratch > Unexpected quotactl error: Inappropriate ioctl for device > Disk quotas for user jwhite (uid 40227): > Filesystem kbytes quota limit grace files quota limit grace > /clusterfs/vulcan/pscratch > [0] [0] [0] - [0] [0] [0] - > Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate. > [root at lrc-xfer ~]# > > Does anyone know of a way to kick the quota internals to reset themselves and initialize under the 1.8.x setup? > ---------------- > John White > HPC Systems Engineer > (510) 486-7307 > One Cyclotron Rd, MS: 50C-3209C > Lawrence Berkeley National Lab > Berkeley, CA 94720 > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
This suggestion worked perfectly. Thanks! ---------------- John White HPC Systems Engineer (510) 486-7307 One Cyclotron Rd, MS: 50C-3209C Lawrence Berkeley National Lab Berkeley, CA 94720 On Jul 20, 2012, at 9:09 AM, Kit Westneat wrote:> Hi John, > > My understanding is if your quota files are broken, and lfs quotacheck > isn''t working, you can take a downtime and remount all the devices as > ldiskfs and delete the lquota files, which should look something like: > -rw-r--r-- 1 root root 6144 Jul 20 09:05 lquota_v2.group > -rw-r--r-- 1 root root 6144 Jul 20 09:05 lquota_v2.user > > Then you shoule be able to run lfs quotacheck again. > > Of course, mounting as ldiskfs is dangerous, but I think the risk of > this operation is not so high. I would make sure any crucial data is > backed up. > > - Kit > > On 6/28/2012 1:23 PM, John White wrote: >> (sorry if this is a dupe, but it looks like my mails aren''t posting to the list) >> >> Hello Folks, >> A while back we accidentally started a 1.8.x cluster up with 2.x software (a git command was missed setting it to the 1_8 branch). During that work, we attempted to enable quotas on 2 file systems (generated the initial file, etc). Once we realized our mistake, we back-rev''d to the 1.8.x train and most everything went back smoothly except for quotas. Now whenever we attempt any quota related commands, we get ioctl errors. For example: >> [root at lrc-xfer ~]# lfs quota -u jwhite /clusterfs/vulcan/pscratch >> Unexpected quotactl error: Inappropriate ioctl for device >> Disk quotas for user jwhite (uid 40227): >> Filesystem kbytes quota limit grace files quota limit grace >> /clusterfs/vulcan/pscratch >> [0] [0] [0] - [0] [0] [0] - >> Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate. >> [root at lrc-xfer ~]# >> >> Does anyone know of a way to kick the quota internals to reset themselves and initialize under the 1.8.x setup? >> ---------------- >> John White >> HPC Systems Engineer >> (510) 486-7307 >> One Cyclotron Rd, MS: 50C-3209C >> Lawrence Berkeley National Lab >> Berkeley, CA 94720 >> >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss