public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chacko <peterchacko35@gmail.com>
To: Whoop Whouzer <tiredandnumb@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs client performance while server is down
Date: Sat, 23 Jan 2010 21:27:44 +0530	[thread overview]
Message-ID: <1f808b4a1001230757i2027d32dxb48482ea7bf8e4ee@mail.gmail.com> (raw)
In-Reply-To: <d7f0b3a81001230745h18dbb14fi42f28adff0c45294-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Which client OS you observed this behavior ?  This has nothing to do
NFS design, and its purely stateless...Its upto the client OS
implementation about aspects like how to deal with local IO, when NFS
share gets  disconnected..

May be a VFS bug on the local OS you found this problem ..

thanks

On Sat, Jan 23, 2010 at 9:15 PM, Whoop Whouzer <tiredandnumb@gmail.com>=
 wrote:
> Howdy,
>
> I was wondering why nfs is designed in such a way that the performanc=
e
> of an nfs client machine gets very bad when the nfs server is offline=
?
> This is even the case with a soft mount (either via mount or fstab).
> Just about every application that requires disk access (not talking
> about nfs share acces) gets really slow to unresponsive. For instance
> nautilus becomes unresponsive when displaying the contents of any
> folder on the local disk,
> playing movie files (stored on local disk) let totem or vlc get stuck
> on set intervals, even the terminal becomes unresponsive at times.
>
> I could understand that these problems would occur while accessing th=
e
> nfs share directoiourry while the server is offline, but why for tota=
lly
> unrelated directories?
>
> I have experienced this behaviour on various distro's, and also found
> various bug reports on this issue, they don't seem to get solved as
> this is viewed as nfs design.
> I see this as a flaw because clients are totally dependent on the
> server. This would be less of a deal if the entire home directory
> would be stored on nfs (although I even think some sort of
> synchronisation technology could and should be implemented in this
> case). It is a bit odd that (technically) one machine serving some
> "useless" files to a non-trivial directory on client machines can tak=
e
> down these client machines.
>
> For me the preferred functionality would be:
> *If an nfs server gets offline the client's nfs share becomes
> unaccessible, but local directories and applications (that only
> require local disk access) stay responsive.
> *If an nfs server gets online (after being offline while the client
> has not been restarted) the nfs share becomes reconnected.
>
> regards,
> Whoop
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>

  parent reply	other threads:[~2010-01-23 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23 15:45 nfs client performance while server is down Whoop Whouzer
     [not found] ` <d7f0b3a81001230745h18dbb14fi42f28adff0c45294-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-23 15:57   ` Peter Chacko [this message]
2010-01-23 16:27     ` Whoop Whouzer
     [not found]       ` <d7f0b3a81001230827y52727993nf60210ae610643b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-24 21:34         ` Muntz, Daniel
     [not found]           ` <7A24DF798E223B4C9864E8F92E8C93EC0527810C-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2010-01-24 22:03             ` Whoop Whouzer
2010-01-25  0:09             ` Whoop Whouzer
2010-01-25 16:48               ` Chuck Lever
2010-01-25 19:02                 ` Whoop Whouzer
     [not found]                   ` <d7f0b3a81001251102p5e631706jfd9f147a00487061-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 19:08                     ` Chuck Lever
     [not found]                       ` <d7f0b3a81001251138h30e25428o25db9bc8c0884636@mail.gmail.com>
     [not found]                         ` <d7f0b3a81001251138h30e25428o25db9bc8c0884636-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 19:48                           ` Whoop Whouzer
2010-01-25 21:01                           ` Chuck Lever
2010-01-25 21:18                             ` Whoop Whouzer
     [not found]                               ` <d7f0b3a81001251318k42de9be2qe54f83bbd86cabb8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 21:26                                 ` Chuck Lever
2010-01-25 23:03                                   ` Whoop Whouzer
2010-01-26 23:21                       ` J. Bruce Fields
2010-01-27  0:40                         ` Whoop Whouzer
2010-01-27 17:10                           ` J. Bruce Fields
2010-01-27 18:23                         ` Chuck Lever
2010-01-27 18:40                           ` Trond Myklebust
2010-01-27 18:47                             ` Whoop Whouzer
2010-01-27 19:09                               ` Trond Myklebust
2010-01-27 19:25                                 ` Whoop Whouzer
2010-01-27 19:30                                   ` Ray Van Dolson
2010-01-27 19:31                                   ` Peter Staubach

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=1f808b4a1001230757i2027d32dxb48482ea7bf8e4ee@mail.gmail.com \
    --to=peterchacko35@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tiredandnumb@gmail.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