Steven Lee
Center for Advanced Computing Cornell University
On Mar 11, 2008, at 3:18 PM, Abhijith Das wrote: Hi Steven,
Here are some things you could try.
1. comment out the gfs2 entry in /etc/fstab and mount only one gfs2 fs
on only one node and perform the reset and init.
2. I wonder if this happens in a freshly created gfs2 fs. Just for
sanity, try this:
if you have a spare device, use that or create a file (and mount
loopback)
dd if=/dev/zero of=/tmp/foo bs=1024 count=1048576
Use the 'nolock' locking protocol. This will make your filesystem
single-node
mkfs.gfs2 -j 1 -p lock_nolock -t foo:bar /tmp/foo
If you're not using a loopback device, you can remove 'loop' below.
mount -t gfs2 -o loop,quota=on /tmp/foo /mnt/bar
gfs2_quota reset -f /mnt/bar
gfs2_quota init -f /mnt/bar
If in both these cases you see the warning, we have a bug. You can go
ahead and file one against me at bugzilla.redhat.com
It would really help if you can dump the device containing the
filesystem to a file, compress it and post it somewhere. If that's not
possible,
I'd like to take a look at the hidden quota file. 'mount -t gfs2meta
/dev/gfs2-device /mnt/gfs2-metamount' will mount the gfs2 meta filesystem.
(You should have the gfs2 filesystem already mounted before you attempt
mounting gfs2meta). There should be a quota file under this
mount that you can copy and send out. I should warn you though that the
meta mount is only used by the gfs2_utils to manipulate
gfs2 metadata and must not be used as a normal filesystem. You should
unmount the metafs as soon as you're done with it.
Thanks,
--Abhi
Steven Lee wrote:
Hi Abhi,
Thanks for your response. I didn't do much to run into this problem.
The 2 file servers in this RedHat cluster are running fully patched
RHEL 5.1. In addition to NFS, they are also serving to Windows
clients using samba. ACLs were enabled. Everything was running
smoothly until I tried enabling quotas: I simply added quota=on in
/etc/fstab and re-mounted the GFS partitions.
As you can see below, I simply issued "reset" and then "init" command
before getting the error message. The "get" command also returned
inconsistent result from the "list" command. This is a new file
server still under testing with only a small "prof" directory.
Did I do anything wrong?
Steven
---
[root@cacfs02 ~]# *mount *
/dev/mapper/vg00-root on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/vg00-var on /var type ext3 (rw)
/dev/mapper/vg00-usr on /usr type ext3 (rw)
/dev/mapper/vg00-tmp on /tmp type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
none on /sys/kernel/config type configfs (rw)
/dev/mapper/st01vg01-lv01 on /export/gfs01 type gfs2
(rw,hostdata=jid=0:id=65537:first=0,acl,quota=on)
/dev/mapper/st01vg02-lv01 on /export/gfs02 type gfs2
(rw,hostdata=jid=1:id=393218:first=0,acl,quota=on)
/dev/mapper/st02vg01-lv01 on /export/gfs03 type gfs2
(rw,hostdata=jid=1:id=524290:first=0,acl,quota=on)
/dev/mapper/st02vg02-lv01 on /export/gfs04 type gfs2
(rw,hostdata=jid=1:id=655362:first=0,acl,quota=on)
[root@cacfs02 ~]# *gfs2_quota reset -f /export/gfs02*
This operation will permanently erase all quota information. You will
have to re-assign all quota limit/warn values. Proceed [y/N]? y
[root@cacfs02 ~]# *gfs2_quota init -f /export/gfs02*
warning: quota file size not a multiple of struct gfs2_quota
Warning: This filesystem doesn't seem to have the new quota list
format or the quota list is corrupt. list, check and init operation
performance will suffer due to this. It is recommended that you run
the 'gfs2_quota reset' operation to reset the quota file. All current
quota information will be lost and you will have to reassign all quota
limits and warnings
[root@cacfs02 ~]# *gfs2_quota list -f /export/gfs02*
warning: quota file size not a multiple of struct gfs2_quota
Warning: This filesystem doesn't seem to have the new quota list
format or the quota list is corrupt. list, check and init operation
performance will suffer due to this. It is recommended that you run
the 'gfs2_quota reset' operation to reset the quota file. All current
quota information will be lost and you will have to reassign all quota
limits and warnings
user root: limit: 0.0 warn: 0.0 value: 0.0
user prof: limit: 0.0 warn: 0.0 value: 0.4
group root: limit: 0.0 warn: 0.0 value: 0.0
group Domain Users: limit: 0.0 warn: 0.0 value: 0.4
[root@cacfs02 ~]# *gfs2_quota get -u prof -f /export/gfs02*
warning: quota file size not a multiple of struct gfs2_quota
user prof: limit: 0.0 warn: 0.0 value: 0.0
[root@cacfs02 ~]# *ls -l /export/gfs02*
total 8
drwxrwx---+ 12 prof Domain Users 3864 Mar 10 14:06 prof
[root@cacfs02 ~]# *uname -a*
Linux cacfs02.cac.cornell.edu 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5
11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
[root@cacfs02 ~]# *rpm -q gfs2-utils*
gfs2-utils-0.1.38-1.el5
---
Steven Lee
shl1@xxxxxxxxxxxxxxx <mailto:shl1@xxxxxxxxxxxxxxx>
Center for Advanced Computing
Cornell University
On Mar 10, 2008, at 5:45 PM, Abhijith Das wrote:
Hi Steven,
Does the 'gfs2_quota reset' operation fail for some reason? The reset
operation should truncate your quota file and you should be able to
start using quotas afresh.
I just tried resetting and initing the quota file on my gfs2 filesystem
(latest bits) and I don't see this warning.
What kernel and what gfs2-utils packages are you running?
Also, any clue with respect to the quota operations you did on the fs
to get to this state would be helpful.
Are you able to perform other quota operations like limit, warn, list,
get etc., without seeing this warning?
Thanks,
--Abhi
Steven Lee wrote:
Hi,
I'm trying to turn on quota on a GFS2 file system. The cluster has 2
nodes with 2 EMC SAN storage units. The nodes are running RHEL 5.1.
When I initialize the quota file using:
*gfs2_quota init -f /export/gfs02*
I would get the following warning:
*warning: quota file size not a multiple of struct gfs2_quota*
*
*
*Warning: This filesystem doesn't seem to have the new quota list
format or the quota list is corrupt. list, check and init operation
performance will suffer due to this. It is recommended that you run
the 'gfs2_quota reset' operation to reset the quota file. All current
quota information will be lost and you will have to reassign all quota
limits and warnings*
I've tried the "gfs2_quota reset" and then "gfs2_quota init" commands,
but still got the warning. I've looked through RedHat GFS
documentation and googled for gfs2. Very little information seems to
be available.
Any help is appreciated. Thanks!
Steven Lee
shl1@xxxxxxxxxxxxxxx <mailto:shl1@xxxxxxxxxxxxxxx>
Center for Advanced Computing
Cornell University
------------------------------------------------------------------------
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx <mailto:Linux-cluster@xxxxxxxxxx>
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx <mailto:Linux-cluster@xxxxxxxxxx>
https://www.redhat.com/mailman/listinfo/linux-cluster
------------------------------------------------------------------------
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
|
