Return-Path: Received: from metis.ext.pengutronix.de ([92.198.50.35]:46726 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754770Ab0L3TSw (ORCPT ); Thu, 30 Dec 2010 14:18:52 -0500 Date: Thu, 30 Dec 2010 20:18:46 +0100 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Trond Myklebust Cc: Linus Torvalds , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: still nfs problems [Was: Linux 2.6.37-rc8] Message-ID: <20101230191846.GB14221@pengutronix.de> References: <20101230171453.GA5787@pengutronix.de> <1293731992.4919.5.camel@heimdal.trondhjem.org> Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <1293731992.4919.5.camel@heimdal.trondhjem.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 Hi Trond, On Thu, Dec 30, 2010 at 12:59:52PM -0500, Trond Myklebust wrote: > On Thu, 2010-12-30 at 18:14 +0100, Uwe Kleine-K?nig wrote: > > I wonder if the nfs-stuff is considered to be solved, because I still > > see strange things. > > > > During boot my machine sometimes (approx one out of two times) hangs with > > the output pasted below on Sysctl-l. The irq > > > > I'm not 100% sure it's related, but at least it seems to hang in > > nfs_readdir. (When the serial irq happend that triggered the sysrq the > > program counter was at 0xc014601c, which is fs/nfs/dir.c:647 for me.) > > > > This is on 2.6.37-rc8 plus some patches for machine support on an ARM > > machine. > > Ccing linux-nfs@vger.kernel.org Yeah, good idea. I had that ~2min after sending my report during dinner, sorry :-\ > What filesystem are you exporting on the server? What is the NFS > version? Is this nfsroot, autofs or an ordinary nfs mount? This is an nfsroot of /home/ukl/nfsroot/tx28 which is a symlink to a directory on a different partition. I don't know the filesystem of my homedir as it resides on a server I have no access to, but I asked the admin, so I can follow up with this info later (I'd suspect ext3, too). The real root directory is on ext3 (rw,noatime). The serving nfs-server is Debian's nfs-kernel-server 1:1.2.2-1. nfs-related kernel parameters are ip=dhcp root=/dev/nfs nfsroot=192.168.23.2:/home/ukl/nfsroot/tx28,v3,tcp I hope this answers your questions. If not, please ask. I tried without the symlink and saw some different errors, e.g. starting splashutils daemon.../etc/rc.d/S00splashutils: line 50: //sbin/fbsplashd.static: Unknown error 521 (this is the init script that hung before) and [ 6.160000] NFS: server 192.168.23.2 error: fileid changed [ 6.160000] fsid 0:c: expected fileid 0x33590a4, got 0x4d11bedc but no hang as before. So maybe it's related to the symlink? I don't know if testing that further would help or just waste of my time, so please let me know if I can help you and how. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |