Re: Linux does not care for data integrity

From: Bill Davidsen (davidsen_at_tmr.com)
Date: 06/02/05

  • Next message: Tony Lindgren: "[PATCH] Dynamic tick for x86 version 050602-1"
    Date:	Wed, 01 Jun 2005 21:37:05 -0400
    To: Jeff Garzik <jgarzik@pobox.com>
    
    

    Jeff Garzik wrote:

    > Bill Davidsen wrote:
    >
    >> This would change the meaning of fsync from "force out the data" to
    >> "wait for the data to be written" in some implementations.
    >
    >
    > This is the meaning of fsync: copies all in-core parts of a file to
    > disk, and waits until the device reports that all parts are on stable
    > storage.
    >
    > Anything less is a bug.

    How about anything more? The truth is that much common hardware doesn't
    really make the cache to disk move visible, and turning off cache really
    hurts performance. And it would appear that fsync force a lot more data
    out of memory than just the blocks for the file in question.

    However, the point I was making is that it would be useful to be able to
    tell when the write to non-volatile took place, not to force that to
    happen. Not to do anything which would flush a lot of other stuff and
    busy the drive. What I suggest is NOT fsync, just a way to assure ordering.

    -- 
    bill davidsen <davidsen@tmr.com>
      CTO TMR Associates, Inc
      Doing interesting things with small computers since 1979
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Tony Lindgren: "[PATCH] Dynamic tick for x86 version 050602-1"

    Relevant Pages

    • Re: 2.6 vm/elevator loading down disks where 2.4 does not
      ... disk more often, as they had less RAM for cache. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Request: I/O request recording
      ... > file, ready for optimized reading. ... Linux caches disk data on a per-file basis. ... we don't go looking for the same disk blocks in the cache of /dev/hda1. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: How can I force a read to hit the disk?
      ... >> on which a file resides actually is readable. ... >> than just returning data already in the cache. ... > Force a readbefore some write data was flushed to the disk?? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Is there a "make hole" (truncate in middle) syscall?
      ... You look at the dentry. ... If you need to look at the contents of the disk (to check for the runs of null ... believe the dentry cache is a different beast than the page cache... ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: cache limit
      ... >> balance cache, and app memory. ... when reads and writes are going to the disk at the same time. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)