Kirill Kolyshkin:
> During my weeks of extensive stress testing of aufs I noticed this bug
> happened twice on one of the servers:
>
> May 31 20:05:42 kirtest dockerd[3912]:
> time="2019-05-31T20:05:42.686603244Z" level=warning msg="auplink flush
> failed: auplink:plink.c:158: proc: No such file or directory\n" error="exit
> status 2" method=Unmount storage-driver=aufs
:::
> I took a look at the source code, and it seems that auplink binary fails to
> open /proc/fs/aufs/plink_maint file for writing. I do not understand why
> this could ever happen.
As you might know, the lifetime of /proc/fs/aufs/plink_maint is
equivalent to aufs module's. Unless you unload aufs module, it must
exists. So I am afraid you hit another bug of procfs', and aufs has
nothing to do essentially. cgroup and namespace may be related to
procfs since docker uses them. But I am not a docker user and know few
things about that.
There may exist a similar workaround as well as the previous problem of
/proc/mounts, ie. try opening /proc/fs/aufs/plink_maint twice or more.
Obviously it is not a good solution, and I don't like it.
Do you think that such workaround is helpful?
J. R. Okajima
