Nothing to report.

  • Hupf@feddit.org
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    15 hours ago

    blake2b checksum, zstd compression, raid1c4 metadata and raid6 data. Kernel 6.12, btrfs-progs 6.17, ECC RAM.

    The files in the affected inode haven’t been touched for a few years. Dmesg was something about zstd decompression failed and prevented btrfs send of an incremental snapshot as well as accessing one single file.

    Due to the size of the array, I don’t always get around to do a full scrub after a (albeit rare) system crash, so I wrote it off as probably that and didn’t analyze much further at the time.

    • FrederikNJS@lemmy.zip
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      9 hours ago

      Ah, it’s probably a result of running RAID6 then. All the parity RAID modes in BTRFS still has some issues, such as suffering from the “write hole” issue. This can result in data loss when the filesystem isn’t unmounted cleanly, such as a crash or power loss.

      RAID5 and RAID6 are still not recommended for production use.