Date: Fri, 14 Nov 2003 11:16:47 +0100
From: Lars Marowsky-Bree <lmb@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>, Daniel Gryniewicz <dang@fprintf.net>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [RFCI] How best to partition MD/raid devices in 2.6
Message-ID: <20031114101647.GJ32211@marowsky-bree.de>
References: <16308.18387.142415.469027@notabene.cse.unsw.edu.au> <1068787304.4157.8.camel@localhost> <16308.26754.867801.131463@notabene.cse.unsw.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <16308.26754.867801.131463@notabene.cse.unsw.edu.au>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1059
Lines: 28

On 2003-11-14T16:30:42,
   Neil Brown <neilb@cse.unsw.edu.au> said:

> There are issues with the raid superblock but assuming they can be
> solved, I want partitioning to work easily.
> 
> Can LVM work happily with 'legacy' partitioning information?

I'd really suggest to run DM (either LVM2 or EVMS2) on top of md
instead. It's much more flexible; I don't see any benefit in 'old style'
partition information, which has all sorts of problems - ie,
non-transactional updates (_why_ were you running raid again? ;), static
as they can't be modified during runtime etc.


Sincerely,
    Lars Marowsky-Br?e <lmb@suse.de>

-- 
High Availability & Clustering	      \ ever tried. ever failed. no matter.
SUSE Labs			      | try again. fail again. fail better.
Research & Development, SUSE LINUX AG \ 	-- Samuel Beckett

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/