TurboGit/hubicfuse

Only the first 'df' call works properly if cache_statfs_timeout enabled

Opened this issue · 3 comments

romanrm commented

Hello,

If I set cache_statfs_timeout=86400, I get the following behavior (right after mounting):

$ df /mnt/hubic/
Filesystem 1K-blocks Used Available Use% Mounted on
hubicfuse 10737418240 6310055300 4427362940 59% /mnt/hubic

$ df /mnt/hubic/
Filesystem 1K-blocks Used Available Use% Mounted on
hubicfuse 0 0 0 - /mnt/hubic

$ df /mnt/hubic/
Filesystem 1K-blocks Used Available Use% Mounted on
hubicfuse 0 0 0 - /mnt/hubic

(etc)

If I comment out the cache_statfs_timeout setting, then each df call works properly (and as expected takes about 0.5-1 second to execute).

romanrm commented

Also with the cache_statfs_timeout enabled the browsing of Hubic directories feels so much more responsive in the file manager (even though the 'df' information is missing), so it'd be really nice to get this working.

Another note, my mount options: allow_other,entry_timeout=86400,attr_timeout=86400,sync_read,no_splice_write,no_splice_move,no_splice_read,no_remote_lock,no_remote_posix_lock

TurboGit commented

I cannot reproduce on my side (using the same mount options). Which version of hubicfuse are you using?

romanrm commented

Well of course before reporting the bug I ensured I use a version compiled the then-current May 30 git source code. And the issue persists with a version that I just compiled from git right now.