Messages in this thread |  | | | Date | Tue, 31 Mar 2009 08:25:40 -0400 | | From | Theodore Tso <> | | Subject | Re: Ext4 and the "30 second window of death" |
On Sun, Mar 29, 2009 at 12:24:21PM +0200, Alberto Gonzalez wrote: > Hi, > > - I use Ext4 as my filesystem (default in next Fedora release).
Fedora will have the patches so that applications that do replace-via-truncate (a bad idea, these applications are buggy, and will lose data sometimes even with ext3), or replace-via-rename without the fsync(), will force the blocks out to disk with the commit.
> - Let's say I've been working on my book for the last 14 months and I've > written about 400 pages on an ODF file.
Openoffice, being a portable application, that has to work on other operating systems and filesystems (for example, like Solaris's UFS), does do open/write/close/fsync/rename. So you're safe if you're using OpenOffice (and emacs, and vim).
The replace-via-truncate and replace-via-rename workarounds are there for the benefit of KDE, and GNOME, which in some configurations apparently will replace hundreds of dot files when the desktop is started up, for no reason that I can understand. (Not such a great idea for SSD write endurance!) Some people apparently spend hours making sure that their windows are exactly positioned the way they want it when their desktop starts up, and if the system crashes while their desktop is starting up, those they could lose their window positions, which apparently made a whole bunch of users cranky. In practice, most of the editors that I'm familiar with have been around for a while, have needed to make sure that that cases such as yours wouldn't result in data loss, and so are pretty good about using fsync() so that users' files wouldn't be lost, no matter what the filesystem or operating system being used.
The problem has been mostly with newer applications, especially the newer desktop ones, which have been written to assume that they only have to work safely on Linux and ext3. The replace-via-truncate and replace-via-rename workarounds provide this safety for ext4.
Best regards,
- Ted
|  |