Re: atime with cephfs

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

 



Hi all,
We would need the same feature in our HPC cluster. I guess this is not an unfrequent problem, I was wondering if you guys found an alternative solution.

Best
-- 
Filippo Stenico
Services and Support for Science IT (S3IT)
Office Y11 F 52
University of Zürich
Winterthurerstrasse 190, CH-8057 Zürich (Switzerland)

On Tuesday, 17 December 2019 02:32:35 CET Oliver Freyermuth wrote:
> Am 16.12.19 um 11:43 schrieb Gregory Farnum:
> > Yes, CephFS makes no attempt to maintain atime. If that's something
> > you care about you should make a ticket and a case for why it's
> > important. :)
> 
> Thanks for confirming :-). 
> For those following along and also interested, I created the ticket here:
> https://tracker.ceph.com/issues/43337
> Our use case (probably applicable to many clusters - also described there) is "cleanup", i.e. find data not read since months
> which might be a good candidate for deletion (or maybe, moving to a "colder" place). 
> 
> Cheers and thanks,
> 	Oliver
> 
> > 
> > On Sat, Dec 14, 2019 at 5:42 AM Oliver Freyermuth
> > <freyermuth@xxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> Hi together,
> >>
> >> I had a look at ceph-fuse code and if I read it correctly, it does indeed not seem to have the relatime behaviour since kernels 2.6.30 implemented.
> >> Should I open a ticket on this?
> >>
> >> Cheers,
> >>         Oliver
> >>
> >> Am 02.12.19 um 14:31 schrieb Oliver Freyermuth:
> >>> I was thinking about the behaviour of relatime on kernels since 2.6.30 (quoting mount(8)):
> >>> --------------------
> >>> "Update inode access times relative to modify or change time.  Access time is only updated if the previous access time was earlier than the current modify or change time.  (Similar to
> >>>  noatime, but it doesn't break mutt or other applications that need to know if a file has been read since the last time it was modified.)
> >>>
> >>>  Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless noatime was specified),
> >>>  and the strictatime option is required to obtain traditional semantics.  In addition, since
> >>>  Linux 2.6.30, the file's last access time is always updated if it is more than 1 day old."
> >>> --------------------
> >>
> >> _______________________________________________
> >> ceph-users mailing list -- ceph-users@xxxxxxx
> >> To unsubscribe send an email to ceph-users-leave@xxxxxxx
> > 
> 
> 



_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux