[LU-4760] New files written to Lustre clients mounted with 'nolock' option are corrupted.

• Type: Bug
• Resolution: Not a Bug
• Priority: Major
• Affects Version/s: Lustre 2.5.0, Lustre 2.4.2
• Labels: client corruption nolock
• Environment: Rosso, Shadow
• Severity: 2

Epic

client

• Assignee: WC Triage
• Reporter: Omkar Kulkarni (Inactive)

Description

If I mount Lustre clients with the nolock option, any new files that are created seem to be aligned along the 4K boundary, even if the total length may fall before the boundary. This causes the file to contain garbage data trailing EOF.

Please see the attached console output.

Additional information: Not sure if this is relevant, but Lustre clients were mounted directly on the OSS and MDS. I haven't tested with standalone clients.