A little help here? One OST fails to mount with the following: LDISKFS-fs: group descriptors corrupted! LustreError: 8364:0:(obd_mount.c:1278:server_kernel_mount()) premount /dev/mpath/lun_13:0x0 ldiskfs failed: -22, ldiskfs2 failed: -19. Is the ldiskfs module available? LustreError: 8364:0:(obd_mount.c:1592:server_fill_super()) Unable to mount device /dev/mpath/lun_13: -22 LustreError: 8364:0:(obd_mount.c:1997:lustre_fill_super()) Unable to mount (-22) LDISKFS-fs error (device dm-13): ldiskfs_check_descriptors: Checksum for group 2560 failed (12546!=45229) I assume running an e2fsck -fy against the OST is the prefered solution, I just want to confirm. ''e2fsck -fn [dev]'' gives: Group descriptor 2560 checksum is invalid. Fix? no [...] Group descriptor 2687 checksum is invalid. Fix? no ---------------- John White High Performance Computing Services (HPCS) (510) 486-7307 One Cyclotron Rd, MS: 50B-3209C Lawrence Berkeley National Lab Berkeley, CA 94720
On 2010-05-19, at 17:37, John White wrote:> A little help here? One OST fails to mount with the following: > > LDISKFS-fs: group descriptors corrupted! > LustreError: 8364:0:(obd_mount.c:1278:server_kernel_mount()) premount /dev/mpath/lun_13:0x0 ldiskfs failed: -22, ldiskfs2 failed: -19. Is the ldiskfs module available? > LustreError: 8364:0:(obd_mount.c:1592:server_fill_super()) Unable to mount device /dev/mpath/lun_13: -22 > LustreError: 8364:0:(obd_mount.c:1997:lustre_fill_super()) Unable to mount (-22) > LDISKFS-fs error (device dm-13): ldiskfs_check_descriptors: Checksum for group 2560 failed (12546!=45229) > > I assume running an e2fsck -fy against the OST is the prefered solution, I just want to confirm.That would be the normal course of action. Actually, "e2fsck -fp" is slightly better than "e2fsck -fy", since it chooses "prudent" answers to the questions, instead of "yes" always, and aborts if there isn''t a safe/obvious choice.> ''e2fsck -fn [dev]'' gives: > Group descriptor 2560 checksum is invalid. Fix? no > [...] > Group descriptor 2687 checksum is invalid. Fix? noBest to save the full "e2fsck -fn" output for future reference. If this is the only problem, then no worries, but the checksums may also be invalid because there is other corruption, and this is only the first sign of trouble Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc.
I just went though something similar. When your fsck completes you may be left with things moved to your lost+found. If that happens, you can mount the file system using -t ldiskfs and run the ll_recover_lost_found_objs against the lost+found directory. -- Andrew -----Original Message----- From: lustre-discuss-bounces at lists.lustre.org [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of Andreas Dilger Sent: Wednesday, May 19, 2010 6:02 PM To: John White Cc: lustre-discuss at lists.lustre.org Subject: Re: [Lustre-discuss] Group descriptors corrupted On 2010-05-19, at 17:37, John White wrote:> A little help here? One OST fails to mount with the following: > > LDISKFS-fs: group descriptors corrupted! > LustreError: 8364:0:(obd_mount.c:1278:server_kernel_mount()) premount /dev/mpath/lun_13:0x0 ldiskfs failed: -22, ldiskfs2 failed: -19. Is the ldiskfs module available? > LustreError: 8364:0:(obd_mount.c:1592:server_fill_super()) Unable to mount device /dev/mpath/lun_13: -22 > LustreError: 8364:0:(obd_mount.c:1997:lustre_fill_super()) Unable to mount (-22) > LDISKFS-fs error (device dm-13): ldiskfs_check_descriptors: Checksum for group 2560 failed (12546!=45229) > > I assume running an e2fsck -fy against the OST is the prefered solution, I just want to confirm.That would be the normal course of action. Actually, "e2fsck -fp" is slightly better than "e2fsck -fy", since it chooses "prudent" answers to the questions, instead of "yes" always, and aborts if there isn''t a safe/obvious choice.> ''e2fsck -fn [dev]'' gives: > Group descriptor 2560 checksum is invalid. Fix? no > [...] > Group descriptor 2687 checksum is invalid. Fix? noBest to save the full "e2fsck -fn" output for future reference. If this is the only problem, then no worries, but the checksums may also be invalid because there is other corruption, and this is only the first sign of trouble Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc. _______________________________________________ Lustre-discuss mailing list Lustre-discuss at lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss