On Thu, Jul 26, 2001 at 09:42:37PM +1000, Andrew Morton wrote:
If postfix is capable of opening the files O_SYNC or of doing
fsync() on them then the `chattr +s' is no longer necessary -
unlike ext2, when the O_SYNC write() or the fsync() return, the
directory contents (as well as the inode, bitmaps, data, etc) will
all be tight on disk and will be restored after a crash.
This should speed things up considerably, especially with
journalled-data mode. I need to test and characterise this some
more to come up with some quantitative results and configuration
recommendations.
Postfix does an fsync on file before closing them, it then does a
rename and expects once rename as returned, the renamed actually
occured --- even if the fs crashes. It also expects if you fsync a
file, then it will appear in the parent directory with certainty and
not say /lost+found after fsck on reboot.
Without +s under ext2, you can loose file(s) in /lost+found because
open+write+fsync+close works and ensures the data is on disk, but the
parent directory doesn't get synced to disk, so it might get lost.
--cw
-
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/
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:26 EST