On 07/03/2014 09:44 PM, Marc MERLIN wrote:
Thanks for the patch. Hopefully this will make it to the next 3.15.x
kernel.
I also went back to 3.14 anyway since the 'blocked for 120 seconds' look
like another instance of deadlocks we've been discussing here.
But just curious:
[160562.925463] parent transid verify failed on 2776298520576 wanted 41015
found 18120
What should I be doing about this?
Does it mean that I do have some kind of corruption/damage on my
filesystem?
I am afraid, scrub maybe could not fix such kind of errors, all scrub
doing is to verify whether
checksums match and if possible use good mirrors to rewrite bad one.
Such errors seem imply contention itself is corrupted, we may have
passed checksum
check after ending io, but we fail generation check afterwards.
So backups are always good.....:-)
Also, is it possible to have all these messages state which devid they
occurred on? I don't even know which device I should be worrying about
right now, and although I'm running scrub now, my understanding is that
scrub doesn't actually look at FS structures and is likely to miss this
anyway.
To get physical device name, we still need mirror num to know which device
we are locating.
Feel free to correct me if i miss something here.:-)
Thanks,
Wang
Thanks,
Marc
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
