From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Doug Nazar <nazard@dragoninc.ca>,
"'David Woodhouse'" <David.Woodhouse@intel.com>,
"'Al Viro'" <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.28-rc3 truncates nfsd results
Date: Sun, 9 Nov 2008 14:09:51 -0500 [thread overview]
Message-ID: <20081109190951.GD25568@fieldses.org> (raw)
In-Reply-To: <491097DA.9040204@garzik.org>
On Tue, Nov 04, 2008 at 01:43:38PM -0500, Jeff Garzik wrote:
> Doug Nazar wrote:
>> Commit 8d7c4203 "nfsd: fix failure to set eof in readdir in some situations"
>> breaks the nfsd server. Bisected it back to this commit and reverting it
>> fixes the problem.
>>
>> However, it only happens on certain machines even with the same kernel &
>> filesystem (ext3). I've two groups of similar computers, each group running
>> identical kernels. The ones listing only ~250 files are of course in error.
>> Eldritch is running 2.6.28-rc3 with that commit reverted. With 2.8.28-rc3 it
>> showed the incorrect number.
>
> I'm seeing "weirdness" on my NFS4-mounted home directory (client and
> server are both x86-64 2.6.28-rc) -- gconfd locking up, and other
> desktop gadgets breaking. 2.6.27 works great.
>
> I'll try reverting this and see if the behavior improves, thanks for the
> pointer...
Any more details on that "weirdness"?
--b.
next prev parent reply other threads:[~2008-11-09 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 18:27 2.6.28-rc3 truncates nfsd results Doug Nazar
2008-11-04 18:43 ` Jeff Garzik
2008-11-04 19:03 ` David Woodhouse
2008-11-04 19:32 ` Doug Nazar
2008-11-04 20:08 ` David Woodhouse
2008-11-09 19:09 ` J. Bruce Fields [this message]
2008-11-04 19:36 ` J. Bruce Fields
2008-11-04 22:30 ` J. Bruce Fields
2008-11-05 11:16 ` Doug Nazar
2008-11-05 21:46 ` J. Bruce Fields
2008-11-05 23:07 ` J. Bruce Fields
2008-11-06 5:21 ` Doug Nazar
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=20081109190951.GD25568@fieldses.org \
--to=bfields@fieldses.org \
--cc=David.Woodhouse@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nazard@dragoninc.ca \
--cc=viro@zeniv.linux.org.uk \
/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