From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org, ofeeley@gmail.com
Cc: William <wh@designed4u.net>
Subject: Re: the umount() saga for regular linux desktop users
Date: Fri, 31 Dec 2004 13:22:14 -0500 [thread overview]
Message-ID: <200412311322.14359.gene.heskett@verizon.net> (raw)
In-Reply-To: <2b8348ba041231094816d02456@mail.gmail.com>
On Friday 31 December 2004 12:48, Ush wrote:
>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?
No, it wouldn't be user friendly, but it would sure be user
educational when he asked why his resume dissappeared.
Let me toss this out for discussion.
There are some times when the usual 5 second flush schedule should be
tossed out the window, and the data written immediately. A quickly
unpluggable usb memory dongle is a prime candidate to bite the user
precisely where it hurts. Floppies also fit this same scenario, I
don't know at the times I've written an image with dd, got up out of
my chair and went to the machine and slapped the eject button to
discover to my horror, that when my hand came away from the button
with disk in hand, the frigging access led was now on that wasn't
when I tapped the button.
Usually just re-inserting the disk allows the write to continue and
nothing is lost. But I've learned to do a couple of sync's and the
umount before pulling the disk. But theres a whole lot more protocol
to doing that with a usb device.
Thats one of the things that could be done to improve the user
friendliness of linux. Really Old Hands are used to those limits,
but newbies just coming in from the dark side are not impressed when
its something like that as nearly their first exposure to linux.
>Oisin
>-
>To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.31% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-12-31 18:22 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
2004-12-31 18:22 ` Gene Heskett [this message]
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
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=200412311322.14359.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ofeeley@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).