Re: fsync() madness
- Date: Mon, 21 Apr 2008 22:03:50 +0200
- From: Arnold Krille <kde@xxxxxxxxxxxxx>
- Subject: Re: fsync() madness
Am Montag, 21. April 2008 schrieb Esben Mose Hansen: > I discussed this with a friend (who liked XFS because it could online grow > >:) ) and it seems that the worst part of XFS behaviour in this regard was > fixed in 2.6.22 --- the bit where any dirty file was zeroed just to be > sure(!). So maybe we don't have to sync() quite so much now. He has tested > it a lot of times by installing a bios that crashed linux all the time, and > it seems to work much better now :) What is working better now? The crashing part or the not-loosing-too-much-data-on-crashes part? Sorry, couldn't help myself... Arnold -- visit http://www.arnoldarts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
- References:
- fsync() madness
- From: Sami Liedes
- Re: fsync() madness
- From: Lubos Lunak
- Re: fsync() madness
- From: Esben Mose Hansen
- fsync() madness
- Prev by Date: Re: fsync() madness
- Next by Date: Call for maintainers: kcharselect, kfloppy, ktimer, kwallet, sweeper, kregexpedit
- Previous by thread: Re: fsync() madness
- Next by thread: Re: fsync() madness
- Index(es):