From: paddy@panici.net
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] partition table needed for lvm ?
Date: Tue, 6 Mar 2007 12:23:28 +0000 [thread overview]
Message-ID: <20070306122328.GC19733@homer.panici.net> (raw)
In-Reply-To: <20070303114507.GD12744@percy.comedia.it>
On Sat, Mar 03, 2007 at 12:45:08PM +0100, Luca Berra wrote:
> On Fri, Mar 02, 2007 at 04:58:37PM +0000, paddy@panici.net wrote:
> >On Fri, Mar 02, 2007 at 03:01:53PM +0100, Luca Berra wrote:
> >>On Thu, Mar 01, 2007 at 11:19:07PM +0000, Alasdair G Kergon wrote:
> >>>On Thu, Mar 01, 2007 at 05:14:25PM -0500, Chris Hunter wrote:
> >>>>Do I reallly need to make partition tables on all my disks to use lvm2 ?
> >>>
> >>>Other packages such as the installer like to have them.
> >>
> >>what about the fact that on many storage creating an ms-dos compatible
> >>partition usually results in screwing io alignment?
> >
> >interesting.
> >
> >Although it comes as no surprise that the CHS boundaries are not aligned
> >with the hardware anymore (like they were back in the days of say MFM),
> >I thought that systems that attempted to use this level of information
> >about a disk were fairly rare these days ?
> The problem comes from smart storage system which like to do IO with
> big block sizes (usually 32K to 64K) from the beginning of the LUN that
> is presented to the OS.
ah! ok :-)
as you say, this has tended to be less of an issue with boot disks.
> My preference would still be for not having msdos partitions on any drive
> at all
The question in my mind these days, is "what kinds of failure modes
can/will it exhibit?".
The secret to "optimising failure" seems to be to keep things as simple as
possible. I think it will depend on what you're doing and exactly how
you are doing it whether one is simpler than the other, but I'd be
especially wary of an approach to the problem that neglects this
question. If nothing else, you get some different options for ways to
shoot yourself in the foot ;-)
Having said that, as you can tell from my previous mail, I have a real
soft spot for the idea of ditching dos partitions and using LVM instead.
> and, since lvm2 does not touch the first 512 bytes of a PV, fitting a
> grub boot block in there is not going to be that difficult.
I didn't realise that had gotten done in the end.
Can't tell you how happy it makes me :-)
Think I'll go and reformat a disk to celebrate! :-)
Don't suppose anyone put in support to stop things getting moved
about by accident that shouldn't ?
Regards,
Paddy
prev parent reply other threads:[~2007-03-06 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 22:14 [linux-lvm] partition table needed for lvm ? Chris Hunter
2007-03-01 23:19 ` Alasdair G Kergon
2007-03-02 11:04 ` paddy
2007-03-02 14:01 ` Luca Berra
2007-03-02 16:58 ` paddy
2007-03-03 11:45 ` Luca Berra
2007-03-06 12:23 ` paddy [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=20070306122328.GC19733@homer.panici.net \
--to=paddy@panici.net \
--cc=linux-lvm@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 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.