Re: Can't mount snapshot LUN with new infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 22, 2007 at 05:53:41PM +0900, Kenji Wakamiya wrote:
> Hello,
> 
> I have a three node GFS1 cluster that is based on OpenAIS and CentOS 5,
> and am using NetApp's iSCSI LUN as a block device.
> 
> Now I want to mount that LUN's snapshot LUN with lock_nolock on any
> member of the three nodes, with having mounted original LUN.
> 
> With old version of CMAN (not OpenAIS), the same thing worked well.
> But I've got the following error with new infrastructure:
> 
> # mount -t gfs
> /dev/isda on /web type gfs (rw,hostdata=jid=2:id=131074:first=0,acl)
> # mount -t gfs -o lockproto=lock_nolock /dev/isdb /testsnap
> /sbin/mount.gfs: error 17 mounting /dev/isdb on /testsnap

> Now I have /sys/fs/gfs/cluster3:gfstest/.  So I suspect that a
> conflict between two LUN's lock table names is occurring in sysfs.

Yes, you're exactly right.  You can also override the locktable name with
a mount option:

  mount -t gfs -o lockproto=lock_nolock,locktable=foo /dev/isdb /testsnap

Dave

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux