I ran that command and I cannot get the email to send properly to the
mailing list as the attachment of the output is over 4.6M.
On 12/7/2018 11:49 AM, Doni Crosby wrote:
The output of the command is attached. This is what errors showed up
on the system:
parent transid verify failed on 3563224842240 wanted 5184691 found 5184689
parent transid verify failed on 3563224842240 wanted 5184691 found 5184689
parent transid verify failed on 3563222974464 wanted 5184691 found 5184688
parent transid verify failed on 3563222974464 wanted 5184691 found 5184688
parent transid verify failed on 3563223121920 wanted 5184691 found 5184688
parent transid verify failed on 3563223121920 wanted 5184691 found 5184688
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
Ignoring transid failure
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
Ignoring transid failure
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
Ignoring transid failure
WARNING: eb corrupted: parent bytenr 31801344 slot 132 level 1 child
bytenr 3563231461376 level has 1 expect 0, skipping the slot
parent transid verify failed on 3563231494144 wanted 5184691 found 5183325
parent transid verify failed on 3563231494144 wanted 5184691 found 5183325
parent transid verify failed on 3563231494144 wanted 5184691 found 5183325
parent transid verify failed on 3563231494144 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563231526912 wanted 5184691 found 5183325
parent transid verify failed on 3563231526912 wanted 5184691 found 5183325
parent transid verify failed on 3563231526912 wanted 5184691 found 5183325
parent transid verify failed on 3563231526912 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563229626368 wanted 5184691 found 5184689
parent transid verify failed on 3563229626368 wanted 5184691 found 5184689
parent transid verify failed on 3563229937664 wanted 5184691 found 5184689
parent transid verify failed on 3563229937664 wanted 5184691 found 5184689
parent transid verify failed on 3563226857472 wanted 5184691 found 5184689
parent transid verify failed on 3563226857472 wanted 5184691 found 5184689
parent transid verify failed on 3563230674944 wanted 5184691 found 5183325
parent transid verify failed on 3563230674944 wanted 5184691 found 5183325
parent transid verify failed on 3563230674944 wanted 5184691 found 5183325
parent transid verify failed on 3563230674944 wanted 5184691 found 5183325
Ignoring transid failure
On Fri, Dec 7, 2018 at 2:22 AM Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote:
On 2018/12/7 下午1:24, Doni Crosby wrote:
All,
I'm coming to you to see if there is a way to fix or at least recover
most of the data I have from a btrfs filesystem. The system went down
after both a breaker and the battery backup failed. I cannot currently
mount the system, with the following error from dmesg:
Note: The vda1 is just the entire disk being passed from the VM host
to the VM it's not an actual true virtual block device
[ 499.704398] BTRFS info (device vda1): disk space caching is enabled
[ 499.704401] BTRFS info (device vda1): has skinny extents
[ 499.739522] BTRFS error (device vda1): parent transid verify failed
on 3563231428608 wanted 5184691 found 5183327
Transid mismatch normally means the fs is screwed up more or less.
And according to your mount failure, it looks the fs get screwed up badly.
What's the kernel version used in the VM?
I don't really think the VM is always using the latest kernel.
[ 499.740257] BTRFS error (device vda1): parent transid verify failed
on 3563231428608 wanted 5184691 found 5183327
[ 499.770847] BTRFS error (device vda1): open_ctree failed
I have tried running btrfsck:
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563224121344 wanted 5184691 found 5184688
parent transid verify failed on 3563221630976 wanted 5184691 found 5184688
parent transid verify failed on 3563221630976 wanted 5184691 found 5184688
parent transid verify failed on 3563223138304 wanted 5184691 found 5184688
parent transid verify failed on 3563223138304 wanted 5184691 found 5184688
parent transid verify failed on 3563223138304 wanted 5184691 found 5184688
parent transid verify failed on 3563223138304 wanted 5184691 found 5184688
parent transid verify failed on 3563224072192 wanted 5184691 found 5184688
parent transid verify failed on 3563224072192 wanted 5184691 found 5184688
parent transid verify failed on 3563225268224 wanted 5184691 found 5184689
parent transid verify failed on 3563225268224 wanted 5184691 found 5184689
parent transid verify failed on 3563227398144 wanted 5184691 found 5184689
parent transid verify failed on 3563227398144 wanted 5184691 found 5184689
parent transid verify failed on 3563229593600 wanted 5184691 found 5184689
parent transid verify failed on 3563229593600 wanted 5184691 found 5184689
parent transid verify failed on 3563229593600 wanted 5184691 found 5184689
parent transid verify failed on 3563229593600 wanted 5184691 found 5184689
According to your later dump-super output, it looks pretty possible that
the corrupted extents are all belonging to extent tree.
So it's still possible that your fs tree and other essential trees are OK.
Please dump the following output (with its stderr) to further confirm
the damage.
# btrfs ins dump-tree -b 31801344 --follow /dev/vda1
If your objective is only to recover data, then you could start to try
btrfs-restore.
It's pretty hard to fix the heavily damaged extent tree.
Thanks,
Qu
Ignoring transid failure
Checking filesystem on /dev/vda1
UUID: 7c76bb05-b3dc-4804-bf56-88d010a214c6
checking extents
parent transid verify failed on 3563224842240 wanted 5184691 found 5184689
parent transid verify failed on 3563224842240 wanted 5184691 found 5184689
parent transid verify failed on 3563222974464 wanted 5184691 found 5184688
parent transid verify failed on 3563222974464 wanted 5184691 found 5184688
parent transid verify failed on 3563223121920 wanted 5184691 found 5184688
parent transid verify failed on 3563223121920 wanted 5184691 found 5184688
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
parent transid verify failed on 3563229970432 wanted 5184691 found 5184689
Ignoring transid failure
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
parent transid verify failed on 3563231428608 wanted 5184691 found 5183327
Ignoring transid failure
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
parent transid verify failed on 3563231444992 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
parent transid verify failed on 3563231412224 wanted 5184691 found 5183325
Ignoring transid failure
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
parent transid verify failed on 3563231461376 wanted 5184691 found 5183325
Ignoring transid failure
Segmentation fault
btrfs check --recover also ends in a segmentation fault
I am aware of chunk-recover and have tried to run it but got weary
when I saw dev0 not vda1.
Any help would be appreciated,
Doni
uname -a:
Linux Homophone 4.18.0-0.bpo.1-amd64 #1 SMP Debian 4.18.6-1~bpo9+1
(2018-09-13) x86_64 GNU/Linux
btrfs --version:
btrfs-progs v4.7.3
btrfs fi show:
Label: 'Array' uuid: 7c76bb05-b3dc-4804-bf56-88d010a214c6
Total devices 1 FS bytes used 6.05TiB
devid 1 size 29.11TiB used 6.13TiB path /dev/vda1
