Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Lustre 2.10.0
-
None
-
trevis-44vm1 thru 8, Failover test,
RHEL7.3/ldiskfs, branch master, v2.9.53.19.gdad9ce4, b3534
-
3
-
9223372036854775807
Description
https://testing.hpdd.intel.com/test_sessions/52027924-0a4d-11e7-b5b2-5254006e85c2
This looks identical to ATM-188:
from test_log:
CMD: trevis-44vm3 mkdir -p /mnt/lustre-mds1; mount -t lustre -o loop /dev/lvm-Role_MDS/P1 /mnt/lustre-mds1 trevis-44vm3: mount: /dev/lvm-Role_MDS/P1: failed to setup loop device: No such file or directory
However, after looking more closely at the "failover to" MDS (vm3), it appears that it wasn't ready to takeover for the "failover from" MDS (vm7):
last line in vm3's dmesg:
Key type id_legacy registered
dmesg lines from a healthy server:
Key type id_legacy registered device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com EXT4-fs (dm-9): mounting ext3 file system using the ext4 subsystem EXT4-fs (dm-9): recovery complete EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: (null
Followed by numerous "Lustre:" messages.