From: "Darrick J. Wong" <djwong@kernel.org>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, fdmanana@suse.com,
ritesh.list@gmail.com, naohiro.aota@wdc.com, wqu@suse.com,
Disha Goel <disgoel@linux.ibm.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 4/6] generic/765: Ignore mkfs warning
Date: Mon, 13 Apr 2026 09:21:20 -0700 [thread overview]
Message-ID: <20260413162120.GV6212@frogsfrogsfrogs> (raw)
In-Reply-To: <adyxi7156VAbL-G1@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
On Mon, Apr 13, 2026 at 02:34:11PM +0530, Ojaswin Mujoo wrote:
> On Sun, Apr 12, 2026 at 10:38:18PM +0530, Ojaswin Mujoo wrote:
> > On Fri, Apr 10, 2026 at 09:54:35AM -0700, Darrick J. Wong wrote:
> > > On Fri, Apr 10, 2026 at 12:06:04PM +0530, Ojaswin Mujoo wrote:
> > > > This test validates atomic writes for all possible block sizes. In ext4, for
> > > > smaller block sizes with configurations like:
> > > >
> > > > export MKFS_OPTIONS="-O bigalloc,quota -b 65536 -C 131072"
> > > >
> > > > The output can get corrupted with warnings like below because clustersize
> > > > more than 16xbs is experimental:
> > > >
> > > > + 16 times the block size is considered experimental
> > > >
> > > > Hence pipe these to seqres.full to avoid false negatives.
> > > >
> > > > Reported-by: Disha Goel <disgoel@linux.ibm.com>
> > > > Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
> > >
> > > Seems fine, though I think I'd rather mke2fs get patched to fix this.
> > >
> > > I'd let the maintainer decide if he wants this, but ... I'm not sure if
> > > he's actually going to receive this message. :/
> >
> > Hi Darrick, yes I'm preparing a quick patch for this. We might still
> > need this so people on older distro who wont have the e2fsprogs fix dont
> > see the failure.
>
> Hi Darrick,
>
> Looking at it again, I am just wondering if its really an issue that
> mke2fs is printing this warning to stderr. Isn't stderr the right place
> for errors and warning (even non critical ones)?
>
> Futher, mke2fs has multiple instances where we print warnings to stderr,
> should we go and fix all of them as well?
"stderr" meaning "standard error", I'd say that errors are anything that
prohibits the format from completing, and only errors should go there.
We ought to kick this to the ext4 list though...
--D
> Regards,
> ojaswin
>
> >
> > Regards,
> > ojaswin
> >
> > >
> > > --D
> > >
> > > > ---
> > > > tests/generic/765 | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/tests/generic/765 b/tests/generic/765
> > > > index 09be53db..b7cc70f1 100755
> > > > --- a/tests/generic/765
> > > > +++ b/tests/generic/765
> > > > @@ -64,7 +64,8 @@ test_atomic_writes()
> > > > local bsize=$1
> > > >
> > > > get_mkfs_opts $bsize
> > > > - _scratch_mkfs $mkfs_opts >> $seqres.full
> > > > + _scratch_mkfs $mkfs_opts &>> $seqres.full || \
> > > > + echo "mkfs $mkfs_opts failed"
> > > > _scratch_mount
> > > >
> > > > test "$FSTYP" = "xfs" && _xfs_force_bdev data $SCRATCH_MNT
> > > > --
> > > > 2.53.0
> > > >
> > > >
>
next parent reply other threads:[~2026-04-13 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1775802601.git.ojaswin@linux.ibm.com>
[not found] ` <afee4fedcc9b3685df0e05800d82b88d27f977f8.1775802601.git.ojaswin@linux.ibm.com>
[not found] ` <20260410165435.GU6212@frogsfrogsfrogs>
[not found] ` <advRgjl1tG4PMc6V@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
[not found] ` <adyxi7156VAbL-G1@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
2026-04-13 16:21 ` Darrick J. Wong [this message]
2026-04-13 20:42 ` [PATCH 4/6] generic/765: Ignore mkfs warning Theodore Tso
2026-04-13 23:28 ` Darrick J. Wong
2026-04-15 18:52 ` Ojaswin Mujoo
2026-04-16 15:55 ` Zorro Lang
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=20260413162120.GV6212@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=disgoel@linux.ibm.com \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=wqu@suse.com \
--cc=zlang@redhat.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