amnguye
commented
5 years ago 1. Mounted directory doesn't expose existing blobs
This is an interesting issue, so when you already have blobs and you see them through the portal. And then when you mount blobfuse, in the directory you don't see the blobs in the directory container?
2. New blobs (e.g. echo 1 > foo) are created under an empty-named directory on the server (i.e. /container//foo)
I'm confused. So it makes an empty folder called foo? But your blob is called foo. Or is container supposed to be the empty directory
3. Segfaults during umount after some simple file interactions:
So when you attempt to umount your mounted container, then it seg faults? Or you umount and then do some file interactions and that segfaults?
4. Umount requires root permissions
Depending on where your folder is, especially if its mounted at the root, it may need root permissions. Have you made sure to give the user access to the mounted folder and temporary cache directory? (E.g. chown
stewartadam
vibhansa-msft
Which version of the blobfuse was used?
1.0.3
Which OS (please include version) are you using?
Fedora 29
What problem was encountered?
echo 1 > foo) are created under an empty-named directory on the server (i.e./container//foo)Have you found a mitigation/solution?
No
By default, blobfuse logs errors to syslog. If this is relevant, is there anything in the syslog that might be helpful?
dmesg:
syslog, note how for example '/baz' is uploaded to the container instead of 'baz' resulting in a blob path of /container//baz':