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

Re: [Linux-cluster] gfs2.fsck bug



----- Original Message -----
| hi,
| 
| our gfs2 datasets are down; when i try to do a mount i get:
| 
| [root DBT1 ~]# mount -a
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| /sbin/mount.gfs2: node not a member of the default fence domain
| /sbin/mount.gfs2: error mounting lockproto lock_dlm
| 
| our cluster.conf is consistent across all devices (listed below).
| 
| so i thought an fsck would fix this, then i get:
| 
| [root DBT1 ~]# fsck.gfs2 -fnp /dev/NEWvg/NEWlvTemp
| (snippage)
| RG #4909212 (0x4ae89c) free count inconsistent: is 16846 should be
| 17157
| Resource group counts updated
| Unlinked block 8639983 (0x83d5ef) bitmap fixed.
| RG #8639976 (0x83d5e8) free count inconsistent: is 65411 should be
| 65412
| Inode count inconsistent: is 20 should be 19
| Resource group counts updated
| Pass5 complete
| The statfs file is wrong:
| 
| Current statfs values:
| blocks: 43324224 (0x2951340)
| free: 38433917 (0x24a747d)
| dinodes: 21085 (0x525d)
| 
| Calculated statfs values:
| blocks: 43324224 (0x2951340)
| free: 38466752 (0x24af4c0)
| dinodes: 21083 (0x525b)
| The statfs file was fixed.
| 
| gfs2_fsck: bad write: Bad file descriptor on line 44 of file buf.c
| 
| i read in https://bugzilla.redhat.com/show_bug.cgi?id=457557 that
| there
| is some way of fixing this with gfs2_edit - are there docs available?

Hi Yvette,

There is not enough information to know whether or not this may
be fixed easily with gfs2_edit since I don't know what block it's
failing on when you run fsck.gfs2.

What version of fsck.gfs2 are you running?  Are you running the version
from my people page?  If not, you could try it.

http://people.redhat.com/rpeterso/Experimental/RHEL5.x/gfs2/fsck.gfs2

Regards,

Bob Peterson
Red Hat File Systems


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