public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petro <petro@auctionwatch.com>
To: Michael Cheung <vividy@justware.co.jp>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-kernel@vger.kernel.org
Subject: Re: mount -o remount,ro cause error "device is busy"
Date: Wed, 6 Mar 2002 18:27:49 -0800	[thread overview]
Message-ID: <20020307022749.GF32504@auctionwatch.com> (raw)
In-Reply-To: <20020306074908.GA342@matchmail.com> <20020306011519.C963@lynx.adilger.int> <20020306172418.C8A3.VIVIDY@justware.co.jp>
In-Reply-To: <20020306172418.C8A3.VIVIDY@justware.co.jp>

On Wed, Mar 06, 2002 at 05:33:45PM +0900, Michael Cheung wrote:
> hi,
> 
> maybe i am wrong, but I really can't find any other process runing.
> 
> my step is:
> 1) "/" and "/usr" are busy
> 2) shut down to single user mode
> 3) "/" still busy
> 4) "/usr" can be unmounted, but can't mount -o ro,remount /usr, show busy error.
> 5) umount -a, after this, only /proc and / exist.
> 6) mount -o ro,remount /, show busy error.
> On Wed, 6 Mar 2002 01:15:19 -0700
> Andreas Dilger <adilger@clusterfs.com> wrote:
> > Clearly, some program is keeping "/usr" busy (which is keeping "/" busy)
> > before the change to single user mode.  Just a bit of "lsof" needed to
> > find such things.                                      ||||
                                                           ^^^^
    Best bet is to man lsof. 

    lsof's your buddy. 
    
-- 
Share and Enjoy. 

      parent reply	other threads:[~2002-03-07  2:28 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
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 [this message]

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=20020307022749.GF32504@auctionwatch.com \
    --to=petro@auctionwatch.com \
    --cc=adilger@clusterfs.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