Jbd2 async problem

[valdis.kletnieks at vt.edu]

On Mon, 22 Jan 2018 20:18:47 +0800, Rock Lee said:

> I think in order to keep the consistency, the whole transaction should
> be discarded, as long as not all the metadata blocks have the right
> crc value in the transaction. But why jbd2 still copies the metadata
> block(with the right crc) to filesystem when bad crc metadata blocks
> exist ?

Consider the case of 75 metadata blocks in the journal, with one bad block.

Which results in less total damage when the journal is replayed:

1) Applying the 74 good ones (if possible) and complain about the one bad one?

2) Refusing to deal with *any* of them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180122/be6e2e9f/attachment.sig>