public inbox for fstests@vger.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: Thu, 13 Aug 2015 11:15:00 -0400 (EDT)	[thread overview]
Message-ID: <109535836.8116036.1439478900232.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>
> 
> but will you see if other tests should be fixed as well?

Hi Eric,

I have checked all xfstests cases about xfs_repair, only xfs/020 and
xfs/032 try to repair a file image.

This patch is about xfs/020. 

But for xfs/032, I think there is no big problem in it. Because always
copy device to a file, if the device's sector size is 4k, the file
image will follow it. Except the TEST_DEV sector size not equal to
SCRATCH_DEV sector size. But yes, add -f will be safe.

Do you need I re-send a patch to add -f in xfs/020 and xfs/032 both?

Or you have another idea to fix this problem, likes add a new function?

Thanks,
Zorro Lang

> 
> -Eric
> 
> 

  parent reply	other threads:[~2015-08-13 15:15 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
2015-08-13 15:15   ` Zirong Lang [this message]
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=109535836.8116036.1439478900232.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox