[LU-5211] sanity-lfsck test 19a failure: Read should be denied! Created: 17/Jun/14  Updated: 30/Jul/14  Resolved: 30/Jul/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: James Nunez (Inactive) Assignee: nasf (Inactive)
Resolution: Duplicate Votes: 0
Labels: lfsck
Environment:

Lustre 2.5.60 on the OpenSFS cluster, CentOS 6.5 with one server (mds01) with a MGS and MDS with two MDTs, another server (mds02) with MDS and two MDTs, four OSSs with two OSTs each and four clients.


Issue Links:
Related
is related to LU-5208 sanity-lfsck test_18c failure: Expect... Resolved
Severity: 3
Rank (Obsolete): 14541

 Description   

Running sanity-lfsck with the stated environment, tests 18c, 18d, 18e, and 19a fail and test 19b hangs. Test results are at https://maloo.whamcloud.com/test_sessions/5ad54b54-f5a5-11e3-b29e-52540035b04c .

sanity-lfsck test 19a fails with the error:

sanity-lfsck test_19a: @@@@@@ FAIL: (3) Read should be denied!


 Comments   
Comment by nasf (Inactive) [ 30/Jul/14 ]

Similar as LU-5209, the former failed test_18c left some dirty environment, and caused the test files had non-initialised PFID xattr, as to the subsequent ofd_verify_ff() will skip the PFID verification for IO RPC from client, that is not the expected result.
So it is the side effect of failed test_18c for LU-5208.

Generated at Sat Feb 10 01:49:29 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.