From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM strategy: Is One VG Safe?
Date: Mon, 20 Dec 2004 12:49:05 -0400 [thread overview]
Message-ID: <41C70281.2070404@ednet.ns.ca> (raw)
In-Reply-To: <a06100527bdebff37d57f@[129.98.90.227]>
Maurice Volaski wrote:
> I plan to start with a hardware RAID (level 5) of one physical volume
> and one volume group. Then create several logical volumes from it and
> grow them each as they are needed pulling space from what's not used in
> the volume group until all the space in the group eventually utilized.
>
> Is it reasonable to believe that such an arrangement is stable enough
> that if anything were to ever go wrong a with an individual logical
> volume that it wouldn't impact the other logical volumes in that same
> volume group or the volume group itself?
We have used the above setup for years (one VG/many LV on top of
hardware RAID 5). It is stable for us.
next prev parent reply other threads:[~2004-12-20 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 4:03 [linux-lvm] LVM strategy: Is One VG Safe? Maurice Volaski
2004-12-20 16:49 ` Patrick Boutilier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-21 0:27 Maurice Volaski
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=41C70281.2070404@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox