Is it, though? 8 years is 8 years.

I might say it’s complicated because all the other presidents finished their presidencies. Trump has three more years, In theory.

Blocky artifacts are the result of poor bitrates. In streaming services it’s due to over compressing the stream, which is why you see it when part of a scene is still or during dark scenes. It’s due to the service cheaping out and sending UHD video at 720p bitrates.

You’re talking about a boycott. A strike is people refusing to work

I’ve done that click and drag many times. Nothing worse than accidentally dragging a folder designated with pseudo random numbers into another pseudo random numbered folder, and not knowing if you actually dragged it into a folder, or missed and did nothing

The only town I saw in that area in my 5 second search is Jordan, with a population of 357.

This seems to only be true in conservative States.

I try keep my data drives and boot drives separate on my servers, I make sure I can rebuild the server relatively easily so no matter what happens I can get back up and running. In my research on LVMs I wasn’t seeing anything saying you could just move the drives to a new setup, that you had to export and import first. In the case of a suddenly dead boot drive, I wouldn’t be able to do that. I did see some steps for backing up an LVMs metadata and recovering from that, so I might be sure I do that at some point, but another user said that modern distros should be able to scan for LVMs without issue, which is not what I found in my quick test in my setup. So I’ll be checking that out in a more modern setup to double check.

From what I was reading, recovering from corrupted metadata is not something I want to do. I’d rather not use LVM if that’s what’s required if I can’t just move the drives to a new server, as nice as it would be to resize filesystems on a whim.

I did not find just moving the drives to work. There were some other issues that I came across that might have a part to play in it, I made the lvm and filesystem on an RPI5 running OMV and moved it to a rock3c running OMV from an armbian install. Turns out there’s a pagefile size mismatch between the two that prevented mounting the btrfs filesystem. But I still wasn’t able to get the rock3c to recognize the VG or that there were new PVs attached without exporting first. So perhaps the armbian install isn’t modern enough to automatically recognize it.

I didn’t expect learning new things about btrfs to be the outcome of this little experiment, but I guess that’s just how things work.

That’s kind of what I figured, my biggest concern at this point would be how difficult it is to move the lvm volume to a different device. It seems pretty straightforward if you have a working setup, but from what I’m seeing in my research is silence if your device (server, etc.) dies and you need to move those volumes to another. I’m finding guides on either recovering from corruption or lost metadata, or transferring from one working device to another. Nothing I can find about importing a fully functional lvm to a new device if it hasn’t been exported.

I’ll be able to do that later today, so I guess I’ll see what happens if I do. Better to try it out now when it isn’t critical.