[lkml]   [2001]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Blocking v/s Non-blocking NFS (and iSCSI) file reads/writes.
>>>>> " " == Ben Greear <> 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?)


> 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)?


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).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:02    [W:0.029 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site