public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Razik <linux@razik.name>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jim Rees <rees@umich.edu>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [BUG?] Maybe NFS bug since 2.6.37 on SPARC64
Date: Fri, 4 Nov 2011 14:57:58 +0000 (GMT)	[thread overview]
Message-ID: <1320418678.59917.YahooMailNeo@web24712.mail.ird.yahoo.com> (raw)
In-Reply-To: <06799B7D-54CD-41D8-934A-F9C78B23677C@oracle.com>

>>  It would be very sad with these nice Oracle (SUN) machines if no one could 

> use them because of this bug.
> 
> If you boot via tftp, I bet this problem will go away because the network 
> interface will be working by the time the NFSROOT mount is attempted.

Yes this could be a workaround but there is another problem with boot via tftp (and OpenBoot) which another team member is trying to solve...


> The NFSROOT code assumes that if kernel IP configuration worked, then the NIC is 
> already up.  That is clearly not the case if you boot from your local disk.

Yes, that's surely not the standard way: To mount nfsroot although you have a local disk...


>>  Do you know a kernel developer who maybe would try to write a patch for 
> this problem?
>>  Or do you have another idea what I could do?
> 
> As for a patch: no-one can write a patch unless we understand precisely why the 
> first RPC fails.  I already explained how to add a line or two to 
> fs/nfs/nfsroot.c to give us more information.  If you need a patch to do this, I 
> can send one later today.
> 
> I might be able to reproduce it here, now that I understand your set up, but it 
> would require building a partial NFSROOT environment.  I can't get to that 
> until next week.
> 

If you have the time for the patch, it would be very nice! Otherwise I'll try it as soon as I can.
The problem is that the system should work as soon as possible. So it would be nice to have a work around.
In parallel, I'll give you all information I have and test all patches you give me as long as you all are interested.

So now I'm trying the proposed workaroundsand after that I'll try to add the lines you wrote about (ASAP)...

Regards,
Lukas

  reply	other threads:[~2011-11-04 15:04 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 19:43 [BUG?] Maybe NFS bug since 2.6.37 on SPARC64 Lukas Razik
2011-11-03 20:54 ` Trond Myklebust
2011-11-03 21:10   ` Chuck Lever
2011-11-03 21:11   ` Jim Rees
2011-11-03 21:16     ` Chuck Lever
2011-11-03 21:37       ` Lukas Razik
2011-11-03 21:51         ` Chuck Lever
2011-11-03 23:09           ` Lukas Razik
2011-11-03 23:59             ` Jim Rees
2011-11-04  0:59               ` Lukas Razik
2011-11-04  1:06             ` Chuck Lever
2011-11-04  1:33               ` Lukas Razik
2011-11-04  9:44               ` Lukas Razik
2011-11-04 13:20                 ` Jim Rees
2011-11-04 14:01                   ` Chuck Lever
2011-11-04 14:09                     ` Myklebust, Trond
2011-11-04 14:24                       ` J. Bruce Fields
2011-11-04 14:46                     ` Jim Rees
2011-11-04 15:02                       ` Lukas Razik
2011-11-04 15:18                       ` Myklebust, Trond
2011-11-04 15:46                       ` Lukas Razik
2011-11-04 22:55                         ` Chuck Lever
2011-11-04 23:17                           ` Lukas Razik
2011-11-04 13:54                 ` Chuck Lever
2011-11-04 14:57                   ` Lukas Razik [this message]
2011-11-04 16:56                   ` Lukas Razik
2011-11-04 17:55                   ` Lukas Razik
2011-11-04 23:15                     ` NFSROOT mount fails on SPARC after 2.6.37 Chuck Lever
2011-11-05  2:03                       ` David Miller
2011-11-05  2:38                         ` Trond Myklebust
2011-11-04 23:40                   ` [BUG?] Maybe NFS bug since 2.6.37 on SPARC64 Lukas Razik
2011-11-05  1:19                     ` Trond Myklebust
2011-11-05  1:52                       ` Lukas Razik
2011-11-05  2:14                       ` Lukas Razik
2011-11-05  2:30                         ` Trond Myklebust
2011-11-05  2:31                         ` Trond Myklebust
2011-11-05  2:31                         ` Trond Myklebust
2011-11-05  3:51                           ` Lukas Razik
2011-11-05 13:05                             ` Jim Rees
2011-11-12 11:35                               ` Lukas Razik
2011-11-12 18:49                                 ` Jim Rees
2011-11-12 21:06                                   ` Chuck Lever
2011-11-13  1:03                                     ` Lukas Razik
2011-11-13 19:32                                       ` Chuck Lever
2011-11-13 21:28                                         ` Lukas Razik
2011-11-13 22:19                                           ` Lukas Razik
2011-11-14 15:31                                             ` Chuck Lever
2011-11-03 21:18   ` Lukas Razik
2011-11-03 21:38     ` Jim Rees
2011-11-03 21:58       ` Lukas Razik

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=1320418678.59917.YahooMailNeo@web24712.mail.ird.yahoo.com \
    --to=linux@razik.name \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox