Skip to contentSkip to conversation

nfs + Reiser4

DISCUSSION [email protected] 5 participants 16 messages Apr 6, 2010 – Apr 12, 2010 7 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore 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® 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

A message that is not in the archive (sent off-list or not yet received): op.vaq49joctxpshh-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]

#2 lore raw
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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?

--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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#3 lore raw
Quoted 17 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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.

Quoted 5 lines

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.

Signature · 15 lines
chuck[dot]lever[at]oracle[dot]com

------------------------------------------------------------------------------
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  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs
#4 lore raw
Quoted 18 lines · Chuck Lever
Quoted 17 lines · J. Bruce Fields
Quoted 15 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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.

Quoted 7 lines
Quoted 5 lines

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?

--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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#5 lore raw
Quoted 22 lines · J. Bruce Fields
Quoted 21 lines · Chuck Lever
Quoted 20 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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?

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

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.

This can be quite reproducible for NFSROOT and a quiescent server.

Signature · 15 lines
chuck[dot]lever[at]oracle[dot]com

------------------------------------------------------------------------------
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  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs
#6 lore raw
Quoted 28 lines · Chuck Lever
Quoted 27 lines · J. Bruce Fields
Quoted 25 lines · Chuck Lever
Quoted 17 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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.

Quoted 5 lines

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.

Quoted 8 lines
Quoted 3 lines

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.

Quoted 1 line

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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#7 lore raw
Quoted 38 lines · J. Bruce Fields
Quoted 28 lines · Chuck Lever
Quoted 27 lines · J. Bruce Fields
Quoted 25 lines · Chuck Lever
Quoted 17 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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.

Quoted 5 lines

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.

Quoted 8 lines
Quoted 3 lines

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.

Quoted 5 lines

Hm, OK.

Quoted 1 line

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.

OK. Some servers do.

Sounds like a server side network trace is in order.

Signature · 15 lines
chuck[dot]lever[at]oracle[dot]com

------------------------------------------------------------------------------
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  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs
#8 lore raw
In reply to J. Bruce Fields
Quoted 38 lines · J. Bruce Fields
Quoted 28 lines · Chuck Lever
Quoted 27 lines · J. Bruce Fields
Quoted 25 lines · Chuck Lever
Quoted 17 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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.

Quoted 5 lines

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.

Quoted 8 lines
Quoted 3 lines

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.

Quoted 7 lines

Hm, OK.

Quoted 1 line

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.

Is he perhaps using the Debian unfsd or some other user space nfs server?

Cheers
Trond

A message that is not in the archive (sent off-list or not yet received): 1270674567.3177.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]

#10 lore raw
Quoted 45 lines · Trond Myklebust
Quoted 44 lines · J. Bruce Fields
Quoted 28 lines · Chuck Lever
Quoted 27 lines · J. Bruce Fields
Quoted 25 lines · Chuck Lever
Quoted 17 lines · J. Bruce Fields
Quoted 8 lines · On Tue, Apr 06, 2010 at 07:52:21PM +0200…

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 :

Quoted 7 lines

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.

Quoted 5 lines

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.

Quoted 8 lines
Quoted 3 lines

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.

Quoted 1 line

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.

Quoted 9 lines
Quoted 1 line

--b.

Is he perhaps using the Debian unfsd or some other user space nfs server?

Cheers
Trond

Hi,

thanks for all the activity.

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.

Thanks for your interest.

A message that is not in the archive (sent off-list or not yet received): [email protected]

#12 lore raw
Quoted 29 lines · On Wed, 2010-04-07 at 23:33 +0200, [email protected]…

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 ?

Quoted 6 lines

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

A message that is not in the archive (sent off-list or not yet received): 1270680542.6995.21.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]

#14 lore raw
Quoted 37 lines · Trond Myklebust
Quoted 29 lines · On Wed, 2010-04-07 at 23:33 +0200, [email protected]…

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 ?

Quoted 6 lines

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.

Quoted 10 lines

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

OK , I just tried this on ext3 partition and I'm not seeing the erratic behaviour. So this may be down to a bad reaction between nfs and R4 as I suspected.

However, I am still seeing vers=2 , does this indicate some problem in initial negociation and a drop back to nfs2 ?

/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)

regards,

A message that is not in the archive (sent off-list or not yet received): [email protected]

#16 lore raw
Quoted 9 lines · On Thu, 2010-04-08 at 23:03 +0200, [email protected]…

OK , I just tried this on ext3 partition and I'm not seeing the erratic behaviour. So this may be down to a bad reaction between nfs and R4 as I suspected.

However, I am still seeing vers=2 , does this indicate some problem in initial negociation and a drop back to nfs2 ?

/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 believe that nfsroot always defaults to vers=2 and udp unless you explicitly set the 'nfsvers=3' and 'proto=tcp' mount options.

It also defaults to 4k rsize and wsize (set 'rsize=0,wsize=0' if you want the client to autonegotiate their values)...

Cheers
Trond

A message that is not in the archive (sent off-list or not yet received): 1270762431.7276.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]

#18 lore raw
Quoted 11 lines · Trond Myklebust
Quoted 9 lines · On Thu, 2010-04-08 at 23:03 +0200, [email protected]…

OK , I just tried this on ext3 partition and I'm not seeing the erratic behaviour. So this may be down to a bad reaction between nfs and R4 as I suspected.

However, I am still seeing vers=2 , does this indicate some problem in initial negociation and a drop back to nfs2 ?

/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)

Quoted 10 lines

I believe that nfsroot always defaults to vers=2 and udp unless you explicitly set the 'nfsvers=3' and 'proto=tcp' mount options.

It also defaults to 4k rsize and wsize (set 'rsize=0,wsize=0' if you want the client to autonegotiate their values)...

Cheers
Trond

Thanks,

I was refering to man nfs which states that nfs will always try nfs3 and if it fails falls back to ver 2. Maybe man nfs is not the definitive reference for what is in the kernel if this has changed recently.

I've pretty much concluded the main issues very nfs not playing well with reiser4. The doc suggests this is a gray area and indeed it seems to be pretty much untested since this kind of grossly bad behavious would not be missed.

I had some anomalies circa 2.6.20 that were less severe but the current state of play is frankly pretty unusable.

Since there seems to be an implied policy of not testing with any fs not in mainline kernel I'll just have to copy the nfs structure to an ext3 partition.

Thanks for you comments and help.

regards.

A message that is not in the archive (sent off-list or not yet received): [email protected]

#20 lore raw
Quoted 3 lines · On Fri, 2010-04-09 at 14:09 +0200, [email protected]…

I was refering to man nfs which states that nfs will always try nfs3 and if it fails falls back to ver 2. Maybe man nfs is not the definitive reference for what is in the kernel if this has changed recently.

The above is true for the ordinary 'mount' program, but is not true of nfsroot.

The fallback policy for mount is now managed entirely in userspace, and in recent versions of nfs-utils, you can configure whether you want nfsv4, nfsv3 or nfsv2 to be the default.

Cheers
Trond

#21 lore raw
In reply to a message not in the archive
Quoted 19 lines · On Tuesday 06 April 2010, [email protected] wrote:

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.

Quoted 4 lines

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 ?

Reminds me about an old bug report I wrote and which nobody ever cared about:

http://article.gmane.org/gmane.linux.nfs/9867/match=

------------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#22 lore raw
Quoted 20 lines · Bernd Schubert
Quoted 19 lines · On Tuesday 06 April 2010, [email protected] wrote:

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.

Quoted 8 lines
Quoted 4 lines

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 ?

Reminds me about an old bug report I wrote and which nobody ever cared about:

http://article.gmane.org/gmane.linux.nfs/9867/match=

On a possibly-too-quick skim, I think this could be explained by just stale cache data, possibly the result of poor ext3 time resolution. (Still a bug of some kind, but not as bizarre as the bug reported here.)

--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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs