[Linux-cluster] no version for "gfs2_unmount_lockproto"
Ferenc Wagner
wferi at niif.hu
Wed Feb 13 08:23:00 UTC 2008
Bob Peterson <rpeterso at redhat.com> writes:
> On Tue, 2008-02-12 at 22:29 +0100, Ferenc Wagner wrote:
>> Actually, I also patched my kernel tree like this. In cases when I
>> forgot it, I wasn't even allowed to load the gfs module into the
>> kernel. In this case the "tainted" warning was related to a slight
>> vermagic mismatch, and after recompiling everything properly, it went
>> away.
>>
>> But the issue remained: the mount command just sits there, consuming
>> some CPU, and by now I've got the following console output (with my
>> notes in the brackets):
>
>> Now, mount is still stalled, and still consumes 6% of CPU.
>
> This gfs hang on failed mounts is documented in bugzilla bug #425421,
> and I've already got a patch for it. Since this bug was reported
> internally to Red Hat, I don't know if this bug record is viewable by
> the public. (I don't have control over the permission bits and how
> they default, so don't shoot the messenger.) :7)
:) I certainly wouldn't have, especially that you provided the patch.
But no worries, the bugzilla entry was perfectly accessible for me.
> The fix has not been shipped yet due to code freeze, but I'll attach
> the patch that fixes it below.
Thanks! This patch indeed fixed the hang. But of course not the
mount:
Trying to join cluster "lock_dlm", "pilot:test"
Joined cluster. Now mounting FS...
GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)
A stab in the dark:
# gfs_tool jindex /dev/mapper/gfs-test
gfs_tool: /dev/mapper/gfs-test is not a GFS file/filesystem
Scary. What may be the problem? The other node is using this
volume... Can even unmount/remount it. Though in dmesg it says:
GFS: fsid=pilot:test.0: jid=0: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=0: Looking at journal...
GFS: fsid=pilot:test.0: jid=0: Done
GFS: fsid=pilot:test.0: jid=1: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=1: Looking at journal...
GFS: fsid=pilot:test.0: jid=1: Done
GFS: fsid=pilot:test.0: jid=2: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=2: Looking at journal...
GFS: fsid=pilot:test.0: jid=2: Done
GFS: fsid=pilot:test.0: jid=3: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=3: Looking at journal...
GFS: fsid=pilot:test.0: jid=3: Done
GFS: fsid=pilot:test.0: jid=4: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=4: Looking at journal...
GFS: fsid=pilot:test.0: jid=4: Done
GFS: fsid=pilot:test.0: jid=5: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=5: Looking at journal...
GFS: fsid=pilot:test.0: jid=5: Done
Maybe it's locking all journals? Why?
--
Thanks,
Feri.
More information about the Linux-cluster
mailing list