Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Network File Sharing--version 2 and 3

Network File Sharing--version 2 and 3

Ratings: (0)|Views: 7 |Likes:
Published by abhineet sharma
This three page document provides an understanding enough to start reading NFS implementation through RedHat customization guides etc. A sort of preamble you might say.
This three page document provides an understanding enough to start reading NFS implementation through RedHat customization guides etc. A sort of preamble you might say.

More info:

Published by: abhineet sharma on Jan 06, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/06/2012

pdf

text

original

 
Source: Network File System Version 2—Ohad Rodeh. Although a few things have beenadded to make meaning clearer.
 NFS has the
issue
of making the access of files over the network to communicate with thefile-system domestic in such a way that access of local system for its file-system iscomparable to that over network. FHS is implicitly involved here.
NFS is defined in terms of procedure calls
, their arguments etc from an RPC point of view.
XDR 
defines the size, byte order and alignment of basic data types which are going to flowover the network. The NFS implementation is divided under RPC and XDR. XDR is a datadefinition language. RPC calls use it—XDR translation procedures used to interpret RPC protocols.
NFS is stateless protocol set
 —parameters passed to procedure calls have completeinformation necessary to implement it; server does not need to remember a thing. This particularly makes crash recovery very easy because crash of server does not kill proceduresclient waits for. But this means one to understand how much parameters can supply, whereis our 
bottleneck 
.
File Handle(fhandle or fh)
: This is procedure
 parameter 
provided by server and used byclient to reference a file. It is opaque—neither contents nor beyond is visible.
We won't go further into the construct of procedures.
Issues with NFSv2:
 No asynchronous read/write
write throughput bottleneck.
 
Major Changes:
READDIRPLUS
 procedure returns fhandle and attributes rendering LOOKUP procedureuseless.
Block concept was dropped for Byte concept.The server is still stateless and there is
weak cache consitency
(meaning whenever a block ismodified at client, it is to be modified at server too and that the cache is affective for read traffic butnot the write traffic. Protocols like Alex protocol might be employed)
Problem with replaying non-idempotent request was not addressed.
The NFSv3 server expects only asynchronous writes, although supports synchronous ones too. Thisis basically because the protocol tends to flush unused(till
 stable storage
) data before taking new.

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->