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).
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).