From: Andrew Rodland <arodland@noln.com>
To: Kareem Dana <kareemy@earthlink.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: loop.o device busy after umount
Date: Wed, 24 Jul 2002 15:36:06 -0400 [thread overview]
Message-ID: <20020724153606.3c1189c6.arodland@noln.com> (raw)
In-Reply-To: <20020724153319.5ebd589b.kareemy@earthlink.net>
On Wed, 24 Jul 2002 15:33:19 -0400
Kareem Dana <kareemy@earthlink.net> wrote:
> Andrew Rodland <arodland@noln.com> wrote:
> > 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
> losetup worked like a charm. Thanks. Any reason umount would not do
> that automatically though? umount -V returns umount: mount-2.11r
No idea, although I can't claim to be an expert. I have mount-2.11h,
and it seems to do it automatically for me.
next prev parent reply other threads:[~2002-07-24 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 18:59 Kareem Dana
2002-07-24 19:19 ` Andrew Rodland
2002-07-24 19:33 ` Kareem Dana
2002-07-24 19:36 ` Andrew Rodland [this message]
2002-07-24 19:41 ` Andries Brouwer
2002-07-24 20:03 ` Richard B. Johnson
2002-07-24 21:25 ` Andries Brouwer
2002-07-25 11:14 ` Richard B. Johnson
2002-07-24 20:15 ` Kareem Dana
2002-07-24 19:20 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020724153606.3c1189c6.arodland@noln.com \
--to=arodland@noln.com \
--cc=kareemy@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®