[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: sparse loop devices and ext3



Hi,

On Fri, Feb 09, 2001 at 06:55:15PM -0800, Peter J. Braam wrote:
> On Thu, 8 Feb 2001, Stephen C. Tweedie wrote:
> 
> It has a function create_missing_block, that calls f_write. So it should
> allocate within an ext3 transaction.  So where is all this corruption
> coming from: probably the fix to 5e you sent in a few days ago.

The 0.0.5e bug might mean that the data flush is not synchronised to
the metadata flush if you are using ordered data mode.  However, loop
device writes using bmap are *never* journaled, and the metadata
updates from the write() allocation will still be journaled.

What exactly is the desired behaviour?  For loop writes to be
data-journaled?  That will require changes to the loop device to
prevent it from ever using bmap().

Cheers,
 Stephen





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]