On 08/03/2010 09:20 AM, Valmor de Almeida wrote: > > Hello, > > After a recent sync and new kernel built, I get these messages from > fdisk -l that did not use to get before. Searching the web, it appears > that fdisk is listing my LVM partitions. Why is it doing now? It has > never done it before. > > Thanks, > > -- > Valmor > > > fdisk -l > > Disk /dev/dm-0: 26.8 GB, 26843545600 bytes > 255 heads, 63 sectors/track, 3263 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-0 doesn't contain a valid partition table > > Disk /dev/dm-1: 10.7 GB, 10737418240 bytes > 255 heads, 63 sectors/track, 1305 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-1 doesn't contain a valid partition table > > Disk /dev/dm-2: 5368 MB, 5368709120 bytes > 255 heads, 63 sectors/track, 652 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-2 doesn't contain a valid partition table > > Disk /dev/dm-3: 2147 MB, 2147483648 bytes > 255 heads, 63 sectors/track, 261 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-3 doesn't contain a valid partition table > > Disk /dev/dm-4: 53.7 GB, 53687091200 bytes > 255 heads, 63 sectors/track, 6527 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-4 doesn't contain a valid partition table > > > df > > /dev/mapper/vfda-usr 26213596 11144004 15069592 43% /usr > /dev/mapper/vfda-var 10485436 232620 10252816 3% /var > /dev/mapper/vfda-opt 5242716 311388 4931328 6% /opt > /dev/mapper/vfda-tmp 2097084 32852 2064232 2% /tmp > /dev/mapper/vfda-home
It seems to me you now have BLK_DEV_DM in your kernel. I've seen this on many systems with lvm. I always thought it was normal and I just ignored them. But I do have some systems that have lvm that don't show those errors. What partition support do you have in your new kernel?
