fuse mount - metadata stale for brief period after upload

[tobiasgrosser]

When running the following command, I get an unexpected output:

cp ~/File100BMbyte  . && ls -l File100MByte
-rwxrwxr-x 1 grosser grosser 0 Aug  6 08:37 File100MByte

The filesize is not updated even thought the copy completed. Only if I put a 'sleep 5' between the copy and the ls, the filesize is printed reliably.

This is a problem, as 'btrbk' uses the filesize to check if the backup creation succeeded. When backing up to acd_cli this check always fails, which means backing up with btrbk is not possible
without hacking a 'sleep 5' into btrbk.

[ThomasWaldmann]

Hmm, the fuse process should know the right file metadata, so it should never return inconsistent data.

[tobiasgrosser]

That's what I believe. Add this is apparently not the case, it seems to
be some kind of bug. Did you try to reproduce this behavior?

On Wed, Aug 10, 2016, at 12:32 PM, TW wrote:

Hmm, the fuse process should know the right file metadata, so it should
never return inconsistent data.

---

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#373 (comment)

[ThomasWaldmann]

I was just processing an issue report from a borgbackup user (see https://github.com/borgbackup/borg ) - looking here for similar issues with acd_cli fuse consistency. I do not personally use acd_cli.