From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd"
Date: Thu, 28 May 2009 22:32:28 +0200 [thread overview]
Message-ID: <20090528203228.GA6056@geggus.net> (raw)
In-Reply-To: <20090528202803.GF13860@fieldses.org>
J. Bruce Fields schrieb am Donnerstag, den 28. Mai um 22:28 Uhr:
> Looks like you have subtree_check set on the "bad" export, and
> no_subtree_check set on the "good" export. subtree_check can result in
> spurious stale errors when files are renamed, so it's possible this is
> by design.
>
> You say you get that message on 296.29.x but not 2.6.27.x.
Exactly! http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527517
may refer the same bug.
> And you say you also get stale filehandle errors.
Only on 2.6.29.x. Everything works fine qwith the older Kernel.
> I assume you didn't get the same stale filehandle errors on 2.6.27.x?
No errors on the older Kernel.
Sven
--
"In my opinion MS is a lot better at making money than it is at making good
operating systems" (Linus Torvalds, August 1997)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
next prev parent reply other threads:[~2009-05-28 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 14:20 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd" Sven Geggus
2009-05-21 16:49 ` Trond Myklebust
2009-05-21 16:57 ` Sven Geggus
2009-05-21 17:32 ` Trond Myklebust
2009-05-21 17:48 ` Sven Geggus
2009-05-21 18:12 ` Trond Myklebust
2009-05-28 20:28 ` J. Bruce Fields
2009-05-28 20:32 ` Sven Geggus [this message]
2009-06-19 12:14 ` Mathias Kretschmer
2009-06-19 12:46 ` Sven Geggus
2009-06-27 19:39 ` Leandro Lucarella
2009-06-22 19:55 ` Thomas Petersen
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=20090528203228.GA6056@geggus.net \
--to=lists@fuchsschwanzdomain.de \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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