Hi Thomas,
Indeed, it's seems to work. It's quite surprising because in the log there's
still the "wrong" last access, but the policy is apply on the "good" one.
If you or someone else have informations about implement robinhood on GPFS, i'm
still interested.
Thank you and have a good day,
Regards,
Emilie
----- Mail original -----
De: "LEIBOVICI Thomas" <[email protected]>
À: [email protected], [email protected]
Envoyé: Mercredi 12 Mars 2014 13:01:41
Objet: Re: [robinhood-support] Issue with accestime criteria
Hi Emilie,
Indeed, robinhood is not notified by Lustre in case of access, only for changes
(actually it could, but it is not recommended on a production system, as it
would represent a huge flow of events).
This explains atime is outdated in rbh DB, unlike change time.
acces times in DB can be updated by scanning regularly your filesystem.
They are also refreshed when applying policy on entries.
You can see this outdated atime in rbh-find output, but don't worry, atime is
correctly handled when applying a policy (like rmdir):
robinhood refreshes its atime when it applies a policy to an entry
to ensure it perfectly respects the policy criteria on access times.
Regards,
Thomas
On 03/12/14 10:56, [email protected] wrote:
Hello to all,
I wanted to use rm policy and rbh-find based on last access criteria and it
appears that the access time is outdated on my test. I use robinhood
2.5.0-0.beta1 version and Lustre 2.1 version.
I run the Lustre find command with an 30 days access time argument and the same
for rbh-find: i have not the same results, it seems that for robinhood "access
time" it's the same than "change time".
For example this file :
File: « /scratch//xxxxx/xxxxx/myfile-2765732 »
Size: 190852 Blocks: 376 IO Block: 2097152 fichier
Device: a2f3dcdch/2733890780d Inode: 144871533880362197 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1045/ xxxx) Gid: ( 300/ xxxxxx)
Access: 2014-02-13 14:26:42.000000000 +0100
Modify: 2014-01-28 12:58:22.000000000 +0100
Change: 2014-02-05 13:07:11.000000000 +0100
Birth: -
With the Lustre find command and the stat command, last access is 13/02/2014
but for Robinhood last acess with rbh-find command and the database
informations is 05/02/2014.
I saw on the documentation of the last version that the access time could be
outdated. But have you a way to fix it or a workaround to suggest?
I have an another question: is anyone using robinhood with GPFS for rm policy
or quota alert? I might have to implement robinhood with GPFS, so if someone
have tips I'm interested.
Thanks by advance for your answer,
Emilie
--
Centre Informatique National de l'Enseignement Supérieur (CINES)
Département Calcul Intensif (DCI)
Tel : 33 4 67 141414
Fax : 33 4 67 523763
http://www.cines.fr
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
robinhood-support mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
