mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #169] Problem with encfs #99
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#99
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 @delx on GitHub (Apr 16, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/169
I executed s3fs-fuse (latest master) with the following command:
Then on top of s3fs-fuse I mounted a encfs file system:
There is a file with path
/mnt/encfs/test/filethat has 30 KB. I executed the following command:After this command the file still has 30 KB although it should only have 8 bytes!
The output of s3fs-fuse:
The output of encfs (with "operation not supported" errors):
If you want me to test something, just leave me a message.
@gaul commented on GitHub (Apr 16, 2015):
s3fs does not support extended attributes that encfs needs -- we could add support via S3 user metadata.
@delx commented on GitHub (Apr 16, 2015):
@andrewgaul: Would it be possible to implement dummy functions for the extended attributes in order to make encfs work?
@ggtakec commented on GitHub (Apr 18, 2015):
@delx It is correct that @andrewgaul said.
The extended attributes caold be realized by s3fs supports setxattr, getxattr and listxattr of FUSE interface.
Probably, s3fs will make original HTTP header(example: "x-amz-meta-xatt") for each object which is set extended attributes.
@ggtakec commented on GitHub (Apr 20, 2015):
I created new branch "xattr" which supported extended attributes FUSE api.
Please try to use and test xattr branch codes.
Thanks in advance for your assistance.
@delx commented on GitHub (Apr 20, 2015):
@ggtakec: I tested your new branch. The error can be reproduced exactly as above.
This time I used the following command:
The output of encfs (with -v flag) while executing the echo command:
The output of s3fs while executing the echo command:
Thank you very much in advance for your help!
@ggtakec commented on GitHub (Apr 21, 2015):
After I checked your log, it did not have log which was calling s3fs_setxattr function.
I was hoping that s3fs_setxattr function is called when s3fs made the file.
Because when I tested s3fs with attar and setfattr command, this function was called.
So s3fs_getxattr function was called, your fuse was compiled with HAVE_SETXATTR flag.
Thus I think fuse does not have a problem for this issue.
And I updated codes on xattr branch which are fixed some problem.
If you can, please try to check new codes(xattr branch).
Thanks in advance for your help.
@delx commented on GitHub (Apr 21, 2015):
I tested your xattr branch with the latest commit
aac92bd. The echo command still does not change the file. Here are the new logfiles:s3fs
encfs
Do you need assistance to reproduce the bug?
Or access to a server where the bug can be reproduced easily?
Just tell me if I can help in any way.
Thanks for your efforts.
@ggtakec commented on GitHub (Apr 28, 2015):
@delx I have not been solved this issue yet.
But s3fs puts following log by accessing from encfs:
So I think we should need to know who(how to) set this extended attribute for the object(file).
I keep to work for solving this issue, please wait a while.
(And please watch #166 too.)
@ggtakec commented on GitHub (May 10, 2015):
@delx I'm sory for replying late.
I tried to reproduce this problem in the first step.
I have prepared the following environment(ubuntu on EC2).
Use both master branch and xattr branch.
version 1.7.4 installed by apt
Then I tried to check both master and xattr branch s3fs.
Following command for mounting.
Next, I done following.
Consequently, I think the cause of this problem is not that s3fs does not support the extended attribute interface.
At first, I was mistaken for the cause of this problem is it.
But in my latest environment(ubuntu), encfs + s3fs are operating without problems now.
I think that the cause of this problem is another factor, however I do not know the cause at the moment.
Regards,
@ggtakec commented on GitHub (Jun 20, 2015):
#199 merged, master branch supports extended attributes.
I closed this issue, if you find a problem, please reopen this issue or post new issue.
Regards,