A very small GFS2 fails to mount with error "can't read superblock" in a Pacemaker cluster
Issue
-
A GFS2 filesystem created on a very small volume (e.g., 500 MB) fails to mount.
# mount -t gfs2 -o noatime /dev/bobsrhel8/test_lv /mnt/gfs2 mount: /mnt/gfs2: can't read superblock on /dev/mapper/bobsrhel8-test_lv.
-
The console and
dmesg
show a filesystem withdrawal after trying to mount a GFS2 filesystem.[ 108.701890] gfs2: fsid=dm-6: Now mounting FS... [ 108.707364] gfs2: fsid=dm-6.0: fatal: filesystem consistency error [ 108.707364] inode = 1 67 [ 108.707364] function = gfs2_check_internal_file_size, file = fs/gfs2/inode.h, line = 92 [ 108.724375] gfs2: fsid=dm-6.0: about to withdraw this file system [ 108.730477] gfs2: fsid=dm-6.0: withdrawn [ 108.734404] CPU: 49 PID: 10065 Comm: mount Kdump: loaded Not tainted 4.18.0-147.el8.x86_64 #1 [ 108.742917] Hardware name: Dell Inc. PowerEdge R740/00WGD1, BIOS 1.4.9 06/29/2018 [ 108.750396] Call Trace: [ 108.752857] dump_stack+0x5c/0x80 [ 108.756184] gfs2_lm_withdraw.cold.1+0xe9/0xf8 [gfs2] [ 108.761243] gfs2_consist_inode_i+0x35/0x40 [gfs2] [ 108.766035] gfs2_jdesc_check+0xa2/0xb0 [gfs2] [ 108.770481] init_inodes+0x4e4/0x750 [gfs2] [ 108.774666] ? init_inodes+0x292/0x750 [gfs2] [ 108.779024] ? snprintf+0x49/0x60 [ 108.782343] fill_super+0x819/0xae0 [gfs2] [ 108.786441] ? vsnprintf+0x37c/0x520 [ 108.790033] ? gfs2_glock_nq_num+0x65/0xc0 [gfs2] [ 108.794736] ? snprintf+0x49/0x60 [ 108.798057] ? __raw_spin_unlock+0x10/0x10 [gfs2] [ 108.802779] gfs2_mount+0x255/0x280 [gfs2] [ 108.806886] mount_fs+0x3b/0x167
Environment
- Red Hat Enterprise Linux 8 (with the Resilient Storage Add-on)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.