All of lore.kernel.org
 help / color / mirror / Atom feed
From: "bo" <bo@sosnetwork.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM tool limitation on using whole disk
Date: Tue Apr 16 16:23:02 2002	[thread overview]
Message-ID: <007901c1e58c$f7884690$6501a8c0@bomoon> (raw)
In-Reply-To: Pine.LNX.4.44.0204161951550.28284-100000@pzat.meep.org

I support RAID1 & 5.
On the top of these RAID 1 or 5 MD device I will use LVM for flexibility.
I read the WARNING I mentioned on my previous email from some LVM document
such as

"There is one important "limitation" when using whole disk. The LVM tools
used to setup  LVM will recognize a whole disk as possible device for LVM
ONLY if it has NO partition table! If the disk already has one, even an
empty
one, LVM will refuse to use it."

This was my question, "is this still TRUE or not?"

Thanks,

Bo
----- Original Message -----
From: "James Hawtin" <oolon@ankh.org>
To: <linux-lvm@sistina.com>
Sent: Tuesday, April 16, 2002 12:57 PM
Subject: Re: [linux-lvm] LVM tool limitation on using whole disk


> On Tue, 16 Apr 2002, Dustin Cooper wrote:
>
> > You can make MD devices out of entire disks, but they won't be
> > autodetected by the kernel.  For MD autodetection to work you have to
have
> > partitions of type 0xfd on your disks.
> >
> > If you still want to use whole disks, make sure /etc/raidtab is up to
date
> > and use raidstart before vgscan.
> >
>
> In that case i recon you should use a partition table just for simplity.
> A partition table only wastes one disk block at the end of the day, you
> going to lose much more space with lvm and the raid in rounding. I have to
> admit I aways use a partition table even when a whole disk has been used
> for lvm.
>
> What kind of raid you going to use? Lvm does do striping and
> Concatination on PEs. (forget what "numbers" those are called ;-)
>
> Mirroring or raid 5 your going to have to use the the linux raid to make
> those devices.
>
> James
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>

  reply	other threads:[~2002-04-16 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 10:15 [linux-lvm] kernel: invalidate: busy buffer Stephenson, Dale
2002-04-16 11:01 ` Rene @ Webscorpion.com
2002-04-16 11:36   ` Markus Dobel
2002-04-16 12:32     ` [linux-lvm] LVM tool limitation on using whole disk bo
2002-04-16 13:51       ` James Hawtin
2002-04-16 14:09         ` bo
2002-04-16 14:36           ` Dustin Cooper
2002-04-16 15:00             ` James Hawtin
2002-04-16 16:23               ` bo [this message]
2002-04-16 17:45     ` [linux-lvm] kernel: invalidate: busy buffer Rene @ Webscorpion.com

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='007901c1e58c$f7884690$6501a8c0@bomoon' \
    --to=bo@sosnetwork.net \
    --cc=linux-lvm@sistina.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.