linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>, Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: question about mkfs.xfs
Date: Fri, 20 Apr 2018 23:43:51 -0500	[thread overview]
Message-ID: <855f13dc-7cb7-b211-94e6-65f600c99ddd@redhat.com> (raw)
In-Reply-To: <b663f0ab-ab78-961f-7e24-a9794eb07d98@sandeen.net>

On 4/20/18 11:34 PM, Eric Sandeen wrote:
> 
> 
> On 4/20/18 10:22 PM, Xiao Yang wrote:
>> Hi Eric,
>>
>> Before commit 16adcb8 in xfsprogs-dev, only "sunit=0,swidth=0" is vaild
>> and will convert
>> into the default stripe config as expected.
> 
> It behaved the same as the default, because it looked the same as
> "not set" to all the conditionals in mkfs.
> 
>> After this commit, both
>> "sunit=0,swidth=0"
>> and "sunit=0,swidth=64" will be forced to convert into the default
>> stripe config.
> 
> 0,0 should be allowed, to force mkfs to ignore any stripe geometry
> reported by the device.
> 
>> If either of sunit and swidth is not 0, should we do a forced conversion?
>> I am not sure if we should reject the combination(e.g. sunit=0,swidth=64).
> 
> I am not sure what you mean by "forced conversion" - can you give specific
> examples?
> 
> However, a stripe unit of 0 with a non-zero stripe width should probably
> also be rejected, because it has no meaning.  I think it was rejected
> before, and my commit accidentally allowed it again.
> 
> It probably needs another test added back in, to check for "both options
> were specified, but (only) one was zero."

Maybe like this:

mkfs.xfs: if either sunit or swidth is nonzero, the other must be as well

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
index 78d0ce5..b356d4d 100644
--- a/mkfs/xfs_mkfs.c
+++ b/mkfs/xfs_mkfs.c
@@ -2271,7 +2271,8 @@ _("data stripe width (%lld) is too large of a multiple of the data stripe unit (
 		dswidth = big_dswidth;
 	}
 
-	if (dsunit && (!dswidth || (dswidth % dsunit != 0))) {
+	if ((dsunit && !dswidth) || (!dsunit && dswidth) ||
+           (dsunit && (dswidth % dsunit != 0))) {
 		fprintf(stderr,
 _("data stripe width (%d) must be a multiple of the data stripe unit (%d)\n"),
 			dswidth, dsunit);


which yields:

# mkfs.xfs -f -dsunit=0,swidth=64,file,name=fsfile,size=1g
data stripe width (64) must be a multiple of the data stripe unit (0)

# mkfs.xfs -f -dsunit=64,swidth=0,file,name=fsfile,size=1g
data stripe width (0) must be a multiple of the data stripe unit (64)

# mkfs.xfs -f -dsunit=64,swidth=7,file,name=fsfile,size=1g
data stripe width (7) must be a multiple of the data stripe unit (64)

# mkfs.xfs -f -dsunit=0,swidth=0,file,name=fsfile,size=1g
<success>

-Eric

  reply	other threads:[~2018-04-21  4:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  3:22 question about mkfs.xfs Xiao Yang
2018-04-21  4:34 ` Eric Sandeen
2018-04-21  4:43   ` Eric Sandeen [this message]
2018-04-21  5:31     ` 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=855f13dc-7cb7-b211-94e6-65f600c99ddd@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=yangx.jy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).