[lkml]   [2001]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    >> It's pretty clear that the IDE drive(r) is *not* waiting for the physical
    >> write to take place before returning control to the user program, whereas
    >> the SCSI drive(r) is.
    >This would not be unexpected.
    >IDE drives generally always do write buffering. I don't even know if you
    >_can_ turn it off. So the drive claims to have written the data as soon as
    >it has made the write buffer.
    >It's definitely not the driver, but the actual drive.

    As I suspected. However, testing shows that many drives, including most
    IBMs, do respond to hdparm -W0 which turns write-caching off (some drives
    don't, including some Seagates). There are also drives in existence that
    have no cache at all (mostly old sub-1G drives) and some with too little
    for this to make a significant difference (the old 1.2G TravelStar in one
    of my PowerBooks is an example).

    So, is there a way to force (the majority of, rather than all) IDE drives
    to wait until it's been truly committed to media? If so, will this be
    integrated into the appropriate parts of the kernel, particularly for
    certain members of the sync() family and FS unmounting?

    from: Jonathan "Chromatix" Morton
    mail: (not for attachments)

    The key to knowledge is not to rely on people to teach you it.

    Get VNC Server for Macintosh from

    Version 3.12
    GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
    PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
    -----END GEEK CODE BLOCK-----

    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:29    [W:0.023 / U:19.320 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site