You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two resources with the following settings and a rule that executes periodically the tiering plugin
$ imeta ls -R laptopResc
AVUs defined for resource laptopResc:
attribute: irods::storage_tiering::group
value: groupie
units: 0
----
attribute: irods::storage_tiering::time
value: 15
units:
$ imeta ls -R laptopResc1
AVUs defined for resource laptopResc1:
attribute: irods::storage_tiering::group
value: groupie
units: 1
Upon itouching an empty data object into laptopResc, this file stays there forever and does not get moved to laptopResc1. On the other hand, any other data object, which contains data, honors the tiering rules
Is this the expected behavior? If so, why to treat differently an empty file generated using itouch and one generated via irsync? Thanks in advance, L.
The text was updated successfully, but these errors were encountered:
I have two resources with the following settings and a rule that executes periodically the tiering plugin
Upon
itouch
ing an empty data object intolaptopResc
, this file stays there forever and does not get moved tolaptopResc1
. On the other hand, any other data object, which contains data, honors the tiering rulesHowever, if I have the following local directory made of an empty file (
test33
) and a data file (file1
)and I copy it over to iRODS
then the empty file DOES get moved to the second storage tier
Finally, by adding again an empty data object to the
TEST33
collection results in a missed transfer to the socond storage tier againIs this the expected behavior? If so, why to treat differently an empty file generated using
itouch
and one generated viairsync
? Thanks in advance, L.The text was updated successfully, but these errors were encountered: