From: Bryan Schumaker <bjschuma@netapp.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop
Date: Wed, 27 Jul 2011 12:40:15 -0400 [thread overview]
Message-ID: <4E303F6F.8010706@netapp.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1107271227340.1451@p34.internal.lan>
On 07/27/2011 12:28 PM, Justin Piszcz wrote:
>
>
> On Wed, 27 Jul 2011, J. Bruce Fields wrote:
>
>> On Wed, Jul 27, 2011 at 09:54:09AM -0400, Justin Piszcz wrote:
>>> Hi,
>>>
>>> Kernel 2.6.30 on client.
>>> Kernel 2.6.28 on server.
>>>
>>> p34 kernel: [92223.918892] NFS: directory motion/cam2 contains a
>>> readdir loop. Please contact your server vendor. Offending cookie: 10272
>>
>> What filesystem on the server are you exporting?
>
> Hi,
>
> xfs.
> /dev/sda1 on / type xfs (rw,noatime)
>
> Nothing special, thoughts?
Are there a lot of files in the directory you're exporting? It looks like cookie 10272 is mapped to multiple files. When the client tries to resume reading from this cookie, xfs will reply from the first matching file and cause the client to enter a loop.
- Bryan
>
> Justin.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-27 16:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1107270952270.1451@p34.internal.lan>
[not found] ` <20110727160752.GC974@fieldses.org>
2011-07-27 16:28 ` 2.6.xx: NFS: directory motion/cam2 contains a readdir loop Justin Piszcz
2011-07-27 16:40 ` Bryan Schumaker [this message]
2011-07-27 17:00 ` Ruediger Meier
2011-07-27 17:09 ` Bryan Schumaker
2011-07-27 17:17 ` Justin Piszcz
2011-07-27 17:45 ` J. Bruce Fields
2011-07-27 18:28 ` Bryan Schumaker
2011-07-27 17:15 ` Justin Piszcz
2011-07-27 18:11 ` Christoph Hellwig
2011-07-27 19:35 ` Justin Piszcz
2011-07-27 19:39 ` Christoph Hellwig
2011-07-27 19:44 ` Justin Piszcz
2011-07-27 19:47 ` Christoph Hellwig
2011-07-27 19:54 ` Bryan Schumaker
2011-07-27 20:02 ` Christoph Hellwig
2011-07-27 20:05 ` Christoph Hellwig
2011-07-27 20:26 ` Rüdiger Meier
2011-07-27 20:47 ` Christoph Hellwig
2011-07-27 21:21 ` Rüdiger Meier
2011-07-27 19:57 ` Justin Piszcz
2011-07-27 20:37 ` Trond Myklebust
2011-07-27 20:54 ` Trond Myklebust
2011-07-27 20:56 ` Trond Myklebust
2011-07-27 21:24 ` Justin Piszcz
2011-07-27 22:44 ` Justin Piszcz
2011-07-28 20:48 ` Trond Myklebust
2011-07-29 20:52 ` Bryan Schumaker
2011-07-29 20:59 ` Justin Piszcz
2011-07-29 22:03 ` Trond Myklebust
2011-07-29 22:23 ` Justin Piszcz
2011-07-30 9:58 ` Justin Piszcz
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=4E303F6F.8010706@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox