Niltze, Ed- I came across this (fixed) issue in ZFS which touches on Reiser4: 'Reiser4's maintainer decided to modify the kernel VFS to export the old function' [1] https://github.com/zfsonlinux/zfs/pull/7021 I am currently running: uname -a Linux huitzilopochtli 4.14.0-3+reiser4.0.2-amd64 #1 SMP Debian 4.14.17-1+reiser4.0.2 (2018-01-16) x86_64 GNU/Linux There are no Reiser4 related apparent operating issues as in this environment I have built GCC7 and VirtualBox 5.1.32 -- the latest that fully supports reiser4 format/create/installation as done with Metztli-Reiser4 Debian Stretch AMD64 netboot in virtual machines creation and software 'cold boots': < https://metztli.it/blog/index.php/ixiptli/?disp=posts#item_143 > < https://metztli.it/blog/index.php/ixiptli > No virtual or physical data loss but after Linux 4.14.x reiser4-patched kernels I am experiencing more frequent cold boot kernel hangs in physical hardware (i.e., laptop scenarios) -- until finally kernel boots appropriately into userland XDM. [2] I do not know if it is due to Zstd not appropriately being loaded initially for my particular transparent compression ~ 1.2Tb reiser4 SFRN 4.0.2 partition daily development machine. For long running instances (including those with transparent compression) -- as in cloud and or remote hosting instances the issue is, of course, less prevalent as I only reboot kernels sporadically. Just wondering if [1] might have any relevance to [2] ? Of course, FYI, Ed. Best professional Regards. P.S. I will provide more detailed information as I am able to capture it from booting kernel. -- Jose R R http://metztli.it --------------------------------------------------------------------------------------------- Download Metztli Reiser4: Debian Stretch w/ Linux 4.14 AMD64 --------------------------------------------------------------------------------------------- feats ZSTD compression https://sf.net/projects/metztli-reiser4/ -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
