zram-swap-config VS zfs

crontab, /etc/rc.local or create a simple systemctl service are all prob the easiest and most secure ways to allow on boot. /etc/rc.local I think happens after all services think `@reboot` with crontab is the same but you would have to google to be sure. or copy and hack the service from https://github.com/StuartIanNaylor/zram-swap-config as really they are also quite simple to create

I still have https://github.com/StuartIanNaylor/zram-swap-config but doesn't do much more than https://github.com/systemd/zram-generator#readme but I passed control of https://github.com/ecdye/zram-config as maintenance aint my strong point and it was just a protest of hey guys get this sorted.

I read in a few articles that the default sram-config package has some sizing/erro handling issues. Two configuration scripts seem to be recommended: this one and this other one.

zram can help as create a swap that the majority of time will be used also mounting a small zram zstd (great text compression) for var/log will practically bring writes to pretty much nothing. Armbian have a util that does that. You are using 62.2m 9very small) of 872m main memory Swap virtual memory you are using 40.8m of 100m because dphys-swap is set to only 100m by default but is just disk space. Its prob pushed 40.8m there because its idle so its pushed it out of main memory and will pull back if ever needed. I use my util https://github.com/StuartIanNaylor/zram-swap-config and another one I did is now maintained by openhab. Dunno if systemd/zram-generator is in raspberry might actually a great zram util.

zram when your confined with 512mb as sd card swap sucks. https://github.com/StuartIanNaylor/zram-swap-config zram isn't perfect as you will get apps that pass already compressed uncompressible data, but luckily is the exception not the rule and web based is usually highly compressable.

https://github.com/StuartIanNaylor/zram-swap-config just install and reboot

Remember to finish the installation and install zram-swap-config for global zram.

Of course, 2.2.7, what was released checks notes 1 hour ago.

https://github.com/openzfs/zfs/releases/tag/zfs-2.2.7

You can, but gcc may replace it with an equivalent set of instructions as a compiler optimization, so you would have no guarantee it is used unless you hack the compiler.

On a related note, GCC optimizing away things is a problem for memset when zeroing buffers containing sensitive data, as GCC can often tell that the buffers are going to be freed and thus the write is deemed unnecessary. That is a security issue and has to be resolved by breaking the compiler’s optimization through a clever trick:

https://github.com/openzfs/zfs/commit/d634d20d1be31dfa8cf06e... 12352

Similarly, GCC may delete a memcpy to a buffer about to be freed, although I have never observed that as you generally don’t do that in production code.

Klara Inc | Fully Remote | Global | Full-time Contract Developer

Klara Inc (klarasystems.com) provides development & solutions focused on open source software and the community-driven development of OpenZFS and FreeBSD.

We develop new features, investigate/fix bugs, and support the community of these important open source infrastructure projects. Some of our recent work includes major ZFS features such as Linux Containers support (OpenZFS 2.2: https://github.com/openzfs/zfs/pull/12263), and Fast Deduplication (OpenZFS 2.3: https://github.com/openzfs/zfs/discussions/15896).

We're looking for OpenZFS Developers (3+ years of experience) to join our team:

I implemented this in ZFS’ btree implementation a few years ago:

https://github.com/openzfs/zfs/commit/677c6f8457943fe5b56d7a...

It only works if the comparator is inclined, which is why I had to use a macro and duplicate the code everywhere. C++’s templates effectively do the same thing.

WD has all kinds of weird issues with their SSDs. Some pretty major, and it's really hit or miss whether any particular one will be completely problem free or be a total nightmare. :(

• https://github.com/openzfs/zfs/discussions/14793

Best to avoid them at all costs.

Also everyone ignores the publicly visible zfs repo/issues. Corruption https://github.com/openzfs/zfs/issues/16631 crash/corruption https://github.com/openzfs/zfs/issues/16626 crash https://github.com/openzfs/zfs/issues/16623 just from this week. One of those filesystems is likely more stable than the other, not the image of perfect zfs is tiring.

There are various issues on ZFS native encryption. ZFS native encryption has been especially buggy when raw encrypted zfs snapshots are being sent or received.

https://github.com/openzfs/zfs/issues/11679

Not in a stable release yet, but check out https://github.com/openzfs/zfs/discussions/15896 if you have a need for that.

Check it out: https://github.com/openzfs/zfs/releases