Re: A buglet with LVM-0.9.1
J Sloan writes: > I discovered that lvm seems to have a problem > with compaq raid controllers - the partitions > don't have the normal names like /dev/sda1, > but instead names like /dev/ida/c0d0p1 - > > lvm seems to works OK, but lvmdiskscan freaks... > > lvmdiskscan -- filling directory cache... > lvmdiskscan -- walking through all found disks / partitions > lvmdiskscan -- /dev/ida/c0d0p1 [1000.06 MB] free whole disk > lvmdiskscan -- no valid disks / partitions found > lvmdiskscan -- please check your disk device special files! LVM _should_ take care of such devices as well, because there are several block devices which don't live directly in /dev, especially with devfs. According to "lvm_dir_cache.c", it should already check /dev/ida for disks. If it doesn't work for you, this is a bug. It would be useful if you ran "lvmdiskscan -d" and "cat /proc/partitions" and sent the output to [EMAIL PROTECTED] Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: A buglet with LVM-0.9.1
> I discovered that lvm seems to have a problem > with compaq raid controllers - the partitions > don't have the normal names like /dev/sda1, > but instead names like /dev/ida/c0d0p1 - Quite a few controllers do this i2o, ida, dac960, .. . The user tools really need to cope with it. Its been true for a fair while and ended up necessary before /dev/ simply got too big - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
A buglet with LVM-0.9.1
Hi, I discovered that lvm seems to have a problem with compaq raid controllers - the partitions don't have the normal names like /dev/sda1, but instead names like /dev/ida/c0d0p1 - lvm seems to works OK, but lvmdiskscan freaks... lvmdiskscan works normally on other systems, which have conventional disk controllers. This is OK - case: /tmp (tty/dev/pts/1): bash: 623 > lvscan lvscan -- ACTIVE "/dev/lxlvm/lvm1" [3.12 GB] lvscan -- 1 logical volumes with 3.12 GB total in 1 volume group lvscan -- 1 active logical volumes This is OK too - case: /tmp (tty/dev/pts/1): bash: 622 > df Filesystem 1k-blocks Used Available Use% Mounted on /dev/ida/c0d0p11007928220124736604 24% / /dev/ida/c0d0p82015904251196 1662304 14% /home /dev/ida/c0d0p71007928 240956488 1% /opt /dev/ida/c0d0p94031856 1660664 2166380 44% /usr /dev/ida/c0d0p32015920 61768 1851744 4% /var /dev/lxlvm/lvm13225352 1888308 1173204 62% /disks/backup But this is not in agreement: case: /tmp (tty/dev/pts/1): bash: 625 > lvmdiskscan -v lvmdiskscan -- reading all disks / partitions (this may take a while...) lvmdiskscan -- filling directory cache... lvmdiskscan -- walking through all found disks / partitions lvmdiskscan -- /dev/ida/c0d0p1 [1000.06 MB] free whole disk lvmdiskscan -- no valid disks / partitions found lvmdiskscan -- please check your disk device special files! Hope this is of use - jjs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
