All of lore.kernel.org
 help / color / mirror / Atom feed
From: gg-B3jsHfKwJfLR7s880joybQ@public.gmane.org
To: nfs@lists.sourceforge.net
Subject: nfs + Reiser4
Date: Tue, 06 Apr 2010 19:52:21 +0200	[thread overview]
Message-ID: <op.vaq49joctxpshh@localhost.localdomain> (raw)

Hi,

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.


This is just one example of serious userablity issues. I have also seen a  
revert 10s later reopening the same file on the ARM.

Is this possibly related to R4 + nfs ?

TIA.

------------------------------------------------------------------------------
Download Intel&#174; 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


             reply	other threads:[~2010-04-06 18:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 17:52 gg-B3jsHfKwJfLR7s880joybQ [this message]
     [not found] ` <op.vaq49joctxpshh-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-07 17:34   ` nfs + Reiser4 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
     [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=op.vaq49joctxpshh@localhost.localdomain \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.