This error disappears after installing 4.13.1, but other problems have arised when unmounting some kind of filesystems. Maybe it was not an overlayfs error. On Fri, Sep 8, 2017 at 9:31 PM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: > On Fri, Sep 8, 2017 at 6:55 PM, Jordi Pujol <jordipujolp@xxxxxxxxx> wrote: >> >> On Fri, 8 Sep 2017 17:20:50 +0300 >> Amir Goldstein <amir73il@xxxxxxxxx> wrote: >> >> > This sounds a lot like >> > https://bugzilla.redhat.com/show_bug.cgi?id=1213602 A long standing >> > issue with a simple workaround (see link above) >> > >> the problem also arises when executing >> touch /var/lib/dpkg/* >> before upgrading, >> maybe the issue is not the same, >> >> The first time replacing the file does OK, but consecutive replacements fail. >> Maybe an unitialized variable internally in overlayfs. >> > Is the problem you are hitting new to v4.13? >> Yes, this problem is new, >> therefore my computer continues running 4.12.11 by now. >> > I see. Do you see any overlay fs warning in dmesg? > Please send them as well. > I did not understand if this happens during file create > rename delete if you understand the scenario and can send a simple > reproducer script that would be great. > > Thanks, > Amir. -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
