Thanks,
That made it so I can mount it from the other nodes, but now I can't
mount it on the storage server.
This is what dmesg reports:
GFS: fsid=SAN1:VserversFS.0: Joined cluster. Now mounting FS...
GFS: fsid=SAN1:VserversFS.0: jid=0: Trying to acquire journal lock...
GFS: fsid=SAN1:VserversFS.0: jid=0: Looking at journal...
GFS: fsid=SAN1:VserversFS.0: jid=0: Done
GFS: fsid=SAN1:VserversFS.0: jid=1: Trying to acquire journal lock...
GFS: fsid=SAN1:VserversFS.0: jid=1: Looking at journal...
GFS: fsid=SAN1:VserversFS.0: jid=1: Done
GFS: fsid=SAN1:VserversFS.0: jid=2: Trying to acquire journal lock...
GFS: fsid=SAN1:VserversFS.0: jid=2: Looking at journal...
GFS: fsid=SAN1:VserversFS.0: jid=2: Done
GFS: fsid=SAN1:VserversFS.0: jid=3: Trying to acquire journal lock...
GFS: fsid=SAN1:VserversFS.0: jid=3: Looking at journal...
GFS: fsid=SAN1:VserversFS.0: jid=3: Done
GFS: fsid=SAN1:VserversFS.0: fatal: filesystem consistency error
GFS: fsid=SAN1:VserversFS.0: inode = 52732294/52732294
GFS: fsid=SAN1:VserversFS.0: function = gfs_change_nlink
GFS: fsid=SAN1:VserversFS.0: file =
/usr/src/cluster/cluster.STABLE.20050701/gfs-kernel/src/gfs/inode.c, line
= 843
GFS: fsid=SAN1:VserversFS.0: time = 1120748944
GFS: fsid=SAN1:VserversFS.0: about to withdraw from the cluster
GFS: fsid=SAN1:VserversFS.0: waiting for outstanding I/O
GFS: fsid=SAN1:VserversFS.0: telling LM to withdraw
lock_dlm: withdraw abandoned memory
GFS: fsid=SAN1:VserversFS.0: withdrawn
mh_magic = 0x01161970
mh_type = 4
mh_generation = 13
mh_format = 400
mh_incarn = 4
no_formal_ino = 52732294
no_addr = 52732294
di_mode = 0600
di_uid = 31
di_gid = 32
di_nlink = 0
di_size = 0
di_blocks = 1
di_atime = 1120690913
di_mtime = 1120690938
di_ctime = 1120690938
di_major = 0
no_formal_ino = 0
no_addr = 0
di_eattr = 0
di_reserved =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
I'm not sure what else I am missing.
Also, the mount I am doing from the clients are done with mounting the
gnbd device ie.. /dev/gnbd/fs
On the storage server itself, I am mounting the actual device ie.. /dev/md0
Don't know if that causes an issue doing it that way or not.
Any other thoughts as to how to get my errors fixed.
Thanks,
Jon
Jason Lanclos wrote:
>On Thursday 07 July 2005 09:33 am, Jon Scottorn wrote:
>
>
>>GFS: Trying to join cluster "fsck_dlm", "SAN1:VserversFS"
>>lock_harness: can't find protocol fsck_dlm
>>GFS: can't mount proto = fsck_dlm, table = SAN1:VserversFS, hostdata =
>>
>>
>>
>
> the lock protocol should be lock_dlm not fsck_dlm
>
> you can change this with gfs_tool
> gfs_tool sb <device> proto lock_dlm
>
>
>
--
Linux-cluster@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/linux-cluster
