Hi Thanks for reporting. May be the same bug reproduced by using $sudo TEST=003\* make test-fuzz in btrfs-progs.
More details in: https://patchwork.kernel.org/patch/10073937/ > -----Original Message----- > From: linux-btrfs-ow...@vger.kernel.org > [mailto:linux-btrfs-ow...@vger.kernel.org] On Behalf Of Patrick Mitchell > Sent: Monday, April 23, 2018 12:17 PM > To: linux-btrfs@vger.kernel.org > Subject: btrfs check : check/main.c:3654: check_owner_ref: BUG_ON > `rec->is_root` triggered, value ` > > Arch, kernel 4.15.14, btrfs progs 4.15.1. > > Had some SATA drives dropout. Have a few btrfs volumes with parent transid > verify failed errors, that all mount. > > This volume has nothing I care about, so I'm just reporting it since it looks > like a bug. None of my other volumes having issues cause core > dumps. Happy to send whatever other info might help track it down. > > > # btrfs check /dev/lvm/snapper1 > Checking filesystem on /dev/lvm/snapper1 > UUID: ef6f4923-0a03-4e41-9655-e24a13a1d879 > parent transid verify failed on 862240768 wanted 29524 found 29182 parent > transid verify failed on 862240768 wanted 29524 found 29182 > checking extents > check/main.c:3654: check_owner_ref: BUG_ON `rec->is_root` triggered, value 1 > btrfs(+0x5f98c)[0x55ec9db9198c] > btrfs(+0x12ad6)[0x55ec9db44ad6] btrfs(+0x18c7f)[0x55ec9db4ac7f] > btrfs(+0x199c6)[0x55ec9db4b9c6] btrfs(+0x19fc0)[0x55ec9db4bfc0] > btrfs(cmd_check+0xf63)[0x55ec9db94423] > btrfs(main+0x81)[0x55ec9db4e441] > /usr/lib/libc.so.6(__libc_start_main+0xea)[0x7f6923f2ff4a] > btrfs(_start+0x2a)[0x55ec9db4e55a] > [1] 9612 abort (core dumped) btrfs check /dev/lvm/snapper1 > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the > body of a message to majord...@vger.kernel.org More > majordomo info at http://vger.kernel.org/majordomo-info.html > N�����r��y����b�X��ǧv�^�){.n�+����{�n�߲)����w* jg��� �����ݢj/���z�ޖ��2�ޙ����&�)ߡ�a���� �G���h��j:+v���w��٥
