From: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
To: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org,
"Luis Henriques (SUSE)" <luis.henriques@linux.dev>
Subject: [PATCH 0/2] e2fsck: make sure orphan files are cleaned-up
Date: Tue, 11 Jun 2024 15:27:02 +0100 [thread overview]
Message-ID: <20240611142704.14307-1-luis.henriques@linux.dev> (raw)
Hi!
I'm sending a fix to e2fsck that forces the filesystem checks to happen
when the orphan file is present in the filesystem. This patch resulted from
a bug reported in openSUSE Tumbleweed[1] where e2fsck doesn't clean-up this
file and later the filesystem fails to be mounted read-only (because it
still requires recovery).
I'm also sending a new test to validate this scenario.
[1] https://bugzilla.suse.com/show_bug.cgi?id=1226043
Luis Henriques (SUSE) (2):
e2fsck: don'k skip checks if the orphan file is present in the
filesystem
tests: new test to check that the orphan file is cleaned up
e2fsck/unix.c | 4 ++++
tests/f_clear_orphan_file/expect.1 | 35 +++++++++++++++++++++++++++++
tests/f_clear_orphan_file/expect.2 | 7 ++++++
tests/f_clear_orphan_file/image.gz | Bin 0 -> 12449 bytes
tests/f_clear_orphan_file/name | 1 +
tests/f_clear_orphan_file/script | 2 ++
6 files changed, 49 insertions(+)
create mode 100644 tests/f_clear_orphan_file/expect.1
create mode 100644 tests/f_clear_orphan_file/expect.2
create mode 100644 tests/f_clear_orphan_file/image.gz
create mode 100644 tests/f_clear_orphan_file/name
create mode 100644 tests/f_clear_orphan_file/script
next reply other threads:[~2024-06-11 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 14:27 Luis Henriques (SUSE) [this message]
2024-06-11 14:27 ` [PATCH 1/2] e2fsck: don't skip checks if the orphan file is present in the filesystem Luis Henriques (SUSE)
2024-06-11 14:27 ` [PATCH 2/2] tests: new test to check that the orphan file is cleaned up Luis Henriques (SUSE)
2024-08-21 13:12 ` [PATCH 0/2] e2fsck: make sure orphan files are cleaned-up Luis Henriques
2024-10-19 0:46 ` Eric Sandeen
2024-10-21 9:24 ` Luis Henriques
2024-10-21 21:08 ` Eric Sandeen
2024-10-25 3:53 ` 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=20240611142704.14307-1-luis.henriques@linux.dev \
--to=luis.henriques@linux.dev \
--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