Thomas,

Thanks for the response.  My problem is that we fake directory based quotas
by ensuring that the ownership of files matches the top level directory.
This means we have to walk the filesystem and change the group ownership if
needed.  The problem is that this changes the mtime and Robinhood then
thinks the file was access, but it wasn't.

Craig

On Wed, Nov 11, 2015 at 12:21 PM, Thomas LEIBOVICI (mail perso) <
[email protected]> wrote:

> Le 10/11/2015 23:31, Craig Tierney - NOAA Affiliate a écrit :
>
> Thomas,
>
> Thanks for the quick response.   To confirm, use of atime with rbh-find
> will compare times to the last_access time?
>
>
> Yes.
> I understand this can be confusing but last_access is taken as the last
> activity on the file (max(atime, mtime, ctime))
> which appears to be a suitable criteria for purge policies in particular.
>
> Regards.
>
>
> Craig
>
> On Tue, Nov 10, 2015 at 2:19 PM, Thomas LEIBOVICI (mail perso) <
> <[email protected]>[email protected]> wrote:
>
>> Hi Craig,
>>
>> rbh's last_mod = stat's mtime
>> rbh's last_access = max(atime, mtime, ctime)
>> with Lustre changelogs:
>>     rbh creation is the timestamp of the CREATE record of the entry
>> when scanning :
>>     rbh creation is the ctime of the entry the first time it was seen.
>>
>> Regards
>> Thomas
>>
>>
>> Le 10/11/2015 21:09, Craig Tierney - NOAA Affiliate wrote:
>>
>> Hello,
>>
>> I have a question regarding the difference in names of timestamps used in
>> Robinhood.  When I run stat on a file, it reports 3 times.  These are
>> Access, Change, and Modify.  When I run rbh-report --entry-info on the same
>> file, Robinhood uses creation, last_access, and last_mod.
>>
>> Are last_access from RBH and Access from stat supposed to be the same?
>> What about Modify and last_mod?  How does the timestamp Change from stat
>> and creation from RBH relate?
>>
>> Thanks,
>> Craig
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> robinhood-support mailing 
>> [email protected]https://lists.sourceforge.net/lists/listinfo/robinhood-support
>>
>>
>>
>>
>> ------------------------------
>> [image: Avast logo] <http://www.avast.com/>
>>
>> L'absence de virus dans ce courrier électronique a été vérifiée par le
>> logiciel antivirus Avast.
>> www.avast.com
>>
>>
>
>
>
> ------------------------------
> [image: Avast logo] <http://www.avast.com/>
>
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> www.avast.com
>
>
------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to