Skip to contentSkip to conversation

crash after fsync causing serious FS corruptions (ext2, 2.6.11)

CHECKER Robert Hancock 1 participant 1 message Mar 8, 2005 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 6 lines · Jens Axboe

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..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/