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 became completely unmountable.
On Tue, 7 Nov 2023 at 13:56, Andreas Dilger <adil...@whamcloud.com> wrote: > 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 the face of such storage issues you need to use > dm-multipath. > > Cheers, Andreas > > > On Nov 5, 2023, at 09:13, Backer via lustre-discuss < > lustre-discuss@lists.lustre.org> wrote: > > > > - Why did OST become in this state after the write failure and was > mounted RO. The write error was due to iSCSI target going offline and > coming back after a few seconds later. >
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
