From: Krister Johansen <kjlx@templeofstupid.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Krister Johansen <kjlx@templeofstupid.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: [e2fsprogs PATCH v2] resize2fs: use directio when reading superblock
Date: Mon, 18 Sep 2023 14:36:43 -0700 [thread overview]
Message-ID: <20230918213643.GA1945@templeofstupid.com> (raw)
In-Reply-To: <729CDEF6-F6B3-4290-8120-F73C990B0D9F@dilger.ca>
Hi Andreas,
On Mon, Sep 18, 2023 at 03:20:01PM -0600, Andreas Dilger wrote:
> On Sep 11, 2023, at 12:39 PM, Krister Johansen <kjlx@templeofstupid.com> wrote:
> >
> > Invocations of resize2fs intermittently report failure due to superblock
> > checksum mismatches in this author's environment. This might happen a few
> > times a week. The following script can make this happen within minutes.
> > (It assumes /dev/nvme1n1 is available and not in use by anything else).
>
> Krister,
> thanks for submitting the patch. This particular issue was already fixed
> in commit v1.46.6-16-g43a498e93888, apparently based on your previous report:
>
> commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
> Author: Theodore Ts'o <tytso@mit.edu>
> AuthorDate: Thu Jun 15 00:17:01 2023 -0400
> Commit: Theodore Ts'o <tytso@mit.edu>
> CommitDate: Thu Jun 15 00:17:01 2023 -0400
>
> resize2fs: use Direct I/O when reading the superblock for online resizes
>
> If the file system is mounted, the superblock can be changing while
> resize2fs is trying to read the superblock, resulting in checksum
> failures. One way of avoiding this problem is read the superblock
> using Direct I/O, since the kernel makes sure that what gets written
> to disk is self-consistent.
>
> Suggested-by: Krister Johansen <kjlx@templeofstupid.com>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>
> So it is landed on the e2fsprogs maint branch, but there has not been a
> maintenance release since the patch was landed.
Thanks for the response. My apologies for resubmitting this. I had
thought that I checked the git trees before sending this out, but I
must've looked at the wrong one. Sorry about that.
Thanks to Ted for applying his reworked patch, it's much appreciated.
-K
prev parent reply other threads:[~2023-09-18 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 18:39 [e2fsprogs PATCH v2] resize2fs: use directio when reading superblock Krister Johansen
2023-09-18 21:20 ` Andreas Dilger
2023-09-18 21:36 ` Krister Johansen [this message]
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=20230918213643.GA1945@templeofstupid.com \
--to=kjlx@templeofstupid.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).