From: Phillip Susi <psusi@cfl.rr.com>
To: Hank Barta <hbarta@gmail.com>
Cc: doug@easyco.com, Roberto Spadim <roberto@spadim.com.br>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: partitions
Date: Fri, 28 Jan 2011 22:46:07 -0500 [thread overview]
Message-ID: <4D438D7F.50007@cfl.rr.com> (raw)
In-Reply-To: <AANLkTikNPmc2AK93k5KTUg4fTM5GoOcr+mtYyv5GN08z@mail.gmail.com>
On 01/28/2011 08:22 PM, Hank Barta wrote:
> One exception: Grub (and perhaps LILO) can boot from a RAID1 partition
> because the individual partition looks like a plain file system. It
> requires v 0.9 metadata which stores the superblock at the end of the
> partition. (Don't ask me how I know! ;) )
Grub2 can boot from raid1, raid0, raid5, it doesn't care ( without a
plain /boot partition ).
> I have used LVM to partition a RAID5. I have no idea if it adds
> significant overhead vs. partitioning the RAID itself if that were
> possible. It was arcane enough for me to not care to do it again. It
> appears to have some powerful capabilities that were not needed by me.
With LVM you can do online resize and moves, and don't run into issues
trying to expand a partition and having to take forever to move an
adjacent one over to make room, or other issues with the 4 primary
partition limit. I find these to be pretty handy.
next prev parent reply other threads:[~2011-01-29 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 21:24 partitions Roberto Spadim
[not found] ` <AANLkTim_16xzRaQJLd1QGd5Dx2LScNX-VUjxrN5uXZng@mail.gmail.com>
2011-01-28 21:45 ` partitions Roberto Spadim
2011-01-28 22:39 ` partitions Doug Dumitru
2011-01-29 1:17 ` partitions Roberto Spadim
2011-01-29 1:22 ` partitions Hank Barta
2011-01-29 3:46 ` Phillip Susi [this message]
2011-01-29 4:17 ` partitions Roberto Spadim
2011-01-29 3:40 ` partitions Phillip Susi
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=4D438D7F.50007@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=doug@easyco.com \
--cc=hbarta@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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).