ewah
ewah
cache-check (interval) is only used in the case of check_cache_size() to determine whether items need to be purged from the cache to free up disk space or memory. so this...
i've also tried ``` B> rm file.txt B> cat file.txt ENOENT .> s3cmd put /tmp/junk s3://bucket/dir/file.txt B> cat file.txt ``` and appears to come back w/ the contents of /tmp/junk
essentially s3cmd will do the same function as dropping something w/ the aws console. the log in on the info level will not track what files have been added/removed from...
does the file show up on subsequent restarts of yas3fs?
I just merged a pull request in (slated to be 2.3.0). I didn't do anything directly w/ your issue, but would you run your tests again with that to confirm...
Hi I guess that would be me.
``` - self.yas3fs_xattrs = [ 'yas3fs.bucket', 'yas3fs.key', 'yas3fs.URL', 'ya - 'yas3fs.expiration' ] + self.yas3fs_xattrs = [ 'user.yas3fs.bucket', 'user.yas3fs.key', 'user.y + 'user.yas3fs.expiration' ] ``` to solve the listxattr not returning anything?
w/ #74
Have you tried it w/ the --recheck-s3 option on? That option when encountering an ENOENT or and error will recheck S3 for the file, this may fix your issue.
would you check your condition off the ewah/yas3fs branch... i may have inadvertently fixed it w/ the way we are locking. i've tried it w node1: cp ~/.cshrc /mnt/yas3fs/a.txt node1:...