Hi Andreas,
AWS Lustre takes a snapshot of S3 file metadata on creation.
However, I am trying to include files that are added to the S3 bucket
after Lustre filesystem creation. Since I know which files were added, I
wanted to simply inform the Lustre HSM layer of their existence. At
Hello Nathaniel,
As a workaround, is there an older lemur rpm version or older Lustre version I
should use to unblock myself?
https://github.com/whamcloud/lemur/issues/7
https://github.com/whamcloud/lemur/issues/8
Thanks,
Pinkesh Valdria
On 12/11/19, 6:31 AM, "Pinkesh Valdria" wrote:
Thanks very much for the replies.. We are utilizing Lustre as a fast cache
on-top of S3.
AWS support has simply said they are not sure, but it is hard to break
through their defensive first line of support.
You have given me several avenues to explore. I did try the --exist flag,
but did not have
Hi Kris,
As people said each HSM has its own copytool with its own constraints. To work
properly with S3, additional metadata is stored in Lustre when files are
imported from a S3 bucket.
Questions specific to Amazon FSx For Lustre would be better asked to AWS
support.
Aurélien
Le
Hi everyone,
I don't know much about Amazon's FSx for Lustre, nor about any S3
copytool. But I do know that lhsmtool_posix (the POSIX copytool shipped
with the Lustre sources), supports an "import" operation comparable to
the "lfs hsm_register" Kris describes.
Actually, Amazon's FSx for
Hi Kris,
I assume you are using Amazon's FSx for Lustre product
(https://aws.amazon.com/fsx/lustre/) for this, rather than rolling
Lustre HSM to S3 on AWS yourself?
I'm afraid I don't know any more than you do on this product but it's
something I've been keen to play with as it sounds really
