-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using backslashes in path, directory creation fails with "No such file or directory" #438
Comments
Kindly paste your 'mkdir -p' command here, it will help us root-cause the issue. |
|
What is your expectation. As you have mentioned 1.1.1 converts '\' to '/' then 'd\a' is no-longer a directory name, rather it represents 'd' as directory and 'a' as sub-directory. You want to create a directory 'd\a' or 'a' as sub-directory. Current implementation is creating the sub-directory structure. Only problem may be the error throwing part, which I will investigate. |
Also in linux the same mkdir creates a directory with name 'd\a' and not a sub-directory structure. |
As per the Azure blob naming documentation: https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata it is a good practice to avoid backslashes. /a /a.txt /a/b /a/b.txt You can take advantage of the delimiter character when enumerating blobs. |
Blobfuse will now replace '\' with '/' and file/directories will be created accordingly. Bug fix is checked in, will be part of next release. |
Which version of the blobfuse was used?
1.2.3, 1.2.4
Which OS (please include version) are you using?
Ubuntu 16.04 (kernel 4.15.0), Ubuntu 20.04 (kernel 5.4.0)
What problem was encountered?
When attempting to create a directory using
mkdir -p
and a path that has backslashes, directory creation fails with "No such file or directory". Linux does handle this correctly if creating in a directory not backed by blobfuse.Have you found a mitigation/solution?
Downgrade to 1.1.1 (it handles this correctly), or convert everything to forward slashes.
By default, blobfuse logs errors to syslog. If this is relevant, is there anything in the syslog that might be helpful?
Unfortunately this was encountered in a docker container without a syslog daemon.
If relevant, please share your mount command.
The text was updated successfully, but these errors were encountered: