From: Oliver Schinagl <oliver+list@schinagl.nl>
To: John Stoffel <john@stoffel.org>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Mike Vanhorn <michael.vanhorn@wright.edu>,
Phil Turmel <philip@turmel.org>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Odd --examine output
Date: Mon, 15 Apr 2013 18:06:36 +0200 [thread overview]
Message-ID: <516C258C.7070406@schinagl.nl> (raw)
In-Reply-To: <20844.24431.814932.275104@quad.stoffel.home>
On 15-04-13 22:13, John Stoffel wrote:
>>>>>> "Roy" == Roy Sigurd Karlsbakk <roy@karlsbakk.net> writes:
>>>> NOT a guess. Back up what you can, while you can, and start over. Use
>>>> "fdisk -u" so you can ensure partitions start on multiples of eight
>>>> (8)
>>>> sectors. (Modern fdisk uses 1MB alignment by default. Highly
>>>> recommended.)
>>>>
>>>>
>>> So, if I start the partition at sector 64 (rather than 63), that's
>>> better,
>>> right (since 64 is a multiple of 8)? Or is there more math to do and
>>> I'm still not getting it?
> Roy> I still don't understand why people use partitions for RAID when
> Roy> the whole drive is used anyway. Partitions were invented to
> Roy> partition things up and are of no use if you want to spend the
> Roy> whole drive's space for RAID use (or otherwise).
>
> Because if I take a 2tb disk a I put a partition on there which is a
> bit smaller than the full disk, if I then add a new 2tb (or any other
> size) disk which says it's 2tb, but it's really a bit smaller, then
> I'm not screwed. I've had it happen.
Or if you use them for your OS, and have several raids for /, /usr, /var
etc.
Or you buy 2 or 3 batches of disks, all varying sizes (1TB != 1TB) and
having partitions allows you to at least align them all to the same size.
And its even possible to buy a replacement disk, that's actually larger
but cheaper as prices came down.
A strange use case could be that 1 disk split into 2 partitions could be
a hot-spare for 2 arrays.
When using 1MiB offsets for partitions, I don't think there's any
performance loss at all (due to alignment) nor will it slow down
anything because md is on a partition rather then a disk. Wasting 1 MiB
per disk is really not significant.
And when using raid1/10 it allows you in theory to wipe the superblock
and make the partition point tot he real data; though there's very
little use for that imo.
I personally, don't see why you want to use the entire disk, is there
any advantage?
>
> John
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" 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:[~2013-04-15 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51681FB2.8060803@turmel.org>
2013-04-12 16:47 ` Odd --examine output Vanhorn, Mike
2013-04-12 17:21 ` Phil Turmel
2013-04-15 13:46 ` Vanhorn, Mike
2013-04-15 14:00 ` Phil Turmel
2013-04-15 18:42 ` Roy Sigurd Karlsbakk
2013-04-15 20:13 ` John Stoffel
2013-04-15 16:06 ` Oliver Schinagl [this message]
2013-04-16 8:58 ` Robin Hill
2013-04-18 11:33 ` Roy Sigurd Karlsbakk
2013-04-18 13:03 ` John Stoffel
2013-04-18 14:22 ` Roy Sigurd Karlsbakk
2013-04-18 11:37 ` Roy Sigurd Karlsbakk
2013-04-18 6:32 ` Sam Bingner
2013-04-11 12:47 Vanhorn, Mike
2013-04-11 20:31 ` Vanhorn, Mike
2013-04-11 21:15 ` Phil Turmel
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=516C258C.7070406@schinagl.nl \
--to=oliver+list@schinagl.nl \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=michael.vanhorn@wright.edu \
--cc=philip@turmel.org \
--cc=roy@karlsbakk.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