== mmp test 9: mount after aborted e2fsck == 01:55:13 (1307609713) Starting mds1: -o user_xattr,acl /dev/sda3 /mnt/mds1 192.168.4.18: error: set_param: writing to file /proc/sys/lnet/debug_mb: Invalid argument debug=0x33f0404 subsystem_debug=0xffb7e3ff debug_mb=10 Started lustre-MDT0000 Starting ost1: /dev/sdc1 /mnt/ost1 192.168.4.128: error: set_param: writing to file /proc/sys/lnet/debug_mb: Invalid argument debug=0x33f0404 subsystem_debug=0xffb7e3ff debug_mb=10 Started lustre-OST0000 Stopping /mnt/mds1 (opts:) Stopping /mnt/ost1 (opts:) Sleep 10 seconds Running e2fsck on the device /dev/sda3 on mds1... 192.168.4.18: e2fsck 1.41.90.wc2 (14-May-2011) Before sleep: Thu Jun 9 01:55:30 PDT 2011 After sleep: Thu Jun 9 01:55:40 PDT 2011 Mounting /dev/sda3 on mds1... Starting mds1: -o user_xattr,acl /dev/sda3 /mnt/mds1 192.168.4.18: mount.lustre: mount /dev/sda3 at /mnt/mds1 failed: Device or resource busy mount -t lustre /dev/sda3 /mnt/mds1 Start of /dev/sda3 on mds1 failed 16 tune2fs 1.41.90.wc2 (14-May-2011) Running e2fsck on the device /dev/sdc1 on ost1... 192.168.4.128: e2fsck 1.41.90.wc2 (14-May-2011) 192.168.4.18: e2fsck: MMP: device currently active while trying to open /dev/sda3 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 16416 Mounting /dev/sdc1 on ost1... Starting ost1: /dev/sdc1 /mnt/ost1 192.168.4.128: mount.lustre: mount /dev/sdc1 at /mnt/ost1 failed: Device or resource busy mount -t lustre /dev/sdc1 /mnt/ost1 Start of /dev/sdc1 on ost1 failed 16 tune2fs 1.41.90.wc2 (14-May-2011) Resetting fail_loc on all nodes...done. 192.168.4.128: e2fsck: MMP: device currently active while trying to open /dev/sdc1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 32768