i agree, that this is a design problem of the filesystem/blockdevice cache
management.
the drive spins down possibly before pending changes are written out so
unmounting has to ensure that later by waking up the disk and commit the
changes. also drives can spindown themself without OS
Is there any way that the drive can signal the OS about a spindown
going to happen? that way, the OS can flush changes *prior* the
spindown and the problem of waking up will be fixed.
On Wed, Sep 15, 2010 at 10:47 AM, AmenophisIII
539...@bugs.launchpad.net wrote:
i agree, that this is a design
I think this is the expected behavior of journalling file systems. When
you unmount a writable file system, the file system needs to write out a
marker saying that it was shut down cleanly and doesn't need a journal
recovery on the next mount.
Perhaps a file system could detect that it's been
I think you're right, but ntfs is not the only journaling file system
for Ubuntu. so your suggestion should apply to all of them, right?
--
Safely remove drive is waking-up my external HD
https://bugs.launchpad.net/bugs/539064
You received this bug notification because you are a member of Ubuntu
When using the Palimpest Disk Utility, unmounting the partition
causes the wakeup and detaching it causes the power-off. Should the
bug be reassigned to another package?
--
Safely remove drive is waking-up my external HD
https://bugs.launchpad.net/bugs/539064
You received this bug notification
seems rather an issue lower in the stack than nautilus then, reassigning
to udisk for now...
** Package changed: nautilus (Ubuntu) = udisks (Ubuntu)
** Changed in: udisks (Ubuntu)
Status: Incomplete = New
--
Safely remove drive is waking-up my external HD
thank you for your bug report, is the issue specific to nautilus or do
you get it in when ejecting on a command line or in the disk utility
dialog?
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low
** Changed in: nautilus (Ubuntu)
Status: New = Incomplete
--
Safely remove
