From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Ilya Dryomov <idryomov@gmail.com>,
linux-xfs@vger.kernel.org, Mark Nelson <mnelson@redhat.com>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH] mkfs.xfs: don't go into multidisk mode if there is only one stripe
Date: Fri, 5 Oct 2018 08:29:52 +1000 [thread overview]
Message-ID: <20181004222952.GV31060@dastard> (raw)
In-Reply-To: <24d229f3-1a75-a65d-5ad3-c8565cb32e76@sandeen.net>
On Thu, Oct 04, 2018 at 01:33:12PM -0500, Eric Sandeen wrote:
> On 10/4/18 12:58 PM, Ilya Dryomov wrote:
> > rbd devices report the following geometry:
> >
> > $ blockdev --getss --getpbsz --getiomin --getioopt /dev/rbd0
> > 512
> > 512
> > 4194304
> > 4194304
dm-thinp does this as well. THis is from the thinp device created
by tests/generic/459:
512
4096
65536
65536
And I've also seen some hardware raid controllers do this, too,
because they only expose the stripe width in their enquiry page
rather than stripe unit and stripe width.
IOWs, this behaviour isn't really specific to Ceph's rbd device, and
it does occur on multi-disk devices that have something layered over
the top (dm-thinp, hardware raid, etc). As such, I don't think
there's a "one size fits all" solution and so someone is going to
have to tweak mkfs settings to have it do the right thing for their
storage subsystem....
Indeed, does Ceph really needs 4MB aligned filesystem IO? What
performance benefit does that give over setting iomin=PAGE_SIZE and
ioopt=0? (i.e mkfs.xfs -d sunit=0,swidth=0 or just mounting with -o
noalign)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-10-05 5:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 17:58 [PATCH] mkfs.xfs: don't go into multidisk mode if there is only one stripe Ilya Dryomov
2018-10-04 18:33 ` Eric Sandeen
2018-10-04 18:56 ` Ilya Dryomov
2018-10-04 22:29 ` Dave Chinner [this message]
2018-10-05 11:27 ` Ilya Dryomov
2018-10-05 13:51 ` Eric Sandeen
2018-10-05 23:27 ` Dave Chinner
2018-10-06 12:17 ` Ilya Dryomov
2018-10-06 23:20 ` Dave Chinner
2018-10-07 0:14 ` Eric Sandeen
2018-11-29 13:53 ` Ric Wheeler
2018-11-29 21:48 ` Dave Chinner
2018-11-29 23:53 ` Ric Wheeler
2018-11-30 2:25 ` Dave Chinner
2018-11-30 18:00 ` block layer API for file system creation - when to use multidisk mode Ric Wheeler
2018-11-30 18:05 ` Mark Nelson
2018-12-01 4:35 ` Dave Chinner
2018-12-01 20:52 ` Ric Wheeler
2018-10-07 13:54 ` [PATCH] mkfs.xfs: don't go into multidisk mode if there is only one stripe Ilya Dryomov
2018-10-10 0:28 ` Dave Chinner
2018-10-05 14:50 ` Mike Snitzer
2018-10-05 14:55 ` Eric Sandeen
2018-10-05 17:21 ` Ilya Dryomov
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=20181004222952.GV31060@dastard \
--to=david@fromorbit.com \
--cc=idryomov@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mnelson@redhat.com \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).