Closed jobcespedes closed 4 years ago
fuse-overlayfs uses caches to not hit the underlying file system for lookups.
As the native overlay, you should not modify the underlying directories as the result is undefined.
To verify it is a caching issue, you can try to drop the caches with echo 3 > /proc/sys/vm/drop_caches
and see if the mounted directory is reloaded
I am testing
fuse-overalyfs
as an unionfs. I'm coming fromunionfs-fusẹ
. There are some file modifications (online, while mounted) that work inunionfs-fusẹ
but not infuse-overlayfs
. I don't have the knowledge to determine if it is because of a bug, a different functionality or me? I'll be thankful if you help determine what it is. Let me present 3 cases. First, these are the steps to reproduce:Directory layout for cases:
Case 1: delete a file common to both layers
Delete file2 in the upper directory. File2 exists in the lower directory too, but with different value.
Expected result in target mount point
Since file2 is deleted in the upper directory and not from the target mount point, I expected to see file2 in the target mount point but with content from the lower directory.
Result in target mount point
File2 is listed but "No such file or directory" is shown also
Case 2: add new file in the lower layer
Create a new file in the lower layer. The file does not exist in the upper layer.
Expected result
I expected to see a new file4 with content from the lower layer
Result
There is no file4 in the target mount point
Case 3: modified file in the lower layer
Modified the content of file1 in the lower layer. File1 does not exist in the upper layer.
Expected result
New content from file1 in lower layer
Result
Old content
Info