#2630 HIGH Trial-3: Not enough feedback for unmount failure
Zarro Boogs per Child
bugtracker at laptop.org
Thu Aug 2 16:02:53 EDT 2007
#2630: Not enough feedback for unmount failure
-------------------------------+--------------------------------------------
Reporter: Zack | Owner: tomeu
Type: defect | Status: new
Priority: high | Milestone: Trial-3
Component: journal-activity | Version:
Resolution: | Keywords:
Verified: 0 |
-------------------------------+--------------------------------------------
Comment (by Zack):
This ticket was for feedback when the user tries to unmount a disk via the
"Unmount" menu item, and the unmount fails due to the device being busy.
The feedback you're describing sounds good for the case of a user
prematurely and physically yanking the disk from the system without
successfully unmounting, but not quite right for this case since the disk
is still physically there, it's just still not safe to remove yet.
{{{
This is what I've poorly described in the initial ticket:
1 User plugs a removable disk in
(stuff happens)
2 User wants to unplug disk
3 User selects 'umount' from the disk's menu in the Journal
4 Journal tries to unmount the disk but fails, because it has open files
What I'm proposing is something like:
5 Journal sticks a Warning badge on the Disk's icon
What you're proposing isn't the same thing, but could fit like:
6A User yanks disk while it's still mounted, losing data
7A Disk's icon goes "white stroke/no fill" with a Warning badge
8A User reinserts disk
9A* Disk is rebuild to correct data loss/corruption
Although #9A isn't possible yet.
And then, I'd like to propose what happens when the user doesn't yank the
disk:
6B When the disk is able to be unmounted, Journal unmounts it
automatically
7B User removes disk and loses no data
}}}
Man, is WikiFormatting a pain sometimes.
--
Ticket URL: <http://dev.laptop.org/ticket/2630#comment:3>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list