From: Jens Axboe <axboe@suse.de>
To: Mircea Damian <dmircea@kappa.ro>
Cc: Alexander Viro <viro@math.psu.edu>,
Arthur Pedyczak <arthur-p@home.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: loop problems continue in 2.4.3
Date: Mon, 16 Apr 2001 18:38:12 +0200 [thread overview]
Message-ID: <20010416183812.I9539@suse.de> (raw)
In-Reply-To: <20010416104936.B9539@suse.de> <Pine.GSO.4.21.0104160527400.3095-100000@weyl.math.psu.edu> <20010416131023.A19844@linux.kappa.ro>
In-Reply-To: <20010416131023.A19844@linux.kappa.ro>; from dmircea@kappa.ro on Mon, Apr 16, 2001 at 01:10:23PM +0300
On Mon, Apr 16 2001, Mircea Damian wrote:
> But the guy said:
> "
> > disappers from cat /proc/mounts output, but the module 'loop' shows as
> > busy and cannot be removed even though there are no more loop mounts.
> "
>
> So he has no loop mounts and he can not remove the module. This is a bug!
Ah indeed, I'll take a look.
--
Jens Axboe
next prev parent reply other threads:[~2001-04-16 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AD7EE80.5AADA578@mandrakesoft.com>
2001-04-16 1:08 ` loop problems continue in 2.4.3 Arthur Pedyczak
2001-04-16 1:37 ` Arthur Pedyczak
2001-04-16 8:49 ` Jens Axboe
2001-04-16 9:30 ` Alexander Viro
2001-04-16 10:10 ` Mircea Damian
2001-04-16 16:38 ` Jens Axboe [this message]
2001-04-16 16:37 ` Jens Axboe
2001-04-14 16:31 Aaron Lunansky
2001-04-14 20:15 ` Arthur Pedyczak
2001-04-16 23:02 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-14 3:35 Arthur Pedyczak
2001-04-14 7:54 ` Jens Axboe
2001-04-14 12:46 ` Arthur Pedyczak
2001-04-14 12:58 ` Ola Garstad
2001-04-07 22:04 Ian Eure
2001-04-09 7:56 ` Jens Axboe
2001-04-11 19:04 ` Ian Eure
2001-04-13 12:56 ` Jens Axboe
2001-04-16 16:17 ` Ian Eure
2001-04-16 20:53 ` Jens Axboe
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=20010416183812.I9539@suse.de \
--to=axboe@suse.de \
--cc=arthur-p@home.com \
--cc=dmircea@kappa.ro \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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