Dear Zeehan,
In our case, it looks like that the removed OST is disappeared. However,
sometimes we feel that some "shodow" of the removed OST still exists in
the Lustre file system.
In our system, running "lctl get_param osc.*.conn_uuid" it shows:
Dear Etienne,
Thank you very much for this information, which very interesting.
Will it be available in Lustre version 2.14 ? Hope that the Lustre
manual could also be updateded for the corresponding usage. Then
we would be happy to test it.
Best Regards,
T.H.Hsieh
On Fri, Mar 05, 2021 at
Dear Tung-Han, even during all the above steps the OST still appears? we
did the same for 3 OSTs in our centre and they disappeared correctly.
Zeehan
On Mon, Mar 8, 2021 at 11:15 AM Tung-Han Hsieh <
thhs...@twcp1.phys.ntu.edu.tw> wrote:
> Dear Zeeshan,
>
> Yes. We did lfs_migrate to move data
Dear Zeeshan,
Yes. We did lfs_migrate to move data out of the OST which we are
going to remove, and then deactivate it, and then unmount it. We
have verified that after the whole process, no data lost, but only
the total space of the Lustre file system decreased due to the
removed OST.
Best
Did you unmount the OST ? remember to lfs_migrate the data otherwise old
data would give errors
On Fri, Mar 5, 2021 at 11:59 AM Etienne Aujames via lustre-discuss <
lustre-discuss@lists.lustre.org> wrote:
> Hello,
>
> There is some process/work in progress on the LU-7668 to remove the OST
>
Hello,
There is some process/work in progress on the LU-7668 to remove the OST
directly on the MGS configuration.
In the comment section Andreas describes a way to remove an OST with
llog_print and llog_cancel (see https://review.whamcloud.com/41449).
Stephane Thiell have submitted a patch (
Dear Angelos,
On Fri, Mar 05, 2021 at 12:15:19PM +0800, Angelos Ching via lustre-discuss
wrote:
> Hi TH,
>
> I think you'll have to set max_create_count=2 after step 7 unless you
> unmount and remount your MDT.
Yes. You are right. We have to set max_create_count=2 for the replaced
OST,
Hi TH,
I think you'll have to set max_create_count=2 after step 7 unless
you unmount and remount your MDT.
And for step 4, I used conf_param instead of set_param during my drill
and I noticed this might be more resilient if you are using a HA pair
for the MDT because the MDS might try
Dear Hans,
Thank you very much. Replacing the OST is new to me and very very
useful. We will try it next time.
So, according to the description of the manual, to replace the OST
we probably need to:
1. Lock the old OST (e.g., chome-OST0008) such that it will not
create new files (run in the
Hi,
The manual describe this:
https://doc.lustre.org/lustre_manual.xhtml#lustremaint.remove_ost
There is a note telling you that it will still be there, but can be
replaced.
Hope you migrated your data away from the OST also. Otherwise you would
have lost it.
Cheers,
Hans Henrik
On
Dear All,
Here is a question about how to remove an OST completely without
restarting the Lustre file system. Our Lustre version is 2.12.6.
We did the following steps to remove the OST:
1. Lock the OST (e.g., chome-OST0008) such that it will not create
new files (run in the MDT server):
11 matches
Mail list logo
