| |||||||||||||
Fsyncers and curveballs (the Firefox 3 fsync() problem)Fsyncers and curveballs (the Firefox 3 fsync() problem)Posted May 26, 2008 15:09 UTC (Mon) by lmb (subscriber, #39048)In reply to: Fsyncers and curveballs (the Firefox 3 fsync() problem) by MisterIO Parent article: Fsyncers and curveballs (the Firefox 3 fsync() problem)
Seems to me firefox should use an append-only format for some of its files - that'd mean that in case of a crash, possibly the last so many transactions would get lost, but that the main bulk of the data would still be intact and consistent.
(Log in to post comments)
Fsyncers and curveballs (the Firefox 3 fsync() problem) Posted May 27, 2008 16:23 UTC (Tue) by drag (subscriber, #31333) [Link] You mean something like: echo "<something>blahlbahlbah</something>" >> file.text ... what a concept ...
Fsyncers and curveballs (the Firefox 3 fsync() problem) Posted Jun 20, 2008 20:38 UTC (Fri) by jlokier (guest, #52227) [Link] If you think 'echo "text" >> file' cannot corrupt data before the place you're writing to, when power is lost at the wrong moment (e.g. laptop runs out of battery), think again. There are filesystems and filesystem options that will prevent that, but ext3 with default options isn't one of them. Not just theoretically: I have actually seen such corruption in log files.
|
|||||||||||||