public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to umount a busy filesystem?
Date: Mon, 11 Oct 2004 00:00:55 +0200	[thread overview]
Message-ID: <1097445655.2235.18.camel@venus> (raw)
In-Reply-To: <20041010211208.GA6986@citd.de>

On Sun, 2004-10-10 at 23:12, Matthias Schniedermeyer wrote:
> On 10.10.2004 22:52, Olaf Fr?czyk wrote:
> > Hi,
> > 
> > Why I cannot umount filesystem if it is being accessed?
> > I tried MNT_FORCE option but it doesn't work.
> > 
> > Killing all processes that access a filesystem is not an option. They
> > should just get an error when accessing filesystem that is umounted.
> > 
> > Any idea how to do it?
> 
> umount -l
> 
> removes the mount in "lazy"-mode, this way the mount-point "vanishes"
> for all programs whose working-dirs aren't "within" that mount-point.
> After all files are closed the filesystem is unmounted totally.
> You can "reuse" the mount-point immediatly.
> 
Thank you.
But this:
1. Does not let the user to remove the media (eg. cdrom).
2. Does not flush buffers etc. so the media cannot be safely removed
even if it were physically possible (eg. cdrom with unlocked tray or
USB-key).

I have read that the MNT_FORCE is currently limited to NFS mounts.
Does somebody have any idea why it is limited? 
Or is the functionality planned for other filesystems too?

Regards,

Olaf


  reply	other threads:[~2004-10-10 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 20:52 How to umount a busy filesystem? Olaf Frączyk
2004-10-10 21:12 ` Matthias Schniedermeyer
2004-10-10 22:00   ` Olaf Frączyk [this message]
2004-10-12  0:24     ` Jon Masters
2004-10-12  8:48       ` Matthias Schniedermeyer

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=1097445655.2235.18.camel@venus \
    --to=olaf@cbk.poznan.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@citd.de \
    /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