I think the major problem is going to be that your MDT image is not
terribly useful without the OSTs that belong to the MDT. The new OSTs
don't contain any of the objects that the MDT references.
Back at old Lustre 2.1 code you won't have any of the lfsck code that
can deal with the MDT to OST inconsistency problems. And even if you
did, every file in your filesystem would be removed or moved to lost+found.
It is not immediately clear to me what amount of useful testing could be
done under that situation. Maybe there is something.
Chris
On 06/25/2015 01:06 PM, Crowe, Tom wrote:
Greetings,
I am investigating the possibility of restoring a DD backup of our MDT,
onto test hardware. Our filesystem is 2.1 based.
The general idea would be to get the MDT/MGS restored in their entirety,
change the MGSNODE parameter on the MDT to reflect the test hardware
LNET setup, add some new OST’s, have clients mount the new setup, and
proceed with our testing.
Is there a procedure that outlines this process? I suspect the exercise
could be considered a disaster recovery test, but we do not have any
intention at this time to relocate and/or recover any of the original OST’s.
Thank You.
-Tom Crowe
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
