All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Andy Lutomirski <luto@myrealbox.com>, linux-kernel@vger.kernel.org
Subject: Re: the umount() saga for regular linux desktop users
Date: Sun, 2 Jan 2005 21:27:12 +0100	[thread overview]
Message-ID: <20050102202712.GC4183@stusta.de> (raw)
In-Reply-To: <E1Cl509-0000TI-00@be1.7eggert.dyndns.org>

On Sun, Jan 02, 2005 at 01:38:29PM +0100, Bodo Eggert wrote:
> Andy Lutomirski wrote:
> 
> > I have this complaint too, and MNT_DETACH doesn't really do it.
> > Sometimes I want to "unmount cleanly, damnit, and I don't care if
> > applications that are currently accessing it lose data."  Windows can do
> > this, and it's _useful_.
> 
> I have an additional feature request: The umount -l will currently not work
> for unmounting the cwd of something like the midnight commander without
> closing it. On the other hand, rmdiring the cwd of running application
> works just fine.

A rm does not actually remove things that are still accessed.

As an example, do the following (1 and 2 are shells, cdimage is a full
CD image):

1> less cdimage
2> df .
2> rm cdimage
2> df . 
1> q (quit less)
2> df .

> Maybe it's possible to extend the semantics of umount -l to change all
> cwds under that mountpoint to be deleted directories which will no
> longer cause the mountpoint to be busy (e.g. by redirecting them to a
> special inode on initramfs). Most applications can cope with that (if
> not, they're buggy), and it will do 90% of the usural cases while still
> avoiding data loss.
>...

If the appication of a user was writing some important output to a file 
on the NFS mount you want to umount there will be data loss...

If you _really_ want to umount something still accessed by applications 
simply kill all applications with "fuser -k".

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-01-02 20:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.iji5lco.m6nrs@ifi.uio.no>
     [not found] ` <fa.fv0gsro.143iuho@ifi.uio.no>
2005-01-02 12:38   ` the umount() saga for regular linux desktop users Bodo Eggert
2005-01-02 20:27     ` Adrian Bunk [this message]
2005-01-03  0:37       ` Bodo Eggert
2005-01-02 22:43     ` Valdis.Kletnieks
2005-01-04 20:28       ` Lee Revell
2005-01-05  2:12         ` Bodo Eggert
     [not found] <fa.foeqpaf.nlmd9n@ifi.uio.no>
     [not found] ` <fa.d9avdr3.1jm46gr@ifi.uio.no>
2005-01-03  1:17   ` Bodo Eggert
2005-01-02 19:37 Pavel Machek
2005-01-02 20:11 ` Adrian Bunk
2005-01-02 20:15   ` Pavel Machek
2005-01-02 20:34   ` Oliver Neukum
2005-01-02 20:51     ` Adrian Bunk
2005-01-02 20:56       ` Pavel Machek
2005-01-02 21:05         ` Adrian Bunk
2005-01-03  9:35           ` Frank van Maarseveen
2005-01-03 19:14             ` Ingo Oeser
2005-01-02 20:36   ` Adrian Bunk
2005-01-03  1:36     ` Puneet Vyas
2005-01-02 20:36   ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31 17:41 William
2004-12-31 17:47 ` Arjan van de Ven
2004-12-31 17:48 ` Ush
2004-12-31 18:22   ` Gene Heskett
2004-12-31 18:31     ` Miquel van Smoorenburg
2004-12-31 21:48     ` Tom Felker
2005-01-01  0:07       ` Gene Heskett
2004-12-31 17:50 ` Andries Brouwer
2005-01-01 19:40   ` Andy Lutomirski
2004-12-31 17:51 ` Gene Heskett
2005-01-16  4:39 ` Greg Stark

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=20050102202712.GC4183@stusta.de \
    --to=bunk@stusta.de \
    --cc=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@myrealbox.com \
    /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.