Christoph Pleger:
> Did that, but I really had to hurry up to get ready before my aufs root
> filesystem was completely flooded with log messages, though it was 8 GB
> size. I am sending the log in compressed format, because uncompressed,
> the file size is about 1.6 GB. I even had to split the compressed file
> into two parts, because our outgoing SMTP host does not accept such big
> messages.
Thank you.
In the log, at the very early stage line 894, aufs produces BUG msg.
892 8.431507] aufs 4.19.17+-20190211
893 8.462386] ------------[ cut here ]------------
894 8.463000] kernel BUG at
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/finfo.c:114!
896 8.464324] CPU: 4 PID: 847 Comm: mkdir Tainted: G OE
4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
898 8.465692] RIP: 0010:au_finfo_fin+0x59/0x60 [aufs]
:::
911 8.475098] Call Trace:
912 8.475796] aufs_release_dir+0x105/0x130 [aufs]
913 8.476495] __fput+0xac/0x1e0
914 8.477193] task_work_run+0x8a/0xb0
915 8.477889] exit_to_usermode_loop+0xeb/0xf0
916 8.478580] do_syscall_64+0x10d/0x110
917 8.479270] entry_SYSCALL_64_after_hwframe+0x44/0xa9
918 8.479948] RIP: 0033:0x7f51d3966b54
It happened when mkdir[847] issues exit(2). At exitting, all opened
file descriptors are closed by kernel and aufs_release_dir() is called.
By enabling CONFIG_AUFS_DEBUG, aufs checks the state of the internal
lock and found it is still locked which sould not happen. I don't think
it sane. I am really doubtful "Is it really correctly built?"
Once the BUG msg line appears, I am not sure how much your system is
reliable afterwards.
Now it seems the suspicious things lay far before man(1) command.
- debian kernel
it may apply some unknown patch which affect the behaviour of aufs.
the easiest way to confirm this will be to use vanilla kernel.
- dkms aufs
although I don't know much about DKMS, what does
"/var/lib/dkms/aufs/4.19+20190211/" mean? why isn't it
"4.19.{17,63}+20190211"? is it really the correct version?
In other words, make it sure to use the correct version and build them
correctly.
Finally I'd suggest you to try the combination of plain linux-v4.19.67
plus aufs patches, and vanilla aufs4.19.63+, build it yourself. README
file in aufs release may help you I hope.
Such huge log file must be heavy for you. Of course me too.
It is better to set 1 to sys/module/aufs/parameters/debug just before
you run man(1), and just after man, set 0 in order to stop the debug
log.
J. R. Okajima
