Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.13.0
-
ZFS
-
3
-
9223372036854775807
Description
conf-sanity test_73 fails with '1st tunefs failed' for ZFS testing only. Looking at the client test_log, we see
== conf-sanity test 73: failnode to update from mountdata properly =================================== 02:33:12 (1559788392) CMD: trevis-14vm11 lsmod | grep zfs >&/dev/null || modprobe zfs; zpool list -H lustre-ost1 >/dev/null 2>&1 || zpool import -f -o cachefile=none -o failmode=panic -d /dev/lvm-Role_OSS lustre-ost1 CMD: trevis-14vm11 tunefs.lustre --failnode=1.2.3.4@tcp lustre-ost1/ost1 checking for existing Lustre data: found Read previous values: Target: lustre-OST0000 Index: 0 Lustre FS: lustre Mount type: zfs Flags: 0x2 (OST ) Persistent mount opts: Parameters: mgsnode=10.9.4.170@tcp sys.timeout=20 Permanent disk data: Target: lustre-OST0000 Index: 0 Lustre FS: lustre Mount type: zfs Flags: 0x42 (OST update ) Persistent mount opts: Parameters: mgsnode=10.9.4.170@tcp sys.timeout=20 failover.node=1.2.3.4@tcp conf-sanity test_73: @@@@@@ FAIL: 1st tunefs failed
There’s no error messages in the console logs that indicate a problem happened.
We see conf-sanity test 73 started failing with this error message for some LNET patches
https://testing.whamcloud.com/test_sets/4b1d791a-82a0-11e9-af1f-52540065bddc
https://testing.whamcloud.com/test_sets/58ea580a-82b5-11e9-a028-52540065bddc
We see conf-sanity test 73 start failing with this error for full testing on 2019-05-30 with Lustre version 2.12.53.79. Here are links to failed conf-sanity test 73 logs:
https://testing.whamcloud.com/test_sets/0fc1337c-83cf-11e9-a028-52540065bddc
https://testing.whamcloud.com/test_sets/582c6b9c-86a7-11e9-be83-52540065bddc
https://testing.whamcloud.com/test_sets/10ce3eaa-8897-11e9-be83-52540065bddc
https://testing.whamcloud.com/test_sets/93bc20f4-8b6a-11e9-9bb5-52540065bddc
Attachments
Issue Links
- mentioned in
-
Page No Confluence page found with the given URL.