Messages in this thread | | | Date | Wed, 24 Jul 2002 15:33:19 -0400 | From | Kareem Dana <> | Subject | Re: loop.o device busy after umount |
| |
On Wed, 24 Jul 2002 15:19:04 -0400 Andrew Rodland <arodland@noln.com> wrote:
> On Wed, 24 Jul 2002 14:59:19 -0400 > Kareem Dana <kareemy@earthlink.net> wrote: > > > Hello, > > > > I've noticed in kernel 2.4.18 that my loop module remains busy after I > > umount the device using it. For example > > > > mount -t iso9660 -o loop file.iso /mnt > > * loop module gets loaded > > * lsmod shows "loop 7952 1 (autoclean)" > > * ps ax shows [loop0] process > > > > then > > umount /mnt > > lsmod shows the same thing - specifically the use of loop as 1 and the > > [loop0] process remains open. Trying to rmmod loop gives me a device > > or resource busy error. > > For some reason or other, umount didn't losetup -d the device. > > Try losetup -d /dev/loop0, and see whether it does what you want, or > returns some sort of error. > > --hobbs umount: mount-2.11r
losetup worked like a charm. Thanks. Any reason umount would not do that automatically though? umount -V returns umount: mount-2.11r
- Kareem - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |