From: Ric Wheeler <rwheeler@redhat.com>
To: Loic Dachary <loic@dachary.org>,
Somnath Roy <Somnath.Roy@sandisk.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph-disk disk partition alignment
Date: Mon, 7 Mar 2016 13:37:37 +0530 [thread overview]
Message-ID: <56DD36C9.9060406@redhat.com> (raw)
In-Reply-To: <56CBF2DB.10602@dachary.org>
On 02/23/2016 11:19 AM, Loic Dachary wrote:
> Here it is http://tracker.ceph.com/issues/14842
>
> On 23/02/2016 12:24, Somnath Roy wrote:
>> eph-deploy is creating data partition from sector 1 ignoring what sgdisk is recommending (256 in my disk). Basically, it should be aligned with physical sector size (reported in /sys/block/<device>/queue/physical_block_size). In my case it is 16K physical and 4K logical...256 is perfectly fine as sgdisk/fdisk internally decides.
>>> Disk performance will be severely impacted because of partitioning this way from ceph-deploy ,
I think that more modern partition tools handle alignment better (and handle the
modern partition types) - sfdisk and parted both are better than fdisk I believe.
For RHEL & Fedora, we try hard to make sure that we use the advertised alignment
when we create a partition and default to an alignment on sector 2048 (1MB) if
it is not set by the device.
Ric
next prev parent reply other threads:[~2016-03-07 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 18:27 ceph-deploy disk partition alignment Somnath Roy
2016-02-23 5:11 ` ceph-disk " Loic Dachary
2016-02-23 5:24 ` Somnath Roy
2016-02-23 5:49 ` Loic Dachary
2016-02-23 7:09 ` Василий Ангапов
2016-02-23 16:52 ` Somnath Roy
2016-03-07 8:07 ` Ric Wheeler [this message]
2016-03-07 8:44 ` Loic Dachary
2016-02-23 12:12 ` ceph-deploy " Alfredo Deza
2016-02-23 16:58 ` Somnath Roy
-- strict thread matches above, loose matches on Subject: below --
2016-02-24 22:01 ceph-disk " Somnath Roy
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=56DD36C9.9060406@redhat.com \
--to=rwheeler@redhat.com \
--cc=Somnath.Roy@sandisk.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.