So, did you do the "writeconf"? And the OST mounted afterwards?
As I understand, the MGS was under the impression that this re-mounting
OST was actually a new one using an old index.
So, what made your repaired OST look new/different ?
I would probably have mounted it locally, as an ext4 file
Thanks for the explanation. There was a problem with the iscsi target. It
is already multi-path. Anyhow, I was expecting things to come back online
after the problem was resolved. This kind of created a data loss situation
and I thought Lustre was resilient not to lose the whole OST. Here the OST
The OST went read-only because that is what happens when the block device
disappears underneath it. That is a behavior of ext4 and other local
filesystems as well.
If you look in the console logs you would see SCSI errors and the filesystem
being remounted read-only.
To have reliability in
From: lustre-discuss on behalf of
Backer via lustre-discuss
Sent: Tuesday, November 7, 2023 2:19 PM
To: lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] OST is not mounting
Hi,
Sending this again. Appreciate your help.
On Sun, 5 Nov 2023 at 11:11, Backer
Hi,
Sending this again. Appreciate your help.
On Sun, 5 Nov 2023 at 11:11, Backer wrote:
> Hi,
>
> I am new to this email list. Looking to get some help on why an OST is not
> getting mounted.
>
>
> The cluster was running healthy and the OST experienced an issue and Linux
> re-mounted the OST
Hi,
I am new to this email list. Looking to get some help on why an OST is not
getting mounted.
The cluster was running healthy and the OST experienced an issue and Linux
re-mounted the OST read only. After fixing the issue and rebooting the node
multiple times, it wouldn't mount.
When the
