[LU-9741] sanity test 27w failed with “/usr/bin/lfs getstripe -d /mnt/lustre/d27w.sanity failed” Created: 06/Jul/17 Updated: 25/Oct/17 Resolved: 16/Oct/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0 |
| Fix Version/s: | Lustre 2.11.0, Lustre 2.10.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | James Nunez (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pfl, test | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Running the sanity test suite with a composite file layout set on the mount point results in sanity test_27w failing with sanity test_27w: @@@@@@ FAIL: /usr/bin/lfs getstripe -d /mnt/lustre/d27w.sanity failed Test 27w gets stripe information for a directory and assumes that there is only one “stripe_count” entry in the output; 1715 test_27w() { # bug 10997
1716 test_mkdir -p $DIR/$tdir || error "mkdir failed"
1717 $SETSTRIPE -S 65536 $DIR/$tdir/f0 || error "setstripe failed"
1718 [ $($GETSTRIPE -S $DIR/$tdir/f0) -ne 65536 ] &&
1719 error "stripe size $size != 65536" || true
1720 [ $($GETSTRIPE -d $DIR/$tdir | grep -c "stripe_count") -ne 1 ] &&
1721 error "$GETSTRIPE -d $DIR/$tdir failed" || true
1722 }
With PFL, directories can have more than one component. For example, if we use ‘lfs setstripe’ to set the component count on a directory greater than one and get the stripe information with ‘lfs getstripe’, we see there is more than one “stripe_count” entry in the output # lfs setstripe -E 2M -S 1M -c 1 -E -1 -c -1 /lustre/scratch
# lfs getstripe /lustre/scratch/
/lustre/scratch/
lcm_layout_gen: 0
lcm_entry_count: 2
lcme_id: N/A
lcme_flags: 0
lcme_extent.e_start: 0
lcme_extent.e_end: 2097152
stripe_count: 1 stripe_size: 1048576 stripe_offset: -1
lcme_id: N/A
lcme_flags: 0
lcme_extent.e_start: 2097152
lcme_extent.e_end: EOF
stripe_count: -1 stripe_size: 1048576 stripe_offset: -1
# mkdir /lustre/scratch/testdir
# lfs getstripe -d /lustre/scratch/testdir
lcm_layout_gen: 0
lcm_entry_count: 2
lcme_id: N/A
lcme_flags: 0
lcme_extent.e_start: 0
lcme_extent.e_end: 2097152
stripe_count: 1 stripe_size: 1048576 stripe_offset: -1
lcme_id: N/A
lcme_flags: 0
lcme_extent.e_start: 2097152
lcme_extent.e_end: EOF
stripe_count: -1 stripe_size: 1048576 stripe_offset: -1
# lfs getstripe -d /lustre/scratch/testdir | grep -c stripe_count
2
It looks like this test needs to be modified to not assume that there is only one stripe_count entry for directories. Logs for one of these failures is at |
| Comments |
| Comment by Andreas Dilger [ 07/Jul/17 ] |
|
This should be as simple as changing -ne 1 to -eq 0. |
| Comment by James Nunez (Inactive) [ 10/Jul/17 ] |
|
Andreas - From the example in the description, the number of lines with "stripe count" in them in the 'lfs getstripe -d' output for directories with a composite layout is now dynamic; one line with "stripe_count" in it per component. So, you're suggesting that we want to see one or more lines with "stripe count" in the 'lfs getstripe -d' output. That sounds reasonable. Thank you. I'll upload a patch. |
| Comment by Gerrit Updater [ 10/Jul/17 ] |
|
James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/27980 |
| Comment by Gerrit Updater [ 16/Oct/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/27980/ |
| Comment by Peter Jones [ 16/Oct/17 ] |
|
Landed for 2.11 |
| Comment by Gerrit Updater [ 16/Oct/17 ] |
|
Minh Diep (minh.diep@intel.com) uploaded a new patch: https://review.whamcloud.com/29625 |
| Comment by Gerrit Updater [ 25/Oct/17 ] |
|
John L. Hammond (john.hammond@intel.com) merged in patch https://review.whamcloud.com/29625/ |