On 6/27/07, Bob Marcan <bob.marcan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Tom Horsley wrote:
> On Wed, 27 Jun 2007 01:14:12 +0200
> "Andras Simon" <szajmi@xxxxxxxxx> wrote:
>
>> The problem is that there shouldn't be any loop devices in use and
>> there's nothing to unmount. The following transcript demonstrates the
>> problem:
>>
>> [root@localhost ~]# losetup -a
>> [root@localhost ~]# mount -o loop,offset=32256
>> /usr/local/kvm-images/WinXP.raw /mnt/
>> [root@localhost ~]# umount /mnt/
umount -d /mnt
>> [root@localhost ~]# losetup -a
>> /dev/loop0: [080c]:14073859 (/usr/local/kvm-images/WinXP.raw), offset
32256
>
> That looks like a pretty clear bug in umount to me. I'd suggest
> turning in a bugzilla on it. (I wonder if it only happens with
> the offset arg - you'd think people would have noticed a general
> leak of loop devices before now considering how few of them
> are available by default).
>
man umount
Right, so it's mount -d. But then there's a bug in FC5, because there
umount (without -d) does free the loop device :-)
Thanks,
Andras
--
Bob Marcan, Consultant mailto:bob.marcan@xxxxxx
S&T Slovenija d.d. tel: +386 (1) 5895-300
Leskoskova cesta 6 fax: +386 (1) 5895-202
1000 Ljubljana, Slovenia url: http://www.snt.si
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
