All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Hawkins <chawkins-eCVT+wl/HiBBDgjK7y7TUQ@public.gmane.org>
To: Shehjar Tikoo <shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Returning error to app on TCP disconnect
Date: Tue, 08 Jun 2010 08:02:41 -0400 (EDT)	[thread overview]
Message-ID: <488124.741275998561110.JavaMail.javamailuser@localhost> (raw)
In-Reply-To: <5462028.721275998477790.JavaMail.javamailuser@localhost>

Hi Shejar, what about the "soft" mount option on the client side, and possibly "intr"? Maybe I am misunderstanding your goal but it sounds like that is what you want. 

Chris  

----- "Shehjar Tikoo" <shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org> wrote:

> Hi all
> 
> I am working on a setup where when a nfsv3 server goes down, the dd
> that 
> is running on the NFS mount point, gets an error on any syscall 
> performed on that mount point, say a write () to a file on that
> mount.
> 
> I've tried setting the timeo and retrans options at mount but that
> does 
> not seem to work in this case. The how-to on linux-nfs site confirms 
> that the nfs client just waits for the server to come back up after 
> retrans number of requests.
> 
> Is there a way to have the app receive an EIO or any other error on
> TCP 
> disconnect?
> 
> Thanks
> -Shehjar
> --
> 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  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2010-06-08 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5462028.721275998477790.JavaMail.javamailuser@localhost>
2010-06-08 12:02 ` Christopher Hawkins [this message]
2010-06-08 11:36 Returning error to app on TCP disconnect Shehjar Tikoo

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=488124.741275998561110.JavaMail.javamailuser@localhost \
    --to=chawkins-ecvt+wl/hibbdgjk7y7tuq@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.