All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zirong Lang <zlang@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: fstests@vger.kernel.org, eguan@redhat.com
Subject: Re: [PATCH] xfs/020: use -f option for xfs_repair a fs image
Date: Wed, 12 Aug 2015 21:59:46 -0400 (EDT)	[thread overview]
Message-ID: <1052072462.7834190.1439431186908.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <55CB846C.6070205@sandeen.net>



----- 原始邮件 -----
> 发件人: "Eric Sandeen" <sandeen@sandeen.net>
> 收件人: "Zorro Lang" <zlang@redhat.com>, fstests@vger.kernel.org
> 抄送: eguan@redhat.com
> 发送时间: 星期四, 2015年 8 月 13日 上午 1:37:48
> 主题: Re: [PATCH] xfs/020: use -f option for xfs_repair a fs image
> 
> On 8/12/15 12:33 PM, Zorro Lang wrote:
> > This case creates a 60t image file on TEST_DIR. Generally
> > this's no problem. But if the image sector size is smaller
> > than the TEST_DEV sector size, for example we create the
> > image on hard 4k TEST_DEV, the test will fail.
> > 
> > So use -f for xfs_repair will helpful.
> > 
> > Signed-off-by: Zorro Lang <zlang@redhat.com>
> > ---
> >  tests/xfs/020 | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/tests/xfs/020 b/tests/xfs/020
> > index dc305c1..120492d 100755
> > --- a/tests/xfs/020
> > +++ b/tests/xfs/020
> > @@ -55,7 +55,7 @@ fsfile=$TEST_DIR/fsfile.$seq
> >  rm -f $fsfile
> >  
> >  $MKFS_PROG -t xfs -d size=60t,file,name=$fsfile >/dev/null
> > -$XFS_REPAIR_PROG -o ag_stride=32 -t 1 $fsfile >/dev/null 2>&1
> > +$XFS_REPAIR_PROG -f -o ag_stride=32 -t 1 $fsfile >/dev/null 2>&1
> 
> Agreed, but we should audit all tests for this problem, I think.
> 
> FWIW, the latest upstream will do this automatically...
> 
> So for this change, it's fine:
> 
> Reviewed-by: Eric Sandeen <sandeen@redhat.com>

Thanks for review.

> 
> but will you see if other tests should be fixed as well?

I saw you fixed one in commit ddd55d5.

Sure, I will help to find all cases should be fixed.

Maybe add -f automatically for xfs_repair will be better, if it
try to repair an image file?

Or maybe add a function likes mkfs_image_file(), try to find the
sector size of the device contain the image file at first?

Thanks,
Zorro


> 
> -Eric
> 
> 

  reply	other threads:[~2015-08-13  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 17:33 [PATCH] xfs/020: use -f option for xfs_repair a fs image Zorro Lang
2015-08-12 17:37 ` Eric Sandeen
2015-08-13  1:59   ` Zirong Lang [this message]
2015-08-13 15:15   ` Zirong Lang
2015-08-14  9:23     ` Eryu Guan

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=1052072462.7834190.1439431186908.JavaMail.zimbra@redhat.com \
    --to=zlang@redhat.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.