From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "<linux-fsdevel@vger.kernel.org>" <linux-fsdevel@vger.kernel.org>,
"xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs deadlocks since upgrading to 4.1.15
Date: Mon, 18 Jan 2016 06:48:52 +1100 [thread overview]
Message-ID: <20160117194852.GR6033@dastard> (raw)
In-Reply-To: <569A972C.5060802@profihost.ag>
On Sat, Jan 16, 2016 at 08:17:00PM +0100, Stefan Priebe wrote:
> Hi Dave,
>
> Am 15.01.2016 um 23:55 schrieb Dave Chinner:
> >On Fri, Jan 15, 2016 at 10:07:58AM +0100, Stefan Priebe wrote:
> >>Hello,
> >>
> >>since we upgraded from 3.18 to 4.1.15 i've seen many deadlocks. Alle
> >>call traces show xfs.
> >>
> >>Attention all those are down top instead of top down (sorry for the
> >>wrong order).
> >
> >Can you repost them with line wrapping turned off, so they are
> >readable without causing beeding eye syndrome?
> i'm sorry. i was a bit optimistic that someone can read that.
>
> Here are the traces in correct order, without timestamps but at
> pastebin which seems to be easier at least with thunderbird as it
> has no easy to use option to disable wrapping.
>
> Nr 1:
> http://pastebin.com/raw/Fuxd86TP
>
> Nr 2:
> http://pastebin.com/raw/Dp7mEcKi
>
> Nr 3:
> http://pastebin.com/raw/BY3gUwzx
Commit 7a29ac4 ("xfs: give all workqueues rescuer threads") should
fix it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "<linux-fsdevel@vger.kernel.org>" <linux-fsdevel@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>
Subject: Re: xfs deadlocks since upgrading to 4.1.15
Date: Mon, 18 Jan 2016 06:48:52 +1100 [thread overview]
Message-ID: <20160117194852.GR6033@dastard> (raw)
In-Reply-To: <569A972C.5060802@profihost.ag>
On Sat, Jan 16, 2016 at 08:17:00PM +0100, Stefan Priebe wrote:
> Hi Dave,
>
> Am 15.01.2016 um 23:55 schrieb Dave Chinner:
> >On Fri, Jan 15, 2016 at 10:07:58AM +0100, Stefan Priebe wrote:
> >>Hello,
> >>
> >>since we upgraded from 3.18 to 4.1.15 i've seen many deadlocks. Alle
> >>call traces show xfs.
> >>
> >>Attention all those are down top instead of top down (sorry for the
> >>wrong order).
> >
> >Can you repost them with line wrapping turned off, so they are
> >readable without causing beeding eye syndrome?
> i'm sorry. i was a bit optimistic that someone can read that.
>
> Here are the traces in correct order, without timestamps but at
> pastebin which seems to be easier at least with thunderbird as it
> has no easy to use option to disable wrapping.
>
> Nr 1:
> http://pastebin.com/raw/Fuxd86TP
>
> Nr 2:
> http://pastebin.com/raw/Dp7mEcKi
>
> Nr 3:
> http://pastebin.com/raw/BY3gUwzx
Commit 7a29ac4 ("xfs: give all workqueues rescuer threads") should
fix it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-01-17 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 9:07 xfs deadlocks since upgrading to 4.1.15 Stefan Priebe
2016-01-15 9:07 ` Stefan Priebe
2016-01-15 22:55 ` Dave Chinner
2016-01-15 22:55 ` Dave Chinner
2016-01-16 19:17 ` Stefan Priebe
2016-01-16 19:17 ` Stefan Priebe
2016-01-17 19:48 ` Dave Chinner [this message]
2016-01-17 19:48 ` Dave Chinner
2016-01-18 7:20 ` Stefan Priebe - Profihost AG
2016-01-18 7:20 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160117194852.GR6033@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.