Uh. OpnSense on bare metal can also do snapshots, if you set it up correctly…

And that’s the fault of whoever uses those hubs. You can use practically any zigbee hub you wish. Zigbee is zigbee.

You didn’t look very hard.

Cheap zigbee stuff exists everywhere. And zigbee is an open standard, so if it works, it will work until the equipment breaks.

The Linux kernel isn’t really much different between any distribution of Linux.

If it works on one, it works on the rest, in like 99% of cases.

The only real exception to that is custom distributions built specifically for a particular device or subset of devices.

In other words, for embedded devices, like phones, routers, TVs and such.

And those aren’t going to be running Ubuntu.

In my own experience, certain things should always be on their own dedicated machines.

My primary router/firewall is on bare metal for this very reason.

I do not want to worry about my home network being completely unusable by the rest of my family because I decided to tweak something on the server.

I could quite easily run OpnSense in a VM, and I do that, too. I run proxmox, and have OpnSense installed and configured to at least provide connectivity for most devices. (Long story short: I have several subnets in my home network, but my VM OpnSense setup does not, as I only had one extra interface on that equipment, so only devices on the primary network would work)

And tbh, that only exists because I did have a router die, and installed OpnSense into my proxmox server temporarily while awaiting new-to-me equipment.

I didn’t see a point in removing it. So it’s there, just not automatically started.

Lidarr + last.fm recommended list.

You sure that’s what is happening, and it’s not just mounting a different snapshot/dataset being mounted “on top” ?

I’ve seen it happen, which is why I ask. Assume the root dataset is named pool0 and has set0 set1 and set1/set2 as child datasets.

Their mount points are as follows:

/pool0/set0

/pool0/set1

/pool0/set1/set2

Now, if somehow, say set2 gets unmounted.temporarily, and you save files to /pool0/set1/set2 while the data set is not mounted, it’ll actually put those files in the set1 dataset, under the set2 directory.

But, when you mount the pool0/set1/set2 dataset again, the files under the set1 dataset are hidden by the set2 child.

Am I explaining it well enough for you to follow along?

Make sure you don’t have some similar situation by temporarily unmounting any nested datasets and ls’ing their mount points.

I’m close to a TB myself. For me, I’m a bit of a “completionist” and can’t stand having just 2 or 3 tracks from an entire album. Every track I have is accompanied by the rest of the album it was released on.

Sure, it means there are some duplicates at times, but it’s worth it to me.

Instructions unclear, now my server is slowly floating into the sky…