On Wed, Mar 3, 2021 at 10:34 AM George R Goffe <grgo...@yahoo.com> wrote: > > Chris, > > Here's the information you requested. > > I'm wondering just how this happened. One of the messages refers to "beyond > end of device". I'm alarmed.
Don't panic. But do keep your backups fresh, while you have the chance. What I can tell you is Btrfs isn't changing the data or the checksums on disk. They've changed since the checksums were computed at btrfs-convert time. While it is possible there's a bug that can explain this, it's not one I'm aware of. Can you file a bug for this? Component is btrfs-progs. You can delete the prefilled form and just include the following info: - kernel and btrfs-progs versions at the time of btrfs-convert - before conversion, did you run 'e2fsck -fvy' (or equivalent)? - after conversion, did you run 'btrfs balance' (don't do it now)? - have there been any partition modifications after conversion? - output from the following: btrfs insp dump-s /dev/sdX fdisk -l /dev/sdX smartctl -x /dev/sdX - complete dmesg from this scrub you just did, please attach as a file, no trimming; if you've rebooted since that scrub you can get a copy back from the journal using 'journalctl -b-1 -k -o short-monotonic --no-hostname > dmesg.txt' where the -b value is -1 for previous boot, -2 for the one before that, etc. > [ 2101.646773] BTRFS warning (device sda8): checksum error at logical > 1780042522624 on dev /dev/sda8, physical 6250299392, root 256, inode 257, > offset 786432, length 4096, links 1 (path: image) All of the 'checksum error' messages are about the same file. The ext2_saved/image file used for rollback. This is surely not a coincidence, I just don't know why there'd be checksum errors only with this one file. The unable to fixup errors match up with each checksum error and indicat there isn't a mirror copy for self-healing. Basically the first error is 'this is bad" and the second error is "I can't fix it". > [36365.549230] BTRFS error (device sda8): scrub: tree block 1777055424512 > spanning stripes, ignored. logical=1777055367168 > [36365.549262] attempt to access beyond end of device > sda8: rw=0, want=3470811376, limit=3470811312 I'm not sure about this yet - need more info. -- Chris Murphy _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
