> This sounds like a bug, either in an application, or in Linux kernel's
> scsi disk implementation.
> Data is only guaranteed to be written onto disk following an
> fsync(2)-like operation in the application. And in turn, it is the
> Linux kernel's responsibility to ensure that such a flush is propagated
> all the down to the low-level driver, in my opinion. Sophisticated
I think file systems also have certain write ordering requirements to
maintain on-disk consistency, these would also need to make sure the
order is correct. AFAICS, SuSE have patched the reiserfs in their
2.4.20 kernel (8.2) to use write barriers (however deep these are
anchored), but ext3 or xfs don't show related log entries at boot-up or
Is this something that will be fixed in 2.6 or will 2.6 still require me
to turn off the write cache?
> hosts can have barriers, and "dumb" hosts can simply call the drive's
> flush-cache / sync-cache command.
-- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/