[LU-5210] sanity-lfsck test 18e failure: Expect file2 size 4, but got

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.6.0
• Type: Bug
• Priority: Minor
• Reporter: James Nunez (Inactive)
• Assignee: nasf (Inactive)
• Resolution: Duplicate
• 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.

• Severity: 3

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 18e fails with the error:

sanity-lfsck test_18e: @@@@@@ FAIL: (8) Expect file2 size 4, but got \n482\n4096\n21504\n21504
\n8834\n8464\n23536\n4096\n8176\n9984\n13344\n9768\n4096\n279 ...

One problem is that the test is trying to get the size of the file

	local cname=$(ls $MOUNT/.lustre/lost+found/MDT0000/*-C-0)

On my system, cname can't be found and the variable $cnameis blank. Thus, when the test does a

ls -il $cname

to get $cname's file size, the file size from all files in the current directory are found and stored in $cur_size.

Issue Links

• is related to: LU-5208 sanity-lfsck test_18c failure: Expect...

Comments

[nasf (Inactive)]

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 LFSCK used new FID for the orphan OST-object's parent, that is not the expected result.

So it is the side effect of failed test_18c for LU-5208.