Closed zaibon closed 4 years ago
Found a bug report that seems to be related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407
I start to wonder if the problem doesn't come from the flist I was using to test. I tried to reproduce using other flists and I cannot make it fail anymore.
I found this issue while working on https://github.com/threefoldtech/zos/issues/793
It seems when we mount 0-fs on the same backend directory after a node reboot. The second time the overlayfs is corrupted and returns IO errors.
To reproduce:
The same scenario doesn't give any error when tested on my laptop running arch with Linux 5.6.13-arch1-1
Here are some error from dmesg: https://gist.github.com/zaibon/7c89c908069005eac9b72afdafed7617
Like shown below, the read-only and read-write layer seems to be healthy. Only the mountpoint of the overlayfs gives issue.