[LU-6096] sanity test_17m: e2fsck Inode 32775, i_size is 0, should be 4096

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.7.0
• Labels: HB
• Severity: 3
• Assignee: Alex Zhuravlev
• Reporter: Maloo

Description

This issue was created by maloo for Bob Glossman <[e-mail]>

This issue relates to the following test suite run of review-ldiskfs: https://testing.hpdd.intel.com/test_sets/277e606e-976d-11e4-bafa-5254006e85c2.

I note that several other recent similar failures have been marked as LU-3534.
As I'm unsure of the reasoning for that and this one is seen on el7 I've raised it as new.
Somebody more expert may decide it's a dup after looking it over.

The sub-test test_17m failed with the following error:

e2fsck -fnvd /dev/lvm-Role_MDS/P1
e2fsck 1.42.12.wc1 (15-Sep-2014)
shadow-26vm8: check_blocks:2814: increase inode 32775 badness 0 to 1
shadow-26vm8: check_blocks:2814: increase inode 32776 badness 0 to 1
Pass 1: Checking inodes, blocks, and sizes
Inode 32775, i_size is 0, should be 4096.  Fix? no

Inode 32776, i_size is 0, should be 4096.  Fix? no

Please provide additional information about the failure here.

Info required for matching: sanity 17m

Issue Links

• is duplicated by: LU-7094 object UID not being set correctly for non-root user
• is related to: LU-5022 support for 3.10 rhel7 linux kernel

Comments

[Gerrit Updater]

Andreas Dilger ([e-mail]) merged in patch http://review.whamcloud.com/14772/
Subject: LU-6096 osd: mark directory's inode dirty
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 52437f5218fc911cc0b6b9f36e8a143bf54f1024

[Bob Glossman (Inactive)]

In local test on el7 servers the fix works. The problem which was 100% reproducible now doesn't appear even once.

[Alex Zhuravlev]

the patch referenced above should address the issue.

[Alex Zhuravlev]

going to reproduce locally, will take a bit.

[Andreas Dilger]

It looks like the requested sanity test_17m test was run, but none of the added LASSERTs/BUG were hit.

Alex, what is the next step?

[Andreas Dilger]

Patch is http://review.whamcloud.com/14772

[Alex Zhuravlev]

ok, thanks. that's just to try to catch the cause.. not to fix the issue.

[Bob Glossman (Inactive)]

I think there may be a typo in that debug patch. title in commit header refers to 6069, not 6096

[Alex Zhuravlev]

I pushed a debug patch.

[Andreas Dilger]

Alex, can you please take a look at this?

[Bob Glossman (Inactive)]

yes, it still fails. see https://testing.hpdd.intel.com/test_sets/32d9d04a-e38c-11e4-bb64-5254006e85c2