-
Notifications
You must be signed in to change notification settings - Fork 95
Description
This may be related to #232 but I prepared
a ready-to-use test-case, it is attached:
fuse_test.AppImage.gz
After you gunzip it, you'll get the AppImage
file called fuse_test.AppImage.
All it does is mounts the read-only lower
dir and the writable upper dir into the
mount-point. Then it does test -r and
test -w to check if the file is actually
readable and writable. Unfortunately its
not writable, in which case it prints the
failure message and also prints mount | grep fuse
that allows you to inspect the mount params.
In fact, its not like the entire dir is not writable -
it IS writable. You can create new files there.
But the files that come from the lower dir,
are themselves not writable for some unclear
reason.
I also added the --debug option for you.
With that option fuse-overlayfs is started
with -d and you can see the logging.
I also added the --keep option which just
mounts the dirs, prints the mount point
and exits without doing any checks and
without unmounting. This may be needed
if you want to work with the mount-point
by hands.
I hope this test-case will help to narrow
down the problem.