All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Cheung <vividy@justware.co.jp>
To: linux-kernel@vger.kernel.org
Subject: mount -o remount,ro cause error "device is busy"
Date: Wed, 06 Mar 2002 16:40:10 +0900	[thread overview]
Message-ID: <20020306161900.C897.VIVIDY@justware.co.jp> (raw)

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.

I switch to init 1, and all user process go away.
except the following:
root         1  0.1  0.7  1056  484 ?        S    15:46   0:04 init [S] 
root         2  0.0  0.0     0    0 ?        SW   15:46   0:00 [keventd]
root         3  0.0  0.0     0    0 ?        SWN  15:46   0:00 [ksoftirqd_CPU0]
root         4  0.0  0.0     0    0 ?        SW   15:46   0:00 [kswapd]
root         5  0.0  0.0     0    0 ?        SW   15:46   0:00 [bdflush]
root         6  0.0  0.0     0    0 ?        SW   15:46   0:00 [kupdated]
root      1042  0.0  0.7  1056  484 tty1     S    16:33   0:00 init [S] 
root      1043  0.6  1.5  1840 1004 tty1     S    16:33   0:00 /bin/sh
root      1045  0.0  1.0  2260  680 tty1     R    16:33   0:00 ps aux

then i try 
mount -o ro,remount /
error occurs: device is busy.

and i try
mount -o ro,remount /usr
(another partition)
also error occurs: device is busy.

but when i try umount /usr,
it works.

certainly, there is error
device is busy for command umount /.

How can i resolve this problem?

Regards;
Michael


             reply	other threads:[~2002-03-06  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  7:40 Michael Cheung [this message]
2002-03-06  7:49 ` mount -o remount,ro cause error "device is busy" Mike Fedyk
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=20020306161900.C897.VIVIDY@justware.co.jp \
    --to=vividy@justware.co.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.