From: "Theodore Ts'o" <tytso@mit.edu>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
kdevops@lists.linux.dev, dave@stgolabs.net, jack@suse.cz
Subject: Re: ext4 v6.15-rc2 baseline
Date: Thu, 17 Apr 2025 11:49:07 -0500 [thread overview]
Message-ID: <20250417164907.GA6008@mit.edu> (raw)
In-Reply-To: <20250416233415.GA3779528@mit.edu>
On Wed, Apr 16, 2025 at 06:34:15PM -0500, Theodore Ts'o wrote:
> > - Is this useful information?
>
> Maybe; the question is why are your results so different from my results.
It looks like the problem is that your kernel config doesn't enable
CONFIG_QFMT_V2. As a result, the quota feature is not supported in
the kernel under test. From ext4/033.full file:
mount: /media/scratch: wrong fs type, bad option, bad superblock on /dev/loop5, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mount -o acl,user_xattr -o dioread_nolock,nodelalloc /dev/loop5 /media/scratch failed
And from the ext4/034.dmesg file:
[ 297.969763] EXT4-fs (loop5): The kernel was not built with CONFIG_QUOTA and CONFIG_QFMT_V2
Cheers,
- Ted
next prev parent reply other threads:[~2025-04-17 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 17:56 ext4 v6.15-rc2 baseline Luis Chamberlain
2025-04-16 23:34 ` Theodore Ts'o
2025-04-17 16:38 ` Darrick J. Wong
2025-04-17 18:37 ` Theodore Ts'o
2025-04-17 20:56 ` Luis Chamberlain
2025-04-19 18:22 ` Theodore Ts'o
2025-04-21 15:54 ` Darrick J. Wong
2025-04-21 16:29 ` Theodore Ts'o
2025-04-21 16:47 ` Darrick J. Wong
2025-04-17 16:49 ` Theodore Ts'o [this message]
2025-04-17 20:35 ` Luis Chamberlain
2025-04-18 1:42 ` Luis Chamberlain
2025-04-18 3:56 ` Theodore Ts'o
2025-04-18 19:08 ` Luis Chamberlain
2025-04-19 18:36 ` Theodore Ts'o
2025-04-20 3:39 ` Theodore Ts'o
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=20250417164907.GA6008@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=dave@stgolabs.net \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=linux-ext4@vger.kernel.org \
--cc=mcgrof@kernel.org \
/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