[LU-3056] conf-sanity test_66 - replace nids failed

• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Major
• Affects Version/s: Lustre 2.4.0
• Labels: revzfs
• Severity: 3
• Assignee: Keith Mannthey (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for Nathaniel Clark <[e-mail]>

This issue relates to the following test suite runs:
https://maloo.whamcloud.com/test_sets/95fcddea-97b0-11e2-a652-52540035b04c
https://maloo.whamcloud.com/test_sets/810da798-9760-11e2-9ec7-52540035b04c

The sub-test test_66 failed with the following error:

replace nids failed

Info required for matching: conf-sanity 66

All subsequent ZFS test suites (recovery-small, etc) fail with the following error:

Starting mds1: -o user_xattr,acl  lustre-mdt1/mdt1 /mnt/mds1
CMD: wtm-16vm3 mkdir -p /mnt/mds1; mount -t lustre -o user_xattr,acl  		                   lustre-mdt1/mdt1 /mnt/mds1
wtm-16vm3: mount.lustre: according to /etc/mtab lustre-mdt1/mdt1 is already mounted on /mnt/mds1

Issue Links

• is related to: LU-3793 conf-sanity, subtest test_66 fails due to previous state
• is related to: LU-5137 Test failure conf-sanity test_66: replace nids failed
• is related to: LU-11990 conf-sanity test_66: replace nids fail alone MGS

Comments

[Keith Mannthey (Inactive)]

We no longer see this issue. Please reopen if this starts to trigger again. There is on sense landing a debug patch for a problem that does not happen.

[Keith Mannthey (Inactive)]

Still no sign of the "replace nids failed" errors.

[Keith Mannthey (Inactive)]

Quick update:

conf_sanity test_66 has not failed in a few weeks. The "replace nids failed" error really dropped off after 2013-04-29. Perhaps some code path has changed.

[Keith Mannthey (Inactive)]

http://review.whamcloud.com/5940 has been resubmitted for testing in the effort to land it after the 2.4 split. We still see the issue on Master a few times a week and it will be good to know more about out what is causing the issue.

[Andreas Dilger]

I definitely don't think this needs to be a 2.4.0 blocker, since replace_nids is a very rarely used code path. The only potential reason for increased priority might be the frequency to other patches failing due to this bug, but I don't see very many failures due to this specific bug (several other conf-sanity failures are increasing the test failure rates).