Date: Tue, 1 Jan 2008 17:25:16 +0100 (CET)
From: Jan Engelhardt <jengelh@computergmbh.de>
To: Gene Heskett <gene.heskett@gmail.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: semi-regular plea for stable device mapping
In-Reply-To: <200801011054.40512.gene.heskett@gmail.com>
Message-ID: <Pine.LNX.4.64.0801011723140.14900@fbirervta.pbzchgretzou.qr>
References: <200801011054.40512.gene.heskett@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1310
Lines: 29


On Jan 1 2008 10:54, Gene Heskett wrote:
>
>BUT!  This defeats a fix I've had in my modprobe.conf for over a year now that 
>gave the LVM stuff a stable major device # of 238, and now my LVM major is 
>back to whatever mood the kernel is in, in this particular bootup case to 
>#253.
>
>It may now be stable for a bit at that number because I see that pktcdvd has 
>been given a stable address of its own, apparently with a major of 10.  That 
>was the wedgie that fscked things up originally for me.  But what else lurks 
>in the deep end of this experimental pool, to play piranna with us again when 
>we least expect it?

Why exactly would you require a fixed major - not running udev or thelike?
Use the boot parameter, dm_mod.major=238.

>This drives tar up a wall because it uses this device number as part of the 
>file comparisons it does, and it thinks everything is therefore new and needs 
>a full level 0 backup.  This is not at all practical, and requires that 

I wonder how FreeBSD gets around this, because they've got dynamic numbers
everywhere.

--
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/