From: Mark Tinguely <tinguely@sgi.com>
To: Florian Pritz <bluewind@xinu.at>
Cc: Ben Myers <bpm@sgi.com>, "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, Alex Elder <elder@kernel.org>,
xfs@oss.sgi.com
Subject: Re: NFS stalls when writing - linux 3.6.x
Date: Fri, 09 Nov 2012 11:53:00 -0600 [thread overview]
Message-ID: <509D42FC.8080204@sgi.com> (raw)
In-Reply-To: <509D3C9A.6040209@xinu.at>
On 11/09/12 11:25, Florian Pritz wrote:
> On 09.11.2012 18:20, Ben Myers wrote:
>> I took a brief look but there were no slam dunks. This seems like it might be
>> a candidate:
>>
>> 8375f922 - xfs: re-enable xfsaild idle mode and fix associated races
>>
>> The sysrq-trigger information would definately be helpful. Meanwhile I'll see
>> if I can reproduce the issue.
>
> No idea why it doesn't show up on gmane yet (the excerpt is from my mail
> to the list), but I've uploaded it here[1]. The link will be valid for
> 10 days.
>
> [1]: https://paste.xinu.at/koXRw/
>
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
Thank-you for the task list. Could we get a dump of the hang?
# echo c >/proc/sysrq-trigger
It requires kdump configured.
--Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Tinguely <tinguely@sgi.com>
To: Florian Pritz <bluewind@xinu.at>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, Ben Myers <bpm@sgi.com>,
Alex Elder <elder@kernel.org>,
linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: NFS stalls when writing - linux 3.6.x
Date: Fri, 09 Nov 2012 11:53:00 -0600 [thread overview]
Message-ID: <509D42FC.8080204@sgi.com> (raw)
In-Reply-To: <509D3C9A.6040209@xinu.at>
On 11/09/12 11:25, Florian Pritz wrote:
> On 09.11.2012 18:20, Ben Myers wrote:
>> I took a brief look but there were no slam dunks. This seems like it might be
>> a candidate:
>>
>> 8375f922 - xfs: re-enable xfsaild idle mode and fix associated races
>>
>> The sysrq-trigger information would definately be helpful. Meanwhile I'll see
>> if I can reproduce the issue.
>
> No idea why it doesn't show up on gmane yet (the excerpt is from my mail
> to the list), but I've uploaded it here[1]. The link will be valid for
> 10 days.
>
> [1]: https://paste.xinu.at/koXRw/
>
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
Thank-you for the task list. Could we get a dump of the hang?
# echo c >/proc/sysrq-trigger
It requires kdump configured.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-09 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 19:29 NFS stalls when writing - linux 3.6.x Florian Pritz
2012-11-07 19:07 ` J. Bruce Fields
[not found] ` <509D2993.4050604@xinu.at>
2012-11-09 16:36 ` J. Bruce Fields
2012-11-09 16:36 ` J. Bruce Fields
2012-11-09 17:20 ` Ben Myers
2012-11-09 17:20 ` Ben Myers
2012-11-09 17:25 ` Florian Pritz
2012-11-09 17:25 ` Florian Pritz
2012-11-09 17:53 ` Mark Tinguely [this message]
2012-11-09 17:53 ` Mark Tinguely
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=509D42FC.8080204@sgi.com \
--to=tinguely@sgi.com \
--cc=bfields@fieldses.org \
--cc=bluewind@xinu.at \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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.