Gagootron

Well, good news then: lvm comes with most modern linux distros. In fact, it is an option you can enable when installing linux mint.

I use it on every system that I run (workstations and servers) and never had any issues.

It really just makes partition management way easyer: With normal partitions you cannot grow any partition without moving all other partitions after it. LVM can do it without touching anything else.

The best case for semthing like this is when you buy bigger ssd. You can copy the data with dd and then grow any and partitions that you want without hassle.

I recommend that you take a look at LVM. It can help you manage your partitions without much planning beforehand.

You usually scrub you pool about once a month, but there are no hard rules on that. The main problem with scrubbing is, that it puts a heavy load on the pool, slowing it down.

Accessing the data does not need a scrub, it is only a routine maintenance task. A scrub is not like a disk cleanup. With a disk cleanup you remove unneeded files and caches, maybe de-fragment as well. A scrub on the other hand validates that the data you stored on the pool is still the same as before. This is primarily to protect from things like bit rot.

There are many ways a drive can degrade. Sectors can become unreadable, random bits can flip, a write can be interrupted by a power outage, etc. Normal file systems like NTFS or ext4 can only handle this in limited ways. Mostly by deleting the corrupted data.

ZFS on the other hand is built using redundant storage. Storing the data spread over multiple drives in a special way allowing it to recover most corruption and even survive the complete failure of a disk. This comes at the cost of losing some capacity however.

A ZFS Scrub validates all the data in a pool and corrects any errors.

It seems to that it works. I don’t get any web-scrapers hitting anything but my main domain. I can’t find any of my subdomains on google.

Please tell me how you believe that it works. Maybe i overlooked something…

Of course i get a bunch of scanners hitting ports 80 and 443. But if they don’t use the correct domain they all end up on an Nginx server hosting a static error page. Not much they can do there

I use good ol’ obscurity. My reverse proxy requires that the correct subdomain is used to access any service that I host and my domain has a wildcard entry. So if you access asdf.example.com you get an error, the same for directly accessing my ip, but going to jellyfin.example.com works. And since i don’t post my valid urls anywhere no web-scraper can find them. This filters out 99% of bots and the rest are handled using authelia and crowdsec

I mounted my zfs dataset in a Jellyfin VM using 9p. All the features of the host ZFS while still running in a VM