enable_content_md5 Input/output error

[GoogleCodeExporter]

Detailed description of observed behavior:

If I set the option enable_content_md5 in my fstab, I cannot write anymore on 
my mounted point.

What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?

Just mount using option enable_content_md5, then try to write any new file:
- /home # mount backups/
- /home # cd backups/
- /home/backups # ll
drwxrwxrwx 1 root root    0 Jan  1  1970 ./
drwxr-x--x 8 root root 4096 Jan  9 10:54 ../
- cp /tmp/test.sql ./
cp: closing './test.sql': Input/output error
- /home/backups # ll
drwxrwxrwx 1 root root    0 Jan  1  1970 ./
drwxr-x--x 8 root root 4096 Jan  9 10:54 ../
-rw-r--r-- 1 root root    0 Jan  9 11:14 test.sql

===================================================================
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): 1.74

Version of fuse being used (pkg-config --modversion fuse): 2.9.0

System information (uname -a): Linux ip-xxx-xxx-xxx-xxx 3.8.0-19-generic 
#30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Distro (cat /etc/issue): Ubuntu 13.04 \n \l

s3fs command line used (if applicable):

/etc/fstab entry (if applicable): s3fs#backups /home/backups  fuse    
_netdev,allow_other,enable_content_md5 0   0

s3fs syslog messages (grep s3fs /var/log/syslog):
Jan  9 11:13:02 ip-10-35-148-57 s3fs: init $Rev: 497 $

Original issue reported on code.google.com by nicolas....@gmail.com on 9 Jan 2014 at 11:17

[GoogleCodeExporter]

Hi,

I'm sorry for replying.

This problem is a bug in codes.
This is fixed on Github(https://github.com/s3fs-fuse/s3fs-fuse/pull/19), fixed 
into master branch.

Please use latest master branch on Github.

I closed this issue, but if you found another bugs, please let me know on 
github or googlecode.

Thanks in advance.

Original comment by ggta...@gmail.com on 3 Mar 2014 at 4:27

• Changed state: Fixed