All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Date: Sun, 27 Feb 2022 18:45:55 +0100	[thread overview]
Message-ID: <2dfcbc130c55cc6fd067b93752e90bd2b079baca.camel@scientia.org> (raw)

Hey.

This is on 5.16.11, Debian sid.

This filesystem has existed since quite long (is the one from my main
working notebook).

Today I was doing a full backup onto another btrfs, with:
  tar --selinux --xattrs "--xattrs-include=*" --acls --numeric-owner -cf backup.tar /mnt/snapshots/2022-02-27
in which /mnt/snapshots/2022-02-27 is a snapshot from the filesystem
with the issues.

While tar was (or actually it still is) running I got these in the
kernel log:
Feb 27 18:35:10 heisenberg kernel: BTRFS info (device dm-1): disk space caching is enabled
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511299584, 64511303680)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511303680, 64511307776)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511307776, 64511311872)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511311872, 64511315968)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511315968, 64511320064)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511320064, 64511324160)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511324160, 64511328256)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511328256, 64511332352)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511332352, 64511336448)
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum hole found for disk bytenr range [64511336448, 64511340544)
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601640960 csum 0x62c2c721 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601645056 csum 0xff51e027 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 2, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601649152 csum 0x681a44cd expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 3, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601653248 csum 0xbbfad1b7 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 4, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601657344 csum 0x09ae86f1 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 5, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601661440 csum 0x09ee43ad expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 6, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601665536 csum 0xaae8fc18 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 7, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601669632 csum 0xe6d04b46 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 8, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601673728 csum 0x3e49bf9d expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 9, gen 0
Feb 27 18:36:52 heisenberg kernel: BTRFS warning (device dm-0): csum failed root 1583 ino 1354893 off 601677824 csum 0x08695db5 expected csum 0x00000000 mirror 1
Feb 27 18:36:52 heisenberg kernel: BTRFS error (device dm-0): bdev /dev/mapper/system errs: wr 0, rd 0, flush 0, corrupt 10, gen 0

And this in tar:
tar: 2022-02-25_1/home/calestyo/cpu-tests/test-vid-high-res.mkv: File shrank by 334726574 bytes; padding with zeros


1) Any ideas what caused this respectively what it means?

2) Can I check whether this is actually the file that caused that
issue?

3) Can I check whether other files are affected?

4) Is it recommended to recreate the filesystem on dm-0?

I would have a number of generations of snaphsots of that filesystem,
also sent/received onto another btrfs, if that would help anything for
debugging.


Thanks,
Chris

             reply	other threads:[~2022-02-27 17:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 17:45 Christoph Anton Mitterer [this message]
2022-02-27 23:26 ` BTRFS error (device dm-0): parent transid verify failed on 1382301696 wanted 262166 found 22 Qu Wenruo
2022-02-28  0:38   ` Christoph Anton Mitterer
2022-02-28  0:55     ` Qu Wenruo
2022-02-28  5:19       ` Christoph Anton Mitterer
2022-02-28  6:54         ` Qu Wenruo
2022-02-28  5:32       ` Christoph Anton Mitterer
2022-02-28  6:48         ` Qu Wenruo
2022-02-28 15:24           ` Christoph Anton Mitterer
2022-03-01  0:19             ` Qu Wenruo
2022-03-01  2:14               ` Christoph Anton Mitterer
2022-03-01  2:30                 ` Qu Wenruo
2022-03-02  1:38                   ` Christoph Anton Mitterer
2022-03-02  2:01                     ` Qu Wenruo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2dfcbc130c55cc6fd067b93752e90bd2b079baca.camel@scientia.org \
    --to=calestyo@scientia.org \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.