- 1 Post
- 521 Comments
2·4 days agoPattern: Sierra
Who sews humans together by their digestive tracts, then stops and goes for a swim?
I’M SORRY, I DIDN’T QUITE GRASP WHAT YOU WERE SAYING. COULD YOU REPEAT THAT MORE CLEARLY?
That’s an Application limit however. Leading to you being able to put files where they can no longer be worked with in a meaningful fashion (e.g. easily deleted).
I read that in the insulting Frenchman’s voice from Monty Python and the Holy Grail
There’s definitely 40% cat in this picture. But where does it start and end? Is that an eye? An ear? Can’t make heads or tails of it.
I know, but I’m poor and can’t afford RAID1 of the same capacity. Thanks for the advice anyhow.
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.
AI slope