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
hosts can have barriers, and "dumb" hosts can simply call the drive's
flush-cache / sync-cache command.
Jeff
-
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/