6:04 a.m.
On 02/04/2014 07:26 PM, Cowe, Malcolm J wrote:
Hi Gary,
Robinhood should pick up the default archive ID, which can be found on the MDT:
lctl get_param mdt.*.hsm.default_archive_id
Otherwise, RH will use archive_id = 0. If it's not picking up the Lustre default,
then there may be a bug in Robinhood.
An HSM archive ID can be recorded in the Robinhood configuration in FileClass
definitions, e.g.:
FileClass mjc_lustre_files {
definition {
tree == "/lustre/fs01/demo"
and
owner == "mjc"
}
archive_num = 4;
}
This is required when there is more than one archive available to Lustre and you want to
define sets of files that are archived somewhere other than the default. Not sure if this
would be enough in the case you presented.
The archive ID is an attribute of the file, so if the file is deleted, so is the archive
ID reference. I wouldn't expect the changelog to necessarily record the archive ID
when a file is deleted but for a deferred removal policy to work, the archive ID would
need to persist somewhere in Robinhood after the original file is deleted.
I was thinking the changelog could have the id when the file was
archived, but I don't see it in the HSM change record. Of coarse,
Robinhood, for requests it makes, could remember what archive it
requested. But there seems to be no path from the "lfs hsm_archive"
command to get the ID into robinhood unless robinhood looks. But
again, I didn't see the archive id in any database table in Robinhood
after doing a "lfs hsm_archive". My main concern is that I don't see a
place for the archive id in the table that is remembering the delayed
removes of deleted files. Like the filesystem, the database appears to
delete all info about the file when it is deleted and creates a record
in the SOFT_RM table in the mysql database in order to remember to do the
hsm_remove at a later time.
It would be worth posting your questions to the "robinhood-support" mailing
list (http://sourceforge.net/p/robinhood/mailman/).
I will. Thanks for the suggestion.
Gary
Regards,
Malcolm.
> -----Original Message-----
> From: HPDD-discuss [mailto:hpdd-discuss-bounces@lists.01.org] On
> Behalf Of Gary Hagensen
> Sent: Wednesday, February 05, 2014 1:26 PM
> To: hpdd-discuss(a)lists.01.org
> Subject: [HPDD-discuss] robinhood delayed removed from archive -
> archive#0 only?
>
>
> I have been playing with robinhood and the delayed removal from the
> archive. I don't see how it can work except from archive = 0. I don't
> see the archive id in the changelog. Robinhood could query for it when
> it sees an HSM changlog entry but I don't see a place holder for it in
> the robinhood mysql database tables. I archived a file (tryitfile2)
> using archive=4 and didn't see the "4" show up in any of the mysql
> tables. I did see the deleted file move through the SOFT_RM table in
> the mysql database, but a query of hsm.actions shows the removal
> waiting with the archive#=0, not 4.
>
> If this is indeed the case, it should be documented that delayed
> removal from the archive will only work for archive=0.
>
> The second file in the mysql tables shows the file waiting for
> removal. Looking at the other tables in the database, it appears that
> all references to it are gone so the data in SOFT_RM appears to be the
> only data that is available (no archive_id to pass along).
>
> mysql> select * from SOFT_RM;
>
+---------------------+-------------------------------+--------------+--------------
> +
> | fid | fullpath | soft_rm_time |
real_rm_time |
>
+---------------------+-------------------------------+--------------+--------------
> +
> | 0x200000400:0x2:0x0 | /mnt/dmf2lfs/tryit/tryitfile | 1391562713 |
> 1391649113 |
> | 0x200000400:0x3:0x0 | /mnt/dmf2lfs/tryit/tryitfile2 | 1391564535 |
> 1391564595 |
>
+---------------------+-------------------------------+--------------+--------------
> +
> 2 rows in set (0.00 sec)
>
> The time expired, robinhood issues the request and removed it from the
> database
>
> mysql> select * from SOFT_RM;
>
+---------------------+------------------------------+--------------+--------------
> +
> | fid | fullpath | soft_rm_time |
real_rm_time |
>
+---------------------+------------------------------+--------------+--------------
> +
> | 0x200000400:0x2:0x0 | /mnt/dmf2lfs/tryit/tryitfile | 1391562713 |
> 1391649113 |
>
+---------------------+------------------------------+--------------+--------------
> +
>
> But here is the request waiting on archive=0, not 4.
>
> # lctl get_param -n mdt.dmf2lfs-MDT0000.hsm.actions
> lrh=[type=10680000 len=136 idx=1/40] fid=[0x200000400:0x3:0x0]
> dfid=[0x200000400:0x3:0x0]
> compound/cookie=0x52f1807b/0x52f180 7b action=REMOVE
> archive#=0 flags=0x0 extent=0x0-0xffffffffffffffff
> gid=0x0 datalen=0 status=WAITING data=[]
>
> Another thing to note is that if you have a deferred_remove_delay of
> say 1 day, then delete a file, then change the deferred_remove_delay
> to 1 hour, only files deleted after the change (using rbh-lhsm -d)
> will get the new delay. The previously deleted file will wait 1 day to
> be removed. Not totally unexpected, but should be documented.
>
> Gary
>
> _______________________________________________
> HPDD-discuss mailing list
> HPDD-discuss(a)lists.01.org
> https://lists.01.org/mailman/listinfo/hpdd-discuss