From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Eryu Guan <eguan@redhat.com>
Cc: darrick.wong@oracle.com, fstests@vger.kernel.org, zlang@redhat.com
Subject: Re: [PATCH v2] xfs/098: fix xfs_repair on newer xfsprogs
Date: Fri, 26 Aug 2016 13:44:06 +0800 [thread overview]
Message-ID: <57BFD726.6080105@cn.fujitsu.com> (raw)
In-Reply-To: <20160826044225.GY27776@eguan.usersys.redhat.com>
On 2016/08/26 12:42, Eryu Guan wrote:
> On Fri, Aug 26, 2016 at 11:36:52AM +0800, Xiao Yang wrote:
>> Make sure xfs_repair can't clear the log by default when it is corrupted.
>> xfs_repair always and only clear the log when the -L parameter is specified.
>> This has updated by:
>> Commit f2053bc ("xfs_repair: don't clear the log by default")
> Can you please put more details in commit log? e.g. what's the problem
> you want to fix, what's the symptom, etc. I had a hard time
> understanding the problems without running the test.
>
Hi Eryu
xfs_repair without -L option succeeded to repair filesystem at xfs/098
if log is corrupted. However,
this feature has been changed by following patch since
xfsprogs-dev(4.3.0), we have to use -L option to
repair filesystem if log is corrupted.
Commit f2053bc ("xfs_repair: don't clear the log by default")
xfs/098 will fail to repair filesystem if log is corrupted since
xfsprogs-dev(4.3.0), so fix it.
Thanks
Xiao Yang.
>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
>> ---
>> common/rc | 4 ++--
>> tests/xfs/098 | 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/common/rc b/common/rc
>> index 3fb0600..c693a31 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -1143,9 +1143,9 @@ _repair_scratch_fs()
>> xfs)
>> _scratch_xfs_repair "$@" 2>&1
>> res=$?
>> - if [ "$res" -eq 2 ]; then
>> + if [ "$res" -ne 0 ]; then
>> echo "xfs_repair returns $res; replay log?"
>> - _scratch_mount
>> + _scratch_mount 2>&1
>> res=$?
>> if [ "$res" -gt 0 ]; then
>> echo "mount returns $res; zap log?"
>> diff --git a/tests/xfs/098 b/tests/xfs/098
>> index d91d617..eb33bb1 100755
>> --- a/tests/xfs/098
>> +++ b/tests/xfs/098
>> @@ -93,7 +93,7 @@ echo "+ mount image"
>> _scratch_mount 2>/dev/null&& _fail "mount should not succeed"
>>
>> echo "+ repair fs"
>> -_scratch_xfs_repair>> $seqres.full 2>&1
>> +_repair_scratch_fs>> $seqres.full
> The above two redirection updates seem not necessary to me, mount
> failure message got redirected to $seqres.full in both cases. Any reason
> doing so?
>
> Thanks,
> Eryu
>
Hi Eryu
if xfs_repair without -L option can succeed to repair filesystem, the
second mount will skip.
Thanks
Xiao Yang.
>>
>> echo "+ mount image (2)"
>> _scratch_mount
>> --
>> 1.8.3.1
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fstests" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
next prev parent reply other threads:[~2016-08-26 5:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 9:22 [PATCH] xfs/098: fix xfs_repair on newer xfsprogs Xiao Yang
2016-08-25 12:09 ` Zorro Lang
2016-08-25 15:40 ` Darrick J. Wong
2016-08-25 16:32 ` Zorro Lang
2016-08-26 3:32 ` Xiao Yang
2016-08-26 16:18 ` Darrick J. Wong
2016-08-26 3:36 ` [PATCH v2] " Xiao Yang
2016-08-26 4:42 ` Eryu Guan
2016-08-26 5:44 ` Xiao Yang [this message]
2016-08-26 4:48 ` Zorro Lang
2016-08-26 6:10 ` Xiao Yang
2016-08-26 9:05 ` Zorro Lang
[not found] ` <57D28101.6000902@cn.fujitsu.com>
2016-09-09 12:28 ` Zorro Lang
2016-09-12 1:07 ` Xiao Yang
2016-09-12 5:13 ` [PATCH v3] " Xiao Yang
2016-09-12 12:59 ` Eric Sandeen
2016-09-13 6:12 ` Xiao Yang
2016-09-13 7:08 ` Zorro Lang
2016-09-14 1:43 ` Xiao Yang
2016-09-14 2:52 ` [PATCH v4] " Xiao Yang
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=57BFD726.6080105@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@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