Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264340AbUD0UjR (ORCPT ); Tue, 27 Apr 2004 16:39:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264344AbUD0UjQ (ORCPT ); Tue, 27 Apr 2004 16:39:16 -0400 Received: from [80.72.36.106] ([80.72.36.106]:50312 "EHLO alpha.polcom.net") by vger.kernel.org with ESMTP id S264340AbUD0UjO (ORCPT ); Tue, 27 Apr 2004 16:39:14 -0400 Date: Tue, 27 Apr 2004 22:39:09 +0200 (CEST) From: Grzegorz Kulewski To: viro@parcelfarce.linux.theplanet.co.uk Cc: Linux Kernel Mailing List Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (? In-Reply-To: <20040427202813.GA17014@parcelfarce.linux.theplanet.co.uk> Message-ID: References: <20040427002323.GW17014@parcelfarce.linux.theplanet.co.uk> <20040427010748.GY17014@parcelfarce.linux.theplanet.co.uk> <1083070293.30344.116.camel@watt.suse.com> <20040427140533.GI14129@stingr.net> <20040427183410.GZ17014@parcelfarce.linux.theplanet.co.uk> <20040427200459.GJ14129@stingr.net> <20040427202813.GA17014@parcelfarce.linux.theplanet.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1972 Lines: 44 On Tue, 27 Apr 2004 viro@parcelfarce.linux.theplanet.co.uk wrote: > On Wed, Apr 28, 2004 at 12:04:59AM +0400, Paul P Komkoff Jr wrote: > > > Excuse me? The damn thing had found nothing. However, it didn't care > > > to release the devices it had claimed - hadn't even closed them, as the > > > matter of fact. That's a clear and obvious bug, regardless of any > > > disagreements. > > > > As far as I can see from here, evms parsed partition table, called > > dmsetup several times and created corresponding nodes in /dev/evms. > > ... without saying anything? > > > Logic is easy - evms trying to concentrate block device management > > into its own hands, but we have in-kernel partitioning code to > > consider ... > > How nice of them. > > Well, AFAICS that means > a) either kernel side of the things or the userland tools should > printk/syslog - at least that evms device had been set up > b) any distribution that runs this from initrd/init scripts would > better take care of having sane fstab. > c) nobody sane should put that as default. Oh, wait, it's gentoo > we are talking about? Nevermind, then. But what default? Gentoo just calls evms_activate before mounting filesystems to check if there are evms volumes (because filesystems can reside on it). And, according to man page, this is the right usage of evms_activate. And Gentoo could not know easily that I have no evms volumes in the system. And I possibly could insert some and boot Gentoo (and for example have label not device in fstab to specify fs to mount). I really think that evms_activate should not take the device that is not for it. And I think Gentoo is right. (And it is the best distro I ever tried.) Grzegorz Kulewski - 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/