Thank you for the clarification.
Am Do., 16. Aug. 2018 um 09:02 Uhr schrieb Kotresh Hiremath Ravishankar <khiremat@xxxxxxxxxx>:
Thanks,Hi David,With this feature enabled, the consistent time attributes (mtime, ctime, atime) will bemaintained in xattr on the file. With this feature enabled, gluster will not used timeattributes from backend. It will be served from xattr of that file which will beconsistent across replica set.
KotreshOn Thu, Aug 16, 2018 at 12:28 PM, David Spisla <spisla80@xxxxxxxxx> wrote:Hello Kotresh,its no problem for me that the atime will be updated, importat is a consistent mtime and ctime on the bricks of my replica set.I have turned on both options you mentioned. After that I created a file on my FUSE mount (mounted with noatime). But on all my bricks of the replica setthe mtime and ctime is not consistent. What about the brick mount? Is there a special mount option?I have a four node cluster and on each node there is only one brick. See below all my volume options:Volume Name: test1
Type: Replicate
Volume ID: e6576010-d9e3-4a98-bcfd-d4a452e92198
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 4 = 4
Transport-type: tcp
Bricks:
Brick1: davids-c1-n1:/gluster/brick1/glusterbrick
Brick2: davids-c1-n2:/gluster/brick1/glusterbrick
Brick3: davids-c1-n3:/gluster/brick1/glusterbrick
Brick4: davids-c1-n4:/gluster/brick1/glusterbrick
Options Reconfigured:
storage.ctime: on
features.utime: on
performance.client-io-threads: off
nfs.disable: on
transport.address-family: inet
user.smb: disable
features.read-only: off
features.worm: off
features.worm-file-level: on
features.retention-mode: relax
network.ping-timeout: 10
features.cache-invalidation: on
features.cache-invalidation-timeout: 600
performance.nl-cache: on
performance.nl-cache-timeout: 600
client.event-threads: 32
server.event-threads: 32
cluster.lookup-optimize: on
performance.stat-prefetch: on
performance.cache-invalidation: on
performance.md-cache-timeout: 600
performance.cache-samba-metadata: on
performance.cache-ima-xattrs: on
performance.io-thread-count: 64
cluster.use-compound-fops: on
performance.cache-size: 512MB
performance.cache-refresh-timeout: 10
performance.read-ahead: off
performance.write-behind-window-size: 4MB
performance.write-behind: on
storage.build-pgfid: on
auth.ssl-allow: *
client.ssl: off
server.ssl: off
changelog.changelog: on
features.bitrot: on
features.scrub: Active
features.scrub-freq: daily
cluster.enable-shared-storage: enableRegardsDavid SpislaAm Mi., 15. Aug. 2018 um 20:15 Uhr schrieb Kotresh Hiremath Ravishankar <khiremat@xxxxxxxxxx>:Kotresh HRThanks,enabled.So even though the volume is mounted with noatime, it will still update atime with this featureThe features currently does not honour mount options related time attributes such as 'noatime'.gluster vol set <vol> ctime ongluster vol set <vol> utime onThe feature is enabled with following two options.Hi David,The feature is to provide consistent time attributes (atime, ctime, mtime) across replica set.On Wed, Aug 15, 2018 at 3:51 PM, David Spisla <spisla80@xxxxxxxxx> wrote:Dear Gluster Community,in the Chapter "Standalone" point 3 of the release notes for 4.1.0there is an introduction to the new utime feature. What kind of options are not allowed if I want to mount a volume? There is "noatime,realatime" mentioned. Does the second mean "relatime". I never heard of "realatime". Is there any recommendation for the mount options?RegardsDavid Spisla
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--Thanks and Regards,Kotresh H R
--Thanks and Regards,Kotresh H R
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
