GFS file system withdraws with "fatal: filesystem consistency error", fsck.gfs reports "No '.' entry found for directory inode at block", but file system continues to withdraw in a RHEL 5 Resilient Storage cluster
Issue
- We had a GFS filesystem withdraw, then ran
fsck.gfsto clean it up. It found some problems and claims to have fixed them, but the file system keeps withdrawing. - GFS1 file system is withdrawing with a filesystem consistency error but
fsck.gfsis not fixing it, despite finding several "No '.' entry found for directory inode'
Checking directory inodes.
No '.' entry found for directory inode at block 15569
The directory was fixed.
Entries is 3 - should be 2 for inode block 15569
No '.' entry found for directory inode at block 15572
The directory was fixed.
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: fatal: filesystem consistency error
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: inode = 15569/15569
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: function = do_filldir_single
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: file = /builddir/build/BUILD/gfs-kmod-0.1.34/_kmod_build_/src/gfs/dir.c, line = 1137
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: time = 1456765652
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: about to withdraw from the cluster
Feb 29 12:07:32 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: telling LM to withdraw
Feb 29 12:07:33 cs-rh5-1 kernel: GFS: fsid=cs5cluster:lv41.0: withdrawn
Environment
- Red Hat Enterprise Linux (RHEL) 5 with the Resilient Storage Add-On
- GFS
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.