[LU-3553] 2.4.0<->2.3 interop: sanity test_185: FAIL: FID is still valid after close Created: 03/Jul/13 Updated: 03/Sep/13 Resolved: 03/Sep/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | Lustre 2.4.1, Lustre 2.5.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jian Yu | Assignee: | Bob Glossman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Lustre server build: https://build.whamcloud.com/job/lustre-chris/25/ |
||
| Severity: | 3 |
| Rank (Obsolete): | 8946 |
| Description |
|
sanity test 185 failed as follows: == sanity test 185: Volatile file support == 21:34:04 (1372826044) /mnt/lustre/.lustre/fid/[0x200000400:0x6:0x0] has type file OK sanity test_185: @@@@@@ FAIL: FID is still valid after close Dmesg on client node showed that: Lustre: DEBUG MARKER: == sanity test 185: Volatile file support == 21:34:04 (1372826044) LustreError: 43830:0:(dir.c:433:ll_get_dir_page()) read cache page: [0x200000002:0x2:0x0] at 0: rc -1 LustreError: 43830:0:(dir.c:595:ll_dir_read()) error reading dir [0x200000002:0x2:0x0] at 0: rc -1 Lustre: DEBUG MARKER: /usr/sbin/lctl mark sanity test_185: @@@@@@ FAIL: FID is still valid after close Maloo report: https://maloo.whamcloud.com/test_sets/9ed1db56-e3a4-11e2-9137-52540035b04c The sanity test 185 was added by patch http://review.whamcloud.com/4836 which were not on Lustre b2_3 branch. |
| Comments |
| Comment by Bob Glossman (Inactive) [ 03/Jul/13 ] |
|
sanity test 185 is testing a feature that doesn't even exist in 2.3 servers, namely volatile files. Will add a version check to skip the test on old server versions. |
| Comment by Bob Glossman (Inactive) [ 03/Jul/13 ] |
| Comment by Jian Yu [ 15/Aug/13 ] |
|
Patch was cherry-picked to Lustre b2_4 branch. |