Not sure, but you'll find that GFS2 is still unstable. The required
bug-fixes haven't made it to the full release stage yet. RHEL5 stuff is
not for production use. Use GFS1 instead.
With the latest GFS2 packages on FC7, I can consistently achieve a
permanent (as in time to reboot the whole cluster) dead-lock within about
10 seconds of fairly light use.
Gordan
On Mon, 8 Oct 2007, John Vijoe George wrote:
I have a four node cluster with four storage nodes as well. I created 4 volume groups vg1,vg2,vg3,vg4 from the storage nodes and used mkfs.gfs2 to make a gfs2 filesystem.
# mkfs.gfs2 -t c1:gfs1 -p lock_dlm -j 4 -r 2048 -J 128 /dev/vg1/lv0
I repeated the above for each volume group. I then mounted vg1 in to /mnt1 of one of the cluster nodes as follows:
# mount -t gfs2 -o quota=off /dev/vg1/lv0 /mnt1
It succeeded in mounting. But, when I try to mount the next volume group, I get an error as follows:
#mount -t gfs2 -o quota=off /dev/vg4/lv0 /mnt4
/sbin/mount.gfs2: lock_dlm_join: gfs_controld join error: -22
/sbin/mount.gfs2: error mounting lockproto lock_dlm
What could be the reason behind it? Am I messing up something related to lock_dlm? Are my options to gfs2.mkfs right? Any help is appreciated.
The following gfs modules were loaded:
# lsmod | grep gfs
gfs2 519988 2 lock_dlm
configfs 62236 2 dlm
Regards,
John G
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
--
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
