From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: nfs@lists.sourceforge.net, gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org
Subject: Re: nfs + Reiser4
Date: Wed, 7 Apr 2010 15:20:25 -0400 [thread overview]
Message-ID: <20100407192025.GH26072@fieldses.org> (raw)
In-Reply-To: <4BBCD618.50301@oracle.com>
On Wed, Apr 07, 2010 at 02:59:36PM -0400, Chuck Lever wrote:
> On 04/07/2010 02:51 PM, J. Bruce Fields wrote:
>> On Wed, Apr 07, 2010 at 02:44:01PM -0400, Chuck Lever wrote:
>>> On 04/07/2010 01:34 PM, J. Bruce Fields wrote:
>>>> On Tue, Apr 06, 2010 at 07:52:21PM +0200, gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org wrote:
>>>>> I am having serious headaches using nfs between a reiser4 server and arm
>>>>> client.
>>>>> Both on 2.6.29 vintage kernels.
>>>>>
>>>>> Files are constantly getting out of sync.
>>>>>
>>>>> Example :
>>>>>
>>>>> boot ARM via nfs
>>>>> edit lighttpd.conf on ARM
>>>>> check edit is visible on server. OK
>>>>>
>>>>> reboot ARM
>>>>> check file : reverted to an earlier state.
>>>>> check server: edited version still showing.
>>>>
>>>> So, on a freshly booted NFS client, you're opening and reading a file
>>>> and seeing file data that isn't even on the NFS server any more?
>>>>
>>>> That's beyond bizarre. Do you have a reliable way to reproduce the
>>>> problem?
>>>
>>> Could be XID replay.
>>
>> I'm not following you. You're thinking of a read request after the
>> reboot that unluckily reuses an old XID and gets stale data from the
>> servers reply cache? Or something else?
>
> Nothing unlucky about it. Just after a boot, if the client
> implementation isn't careful about choosing an initial XID, (eg it
> always starts with a psuedorandom number but uses the same seed every
> time), it will hit the server's replay cache.
Hm, OK.
> This can be quite reproducible for NFSROOT and a quiescent server.
The Linux server doesn't cache READ results as far as I can tell.
--b.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2010-04-07 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 17:52 nfs + Reiser4 gg-B3jsHfKwJfLR7s880joybQ
[not found] ` <op.vaq49joctxpshh-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-07 17:34 ` J. Bruce Fields
2010-04-07 18:44 ` Chuck Lever
2010-04-07 18:51 ` J. Bruce Fields
2010-04-07 18:59 ` Chuck Lever
2010-04-07 19:20 ` J. Bruce Fields [this message]
2010-04-07 19:24 ` Chuck Lever
2010-04-07 21:09 ` Trond Myklebust
[not found] ` <1270674567.3177.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-07 21:33 ` gg-B3jsHfKwJfLR7s880joybQ
[not found] ` <4BBCFA28.2030101-B3jsHfKwJfLR7s880joybQ@public.gmane.org>
2010-04-07 22:49 ` Trond Myklebust
[not found] ` <1270680542.6995.21.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-08 21:03 ` gg-B3jsHfKwJfLR7s880joybQ
[not found] ` <4BBE448A.3050408-B3jsHfKwJfLR7s880joybQ@public.gmane.org>
2010-04-08 21:33 ` Trond Myklebust
[not found] ` <1270762431.7276.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-09 12:09 ` gg-B3jsHfKwJfLR7s880joybQ
[not found] ` <4BBF18E5.5080306-B3jsHfKwJfLR7s880joybQ@public.gmane.org>
2010-04-09 12:30 ` Trond Myklebust
2010-04-07 22:44 ` Bernd Schubert
2010-04-12 19:44 ` J. Bruce Fields
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=20100407192025.GH26072@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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