Hey, could you please provide the additional information the upstream developer requests for in the README, then I will forward it to upstream:
5. Contact ---------------------------------------- When you have any problems or strange behaviour in aufs, please let me know with: - /proc/mounts (instead of the output of mount(8)) - /sys/module/aufs/* - /sys/fs/aufs/* (if you have them) - /debug/aufs/* (if you have them) - linux kernel version if your kernel is not plain, for example modified by distributor, the url where i can download its source is necessary too. - aufs version which was printed at loading the module or booting the system, instead of the date you downloaded. - configuration (define/undefine CONFIG_AUFS_xxx) - kernel configuration or /proc/config.gz (if you have it) - behaviour which you think to be incorrect - actual operation, reproducible one is better - mailto: aufs-users at lists.sourceforge.net Best regards, Jan Am 24.01.2018 um 09:50 schrieb intrigeri: > Indeed! > > I've just reproduced this in an up-to-date sid VM where /tmp is on > the ext4 root filesystem. I've purged and reinstalled aufs-dkms to > make sure I had a fresh copy built with the current compiler etc. > from sid. I've also tried with AppArmor disabled, same result. > > anonym can reproduce it too, and the bug can be reproduced > consistently while booting Tails 3.5 (for testing purposes, one > can grab the ISO from > http://dl.amnesia.boum.org/tails/stable/tails-amd64-3.5/ and boot > it in a VM). > > Perhaps we should take it upstream and hope the debug trace will > ring a bell for them?