I'm using 2.4.5-pre5 and before on 2.4.x (without -ac) and don't have such
problem.
boston:root:/tmp> mount -o loop ram /mnt
boston:root:/tmp> umount /mnt
boston:root:/tmp> strace losetup -d /dev/loop0
execve("/sbin/losetup", ["losetup", "-d", "/dev/loop0"], [/* 47 vars */])
= 0
brk(0) = 0x804b408
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or
directory)
Did you umount the loopback device or ensure that nobody is using it?
On Wed, 23 May 2001, Adam Schrotenboer wrote:
> Using 2.4.4-ac3 (as well as in 2.4.3*) I have found it impossible to
> unmap a loopback
>
> strace losetup -d /dev/loop0 (relevant portion)
>
> open("/dev/loop0", O_RDONLY) = 3
> ioctl(3, LOOP_CLR_FD, 0) = -1 EBUSY (Device or resource busy)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
