[Top] [All Lists]

Re: xfs file system corruption

To: Allan Haywood <Allan.Haywood@xxxxxxxxxxxxx>
Subject: Re: xfs file system corruption
From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Date: Wed, 08 Oct 2008 02:15:29 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <E8DED08235A93F4D8A2AB6CD0ABAB32A0A937FC922@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> (Allan Haywood's message of "Tue, 7 Oct 2008 16:49:40 -0700")
References: <E8DED08235A93F4D8A2AB6CD0ABAB32A0A937FC8EC@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081007233418.GB7342@disturbed> <E8DED08235A93F4D8A2AB6CD0ABAB32A0A937FC922@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (gnu/linux)
Allan Haywood <Allan.Haywood@xxxxxxxxxxxxx> writes:
>         Would reloading the xfs module work also, to clear any pending
>         writes (if I could get it to a point where modprobe -r xfs
>         would work)? Although I am doubting that if there are pending
>         writes that it would be easy to get xfs to unload.

Linux doesn't have IO cancel and it's hard to stop everything
in the IO stack, so the usual way is to fence it at a high level
and then wait for all pending IO. But that might take a long time.

That is why most HA setups use hard stonith, as in power switch.


<Prev in Thread] Current Thread [Next in Thread>