From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218626] fstest ext4/014 fails when using filesystem quotas
Date: Tue, 26 Mar 2024 15:38:09 +0000 [thread overview]
Message-ID: <bug-218626-13602-xYEOTpypHh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218626-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218626
--- Comment #1 from Luis Henriques (luis.henriques@linux.dev) ---
Created attachment 306044
--> https://bugzilla.kernel.org/attachment.cgi?id=306044&action=edit
Fix lost+found directory
OK, I've a patch that seems to fix the issue.
When mke2fs creates the 'lost+found' directory, it ensures that there are a few
empty blocks in it. However, this test (ext4/014) corrupts the filesystem and
this directory needs to be created again.
The e2fsck program, however, when recreating the lost+found directory, isn't
making sure that there are these empty blocks. These extra blocks will be then
taken into account in the quota calculation, as they were in the initial
(non-corrupted) filesystem. The patch I'm attaching basically copies the loop
that adds the blocks to the empty directory. There are a few I haven't yet
understood -- for example, the '16*1024' magic number is still a mistery.
Any thoughts?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-03-26 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:54 [Bug 218626] New: fstest ext4/014 fails when using filesystem quotas bugzilla-daemon
2024-03-26 15:38 ` bugzilla-daemon [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=bug-218626-13602-xYEOTpypHh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.