From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dale Stimson <DaleStimson@gmail.com>
Cc: linux-nfs@vger.kernel.org,
David Shaw <dshaw-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org>
Subject: Re: [solved] Re: [PATCH] Short write in nfsd becomes a full write to the client
Date: Tue, 30 Jun 2009 11:22:50 -0400 [thread overview]
Message-ID: <20090630152250.GD17840@fieldses.org> (raw)
In-Reply-To: <20090630152209.GA3320-NmLOIDrUSDQtrE7AZYN0JQC/G2K4zDHf@public.gmane.org>
On Tue, Jun 30, 2009 at 08:22:09AM -0700, Dale Stimson wrote:
> On Mon, Jun 29, 2009 at 03:49:25PM -0400, J. Bruce Fields wrote:
> > After looking at the trace: yes, looks like the same problem. (The
> > (succesful) FILE_SYNC write request returned with a 0 length.) So
> > retest with the new patch applied, then poke the Fedora people to apply
> > it as well.
> >
> > --b.
>
> Success.
>
> I applied patch a0d24b295aed7a9daf4ca36bd4784e4d40f82303
> "nfsd: fix hung up of nfs client while sync write data to nfs server"
> to the otherwise unmodified Fedora 11 kernel 2.6.29.5-191.fc11.i686.PAE
> and the problem was resolved.
>
> Thank you for your help. I will update
> https://bugzilla.redhat.com/show_bug.cgi?id=508174
> and suggest that the patch be applied to future Fedora 2.6.29-based kernels.
Thanks for following up.--b.
prev parent reply other threads:[~2009-06-30 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 4:24 [PATCH] Short write in nfsd becomes a full write to the client Dale Stimson
[not found] ` <20090627042449.GC15665-NmLOIDrUSDQtrE7AZYN0JQC/G2K4zDHf@public.gmane.org>
2009-06-29 14:59 ` J. Bruce Fields
2009-06-29 19:29 ` Dale Stimson
[not found] ` <20090629192951.GA3851-NmLOIDrUSDQtrE7AZYN0JQC/G2K4zDHf@public.gmane.org>
2009-06-29 19:47 ` J. Bruce Fields
2009-06-29 19:49 ` J. Bruce Fields
2009-06-30 15:22 ` [solved] " Dale Stimson
[not found] ` <20090630152209.GA3320-NmLOIDrUSDQtrE7AZYN0JQC/G2K4zDHf@public.gmane.org>
2009-06-30 15:22 ` J. Bruce Fields [this message]
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=20090630152250.GD17840@fieldses.org \
--to=bfields@fieldses.org \
--cc=DaleStimson@gmail.com \
--cc=dshaw-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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