Return-Path: Received: from rcsinet10.oracle.com ([148.87.113.121]:22657 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932337Ab1CWOyt convert rfc822-to-8bit (ORCPT ); Wed, 23 Mar 2011 10:54:49 -0400 Subject: Re: [bisect] kernel 2.6.38 regression with root nfs mounting Content-Type: text/plain; charset=us-ascii From: Chuck Lever In-Reply-To: Date: Wed, 23 Mar 2011 10:54:39 -0400 Cc: Trond.Myklebust@netapp.com, broonie@opensource.wolfsonmicro.com, bdowning@lavos.net, linux-nfs@vger.kernel.org, LKML Message-Id: <8F19F0FE-0800-4C45-B857-1C682CF6A30D@oracle.com> References: <43F07477-9075-444D-9BBB-368650538EA8@oracle.com> <977C528D-4540-4EB2-92F9-6DAF357D8C81@oracle.com> To: Belisko Marek Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 On Mar 23, 2011, at 10:30 AM, Belisko Marek wrote: > On Wed, Mar 23, 2011 at 3:06 PM, Chuck Lever wrote: >> >> On Mar 23, 2011, at 9:46 AM, Belisko Marek wrote: >> >>> On Wed, Mar 23, 2011 at 2:44 PM, Chuck Lever wrote: >>>> >>>> What does "rpcinfo -p 10.146.1.21" output look like? Is NFS over UDP enabled on your server? >>> program vers proto port >>> 100000 2 tcp 111 portmapper >>> 100000 2 udp 111 portmapper >>> 100024 1 udp 40517 status >>> 100024 1 tcp 51397 status >>> 100021 1 udp 44516 nlockmgr >>> 100021 3 udp 44516 nlockmgr >>> 100021 4 udp 44516 nlockmgr >>> 100021 1 tcp 55152 nlockmgr >>> 100021 3 tcp 55152 nlockmgr >>> 100021 4 tcp 55152 nlockmgr >>> 100003 2 tcp 2049 nfs >>> 100003 3 tcp 2049 nfs >>> 100003 4 tcp 2049 nfs >>> 100227 2 tcp 2049 >>> 100227 3 tcp 2049 >>> 100003 2 udp 2049 nfs >>> 100003 3 udp 2049 nfs >>> 100003 4 udp 2049 nfs The server is advertising NFS over UDP. Why can't a client access your server via UDP? What happens if you perform a normal post-boot mount of this file system via UDP? >>> 100227 2 udp 2049 >>> 100227 3 udp 2049 >>> 100005 1 udp 58278 mountd >>> 100005 1 tcp 37178 mountd >>> 100005 2 udp 58278 mountd >>> 100005 2 tcp 37178 mountd >>> 100005 3 udp 58278 mountd >>> 100005 3 tcp 37178 mountd >> >> Can you boot if you specify either the "tcp" or "proto=tcp" NFSROOT mount options? > When add proto=tcp to bootargs it boot fine > (....nfsroot=10.146.1.21:/home/open-nandra/rootfs,proto=tcp....). >> Perhaps a network trace would be probative. Capture on the server with "tcpdump -s0 -w /tmp/foo ip 10.146.1.199" (untested, but I think you get the idea) while the client is attempting to boot, and post. > Log is attached in attachment (too big 4.8M). Correct form is: tcpdump > -s0 -w /tmp/foo host 10.146.1.199 Received. I should have been clear: Please capture a non-working client boot attempt. To reduce the size of the attachment, strip the TFTP packets before sending, and please gzip the file. -- Chuck Lever chuck[dot]lever[at]oracle[dot]com