From kde-devel  Mon Apr 21 15:56:29 2008
From: Allan Sandfeld Jensen <kde () carewolf ! com>
Date: Mon, 21 Apr 2008 15:56:29 +0000
To: kde-devel
Subject: Re: fsync() madness
Message-Id: <200804211833.46923.kde () carewolf ! com>
X-MARC-Message: https://marc.info/?l=kde-devel&m=120879338917982

On Monday 21 April 2008, Stephan Kulow wrote:
> Am Montag 21 April 2008 schrieb Esben Mose Hansen:
> > On Monday April 21 2008 11:06:07 Allan Sandfeld Jensen wrote:
> > > I prefer fsync() in a number of cases. The one time where I appreciate
> > > it the most; is when copying files to a USB-device, because I know can
> > > unplug the device as soon as KDE copy claims to be done.
> >
> > I'm pretty sure I saw the kernel devs had or would implement something to
> > ensure USB-devices were aggresively flushed, which means you can take the
> > stick whether using KDE or some other applications.
>
> You may think about vfat file system, which does flush-on-close since Chris
> Mason implemented it somewhen 2006. So a ext3 file system on USB stick will
> still be dangerous if not mounted sync (which the KDE mediamanager does by
> default, btw).
>
Okay then, sounds logically. Just seems wrong to disable the kernel 
disk-scheduler and disk-cache this way. If only the applications managed to 
sync everytime they indicated to the user a task was done, things would be 
more efficient.

`Allan
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<