bjmi

I'm also interested in this configuration. All my large HDDs should form a large BTRFS RAID 1 storage. I know Unraid was designed to be the opposite of RAID but over time filesystems, technologies and user needs change. Is there a chance that it will become a feature of Unraid?

zstd is my preferred one. I can't prove which algorithm would fit best as it is highly dependent of the usage scenario. As zstd isn't available out of the box, one can't make measurements easily. I'm fine with lz4 for the moment as everything else work as expected and Yann Collet is the author of the both algs Thanks for your effort.

lz4 works fine. # zramctl --find --size 8GiB -a lz4 /dev/zram0 But zstd emerges everywhere. Even zramctl --help mentions it <alg> specify algorithm, supported are: lzo, lz4, lz4hc, deflate, 842 and zstd

It would be great if zstd compression is also supported: # zramctl --find --size 8GiB -a zstd zramctl: /dev/zram0: failed to set algorithm: Invalid argument

I'm interested in ZRAM support in Unraid too. I can't create a traditional swapfile because the cache pool (/mnt/cache) is backed by a btrfs RAID1 filesystem and that isn't supported. root@unraid# modprobe zram modprobe: FATAL: Module zram not found in directory /lib/modules/5.15.43-Unraid but zramctl is installed... root@unraid# zramctl -V zramctl from util-linux 2.37.4

From /usr/local/sbin/update_cron you can see all *.cron within dynamix are gathered (Unraid 6.9.0) cat /boot/config/plugins/dynamix/*.cron 2>/dev/null

Total Commander SFTP plugin suffers from this problem too. It auto-detects Encoding (codepage) of file names: ANSI (local) (0) which scrambles non ANSI characters in file names.

That is what probably happened. That's why I want to export LANG variable and WinSCP encoding detection works again.

My preferred language is German where ÄäÖöÜuß– characters are used additionally. I did an initial import of my files to a user share by WinSCP (SCP method). When I accessed the same share with Windows Explorer (Windows 10, Client for Microsoft Networks) some files were missing or had bogus characters in their filenames. Samba hides those files but they were in the filesystem (ls -l shows them). It turned out that WinSCP didn't detect UTF-8 and use another code page for filenames. I could rename those files to proper UTF-8 filenames with an adapted version of iconvmv script (https://github.com/YeLee/code/blob/master/shell/iconvmv) using iconv -f ISO-8859-1 in the mv command. In order preserve other unraid users from this issue how can environment variable LANG be filled with en_US.UTF-8 for non-interactive sessions? In /etc/profile.d/lang.sh this LANG variable is exported but isn't filled when WinSCP queries it. I don't have this behaviour with Ubuntu Server. Additionally dos charset was set to cp1252 in /boot/config/smb-extra.conf afterwards. dos charset = cp1252

Hallo, WinSCP uses an auto detection method for filename encoding by quering LANG environment variable printenv LANG and activates UTF-8 filenames if the result contains UTF-8 like: en_US.UTF-8 Unfortunately this isn't the case for non-interactive sessions in Unraid. How can I set LANG variable to en_US.UTF-8 for non-interactive session? Ref: https://winscp.net/forum/viewtopic.php?p=96851#96851