These answers are for lvm2 not lvm1. On Tue, May 10, 2005 at 12:23:02PM +0530, Aditya Kulkarni wrote: > [1] Suppose I create two LVs named vol1 and vol2. They have the > following (major, minor) no.s. vol1 = (major=X, minor=0) and vol2 = > (major=X, minor=1). Now I reboot the system. Is it guaranteed that > vol1 and vol2 will retain their minor no.s? No. > [2] Are there some options while creating LVs that we can use so that > LVs are created with a particular minor number? Yes. lvcreate/lvchange -My --major 254 --minor 200 Minor numbers normally allocated lowest first, so best to choose higher numbers for persistent ones. [2.6 kernel currently ignores the --major option] > The issue of minor number remaining same is relevant to services being > "highly available". In my case, it happens to be the NFS exported file > system. The NFS file handle includes, among other things, the minor > no. of the device on which the exported file system resides. These days, that's configurable. See 'man exports' fsid=num. + This option forces the filesystem identification portion of the file handle + and file attributes used on the wire to be num instead of a number + derived from the major and minor number of the block device on which the + filesystem is mounted. Any 32 bit number can be used, but it must be unique + amongst all the exported filesystems. + This can be useful for NFS failover, to ensure that both + servers of the failover pair use the same NFS file handles for the shared + filesystem thus avoiding stale file handles after failover. Alasdair -- agk@redhat.com _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
