fsync on ext2 only really guarantees that the data has reached the disk, what the disk does it outside the realm of the fs. If the ide drive has write back caching enabled, the data just might only be in cache. If the power is removed right after fsync returns, the drive might not get a chance to actually commit the write to platter.
Is this really the behavior in the current kernel? If so this seems quite wrong to me - if the application did an fsync, I think the kernel should be sending cache flush commands to the drive before the call completes..
-- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
