On Mon, Dec 29, 2014 at 10:41 AM, Marc MERLIN <marc@xxxxxxxxxxx> wrote:
On Mon, Dec 29, 2014 at 10:17:00AM -0500, Chris Mason wrote:
I've hit this recently on my laptop, and haven't yet been able to
recreate it on a machine where I can debug things. The messages are
an error in the log tree replay code, and I don't think they are
actually related to any corruptions. Trying to nail it down today.
Thanks for the update and looking at it.
Just to rule things out for me, on your laptop, are you running btrfs
directly on disk, or do you have layers like dmcrypt in the middle?
(having 2 other layers myself, I never know if it's btrfs that could
be
to blame, or the other 2 layers not passing data through in atomic
bits
like they're supposed to)
I do have dmcrypt, but I really think this is only in btrfs.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
