Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932452AbWAWKkV (ORCPT ); Mon, 23 Jan 2006 05:40:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932450AbWAWKkU (ORCPT ); Mon, 23 Jan 2006 05:40:20 -0500 Received: from mx1.redhat.com ([66.187.233.31]:45758 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932448AbWAWKkT (ORCPT ); Mon, 23 Jan 2006 05:40:19 -0500 Date: Mon, 23 Jan 2006 11:38:51 +0100 From: Heinz Mauelshagen To: Lars Marowsky-Bree Cc: Heinz Mauelshagen , Neil Brown , Phillip Susi , Jan Engelhardt , "Lincoln Dale (ltd)" , Michael Tokarev , linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, "Steinar H. Gunderson" Subject: Re: [PATCH 000 of 5] md: Introduction Message-ID: <20060123103851.GY2801@redhat.com> Reply-To: mauelshagen@redhat.com References: <43D02033.4070008@cfl.rr.com> <17360.9233.215291.380922@cse.unsw.edu.au> <20060120183621.GA2799@redhat.com> <20060120225724.GW22163@marowsky-bree.de> <20060121000142.GR2801@redhat.com> <20060121000344.GY22163@marowsky-bree.de> <20060121000806.GT2801@redhat.com> <20060121001311.GA22163@marowsky-bree.de> <20060123094418.GX2801@redhat.com> <20060123102601.GD2366@marowsky-bree.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060123102601.GD2366@marowsky-bree.de> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2083 Lines: 55 On Mon, Jan 23, 2006 at 11:26:01AM +0100, Lars Marowsky-Bree wrote: > On 2006-01-23T10:44:18, Heinz Mauelshagen wrote: > > > > Besides, stacking between dm devices so far (ie, if I look how kpartx > > > does it, or LVM2 on top of MPIO etc, which works just fine) is via the > > > block device layer anyway - and nothing stops you from putting md on top > > > of LVM2 LVs either. > > > > > > I use the regularly to play with md and other stuff... > > > > Me too but for production, I want to avoid the > > additional stacking overhead and complexity. > > Ok, I still didn't get that. I must be slow. > > Did you implement some DM-internal stacking now to avoid the above > mentioned complexity? > > Otherwise, even DM-on-DM is still stacked via the block device > abstraction... No, not necessary because a single-level raid4/5 mapping will do it. Ie. it supports parameters in the constructor as other targets do as well (eg. mirror or linear). > > > Sincerely, > Lars Marowsky-Br?e > > -- > High Availability & Clustering > SUSE Labs, Research and Development > SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin > "Ignorance more frequently begets confidence than does knowledge" -- Regards, Heinz -- The LVM Guy -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Heinz Mauelshagen Red Hat GmbH Consulting Development Engineer Am Sonnenhang 11 Cluster and Storage Development 56242 Marienrachdorf Germany Mauelshagen@RedHat.com +49 2626 141200 FAX 924446 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - 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/