linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jim Rees <rees@umich.edu>,
	Srinivas KANDAGATLA <srinivas.kandagatla@st.com>,
	<linux-nfs@vger.kernel.org>, <akpm@linux-foundation.org>,
	<mingo@redhat.com>, <neilb@suse.de>, <stuart.menefy@st.com>
Subject: Re: [RFC:PATCH 3.1.0] do_mount: Add mount retry option for nfs root mount.
Date: Wed, 25 Jan 2012 21:04:44 +0200	[thread overview]
Message-ID: <4F20524C.6030704@panasas.com> (raw)
In-Reply-To: <F96642BB-3C49-4E70-BFE9-E7549CDEDB55@oracle.com>

On 01/25/2012 08:52 PM, Chuck Lever wrote:
> 
> 
>>  I always thought that was inconsistent. With an hard mount NFS
>>  will never give up and will retry for ever freezing all IOers until
>>  the server came back. Only with root-mount it gives up.
> 
> Not true, user space mount can also give up. See nfs(5), the retry=
> option. This is not NFS I/O we're talking about here, there is no
> risk of data corruption. So "hard" versus "soft" does not apply.
> 

OK I see your point

>>  Please explain what is the benefits of giving up at all. Can a machine
>>  be at all usable without it's root? 
> 
> There are several different root file system options built into the
> kernel. NFSROOT is but one. Each is tried in succession. If NFSROOT
> never gives up, then the others that follow it are never tried.
> 

OK I did not know that. Thanks for the explanation, good to know.
In the few times I tried NFSROOT I never setup an alternative.

I wish that in the case that the NFSROOT is the only option it would
keep trying.

When the Kernel does not find it's root it panics, I know. If the sata
disk is not there, it's not there. But with NFSROOT there is a good chance it
will come up soon. (We all saw the same power outage and the server is slow
to boot)

I just think it could be more user friendly that's all

Thanks
Boaz

      reply	other threads:[~2012-01-25 19:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 14:50 [RFC:PATCH 3.1.0] do_mount: Add mount retry option for nfs root mount Srinivas KANDAGATLA
2012-01-25 15:45 ` Jim Rees
2012-01-26  7:56   ` Srinivas KANDAGATLA
2012-01-26  8:37     ` Boaz Harrosh
2012-01-26  8:51       ` Srinivas KANDAGATLA
2012-01-26 11:08         ` Boaz Harrosh
2012-01-26 14:35           ` Srinivas KANDAGATLA
2012-01-25 16:20 ` Boaz Harrosh
2012-01-25 18:32   ` Jim Rees
2012-01-25 18:51     ` Boaz Harrosh
2012-01-25 18:52     ` Chuck Lever
2012-01-25 19:04       ` Boaz Harrosh [this message]

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=4F20524C.6030704@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=akpm@linux-foundation.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@suse.de \
    --cc=rees@umich.edu \
    --cc=srinivas.kandagatla@st.com \
    --cc=stuart.menefy@st.com \
    /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;
as well as URLs for NNTP newsgroup(s).