[Gluster-users] Question to utime feature for release 4.1.0

Discussion:

David Spisla

2018-08-15 10:21:19 UTC

Dear Gluster Community,
in the Chapter "Standalone" point 3 of the release notes for 4.1.0
https://docs.gluster.org/en/latest/release-notes/4.1.0/

there 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?

Regards
David Spisla

Kotresh Hiremath Ravishankar

2018-08-15 18:15:17 UTC

Permalink

Hi David,

The feature is to provide consistent time attributes (atime, ctime, mtime)
across replica set.
The feature is enabled with following two options.

gluster vol set <vol> utime on
gluster vol set <vol> ctime on

The features currently does not honour mount options related time
attributes such as 'noatime'.
So even though the volume is mounted with noatime, it will still update
atime with this feature
enabled.

Thanks,
Kotresh HR

Post by David Spisla
Dear Gluster Community,
in the Chapter "Standalone" point 3 of the release notes for 4.1.0
https://docs.gluster.org/en/latest/release-notes/4.1.0/
there 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?
Regards
David Spisla
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

--
Thanks and Regards,
Kotresh H R

Jim Kinney

2018-08-15 20:23:00 UTC

Permalink

Is this 'or' of atime settings also in 3.10/3.12 versions?

If it's set off in gluster but on in mount will atime be updated?

Post by Kotresh Hiremath Ravishankar
Hi David,
The feature is to provide consistent time attributes (atime, ctime, mtime)
across replica set.
The feature is enabled with following two options.
gluster vol set <vol> utime on
gluster vol set <vol> ctime on
The features currently does not honour mount options related time
attributes such as 'noatime'.
So even though the volume is mounted with noatime, it will still update
atime with this feature
enabled.
Thanks,
Kotresh HR

options

Post by David Spisla
are not allowed if I want to mount a volume? There is

"noatime,realatime"

Post by David Spisla
mentioned. Does the second mean "relatime". I never heard of

"realatime".

Post by David Spisla
Is there any recommendation for the mount options?
Regards
David Spisla
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

--
Thanks and Regards,
Kotresh H R

--
Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.

David Spisla

2018-08-16 06:35:11 UTC

Permalink

AFAIK this feature is not available in 3.X series. It was introduced in
4.1.0
If this feature is off in gluster your atime will be updated according to
your mount options. There are several options availabe. Look at $ man mount.
I found this options: noatime, atime, nostrictatime, strictatime,
norelatime, relatime, nolazytime, lazytime

But at the moment I don't know what klind of mount options should be set if
the feature utime is working

Regards
David

Post by Jim Kinney
Is this 'or' of atime settings also in 3.10/3.12 versions?
If it's set off in gluster but on in mount will atime be updated?
On August 15, 2018 2:15:17 PM EDT, Kotresh Hiremath Ravishankar <

Post by Kotresh Hiremath Ravishankar
Hi David,
The feature is to provide consistent time attributes (atime, ctime,
mtime) across replica set.
The feature is enabled with following two options.
gluster vol set <vol> utime on
gluster vol set <vol> ctime on
The features currently does not honour mount options related time
attributes such as 'noatime'.
So even though the volume is mounted with noatime, it will still update
atime with this feature
enabled.
Thanks,
Kotresh HR

--
Sent from my Android device with K-9 Mail. All tyopes are thumb related
and reflect authenticity.

David Spisla

2018-08-16 06:58:58 UTC

Permalink

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
set
the 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: test1Type: ReplicateVolume ID:
e6576010-d9e3-4a98-bcfd-d4a452e92198Status: StartedSnapshot Count: 0Number
of Bricks: 1 x 4 = 4Transport-type: tcpBricks:Brick1:
davids-c1-n1:/gluster/brick1/glusterbrickBrick2:
davids-c1-n2:/gluster/brick1/glusterbrickBrick3:
davids-c1-n3:/gluster/brick1/glusterbrickBrick4:
davids-c1-n4:/gluster/brick1/glusterbrickOptions
Reconfigured:storage.ctime: onfeatures.utime:
onperformance.client-io-threads: offnfs.disable:
ontransport.address-family: inetuser.smb: disablefeatures.read-only:
offfeatures.worm: offfeatures.worm-file-level: onfeatures.retention-mode:
relaxnetwork.ping-timeout: 10features.cache-invalidation:
onfeatures.cache-invalidation-timeout: 600performance.nl-cache:
onperformance.nl-cache-timeout: 600client.event-threads:
32server.event-threads: 32cluster.lookup-optimize:
onperformance.stat-prefetch: onperformance.cache-invalidation:
onperformance.md-cache-timeout: 600performance.cache-samba-metadata:
onperformance.cache-ima-xattrs: onperformance.io-thread-count:
64cluster.use-compound-fops: onperformance.cache-size:
512MBperformance.cache-refresh-timeout: 10performance.read-ahead:
offperformance.write-behind-window-size: 4MBperformance.write-behind:
onstorage.build-pgfid: onauth.ssl-allow: *client.ssl: offserver.ssl:
offchangelog.changelog: onfeatures.bitrot: onfeatures.scrub:
Activefeatures.scrub-freq: dailycluster.enable-shared-storage: enable*

Regards
David Spisla

Am Mi., 15. Aug. 2018 um 20:15 Uhr schrieb Kotresh Hiremath Ravishankar <

--
Thanks and Regards,
Kotresh H R

Kotresh Hiremath Ravishankar

2018-08-16 07:02:57 UTC

Permalink

Hi David,

With this feature enabled, the consistent time attributes (mtime, ctime,
atime) will be
maintained in xattr on the file. With this feature enabled, gluster will
not used time
attributes from backend. It will be served from xattr of that file which
will be
consistent across replica set.

Thanks,
Kotresh

Post by David Spisla
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 set
the 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
e6576010-d9e3-4a98-bcfd-d4a452e92198Status: StartedSnapshot Count: 0Number
davids-c1-n4:/gluster/brick1/glusterbrickOptions
Activefeatures.scrub-freq: dailycluster.enable-shared-storage: enable*
Regards
David Spisla
Am Mi., 15. Aug. 2018 um 20:15 Uhr schrieb Kotresh Hiremath Ravishankar <

Post by Kotresh Hiremath Ravishankar
Hi David,
The feature is to provide consistent time attributes (atime, ctime,
mtime) across replica set.
The feature is enabled with following two options.
gluster vol set <vol> utime on
gluster vol set <vol> ctime on
The features currently does not honour mount options related time
attributes such as 'noatime'.
So even though the volume is mounted with noatime, it will still update
atime with this feature
enabled.
Thanks,
Kotresh HR

--
Thanks and Regards,
Kotresh H R

David Spisla

2018-08-16 07:56:02 UTC

Permalink

Thank you for the clarification.

Am Do., 16. Aug. 2018 um 09:02 Uhr schrieb Kotresh Hiremath Ravishankar <

Post by Kotresh Hiremath Ravishankar
Hi David,
With this feature enabled, the consistent time attributes (mtime, ctime,
atime) will be
maintained in xattr on the file. With this feature enabled, gluster will
not used time
attributes from backend. It will be served from xattr of that file which
will be
consistent across replica set.
Thanks,
Kotresh

Post by Kotresh Hiremath Ravishankar
Hi David,
The feature is to provide consistent time attributes (atime, ctime,
mtime) across replica set.
The feature is enabled with following two options.
gluster vol set <vol> utime on
gluster vol set <vol> ctime on
The features currently does not honour mount options related time
attributes such as 'noatime'.
So even though the volume is mounted with noatime, it will still update
atime with this feature
enabled.
Thanks,
Kotresh HR

--
Thanks and Regards,
Kotresh H R