On Sun, Aug 11, 2019 at 10:54 PM Qu Wenruo <quwenruo.bt...@gmx.com> wrote: > > > > On 2019/8/12 下午12:24, Chris Murphy wrote: > > On Sun, Mar 10, 2019 at 5:20 PM Chris Murphy <li...@colorremedies.com> > > wrote: > >> > >> On Sat, Mar 2, 2019 at 11:18 AM Chris Murphy <li...@colorremedies.com> > >> wrote: > >>> > >>> Sending URL for dump-tree output offlist. Conversation should still be > >>> on-list. > >> > >> > >> Any more information required from me at this point? > > > > This file system has been on a shelf since the problem happened. Is > > the lack of COW repairs with btrfs check solved? Can this file system > > be fixed? Maybe --init-extent-tree is worth a shot? > > > > > Latest btrfs check has solved the problem of bad CoW. In fact it's > solved in btrfs-progs v5.1 release. > > So, if you run btrfs check --clear-space-cache v1 again, it shouldn't > cause transid mismatch problem any more.
That's good news. > > Although IIRC that fs already got transid error, thus enhanced > btrfs-check won't help much to solve the existing transid mismatch problem. OK and the other bug report I just posted is this same file system failing to ro scrub. It's not obvious that the failure is due to transid mismatch. If the file system can't be fixed, I'll wipe it. -- Chris Murphy
