Should Gluster use nanoseconds instead of microseconds for [am]time?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/1422074 was opened to support nanoseconds on
Gluster Volumes. Is anyone aware of problems when we do this?

This would help where applications (like backup systems) check for the
difference between timestamps on original (nanosecond precision) and
Gluster Volumes (microseconds rounded down). Because the original would
always be newer than the copy on the Gluster Volume, incremental backups
become full backups again (using 'rsync' and 'cp -u' as examples).

Please leave your conserns or recommendation in the bug or reply this
this email.

Thanks,
Niels

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux