On Mon, Oct 1, 2018 at 1:29 PM Nigel Banks <Nigel_Banks@xxxxxxxxxx> wrote: > > Thank you Amir, > > I will try the patch you've recommend. It some times takes several days for this issue to arise, so you may not hear back from me for a week or so. On a side note if I were to use AUFS instead of Overlay2 would that potentially avoid this issue? > I don't know the answer to that question, but there is an easy way to find out. The fix patch has a simple reproducer in commit message. Run the same reproducer with AUFS instead of overlayfs and tell me. I can only say that AFAIK all past versions of overlayfs has had this problem with inotify. I can also say that if you have a hardlink in lower layer and you are not using the new overlayfs index feature (docker is not using this feature) then said inotify issue will still happen on that lower hardlink. Thanks, Amir.
