multiple writes to file, followed by 'rename' then more writes result in missing bytes, and orphaned file

[bitsofinfo]

Start w/ a clean mount and clean local cache. Run the command below

The size of the "renamed.txt" file should be 780288. This is not always the case.

It is always reflected in the cache as 780288 but on S3 sometimes it can be short bytes. (short the last write of bytes AFTER the file move).

Other times on S3 you will see the old test_pwc.txt orphaned and still on S3 (but appears gone locally on the cache) as if the 'delete' after the key copy never actually occurred.

dd if=/dev/zero of=/tmp/junk bs=1024 count=254; touch test_pwc2.txt; cat /tmp/junk >> test_pwc2.txt; cat /tmp/junk >> test_pwc2.txt; mv test_pwc2.txt renamed2.txt; cat /tmp/junk >> renamed2.txt

[ewah]

working it out w ewah@1e16925

[ewah]

in ewah/yas3fs(master) s3_busy flag now set, and checked w/ get_locks.

[ewah]

with #72