Hello! (sorry to those who’ve seen a similar message on Slack, but I understand that more GPFS devs have visibility of this mailing list)
I run the GPFS-based (currently 5.1.2) general purpose research data storage facility at KCL and I’ve been experimenting with external storage pools. Using a VM running the Developer Edition I’m trying to implement a proof of concept. I’ve defined the external storage pool: RULE EXTERNAL POOL ‘dt’ EXEC ‘/root/rule/dt_esp’ pointing to my go code that understands the “verbs” from the policy engine – TEST, MIGRATE, PREMIGRATE etc. and I have RULE ‘migrate_to_dt’ MIGRATE FROM POOL ‘system’ to POOL ‘dt’ WHERE PATH_NAME LIKE ‘/test1/fileset1/%’ I’ve implemented MIGRATE, to start with, and I get the list of files and copy them over the the external storage. All that seems to be working fine and the files are getting copied over as expected. However, I’m struggling to find any documentation or examples of stubbing the file in GPFS or how the RECALL action should work. Is it up to the implementation of any particular external storage pool type to decide what to leave in place and set whichever extended attribute it wants? I wondered whether there are any examples of this and what’s needed (DMAPI?) to get the RECALL. Many thanks! Daniel. /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Daniel Hanlon Head of e-Research Data, e-Research, RMID, King’s College London.
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
