[LU-13233] sanity test 161a fails with 'bad link ea' Created: 10/Feb/20 Updated: 17/Feb/21 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.14.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ppc | ||
| Environment: |
PPC clients |
||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
sanity test_161a fails with 'bad link ea' fails 100% of the time for PPC client testing starting on 27 SEPT 2019. Looking at a recent failure at https://testing.whamcloud.com/test_sets/d3720002-4a27-11ea-b69a-52540065bddc, we see that we are having problems with path2fid/fid2path == sanity test 161a: link ea sanity ================================================================== 01:25:04 (1581125104) lfs path2fid: cannot get fid for '/mnt/lustre/d161a.sanity/f161a.sanity': No data available lfs fid2path: <fsname|rootpath> and <fid>... must be specified Resolve the full path(s) for given FID(s). For a specific hardlink specify link number <linkno>. usage: fid2path [-c] [--link|-l <linkno>] <fsname|root> <fid> ... lfs fid2path: <fsname|rootpath> and <fid>... must be specified Resolve the full path(s) for given FID(s). For a specific hardlink specify link number <linkno>. usage: fid2path [-c] [--link|-l <linkno>] <fsname|root> <fid> ... sanity test_161a: @@@@@@ FAIL: bad link ea Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6121:error() = /usr/lib64/lustre/tests/sanity.sh:14413:test_161a() The portion of test 161a that is failing is 14402 local FID=$($LFS path2fid $DIR/$tdir/$tfile | tr -d '[]') 14403 if [ "$($LFS fid2path $DIR $FID | wc -l)" != "5" ]; then 14404 $LFS fid2path $DIR $FID 14405 error "bad link ea" 14406 fi Logs for more sanity test 161a test failures are at |
| Comments |
| Comment by James Nunez (Inactive) [ 11/Feb/20 ] |
|
Looking at https://testing.whamcloud.com/test_sets/d3720002-4a27-11ea-b69a-52540065bddc, several sanity tests fail with problems with path2fid including 162a, 162c, 226a, 228a, 228b, 228c, 233a, 233b, 238, 247d, 421a, 421b, 421c, 421d and 421f. These failures also started on 27 SEPT 2019. == sanity test 162a: path lookup sanity ============================================================== 01:25:14 (1581125114) lfs path2fid: cannot get fid for '/mnt/lustre/d162a.sanity/d2/f162a.sanity': No data available lfs fid2path: bad FID format '', should be [seq:oid:ver] (e.g. [0x200000400:0x2:0x0]) lfs fid2path: cannot find '': Invalid argument sanity test_162a: @@@@@@ FAIL: path looked up of 'd162a.sanity/d2/f162a.sanity' failed: rc=22 Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6121:error() = /usr/lib64/lustre/tests/sanity.sh:14620:check_path() = /usr/lib64/lustre/tests/sanity.sh:14637:test_162a() == sanity test 233b: checking that OBF of the FS .lustre succeeds ==================================== 02:31:22 (1581129082) lfs path2fid: cannot get fid for '/mnt/lustre/.lustre': No such file or directory stat: cannot stat '/mnt/lustre/.lustre/fid/': No such file or directory sanity test_233b: @@@@@@ FAIL: cannot access /mnt/lustre/.lustre using its FID '' Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6121:error() = /usr/lib64/lustre/tests/sanity.sh:17291:test_233b() == sanity test 238: Verify linkea consistency ======================================================== 02:31:34 (1581129094) lfs path2fid: cannot get fid for '/mnt/lustre/f238.sanity': No data available lfs path2fid: cannot get fid for '/mnt/lustre/f238.sanity.lnk': No data available lfs fid2path: bad FID format '', should be [seq:oid:ver] (e.g. [0x200000400:0x2:0x0]) lfs fid2path: cannot find '': Invalid argument /usr/lib64/lustre/tests/sanity.sh: line 17379: [: f238.sanity: unary operator expected sanity test_238: @@@@@@ FAIL: linkea inconsistent: f238.sanity Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6121:error() = /usr/lib64/lustre/tests/sanity.sh:17379:test_238() |