[lkml]   [2002]   [Jul]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ANNOUNCE] Ext3 vs Reiserfs benchmarks
    On Mon, Jul 15, 2002 at 11:59:48PM +0200, Ketil Froyn wrote:
    > On 15 Jul 2002, Patrick J. LoPresti wrote:
    > > Without calling fsync(), you *never* know when the data will hit the
    > > disk.
    > Doesn't bdflush ensure that data is written to disk within 30 seconds or
    > some tunable number of seconds?

    It TRIES TO, it does not guarantee anything.

    The MTA systems are an example of software suites which have
    transaction requirements. The goal has been usually stated
    as: must not fail to deliver.

    Practical implementations without full-blown all encompassing
    transactions will usually mean that the message "will be delivered
    at least once", e.g. double-delivery can happen.

    One view to MTA behaviour is moving the message from one substate
    to another during its processing.

    These days, usually, the transaction database for MTAs is UNIX
    filesystem. For ZMailer I have considered (although not actually
    done - yet) using SleepyCat DB files for the transaction subsystem.
    There are great challenges in failure compartementalisation, and
    integrity, when using that kind of integrated database mechanisms.
    Getting SEGV is potentially _very_ bad thing!

    > Ketil

    /Matti Aarnio
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:27    [W:0.024 / U:4.164 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site