Messages in this thread |  | | Subject | Re: Blocking v/s Non-blocking NFS (and iSCSI) file reads/writes. | From | Trond Myklebust <> | Date | 08 Sep 2001 13:24:32 +0200 |
| |
>>>>> " " == 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |