[lkml]   [2010]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.36 io bring the system to its knees
    On Tue, Nov 9, 2010 at 5:32 PM, Dave Chinner <> wrote:
    > Don't forget to mention data=writeback is not the default because if
    > your system crashes or you lose power running in this mode it will

    You will lose data even with data=ordered. All the data that didn't
    get logged before the crash is lost anyway.

    So your argument is kind of dishonest. The thing is, if you have a
    crash or power outage or whatever, the only data you can really rely
    on is always going to be the data that you fsync'ed before the crash.
    Everything else is just gravy.

    Are there downsides to "data=writeback"? Absolutely. But anybody who
    tries to push those downsides without taking the performance and
    latency issues into account is just not thinking straight.

    Too many people think that "correct" is somehow black-and-white. It's
    not. "The correct answer too late" is not worth anything. Sane people
    understand that "good enough" is important.

    And quite frankly, "data=writeback" is not wonderful, but it's "good
    enough". And it helps enormously with at least one class of serious
    performance problems. Dismissing it because it doesn't have quite the
    guarantees of "data=ordered" is like saying that you should never use
    "pi=3.14" for any calculations because it's not as exact as
    "pi=3.14159265". The thing is, for many things, three significant
    digits (or even _one_ significant digit) is plenty.

    ext3 [f]sync sucks. We know. All filesystems suck. They just tend to
    do it in different dimensions.


     \ /
      Last update: 2010-11-10 17:07    [W:0.021 / U:0.360 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site