> From what I recall AWS FSx Lustre is a manage service that provides your clients a mounted lustre and zero control over the backend servers Makes total sense. I'd do the same thing in their shoes.
Sounds like I'd be better off just doing lustre on top of it via EC2 or whatever provider I want to use. Thanks! -Paulson On Fri, Jun 23, 2023 at 1:47 PM Coffman, Chris <coffma...@ornl.gov> wrote: > From what I recall AWS FSx Lustre is a manage service that provides your > clients a mounted lustre and zero control over the backend servers. I > believe the mdt option you’re attempting to enable requires you be on the > MDS node you are not able to access. > > > > If this is functionality you need documenting with AWS is likely the first > step. They may find the value in providing robinhood functionality for you > and others. > > > > -Chris > > > > *From: *lustre-discuss <lustre-discuss-boun...@lists.lustre.org> on > behalf of Paulson McIntyre <p...@gpmidi.net> > *Date: *Friday, June 23, 2023 at 1:38 PM > *To: *lustre-discuss@lists.lustre.org <lustre-discuss@lists.lustre.org> > *Subject: *[EXTERNAL] [lustre-discuss] AWS's FSX-Lustre - Robinhood & MDT > Registration > > I'm using AWS's FSX's Lustre and am having issues enabling HSM and the > changelog settings: > > > > # lctl set_param mdt.64rczbev-MDT0000.hsm_control=enabled > error: set_param: param_path > 'mdt/64rczbev-MDT0000/hsm_control': No such file or directory > > > > As best as I can tell the MDTs don't exist or aren't visible. I'm trying > to figure out if it's a PBKEC or AWS blocks this. > > > > # lctl list_param \*.64rczbev-MDT0000\* > mdc.64rczbev-MDT0000-mdc-ffff888007eef000 > > > > Normally I'd ask AWS's support but it's a personal project and that's $$$. > > > > -Paulson >
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
