> On May 28, Andreas Dilger <adilger@turbolabs.com> wrote:
>
> >Actually ext3/jfs does exactly what you suggest - it uses lazy commits
> >of the journal to disk, but honors the O_SYNC flag and does an immediate
> What about metadata? BSD people usually complain ext2 can lose data
> in a crash because of lazy metadata updates.
Ditto with standard BSD UFS - only you tend to get data you shouldnt be able
to see. Ext3 is journalling so your metadata is always consistent or can be
made so by playback of the log.
Effectively your file system comes back at some consistent point in time. It
might not be the instant you switched off though. O_SYNC and fsync() effectively
ensure they dont return until the state the machine will come back has that
data committed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:20 EST