[LU-12417] conf-sanity test 73 fails with '1st tunefs failed' Created: 10/Jun/19 Updated: 19/Jun/19 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | zfs | ||
| Environment: |
ZFS |
||
| Severity: | 3 |
| Rank (Obsolete): | 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 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: |