To follow-up on on my own question and help potential others with the same
issue, the 'problem' I was seeing was caused by the fact that the
hsm_state is actually stored in lustre (thanks Davide).
After the files have been successfully archived once the hsm_state is set
to archived. Deleting the archive and robinhood db does (of course) not
reset the hsm_state in lustre. So the next rbh scan of those files results
in lhsm_state synchro.
If anyone knows how to reset the whole lustre fs to a 'fresh' state,
please let me know.
For now I just reset all the files with the following command:
rbh-find --status=lhsm_status:synchro | while read x; do lfs hsm_clear
--archived "$x"; done
Martin
"Martin BALVERS" <martin.balv...@nutricia.com> wrote on 29-06-2017
09:48:33:
> From: "Martin BALVERS" <martin.balv...@nutricia.com>
> To: robinhood-support@lists.sourceforge.net
> Date: 29-06-2017 10:09
> Subject: [robinhood-support] Files inserted into database with
> lhsm_status synchro
>
> Hi,
>
> I am trying to setup robinhood v3 to backup part of our lustre fs
(2.9.0).
> I have been trying some different configuration options on a
> specific dir on our lustre fs and I am seeing something that does
> not make sense to me.
> When I drop all tables in the robinhood db, and I scan dir /lustre/
> sds, the files are all inserted with lhsm_status synchro instead of new.
>
> Below are a part of the generated scan log and the used .conf file.
> I am probably just missing something obvious here, and I recall that
> it did work at some point (first time maybe?).
>
> Regards,
> Martin Balvers
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support
