When FUSE_CAP_WRITEBACK_CACHE is enabled, the kernel is responsible
for updating mtime and ctime when write requests are received. The
updated values are passed to the filesystem with setattr() requests.
However, if the filesystem does not support the full resolution of
the kernel timestamps (nanoseconds), the mtime and ctime values used
by kernel and filesystem will differ (and result in an apparent
change of times after a cache flush).
To prevent this problem, this variable can be used to inform the
kernel about the timestamp granularity supported by the file-system.
The value should be power of 10. The default is 1, i.e. full
nano-second resolution. Filesystems supporting only second resolution
should set this to 1000000000.
When FUSE_CAP_WRITEBACK_CACHE is enabled, the kernel is responsible for updating mtime and ctime when write requests are received. The updated values are passed to the filesystem with setattr() requests. However, if the filesystem does not support the full resolution of the kernel timestamps (nanoseconds), the mtime and ctime values used by kernel and filesystem will differ (and result in an apparent change of times after a cache flush).
To prevent this problem, this variable can be used to inform the kernel about the timestamp granularity supported by the file-system. The value should be power of 10. The default is 1, i.e. full nano-second resolution. Filesystems supporting only second resolution should set this to 1000000000.