[Top] [All Lists]

Re: Insight into soft lockup related to XFS?

To: Brian Foster <bfoster@xxxxxxxxxx>
Subject: Re: Insight into soft lockup related to XFS?
From: Galen Charlton <gmc@xxxxxxxxxxxxxx>
Date: Tue, 25 Nov 2014 11:57:25 -0800
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20141125192737.GC8132@xxxxxxxxxxxxxxx>
References: <CAPLnt650QrFkkUC7kw4zVtDg6VsFqGoXEKSq_fzVjQ9acpruKg@xxxxxxxxxxxxxx> <20141125192737.GC8132@xxxxxxxxxxxxxxx>

On Tue, Nov 25, 2014 at 11:27 AM, Brian Foster <bfoster@xxxxxxxxxx> wrote:
> Do you reproduce this often or is this a one-off occurrence?

So far, just a one-off after a couple hundred days of uptime.

> FYI, the output below is line-wrapped and difficult to read. It's best
> to try and post log content so your mailer doesn't munge it (or also
> attach it unformatted so it's easier to parse).

Gah, sorry about that.

> Anyways, this looks like it could be the lock recursion problem fixed by
> the following commits:
> 5337fe9b xfs: recheck buffer pinned status after push trylock failure
> fa5566e4 xfs: remove log force from xfs_buf_trylock()
> ... which were introduced around v3.9. On a quick search, I don't see
> these commits in stable trees before that so the v3.10 stable tree would
> be the first where they are available.



Galen Charlton
Manager of Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc@xxxxxxxxxxxxxx
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &

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