It would be useful if you provided the actual error messages, so we can see where the problem is.
What command did you run on the OST? Does the OST still show that it has data in it (e.g. "df" or "dumpe2fs -h" shows lots of used blocks)? On Mar 25, 2020, at 10:05, Gong-Do Hwang <grover.hw...@gmail.com<mailto:grover.hw...@gmail.com>> wrote: Dear Lustre, Months ago when I tried to add a new disk to my new Lustre FS, I accidentally target the mkfs.lustre to a then mounted OST partition of another Lustre FS. Weird enough the command passed through, and without paying attention to it, I umount the partition months later and couldn't mount it back, then I realized the mkfs.lustre command was legit. But my old lustre FS worked well through these months, so I guess the data in that OST is still there. But now the permanent CONFIG/mountdata is the new one, and I can still see my old config in the previous value. My question is is there any way I can write back the old CONFIG/mountdata and still keep all my files in that OST? I am using Luster 2.13.0 for my mgs/mdt/ost Thanks for your help and I really appreciate it! Grover _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org Cheers, Andreas -- Andreas Dilger Principal Lustre Architect Whamcloud
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
