mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #561] Operation not permitted issue when using openstack Mitaka version in centos #318
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @janibashamd on GitHub (Apr 10, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/561
I installed s3fs and configured it successfully.
Later i added my local swift container to local mount point. I can't view or create new files in this location.
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Version of s3fs being used (s3fs --version)
V1.80
Version of fuse being used (pkg-config --modversion fuse)
2.9.2
System information (uname -a)
Linux centos 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Distro (cat /etc/issue)
\S Kernel \r on an \m
s3fs command line used (if applicable)
s3fs dhanu /mnt/s3fs -o passwd_file=passwd -o url=http://centos.com:35357/v3 -o endpoint=RegionOne -d -d -f -o f2 -o curldbg
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
Mount was successful and can be seen in mount command..
[root@vda pratap]# mount
s3fs on /mnt/pratap type fuse.s3fs (rw,relatime,user_id=0,group_id=0,allow_other)
Later tied to check files but got below error...
Details about issue
Debug output is as below -
We tried multiple options allow_other, umask ,.... but in vain.... Please check and let me know..
If need anything else just let me know...
@gaul commented on GitHub (Apr 14, 2017):
s3fs works with S3-compatible object stores. Swift uses a different protocol. If you want to use s3fs with Swift, you need to install the swift3 middleware or use a translator like S3Proxy.
@janibashamd commented on GitHub (Apr 17, 2017):
Hai Andrew,
We installed swift3 on swift and then tried s3fs but getting same issue - "Operation not permitted" .
[root@vda ~]# ls /mnt/s3fs
ls: reading directory /mnt/s3fs: Operation not permitted
Debug logs is as below -
[ERR] s3fs.cpp:list_bucket(2516): xmlReadMemory returns with error.
[ERR] s3fs.cpp:s3fs_readdir(2437): list_bucket returns error(-1).
We tried with both v2 and v3 still no go... Please let me know if you need anything..
@gaul commented on GitHub (Apr 20, 2017):
Please include logs with these flags:
-d -f -o curldbg@janibashamd commented on GitHub (Apr 24, 2017):
Hai Andrew,
I have already provided debug logs in above comments, please check and if needed i will provide them again..
@ggtakec commented on GitHub (Apr 30, 2017):
@janibashamd
I think that result of list bucket is not xml but it is json format body.
Thus s3fs failed to parse body as xml, and exited.
Then I think you need to use middleware or translator for xml, as @andrewgaul says.
@janibashamd commented on GitHub (May 5, 2017):
We already tried installing s3 middleware over swift still facing same issues..
@gaul commented on GitHub (Feb 2, 2019):
@janibashamd did you ever resolve this issue? Note that S3 functionality is built into newer versions of Swift which also includes fixes for many compatibility issues.
@janibashamd commented on GitHub (Feb 2, 2019):
Sorry, right now i am not working in swift. So i didn't verify it.
On Sat, Feb 2, 2019, 09:26 Andrew Gaul <notifications@github.com wrote:
@gaul commented on GitHub (Mar 17, 2019):
It appears that you connected to the Swift endpoint and not the S3 endpoint. The request s3fs performs unexpected returns a JSON response and not XML:
Please reopen if you can reproduce these symptoms against the S3 endpoint.