NFS problems with 2.6.4-rc1-mm2

NFS problems with 2.6.4-rc1-mm2

[Peter Zijlstra]

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

Hi,

I've just build and booted 2.6.4-rc1-mm2, and mounting my NFS exports
works. however when I try to unzip a file over those mount the process
freezes over and any other IO to that mount results in more stuck
processes. SIGKILL will not remove the processes, only reboot will
manage.

dmesg reports like:

nfs: server 192.168.0.1 not responding, timed out

which is total nonsense, because all other hosts on the network can
access the exports just fine.

I'm about to back out all nfs patches from the broken-out patch set to
see what that does for me.

Peter Zijlstra

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: NFS problems with 2.6.4-rc1-mm2

[Peter Zijlstra]

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

I'm amazed at the total lack of information I managed to put into it ;-)

Its a dual athlon machine, nfs v3 over tcp. nfsd is run on vanilla
2.4.22 and reports no problems. (yes I know I should upgrade that
machine but its not exposed to the outside world).

anyway,. I played about a bit and it's in one of these patches:

#nfs-remove-XID-spinlock.patch
#nfs-misc-rpc-fixes.patch
#nfs-improved-writeback-strategy.patch
#nfs-simplify-config-options.patch
#nfs-fix-msync.patch
#nfs-mount-return-useful-errors.patch
#nfs-misc-minor-fixes.patch
#nfs-lockd-sync-01.patch
#nfs-lockd-sync-02.patch
#nfs-lockd-sync-03.patch
#nfs-lockd-sync-04.patch
#nfs-rpc-remove-redundant-memset.patch
#nfs-tunable-rpc-slot-table.patch
#nfs-short-read-fix.patch

I'll do a binary search through these patches and report those that seem
to cause the problem.

Peter Zijlstra


On Thu, 2004-03-04 at 21:07, Peter Zijlstra wrote:
> Hi,
> 
> I've just build and booted 2.6.4-rc1-mm2, and mounting my NFS exports
> works. however when I try to unzip a file over those mount the process
> freezes over and any other IO to that mount results in more stuck
> processes. SIGKILL will not remove the processes, only reboot will
> manage.
> 
> dmesg reports like:
> 
> nfs: server 192.168.0.1 not responding, timed out
> 
> which is total nonsense, because all other hosts on the network can
> access the exports just fine.
> 
> I'm about to back out all nfs patches from the broken-out patch set to
> see what that does for me.
> 
> Peter Zijlstra

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: NFS problems with 2.6.4-rc1-mm2

[Peter Zijlstra]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

The bad guy is: 
	nfs-tunable-rpc-slot-table.patch
without that patch nfs works fine for me.

As said I use NFSv3 over TCP, and its a SMP machine
that has the problem, I haven't tried any UP box.

Peter

On Fri, 2004-03-05 at 23:37, Andrew Morton wrote:
> Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > I played about a bit and it's in one of these patches:
> > 
> > #nfs-remove-XID-spinlock.patch
> > #nfs-misc-rpc-fixes.patch
> > #nfs-improved-writeback-strategy.patch
> > #nfs-simplify-config-options.patch
> > #nfs-fix-msync.patch
> > #nfs-mount-return-useful-errors.patch
> > #nfs-misc-minor-fixes.patch
> > #nfs-lockd-sync-01.patch
> > #nfs-lockd-sync-02.patch
> > #nfs-lockd-sync-03.patch
> > #nfs-lockd-sync-04.patch
> > #nfs-rpc-remove-redundant-memset.patch
> > #nfs-tunable-rpc-slot-table.patch
> > #nfs-short-read-fix.patch
> > 
> > I'll do a binary search through these patches and report those that seem
> > to cause the problem.
> 
> Thanks, that would be muchly appreciated.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: NFS problems with 2.6.4-rc1-mm2

[Trond Myklebust]

På lau , 06/03/2004 klokka 06:10, skreiv Peter Zijlstra:
> The bad guy is: 
> 	nfs-tunable-rpc-slot-table.patch
> without that patch nfs works fine for me.
> 
> As said I use NFSv3 over TCP, and its a SMP machine
> that has the problem, I haven't tried any UP box.

I have no such problems on my SMP boxes. Could you try just resetting
the default TCP slot size to 16?

sysctl -w sunrpc.tcp_slot_table_entries=16

that should in theory give you the same settings as without the above
patch.

Cheers,
  Trond