From: Serge L. <ser...@gm...> - 2012-03-28 20:04:58
|
Heiko, yes, that does the trick - with the patch it works fine. Thanks, Serge On 03/27/2012 04:52 AM, Heiko Zuerker wrote: > Serge, > > there's a new loop-aes patch for the new util-linux: > http://loop-aes.sourceforge.net/updates/util-linux-2.21-20120228.diff.bz2 > > Maybe this helps > > Heiko > > Quoting Serge Leschinsky<ser...@gm...>: > >> Dominic, >> >> thank you and sorry for the false alarm. >> The problem was narrowed down to util-linux-2.21. >> >> Sincerely, >> Serge >> >> >> On 03/26/2012 03:05 AM, Dominic Raferd wrote: >>> On 26/03/2012 04:01, Serge Leschinsky wrote: >>>> Hi everybody, >>>> >>>> I probably found a problem with loop devices, but would like to >>>> make sure it's >>>> not the only my problem. >>>> >>>> root@temp:~ # cat /proc/partitions >>>> major minor #blocks name >>>> >>>> 8 0 31285248 sda >>>> 8 1 999956 sda1 >>>> 8 2 125004 sda2 >>>> 8 3 30160243 sda3 >>>> 7 0 97036 loop0 >>>> 252 0 7340032 dm-0 >>>> root@temp:~ # losetup -f >>>> /dev/loop0 >>>> root@temp:~ # losetup -a >>>> root@temp:~ # >>>> >>>> I.e. I booted from usb (/dev/loop0 is a system image) and it's listed in >>>> /proc/partitions, but losetup tool doesn't recognize this loop. It >>>> cause a hang >>>> during the next "mount -o loop". >>>> >>>> Thanks >>>> Serge >>> >>> It seems to work okay for me (Devil-Linux 1.6.0-RC3 32bit, server >>> version, running from 2-partition USB, booting with Syslinux): >>> >>> root@Samba:~ # cat /proc/partitions >>> major minor #blocks name >>> >>> 3 64 156290904 hdb >>> ... >>> 7 0 509118 loop0 >>> 9 0 156290816 md0 >>> 253 0 262144 dm-0 >>> 253 1 573440 dm-1 >>> 253 2 524288 dm-2 >>> 253 3 131072 dm-3 >>> 253 4 152043520 dm-4 >>> root@dl1:~ # losetup -f >>> /dev/loop1 >>> root@dl1:~ # losetup -a >>> /dev/loop0: [0801]:33 (/cd/bootcd.iso) read-only >>> >>> Regards >>> >>> Dominic |