[lkml]   [2000]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Status of ReiserFS + Journalling
On Thu, Oct 05, 2000 at 01:54:59PM +1100, Neil Brown wrote:
> 2/ Arrange your filesystem so that you write new data to an otherwise
> unused stripe a whole stripe at a time, and store some sort of
> chechksum in the stripe so that corruption can be detected. This
> implies a log structured filesystem (though possibly you could come
> close enough with a journalling or similar filesystem, I'm not
> sure).

You don't need a checksum I think, just an atomically updated fs block
-> actually stripe map would be enough. It can be only updated after
you wrote the new independent stripe completely.

Simply using ordered writes for it (only write map after you wrote stripe)
may be tricky though, because you could get cyclic dependencies in a single
HW map block when the file system allocates many new stripes in parallel
[so you would probably need something like soft updates and handling
of multiple versions of the map in core]

Another method when you have a logging fs is to simply log the
map block change into your normal log. At least for ext3 and reiserfs
it would be expensive though, because they can only log complete changed
hardware blocks of the map. JFS or XFS with item logging could do it
relatively cheaply.

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

 \ /
  Last update: 2005-03-22 12:45    [W:0.125 / U:23.496 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site