From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Problems mounting GFS2/GFS devices and possible ipv6 dlm issue.
Date: Tue, 25 Jul 2006 10:33:38 +0200 [thread overview]
Message-ID: <44C5D762.9080409@ubuntu.com> (raw)
In-Reply-To: <44C0C07F.3040009@ubuntu.com>
Just a short update after fixing a bunhc of bugs
Fabio Massimo Di Nitto wrote:
> David Teigland wrote:
>
> GFS1 lock_nolock
> .18-rc2: ok
> .17-5-server: ok
>
> GFS1 lock_dlm
> 18-rc2: nok
> .17-5-server: nok
>
> the mount operation seems to succeed. in dmesg:
>
> [ 148.044734] GFS: fsid=edgy:gfs1.4294967295: can't mount journal #4294967295
> [ 148.044800] GFS: fsid=edgy:gfs1.4294967295: there are only 4 journals (0 - 3)
>
> (note that there is no mount.gfs and it's not in CVS either. There is man page
> for it tho)
This is now ok after symlinking mount/umount.gfs to mount/jmount.gfs2 and
applying the patch i posted a few minutes ago to handle /mnt or /mnt/.
>
> umount generate a OOPS.
not anymore.
It is still NOT possible to mount the shared device on two nodes when using IPv6
address. It seems that the dlm kernel module isn't configured properly and we
get messages like this one in dmesg:
[ 403.530413] Joined cluster. Now mounting FS...
[ 403.537627] dlm: reject connect from unknown addr
[ 403.538067] dlm: Error sending to node 2 -32
[ 403.538119] dlm: Initiating association with node 2
also when trying to running other services, so it's not GFS/GFS2.
gfs2 status isn't changed.
Thanks
Fabio
--
I'm going to make him an offer he can't refuse.
prev parent reply other threads:[~2006-07-25 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 6:34 [Cluster-devel] Problems mounting GFS2 devices Fabio M. Di Nitto
2006-07-20 14:49 ` David Teigland
2006-07-21 11:54 ` Fabio Massimo Di Nitto
2006-07-25 8:33 ` Fabio Massimo Di Nitto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C5D762.9080409@ubuntu.com \
--to=fabbione@ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.