From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from agk.surrey.redhat.com (agk.surrey.redhat.com [172.16.10.74]) by pobox.surrey.redhat.com (8.12.8/8.12.8) with ESMTP id k3ELWpgI014198 for ; Fri, 14 Apr 2006 22:32:51 +0100 Received: from agk by agk.surrey.redhat.com with local (Exim 4.34) id 1FUVuN-0004Ay-3T for linux-lvm@redhat.com; Fri, 14 Apr 2006 22:32:51 +0100 Date: Fri, 14 Apr 2006 22:32:51 +0100 From: Alasdair G Kergon Subject: Re: [linux-lvm] LVM2, NFS and random device (major:minor) numbers Message-ID: <20060414213251.GH10725@agk.surrey.redhat.com> References: <20060414145052.GD10725@agk.surrey.redhat.com> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: LVM general discussion and development On Fri, Apr 14, 2006 at 05:22:20PM -0400, Paul Raines wrote: > that depend on a persistent device id. 2.4 kernel supported both persistent major and persistent minor But the changes to do that came after 2.6 forked off and they have never been ported to 2.6. So the tools pretend to let you specify the major - on 2.4 this works - but on 2.6 it's ignored by the kernel. I expect someone will fix the kernel side of this some day so it works like the 2.4 version in which device-mapper can use different major numbers for different devices. You should be able to specify the device-mapper major number at boot/module load time though, as the 'major' parameter, instead of having a dynamic one. Persistent minors, as you discovered, should be allocated from the top of the range. Alasdair -- agk@redhat.com