Hello all,
Centos 5.5
drbd --> lv --> gfs2
gfs2_tool 0.1.62 (built Mar 31 2010 07:34:45)
The filesystem was created in Centos5.2
Running gfs2_fsck seg faults:
[r...@tweety-2 /]# gfs2_fsck -v /dev/mapper/vg1-data1
Initializing fsck
Initializing lists...
jid=0: Looking at journal...
jid=0: Journal is clean.
jid=1: Looking at journal...
jid=1: Journal is clean.
jid=2: Looking at journal...
jid=2: Journal is clean.
jid=3: Looking at journal...
jid=3: Journal is clean.
jid=4: Looking at journal...
jid=4: Journal is clean.
jid=5: Looking at journal...
jid=5: Journal is clean.
Segmentation fault
gfs2_fsck[5131]: segfault at 00000000000000f0 rip 000000000040aefa
rsp 00007fffd02c2d50 error 4
The nice thing is that it also alters the lock mechanism defined for the
fs, in one that does not exist (fsck_dlm):
[r...@tweety-2 /]# mount /mounts
/sbin/mount.gfs2: error mounting /dev/mapper/vg1-data1 on /mounts:
No such file or directory
GFS2: fsid=: Trying to join cluster "fsck_dlm", "tweety:gfs2-11"
GFS2: can't find protocol fsck_dlm
GFS2: fsid=: can't mount proto=fsck_dlm, table=tweety:gfs2-11, hostdata=
GFS2: fsid=: Trying to join cluster "fsck_dlm", "tweety:gfs2-11"
GFS2: can't find protocol fsck_dlm
GFS2: fsid=: can't mount proto=fsck_dlm, table=tweety:gfs2-11, hostdata=
GFS2: fsid=: Trying to join cluster "fsck_dlm", "tweety:gfs2-11"
GFS2: can't find protocol fsck_dlm
GFS2: fsid=: can't mount proto=fsck_dlm, table=tweety:gfs2-11, hostdata=
It gets restored with:
[r...@tweety-2 /]# gfs2_tool sb /dev/mapper/vg1-data1 proto lock_dlm
You shouldn't change any of these values if the filesystem is mounted.
Are you sure? [y/n] y
current lock protocol name = "fsck_dlm"
new lock protocol name = "lock_dlm"
Done
[r...@tweety-2 /]#mount /mounts
[r...@tweety-2 /]#
GFS2: fsid=: Trying to join cluster "lock_dlm", "tweety:gfs2-11"
GFS2: fsid=tweety:gfs2-11.0: Joined cluster. Now mounting FS...
GFS2: fsid=tweety:gfs2-11.0: jid=0, already locked for use
GFS2: fsid=tweety:gfs2-11.0: jid=0: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=0: Done
GFS2: fsid=tweety:gfs2-11.0: jid=1: Trying to acquire journal lock...
GFS2: fsid=tweety:gfs2-11.0: jid=1: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=1: Done
GFS2: fsid=tweety:gfs2-11.0: jid=2: Trying to acquire journal lock...
GFS2: fsid=tweety:gfs2-11.0: jid=2: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=2: Done
GFS2: fsid=tweety:gfs2-11.0: jid=3: Trying to acquire journal lock...
GFS2: fsid=tweety:gfs2-11.0: jid=3: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=3: Done
GFS2: fsid=tweety:gfs2-11.0: jid=4: Trying to acquire journal lock...
GFS2: fsid=tweety:gfs2-11.0: jid=4: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=4: Done
GFS2: fsid=tweety:gfs2-11.0: jid=5: Trying to acquire journal lock...
GFS2: fsid=tweety:gfs2-11.0: jid=5: Looking at journal...
GFS2: fsid=tweety:gfs2-11.0: jid=5: Done
I have saved all my date, but before destroying this GFS2, would any
developer like me to assist in debugging?
(Filed as https://bugzilla.redhat.com/show_bug.cgi?id=620384)
Sincerely,
Theophanis Kontogiannis
--
Linux-cluster mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-cluster
