From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ben Greear <greearb@candelatech.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Blocking v/s Non-blocking NFS (and iSCSI) file reads/writes.
Date: 08 Sep 2001 13:24:32 +0200 [thread overview]
Message-ID: <shsu1yencwf.fsf@charged.uio.no> (raw)
In-Reply-To: <3B992F7D.4E07D59B@candelatech.com>
In-Reply-To: Ben Greear's message of "Fri, 07 Sep 2001 13:35:09 -0700"
>>>>> " " == Ben Greear <greearb@candelatech.com> writes:
> So, does select() work for NFS reads? (IE: I open a
> file-descriptor on an NFS mounted file system, and start
> reading. The network goes down. Will select() start not
> marking that file as read/write-able?)
No.
> If I set the file descriptor to be O_NONBLOCK, will it return
> immediately if the network is down (regardless of what select
> told me)?
No.
The NFS layer knows nothing at all about the network. It relies on the
RPC layer to handle all that for it. There are 2 ways in which it can
do this:
1) keep the NFS layer in the dark (using the 'hard' mount option)
2) pass an error back which then propagates back through NFS to the
user (the 'soft' mount option).
Cheers,
Trond
prev parent reply other threads:[~2001-09-08 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 20:35 Blocking v/s Non-blocking NFS (and iSCSI) file reads/writes Ben Greear
2001-09-08 11:24 ` Trond Myklebust [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=shsu1yencwf.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox