From: Nix <nix@esperi.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: 2.6.34 nfs fsync() deadlock
Date: Mon, 31 May 2010 18:14:37 +0100 [thread overview]
Message-ID: <87ljb0j8n6.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1275320467.5038.9.camel@heimdal.trondhjem.org> (Trond Myklebust's message of "Mon, 31 May 2010 11:41:07 -0400")
On 31 May 2010, Trond Myklebust said:
> Can you see if the following 2 attached patches (already sent to
> stable@kernel.org) suffice to fix the hang?
I'm almost getting blasé about ultrafast solutions to NFS bugs by
now. I submit a problem report and it turns out it's already been
fixed or will be in fifteen minutes. :)
I have to wait for a RAID resync first *sigh* but after that I'll try
the patches out. I'll know in four hours or so... (the problem is
relatively rare: it takes ten or so postgresql 'make check' runs to
trigger it.)
next prev parent reply other threads:[~2010-05-31 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 14:41 2.6.34 nfs fsync() deadlock Nix
2010-05-31 15:41 ` Trond Myklebust
2010-05-31 17:14 ` Nix [this message]
2010-05-31 18:11 ` Nix
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=87ljb0j8n6.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox