From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>, David Disseldorp <ddiss@suse.de>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs
Date: Thu, 17 Aug 2023 13:59:36 +0800 [thread overview]
Message-ID: <5d357e04-106a-a288-6e9a-eb102a768d23@oracle.com> (raw)
In-Reply-To: <20230816145543.ic73cnwhzayuivag@zlang-mailbox>
On 16/8/23 22:55, Zorro Lang wrote:
> On Wed, Aug 16, 2023 at 12:33:30PM +0200, David Disseldorp wrote:
>> The '-f' parameter is fsck.ext# specific, where it's documented to:
>> Force checking even if filesystem is marked clean
>>
>> _repair_test_fs() is only called on _check_test_fs() failure, so
>> dropping the parameter should be possible without changing ext#
>> behaviour.
>> Doing so fixes _repair_test_fs() on exfat, where fsck.exfat doesn't
>> support '-f'.
>>
>> Signed-off-by: David Disseldorp <ddiss@suse.de>
>> ---
>> v2: drop -f from default case instead of splitting out exfat case
>
> This version is good to me.
>
> Reviewed-by: Zorro Lang <zlang@redhat.com>
>
> I remembered you hope to add a btrfs branch to _repair_scratch_fs and
> _repair_test_fs [1]. Is that still in your plan? Anand, could you provide
> more suggestions about that?
>
> [1]
> https://lore.kernel.org/fstests/20230808091454.4skdyjnaxjqa7zyi@zlang-mailbox/
Thanks for bringing to my notice.
The reason fstyp=btrfs has not detected this missing part so far is
that 'fsck -t btrfs' returns 0, along with a message to use 'btrfs
check', which means repair is never invoked for the 'fstyp=btrfs'.
The appropriate repair command to use here is 'btrfs check --repair'.
However, it would be better to address this in a separate patch
as I guess some tests may fail. I will send a patch for it.
Thanks, Anand
>
>>
>> common/rc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/common/rc b/common/rc
>> index 5c4429ed..66d270ac 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -1231,7 +1231,7 @@ _repair_test_fs()
>> ;;
>> *)
>> # Let's hope fsck -y suffices...
>> - fsck -t $FSTYP -fy $TEST_DEV >$tmp.repair 2>&1
>> + fsck -t $FSTYP -y $TEST_DEV >$tmp.repair 2>&1
>> res=$?
>> if test "$res" -lt 4 ; then
>> res=0
>> --
>> 2.35.3
>>
>
parent reply other threads:[~2023-08-17 6:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230816145543.ic73cnwhzayuivag@zlang-mailbox>]
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=5d357e04-106a-a288-6e9a-eb102a768d23@oracle.com \
--to=anand.jain@oracle.com \
--cc=ddiss@suse.de \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--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