Closed GoogleCodeExporter closed 8 years ago
Hi,
I chacked this issue with latest version s3fs, It works without problem.
Please use latest version and check this issue with it.
I closed this issue, and if you find a bug please let me know.
Thanks in advance.
Original comment by ggta...@gmail.com
on 23 Aug 2013 at 1:14
I upgraded two of the machines to version 1.72 from the download tab.
The same behavior happens. A simple test file is quickly synched, but new
folders are never shown on the other computer.
Original comment by jeremyvillalobos
on 23 Aug 2013 at 5:05
Hi,
I changed status for this issue.
But I did not reappeared this problem yet.
Please let me know about your command line for running s3fs.
Thans in advance.
Original comment by ggta...@gmail.com
on 23 Aug 2013 at 3:14
To mount the bucket I use
s3fs bucket_name /target/dir -o allow_other -o use_cache=/cache/dir -o retries=5
Original comment by jeremyvillalobos
on 23 Aug 2013 at 7:35
Hi,
Thnaks for your command line.
But I could not reappear this problem, s3fs found the directory/file which is
updated on another machines.
When s3fs lists in the directory, s3fs sends request to S3(bucket list). And
when s3fs looks the file directly, s3fs sends request(head), too.
Thus s3fs always gets correct file list and file attributes(except specified
enable_noobj_cache).
I'm sorry that I do not understand the reason for this problem without
reappearing it.
If you can, please run s3fs with "-f" and foreground.
Then you will get many log on your display, it probably helps us for solving
this issue.
Thanks in advance for your help.
Original comment by ggta...@gmail.com
on 26 Aug 2013 at 7:36
The version that was showing this error was version 1.61. Once I updated to
version 1.73 the error was fixed.
The post where I said I had updated the machines was incorrect because version
1.61 was installed in another path that took PATH precedence.
Original comment by jeremyvillalobos
on 28 Aug 2013 at 12:53
Hi,
Thanks for your reports.
So I closed this issue.
Thanks a lot.
Original comment by ggta...@gmail.com
on 29 Aug 2013 at 6:41
Original issue reported on code.google.com by
jeremyvillalobos
on 23 Aug 2013 at 12:17