I bought a proper country jacket last year for far more than I'd normally spend. It's very heavy, very waterproof, very full of pockets, very farmerish, very good.
blackstrat
joined 1 year ago
I gave up trying to setup a Mastodon server in docker. Lemmy was pretty tricky at the time as the docs were wrong. My email server was a bit tricky, but I've not really done much to tinker with it in the proceeding 6 years, so was worth it.
Depends what you want to do.
Want to sit? The chairs. Want to see? The lights. Want to not fall under the building? The floor. Want to get out? The door. Want to swim? The pool. Want to get out of the pool? The ladder. Want to get changed? The changing room. Want to warm the room? The heater.
Why fake serial numbers?
I used btrfs once. Never again!
Are you saying SSDs are faster than HDDs?
I was thinking Proxmox would add a layer between the raw disks and the VM that might interfere with ZFS, in a similar way how a non IT more HBA does. From what I understand now, the passthrough should be fine.
The server runs Proxmox and one of the VMs runs as a fileserver. Other VMs and containers do other things.
I won't be running ZFS on any solid state media, I'm using spinning rust disks meant for NAS use.
My desire to move to ZFS is bitrot prevention and as a result of this:
Good point. Having a small VM that just needs the HBA passed through sounds like the best idea so far. More portable and less dependencies.
I'm starting to think this is the way to do it because it loses the dependency on Proxmox to a large degree.
It stole all my data. It's a bit of a clusterfuck of a file system, especially one so old. This article gives a good overview: https://arstechnica.com/gadgets/2021/09/examining-btrfs-linuxs-perpetually-half-finished-filesystem/ It managed to get into a state where it wouldn't even let me mount it readonly. I even resorted to running commands of which the documentation just said "only run this if you know what you're doing", but actually gave no guidance to understand - it was basically a command for the developer to use and noone else. It ddn't work anyway. Every other system that was using the same disks but with ext4 on their filesystems came back and I was able to fsck them and continue on. I think they're all still running without issue 6 years later.
For such an old file system, it has a lot of braindead design choices and a huge amount of unreliability.