From: Ush <ofeeley@gmail.com>
To: William <wh@designed4u.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: the umount() saga for regular linux desktop users
Date: Fri, 31 Dec 2004 09:48:41 -0800 [thread overview]
Message-ID: <2b8348ba041231094816d02456@mail.gmail.com> (raw)
In-Reply-To: <200412311741.02864.wh@designed4u.net>
On Fri, 31 Dec 2004 17:41:02 +0000, William <wh@designed4u.net> wrote:
> Regularly, when attempting to umount() a filesystem I receive 'device is busy'
> errors. The only way (that I have found) to solve these problems is to go on
> a journey into processland and kill all the guilty ones that have tied
> themselves to the filesystem concerned.
Even a lazy umount doesn't work? "umount -l <filesystem-name>"
> In my opinion, in order for linux to be trully user friendly, "a umount()
> should NEVER fail" (even if the device containing the filesystem is no
> longuer attached to the system). The kernel should do it's best to satisfy
> the umount request and cleanup. Maybe the kernel could try some of the
> following:
Would it be user-friendly if this forcible umount caused the user to lose data?
Oisin
next prev parent reply other threads:[~2004-12-31 17:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 17:41 the umount() saga for regular linux desktop users William
2004-12-31 17:47 ` Arjan van de Ven
2004-12-31 17:48 ` Ush [this message]
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
[not found] <fa.iji5lco.m6nrs@ifi.uio.no>
[not found] ` <fa.fv0gsro.143iuho@ifi.uio.no>
2005-01-02 12:38 ` Bodo Eggert
2005-01-02 20:27 ` Adrian Bunk
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
-- strict thread matches above, loose matches on Subject: below --
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
[not found] <fa.foeqpaf.nlmd9n@ifi.uio.no>
[not found] ` <fa.d9avdr3.1jm46gr@ifi.uio.no>
2005-01-03 1:17 ` Bodo Eggert
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=2b8348ba041231094816d02456@mail.gmail.com \
--to=ofeeley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wh@designed4u.net \
/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.