Issue 247 in s3fs: Mount Broken after CURLE_OPERATION_TIMEDOUT
s3...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 247 by arnaud.c...@gmail.com: Mount Broken after
CURLE_OPERATION_TIMEDOUT
http://code.google.com/p/s3fs/issues/detail?id=247
Detailed description of observed behavior:
Good morning,
We have an EC2 instance with a S3 mounted with S3FS with the following
parameter.
-o allow_other
This server is running PHP CLI script as cron job.
The differents scripts are just browsing few folder, read, rename and write
few files on mounted folder (not really heavy task)
Most of the time those script are running well. But after few days the same
script fails sudenly (with syslog s3fs: ### CURLE_OPERATION_TIMEDOUT),
right after this error, the mount folder is broken. We have to force the
umount and mount the folder back.
Do you have a clue why CURLE_OPERATION_TIMEDOUT could break the mounted
folder?
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)?
Thanks for your help
===================================================================
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.61
Version of fuse being used (pkg-config --modversion fuse):2.8.4
System information (uname -a): #27-Ubuntu SMP Wed Mar 2 22:54:48 UTC 2011
i686 GNU/Linux
Distro (cat /etc/issue): Ubuntu 10.04.3 LTS
s3fs command line used (if applicable):
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog):
Jan 11 23:24:12 ip-10-235-23-1 s3fs: ### CURLE_OPERATION_TIMEDOUT
Jan 11 23:24:14 ip-10-235-23-1 s3fs: ###retrying...
s3...@googlecode.com
Status: Done
Comment #1 on issue 247 by ggta...@gmail.com: Mount Broken after
CURLE_OPERATION_TIMEDOUT
http://code.google.com/p/s3fs/issues/detail?id=247
Hi
Does this problem still continue?
I think this issue seems trouble about S3.
And we are so sorry for not solving this issue for over one year.
If you can, please use latest version and try to check it.
I am closing this issue, but if you have this trouble now please let me
know and open new issue.
Regards,
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings