FS/XFS testing framework
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: <fstests@vger.kernel.org>
Subject: Re: [PATCH 1/2] common: Provide blocksize and ecclength to udf fsck
Date: Fri, 20 Jan 2023 15:41:23 +0100	[thread overview]
Message-ID: <20230120154123.7f59e1cc@echidna.fritz.box> (raw)
In-Reply-To: <20230119105410.9236-1-jack@suse.cz>

Hi Jan,

On Thu, 19 Jan 2023 11:54:02 +0100, Jan Kara wrote:

> udf_test program used for verifying filesystem is not able to determine
> filesystem blocksize. Provide it in the options together with disabling
> ecclength as it is not used on harddrives.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
>  common/rc | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/common/rc b/common/rc
> index 8060c03b7d18..de94e5a4cde4 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -3075,9 +3075,13 @@ _check_udf_filesystem()
>      fi
>  
>      local device=$1
> -    local opt_arg=""
> +    local blksz=`echo $MKFS_OPTIONS | sed -rn 's/.*-b ?+([0-9]+).*/\1/p'`

It looks as though mkudffs also accepts --blocksize= for this, so it
should also be handled here, IIUC.

Looks fine otherwise.

> +    if [ -z "$blksz" ]; then
> +	blksz=512
> +    fi
> +    local opt_arg="-ecclength 1 -blocksize $blksz"
>      if [ $# -eq 2 ]; then
> -	opt_arg="-lastvalidblock $(( $2 - 1 ))"
> +	opt_arg+=" -lastvalidblock $(( $2 - 1 ))"
>      fi
>  
>      rm -f $seqres.checkfs


  reply	other threads:[~2023-01-20 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:54 [PATCH 0/2] fstests: Fix checking of UDF filesystems Jan Kara
2023-01-19 10:54 ` [PATCH 1/2] common: Provide blocksize and ecclength to udf fsck Jan Kara
2023-01-20 14:41   ` David Disseldorp [this message]
2023-01-20 15:45     ` Jan Kara
2023-01-20 19:08       ` Zorro Lang
2023-01-20 19:22         ` Jan Kara
2023-01-19 10:54 ` [PATCH 2/2] common: Unmount udf filesystem prior checking Jan Kara
2023-01-20 14:42   ` David Disseldorp

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=20230120154123.7f59e1cc@echidna.fritz.box \
    --to=ddiss@suse.de \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    /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