public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: nfs + Reiser4
Date: Wed, 07 Apr 2010 18:49:02 -0400	[thread overview]
Message-ID: <1270680542.6995.21.camel@localhost.localdomain> (raw)
In-Reply-To: <4BBCFA28.2030101-B3jsHfKwJfLR7s880joybQ@public.gmane.org>

On Wed, 2010-04-07 at 23:33 +0200, gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org wrote: 
> Some more info on the machines in question.
> 
> server: gentoo linux 2.6.29 kernel patched for R4 
> .net-fs/nfs-utils-1.2.1  Recently added nfs4 to existing nfs3 in kernel. 
> This did not seem to improve/deteriorate the problem. This has been an 
> issue ever since I used nfs to remote boot the client.
> 
> Client. ARM SBC also running 2.6.29 nfs3. Similar issues seen when 
> running manufacturer's 2.4 kernel. Suggests problem is on server.
> 
> Redboot bootstrap loads kernel via http then boots with nfsroot supplied 
> by server.
> 
> All specific issues related here are as seen yesterday with both running 
> 2.6.29.
> 
> The set up is damn near unusable as it is behaving now . Files are 
> constantly out of sync. Changes seem to stay or disappear in a more or 
> less arbitrary fashion (ie no percievable repeatable pattern or cause). 
> Files often get some kind of merge state which is neither the state on 
> the server , nor the last saved state on the client.
> 
> /dev/root on / type nfs
> (rw,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nointr,nolock,\proto=udp,timeo=\
> 11,retrans=3,sec=sys,addr=192.168.1.3)
> 
> I note vers=2 here, does this maybe indicate some trouble with the 
> initial negotiation and fallback to nfs2 ?
> 
> I don't have one clear , reproducible problem because the results are so 
> erratic. But just editting a file with vi on the client and reopening it 
> will give incorrect results 8 time out of 10.
> 
> The reboot issue killed me. I thought is desperation that that would at 
> least mean I got a clean copy.

OK, so clearly not a userspace NFS issue then.

Just out of interest, are you able to reproduce this problem with other
underlying filesystems? Reiser4 has never been merged into the mainline
kernel, so I doubt that any one of us has a test setup.

Cheers
  Trond


  parent reply	other threads:[~2010-04-07 22:49 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
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 [this message]
     [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=1270680542.6995.21.camel@localhost.localdomain \
    --to=trond.myklebust@fys.uio.no \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=gg-B3jsHfKwJfLR7s880joybQ@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