Open keybrdist opened 6 years ago
Exact same issue here with DigitalOcean Spaces.
goofys -v
:
goofys version 0.19.0-943e017724ea820eb4185419ef3c41d6f921a324
uname -a
:
Linux nyc3-01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
TLDR seems to be related to error SignatureDoesNotMatch
, which is also in my syslog:
2018/07/21 19:25:24.977681 s3.DEBUG DEBUG: Validate Response s3/PutObject failed, not retrying, error SignatureDoesNotMatch: status code: 403, request id: tx000000000000002e0641c-005b53c0e4-a3d017-nyc3a, host id: 2018/07/21 19:25:24.977880 catfs.INFO 2018-07-21 19:25:24 ERROR - !flush(src) = Permission denied (os error 13) 2018/07/21 19:25:24.979882 catfs.INFO 2018-07-21 19:25:24 ERROR - <-- !flush 0000000000000001 = Permission denied (os error 13)
Edit: no clue why, but I installed s3tools 2.x, configured it for Digital Ocean spaces, and then goofys works as expected.
I'm having this issue as well. Even when touching as root user.
Exact same issue here with DigitalOcean Spaces.
goofys -v
:goofys version 0.19.0-943e017724ea820eb4185419ef3c41d6f921a324
uname -a
:Linux nyc3-01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
TLDR seems to be related to
error SignatureDoesNotMatch
, which is also in my syslog:2018/07/21 19:25:24.977681 s3.DEBUG DEBUG: Validate Response s3/PutObject failed, not retrying, error SignatureDoesNotMatch: status code: 403, request id: tx000000000000002e0641c-005b53c0e4-a3d017-nyc3a, host id: 2018/07/21 19:25:24.977880 catfs.INFO 2018-07-21 19:25:24 ERROR - !flush(src) = Permission denied (os error 13) 2018/07/21 19:25:24.979882 catfs.INFO 2018-07-21 19:25:24 ERROR - <-- !flush 0000000000000001 = Permission denied (os error 13)
Edit: no clue why, but I installed s3tools 2.x, configured it for Digital Ocean spaces, and then goofys works as expected.
Hi, can You please explain it more detail about installing s3tools and goofys works? I've got this issue and installed s3tools but still not working.. thank you
just found the problem:
change this option --endpoint http://ams3.digitaloceanspaces.com/
to
--endpoint ams3.digitaloceanspaces.com
and it works well
I'm having the same issue running on Wasabi. I tried all of the suggested methods above and nothing's fixing the problem. Whenever I try to create a file, it returns the error cp: failed to close '{file}: No such file or directory
, and then when I try a second time it returns cp: cannot create regular file '{file}': File exists
, however the file does not exist when I ls the directory.
I tried fixing the endpoint URL, installing s3tools 2.x, etc and nothing seems to actually resolve it.
Crazy, @bintt's advice fixed my problem as well. Looks like some quirky behaviour of goofys. It should probably normalize the endpoint parameter.
I've mounted using the following and I can read files but cannot write. My key has proper permissions and works using s3fs. I also tried adding -o use_path_request_style (--use-path-request is invalid)
goofys v0.19.0
goofys --debug_fuse --debug_s3 --endpoint http://ams3.digitaloceanspaces.com/ --file-mode=0777 --dir-mode=0777 --profile data data /mnt/users
Any attempt to writes to /mnt/users fails:
touch users/testsasdfasdf.txt
touch: failed to close 'users/testsasdfasdf.txt': Permission denied
The syslog