Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Zorro Lang <zlang@redhat.com>,
	"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
	xfs <linux-xfs@vger.kernel.org>
Subject: Re: question of xfs/148 and xfs/149
Date: Thu, 19 Sep 2019 18:49:03 +0800	[thread overview]
Message-ID: <638537d9-ce38-7285-c598-8637adbebd8f@cn.fujitsu.com> (raw)
In-Reply-To: <20190918163711.GX2229799@magnolia>



on 2019/09/19 0:37, Darrick J. Wong wrote:
>>   I am finding the reasion. It seems wipefs wipes important information and
>> $DSIZE option(using single agcount or dsize, it also fails ) can not format
>> disk completely. If we use other options, it can pass.
> How does mkfs fail, specifically?
> 
> Also, what's your storage configuration?  And lsblk -D output?

I only guess it from result. Even though, mkfs.xfs $DSIZE 
successfully($? is 0), but UUID mismatch in 030.full, so it may
format the first superblock failed.  This is just my guess.

 From your detailed explanation, I understand why it fails.

Thanks
Yang Xu



      parent reply	other threads:[~2019-09-19 10:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BF2FD5A942B1C4B828DDAF5635768C1041AB0E2@G08CNEXMBPEKD02.g08.fujitsu.local>
2019-09-17 16:39 ` question of xfs/148 and xfs/149 Darrick J. Wong
2019-09-18  2:59   ` Zorro Lang
2019-09-18  3:24     ` Yang Xu
2019-09-18 16:37       ` Darrick J. Wong
2019-09-18 23:10         ` Darrick J. Wong
2019-09-19  5:20           ` Zorro Lang
2019-09-19  6:33             ` Darrick J. Wong
2019-09-19  6:59               ` Zorro Lang
2019-09-19 10:49         ` Yang Xu [this message]

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=638537d9-ce38-7285-c598-8637adbebd8f@cn.fujitsu.com \
    --to=xuyang2018.jy@cn.fujitsu.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@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