[LU-5967] sanity: e2fsck report error after create files under remote dir Created: 01/Dec/14  Updated: 26/Feb/15  Resolved: 26/Feb/15

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

Type: Bug Priority: Critical
Reporter: Maloo Assignee: Di Wang
Resolution: Duplicate Votes: 0
Labels: HB

Issue Links:
Related
is related to LU-6161 e2fsck failure after sanity.sh 65 Open
Severity: 3
Rank (Obsolete): 16666

 Description   

This issue was created by maloo for Jodi Levi <jlevi@whamcloud.com>

Please provide additional information about the failure here.

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/a592652a-75cd-11e4-b87d-5254006e85c2.



 Comments   
Comment by Jodi Levi (Inactive) [ 01/Dec/14 ]

Di,
Could you please have a look at this one?
Thank you!

Comment by Di Wang [ 31/Dec/14 ]

Hmm, I can not reproduce it with master. And also I checked the maloo, and it seems the most recent failure happened in Nov 26th. So I guess the problem has been fixed somehow in master. I will close it for now. And please re-open it if it happens again.

Comment by James Nunez (Inactive) [ 26/Jan/15 ]

I'm reopening this ticket since I've hit this problem with lustre-master tag 2.6.92 build #2812. Results are at https://testing.hpdd.intel.com/test_sets/37e63f92-9f0d-11e4-91b3-5254006e85c2 .

Comment by Di Wang [ 26/Jan/15 ]

I do not think this failure is related remote directory.

Inode 170393601 ref count is 1, should be 40.  Fix? no

And also I checked the dmesg, it seems the test initially run runtests and sanity.sh 1-65, then restart acceptance test again without reformat the filesystem. So this e2fsck check failure should cause by some tests between 17n and test 65, probably some long existing bug. That said I do not think this is the critical ticket for 2.7.

Comment by Di Wang [ 26/Jan/15 ]

This is different ticket. Not about remote directory. So I will close this one and open a new ticket.

Comment by Di Wang [ 26/Jan/15 ]

reopen the issue for linking to the new ticket.

Comment by Di Wang [ 26/Jan/15 ]

create a new ticket LU-6161

Comment by Di Wang [ 26/Jan/15 ]

reopen it for triage team to decide.

Comment by Andreas Dilger [ 27/Jan/15 ]

It would have been easier to just change the description of this ticket instead of opening a new one, but I don't think it is needed to have two tickets open.

Comment by Andreas Dilger [ 26/Feb/15 ]

Close as a duplicate of LU-6161

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