Re: [Gluster-users] XFS, WORM and the Year-2038 Problem

2019-04-29 Thread David Spisla
Hello Gluster Community, here is a possible explanation why the LastAccess date is changed at brick level resp why can XFS ever have a date of e.g. Can store 2070 in an INT32 field: It's amazing that you can set timestamps well above 2038 for the atime and these are also displayed via the usual

Re: [Gluster-users] XFS, WORM and the Year-2038 Problem

2019-04-15 Thread Amar Tumballi Suryanarayan
On Mon, Apr 15, 2019 at 2:40 PM David Spisla wrote: > Hi folks, > I tried out default retention periods e.g. to set the Retention date to > 2071. When I did the WORMing, everything seems to be OK. From FUSE and also > at Brick-Level, the retention was set to 2071 on all nodes.Additionally I >

[Gluster-users] XFS, WORM and the Year-2038 Problem

2019-04-15 Thread David Spisla
Hi folks, I tried out default retention periods e.g. to set the Retention date to 2071. When I did the WORMing, everything seems to be OK. From FUSE and also at Brick-Level, the retention was set to 2071 on all nodes.Additionally I enabled the storage.ctime option, so that the timestamps are