On Tue, 2017-03-28 at 17:50 +0200, Nicolai Hähnle wrote:
> The crossing happens because I'm running it inside a docker container,
> > which uses internally an overlayfs. This means that some of those
> > subdirectories can be in one mountpoint and others in other mountpoint.
> > This seems to be
On 28.03.2017 17:32, Juan A. Suarez Romero wrote:
On Tue, 2017-03-28 at 16:53 +0200, Nicolai Hähnle wrote:
On 25.03.2017 01:40, Juan A. Suarez Romero wrote:
When using an overlayfs system (like a Docker container), rmrf_local()
fails because part of the files to be removed are in different moun
On Tue, 2017-03-28 at 16:53 +0200, Nicolai Hähnle wrote:
> On 25.03.2017 01:40, Juan A. Suarez Romero wrote:
> > When using an overlayfs system (like a Docker container), rmrf_local()
> > fails because part of the files to be removed are in different mount
> > points (layouts). And thus cache-test
On 25.03.2017 01:40, Juan A. Suarez Romero wrote:
When using an overlayfs system (like a Docker container), rmrf_local()
fails because part of the files to be removed are in different mount
points (layouts). And thus cache-test fails.
Can you explain a bit more how this can happen? I thought th
When using an overlayfs system (like a Docker container), rmrf_local()
fails because part of the files to be removed are in different mount
points (layouts). And thus cache-test fails.
Letting crossing mount points is not a big problem, specially because
this is just for a test, not to be used in
