On 9/12/19 3:28 PM, Filipe Manana wrote: >>> 2) writeback for some btree nodes may never be started and we end up >>> committing a transaction without noticing that. This is really >>> serious >>> and that will lead to the "parent transid verify failed on ..." >>> messages. > Two people reported the hang yesterday here on the list, plus at least > one more some weeks ago. This was one of my messages that I got when I reported an issue in the thread 'Chasing IO errors' which occurred in mid to late August. > I hit it myself once last week and once 2 evenings ago with test cases > from fstests after changing my development branch from 5.1 to 5.3-rcX. > > To hit any of the problems, sure, you still need to have some bad > luck, but it's impossible to tell how likely to run into it. > It depends on so many things, from workloads, system configuration, etc. > No matter how likely (and how likely will not be the same for > everyone), it's serious because if it happens you can get a corrupt > filesystem. I can't help you with any specifics workloads causing it. I just notices that my fs went read only, that is all.
