taught my machines to talk and this is how they repay me
preview
have you ever successfully broken the zfs to the point where it’s not recoverable?
@GrapheneOSRuinedMyPixel@sh.itjust.works
member since 13 Feb 2025 04:53
posts
comments
- on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 2 Sep 2026
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 2 Sep 2026
do you ever get a new shiny thing and it looks like it works very nice and coherently and then you dig a bit deeper and realize that it is just a bunch of semi-broken shit held together by glue and duct tape? that’s the state of android, that is nicely obscured on pixels by google customizations
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 2 Sep 2026
haha, no, depending on your use case zfs is mostly set and forget, you just have to get a set of sane defaults, which, at least for me, is way easier and saner than stuff like btrfs. Arch wiki is a good source for that.
scrub is a command that reads data from disks and verifies checksums, it can automatically heal the corrupt data if some redundancy is available. 0 bytes repaired means nothing was repaired, 5 errors mean that there are 5 instances where the recalculated checksums of data did not match the expected values that were calculated when initially written. Normally the command would output ‘scrub repaired 0B with 0 errors’, that’s how you know that the pool is healthy.
shprutzling the cache vdevs sideways is generally required only for obscure optimizations, I’ve never seen a case where a wrong setting would lead to data loss.
The gotchas come from a single thing: the stupid CDDL licence, which is not compatible with GPL. That means that zfs is not included in linux kernel and most of the normal linux userspace filesystem stuff do not work with zfs.
Also, keep in mind that zfs is generally almost impossible to fuck up, what I’ve done here is a result of extreme dedication and like 8 years of experience.
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 1 Sep 2026
I’ve seen a calculation somewhere for drive speed, size and scrub frequency where optimal number of extra drives was calculated. On fast storage and with weekly scrubs one extra drive should be mostly fine.
My philosophy is any raid is not really a data contingency solution - it just saves some time when the drive fails.
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 1 Sep 2026
that’s no fun. also, it turned out that this is not a disk error, the zfs metadata got corrupted and now I get a panic when trying to mount this.
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 1 Sep 2026
This is raidz1. Three 4TB NVME drives. I’ve built this machine as the primary server for services like immich as a fun project that enables me to say that my photo service runs faster than all the commercial stuff and is on ARM64. The downside is that the SoC is not supported by upstream very well so vendor patches had to be applied and there was some instability between that and my shitty electricity supply.
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 1 Sep 2026
I feel very sorry for you. I have the same problem (panic on mount) with this one, but at least it works when mounting read-only. I’ve been moving data with zfs send the entire day
-
on taught my machines to talk and this is how they repay me in c/linuxmemes@lemmy.world · 1 Sep 2026
my achievement here is that this is a proper raidz setup with multiple disks and ecc ram
-
on YOLO in c/linuxmemes@lemmy.world · 22 Aug 2026
also, machines wipe themselves at each boot! service state data is distributed via zfs send! zfs that actually works!
the problem here does not originate in zfs, this is a hardware failure due to a poorly supported SoC (vendor says PCIe works ‘normally’ since kernel 7.1, this system ran 6.19) and bad electricity supply