[LU-4388] fsync on client does not cause OST_SYNCs to be issued

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.6.0
• Affects Version/s: Lustre 2.5.0, Lustre 2.6.0
• Labels: MB
• Severity: 3
• Assignee: Zhenyu Xu
• Reporter: Nathaniel Clark

Description

Issuing an fsync() only causes MDS_SYNC's to be issued.

Testing:
dd with conv=fsync vs. dd with oflag=sync

Comments

[Gerrit Updater]

Bobi Jam ([e-mail]) uploaded a new patch: http://review.whamcloud.com/15390
Subject: LU-4388 test: add sanity test case
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 3112c90215374573c987a800c192300817c62200

[Gerrit Updater]

Bobi Jam ([e-mail]) uploaded a new patch: http://review.whamcloud.com/14840
Subject: LU-4388 llite: issue OST_SYNC for fsync()
Project: fs/lustre-release
Branch: b2_5
Current Patch Set: 1
Commit: 3951a7c7aed155c206043838e4e800c94ac1c692

[Hans Henrik Happe]

Given the severity (data loss, inconsistent databases, etc..), shouldn't it be included in the maintenance release?

[Zhenyu Xu]

2.6.0 has the patches and 2.5.0 does not.

[Hans Henrik Happe]

Should this have been fixed after 2.5.0 or is it only 2.6.0? I see the same problem with b2_5 on zfs (fdatasync okay and slow, fsync not touching the disk). I think it is important that fsync works as expected.

[Jodi Levi (Inactive)]

Patch landed to Master.

[Andreas Dilger]

The patch http://review.whamcloud.com/8626 has not landed yet.

[Jodi Levi (Inactive)]

Patch has landed to Master. Please reopen if more work is needed in this ticket.

[Zhenyu Xu]

patch tracking at http://review.whamcloud.com/8684

[Jinshan Xiong (Inactive)]

I see. So this is a misunderstanding of @datasync parameter. This bug may exist in all series of lustre client implementation. Thanks for explanation.