[GLLUG] SAN events kill Linux filesystems

James Dutton james.dutton at gmail.com
Sat Jan 6 10:08:32 UTC 2024

On Wed, 20 Dec 2023, 11:51 Henrik Morsing via GLLUG, <
gllug at mailman.lug.org.uk> wrote:

> Good morning,
> Don't know if anyone has come across this but every time a SAN node is
> powered down on our SAN, even if un-used, we have a handful of Linux LPARs
> (across multiple frames) with filesystems going into read-only.
> We had migrated away from our IBM V9000 and many months later powered it
> off resulting in the first occurrence of this issue. Later on, we patched
> our new EMC 9200T, which (I'm not a storage person) has two... linked
> systems?... with two nodes each, so four node in total. Even when the first
> node rebooted, we had a handful of Linux systems going into read-only
> (Other OSes un-affected).


Is there anything in the kernel logs? There should be something in there
that explains why Linux thought it best to switch the fs to readonly.

There are lots of different reasons to go readonly, so without logs, it's
difficult to give any helpful info.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20240106/dbcc9711/attachment.htm>

More information about the GLLUG mailing list