linux VS sanoid

Fan control generally involves hysteresis. This means a cooling fan turns on at one temperature, and then turns off once temperature has fallen to another lower temperature. This avoids cycling the fan on and off too much. The difference between those two temperatures is hysteresis. The default hysteresis is 10°C and maybe the fan never manages to cool the CPU to 45°C. A parameter has been added to change hysteresis: https://github.com/raspberrypi/linux/commit/fa390133fd17f2cc6aa5a7d2e472c073a1115fe1

I see that the PR against the Raspberry Pi linux repo is out [0]. Interestingly they are introducing a BCM2712 defconfig with a 64k default page size.

[0] - https://github.com/raspberrypi/linux/pull/5618

and can grab their patched kernel source here ( use the dtbs and overlays and kernel from your compiled version)

Also was your pi issue related to this? https://github.com/raspberrypi/linux/issues/3381 or what do you mean jittery, unstable?

Could be related to the driver load order/blacklisting (https://github.com/raspberrypi/linux/issues/435) Or couple of people report configuring the dtoverlay=imx477 in the boot config helped (https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README)

thanks, I also found this: https://github.com/raspberrypi/linux/issues/5398

And ready! :)

> It is the most basic task for Linux computer...

Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited:

https://github.com/raspberrypi/linux/issues/3010

Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless.

https://www.discomp.eu/wireless-minipci-cards_c14501412.html

I’m on the other end of the spectrum. I like knowing the flags and settings I use to create the pools.

For snapshots and replication take a look at sanoid (https://github.com/jimsalterjrs/sanoid).

I use a combo of PBS and ZFS with Sanoid. The ZFS snapshots are nice because you define it all in a config file with frequent, hourly, daily, weekly, monthly snaps retained however you want. Importantly I use that on the root pool as well as my data pools. With PBS I have a custom retention config and have it backing up VMs and LXCs every couple hours. The PBS dedupe functionality makes it possible to keep full backups going back ages with minimal storage consumption, just the changed blocks. PBS is running inside a VM yes, but it’s storage is on another pool.

[3] https://github.com/jimsalterjrs/sanoid/

No, it's written by the developer of Sanoid and Syncoid. The foremost open source ZFS snapshotting tool. He contributes on this sub all the time.

Hi there! Not so much to answer your questions, but are you aware of Sanoid and syncoid? It does backup and remote Sync in the most seamless way. Perhaps this would solve some of your concerns...