For media files (bad idea for databases), I’m using Kubernetes CronJobs with restic. It mounts PVC to the cron job pod and backups target directories to S3 storage.

Plot twist: The handed fishes are highly contained with inorganic arsenic, and they’re trying to kill humans with more sophisticated methods.

jmpd(jump directory): fuzzy finds and opens directory with fzf

# fish shell
function jmpd
    set _selection $(fzf --walker=dir);
    if test -n "$_selection"
        cd "$_selection";
    end
end

The worst part is, international laws and conventions are basically means nothing at this point. US actions simply incentivizes more countries to get mass-destruction weapons.

• Does US call you as 51. state? Get a nuke.
• Does US want to invade your island? Get a nuke.
• Does US want to airstrike your country? Get a nuke.
• Does US government officials breach your constitutional rights? Maybe consider owning a mini-nuke.

Thanks to these maniacs, Kim Jong Un now seems to be wisest person on the earth…

I don’t think its rpi or network switch, unless you’ve overclocked rpi with liquid nitrogen 😅. So, I assume its TrueNas device.

If it were a significant power difference, say 20-30 watts, you could easily find the process using htop/iotop. However, 6 watt difference is a relatively small value for a device with ~25 watts of idle power . It might be a process using just 1% system resources. That’s why I would look for systemd timers, cronjobs etc. to find scheduled tasks on specific times. Another possibility is automated S.M.A.R.T. self-tests. Those tests don’t show up in htop or iotop.

LinkedIn.

Imagine Twitter and Facebook teaming up for a Dragon Ball style fusion, turning into this cringe fake business guru with a Ghibli style profile picture, spitting out AI generated posts and running impression based non-sense polls.

UPS devices normally uses wall (input) power, and switches to battery when input voltage is out of the target thresholds. So, input.load should represent the percentage of current wall power (in VA) relative to UPS’s max rated input power (VA). If your devices uses more power, input power from wall should increase as well.

If it’s peaking in certain times, it could be due some scheduled job temporarily increase CPU frequency, or automated tasks like file system snapshot might power-up/spin drives longer than regular usage.

• 2x18k - mirrored ZFS pool.
• 1x47k - 2.5" drive from an old laptop used for torrents, temp data, non-critical pod volumes, application logs etc.
• 1x32k - automated backups from ZFS pool. It’s kinda partial mirror of the main pool.
• 1x18k - (NVME) OS drive, cache volumes for pods.

Instead of single pool, I simply split my drives into tiers: cache, storage, and trash due to limited drive counts. Most R/W goes to the cheap trash and cache disks instead of relatively new and expensive NAS drives.

Biggest difference is being able to execute INSTCMD commands, at least that was the main reason why I developed my own tool. Another less important differences are: older ARM support and since it’s written in Rust, it’s much more efficient in terms of resource usage. TBH, being that efficient only makes sense for very low-power devices.

Besides that, I don’t think you can go wrong with either project.