Messages in this thread | | | From | Erik Hensema <> | Subject | LVM/Device mapper breaks with -mm (was: Re: 2.5.66-mm1) | Date | Wed, 26 Mar 2003 12:26:37 +0000 (UTC) |
| |
Andrew Morton (akpm@digeo.com) wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.66/2.5.66-mm1/
LVM or device mapper seems to be broken in -mm. I've only tried the following kernels so far: 2.5.64 - works 2.5.65-mm2 - doesn't work 2.5.66 - works 2.5.66-mm1 - doesn't work
I'm getting these messages while setting up LVM from my bootscripts (I've included the actual commands prefixed with a > ):
Remounting root file system (/) read/write for vgscan... > mount -n -o remount,rw / Removing old device inodes... > rm /dev/system/* /dev/mapper/* Setting up devices... > /usr/local/sbin/devmap_mknod.sh Creating /dev/mapper/control character device with major:10 minor:63. Scanning for LVM volume groups... > /usr/local/sbin/vgscan Reading all physical volumes. This may take a while... Found volume group "system" using metadata type lvm1 Activating LVM volume groups... > /usr/local/sbin/vgchange -a y system device-mapper: allocating minor 0. device-mapper: allocating minor 1. device-mapper: destroying md device-mapper: destroying table device-mapper: allocating minor 0. device-mapper: destroying md device-mapper: destroying table 1 logical volume(s) in volume group "system" now active
The only active volume is the most recently created volume.
On 2.5.6x-vanilla the output of vgchange is: device-mapper: allocating minor 0. device-mapper: allocating minor 1. device-mapper: allocating minor 2. 3 logical volume(s) in volume group "system" now active -- Erik Hensema <erik@hensema.net> - 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/
| |