Takeshi Nakatani

I merged PR #2204 from @VVoidV. The cause of this is not yet clear, but it is possible that the bug found in #2204 has an effect. If you can,...

@jsm222 Have you tried the `compat_dir` (and `complement_stat`) options? After v1.91, the default compatibility for folders(objects) created from other s3fs clients has changed. If the directory you can't see was...

@stevenlafl Thanks for some log. I checked your 2'nd log and I have a rough idea of what's going on. At first, s3fs listed file objects and detecting two objects....

If the handle passed to pthread_join is unique, this error should not occur, but there may be a problem somewhere.(I haven't been able to find it yet.) The Stat cache...

@netlore It seems that the combination of ecryptfs and s3fs was not finally resolved in the old issue. I'd like to check, does this error occur not only for large...

@netlore Thank you for your cooperation. If possible during testing, having logs with `dbglevel=info` (and `curldbg`) options may help identify the cause. (However, this option will output a lot of...

@dnlchen Are those folders created from a client other than s3fs? If so, try starting it with `compat_dir`(and maybe `complement_stat`) option.

@dnlchen I had overlooked the following line in your log. I think you are failing to start the s3fs process. ``` Jun 06 16:30:43 host-01 s3fs[29779]: s3fs: could not determine...

@gaul If s3fs can be started, the problem may be caused by modifying the `compat_dir` feature. (However, if you check the first log shown in this issue, s3fs has not...

@iptizer @nobodyme @jacobtolar @gaul #2190 seems to be the same phenomenon.