-devel] [GFS2 PATCH] gfs2: Panic when an io error occurs
writing
- Original Message -
Hi Bob,
I agree, it's a hard problem. I'm just trying to understand that we've
done the absolute best we can and that if this condition is hit then
the best solution really is to just kill the node. I
: 18 December 2018 15:52
To: Mark Syms
Cc: cluster-devel@redhat.com
Subject: Re: [Cluster-devel] [GFS2 PATCH] gfs2: Panic when an io error occurs
writing
- Original Message -
> Hi Bob,
>
> I agree, it's a hard problem. I'm just trying to understand that we've
> done the abso
- Original Message -
> Hi Bob,
>
> I agree, it's a hard problem. I'm just trying to understand that we've done
> the absolute best we can and that if this condition is hit then the best
> solution really is to just kill the node. I guess it's also a question of
> how common this actually
PATCH] gfs2: Panic when an io error occurs
writing
- Original Message -
> I think a reasonable alternative to this is to just sit in an infinite
> retry loop until the i/o succeeds.
>
> Dave
> [Mark Syms] I would hope that this code would only trigger after some
> e
- Original Message -
> I think a reasonable alternative to this is to just sit in an infinite retry
> loop until the i/o succeeds.
>
> Dave
> [Mark Syms] I would hope that this code would only trigger after some effort
> has been put into retrying as panicing the host on the first I/O
On Mon, Dec 17, 2018 at 09:58:47AM -0500, Bob Peterson wrote:
> Dave Teigland recommended. Unless I'm mistaken, Dave has said that
> GFS2 should never withdraw; it should always just kernel panic (Dave,
> correct me if I'm wrong). At least this patch confines that behavior
> to a small subset
On Mon, Dec 17, 2018 at 09:58:47AM -0500, Bob Peterson wrote:
> Dave Teigland recommended. Unless I'm mistaken, Dave has said that GFS2
> should never withdraw; it should always just kernel panic (Dave, correct
> me if I'm wrong). At least this patch confines that behavior to a small
> subset of
Hi,
- Original Message -
> On 17/12/2018 09:04, Edwin Török wrote:
> >> If we get an io error writing to the journal, the only correct
> >> thing to do is to kernel panic.
> > Hi,
> >
> > That may be required for correctness, however are we sure there is no
> > other way to force the DLM
Hi,
On 17/12/2018 09:04, Edwin Török wrote:
On 17/12/2018 13:54, Bob Peterson wrote:
Hi,
Before this patch, gfs2 would try to withdraw when it encountered
io errors writing to its journal. That's incorrect behavior
because if it can't write to the journal, it cannot write revokes
for the
On 17/12/2018 13:54, Bob Peterson wrote:
> Hi,
>
> Before this patch, gfs2 would try to withdraw when it encountered
> io errors writing to its journal. That's incorrect behavior
> because if it can't write to the journal, it cannot write revokes
> for the metadata it sends down. A withdraw will
10 matches
Mail list logo
