FS/XFS testing framework
 help / color / mirror / Atom feed
* [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs
@ 2023-08-16 10:33 David Disseldorp
  2023-08-16 14:55 ` Zorro Lang
  0 siblings, 1 reply; 4+ messages in thread
From: David Disseldorp @ 2023-08-16 10:33 UTC (permalink / raw)
  To: fstests; +Cc: David Disseldorp

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

 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


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs
  2023-08-16 10:33 [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs David Disseldorp
@ 2023-08-16 14:55 ` Zorro Lang
  2023-08-16 19:42   ` David Disseldorp
  2023-08-17  5:59   ` Anand Jain
  0 siblings, 2 replies; 4+ messages in thread
From: Zorro Lang @ 2023-08-16 14:55 UTC (permalink / raw)
  To: David Disseldorp; +Cc: fstests, Anand Jain

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/

> 
>  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
> 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs
  2023-08-16 14:55 ` Zorro Lang
@ 2023-08-16 19:42   ` David Disseldorp
  2023-08-17  5:59   ` Anand Jain
  1 sibling, 0 replies; 4+ messages in thread
From: David Disseldorp @ 2023-08-16 19:42 UTC (permalink / raw)
  To: Zorro Lang; +Cc: fstests, Anand Jain

On Wed, 16 Aug 2023 22:55:43 +0800, 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>

Thanks.

> 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?

Yes, that's still my plan, but I was hoping to get some more input on
whether "btrfs check --repair ..." is sufficient before proposing the
change.

Cheers, David

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs
  2023-08-16 14:55 ` Zorro Lang
  2023-08-16 19:42   ` David Disseldorp
@ 2023-08-17  5:59   ` Anand Jain
  1 sibling, 0 replies; 4+ messages in thread
From: Anand Jain @ 2023-08-17  5:59 UTC (permalink / raw)
  To: Zorro Lang, David Disseldorp; +Cc: fstests, linux-btrfs



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
>>
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-08-17  6:00 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-16 10:33 [PATCH v2] common/rc: drop 'fsck -f' parameter from _repair_test_fs David Disseldorp
2023-08-16 14:55 ` Zorro Lang
2023-08-16 19:42   ` David Disseldorp
2023-08-17  5:59   ` Anand Jain

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox