You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is quite possible to make objects like this (in s3 or swift)
test_file
test_file/1
However when rsync tries to copy them it is confused about the status of "test_file" whether it should be a file or a directory, and gives errors like this
2014/11/27 13:17:54 test_file/1: Failed to copy: mkdir /tmp/test/test_file: not a directory
Not sure how to fix this as it isn't possible to represent this in a filesystem. syncing a bucket/container like this to s3/swift does work fine though.
This can be caused by the s3fs program which creates a file object "dir/" for every directory - presumably to store permissions, eg
currently when context is canceled, and if in Serve() based Accept()
loop, the process is shut down without waiting for the client
connections to gracefully exit.
not sure if graceful handling would be worth the effort.
It is quite possible to make objects like this (in s3 or swift)
However when rsync tries to copy them it is confused about the status of "test_file" whether it should be a file or a directory, and gives errors like this
Not sure how to fix this as it isn't possible to represent this in a filesystem. syncing a bucket/container like this to s3/swift does work fine though.
This can be caused by the s3fs program which creates a file object "dir/" for every directory - presumably to store permissions, eg
Could just ignore zero length files with trailing / ?
The text was updated successfully, but these errors were encountered: