Re: fsync() madness
- Date: Mon, 21 Apr 2008 08:25:47 -0700
- From: Gary Greene <greeneg@xxxxxxxxxxxxxx>
- Subject: Re: fsync() madness
On Monday 21 April 2008 8:15:51 am Sami Liedes wrote: > On Mon, Apr 21, 2008 at 02:11:40PM +0200, Lubos Lunak wrote: > > On Sunday 20 of April 2008, Sami Liedes wrote: > > > I had missed that post. Still, no analysis of the performance hit > > > there, and I think the attitude of "no data loss at all allowed at any > > > power loss, implement at any cost to performance" is misguided. > > > > Tell that to XFS developers and their users. Anyway, where's your patch? > > The patch is simple and not very fine grained, but effective and > shouldn't break anything unless a power loss happens. Attached. > > Sami Again you are not taking into account XFS. How many times must we iterate over this.... _If you don't have the code check which FS this is on and PROPERLY deal with this, you will kill users data._ -- Gary L. Greene, Jr. Sent from: peorth.tolharadys.net 08:24:18 up 11 days, 12:34, 1 user, load average: 0.22, 0.07, 0.10 ========================================================================== Developer and Project Lead for the AltimatOS open source project Volunteer Developer for the KDE open source project See http://www.altimatos.com/ and http://www.kde.org/ for more information ========================================================================== Please avoid sending me Word or PowerPoint attachments.
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
- Follow-Ups:
- Re: fsync() madness
- From: Luciano Montanaro
- Re: fsync() madness
- From: Sami Liedes
- Re: fsync() madness
- From: John Tapsell
- Re: fsync() madness
- References:
- fsync() madness
- From: Sami Liedes
- Re: fsync() madness
- From: Lubos Lunak
- Re: fsync() madness
- From: Sami Liedes
- fsync() madness
- Prev by Date: Re: fsync() madness
- Next by Date: Re: fsync() madness
- Previous by thread: Re: fsync() madness
- Next by thread: Re: fsync() madness
- Index(es):