[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-fsdevel
Subject:    Re: Raid resync changes buffer cache semantics --- not good for journaling!
From:       Ingo Molnar <mingo () redhat ! com>
Date:       1999-10-29 18:06:24
[Download RAW message or body]


On Fri, 29 Oct 1999, Stephen C. Tweedie wrote:

> Ingo, can we work together to address this?  One solution would be the
> ability to mark a buffer_head as "pinned" against being written to disk,

> Fixing this in raid seems far, far preferable to fixing it in the
> filesystems.  The filesystem should be allowed to use the buffer cache
> for metadata and should be able to assume that there is a way to prevent
> those buffers from being written to disk until it is ready.

why dont you lock the buffer during transaction, thats the right way to
'pin' down a buffer and prevent it from being written out. You can keep a
buffer locked && dirty indefinitely, and it should be easy to unlock them
when comitting a transaction. Am i missing something? 

	Ingo

[prev in list] [next in list] [prev in thread] [next in thread]