[LU-7202] sanity-benchmark: no label for lustre-ost5/ost5 Created: 23/Sep/15 Updated: 18/Dec/15 Resolved: 18/Dec/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | Emoly Liu |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | zfs | ||
| Environment: |
client and server: lustre-master build# 3192 ZFS DKMS |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
This issue was created by maloo for sarah_lw <wei3.liu@intel.com> Please provide additional information about the failure here. This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/827c33ae-6140-11e5-96b6-5254006e85c2. the test hasn't been run due to following error CMD: shadow-40vm4 zfs get -H -o value lustre:svname lustre-ost5/ost5 2>/dev/null no label for lustre-ost5/ost5 |
| Comments |
| Comment by Sarah Liu [ 02/Oct/15 ] |
|
more instance: https://testing.hpdd.intel.com/test_sets/9a10f4ba-6158-11e5-b495-5254006e85c2 |
| Comment by Saurabh Tandan (Inactive) [ 13/Oct/15 ] |
|
Another instance : |
| Comment by Sarah Liu [ 16/Dec/15 ] |
|
the issue blocks the sanity-benchmark suite(6 sub tests) |
| Comment by Peter Jones [ 16/Dec/15 ] |
|
Emoly Could you please look into this issue? Thanks Peter |
| Comment by Emoly Liu [ 17/Dec/15 ] |
|
I will look into it. |
| Comment by Emoly Liu [ 17/Dec/15 ] |
|
Sarah, does this issue only happen on zfs? |
| Comment by Sarah Liu [ 17/Dec/15 ] |
|
Hi Emoly, |
| Comment by Emoly Liu [ 18/Dec/15 ] |
|
By searching recent 4 weeks maloo testing results on zfs, I found before this error happened, sanity-scrub.sh was skipped, 100%. And before skipping, sanity-scrub always reformats ost[1-4], I think that is why "no label for lustre-ost5" was reported later. I just checked sanity-scrub.sh and found this issue was fixed by So, please update the code to include the fix and see if this error still exists. |
| Comment by Peter Jones [ 18/Dec/15 ] |
|
ok great. So let's close this ticket as a duplicate of |