[LU-1998] Can't fsck/mount mdadm device with external journal after journal was deleted and re-added. LDISKFS-fs: journal UUID does not match

Thu, 20 Sep 2012 15:25:36 +0000

We encountered a problem with one of our OSTs that would not start because of "[ 5437.653340] md2: bitmap superblock UUID mismatch". Also while we were able to run fsck.ldiskfs (livermore's renaming) on the other md device on the OSS, on the problem target fsck was refusing to run because of the following error: "external journal does not support filesystem". So following directions posted by Andreas in an earlier lustre discuss thread, we removed the journal, ran fsck and re-added the external journal.

After running those steps and trying to mount -t lustre, it fails asking whether the ldiskfs module is available with "LDISKFS-fs: journal UUID does not match" in dmesg. In addition, fsck still reports the journal does not support filesystem.

I need some help fixing this problem ASAP because this is a production system.

dmesg output:
[ 2414.128187] LDISKFS-fs: journal UUID does not match
[ 2415.232953] LustreError: 7358:0:(obd_mount.c:1292:server_kernel_mount()) premount /dev/md2:0x0 ldiskfs failed: -22, ldiskfs2 failed: -19. Is the ldiskfs module available?
[ 2415.232963] LustreError: 7358:0:(obd_mount.c:1618:server_fill_super()) Unable to mount device /dev/md2: -22
[ 2415.232973] LustreError: 7358:0:(obd_mount.c:2050:lustre_fill_super()) Unable to mount (-22)

Whamcloud Community JIRA

[LU-1998] Can't fsck/mount mdadm device with external journal after journal was deleted and re-added. LDISKFS-fs: journal UUID does not match