[lkml]   [2003]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: precise characterization of ext3 atomicity
Mike Fedyk wrote:

>On Thu, Sep 04, 2003 at 08:25:18PM +0400, Hans Reiser wrote:
>>In data=journal and data=ordered modes ext3 also guarantees that the
>>metadata will be committed atomically with the data they point to. However
>>ext3 does not provide user data atomicity guarantees beyond the scope of a
>>single filesystem disk block (usually 4 kilobytes). If a single write()
>>spans two disk blocks it is possible that a crash partway through the write
>>will result in only one of those blocks appearing in the file after
>And how does reiser4 do this without changing the userspace apps?
We don't. We just make the hovercraft, we don't force you to go over
the water.....

>Most files are written with several write() calls, so even if each call is
>atomic, your entire file will not be there.
>Also, ext3 could claim the same atomicity if it only updated meta-data on
>write() call boundaries, instead of block boundaries.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:48    [W:0.080 / U:17.872 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site