mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chakri n" <chakriin5@gmail.com>
To: "Trond Myklebust" <Trond.Myklebust@netapp.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] NFS on loopback locks up entire system(2.6.23-rc6)?
Date: Fri, 21 Sep 2007 11:06:13 -0700	[thread overview]
Message-ID: <92cbf19b0709211106n12b1b4ecxc0d415aa097d21b2@mail.gmail.com> (raw)
In-Reply-To: <1190391881.6680.73.camel@heimdal.trondhjem.org>

Isn't this a strict requirement from client side, asking to guarantee
that a server stays up all the time?

I have seen many cases, where people go and directly change IP of
their NFS filers or servers worrying least about the clients using
them.

Can we get around with some sort of congestion logic?

Thanks
--Chakri

On 9/21/07, Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> On Fri, 2007-09-21 at 09:20 -0700, Chakri n wrote:
> > Thanks.
> >
> > I was using flock (BSD locking) and I think the problem should be
> > solved if I move my application to use POSIX locks.
>
> Yup.
>
> > And any option to avoid processes waiting indefinitely to free pages
> > from NFS requests waiting on unresponsive NFS server?
>
> The only solution I know of is to use soft mounts, but that brings
> another set of problems:
>      1. most applications don't know how to recover safely from an EIO
>         error.
>      2. You lose data.
>
> Cheers
>   Trond
>

  reply	other threads:[~2007-09-21 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  0:22 Chakri n
2007-09-21  0:43 ` Trond Myklebust
2007-09-21  3:12   ` Chakri n
2007-09-21 12:47     ` J. Bruce Fields
2007-09-21 14:13     ` [NFS] " Trond Myklebust
2007-09-21 16:20       ` Chakri n
2007-09-21 16:24         ` Trond Myklebust
2007-09-21 18:06           ` Chakri n [this message]
2007-09-21 18:14             ` Trond Myklebust
2007-09-22  6:28               ` Chakri n
2007-10-06  7:35   ` Pavel Machek

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=92cbf19b0709211106n12b1b4ecxc0d415aa097d21b2@mail.gmail.com \
    --to=chakriin5@gmail.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®