From: Jacek Tomaka <Jacek.Tomaka@poczta.fm>
To: trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
neilb@suse.de
Cc: linux-nfs@vger.kernel.org
Subject: NFS data corruption on congested network
Date: Thu, 22 Feb 2024 15:54:26 +0100 [thread overview]
Message-ID: <ujvntmhlfharduyanjob@tgqn> (raw)
Hello,
I ran into an issue where the NFS file ends up being corrupted on disk. We started noticing it on certain, quite old hardware after upgrading OS from Centos 6 to Rocky 9.2. We do see it on Rocky 9.3 but not on 9.1.
After some investigation we have reasons to believe that the change was introduced by the following commit:
https://github.com/torvalds/linux/commit/6df25e58532be7a4cd6fb15bcd85805947402d91
We write a number of files on a single thread. Each file is up to 4GB. Before closing we call fdatasync. Sometimes the file ends up being corrupted. The corruptions is in a form of a number ( more than 3k pages in one case) of zero filled pages.
When this happens the file cannot be deleted from the client machine which created the file, even when the process which wrote the file completed successfully.
The machines have about 128GB of memory, i think and probably network that leaves to be desired.
My reproducer is currently tied up to our internal software, but i suspect setting the write_congested flag randomly should allow to reproduce the issue.
Regards.
Jacek Tomaka
next reply other threads:[~2024-02-22 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 14:54 Jacek Tomaka [this message]
2024-02-25 23:02 ` NFS data corruption on congested network NeilBrown
2024-02-25 23:19 ` NeilBrown
2024-02-26 8:39 ` Cedric Blancher
2024-02-26 11:58 ` Jacek Tomaka
2024-02-27 22:59 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ujvntmhlfharduyanjob@tgqn \
--to=jacek.tomaka@poczta.fm \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox