From: "Gregory T. Norris" <haphazard@socket.net>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: umount report "busy" on r/o remount of root filesystem
Date: Mon, 18 Sep 2000 20:47:08 -0500 [thread overview]
Message-ID: <20000918204708.B11052@glitch.snoozer.net> (raw)
In-Reply-To: <39C61AD4.BEC29E72@Hell.WH8.TU-Dresden.De>; from sorisor@Hell.WH8.TU-Dresden.De on Mon, Sep 18, 2000 at 03:38:28PM +0200
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
I seem to be able to reliably reproduce it as well. Let me know if I
can be of any help.
On Mon, Sep 18, 2000 at 03:38:28PM +0200, Udo A. Steinberg wrote:
> This should probably be added to the 2.4.x bug-list. Since Pavel
> seems to be able to constantly reproduce it, it should be possible to
> track the problem down with his help.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
parent reply other threads:[~2000-09-19 2:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <39C61AD4.BEC29E72@Hell.WH8.TU-Dresden.De>]
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=20000918204708.B11052@glitch.snoozer.net \
--to=haphazard@socket.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®