[LU-5765] sanity test_123a test_123b: rm: no such file or directory

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Affects Version/s: Lustre 2.7.0
• Labels: HB zfs
• Severity: 3
• Assignee: Isaac Huang (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for Andreas Dilger <[e-mail]>

In sanity.sh test_123a and test_123b a large number of errors are being reported when "rm -r" is running:

rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity2': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity5': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity8': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity11': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity12': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity16': No such file or directory
rm: cannot remove `/mnt/lustre/d123a.sanity/f123a.sanity18': No such file or directory

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/186592e2-5577-11e4-8542-5254006e85c2.

Info required for matching: sanity 123a
Info required for matching: sanity 123b

Issue Links

• duplicates: LU-3573 lustre-rsync-test test_8: @@@@@@ FAIL: Failure in replication; differences found.
• is related to: LU-6101 sanity test_24A: Can not delete directories

Comments

[Andreas Dilger]

Haven't seen this again for the past 4 weeks.

Closing it again. Maybe LU-6101 will fix the final trigger.

[Andreas Dilger]

This might also be related to LU-6101, which also has a patch.

[Andreas Dilger]

Saw this again on a recent patch run:
https://testing.hpdd.intel.com/test_sets/e55f7412-881b-11e4-aa28-5254006e85c2
https://testing.hpdd.intel.com/test_sets/c69c83ca-87f9-11e4-a70f-5254006e85c2

[Andreas Dilger]

Is it possible that this problem is the same as LU-3573 and was fixed by http://review.whamcloud.com/12904 ?

The most recent failure https://testing.hpdd.intel.com/test_sets/97ea0fd0-84f6-11e4-a60f-5254006e85c2 was on a patch based on a tree that doesn't contain the LU-3573 fix.

Before that, the most recent test failure was https://testing.hpdd.intel.com/test_sets/863b9434-fcb2-11e2-9222-52540035b04c on 2014-08-03.