• 2 Posts
  • 106 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
  • I really try to move to Jellyfin, but there’s always some papercuts that block me. Tried it last weekend again, and:

    • It just can’t find most of my movies in the NAS share. They never appear in the library.
    • The music player cannot play all my files. DSF files are transcoded to AAC. Also finamp streams AAC and not Opus, and uses more data than Plexamp did.

    I also tried Navidrome for music. Weirdly it had hiccups playing some files, and DSF was again a problem.

    I really want to get out from Plex, but I use Plexamp so much and it handles my huge music library really well it’s hard to switch :(




  • Yeah… So I’m in Berlin, and in Germany the internet operators finally are building fiber everywhere. The provider who lays the fiber to our street is Deutsche Telekom, and they promise to pay everything: laying the fiber, bringing it to our house and bringing the fiber to every apartment for a two year monopoly on fiber internet after which it’s up for competition using their cables. What needs to happen next is our landlord (a Swiss company) and house management company to agree on these guys to come in, put little fiber dividers to every floor and drill a hole to the walls so we get the fiber cable to our apartment.

    Of course this being Germany, they are very slow on agreeing on that, we might need to go to court and for sure we need to talk to our neighbors who own their apartments to push them a bit. I’d expect us to get the connection maybe before end of 2025. But eventually it will happen…


  • I am doing exactly the same as what the OP is doing. In addition to that, I will unify my beelink mini PC proxmox server and our old Intel atom NAS into one rack server with AMD EPYC, proxmox and truenas in a VM.

    I sure hope our landlord and the Internet operator can agree on the operator finally bringing fiber cables to all apartments. Then I would have fast enough uplink to my homelab.










  • His job is to not get the maintainers to agree, but his job definitely is to bark a bit if somebody behaves like Ted.

    It might even be Rust is not meant for Linux kernel and it will never happen. Or it happens in the driver layers, but stays out from the core. We do not know yet. The concern Ted is raising is definitely valid: if the C APIs change, people who work daily in the C code cannot spent cycles fixing the Rust APIs. These people have their day jobs which pays them to maintain these subsystems, and it is at least not yet clear will these employers fund rewriting anything in Rust. There are tens of filesystems in Linux, with lifetimes passing around that are not documented and might not work in Rust.

    Note: I’m a Rust dev for the past 10 years, and I follow this discussion with high interest.






  • Me neither, but the risk is there and well documented.

    The point was, ZFS is not great as your normal laptop/workstation filesystem. It kind of requires a certain setup, can be slow in certain kinds of workflows, expects disks of same size and is never available immediately for the latest kernel version. Nowadays you actually can add more disks to a pool, but for a very long time you needed to build a new one. Adding a larger disk to a pool will still not resize it, untill all the disks are replaced.

    It shines with steady and stable raid arrays, which are designed to a certain size and never touched after they are built. I would never use it in my workstation, and this is the point where bcachefs gets interesting.


  • But scrub is not fsck. It just goes through the checksums and corrects if needed. That’s why you need ECC ram so the checksums are always correct. If you get any other issues with the fs, like a power off when syncing a raidz2, there is a chance of an error that scrub cannot fix. Fsck does many other things to fix a filesystem…

    So basically a typical zfs installation is with UPS, and I would avoid using it on my laptop just because it kind of needs ECC ram and you should always unmount it cleanly.

    This is the spot where bcachefs comes into place. It will implement whatever we love about zfs, but also be kind of feasible for mobile devices. And its fsck is pretty good already, it even gets online checks in 6.11.

    Don’t get me wrong, my NAS has and will have zfs because it just works and I don’t usually need to touch it. The NAS sits next to UPS…