Skip to contentSkip to conversation

Loopback, unable to release

DISCUSSION Adam Schrotenboer 3 participants 3 messages May 23, 2001 – May 24, 2001

lore
Share & tools
lore
#0 lore raw

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)
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "ioctl: LOOP_CLR_FD: Device or re"..., 44ioctl: LOOP_CLR_FD: Device or resource busy) = 44
_exit(1) = ?

also I have loop.o as module, and use count never decreases, in fact right now it is at 294.

#1 lore raw
Quoted 15 lines · Adam Schrotenboer

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)
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "ioctl: LOOP_CLR_FD: Device or re"..., 44ioctl: LOOP_CLR_FD:
Device or resource busy) = 44
_exit(1) = ?

Quoted 2 lines

also I have loop.o as module, and use count never decreases, in fact right now it is at 294.

Uhm weird. Are you talking about module use count or loop reference count?

Signature · 1 line
Jens Axboe
#2 lore raw
In reply to Adam Schrotenboer

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?

Quoted 7 lines · Adam Schrotenboer

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)