mailto:adil...@whamcloud.com>>
Sent: Wednesday, February 1, 2023 18:16
To: BALVERS Martin mailto:martin.balv...@danone.com>>
Cc: lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] Mistake while removing an OST
** Caution - this is an ext
o keep.
Regards,
Martin
From: Andreas Dilger mailto:adil...@whamcloud.com>>
Sent: Wednesday, February 1, 2023 18:16
To: BALVERS Martin mailto:martin.balv...@danone.com>>
Cc: lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] Mista
the add_uuid and attach indexes for OST0002. OST0002 is the
one I need to keep.
Regards,
Martin
From: Andreas Dilger
Sent: Wednesday, February 1, 2023 18:16
To: BALVERS Martin
Cc: lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] Mistake while removing an OST
** Caution
You should just be able to run the "writeconf" process to regenerate the config
logs. The removed OST will not re-register with the MGS, but all of the other
servers will, so it should be fine.
Cheers, Andreas
On Feb 1, 2023, at 03:48, BALVERS Martin via lustre-discuss
wrote:
Hi,
I have
Hi,
I have a defective OSS with a single OST that I was tying to remove from the
lustre filesystem completely (2.15.1). I was following
https://doc.lustre.org/lustre_manual.xhtml#lustremaint.remove_ost
I had drained the OST and was now using the commands with llog_cancel to remove
the config.
