"Stephen C. Tweedie" wrote:
> Ideally, what I'd like to see the reconstruction code do is to:
>
> * lock a stripe
> * read a new copy of that stripe locally
> * recalc parity and write back whatever disks are necessary for the stripe
> * unlock the stripe
>
> so that the data never goes through the buffer cache at all, but that
> the stripe is locked with respect to other IOs going on below the level
> of ll_rw_block (remember there may be IOs coming in to ll_rw_block which
> are not from the buffer cache, eg. swap or journal IOs).
>
> > We are '100% journal-safe' if power fails during resync.
>
> Except for the fact that resync isn't remotely journal-safe in the first
> place, yes. :-)
>
> --Stephen
Sorry for my ignorance I got a little confused by this post:
Ingo said we are 100% journal-safe, you said the contrary,
can you or Ingo please explain us in which situation (power-loss)
running linux-raid+ journaled FS we risk a corrupted filesystem ?
I am interested what happens if the power goes down while you write
heavily to a ext3/reiserfs (journaled FS) on soft-raid5 array.
After the reboot if all disk remain intact physically,
will we only lose the data that was being written, or is there a possibility
to end up in a corrupted filesystem which could more damages in future ?
(or do we need to wait for the raid code in 2.3 ?)
sorry for re-asking that question, but I am still confused.
regards,
Benno.
