From: David Disseldorp <ddiss@suse.de>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, linkinjeon@kernel.org,
sj1557.seo@samsung.com, "Darrick J. Wong" <djwong@kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] common/rc: drop '-f' parameter from fsck.exfat
Date: Tue, 8 Aug 2023 00:34:49 +0200 [thread overview]
Message-ID: <20230808003449.760508f1@echidna.fritz.box> (raw)
In-Reply-To: <20230807174835.moxyuvx4mp47pvky@zlang-mailbox>
Thanks for the feedback, Zorro...
On Tue, 8 Aug 2023 01:48:35 +0800, Zorro Lang wrote:
> On Mon, Aug 07, 2023 at 01:28:50PM +0200, David Disseldorp wrote:
> > fsck.exfat doesn't support the '-f' flag, so add a special case to
> > _repair_test_fs().
>
> I'm wondering why _repair_scratch_fs() doesn't have the '-f', but the
> _repair_test_fs() has it. Looks like the '-f' option was for extN fs
> originally, it's not a fsck common option, but in fsck.ext4.
>
> So I think the '-f' might not be a necessary option. As _repair_scratch_fs
> works without it, can we just remove the '-f' from _repair_test_fs()?
The fsck.ext4 usage states:
-f Force checking even if filesystem is marked clean
As _repair_test_fs() is only called on _check_test_fs() failure, I
suppose '-f' removal should be fine. Still, to avoid any behavioural
changes I could also just add an explicit ext case with '-f'.
There's also a question of what btrfs should do here, as calling the
"fsck.btrfs" no-op script following btrfs check failure likely
doesn't make much sense.
Cheers, David
next prev parent reply other threads:[~2023-08-07 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 11:28 [PATCH] common/rc: drop '-f' parameter from fsck.exfat David Disseldorp
2023-08-07 17:48 ` Zorro Lang
2023-08-07 22:34 ` David Disseldorp [this message]
2023-08-08 9:14 ` Zorro Lang
2023-08-08 2:39 ` Darrick J. Wong
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=20230808003449.760508f1@echidna.fritz.box \
--to=ddiss@suse.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linkinjeon@kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=tytso@mit.edu \
--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