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.
If someone wants some "smart" lights but can't do mains wiring they are going to buy the bulbs. Easy as that. Most people don't know/care about the issues those bulbs have.
Because then the lights wouldn't change brightness or color temperature with the angle of the sun, my motion sensors wouldn't work, and the light wouldn't turn on together with my morning alarm.
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've got a Sever running Homeassistant with the ESPHome Addon.
The Lights got a custom PCB in them using a ESP32 and a 4 channel warm/cold white led strip driver. But you can also build them using of-the-shelf parts.
They are mains powered without a switch, instead i wired the switches to a sensor input. This allows me to control the light either via the switch, or Homeassistant. They even got some buttons directly on them to force them on/off if my server is down.
I also got a radar in there for presence detection. Basically the same as an infrared motion sensor, but it doesn't turn the light off while im on the toilet.
Thanks to using Homeassistant, I can change the color temperature and brightness of the lights depending on the time of day. It's really nice to have some dim and warm lights in the evening before going to bed.
But ESPHome isn't limited to some custom build stuff. Anything that uses an ESP32* chip can be flashed to run ESPHome instead of whatever it came with.
I got some sonoff relays that control my shutters and an Emporia Vue 2 to measure my power usage. Depending on the device you might be able to flash it either via Wifi or you have to disassemble it to get to the programming pins. The nice thing about the ESP32 is that a vendor cannot lock the firmware. You can always flash something custom.
ESPHome isn't limited to Homeassistant however. You can also have each device run a web-server to control it, or connect it to MQTT.
Also i should mention some alternatives:
Tasmota: similar to ESPHome, but while ESPHome as the configuration compiled into the firmware Tasmota can be reconfigured on the fly. Not like the update process of ESPHome is slow however.
WLED: if you only want to control some addressable RGB led strips. It does that one job way better than ESPHome.
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 build my own smart lights to avoid this kind of bs. Thanks to ESPhome i didn't even need to program them myself. Everything is in an offline VLan and connected to Homeassistant.
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.