Bug - dir and log versions are not preserving ownership and permissions of target_dir about zram-config HOT 4 CLOSED

Don't configure zram for tmp. Haven't a clue how zram would bind to a tmpfs folder but never occured to me that it would be of any use at all.

from zram-config.

tmpfs when idle pushes out to zswap so this is a pointless exercise and prob not a good idea. Tmpfs even though uncompressed is only uncompressed for none idle files and when idle should be pushed to swap which if zswap enabled will end there or normal HD swap if exist.
Supposedly as was at one stage thinking it maybe good for systemd and such but when idle its pushed to swap.

from zram-config.

/tmp is not always tmpfs, there are many systems where /tmp is just directory in the root partition like in raspbian. Next, /tmp was just example, the described bug occurs on any directory as the problem is with not preserved ownership and permissions. Simply, the current implementation works only for root or if there is a higher level directory from which it takes proper default ownership. Which is limiting factor.

from zram-config.

Yeah you are right as really perms should be cloned I will get round to that sometime this week.
Try that as with the kernel updates of raspberry many of the overlay patches are now in place as was always a wait for 4.18+

from zram-config.