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
<email address hidden> wrote:
> 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 intervention (see hdparm -S docs).
>
> --
> "Safely remove drive" is waking-up my external HD
> https://bugs.launchpad.net/bugs/539064
> You received this bug notification because you are a direct subscriber
> of the bug.
>
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 blockdevice cache management. /bugs.launchpad .net/bugs/ 539064
<email address hidden> wrote:
> i agree, that this is a design problem of the filesystem/
> 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 intervention (see hdparm -S docs).
>
> --
> "Safely remove drive" is waking-up my external HD
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>