From: Mike Fedyk <mfedyk@matchmail.com>
To: Michael Cheung <vividy@justware.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mount -o remount,ro cause error "device is busy"
Date: Tue, 5 Mar 2002 23:49:08 -0800 [thread overview]
Message-ID: <20020306074908.GA342@matchmail.com> (raw)
In-Reply-To: <20020306161900.C897.VIVIDY@justware.co.jp>
In-Reply-To: <20020306161900.C897.VIVIDY@justware.co.jp>
On Wed, Mar 06, 2002 at 04:40:10PM +0900, Michael Cheung wrote:
> hi, all;
> I have upgraded my kernel to version 2.4.
> And i have tested 2.4.16 and 2.4.18. Both of these
> two version have the same problem when system reboot.
> "/: device is busy";
> in shutdown script:
> umount -a
> mount -n -o ro,remount /
> these two line result error: device is busy.
>
We need more info about your config. Do you have any patches in this
kernel? What modules have been loaded? Highmem? x86? drive controller?
drive? ram size? lspci output, etc...
next prev parent reply other threads:[~2002-03-06 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 7:40 mount -o remount,ro cause error "device is busy" Michael Cheung
2002-03-06 7:49 ` Mike Fedyk [this message]
2002-03-06 8:13 ` Re[2]: " Michael Cheung
2002-03-06 8:15 ` Andreas Dilger
2002-03-06 8:33 ` Re[2]: " Michael Cheung
2002-03-06 9:47 ` Andreas Schwab
2002-03-07 2:27 ` Petro
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=20020306074908.GA342@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vividy@justware.co.jp \
/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