All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm and md
Date: Fri Mar  7 08:11:02 2003	[thread overview]
Message-ID: <20030307150941.A9634@sistina.com> (raw)
In-Reply-To: <3E6803F3.5060507@exavio.com.cn>; from peter@exavio.com.cn on Fri, Mar 07, 2003 at 10:29:07AM +0800

Peter,
both ways are fine depending on your priorities.

I'ld prefer to group disks together with MD for resilience (i.e RAID1)
and then use those as LVM physical volumes to have the flexibility to allocate
space to logical volumes online.

More convenient this way rather than changing raidtabs which cause interruptions
to your volumes on size changes.

Because a core feature of LVM is to resize logical volumes online, the given
resizing capabilities of filesystems (i.e. reiser, xfs) allow you to
grow the filesystem online as well.


On Fri, Mar 07, 2003 at 10:29:07AM +0800, Peter Yao wrote:
> Should we build lvm volumns on top of soft raid(md) or build md on top 
> of lvm volumns?
> I prefer to build md on top of lvm volumns because lvm can hide the 
> hardware details from md. Just want to know how do you think about this.
> Or any URLs? Thanks.
> -- 
> Peter Yao
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-03-07  8:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  8:01 [linux-lvm] lvm and md Peter Yao
2003-03-07  8:11 ` Heinz J . Mauelshagen [this message]
2003-03-07  9:42 ` Jon Bendtsen
2003-03-09 19:35   ` Peter Yao
2003-03-10  2:05     ` Luca Berra
2003-03-10  3:05     ` William Blunn
2003-03-10  3:29       ` William Blunn
2003-03-10  8:17         ` [linux-lvm] not enough free/allocatable physical extents to extend logical volume Ron Arts
2003-03-10  3:50     ` [linux-lvm] lvm and md Jon Bendtsen
2003-03-09 16:59 ` Stephan Austermuehle
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  8:09 Koch, Steffen
2003-03-10  6:57 Rechenberg, Andrew
2003-03-20  3:36 Rocky Lee
2003-03-20  4:04 ` jon+lvm
2003-03-20 19:45 Rocky Lee
2003-03-21  2:22 ` jon+lvm
2003-03-21  9:54 ` Dale J. Stephenson

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=20030307150941.A9634@sistina.com \
    --to=mauelshagen@sistina.com \
    --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.