%! %%BoundingBox: (atend) %%Pages: (atend) %%DocumentFonts: (atend) %%EndComments %%BeginProlog % % FrameMaker postscript_prolog 3.0, for use with FrameMaker 3.0 % This postscript_prolog file is Copyright (c) 1986-1991 Frame Technology % Corporation. All rights reserved. This postscript_prolog file may be % freely copied and distributed in conjunction with documents created using % FrameMaker. % NOTE % This file fixes the problem with NeWS printers dithering color output. % Any questions should be sent to mickey@magickingdom.eng.sun.com % % Known Problems: % Due to bugs in Transcript, the 'PS-Adobe-' is omitted from line 1 /FMversion (3.0) def % Set up Color vs. Black-and-White /FMPrintInColor { % once-thru loop gimmick % See if we're a NeWSprint printer /currentcanvas where { pop systemdict /separationdict known exit } if % originally had the following, which should always be false: % /currentcanvas where { % pop currentcanvas /Color known { % currentcanvas /Color get % exit % } if % } if systemdict /colorimage known systemdict /currentcolortransfer known and exit } loop def % Uncomment the following line to force b&w on color printer % /FMPrintInColor false def /FrameDict 195 dict def systemdict /errordict known not {/errordict 10 dict def errordict /rangecheck {stop} put} if % The readline in 23.0 doesn't recognize cr's as nl's on AppleTalk FrameDict /tmprangecheck errordict /rangecheck get put errordict /rangecheck {FrameDict /bug true put} put FrameDict /bug false put mark % Some PS machines read past the CR, so keep the following 3 lines together! currentfile 5 string readline 00 0000000000 cleartomark errordict /rangecheck FrameDict /tmprangecheck get put FrameDict /bug get { /readline { /gstring exch def /gfile exch def /gindex 0 def { gfile read pop dup 10 eq {exit} if dup 13 eq {exit} if gstring exch gindex exch put /gindex gindex 1 add def } loop pop gstring 0 gindex getinterval true } def } if /FMVERSION { FMversion ne { /Times-Roman findfont 18 scalefont setfont 100 100 moveto (FrameMaker version does not match postscript_prolog!) dup = show showpage } if } def /FMLOCAL { FrameDict begin 0 def end } def /gstring FMLOCAL /gfile FMLOCAL /gindex FMLOCAL /orgxfer FMLOCAL /orgproc FMLOCAL /organgle FMLOCAL /orgfreq FMLOCAL /yscale FMLOCAL /xscale FMLOCAL /manualfeed FMLOCAL /paperheight FMLOCAL /paperwidth FMLOCAL /FMDOCUMENT { array /FMfonts exch def /#copies exch def FrameDict begin 0 ne dup {setmanualfeed} if /manualfeed exch def /paperheight exch def /paperwidth exch def /yscale exch def /xscale exch def currenttransfer cvlit /orgxfer exch def currentscreen cvlit /orgproc exch def /organgle exch def /orgfreq exch def setpapername manualfeed {true} {papersize} ifelse {manualpapersize} {false} ifelse {desperatepapersize} if end } def /pagesave FMLOCAL /orgmatrix FMLOCAL /landscape FMLOCAL /FMBEGINPAGE { FrameDict begin /pagesave save def 3.86 setmiterlimit /landscape exch 0 ne def landscape { 90 rotate 0 exch neg translate pop } {pop pop} ifelse xscale yscale scale /orgmatrix matrix def gsave } def /FMENDPAGE { grestore pagesave restore end showpage } def /FMFONTDEFINE { FrameDict begin findfont ReEncode 1 index exch definefont FMfonts 3 1 roll put end } def /FMFILLS { FrameDict begin array /fillvals exch def end } def /FMFILL { FrameDict begin fillvals 3 1 roll put end } def /FMNORMALIZEGRAPHICS { newpath 0.0 0.0 moveto 1 setlinewidth 0 setlinecap 0 0 0 sethsbcolor 0 setgray } bind def /fx FMLOCAL /fy FMLOCAL /fh FMLOCAL /fw FMLOCAL /llx FMLOCAL /lly FMLOCAL /urx FMLOCAL /ury FMLOCAL /FMBEGINEPSF { end /FMEPSF save def /showpage {} def FMNORMALIZEGRAPHICS [/fy /fx /fh /fw /ury /urx /lly /llx] {exch def} forall fx fy translate rotate fw urx llx sub div fh ury lly sub div scale llx neg lly neg translate } bind def /FMENDEPSF { FMEPSF restore FrameDict begin } bind def FrameDict begin /setmanualfeed { %%BeginFeature *ManualFeed True statusdict /manualfeed true put %%EndFeature } def /max {2 copy lt {exch} if pop} bind def /min {2 copy gt {exch} if pop} bind def /inch {72 mul} def /pagedimen { paperheight sub abs 16 lt exch paperwidth sub abs 16 lt and {/papername exch def} {pop} ifelse } def /papersizedict FMLOCAL /setpapername { /papersizedict 14 dict def papersizedict begin /papername /unknown def /Letter 8.5 inch 11.0 inch pagedimen /LetterSmall 7.68 inch 10.16 inch pagedimen /Tabloid 11.0 inch 17.0 inch pagedimen /Ledger 17.0 inch 11.0 inch pagedimen /Legal 8.5 inch 14.0 inch pagedimen /Statement 5.5 inch 8.5 inch pagedimen /Executive 7.5 inch 10.0 inch pagedimen /A3 11.69 inch 16.5 inch pagedimen /A4 8.26 inch 11.69 inch pagedimen /A4Small 7.47 inch 10.85 inch pagedimen /B4 10.125 inch 14.33 inch pagedimen /B5 7.16 inch 10.125 inch pagedimen end } def /papersize { papersizedict begin /Letter {lettertray letter} def /LetterSmall {lettertray lettersmall} def /Tabloid {11x17tray 11x17} def /Ledger {ledgertray ledger} def /Legal {legaltray legal} def /Statement {statementtray statement} def /Executive {executivetray executive} def /A3 {a3tray a3} def /A4 {a4tray a4} def /A4Small {a4tray a4small} def /B4 {b4tray b4} def /B5 {b5tray b5} def /unknown {unknown} def papersizedict dup papername known {papername} {/unknown} ifelse get end /FMdicttop countdictstack 1 add def statusdict begin stopped end countdictstack -1 FMdicttop {pop end} for } def /manualpapersize { papersizedict begin /Letter {letter} def /LetterSmall {lettersmall} def /Tabloid {11x17} def /Ledger {ledger} def /Legal {legal} def /Statement {statement} def /Executive {executive} def /A3 {a3} def /A4 {a4} def /A4Small {a4small} def /B4 {b4} def /B5 {b5} def /unknown {unknown} def papersizedict dup papername known {papername} {/unknown} ifelse get end stopped } def /desperatepapersize { statusdict /setpageparams known { paperwidth paperheight 0 1 statusdict begin {setpageparams} stopped pop end } if } def /savematrix { orgmatrix currentmatrix pop } bind def /restorematrix { orgmatrix setmatrix } bind def /dmatrix matrix def /dpi 72 0 dmatrix defaultmatrix dtransform dup mul exch dup mul add sqrt def /freq dpi 18.75 div 8 div round dup 0 eq {pop 1} if 8 mul dpi exch div def /sangle 1 0 dmatrix defaultmatrix dtransform exch atan def /DiacriticEncoding [ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quotesingle /parenleft /parenright /asterisk /plus /comma /hyphen /period /slash /zero /one /two /three /four /five /six /seven /eight /nine /colon /semicolon /less /equal /greater /question /at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O /P /Q /R /S /T /U /V /W /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore /grave /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o /p /q /r /s /t /u /v /w /x /y /z /braceleft /bar /braceright /asciitilde /.notdef /Adieresis /Aring /Ccedilla /Eacute /Ntilde /Odieresis /Udieresis /aacute /agrave /acircumflex /adieresis /atilde /aring /ccedilla /eacute /egrave /ecircumflex /edieresis /iacute /igrave /icircumflex /idieresis /ntilde /oacute /ograve /ocircumflex /odieresis /otilde /uacute /ugrave /ucircumflex /udieresis /dagger /.notdef /cent /sterling /section /bullet /paragraph /germandbls /registered /copyright /trademark /acute /dieresis /.notdef /AE /Oslash /.notdef /.notdef /.notdef /.notdef /yen /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /ordfeminine /ordmasculine /.notdef /ae /oslash /questiondown /exclamdown /logicalnot /.notdef /florin /.notdef /.notdef /guillemotleft /guillemotright /ellipsis /.notdef /Agrave /Atilde /Otilde /OE /oe /endash /emdash /quotedblleft /quotedblright /quoteleft /quoteright /.notdef /.notdef /ydieresis /Ydieresis /fraction /currency /guilsinglleft /guilsinglright /fi /fl /daggerdbl /periodcentered /quotesinglbase /quotedblbase /perthousand /Acircumflex /Ecircumflex /Aacute /Edieresis /Egrave /Iacute /Icircumflex /Idieresis /Igrave /Oacute /Ocircumflex /.notdef /Ograve /Uacute /Ucircumflex /Ugrave /dotlessi /circumflex /tilde /macron /breve /dotaccent /ring /cedilla /hungarumlaut /ogonek /caron ] def /ReEncode { dup length dict begin { 1 index /FID ne {def} {pop pop} ifelse } forall 0 eq {/Encoding DiacriticEncoding def} if currentdict end } bind def /graymode true def /bwidth FMLOCAL /bpside FMLOCAL /bstring FMLOCAL /onbits FMLOCAL /offbits FMLOCAL /xindex FMLOCAL /yindex FMLOCAL /x FMLOCAL /y FMLOCAL /setpattern { /bwidth exch def /bpside exch def /bstring exch def /onbits 0 def /offbits 0 def freq sangle landscape {90 add} if {/y exch def /x exch def /xindex x 1 add 2 div bpside mul cvi def /yindex y 1 add 2 div bpside mul cvi def bstring yindex bwidth mul xindex 8 idiv add get 1 7 xindex 8 mod sub bitshift and 0 ne {/onbits onbits 1 add def 1} {/offbits offbits 1 add def 0} ifelse } setscreen {} settransfer offbits offbits onbits add div FMsetgray /graymode false def } bind def /grayness { FMsetgray graymode not { /graymode true def orgxfer cvx settransfer orgfreq organgle orgproc cvx setscreen } if } bind def /HUE FMLOCAL /SAT FMLOCAL /BRIGHT FMLOCAL /Colors FMLOCAL FMPrintInColor { /HUE 0 def /SAT 0 def /BRIGHT 0 def % array of arrays Hue and Sat values for the separations [HUE BRIGHT] /Colors [[0 0 ] % black [0 0 ] % white [0.00 1.0] % red [0.37 1.0] % green [0.60 1.0] % blue [0.50 1.0] % cyan [0.83 1.0] % magenta [0.16 1.0] % comment / yellow ] def /BEGINBITMAPCOLOR { BITMAPCOLOR} def /BEGINBITMAPCOLORc { BITMAPCOLORc} def /BEGINBITMAPTRUECOLOR { BITMAPTRUECOLOR } def /BEGINBITMAPTRUECOLORc { BITMAPTRUECOLORc } def /K { Colors exch get dup 0 get /HUE exch store 1 get /BRIGHT exch store HUE 0 eq BRIGHT 0 eq and {1.0 SAT sub setgray} {HUE SAT BRIGHT sethsbcolor} ifelse } def /FMsetgray { /SAT exch 1.0 exch sub store HUE 0 eq BRIGHT 0 eq and {1.0 SAT sub setgray} {HUE SAT BRIGHT sethsbcolor} ifelse } bind def } { /BEGINBITMAPCOLOR { BITMAPGRAY} def /BEGINBITMAPCOLORc { BITMAPGRAYc} def /BEGINBITMAPTRUECOLOR { BITMAPTRUEGRAY } def /BEGINBITMAPTRUECOLORc { BITMAPTRUEGRAYc } def /FMsetgray {setgray} bind def /K { pop } def } ifelse /normalize { transform round exch round exch itransform } bind def /dnormalize { dtransform round exch round exch idtransform } bind def /lnormalize { 0 dtransform exch cvi 2 idiv 2 mul 1 add exch idtransform pop } bind def /H { lnormalize setlinewidth } bind def /Z { setlinecap } bind def /fillvals FMLOCAL /X { fillvals exch get dup type /stringtype eq {8 1 setpattern} {grayness} ifelse } bind def /V { gsave eofill grestore } bind def /N { stroke } bind def /M {newpath moveto} bind def /E {lineto} bind def /D {curveto} bind def /O {closepath} bind def /n FMLOCAL /L { /n exch def newpath normalize moveto 2 1 n {pop normalize lineto} for } bind def /Y { L closepath } bind def /x1 FMLOCAL /x2 FMLOCAL /y1 FMLOCAL /y2 FMLOCAL /rad FMLOCAL /R { /y2 exch def /x2 exch def /y1 exch def /x1 exch def x1 y1 x2 y1 x2 y2 x1 y2 4 Y } bind def /RR { /rad exch def normalize /y2 exch def /x2 exch def normalize /y1 exch def /x1 exch def newpath x1 y1 rad add moveto x1 y2 x2 y2 rad arcto x2 y2 x2 y1 rad arcto x2 y1 x1 y1 rad arcto x1 y1 x1 y2 rad arcto closepath 16 {pop} repeat } bind def /C { grestore gsave R clip } bind def /FMpointsize FMLOCAL /F { FMfonts exch get FMpointsize scalefont setfont } bind def /Q { /FMpointsize exch def F } bind def /T { moveto show } bind def /RF { rotate 0 ne {-1 1 scale} if } bind def /TF { gsave moveto RF show grestore } bind def /P { moveto 0 32 3 2 roll widthshow } bind def /PF { gsave moveto RF 0 32 3 2 roll widthshow grestore } bind def /S { moveto 0 exch ashow } bind def /SF { gsave moveto RF 0 exch ashow grestore } bind def /B { moveto 0 32 4 2 roll 0 exch awidthshow } bind def /BF { gsave moveto RF 0 32 4 2 roll 0 exch awidthshow grestore } bind def /G { gsave newpath normalize translate 0.0 0.0 moveto dnormalize scale 0.0 0.0 1.0 5 3 roll arc closepath fill grestore } bind def /A { gsave savematrix newpath 2 index 2 div add exch 3 index 2 div sub exch normalize 2 index 2 div sub exch 3 index 2 div add exch translate scale 0.0 0.0 1.0 5 3 roll arc restorematrix stroke grestore } bind def /x FMLOCAL /y FMLOCAL /w FMLOCAL /h FMLOCAL /xx FMLOCAL /yy FMLOCAL /ww FMLOCAL /hh FMLOCAL /FMsaveobject FMLOCAL /FMoptop FMLOCAL /FMdicttop FMLOCAL /BEGINPRINTCODE { /FMdicttop countdictstack 1 add def /FMoptop count 4 sub def /FMsaveobject save def userdict begin /showpage {} def FMNORMALIZEGRAPHICS 3 index neg 3 index neg translate } bind def /ENDPRINTCODE { count -1 FMoptop {pop pop} for countdictstack -1 FMdicttop {pop end} for FMsaveobject restore } bind def /gn { 0 { 46 mul cf read pop 32 sub dup 46 lt {exit} if 46 sub add } loop add } bind def /str FMLOCAL /cfs { /str sl string def 0 1 sl 1 sub {str exch val put} for str def } bind def /ic [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0223 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0223 0 {0 hx} {1 hx} {2 hx} {3 hx} {4 hx} {5 hx} {6 hx} {7 hx} {8 hx} {9 hx} {10 hx} {11 hx} {12 hx} {13 hx} {14 hx} {15 hx} {16 hx} {17 hx} {18 hx} {19 hx} {gn hx} {0} {1} {2} {3} {4} {5} {6} {7} {8} {9} {10} {11} {12} {13} {14} {15} {16} {17} {18} {19} {gn} {0 wh} {1 wh} {2 wh} {3 wh} {4 wh} {5 wh} {6 wh} {7 wh} {8 wh} {9 wh} {10 wh} {11 wh} {12 wh} {13 wh} {14 wh} {gn wh} {0 bl} {1 bl} {2 bl} {3 bl} {4 bl} {5 bl} {6 bl} {7 bl} {8 bl} {9 bl} {10 bl} {11 bl} {12 bl} {13 bl} {14 bl} {gn bl} {0 fl} {1 fl} {2 fl} {3 fl} {4 fl} {5 fl} {6 fl} {7 fl} {8 fl} {9 fl} {10 fl} {11 fl} {12 fl} {13 fl} {14 fl} {gn fl} ] def /sl FMLOCAL /val FMLOCAL /ws FMLOCAL /im FMLOCAL /bs FMLOCAL /cs FMLOCAL /len FMLOCAL /pos FMLOCAL /ms { /sl exch def /val 255 def /ws cfs /im cfs /val 0 def /bs cfs /cs cfs } bind def 400 ms /ip { is 0 cf cs readline pop { ic exch get exec add } forall pop } bind def /wh { /len exch def /pos exch def ws 0 len getinterval im pos len getinterval copy pop pos len } bind def /bl { /len exch def /pos exch def bs 0 len getinterval im pos len getinterval copy pop pos len } bind def /s1 1 string def /fl { /len exch def /pos exch def /val cf s1 readhexstring pop 0 get def pos 1 pos len add 1 sub {im exch val put} for pos len } bind def /hx { 3 copy getinterval cf exch readhexstring pop pop } bind def /h FMLOCAL /w FMLOCAL /d FMLOCAL /lb FMLOCAL /bitmapsave FMLOCAL /is FMLOCAL /cf FMLOCAL /wbytes { dup 8 eq {pop} {1 eq {7 add 8 idiv} {3 add 4 idiv} ifelse} ifelse } bind def /BEGINBITMAPBWc { 1 {} COMMONBITMAPc } bind def /BEGINBITMAPGRAYc { 8 {} COMMONBITMAPc } bind def /BEGINBITMAP2BITc { 2 {} COMMONBITMAPc } bind def /COMMONBITMAPc { /r exch def /d exch def gsave translate rotate scale /h exch def /w exch def /lb w d wbytes def sl lb lt {lb ms} if /bitmapsave save def r /is im 0 lb getinterval def ws 0 lb getinterval is copy pop /cf currentfile def w h d [w 0 0 h neg 0 h] {ip} image bitmapsave restore grestore } bind def /BEGINBITMAPBW { 1 {} COMMONBITMAP } bind def /BEGINBITMAPGRAY { 8 {} COMMONBITMAP } bind def /BEGINBITMAP2BIT { 2 {} COMMONBITMAP } bind def /COMMONBITMAP { /r exch def /d exch def gsave translate rotate scale /h exch def /w exch def /bitmapsave save def r /is w d wbytes string def /cf currentfile def w h d [w 0 0 h neg 0 h] {cf is readhexstring pop} image bitmapsave restore grestore } bind def /proc1 FMLOCAL /proc2 FMLOCAL /newproc FMLOCAL /Fmcc { /proc2 exch cvlit def /proc1 exch cvlit def /newproc proc1 length proc2 length add array def newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval newproc cvx } bind def /ngrayt 256 array def /nredt 256 array def /nbluet 256 array def /ngreent 256 array def /gryt FMLOCAL /blut FMLOCAL /grnt FMLOCAL /redt FMLOCAL /indx FMLOCAL /cynu FMLOCAL /magu FMLOCAL /yelu FMLOCAL /k FMLOCAL /u FMLOCAL /colorsetup { currentcolortransfer /gryt exch def /blut exch def /grnt exch def /redt exch def 0 1 255 { /indx exch def /cynu 1 red indx get 255 div sub def /magu 1 green indx get 255 div sub def /yelu 1 blue indx get 255 div sub def /k cynu magu min yelu min def /u k currentundercolorremoval exec def nredt indx 1 0 cynu u sub max sub redt exec put ngreent indx 1 0 magu u sub max sub grnt exec put nbluet indx 1 0 yelu u sub max sub blut exec put ngrayt indx 1 k currentblackgeneration exec sub gryt exec put } for {255 mul cvi nredt exch get} {255 mul cvi ngreent exch get} {255 mul cvi nbluet exch get} {255 mul cvi ngrayt exch get} setcolortransfer {pop 0} setundercolorremoval {} setblackgeneration } bind def /tran FMLOCAL /fakecolorsetup { /tran 256 string def 0 1 255 {/indx exch def tran indx red indx get 77 mul green indx get 151 mul blue indx get 28 mul add add 256 idiv put} for currenttransfer {255 mul cvi tran exch get 255.0 div} exch Fmcc settransfer } bind def /BITMAPCOLOR { /d 8 def gsave translate rotate scale /h exch def /w exch def /bitmapsave save def colorsetup /is w d wbytes string def /cf currentfile def w h d [w 0 0 h neg 0 h] {cf is readhexstring pop} {is} {is} true 3 colorimage bitmapsave restore grestore } bind def /BITMAPCOLORc { /d 8 def gsave translate rotate scale /h exch def /w exch def /lb w d wbytes def sl lb lt {lb ms} if /bitmapsave save def colorsetup /is im 0 lb getinterval def ws 0 lb getinterval is copy pop /cf currentfile def w h d [w 0 0 h neg 0 h] {ip} {is} {is} true 3 colorimage bitmapsave restore grestore } bind def /BITMAPTRUECOLORc { gsave translate rotate scale /h exch def /w exch def /bitmapsave save def /is w string def ws 0 w getinterval is copy pop /cf currentfile def w h 8 [w 0 0 h neg 0 h] {ip} {gip} {bip} true 3 colorimage bitmapsave restore grestore } bind def /BITMAPTRUECOLOR { gsave translate rotate scale /h exch def /w exch def /bitmapsave save def /is w string def /gis w string def /bis w string def /cf currentfile def w h 8 [w 0 0 h neg 0 h] { cf is readhexstring pop } { cf gis readhexstring pop } { cf bis readhexstring pop } true 3 colorimage bitmapsave restore grestore } bind def /BITMAPTRUEGRAYc { gsave translate rotate scale /h exch def /w exch def /bitmapsave save def /is w string def ws 0 w getinterval is copy pop /cf currentfile def w h 8 [w 0 0 h neg 0 h] {ip gip bip w gray} image bitmapsave restore grestore } bind def /ww FMLOCAL /r FMLOCAL /g FMLOCAL /b FMLOCAL /i FMLOCAL /gray { /ww exch def /b exch def /g exch def /r exch def 0 1 ww 1 sub { /i exch def r i get .299 mul g i get .587 mul b i get .114 mul add add r i 3 -1 roll floor cvi put } for r } bind def /BITMAPTRUEGRAY { gsave translate rotate scale /h exch def /w exch def /bitmapsave save def /is w string def /gis w string def /bis w string def /cf currentfile def w h 8 [w 0 0 h neg 0 h] { cf is readhexstring pop cf gis readhexstring pop cf bis readhexstring pop w gray} image bitmapsave restore grestore } bind def /BITMAPGRAY { 8 {fakecolorsetup} COMMONBITMAP } bind def /BITMAPGRAYc { 8 {fakecolorsetup} COMMONBITMAPc } bind def /ENDBITMAP { } bind def end /ALDsave FMLOCAL /ALDmatrix matrix def ALDmatrix currentmatrix pop /StartALD { /ALDsave save def savematrix ALDmatrix setmatrix } bind def /InALD { restorematrix } bind def /DoneALD { ALDsave restore } bind def %%EndProlog %%BeginSetup (3.0) FMVERSION 1 1 612 792 0 1 19 FMDOCUMENT 0 0 /Times-Roman FMFONTDEFINE 1 0 /Helvetica FMFONTDEFINE 2 0 /Helvetica-Bold FMFONTDEFINE 3 0 /Times-Italic FMFONTDEFINE 4 0 /Courier FMFONTDEFINE 5 0 /Courier-Bold FMFONTDEFINE 6 0 /Times-Bold FMFONTDEFINE 7 0 /Times-BoldItalic FMFONTDEFINE 8 0 /Helvetica-Oblique FMFONTDEFINE 9 0 /Courier-Oblique FMFONTDEFINE 32 FMFILLS 0 0 FMFILL 1 0.1 FMFILL 2 0.3 FMFILL 3 0.5 FMFILL 4 0.7 FMFILL 5 0.9 FMFILL 6 0.97 FMFILL 7 1 FMFILL 8 <0f1e3c78f0e1c387> FMFILL 9 <0f87c3e1f0783c1e> FMFILL 10 FMFILL 11 FMFILL 12 <8142241818244281> FMFILL 13 <03060c183060c081> FMFILL 14 <8040201008040201> FMFILL 16 1 FMFILL 17 0.9 FMFILL 18 0.7 FMFILL 19 0.5 FMFILL 20 0.3 FMFILL 21 0.1 FMFILL 22 0.03 FMFILL 23 0 FMFILL 24 FMFILL 25 FMFILL 26 <3333333333333333> FMFILL 27 <0000ffff0000ffff> FMFILL 28 <7ebddbe7e7dbbd7e> FMFILL 29 FMFILL 30 <7fbfdfeff7fbfdfe> FMFILL %%EndSetup %%Page: "1" 1 %%BeginPaperSize: Letter %%EndPaperSize 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 72 144 504 144 2 L 3 X V 3 H 2 Z N 0 9 Q 0 X (ONC\252 T) 198 181.6 T (echnologies) 232.89 181.6 T (2550 Garcia A) 198 172.6 T (venue) 250.24 172.6 T (Mountain V) 198 163.6 T (iew) 241.15 163.6 T (, CA 94043 USA) 253.54 163.6 T 0 72 162 -72 -162 108 36 BEGINPRINTCODE %! % SUN logo % get width and height from Frame. /dlh exch def /dlw exch def % adjust dlw and translate to make it fit in a Frame rect. .015 dlw mul dup translate /dlw dlw .97 mul def % size of quadrant in logo /qsize 24 def % size of space in slot of U. This is adjusted at small scales /spsize 1 def % since qsize is not adjusted we precompute this /qs2 qsize 2 div def /qs4 qsize 4 div def /sunwd qsize 3.9 mul def /amin { abs exch abs 2 copy lt {pop} {exch pop} ifelse } bind def /amax { abs exch abs 2 copy gt {pop} {exch pop} ifelse } bind def /u { newpath uwd2 neg uht2 moveto 0 uwd2 uht2 sub uwd2 180 0 arc uwd2 uht2 lineto spd2 uht2 lineto 0 uwd2 uht2 sub spd2 0 180 arcn spd2 neg uht2 lineto closepath fill } bind def /quarter { gsave qs4 qs2 translate u qs2 0 translate 180 rotate u grestore } bind def /logo { % adjust space size so that space is maintain at small res. spsize dup dtransform amin 2.5 amax dup idtransform amax /spsize exch def spsize qsize ge { /spsize 0 def } if % compute sizes for U /lw qs2 spsize 2 mul sub 2 div def /spd2 spsize 2 div def /uht2 qsize spsize sub 2 div def /uwd2 lw spd2 add def % draw the quadrants gsave 45 rotate quarter 90 rotate quarter 90 rotate quarter 90 rotate quarter grestore } def /sun { sunwd 272 div dup scale -216.275 -533.334 translate 1 setlinecap 1 setlinejoin 2 setlinewidth % lowleft=216.275,533.334 upright=488.274,635 newpath 270.75 604.375 moveto 266.25 606.25 269.026 615.174 263.5 616.875 curveto 257 618.875 247.488 619.847 244 612.375 curveto 241.375 606.75 244.545 599.441 251.375 596.75 curveto 262.648 592.309 278.206 592.094 283.875 580.125 curveto 286.125 575.375 286.066 566.289 284.625 560.125 curveto 281.5 546.75 265.533 536.608 250.875 535.5 curveto 240.713 534.732 228.457 533.334 219.875 539.875 curveto 221.902 548.102 219 557.25 221.25 565.5 curveto 221.506 566.436 228.205 566.119 229.25 565 curveto 232.75 561.25 231.396 554.125 237.375 550.75 curveto 243.684 547.188 250.147 545.921 256.125 550.875 curveto 260.5 554.5 262.107 564.823 255.625 568.25 curveto 244.572 574.095 232 572 222.375 583.5 curveto 216.275 590.789 217.186 602.558 219.75 611.25 curveto 222 618.875 233.369 629.37 244.625 630.25 curveto 252.625 630.875 273.891 631.686 279.125 624.125 curveto 280.25 622.5 279.625 609.125 277.375 605.125 curveto 276.638 603.813 271.695 603.981 270.75 604.375 curveto closepath fill newpath 395.411 610.875 moveto 395.18 617.191 384.484 612.444 381 616.625 curveto 379.581 618.328 380.496 624.597 382.25 625 curveto 394.505 627.81 398.848 626.858 417.938 632.312 curveto 421.875 633.437 421.5 621.367 421.5 620.25 curveto 421.5 619.062 423.631 619.088 424.625 619.625 curveto 437.125 626.375 447.875 635 462.875 631.125 curveto 471.29 628.951 477.672 621.298 478 612.75 curveto 478.75 593.25 475.539 576.927 477.25 557.25 curveto 477.375 549.5 486.333 552.552 486.875 549.625 curveto 487.347 547.08 488.274 539.692 485.875 539.946 curveto 462.875 542.375 456.875 537.375 451.518 540.375 curveto 449.793 541.34 451.335 549.006 451.518 552.75 curveto 452.518 573.25 453.375 583.75 449.853 604.809 curveto 447.937 616.262 431.5 613.875 423.125 608 curveto 423.125 590 423.107 573.5 423.14 556.025 curveto 423.152 550.156 432.25 552.25 434.75 548.625 curveto 436.547 546.019 435.5 538.375 430.625 539.375 curveto 416.656 542.24 403.875 540.25 389.625 539.375 curveto 387.017 539.214 386.705 544.768 387.25 547.375 curveto 388.189 551.861 395.7 549.335 395.75 553.625 curveto 396 574.728 396.161 590.375 395.411 610.875 curveto closepath fill newpath 295.625 610 moveto 295.087 616.297 285.699 610.944 282.215 615.125 curveto 280.796 616.828 281.711 623.097 283.465 623.5 curveto 295.72 626.31 297.323 624.806 318.125 630.75 curveto 321.625 631.75 321.018 625.242 321.018 624.125 curveto 321.018 600.247 320.099 571.274 323.125 563.75 curveto 327.75 552.25 349.875 557.329 349.875 565.75 curveto 349.875 581.75 350.286 593.875 349.661 610.625 curveto 349.426 616.941 338.734 611.569 335.25 615.75 curveto 333.831 617.453 334.746 623.722 336.5 624.125 curveto 348.755 626.935 354.054 624.947 372.75 631.625 curveto 376.25 632.875 376.125 627.617 376.125 626.5 curveto 376.125 599.75 375.712 581.996 376.125 556.375 curveto 376.25 548.625 385.208 551.677 385.75 548.75 curveto 386.222 546.205 387.159 539.375 384.75 539.5 curveto 367.875 540.375 355.33 536.675 351.25 539.5 curveto 349.625 540.625 351.61 548.144 351.25 551.875 curveto 351.178 552.621 350.377 553.739 349.5 553.25 curveto 340.541 548.24 336.647 537.684 325.375 536.5 curveto 313.54 535.256 300.362 540.698 297.375 552.875 curveto 294.125 566.125 296.875 595.375 295.625 610 curveto closepath fill } def /logotype { gsave % origin of logotype is lower left edge qsize 1.29 mul dup translate logo grestore gsave qsize 2.98 mul qsize .54 mul translate sun grestore gsave qsize 3.01 mul 0 moveto /Helvetica findfont qsize .6 mul round scalefont setfont qsize 3.9 mul (microsystems) stringwidth pop sub 12 div 0 (microsystems) ashow grestore } def dlw qsize 6.879 mul div dup scale logotype showpage ENDPRINTCODE 1 10 Q (February 16, 1994) 265.17 474.33 T 1 24 Q -1.2 (NFS: Network File System) 179.79 614 S -1.2 (V) 156.54 587 S -1.2 (ersion 3 Protocol Speci\336cation) 170.02 587 S 1 10 Q (Comments to:) 274.9 549.33 T (sun!eng!nfs3) 277.39 537.33 T (nfs3@Eng.sun.com) 262.32 525.33 T FMENDPAGE %%EndPage: "1" 2 %%Page: "2" 2 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (2) 303.22 35.33 T (Version 3) 495.01 35.33 T 0 F (Copyright 1993, 1994 Sun Microsystems, Inc. Printed in the United States of America. All rights reserved.) 72 713.33 T (This specification is protected by copyright and is distributed under the following conditions:) 72 695.33 T -0.19 (The NFS Version 3 Protocol Specification is made available for your use provided that you include this provision and) 72 677.33 P (copyright notice on all copies made.) 72 665.33 T 0.01 (Without express written consent of Sun Microsystems, Inc. \050\322Sun\323\051, the names of Sun and any of its subsidiaries and) 72 647.33 P 0.19 (affiliates may not be used in advertising or publicity pertaining to the distribution or use of this Specification as per-) 72 635.33 P (mitted herein.) 72 623.33 T -0.58 (THIS SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING, BUT NOT) 72 605.33 P 0.02 (LIMITED TO, THE WARRANTIES OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR) 72 593.33 P -0.54 (PURPOSE, NONINFRINGEMENT, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRAC-) 72 581.33 P -0.16 (TICE. THIS SPECIFICATION IS NOT PROVIDED WITH ANY SUPPORT, AND SUN IS UNDER NO OBLIGA-) 72 569.33 P (TION TO ASSIST IN ITS USE, MODIFICATION, OR ENHANCEMENT.) 72 557.33 T 0.43 (SUN OR ANY OF ITS SUBSIDIARIES OR AFFILIATES SHALL HAVE NO LIABILITY WITH RESPECT TO) 72 539.33 P -0.23 (THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS, OR ANY OTHER INTELLECTUAL PROPERTY) 72 527.33 P -0.23 (RIGHTS OF ANY THIRD PARTIES BY THIS SPECIFICATION OR ITS USE THEREOF, NOR SHALL SUN OR) 72 515.33 P -0.62 (ANY OF ITS SUBSIDIARIES OR AFFILIATES BE LIABLE FOR ANY LOST REVENUE OR PROFITS OR OTH-) 72 503.33 P -0.11 (ER SPECIAL, INDIRECT AND CONSEQUENTIAL DAMAGES, EVEN IF SUN HAS BEEN ADVISED OF THE) 72 491.33 P (POSSIBILITY OF SUCH DAMAGES.) 72 479.33 T -0.25 (Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph \050c\051\0501\051\050ii\051 of the) 72 461.33 P (Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19.) 72 449.33 T FMENDPAGE %%EndPage: "2" 3 %%Page: "1" 3 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (1) 303.22 35.33 T 1 24 Q -1.2 (T) 222.87 704 S -1.2 (able of Contents) 233.66 704 S 2 12 Q (Introduction) 72 665 T (1) 533.33 665 T 1 F (Scope of the NFS version 3 protocol) 90 651 T (1) 533.33 651 T (Useful terms) 90 637 T (1) 533.33 637 T (Remote Procedure Call) 90 623 T (2) 533.33 623 T (External Data Representation) 90 609 T (2) 533.33 609 T (Authentication and Permission Checking) 90 595 T (3) 533.33 595 T (Philosophy) 90 581 T (3) 533.33 581 T (Changes from the NFS version 2 protocol) 90 567 T (5) 533.33 567 T 2 F (RPC Information) 72 553 T (7) 533.33 553 T 1 F (Authentication) 90 539 T (7) 533.33 539 T (Constants) 90 525 T (7) 533.33 525 T (Transport address) 90 511 T (7) 533.33 511 T (Sizes) 90 497 T (7) 533.33 497 T (Basic Data Types) 90 483 T (7) 533.33 483 T (Defined Error Numbers) 90 469 T (9) 533.33 469 T 2 F (Server Procedures) 72 455 T (16) 526.66 455 T 1 F (NULL: Do nothing) 90 441 T (18) 526.66 441 T (GETATTR: Get file attributes) 90 427 T (19) 526.66 427 T (SETATTR: Set file attributes) 90 413 T (20) 526.66 413 T (LOOKUP: Lookup filename) 90 399 T (22) 526.66 399 T (ACCESS: Check Access Permission) 90 385 T (24) 526.66 385 T (READLINK: Read from symbolic link) 90 371 T (26) 526.66 371 T (READ: Read From file) 90 357 T (28) 526.66 357 T (WRITE: Write to file) 90 343 T (30) 526.66 343 T (CREATE: Create a file) 90 329 T (33) 526.66 329 T (MKDIR: Create a directory) 90 315 T (36) 526.66 315 T (SYMLINK: Create a symbolic link) 90 301 T (38) 526.66 301 T (MKNOD: Create a special device) 90 287 T (40) 526.66 287 T (REMOVE: Remove a File) 90 273 T (43) 526.66 273 T (RMDIR: Remove a Directory) 90 259 T (45) 526.66 259 T (RENAME: Rename a File or Directory) 90 245 T (47) 526.66 245 T (LINK: Create Link to an object) 90 231 T (49) 526.66 231 T (READDIR: Read From Directory) 90 217 T (51) 526.66 217 T (READDIRPLUS: Extended read from directory) 90 203 T (54) 526.66 203 T (FSSTAT: Get dynamic file system information) 90 189 T (57) 526.66 189 T (FSINFO: Get static file system Information) 90 175 T (59) 526.66 175 T (PATHCONF: Retrieve POSIX information) 90 161 T (62) 526.66 161 T (COMMIT: Commit cached data on a server to stable storage) 90 147 T (64) 526.66 147 T 2 F (Implementation issues) 72 133 T (67) 526.66 133 T 1 F (Multiple version support) 90 119 T (67) 526.66 119 T (Server/client relationship) 90 105 T (67) 526.66 105 T (Path name interpretation) 90 91 T (67) 526.66 91 T (Permission issues) 90 77 T (67) 526.66 77 T FMENDPAGE %%EndPage: "1" 4 %%Page: "2" 4 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (2) 303.22 35.33 T (Version 3) 495.01 35.33 T 1 12 Q (Duplicate request cache) 90 712 T (68) 526.66 712 T (File name component handling) 90 698 T (69) 526.66 698 T (Synchronous modifying operations) 90 684 T (69) 526.66 684 T (Stable storage) 90 670 T (69) 526.66 670 T (Lookups and name resolution) 90 656 T (70) 526.66 656 T (Adaptive retransmission) 90 642 T (70) 526.66 642 T (Caching policies) 90 628 T (70) 526.66 628 T (Stable versus unstable writes) 90 614 T (70) 526.66 614 T (32 bit clients/servers and 64 bit clients/servers) 90 600 T (71) 526.66 600 T 2 F (Appendix I: Mount protocol) 72 586 T (73) 526.66 586 T (RPC Information) 72 572 T (74) 526.66 572 T 1 F (Authentication) 90 558 T (74) 526.66 558 T (Constants) 90 544 T (74) 526.66 544 T (Transport address) 90 530 T (74) 526.66 530 T (Sizes) 90 516 T (74) 526.66 516 T (Basic Data Types) 90 502 T (74) 526.66 502 T 2 F (Server Procedures) 72 488 T (75) 526.66 488 T 1 F (Null: Do nothing) 90 474 T (76) 526.66 474 T (Mount: Add mount entry) 90 460 T (77) 526.66 460 T (Dump: Return mount entries) 90 446 T (78) 526.66 446 T (Unmount: Remove mount entry) 90 432 T (79) 526.66 432 T (Unmount all: Remove all mount entries) 90 418 T (80) 526.66 418 T (Export: Return export list) 90 404 T (81) 526.66 404 T 2 F (Appendix II: Lock manager protocol) 72 390 T (83) 526.66 390 T (RPC Information) 72 376 T (84) 526.66 376 T 1 F (Authentication) 90 362 T (84) 526.66 362 T (Constants) 90 348 T (84) 526.66 348 T (Transport Address) 90 334 T (84) 526.66 334 T (Basic Data Types) 90 320 T (84) 526.66 320 T 2 F (NLM Procedures) 72 306 T (87) 526.66 306 T 1 F (NULL: Do nothing) 90 292 T (88) 526.66 292 T 2 F (Implementation issues) 72 278 T (89) 526.66 278 T (Appendix III: Bibliography) 72 264 T (91) 526.66 264 T (Index) 72 250 T (93) 526.66 250 T FMENDPAGE %%EndPage: "2" 5 %%Page: "1" 5 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (1) 303.22 35.33 T 2 12 Q (Introduction) 72 712 T 0 10 Q 0.08 (The Sun Network File System \050NFS) 72 693.33 P 0 6 Q 0.05 (\252) 217.62 696.53 P 0 10 Q 0.08 (\051 protocol provides transparent remote access to shared file systems across net-) 223.49 693.33 P 0.46 (works. The NFS protocol is designed to be machine, operating system, network architecture, and transport protocol) 72 681.33 P 0.09 (independent. This independence is achieved through the use of Remote Procedure Call \050RPC\051 primitives built on top) 72 669.33 P 0.08 (of an eXternal Data Representation \050XDR\051. Implementations of the NFS version 2 protocol exist for a variety of ma-) 72 657.33 P -0.54 (chines, from personal computers to supercomputers. The initial version of the NFS protocol is specified in the Network) 72 645.33 P (File System specification) 72 633.33 T 3 F ([RFC1094]) 175.55 633.33 T 0 F (. A description of the initial implementation can be found in) 222.2 633.33 T 3 F ([Sandberg]) 464.82 633.33 T 0 F (.) 510.91 633.33 T -0.24 (The supporting MOUNT protocol performs the operating system-specific functions that allow clients to attach remote) 72 615.33 P -0.1 (directory trees to a point within the local file system. The mount process also allows the server to grant remote access) 72 603.33 P (privileges to a restricted set of clients via export control.) 72 591.33 T -0.19 (The Lock Manager provides support for file locking when used in the NFS environment. The Network Lock Manager) 72 573.33 P (\050NLM\051 protocol isolates the inherently stateful aspects of file locking into a separate protocol.) 72 561.33 T (A complete description of the above protocols and their implementation is to be found in) 72 543.33 T 3 F ([X/OpenNFS]) 429.82 543.33 T 0 F (.) 485.9 543.33 T (The purpose of this document is to:) 72 525.33 T (\245) 90 509.33 T (Specify the NFS version 3 protocol) 108 509.33 T (\245) 90 497.33 T (Describe semantics of the protocol through annotation and description of intended implementation) 108 497.33 T (\245) 90 485.33 T (Specify the MOUNT version 3 protocol) 108 485.33 T (\245) 90 473.33 T -0.14 (Briefly describe the changes between the NLM version 3 protocol and the NLM version 4 protocol.) 108 473.33 P 0.39 (The normative text is the description of the RPC procedures and arguments and results, which defines the over-the-) 72 455.33 P -0.24 (wire protocol, and the semantics of those procedures. The material describing implementation practice aids the under-) 72 443.33 P 0.08 (standing of the protocol specification and describes some possible implementation issues and solutions. It is not pos-) 72 431.33 P 0.03 (sible to describe all implementations and the UNIX) 72 419.33 P 0 6 Q 0.01 (\250) 277.87 422.53 P 0 10 Q 0.03 ( operating system implementation of the NFS version 3 protocol) 282.43 419.33 P 0.21 (is most often used to provide examples. Given that, the implementation discussion does not bear the authority of the) 72 407.33 P (description of the over-the wire protocol itself.) 72 395.33 T 2 F (Scope of the NFS version 3 protocol) 72 373.33 T 0 F 0.32 (This revision of the NFS protocol addresses new requirements. The need to support larger files and file systems has) 72 355.33 P 0.52 (prompted extensions to allow) 72 343.33 P 4 F 1.25 (64) 194.57 343.33 P 0 F 0.52 ( bit file sizes and offsets. The revision enhances security by adding support for an) 206.56 343.33 P (access check to be done on the server. Performance modifications are of three types.) 72 331.33 T 1 F (1.) 90 315.33 T 0 F 0.25 (First, the number of over-the-wire packets for a given set of file operations is reduced by returning file) 108 315.33 P (attributes on every operation, thus decreasing the number of calls to get modified attributes.) 108 303.33 T 1 F (2.) 90 289.33 T 0 F -0.6 (Second, the write throughput bottleneck caused by the synchronous definition of write in the NFS version) 108 289.33 P 0.61 (2 protocol has been addressed by adding support so that the NFS server can do unsafe writes. Unsafe) 108 277.33 P -0.58 (writes are writes which have not been committed to stable storage before the operation returns. This spec-) 108 265.33 P (ification defines a method for committing these unsafe writes to stable storage in a reliable way.) 108 253.33 T 1 F (3.) 90 239.33 T 0 F (Third, limitations on transfer sizes have been relaxed.) 108 239.33 T 0.16 (The ability to support multiple versions of a protocol in RPC will allow implementors of the NFS version 3 protocol) 72 221.33 P 0.47 (to define clients and servers that provide backwards compatibility with the existing installed base of NFS version 2) 72 209.33 P (protocol implementations.) 72 197.33 T 0.09 (The extensions described here represent an evolution of the existing NFS protocol and most of the design features of) 72 179.33 P -0.49 (NFS described in) 72 167.33 P 3 F -0.49 ([Sandberg]) 142.44 167.33 P 0 F -0.49 ( persist. See) 188.52 167.33 P 3 F -0.49 (Changes from the NFS version 2 protocol) 237.58 167.33 P 0 F -0.49 ( on page 5 for a more detailed sum-) 401.79 167.33 P (mary of the changes introduced by this revision.) 72 155.33 T 2 F (Useful terms) 72 133.33 T 0 F 0.21 (In this specification, a) 72 115.33 P 3 F 0.21 (server) 163.61 115.33 P 0 F 0.21 ( is a machine that provides resources to the network; a) 188.58 115.33 P 3 F 0.21 (client) 410.44 115.33 P 0 F 0.21 ( is a machine that accesses) 432.65 115.33 P 72 96 540 110.98 C 81 108.96 225 108.96 2 L 7 X 0 K V 0.5 H 2 Z 0 X N 0 0 612 792 C 0 6 Q 0 X 0 K (\252) 92.5 92.53 T 0 10 Q (NFS is a registered trademark of Sun Microsystems, Inc.) 99.88 89.33 T 0 6 Q (\250) 92.5 80.53 T 0 10 Q ( UNIX is a registered trademark of UNIX System Laboratories.) 97.06 77.33 T FMENDPAGE %%EndPage: "1" 6 %%Page: "2" 6 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (2) 303.22 35.33 T (Version 3) 495.01 35.33 T 0 F 0.56 (resources over the network; a) 72 713.33 P 3 F 0.56 (user) 194.95 713.33 P 0 F 0.56 ( is a person \177logged in on a client; an) 212.16 713.33 P 3 F 0.56 (application) 364.29 713.33 P 0 F 0.56 ( is a program that executes on a) 409.82 713.33 P (client.) 72 701.33 T 2 F (Remote Procedure Call) 72 679.33 T 0 F -0.14 (The Sun Remote Procedure Call specification provides a procedure-oriented interface to remote services. Each server) 72 661.33 P 0.04 (supplies a) 72 649.33 P 3 F 0.04 (program) 114.28 649.33 P 0 F 0.04 (, which is a set of procedures. The NFS service is one such program. The combination of host ad-) 149.26 649.33 P 0.72 (dress, program number, version number, and procedure number specify one remote service procedure. Servers can) 72 637.33 P (support multiple versions of a program by using different protocol version numbers.) 72 625.33 T 0.08 (The NFS protocol was designed to not require any specific level of reliability from its lower levels so it could poten-) 72 607.33 P 0.05 (tially be used on many underlying transport protocols. The NFS service is based on RPC which provides the abstrac-) 72 595.33 P (tion above lower level network and transport protocols.) 72 583.33 T 0.64 (The rest of this document assumes the NFS environment is implemented on top of Sun RPC, which is specified in) 72 565.33 P 3 F ([RFC1057]) 72 553.33 T 0 F (. A complete discussion is found in) 118.64 553.33 T 3 F ([Corbin]) 261.9 553.33 T 0 F (.) 298 553.33 T 2 F (External Data Representation) 72 531.33 T 0 F -0.05 (The eXternal Data Representation \050XDR\051 specification provides a standard way of representing a set of data types on) 72 513.33 P 0.2 (a network. This solves the problem of different byte orders, structure alignment, and data type representation on dif-) 72 501.33 P (ferent, communicating machines.) 72 489.33 T 0.48 (In this document, the RPC Data Description Language is used to specify the XDR format parameters and results to) 72 471.33 P 0.42 (each of the RPC service procedures that an NFS server provides. The RPC Data Description Language is similar to) 72 459.33 P (declarations in the C programming language. A few new constructs have been added. The notation:) 72 447.33 T 4 F (string name[SIZE];) 90 431.33 T (string data;) 90 419.33 T 0 F 0.02 (defines) 72 401.33 P 5 F 0.05 (name) 103.39 401.33 P 0 F 0.02 (, which is a fixed size block of) 127.37 401.33 P 4 F 0.05 (SIZE) 252.18 401.33 P 0 F 0.02 ( bytes, and) 276.17 401.33 P 5 F 0.05 (data) 321.76 401.33 P 0 F 0.02 (, which is a variable sized block of up to) 345.74 401.33 P 4 F 0.05 (DSIZE) 510.02 401.33 P 0 F 0.35 (bytes. This notation indicates fixed-length arrays and arrays with a variable number of elements up to a fixed maxi-) 72 389.33 P (mum. A variable-length definition with no size specified means there is no maximum size for the field.) 72 377.33 T (The discriminated union definition:) 72 359.33 T 4 F (union example switch \050enum status\051 {) 90 343.33 T (case OK:) 90 331.33 T (struct {) 108 319.33 T (filename) 126 307.33 T (file1;) 198 307.33 T (filename) 126 295.33 T (file2;) 198 295.33 T (integer) 126 283.33 T (count;) 198 283.33 T (}) 108 271.33 T (case ERROR:) 90 259.33 T (struct {) 108 247.33 T (errstat) 126 235.33 T (error;) 198 235.33 T (integer) 126 223.33 T (errno;) 198 223.33 T (}) 108 211.33 T (default:) 90 199.33 T (void;) 108 187.33 T (}) 90 175.33 T 0 F 1.15 (defines a structure where the first thing over the network is an enumeration type called) 72 157.33 P 5 F 2.75 (status) 438.1 157.33 P 0 F 1.15 (. If the value of) 474.08 157.33 P 5 F 0.81 (status) 72 145.33 P 0 F 0.34 ( is) 107.98 145.33 P 4 F 0.81 (OK) 120.32 145.33 P 0 F 0.34 (, the next thing on the network will be the structure containing) 132.31 145.33 P 5 F 0.81 (file1) 388.13 145.33 P 0 F 0.34 (,) 418.11 145.33 P 5 F 0.81 (file2) 423.45 145.33 P 0 F 0.34 (, and) 453.43 145.33 P 5 F 0.81 (count) 476.03 145.33 P 0 F 0.34 (. Else, if) 506.02 145.33 P 0.28 (the value of) 72 133.33 P 5 F 0.68 (status) 122.53 133.33 P 0 F 0.28 ( is) 158.51 133.33 P 4 F 0.68 (ERROR) 170.74 133.33 P 0 F 0.28 (, the next thing on the network will be a structure containing) 200.72 133.33 P 5 F 0.68 (error) 448.1 133.33 P 0 F 0.28 ( and) 478.09 133.33 P 5 F 0.68 (errno) 498.08 133.33 P 0 F 0.28 (. If) 528.06 133.33 P (the value of) 72 121.33 T 5 F (status) 121.68 121.33 T 0 F ( is neither) 157.66 121.33 T 4 F (OK) 199.58 121.33 T 0 F ( nor) 211.57 121.33 T 4 F (ERROR) 229.89 121.33 T 0 F (, then there is no more data in the structure.) 259.88 121.33 T (The XDR type,) 72 103.33 T 5 F (hyper) 135.85 103.33 T 0 F (, is an) 165.83 103.33 T 4 F (8) 191.92 103.33 T 0 F ( byte \050) 197.92 103.33 T 4 F (64) 223.46 103.33 T 0 F ( bit\051 quantity. It is used in the same way as the integer type. For example:) 235.45 103.33 T 4 F (hyper) 90 87.33 T (foo;) 198 87.33 T (unsigned hyper) 90 75.33 T (bar;) 198 75.33 T FMENDPAGE %%EndPage: "2" 7 %%Page: "3" 7 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (3) 303.22 35.33 T 5 F (foo) 72 713.33 T 0 F ( is an) 89.99 713.33 T 4 F (8) 113.59 713.33 T 0 F ( byte signed value, while) 119.58 713.33 T 5 F (bar) 221.74 713.33 T 0 F ( is an) 239.73 713.33 T 4 F (8) 263.33 713.33 T 0 F ( byte unsigned value.) 269.32 713.33 T 0.15 (Although RPC/XDR compilers exist to generate client and server) 72 695.33 P 3 F 0.15 (stubs) 337.31 695.33 P 0 F 0.15 ( from RPC Data Description Language input,) 357.86 695.33 P 0.47 (NFS implementations do not require their use. Any software that provides equivalent encoding and decoding to the) 72 683.33 P (canonical network order of data defined by XDR can be used to interoperate with other NFS implementations.) 72 671.33 T (XDR is described in) 72 653.33 T 3 F ([RFC1014]) 155.83 653.33 T (.) 202.48 653.33 T 2 F (Authentication and Permission Checking) 72 631.33 T 0 F 0.33 (The RPC protocol includes a slot for authentication parameters on every call. The contents of the authentication pa-) 72 613.33 P -0.06 (rameters are determined by the type of authentication used by the server and client. A server may support several dif-) 72 601.33 P -0.49 (ferent flavors of authentication at once. The) 72 589.33 P 4 F -1.17 (AUTH_NONE) 246.21 589.33 P 0 F -0.49 ( flavor provides null authentication, that is, no authentication) 300.18 589.33 P -0.19 (information is passed. The) 72 577.33 P 4 F -0.45 (AUTH_UNIX) 179.79 577.33 P 0 F -0.19 ( flavor provides UNIX-style user id, group id, and groups with each call. The) 233.76 577.33 P 4 F 1.24 (AUTH_DES) 72 565.33 P 0 F 0.51 ( flavor provides DES-encrypted authentication parameters based on a network-wide name, with session) 119.97 565.33 P -0.22 (keys exchanged via a public key scheme. The) 72 553.33 P 4 F -0.54 (AUTH_KERB) 255.33 553.33 P 0 F -0.22 ( flavor provides DES encrypted authentication parameters) 309.3 553.33 P (based on a network-wide name with session keys exchanged via Kerberos secret keys.) 72 541.33 T -0.24 (The NFS server checks permissions by taking the credentials from the RPC authentication information in each remote) 72 523.33 P 0.17 (request. For example, using the) 72 511.33 P 4 F 0.42 (AUTH_UNIX) 200.84 511.33 P 0 F 0.17 ( flavor of authentication, the server gets the user\325s effective user id, ef-) 254.81 511.33 P -0.05 (fective group id and groups on each call, and uses them to check access. Using user ids and group ids implies that the) 72 499.33 P -0.16 (client and server either share the same id list or do local user and group id mapping. Servers and clients must agree on) 72 487.33 P -0.49 (the mapping from user to uid and from group to gid, for those sites that do not implement a consistent user id and group) 72 475.33 P -0.14 (id space. In practice, such mapping is typically performed on the server, following a static mapping scheme or a map-) 72 463.33 P (ping established by the user from a client at mount time.) 72 451.33 T -0.04 (The) 72 433.33 P 4 F -0.09 (AUTH_DES) 90 433.33 P 0 F -0.04 ( and) 137.98 433.33 P 4 F -0.09 (AUTH_KERB) 157.33 433.33 P 0 F -0.04 ( style of authentication is based on a network-wide name. It provides greater secu-) 211.3 433.33 P -0.04 (rity through the use of DES encryption and public keys in the case of) 72 421.33 P 4 F -0.1 (AUTH_DES) 350.12 421.33 P 0 F -0.04 (, and DES encryption and Kerberos) 398.09 421.33 P -0.48 (secret keys \050and tickets\051 in the) 72 409.33 P 4 F -1.14 (AUTH_KERB) 192.93 409.33 P 0 F -0.48 ( case. Again, the server and client must agree on the identity of a particular) 246.9 409.33 P 0.55 (name on the network, but the name to identity mapping is more operating system independent than the uid and gid) 72 397.33 P -0.19 (mapping in) 72 385.33 P 4 F -0.46 (AUTH_UNIX) 119.37 385.33 P 0 F -0.19 (. Also, because the authentication parameters are encrypted, a malicious user must know an-) 173.34 385.33 P 0.05 (other users network password or private key to masquerade as that user. Similarly, the server returns a verifier that is) 72 373.33 P (also encrypted so that masquerading as a server requires knowing a network password.) 72 361.33 T (The) 72 343.33 T 4 F (NULL) 90.04 343.33 T 0 F ( procedure typically requires no authentication.) 114.03 343.33 T 2 F (Philosophy) 72 321.33 T 0 F 0.2 (This specification defines the NFS version 3 protocol, that is the over-the-wire protocol by which a client accesses a) 72 303.33 P 0.48 (server. The protocol provides a well-defined interface to a server\325s file resources. A client or server) 72 291.33 P 3 F 0.48 (implements) 479.29 291.33 P 0 F 0.48 ( the) 524.81 291.33 P 0.07 (protocol and provides a mapping of the local file system semantics and actions into those defined in the NFS version) 72 279.33 P -0.28 (3 protocol. Implementations may differ to varying degrees, depending on the extent to which a given environment can) 72 267.33 P 0.26 (support all the operations and semantics defined in the NFS version 3 protocol. Although implementations exist and) 72 255.33 P -0.32 (are used to illustrate various aspects of the NFS version 3 protocol, the protocol specification itself is the final descrip-) 72 243.33 P (tion of how clients access server resources.) 72 231.33 T -0.2 (Because the NFS version 3 protocol is designed to be operating-system independent, it does not necessarily match the) 72 213.33 P -0.51 (semantics of any existing system. Server implementations are expected to make a) 72 201.33 P 3 F -0.51 (best effort) 394.29 201.33 P 0 F -0.51 ( at supporting the protocol.) 434.04 201.33 P -0.02 (If a server cannot support a particular protocol procedure, it may return the error,) 72 189.33 P 4 F -0.05 (NFS3ERR_NOTSUP) 398.07 189.33 P 0 F -0.02 (, that indicates) 482.03 189.33 P 0.15 (that the operation is not supported. For example, many operating systems do not support the notion of a) 72 177.33 P 3 F 0.15 (\177hard link) 491.12 177.33 P 0 F 0.15 (. A) 527.64 177.33 P 0.08 (server that cannot support hard links should return) 72 165.33 P 4 F 0.19 (NFS3ERR_NOTSUP) 276.38 165.33 P 0 F 0.08 ( in response to a) 360.33 165.33 P 4 F 0.19 (LINK) 428.17 165.33 P 0 F 0.08 ( request.) 452.16 165.33 P 4 F 0.19 (FSINFO) 488.68 165.33 P 0 F 0.08 ( de-) 524.66 165.33 P -0.28 (scribes the most commonly unsupported procedures in the) 72 153.33 P 5 F -0.67 (properties) 305.17 153.33 P 0 F -0.28 ( bit map. Alternatively, a server may not na-) 365.14 153.33 P 0.26 (tively support a given operation, but can emulate it in the NFS version 3 protocol implementation to provide greater) 72 141.33 P (functionality.) 72 129.33 T 0.93 (In some cases, a server can support most of the semantics described by the protocol but not all. For example, the) 72 111.33 P 5 F 1.19 (ctime) 72 99.33 P 0 F 0.5 ( field in the) 101.98 99.33 P 5 F 1.19 (fattr) 152.27 99.33 P 0 F 0.5 ( structure gives the time that a file\325s attributes were last modified. Many systems do not) 182.25 99.33 P 0.3 (keep this information. In this case, rather than not support the) 72 87.33 P 4 F 0.73 (GETATTR) 323.78 87.33 P 0 F 0.3 ( operation, a server could simulate it by re-) 365.76 87.33 P 0.19 (turning the last modified time in place of) 72 75.33 P 5 F 0.47 (ctime) 239.56 75.33 P 0 F 0.19 (. Servers must be careful when simulating attribute information be-) 269.55 75.33 P FMENDPAGE %%EndPage: "3" 8 %%Page: "4" 8 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (4) 303.22 35.33 T (Version 3) 495.01 35.33 T 0 F -0.5 (cause of possible side effects on clients. For example, many clients use file modification times as a basis for their cache) 72 713.33 P (consistency scheme.) 72 701.33 T (NFS servers are dumb and NFS clients are smart. It is the clients that do the work required to convert the generalized) 72 683.33 T -0.08 (file access that servers provide into a file access method that is useful to applications and users. In the) 72 671.33 P 4 F -0.18 (LINK) 479.73 671.33 P 0 F -0.08 ( example) 503.71 671.33 P -0.33 (given above, a UNIX client that received an) 72 659.33 P 4 F -0.79 (NFS3ERR_NOTSUP) 247.82 659.33 P 0 F -0.33 ( error from a server would do the recovery necessary) 331.78 659.33 P 0.07 (to either make it look to the application like the link request had succeeded or return a reasonable error. In general, it) 72 647.33 P (is the burden of the client to recover.) 72 635.33 T 0.33 (The NFS version 3 protocol assumes a stateless server implementation. Statelessness means that the server does not) 72 617.33 P -0.23 (need to maintain state about any of its clients in order to function correctly. Stateless servers have a distinct advantage) 72 605.33 P 0.36 (over stateful servers in the event of a crash. With stateless servers, a client need only retry a request until the server) 72 593.33 P 0.6 (responds; the client does not even need to know that the server has crashed. See additional comments in) 72 581.33 P 3 F 0.6 (Duplicate) 500.58 581.33 P (request cache) 72 569.33 T 0 F ( on page 68.) 127.23 569.33 T -0.07 (For a server to be useful, it holds nonvolatile state: data stored in the file system. Design assumptions in the NFS ver-) 72 551.33 P -0.28 (sion 3 protocol regarding flushing of modified data to stable storage reduce the number of failure modes in which data) 72 539.33 P -0.23 (loss can occur. In this way, NFS version 3 protocol implementations can tolerate transient failures, including transient) 72 527.33 P 0.21 (failures of the network. In general, server implementations of the NFS version 3 protocol cannot tolerate a non-tran-) 72 515.33 P 0.14 (sient failure of the stable storage itself. However, there exist fault tolerant implementations which attempt to address) 72 503.33 P (such problems.) 72 491.33 T 0.39 (That is not to say that an NFS version 3 protocol server can\325t maintain noncritical state. In many cases, servers will) 72 473.33 P 0.2 (maintain state \050cache\051 about previous operations to increase performance. For example, a client) 72 461.33 P 4 F 0.47 (READ) 458.43 461.33 P 0 F 0.2 ( request might) 482.42 461.33 P -0.1 (trigger a read\320ahead of the next block of the file into the server\325s data cache in the anticipation that the client is doing) 72 449.33 P 0.38 (a sequential read and the next client) 72 437.33 P 4 F 0.92 (READ) 220.41 437.33 P 0 F 0.38 ( request will be satisfied from the server\325s data cache instead of from the) 244.4 437.33 P -0.14 (disk. Read-ahead on the server increases performance by overlapping server disk I/O with client requests. The impor-) 72 425.33 P -0.15 (tant point here is that the read\320ahead block is not necessary for correct server behavior. If the server crashes and loses) 72 413.33 P 0.12 (its memory cache of read buffers, recovery is simple on reboot\321clients will continue read operations retrieving data) 72 401.33 P (from the server disk.) 72 389.33 T 0.28 (Most data-modifying operations in the NFS protocol are synchronous. That is, when a data modifying procedure re-) 72 371.33 P 0.29 (turns to the client, the client can assume that the operation has completed and any modified data associated with the) 72 359.33 P 0.49 (request is now on stable storage. For example, a synchronous client) 72 347.33 P 4 F 1.19 (WRITE) 349.74 347.33 P 0 F 0.49 ( request may cause the server to update) 379.73 347.33 P -0.32 (data blocks, file system information blocks, and file attribute information\321the latter information is usually referred to) 72 335.33 P 0.5 (as) 72 323.33 P 3 F 0.5 (metadata) 83.32 323.33 P 0 F 0.5 (. When the) 120.52 323.33 P 4 F 1.19 (WRITE) 168.09 323.33 P 0 F 0.5 ( operation completes, the client can assume that the write data is safe and discard it.) 198.07 323.33 P -0.05 (This is a very important part of the stateless nature of the server. If the server did not flush dirty data to stable storage) 72 311.33 P -0.28 (before returning to the client, the client would have no way of knowing when it was safe to discard modified data. The) 72 299.33 P 0.71 (following data modifying procedures are synchronous:) 72 287.33 P 4 F 1.71 (WRITE) 297.77 287.33 P 0 F 0.71 ( \050with) 327.76 287.33 P 5 F 1.71 (stable) 355.27 287.33 P 0 F 0.71 ( flag set to) 391.26 287.33 P 4 F 1.71 (FILE_SYNC) 438.51 287.33 P 0 F 0.71 (\051,) 492.48 287.33 P 4 F 1.71 (CREATE) 501.52 287.33 P 0 F 0.71 (,) 537.5 287.33 P 4 F (MKDIR) 72 275.33 T 0 F (,) 101.98 275.33 T 4 F (SYMLINK) 106.98 275.33 T 0 F (,) 148.96 275.33 T 4 F (MKNOD) 153.96 275.33 T 0 F (,) 183.94 275.33 T 4 F (REMOVE) 188.94 275.33 T 0 F (,) 224.92 275.33 T 4 F (RMDIR) 229.91 275.33 T 0 F (,) 259.9 275.33 T 4 F (RENAME) 264.89 275.33 T 0 F (,) 300.87 275.33 T 4 F (LINK) 305.87 275.33 T 0 F (, and) 329.86 275.33 T 4 F (COMMIT) 351.79 275.33 T 0 F (.) 387.77 275.33 T -0.11 (The NFS version 3 protocol introduces) 72 257.33 P 3 F -0.11 (safe asynchronous writes) 229.58 257.33 P 0 F -0.11 ( on the server, when the) 330.42 257.33 P 4 F -0.26 (WRITE) 427.74 257.33 P 0 F -0.11 ( procedure is used in) 457.72 257.33 P -0.31 (conjunction with the) 72 245.33 P 4 F -0.75 (COMMIT) 155.74 245.33 P 0 F -0.31 ( procedure. The) 191.72 245.33 P 4 F -0.75 (COMMIT) 256.28 245.33 P 0 F -0.31 ( procedure provides a way for the client to flush data from pre-) 292.26 245.33 P -0.03 (vious asynchronous) 72 233.33 P 4 F -0.07 (WRITE) 153.55 233.33 P 0 F -0.03 ( requests on the server to stable storage and to detect whether it is necessary to retransmit) 183.54 233.33 P (the data. See the procedure descriptions of) 72 221.33 T 4 F (WRITE) 244.09 221.33 T 0 F ( on page 30) 274.07 221.33 T ( and) 320.42 221.33 T 4 F (COMMIT) 339.85 221.33 T 0 F ( on page 64) 375.83 221.33 T (.) 422.19 221.33 T -0.54 (The) 72 203.33 P 4 F -1.3 (LOOKUP) 89.5 203.33 P 0 F -0.54 ( procedure is used by the client to traverse multicomponent file names \050pathnames\051. Each call to) 125.48 203.33 P 4 F -1.3 (LOOKUP) 504.02 203.33 P 0 F -0.05 (is used to resolve one segment of a pathname. There are two reasons for restricting) 72 191.33 P 4 F -0.12 (LOOKUP) 404.91 191.33 P 0 F -0.05 ( to a single segment: it is) 440.89 191.33 P -0.49 (hard to standardize a common format for hierarchical file names and the client and server may have different mappings) 72 179.33 P -0.57 (of pathnames to file systems. This would imply that either the client must break the path name at file system attachment) 72 167.33 P -0.22 (points, or the server must know about the client\325s file system attachment points. In NFS version 3 protocol implemen-) 72 155.33 P 0.01 (tations, it is the client that constructs the hierarchical file name space using mounts to build a hierarchy. Support util-) 72 143.33 P 0.07 (ities, such as the Automounter, provide a way to manage a shared, consistent image of the file name space while still) 72 131.33 P (being driven by the client mount process.) 72 119.33 T -0.35 (Clients can perform caching in varied manner. The general practice with the NFS version 2 protocol was to implement) 72 101.33 P 0.06 (a time-based client-server cache consistency mechanism. It is expected NFS version 3 protocol implementations will) 72 89.33 P 0.55 (use a similar mechanism. The NFS version 3 protocol has some explicit support, in the form of additional attribute) 72 77.33 P FMENDPAGE %%EndPage: "4" 9 %%Page: "5" 9 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (5) 303.22 35.33 T 0 F -0.19 (information to eliminate explicit attribute checks. However, caching is not required, nor is any caching policy defined) 72 713.33 P 0.32 (by the protocol. Neither the NFS version 2 protocol nor the NFS version 3 protocol provide a means of maintaining) 72 701.33 P (strict client-server consistency \050and, by implication, consistency across client caches\051.) 72 689.33 T 2 F (Changes from the NFS version 2 protocol) 72 667.33 T 0 F -0.26 (The) 72 649.33 P 4 F -0.64 (ROOT) 89.78 649.33 P 0 F -0.26 ( and) 113.76 649.33 P 4 F -0.64 (WRITECACHE) 132.66 649.33 P 0 F -0.26 ( procedures have been removed. A) 192.63 649.33 P 4 F -0.64 (MKNOD) 332.3 649.33 P 0 F -0.26 ( procedure has been defined to allow the cre-) 362.28 649.33 P -0.16 (ation of special files, eliminating the overloading of) 72 637.33 P 4 F -0.38 (CREATE) 280.33 637.33 P 0 F -0.16 (. Caching on the client is) 316.31 637.33 P 6 F -0.16 (not) 417.26 637.33 P 0 F -0.16 ( defined nor dictated by the) 431.14 637.33 P -0.09 (NFS version 3 protocol, but additional information and hints have been added to the protocol to allow clients that im-) 72 625.33 P -0.51 (plement caching to manage their caches more effectively. Procedures that affect the attributes of a file or directory may) 72 613.33 P 0.1 (now return the new attributes after the operation has completed to optimize out a subsequent) 72 601.33 P 4 F 0.25 (GETATTR) 445.8 601.33 P 0 F 0.1 ( used in vali-) 487.77 601.33 P 0.31 (dating attribute caches. In addition, operations that modify the directory in which the target object resides return the) 72 589.33 P 0.36 (old and new attributes of the directory to allow clients to implement more intelligent cache invalidation procedures.) 72 577.33 P 0.16 (The) 72 565.33 P 4 F 0.38 (ACCESS) 90.2 565.33 P 0 F 0.16 ( procedure provides access permission checking on the server, the) 126.18 565.33 P 4 F 0.38 (FSSTAT) 393.92 565.33 P 0 F 0.16 ( procedure returns dynamic) 429.9 565.33 P 0.15 (information about a file system, the) 72 553.33 P 4 F 0.37 (FSINFO) 217.55 553.33 P 0 F 0.15 ( procedure returns static information about a file system and server, the) 253.53 553.33 P 4 F -0.55 (READDIRPLUS) 72 541.33 P 0 F -0.23 ( procedure returns file handles and attributes in addition to directory entries, and the) 137.96 541.33 P 4 F -0.55 (PATHCONF) 473.11 541.33 P 0 F -0.23 ( pro-) 521.08 541.33 P (cedure returns POSIX pathconf information about a file.) 72 529.33 T (Below is a list of the important changes between the NFS version 2 protocol and the NFS version 3 protocol.) 72 511.33 T (File handle size) 90 495.33 T -0.34 (The file handle has been increased to a variable-length array of) 113.04 483.33 P 4 F -0.81 (64) 363.83 483.33 P 0 F -0.34 ( bytes maximum from a fixed array of) 375.82 483.33 P 4 F -0.81 (32) 528.01 483.33 P 0 F 0.52 (bytes. This addresses some known requirements for a slightly larger file handle size. The file handle was) 113.04 471.33 P -0.12 (converted from fixed length to variable length to reduce local storage and network bandwidth requirements) 113.04 459.33 P (for systems which do not utilize the full) 113.04 447.33 T 4 F (64) 274.61 447.33 T 0 F ( bytes of length.) 286.61 447.33 T (Maximum data sizes) 90 433.33 T 0.22 (The maximum size of a data transfer used in the) 113.04 421.33 P 4 F 0.52 (READ) 310.08 421.33 P 0 F 0.22 ( and) 334.07 421.33 P 4 F 0.52 (WRITE) 353.93 421.33 P 0 F 0.22 ( procedures is now set by values in the) 383.92 421.33 P 4 F 0.57 (FSINFO) 113.04 409.33 P 0 F 0.24 ( return structure. In addition, preferred transfer sizes are returned by) 149.02 409.33 P 4 F 0.57 (FSINFO) 426.13 409.33 P 0 F 0.24 (. The protocol does) 462.11 409.33 P -0.33 (not place any artificial limits on the maximum transfer sizes. Filenames and pathnames are now specified as) 113.04 397.33 P 0.15 (strings of variable length. The actual length restrictions are determined by the client and server implemen-) 113.04 385.33 P 3.15 (tations as appropriate. The protocol does not place any artificial limits on the length. The error,) 113.04 373.33 P 4 F 1.03 (NFS3ERR_NAMETOOLONG) 113.04 361.33 P 0 F 0.43 (, is provided to allow the server to return an indication to the client that it re-) 226.98 361.33 P (ceived a pathname that was too long for it to handle.) 113.04 349.33 T (Error return) 90 335.33 T 0.19 (Error returns in some instances now return data \050for example, attributes\051.) 113.04 323.33 P 5 F 0.46 (nfsstat3) 409.09 323.33 P 0 F 0.19 ( now defines the full) 457.07 323.33 P (set of errors that can be returned by a server. No other values are allowed.) 113.04 311.33 T (File type) 90 297.33 T 0.31 (The file type now includes) 113.04 285.33 P 4 F 0.75 (NF3CHR) 223.68 285.33 P 0 F 0.31 ( and) 259.66 285.33 P 4 F 0.75 (NF3BLK) 279.71 285.33 P 0 F 0.31 ( for special files. Attributes for these types include sub-) 315.7 285.33 P 0.22 (fields for UNIX major and minor devices numbers.) 113.04 273.33 P 4 F 0.52 (NF3SOCK) 322.13 273.33 P 0 F 0.22 ( and) 364.11 273.33 P 4 F 0.52 (NF3FIFO) 383.97 273.33 P 0 F 0.22 ( are now defined for sockets) 425.95 273.33 P (and fifos in the file system.) 113.04 261.33 T (File attributes) 90 247.33 T -0.27 (The) 113.04 235.33 P 5 F -0.65 (blocksize) 130.81 235.33 P 0 F -0.27 ( \050the size in bytes of a block in the file\051 field has been removed. The) 184.78 235.33 P 5 F -0.65 (mode) 455.48 235.33 P 0 F -0.27 ( field no longer) 479.47 235.33 P -0.22 (contains file type information. The) 113.04 223.33 P 5 F -0.53 (size) 253.51 223.33 P 0 F -0.22 ( and) 277.5 223.33 P 5 F -0.53 (fileid) 296.49 223.33 P 0 F -0.22 ( fields have been widened to eight-byte unsigned in-) 332.47 223.33 P -0.16 (tegers from four-byte integers. Major and minor device information is now presented in a distinct structure.) 113.04 211.33 P -0.25 (The) 113.04 199.33 P 5 F -0.59 (blocks) 130.83 199.33 P 0 F -0.25 ( field name has been changed to) 166.81 199.33 P 5 F -0.59 (used) 295.82 199.33 P 0 F -0.25 ( and now contains the total number of bytes used by the) 319.8 199.33 P (file. It is also an eight-byte unsigned integer.) 113.04 187.33 T (Set file attributes) 90 173.33 T -0.32 (In the NFS version 2 protocol, the settable attributes were represented by a subset of the file attributes struc-) 113.04 161.33 P 0.28 (ture; the client indicated those attributes which were) 113.04 149.33 P 7 F 0.28 (not) 326.78 149.33 P 0 F 0.28 ( to be modified by setting the corresponding field) 340.12 149.33 P -0.3 (to) 113.04 137.33 P 4 F -0.71 (-1) 123.02 137.33 P 0 F -0.3 (, overloading some unsigned fields. The set file attributes structure now uses a discriminated union for) 135.01 137.33 P -0.29 (each field to tell whether or how to set that field. The atime and mtime fields can be set to either the server\325s) 113.04 125.33 P (current time or a time supplied by the client.) 113.04 113.33 T 4 F (LOOKUP) 90 99.33 T 0 F (The) 113.04 87.33 T 4 F (LOOKUP) 131.08 87.33 T 0 F ( return structure now includes the attributes for the directory searched.) 167.06 87.33 T FMENDPAGE %%EndPage: "5" 10 %%Page: "6" 10 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (6) 303.22 35.33 T (Version 3) 495.01 35.33 T 4 F (ACCESS) 90 713.33 T 0 F -0.4 (An) 113.04 701.33 P 4 F -0.97 (ACCESS) 127.35 701.33 P 0 F -0.4 ( procedure has been added to allow an explicit over-the-wire permissions check. This addresses) 163.33 701.33 P -0.51 (known problems with the superuser id mapping feature in many server implementations \050where, due to map-) 113.04 689.33 P -0.05 (ping of root user, unexpected) 113.04 677.33 P 3 F -0.05 (permission denied) 232.17 677.33 P 0 F -0.05 ( errors could occur while reading from or writing to a file\051.) 305.13 677.33 P 0.43 (This also removes the assumption which was made in the NFS version 2 protocol that access to files was) 113.04 665.33 P (based solely on UNIX style mode bits.) 113.04 653.33 T 4 F (READ) 90 639.33 T 0 F 0.35 (The reply structure includes a Boolean that is) 113.04 627.33 P 4 F 0.85 (TRUE) 299.62 627.33 P 0 F 0.35 ( if the end\320of\320file was encountered during the) 323.61 627.33 P 4 F 0.85 (READ) 513.51 627.33 P 0 F 0.35 (.) 537.5 627.33 P (This allows the client to correctly detect end-of-file.) 113.04 615.33 T 4 F (WRITE) 90 601.33 T 0 F 0.22 (The) 113.04 589.33 P 5 F 0.54 (beginoffset) 131.3 589.33 P 0 F 0.22 ( and) 197.27 589.33 P 5 F 0.54 (totalcount) 217.15 589.33 P 0 F 0.22 ( fields were removed from the) 277.11 589.33 P 4 F 0.54 (WRITE) 401.7 589.33 P 0 F 0.22 ( arguments. The reply now) 431.68 589.33 P -0.27 (includes a count so that the server can write less than the requested amount of data, if required. An indicator) 113.04 577.33 P -0.19 (was added to the arguments to instruct the server as to the level of cache synchronization that is required by) 113.04 565.33 P (the client.) 113.04 553.33 T 4 F (CREATE) 90 539.33 T 0 F (An exclusive flag and a create verifier was added for the exclusive creation of regular files.) 113.04 527.33 T 4 F (MKNOD) 90 513.33 T 0 F -0.39 (This procedure was added to support the creation of special files. This avoids overloading fields of) 113.04 501.33 P 4 F -0.94 (CREATE) 504.02 501.33 P 0 F (as was done in some NFS version 2 protocol implementations.) 113.04 489.33 T 4 F (READDIR) 90 475.33 T 0 F 0.51 (The) 113.04 463.33 P 4 F 1.21 (READDIR) 131.59 463.33 P 0 F 0.51 ( arguments now include a verifier to allow the server to validate the cookie. The cookie is) 173.56 463.33 P 0.48 (now a) 113.04 451.33 P 4 F 1.14 (64) 140.64 451.33 P 0 F 0.48 ( bit unsigned integer instead of the) 152.63 451.33 P 4 F 1.14 (4) 296.7 451.33 P 0 F 0.48 ( byte array which was used in the NFS version 2 protocol.) 302.7 451.33 P (This will help to reduce interoperability problems.) 113.04 439.33 T 4 F (READDIRPLUS) 90 425.33 T 0 F (This procedure was added to return file handles and attributes in an extended directory list.) 113.04 413.33 T 4 F (FSINFO) 90 399.33 T -1.13 (FSINFO) 113.04 387.33 P 0 F -0.47 ( was added to provide nonvolatile information about a file system. The reply includes preferred and) 149.02 387.33 P 0.13 (maximum read transfer size, preferred and maximum write transfer size, and flags stating whether links or) 113.04 375.33 P -0.57 (symbolic links are supported. Also returned are preferred transfer size for) 113.04 363.33 P 4 F -1.37 (READDIR) 403.16 363.33 P 0 F -0.57 ( procedure replies, serv-) 445.14 363.33 P (er time granularity, and whether times can be set in a) 113.04 351.33 T 4 F (SETATTR) 327.32 351.33 T 0 F ( request.) 369.3 351.33 T 4 F (FSSTAT) 90 337.33 T -1.09 (FSSTAT) 113.04 325.33 P 0 F -0.46 ( was added to provide volatile information about a file system, for use by utilities such as) 149.02 325.33 P 3 F -0.46 (df\0501\051) 500.49 325.33 P 0 F -0.46 (. The) 519.92 325.33 P -0.18 (reply includes the total size and free space in the file system specified in bytes, the total number of files and) 113.04 313.33 P 0.26 (number of free file slots in the file system, and an estimate of time between file system modifications \050for) 113.04 301.33 P (use in cache consistency checking algorithms\051.) 113.04 289.33 T 4 F (COMMIT) 90 275.33 T 0 F -0.35 (The) 113.04 263.33 P 4 F -0.84 (COMMIT) 130.73 263.33 P 0 F -0.35 ( procedure provides the synchronization mechanism to be used with asynchronous) 166.71 263.33 P 4 F -0.84 (WRITE) 494.55 263.33 P 0 F -0.35 ( op-) 524.53 263.33 P (erations.) 113.04 251.33 T FMENDPAGE %%EndPage: "6" 11 %%Page: "7" 11 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (7) 303.22 35.33 T 2 12 Q (RPC Information) 72 712 T 2 10 Q (Authentication) 72 689.33 T 0 F -0.05 (The NFS service uses) 72 671.33 P 4 F -0.11 (AUTH_NONE) 161.2 671.33 P 0 F -0.05 ( in the) 215.17 671.33 P 4 F -0.11 (NULL) 242.52 671.33 P 0 F -0.05 ( procedure.) 266.5 671.33 P 4 F -0.11 (AUTH_UNIX) 313.87 671.33 P 0 F -0.05 (,) 367.84 671.33 P 4 F -0.11 (AUTH_DES) 372.79 671.33 P 0 F -0.05 (, or) 420.76 671.33 P 4 F -0.11 (AUTH_KERB) 436.49 671.33 P 0 F -0.05 ( are used for) 490.46 671.33 P (all other procedures. Other authentication types may be supported in the future.) 72 659.33 T 2 F (Constants) 72 637.33 T 0 F (These are the RPC constants needed to call the NFS Version 3 service. They are given in decimal.) 72 619.33 T 4 F (PROGRAM) 90 603.33 T ( 100003) 131.98 603.33 T (VERSION) 90 591.33 T ( 3) 131.98 591.33 T 2 F (Transport address) 72 569.33 T 0 F (NFS is normally supported over the UDP protocol. It uses port) 72 551.33 T 4 F (2049) 325.18 551.33 T 0 F (, the same as the NFS version 2 protocol.) 349.17 551.33 T 2 F (Sizes) 72 529.33 T 0 F (These are the sizes, given in decimal bytes, of various XDR structures used in the NFS version 3 protocol:) 72 511.33 T 4 F (NFS3_FHSIZE 64) 90 495.33 T 0 F (The maximum size in bytes of the opaque file handle.) 113.04 483.33 T 4 F (NFS3_COOKIEVERFSIZE 8) 90 469.33 T 0 F (The size in bytes of the opaque cookie verifier passed by) 113.04 457.33 T 4 F (READDIR) 342.58 457.33 T 0 F ( and) 384.56 457.33 T 4 F (READDIRPLUS) 403.99 457.33 T 0 F (.) 469.95 457.33 T 4 F (NFS3_CREATEVERFSIZE 8) 90 443.33 T 0 F (The size in bytes of the opaque verifier used for exclusive) 113.04 431.33 T 4 F (CREATE) 347.02 431.33 T 0 F (.) 383 431.33 T 4 F (NFS3_WRITEVERFSIZE 8) 90 417.33 T 0 F (The size in bytes of the opaque verifier used for asynchronous) 113.04 405.33 T 4 F (WRITE) 364.23 405.33 T 0 F (.) 394.21 405.33 T 2 F (Basic Data Types) 72 383.33 T 0 F (The following XDR definitions are basic definitions that are used in other structures.) 72 365.33 T 5 F (uint64) 72 347.33 T 4 F (typedef unsigned hyper) 90 335.33 T (uint64;) 234 335.33 T 5 F (int64) 72 317.33 T 4 F (typedef hyper) 90 305.33 T (int64;) 234 305.33 T 5 F (uint32) 72 287.33 T 4 F (typedef unsigned long) 90 275.33 T (uint32;) 234 275.33 T 5 F (int32) 72 257.33 T 4 F (typedef long) 90 245.33 T (int32;) 234 245.33 T 5 F (filename3) 72 227.33 T 4 F (typedef string) 90 215.33 T (filename3<>;) 234 215.33 T 5 F (nfspath3) 72 197.33 T 4 F (typedef string) 90 185.33 T (nfspath3<>;) 234 185.33 T 5 F (fileid3) 72 167.33 T 4 F (typedef uint64) 90 155.33 T (fileid3;) 234 155.33 T 5 F (cookie3) 72 137.33 T 4 F (typedef uint64) 90 125.33 T (cookie3;) 234 125.33 T 5 F (cookieverf3) 72 107.33 T 4 F (typedef opaque) 90 95.33 T (cookieverf3[NFS3_COOKIEVERFSIZE];) 234 95.33 T FMENDPAGE %%EndPage: "7" 12 %%Page: "8" 12 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (8) 303.22 35.33 T (Version 3) 495.01 35.33 T 5 F (createverf3) 72 713.33 T 4 F (typedef opaque) 90 701.33 T (createverf3[NFS3_CREATEVERFSIZE];) 234 701.33 T 5 F (writeverf3) 72 683.33 T 4 F (typedef opaque) 90 671.33 T (writeverf3[NFS3_WRITEVERFSIZE];) 234 671.33 T 5 F (uid3) 72 653.33 T 4 F (typedef uint32) 90 641.33 T (uid3;) 234 641.33 T 5 F (gid3) 72 623.33 T 4 F (typedef uint32) 90 611.33 T (gid3;) 234 611.33 T 5 F (size3) 72 593.33 T 4 F (typedef uint64) 90 581.33 T (size3;) 234 581.33 T 5 F (offset3) 72 563.33 T 4 F (typedef uint64) 90 551.33 T (offset3;) 234 551.33 T 5 F (mode3) 72 533.33 T 4 F (typedef uint32) 90 521.33 T (mode3;) 234 521.33 T 5 F (count3) 72 503.33 T 4 F (typedef uint32) 90 491.33 T (count3;) 234 491.33 T 5 F (nfsstat3) 72 473.33 T 4 F (enum nfsstat3 {) 90 461.33 T (NFS3_OK) 108 449.33 T (= 0,) 234 449.33 T (NFS3ERR_PERM) 108 437.33 T (= 1,) 234 437.33 T (NFS3ERR_NOENT) 108 425.33 T (= 2,) 234 425.33 T (NFS3ERR_IO) 108 413.33 T (= 5,) 234 413.33 T (NFS3ERR_NXIO) 108 401.33 T (= 6,) 234 401.33 T (NFS3ERR_ACCES) 108 389.33 T (= 13,) 234 389.33 T (NFS3ERR_EXIST) 108 377.33 T (= 17,) 234 377.33 T (NFS3ERR_XDEV) 108 365.33 T (= 18,) 234 365.33 T (NFS3ERR_NODEV) 108 353.33 T (= 19,) 234 353.33 T (NFS3ERR_NOTDIR) 108 341.33 T (= 20,) 234 341.33 T (NFS3ERR_ISDIR) 108 329.33 T (= 21,) 234 329.33 T (NFS3ERR_INVAL) 108 317.33 T (= 22,) 234 317.33 T (NFS3ERR_FBIG) 108 305.33 T (= 27,) 234 305.33 T (NFS3ERR_NOSPC) 108 293.33 T (= 28,) 234 293.33 T (NFS3ERR_ROFS) 108 281.33 T (= 30,) 234 281.33 T (NFS3ERR_MLINK) 108 269.33 T (= 31,) 234 269.33 T (NFS3ERR_NAMETOOLONG) 108 257.33 T (= 63,) 234 257.33 T (NFS3ERR_NOTEMPTY) 108 245.33 T (= 66,) 234 245.33 T (NFS3ERR_DQUOT) 108 233.33 T (= 69,) 234 233.33 T (NFS3ERR_STALE) 108 221.33 T (= 70,) 234 221.33 T (NFS3ERR_REMOTE) 108 209.33 T (= 71,) 234 209.33 T (NFS3ERR_BADHANDLE) 108 197.33 T (= 10001,) 234 197.33 T (NFS3ERR_NOT_SYNC) 108 185.33 T (= 10002,) 234 185.33 T (NFS3ERR_BAD_COOKIE) 108 173.33 T (= 10003,) 234 173.33 T (NFS3ERR_NOTSUPP) 108 161.33 T (= 10004,) 234 161.33 T (NFS3ERR_TOOSMALL) 108 149.33 T (= 10005,) 234 149.33 T (NFS3ERR_SERVERFAULT) 108 137.33 T (= 10006,) 234 137.33 T (NFS3ERR_BADTYPE) 108 125.33 T (= 10007,) 234 125.33 T (NFS3ERR_JUKEBOX) 108 113.33 T (= 10008) 234 113.33 T (};) 90 101.33 T 0 F -0.23 (The) 72 83.33 P 5 F -0.56 (nfsstat3) 89.81 83.33 P 0 F -0.23 ( type is returned with every procedure\325s results except for the) 137.78 83.33 P 4 F -0.56 (NULL) 383.06 83.33 P 0 F -0.23 ( procedure. A value of) 407.05 83.33 P 4 F -0.56 (NFS3_OK) 498.02 83.33 P FMENDPAGE %%EndPage: "8" 13 %%Page: "9" 13 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (9) 303.22 35.33 T 0 F -0.03 (indicates that the call completed successfully. Any other value indicates that some error occurred on the call, as iden-) 72 713.33 P -0.28 (tified by the error code. Note that the precise numeric encoding must be followed. No other values may be returned by) 72 701.33 P 0.36 (a server. Servers are expected to make a best effort mapping of error conditions to the set of error codes defined. In) 72 689.33 P 0.84 (addition, no error precedences are specified by this specification. Error precedences determine the error value that) 72 677.33 P -0.09 (should be returned when more than one error applies in a given situation. The error precedence will be determined by) 72 665.33 P 0 (the individual server implementation. If the client requires specific error precedences, it should check for the specific) 72 653.33 P (errors for itself.) 72 641.33 T (A description of each defined error follows.) 72 623.33 T 2 F (Defined Error Numbers) 72 601.33 T 4 F (NFS3_OK) 90 587.33 T 0 F (Indicates the call completed successfully.) 113.04 575.33 T 4 F (NFS3ERR_PERM) 90 561.33 T 0 F -0.11 (Not owner. The operation was not allowed because the caller is either not a privileged user \050root\051 or not the) 113.04 549.33 P (owner of the target of the operation.) 113.04 537.33 T 4 F (NFS3ERR_NOENT) 90 523.33 T 0 F (No such file or directory. The file or directory name specified does not exist.) 113.04 511.33 T 4 F (NFS3ERR_IO) 90 497.33 T 0 F (I/O error. A hard error \050for example, a disk error\051 occurred while processing the requested operation.) 113.04 485.33 T 4 F (NFS3ERR_NXIO) 90 471.33 T 0 F (I/O error. No such device or address.) 113.04 459.33 T 4 F (NFS3ERR_ACCES) 90 445.33 T 0 F -0.42 (Permission denied. The caller does not have the correct permission to perform the requested operation. Con-) 113.04 433.33 P (trast this with) 113.04 421.33 T 4 F (NFS3ERR_PERM) 169.96 421.33 T 0 F (, which restricts itself to owner or privileged user permission failures.) 241.92 421.33 T 4 F (NFS3ERR_EXIST) 90 407.33 T 0 F (File exists. The file specified already exists.) 113.04 395.33 T 4 F (NFS3ERR_XDEV) 90 381.33 T 0 F (Attempt to do a cross-device hard link.) 113.04 369.33 T 4 F (NFS3ERR_NODEV) 90 355.33 T 0 F (No such device.) 113.04 343.33 T 4 F (NFS3ERR_NOTDIR) 90 329.33 T 0 F (Not a directory. The caller specified a non-directory in a directory operation.) 113.04 317.33 T 4 F (NFS3ERR_ISDIR) 90 303.33 T 0 F (Is a directory. The caller specified a directory in a non-directory operation.) 113.04 291.33 T 4 F (NFS3ERR_INVAL) 90 277.33 T 0 F -0.31 (Invalid argument or unsupported argument for an operation. Two examples are attempting a) 113.04 265.33 P 4 F -0.75 (READLINK) 479.84 265.33 P 0 F -0.31 ( on) 527.82 265.33 P -0.38 (an object other than a symbolic link or attempting to) 113.04 253.33 P 4 F -0.9 (SETATTR) 321.36 253.33 P 0 F -0.38 ( a time field on a server that does not support) 363.34 253.33 P (this operation.) 113.04 241.33 T 4 F (NFS3ERR_FBIG) 90 227.33 T 0 F (File too large. The operation would have caused a file to grow beyond the server\325s limit.) 113.04 215.33 T 4 F (NFS3ERR_NOSPC) 90 201.33 T 0 F (No space left on device. The operation would have caused the server\325s file system to exceed its limit.) 113.04 189.33 T 4 F (NFS3ERR_ROFS) 90 175.33 T 0 F (Read-only file system. A modifying operation was attempted on a read-only file system.) 113.04 163.33 T 4 F (NFS3ERR_MLINK) 90 149.33 T 0 F (Too many hard links.) 113.04 137.33 T 4 F (NFS3ERR_NAMETOOLONG) 90 123.33 T 0 F (The filename in an operation was too long.) 113.04 111.33 T 4 F (NFS3ERR_NOTEMPTY) 90 97.33 T 0 F (An attempt was made to remove a directory that was not empty.) 113.04 85.33 T FMENDPAGE %%EndPage: "9" 14 %%Page: "10" 14 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (10) 300.44 35.33 T (Version 3) 495.01 35.33 T 4 F (NFS3ERR_DQUOT) 90 713.33 T 0 F (Resource \050quota\051 hard limit exceeded. The user\325s resource limit on the server has been exceeded.) 113.04 701.33 T 4 F (NFS3ERR_STALE) 90 687.33 T 0 F -0.51 (Invalid file handle. The file handle given in the arguments was invalid. The file referred to by that file handle) 113.04 675.33 P (no longer exists or access to it has been revoked.) 113.04 663.33 T 4 F (NFS3ERR_REMOTE) 90 649.33 T 0 F 0.16 (Too many levels of remote in path. The file handle given in the arguments referred to a file on a non-local) 113.04 637.33 P (file system on the server.) 113.04 625.33 T 4 F (NFS3ERR_BADHANDLE) 90 611.33 T 0 F (Illegal NFS file handle. The file handle failed internal consistency checks.) 113.04 599.33 T 4 F (NFS3ERR_NOT_SYNC) 90 585.33 T 0 F (Update synchronization mismatch was detected during a) 113.04 573.33 T 4 F (SETATTR) 341.48 573.33 T 0 F ( operation.) 383.46 573.33 T 4 F (NFS3ERR_BAD_COOKIE) 90 559.33 T (READDIR) 113.04 547.33 T 0 F ( or) 155.02 547.33 T 4 F (READDIRPLUS) 168.34 547.33 T 0 F ( cookie is stale.) 234.3 547.33 T 4 F (NFS3ERR_NOTSUPP) 90 533.33 T 0 F (Operation is not supported.) 113.04 521.33 T 4 F (NFS3ERR_TOOSMALL) 90 507.33 T 0 F (Buffer or request is too small.) 113.04 495.33 T 4 F (NFS3ERR_SERVERFAULT) 90 481.33 T 0 F -0.23 (An error occurred on the server which does not map to any of the legal NFS version 3 protocol error values.) 113.04 469.33 P -0.06 (The client should translate this into an appropriate error. UNIX clients may choose to translate this to) 113.04 457.33 P 4 F -0.14 (EIO) 519.51 457.33 P 0 F -0.06 (.) 537.5 457.33 P 4 F (NFS3ERR_BADTYPE) 90 443.33 T 0 F (An attempt was made to create an object of a type not supported by the server.) 113.04 431.33 T 4 F (NFS3ERR_JUKEBOX) 90 417.33 T 0 F 0.22 (The server initiated the request, but was not able to complete it in a timely fashion. The client should wait) 113.04 405.33 P 0.34 (and then try the request with a new RPC transaction id. For example, this error should be returned from a) 113.04 393.33 P 0.33 (server that supports hierarchical storage and receives a request to process a file that has been migrated. In) 113.04 381.33 P (this case, the server should start the immigration process and respond to client with this error.) 113.04 369.33 T 5 F (ftype3) 72 351.33 T 4 F (enum ftype3 {) 90 339.33 T (NF3REG =) 108 327.33 T (1,) 180 327.33 T (NF3DIR =) 108 315.33 T (2,) 180 315.33 T (NF3BLK =) 108 303.33 T (3,) 180 303.33 T (NF3CHR =) 108 291.33 T (4,) 180 291.33 T (NF3LNK =) 108 279.33 T (5,) 180 279.33 T (NF3SOCK =) 108 267.33 T (6,) 180 267.33 T (NF3FIFO =) 108 255.33 T (7) 180 255.33 T (};) 90 243.33 T 0 F -0.31 (The enumeration) 72 225.33 P 6 F -0.31 (,) 139.69 225.33 P 5 F -0.74 (ftype3) 144.38 225.33 P 0 F -0.31 (, gives the type of a file. The type,) 180.36 225.33 P 4 F -0.74 (NF3REG) 316.93 225.33 P 0 F -0.31 (, is a regular file,) 352.91 225.33 P 4 F -0.74 (NF3DIR) 421.59 225.33 P 0 F -0.31 ( is a directory,) 457.57 225.33 P 4 F -0.74 (NF3-) 516.01 225.33 P 0.31 (BLK) 72 213.33 P 0 F 0.13 ( is a block special device file,) 89.99 213.33 P 4 F 0.31 (NF3CHR) 211.35 213.33 P 0 F 0.13 ( is a character special device file,) 247.33 213.33 P 4 F 0.31 (NF3LNK) 383.1 213.33 P 0 F 0.13 ( is a symbolic link,) 419.08 213.33 P 4 F 0.31 (NF3SOCK) 498.02 213.33 P 0 F (is a socket, and) 72 201.33 T 4 F (NF3FIFO) 135.57 201.33 T 0 F ( is a named pipe. Note that the precise enum encoding must be followed.) 177.54 201.33 T 5 F (specdata3) 72 183.33 T 4 F (struct specdata3 {) 90 171.33 T (uint32) 108 159.33 T (specdata1;) 162 159.33 T (uint32) 108 147.33 T (specdata2;) 162 147.33 T (};) 90 135.33 T 0 F 0.02 (The interpretation of the two words depends on the type of file system object. For a block special \050) 72 117.33 P 4 F 0.05 (NF3BLK) 466.8 117.33 P 0 F 0.02 (\051 or char-) 502.78 117.33 P 0.37 (acter special \050) 72 105.33 P 4 F 0.89 (NF3CHR) 128.24 105.33 P 0 F 0.37 (\051 file,) 164.22 105.33 P 5 F 0.89 (specdata1) 189.1 105.33 P 0 F 0.37 ( and) 243.07 105.33 P 5 F 0.89 (specdata2) 263.24 105.33 P 0 F 0.37 ( are the major and minor device numbers, respectively.) 317.21 105.33 P 0.12 (\050This is obviously a UNIX-specific interpretation.\051 For all other file types, these two elements should either be set to) 72 93.33 P 0.28 (0 or the values should be agreed upon by the client and server. If the client and server do not agree upon the values,) 72 81.33 P FMENDPAGE %%EndPage: "10" 15 %%Page: "11" 15 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (11) 300.44 35.33 T 0 F -0.3 (the client should treat these fields as if they are set to) 72 713.33 P 4 F -0.73 (0) 282.66 713.33 P 0 F -0.3 (. This data field is returned as part of the) 288.65 713.33 P 5 F -0.73 (fattr3) 450.23 713.33 P 0 F -0.3 ( structure and) 486.2 713.33 P 0.29 (so is available from all replies returning attributes. Since these fields are otherwise unused for objects which are not) 72 701.33 P -0.19 (devices, out of band information can be passed from the server to the client. However, once again, both the server and) 72 689.33 P (the client must agree on the values passed.) 72 677.33 T 5 F (nfs_fh3) 72 659.33 T 4 F (struct nfs_fh3 {) 90 647.33 T (opaque) 108 635.33 T (data;) 162 635.33 T (};) 90 623.33 T 0 F -0.43 (The) 72 605.33 P 5 F -1.03 (nfs_fh3) 89.61 605.33 P 0 F -0.43 ( is the variable-length opaque object returned by the server on) 131.59 605.33 P 4 F -1.03 (LOOKUP) 376.97 605.33 P 0 F -0.43 (,) 412.95 605.33 P 4 F -1.03 (CREATE) 417.52 605.33 P 0 F -0.43 (,) 453.5 605.33 P 4 F -1.03 (SYMLINK) 458.07 605.33 P 0 F -0.43 (,) 500.05 605.33 P 4 F -1.03 (MKNOD) 507.52 605.33 P 0 F -0.43 (,) 537.5 605.33 P 4 F 0.31 (LINK) 72 593.33 P 0 F 0.13 (, or) 95.99 593.33 P 4 F 0.31 (READDIRPLUS) 112.07 593.33 P 0 F 0.13 ( operations, which is used by the client on subsequent operations to reference the file. The) 178.03 593.33 P 0.04 (file handle contains all the information the server needs to distinguish an individual file. To the client, the file handle) 72 581.33 P -0.54 (is opaque. The client stores file handles for use in a later request and can compare two file handles from the same server) 72 569.33 P -0.31 (for equality by doing a byte-by-byte comparison, but cannot otherwise interpret the contents of file handles. If two file) 72 557.33 P 0.06 (handles from the same server are equal, they must refer to the same file, but if they are not equal, no conclusions can) 72 545.33 P 0.22 (be drawn. Servers should try to maintain a one\320to\320one correspondence between file handles and files, but this is not) 72 533.33 P (required. Clients should use file handle comparisons only to improve performance, not for correct behavior.) 72 521.33 T 0.29 (Servers can revoke the access provided by a file handle at any time. If the file handle passed in a call refers to a file) 72 503.33 P 1.32 (system object that no longer exists on the server or access for that file handle has been revoked, the error,) 72 491.33 P 4 F 3.17 (NF-) 522.01 491.33 P (S3ERR_STALE) 72 479.33 T 0 F (, should be returned.) 137.96 479.33 T 5 F (nfstime3) 72 461.33 T 4 F (struct nfstime3 {) 90 449.33 T (uint32) 108 437.33 T (seconds;) 162 437.33 T (uint32) 108 425.33 T (nseconds;) 162 425.33 T (};) 90 413.33 T 0 F 0.24 (The) 72 395.33 P 5 F 0.59 (nfstime3) 90.28 395.33 P 0 F 0.24 ( structure gives the number of seconds and nanoseconds since midnight January 1, 1970 Greenwich) 138.26 395.33 P -0.04 (Mean Time. It is used to pass time and date information. The times associated with files are all server times except in) 72 383.33 P -0.01 (the case of a) 72 371.33 P 4 F -0.04 (SETATTR) 124.11 371.33 P 0 F -0.01 ( operation where the client can explicitly set the file time. A server converts to and from local) 166.09 371.33 P 0.02 (time when processing time values, preserving as much accuracy as possible. If the precision of timestamps stored for) 72 359.33 P 0.44 (a file is less than that defined by NFS version 3 protocol, loss of precision can occur. An adjunct time maintenance) 72 347.33 P (protocol is recommended to reduce client and server time skew.) 72 335.33 T 5 F (fattr3) 72 317.33 T 4 F (struct fattr3 {) 90 305.33 T (ftype3) 108 293.33 T (type;) 180 293.33 T (mode3) 108 281.33 T (mode;) 180 281.33 T (uint32) 108 269.33 T (nlink;) 180 269.33 T (uid3) 108 257.33 T (uid;) 180 257.33 T (gid3) 108 245.33 T (gid;) 180 245.33 T (size3) 108 233.33 T (size;) 180 233.33 T (size3) 108 221.33 T (used;) 180 221.33 T (specdata3) 108 209.33 T (rdev;) 180 209.33 T (uint64) 108 197.33 T (fsid;) 180 197.33 T (fileid3) 108 185.33 T (fileid;) 180 185.33 T (nfstime3) 108 173.33 T (atime;) 180 173.33 T (nfstime3) 108 161.33 T (mtime;) 180 161.33 T (nfstime3) 108 149.33 T (ctime;) 180 149.33 T (};) 90 137.33 T 0 F 0.13 (This structure defines the attributes of a file system object. It is returned by most operations on an object; in the case) 72 119.33 P 0.43 (of operations that affect two objects \050for example, a) 72 107.33 P 4 F 1.02 (MKDIR) 285.1 107.33 P 0 F 0.43 ( that modifies the target directory attributes and defines) 315.09 107.33 P 0.36 (new attributes for the newly created directory\051, the attributes for both may be returned. In some cases, the attributes) 72 95.33 P -0.15 (are returned in the structure,) 72 83.33 P 5 F -0.36 (wcc_data) 186.71 83.33 P 0 F -0.15 (, which is defined below; in other cases the attributes are returned alone. The) 234.68 83.33 P FMENDPAGE %%EndPage: "11" 16 %%Page: "12" 16 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (12) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F 0.54 (main changes from the NFS version 2 protocol are that many of the fields have been widened and the major/minor) 72 713.33 P (device information is now presented in a distinct structure rather than being packed into a word.) 72 701.33 T 0.44 (The) 72 683.33 P 5 F 1.06 (fattr3) 90.48 683.33 P 0 F 0.44 ( structure contains the basic attributes of a file. All servers should support this set of attributes even if) 126.46 683.33 P -0.06 (they have to simulate some of the fields.) 72 671.33 P 5 F -0.14 (Type) 235.58 671.33 P 0 F -0.06 ( is the type of the file.) 259.57 671.33 P 5 F -0.14 (Mode) 349.08 671.33 P 0 F -0.06 ( is the protection mode bits.) 373.07 671.33 P 5 F -0.14 (Nlink) 486.26 671.33 P 0 F -0.06 ( is the) 516.24 671.33 P -0.56 (number of hard links to the file\321that is, the number of different names for the same file.) 72 659.33 P 5 F -1.36 (Uid) 419.65 659.33 P 0 F -0.56 ( is the user id of the owner) 437.64 659.33 P 0.39 (of the file.) 72 647.33 P 5 F 0.94 (Gid) 117.04 647.33 P 0 F 0.39 ( is the group id of the group of the file.) 135.03 647.33 P 5 F 0.94 (Size) 297.03 647.33 P 0 F 0.39 ( is the size of the file in bytes.) 321.02 647.33 P 5 F 0.94 (Used) 446.7 647.33 P 0 F 0.39 ( is the number of) 470.69 647.33 P -0.05 (bytes of disk space that the file actually uses \050which can be smaller than the) 72 635.33 P 5 F -0.13 (size) 376.23 635.33 P 0 F -0.05 ( because the file may have) 400.22 635.33 P 3 F -0.05 (holes) 508.13 635.33 P 0 F -0.05 ( or) 529.23 635.33 P 0.5 (it may be larger due to fragmentation\051.) 72 623.33 P 5 F 1.21 (Rdev) 232.62 623.33 P 0 F 0.5 ( describes the device file if the file type is) 256.61 623.33 P 4 F 1.21 (NF3CHR) 430.95 623.33 P 0 F 0.5 ( or) 466.93 623.33 P 4 F 1.21 (NF3BLK) 481.26 623.33 P 0 F 0.5 (\321see) 517.24 623.33 P 5 F -0.4 (specdata3) 72 611.33 P 0 F -0.17 ( on page 10) 125.97 611.33 P -0.17 (.) 171.83 611.33 P 5 F -0.4 (Fsid) 176.66 611.33 P 0 F -0.17 ( is the file system identifier for the file system.) 200.65 611.33 P 5 F -0.4 ( Fileid) 385.71 611.33 P 0 F -0.17 ( is a number which uniquely) 427.29 611.33 P 0.37 (identifies the file within its file system \050on UNIX this would be the inumber\051.) 72 599.33 P 5 F 0.88 (Atime) 389.46 599.33 P 0 F 0.37 ( is the time when the file data) 419.45 599.33 P 0.2 (was last accessed.) 72 587.33 P 5 F 0.47 (Mtime) 146.97 587.33 P 0 F 0.2 ( is the time when the file data was last modified.) 176.96 587.33 P 5 F 0.47 (Ctime) 375.11 587.33 P 0 F 0.2 ( is the time when the attributes of) 405.09 587.33 P (the file were last changed. Writing to the file changes the) 72 575.33 T 5 F (ctime) 302.93 575.33 T 0 F ( in addition to the) 332.92 575.33 T 5 F (mtime) 405.94 575.33 T 0 F (.) 435.92 575.33 T (The) 72 557.33 T 5 F (mode) 90.04 557.33 T 0 F ( bits are defined as follows:) 114.03 557.33 T (0x00800) 90 541.33 T (Set user id on execution.) 144 541.33 T (0x00400) 90 529.33 T (Set group id on execution.) 144 529.33 T (0x00200) 90 517.33 T (Save swapped text \050not defined in POSIX\051.) 144 517.33 T (0x00100) 90 505.33 T (Read permission for owner.) 144 505.33 T (0x00080) 90 493.33 T (Write permission for owner.) 144 493.33 T (0x00040) 90 481.33 T (Execute permission for owner on a file. Or lookup \050search\051 permission for owner in directory.) 144 481.33 T (0x00020) 90 469.33 T (Read permission for group.) 144 469.33 T (0x00010) 90 457.33 T (Write permission for group.) 144 457.33 T (0x00008) 90 445.33 T (Execute permission for group on a file. Or lookup \050search\051 permission for group in directory.) 144 445.33 T (0x00004) 90 433.33 T (Read permission for others.) 144 433.33 T (0x00002) 90 421.33 T (Write permission for others.) 144 421.33 T (0x00001) 90 409.33 T (Execute permission for others on a file. Or lookup \050search\051 permission for others in directory.) 144 409.33 T 5 F (post_op_attr) 72 391.33 T 4 F (union post_op_attr switch \050bool attributes_follow\051{) 90 379.33 T (case TRUE:) 90 367.33 T (fattr3) 108 355.33 T (attributes;) 162 355.33 T (case FALSE:) 90 343.33 T (void;) 108 331.33 T (};) 90 319.33 T 0 F 0.31 (This structure is used for returning attributes in those operations that are not directly involved with manipulating at-) 72 301.33 P -0.08 (tributes. One of the principles of this revision of the NFS protocol is to return the real value from the indicated opera-) 72 289.33 P -0.28 (tion and not an error from an incidental operation. The) 72 277.33 P 5 F -0.67 (post_op_attr) 289.86 277.33 P 0 F -0.28 ( structure was designed to allow the server to) 361.82 277.33 P (recover from errors encountered while getting attributes.) 72 265.33 T 0.36 (This appears to make returning attributes optional. However, server implementors are) 72 247.33 P 6 F 0.36 (strongly) 420.96 247.33 P 0 F 0.36 ( encouraged to make) 455.94 247.33 P (best effort to return attributes whenever possible, even when returning an error.) 72 235.33 T 5 F (wcc_attr) 72 217.33 T 4 F (struct wcc_attr {) 90 205.33 T (size3) 108 193.33 T (size;) 180 193.33 T (nfstime3) 108 181.33 T (mtime;) 180 181.33 T (nfstime3) 108 169.33 T (ctime;) 180 169.33 T (};) 90 157.33 T 0 F (This is the subset of pre-operation attributes needed to better support the weak cache consistency semantics. Size is) 72 139.33 T -0.07 (the file size in bytes of the object before the operation. Mtime is the time of last modification of the object before the) 72 127.33 P (operation. Ctime is the time of last change to the attributes of the object before the operation. See discussion in) 72 115.33 T 5 F (wcc_attr) 72 103.33 T 0 F ( on page 12.) 119.97 103.33 T 0.2 (The use of) 72 85.33 P 5 F 0.48 (mtime) 117.28 85.33 P 0 F 0.2 ( by clients to detect changes to file system objects residing on a server is dependent on the granu-) 147.26 85.33 P FMENDPAGE %%EndPage: "12" 17 %%Page: "13" 17 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (13) 300.44 35.33 T 0 F (larity of the time base on the server.) 72 713.33 T 5 F (pre_op_attr) 72 695.33 T 4 F (union pre_op_attr switch \050bool attributes_follow\051{) 90 683.33 T (case TRUE:) 90 671.33 T (wcc_attr) 108 659.33 T (attributes;) 180 659.33 T (case FALSE:) 90 647.33 T (void;) 108 635.33 T (};) 90 623.33 T 5 F (wcc_data) 72 605.33 T 4 F (struct wcc_data {) 90 589.33 T (pre_op_attr) 108 577.33 T (before;) 198 577.33 T (post_op_attr) 108 565.33 T (after;) 198 565.33 T (};) 90 553.33 T 0 F 0.1 (When a client performs an operation that modifies the state of a file or directory on the server, it cannot immediately) 72 535.33 P -0.42 (determine from the post-operation attributes whether the operation just performed was the only operation on the object) 72 523.33 P 0.13 (since the last time the client received the attributes for the object. This is important, since if an intervening operation) 72 511.33 P 6 F -0.09 (has) 72 499.33 P 0 F -0.09 ( changed the object, the client will need to invalidate any cached data for the object \050except for the data that it just) 86.44 499.33 P (wrote\051.) 72 487.33 T -0.52 (To deal with this, the notion of) 72 469.33 P 3 F -0.52 (weak cache consistency data) 194.41 469.33 P 0 F -0.52 ( or) 308.03 469.33 P 5 F -1.25 (wcc_data) 320.32 469.33 P 0 F -0.52 ( is introduced. A) 368.29 469.33 P 5 F -1.25 (wcc_data) 435.34 469.33 P 0 F -0.52 ( structure con-) 483.31 469.33 P 0.2 (sists of certain key fields from the object attributes) 72 457.33 P 6 F 0.2 (before) 278.95 457.33 P 0 F 0.2 ( the operation, together with the object attributes) 306.14 457.33 P 6 F 0.2 (after) 504.56 457.33 P 0 F 0.2 ( the) 525.09 457.33 P -0.02 (operation. This information allows the client to manage its cache more accurately than in NFS version 2 protocol im-) 72 445.33 P -0.09 (plementations. The term,) 72 433.33 P 3 F -0.09 (weak cache consistency) 174.17 433.33 P 0 F -0.09 (, emphasizes the fact that this mechanism does not provide the strict) 268.92 433.33 P (server-client consistency that a cache consistency protocol would provide.) 72 421.33 T -0.35 (In order to support the) 72 403.33 P 3 F -0.35 (weak cache consistency) 162.15 403.33 P 0 F -0.35 ( model, the server will need to be able to get the pre-operation attributes) 256.38 403.33 P 0.06 (of the object, perform the intended modify operation, and then get the post-operation attributes atomically. If there is) 72 391.33 P -0.46 (a window for the object to get modified between the operation and either of the get attributes operations, then the client) 72 379.33 P -0.41 (will not be able to determine whether it was the only entity to modify the object. Some information will have been lost,) 72 367.33 P (thus weakening the) 72 355.33 T 3 F (weak cache consistency) 151.67 355.33 T 0 F ( guarantees.) 246.58 355.33 T 5 F (post_op_fh3) 72 337.33 T 4 F (union post_op_fh3 switch \050bool handle_follows\051{) 90 325.33 T (case TRUE:) 90 313.33 T (nfs_fh3) 108 301.33 T (handle;) 180 301.33 T (case FALSE:) 90 289.33 T (void;) 108 277.33 T (};) 90 265.33 T 0 F 0.2 (One of the principles of this revision of the NFS protocol is to return the real value from the indicated operation and) 72 247.33 P 0.2 (not an error from an incidental operation. The) 72 235.33 P 5 F 0.49 (post_op_fh3) 259.32 235.33 P 0 F 0.2 ( structure was designed to allow the server to recover) 325.28 235.33 P (from errors encountered while constructing a file handle.) 72 223.33 T -0.03 (This is the structure used to return a file handle from the) 72 205.33 P 4 F -0.06 (CREATE) 299.32 205.33 P 0 F -0.03 (,) 335.3 205.33 P 4 F -0.06 (MKDIR) 340.27 205.33 P 0 F -0.03 (,) 370.25 205.33 P 4 F -0.06 (SYMLINK) 375.23 205.33 P 0 F -0.03 (,) 417.2 205.33 P 4 F -0.06 (MKNOD) 422.17 205.33 P 0 F -0.03 (, and) 452.16 205.33 P 4 F -0.06 (READDIRPLUS) 474.04 205.33 P 0 F -0.38 (requests. In each case, the client can get the file handle by issuing a) 72 193.33 P 4 F -0.9 (LOOKUP) 338.74 193.33 P 0 F -0.38 ( request after a successful return from one) 374.72 193.33 P -0.41 (of the listed operations. Returning the file handle is an optimization so that the client is not forced to immediately issue) 72 181.33 P (a) 72 169.33 T 4 F (LOOKUP) 78.94 169.33 T 0 F ( request to get the file handle.) 114.92 169.33 T FMENDPAGE %%EndPage: "13" 18 %%Page: "14" 18 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (14) 300.44 35.33 T (Version 3) 495.01 35.33 T 72 72 540 720 R 7 X V 5 F 0 X (sattr3) 72 713.33 T 4 F (enum time_how {) 90 701.33 T (DONT_CHANGE) 108 689.33 T (= 0,) 234 689.33 T (SET_TO_SERVER_TIME) 108 677.33 T (= 1,) 234 677.33 T (SET_TO_CLIENT_TIME) 108 665.33 T (= 2) 234 665.33 T (};) 90 653.33 T (union set_mode3 switch \050bool set_it\051 {) 90 641.33 T (case TRUE:) 90 629.33 T (mode3) 108 617.33 T (mode;) 162 617.33 T (default:) 90 605.33 T (void;) 108 593.33 T (};) 90 581.33 T (union set_uid3 switch \050bool set_it\051 {) 90 569.33 T (case TRUE:) 90 557.33 T (uid3) 108 545.33 T (uid;) 162 545.33 T (default:) 90 533.33 T (void;) 108 521.33 T (};) 90 509.33 T (union set_gid3 switch \050bool set_it\051 {) 90 497.33 T (case TRUE:) 90 485.33 T (gid3) 108 473.33 T (gid;) 162 473.33 T (default:) 90 461.33 T (void;) 108 449.33 T (};) 90 437.33 T (union set_size3 switch \050bool set_it\051 {) 90 425.33 T (case TRUE:) 90 413.33 T (size3) 108 401.33 T (size;) 162 401.33 T (default:) 90 389.33 T (void;) 108 377.33 T (};) 90 365.33 T (union set_atime switch \050time_how set_it\051 {) 90 353.33 T (case SET_TO_CLIENT_TIME:) 90 341.33 T (nfstime3) 108 329.33 T (atime;) 162 329.33 T (default:) 90 317.33 T (void;) 108 305.33 T (};) 90 293.33 T (union set_mtime switch \050time_how set_it\051 {) 90 281.33 T (case SET_TO_CLIENT_TIME:) 90 269.33 T (nfstime3) 108 257.33 T (mtime;) 162 257.33 T (default:) 90 245.33 T (void;) 108 233.33 T (};) 90 221.33 T (struct sattr3 {) 90 197.33 T (set_mode3) 108 185.33 T (mode;) 180 185.33 T (set_uid3) 108 173.33 T (uid;) 180 173.33 T (set_gid3) 108 161.33 T (gid;) 180 161.33 T (set_size3) 108 149.33 T (size;) 180 149.33 T (set_atime) 108 137.33 T (atime;) 180 137.33 T (set_mtime) 108 125.33 T (mtime;) 180 125.33 T (};) 90 113.33 T 0 F -0.55 (The) 72 95.33 P 5 F -1.32 (sattr3) 89.49 95.33 P 0 F -0.55 ( structure contains the file attributes that can be set from the client. The fields are the same as the similarly) 125.47 95.33 P -0.56 (named fields in the) 72 83.33 P 5 F -1.35 (fattr3) 148.58 83.33 P 0 F -0.56 ( structure. In the NFS version 3 protocol, the settable attributes are described by a structure) 184.56 83.33 P FMENDPAGE %%EndPage: "14" 19 %%Page: "15" 19 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (15) 300.44 35.33 T 0 F 0.45 (containing a set of discriminated unions. Each union indicates whether the corresponding attribute is to be updated,) 72 713.33 P (and if so, how.) 72 701.33 T 0.01 (There are two forms of discriminated unions used. In setting the) 72 683.33 P 5 F 0.02 (mode) 330.79 683.33 P 0 F 0.01 (,) 354.78 683.33 P 5 F 0.02 (uid) 359.78 683.33 P 0 F 0.01 (,) 377.77 683.33 P 5 F 0.02 (gid) 382.78 683.33 P 0 F 0.01 (, or) 400.77 683.33 P 5 F 0.02 (size) 416.6 683.33 P 0 F 0.01 (, the discriminated union) 440.59 683.33 P (is switched on a boolean,) 72 671.33 T 5 F (set_it) 175.26 671.33 T 0 F (; if it is) 211.24 671.33 T 4 F (TRUE) 242.35 671.33 T 0 F (, a value of the appropriate type is then encoded.) 266.33 671.33 T 0.42 (In setting the) 72 653.33 P 5 F 1.01 (atime) 127.95 653.33 P 0 F 0.42 ( or) 157.93 653.33 P 5 F 1.01 (mtime) 172.09 653.33 P 0 F 0.42 (, the union is switched on an enumeration type,) 202.07 653.33 P 5 F 1.01 (set_it) 397.11 653.33 P 0 F 0.42 (. If) 433.09 653.33 P 5 F 1.01 (set_it) 448.08 653.33 P 0 F 0.42 ( has the value) 484.06 653.33 P 4 F 0.64 (DONT_CHANGE) 72 641.33 P 0 F 0.27 (, the corresponding attribute is unchanged. If it has the value,) 137.96 641.33 P 4 F 0.64 (SET_TO_SERVER_TIME) 387.96 641.33 P 0 F 0.27 (, the corre-) 495.9 641.33 P 0.33 (sponding attribute is set by the server to its local time; no data is provided by the client. Finally, if) 72 629.33 P 5 F 0.79 (set_it) 472.83 629.33 P 0 F 0.33 ( has the) 508.8 629.33 P -0.09 (value,) 72 617.33 P 4 F -0.22 (SET_TO_CLIENT_TIME) 98.55 617.33 P 0 F -0.09 (, the attribute is set to the time passed by the client in an) 206.49 617.33 P 5 F -0.22 (nfstime3) 431.99 617.33 P 0 F -0.09 ( structure. \050See) 479.96 617.33 P 4 F (FSINFO) 72 605.33 T 0 F ( on page 59, which addresses the issue of time granularity\051.) 107.98 605.33 T 5 F (diropargs3) 72 587.33 T 4 F (struct diropargs3 {) 90 575.33 T (nfs_fh3) 108 563.33 T (dir;) 180 563.33 T (filename3) 108 551.33 T (name;) 180 551.33 T (};) 90 539.33 T 0 F -0.11 (The) 72 521.33 P 5 F -0.27 (diropargs3) 89.93 521.33 P 0 F -0.11 ( structure is used in directory operations. The file handle,) 149.9 521.33 P 5 F -0.27 (dir) 379.72 521.33 P 0 F -0.11 (, identifies the directory in which to) 397.71 521.33 P (manipulate or access the file,) 72 509.33 T 5 F (name) 190.79 509.33 T 0 F (. See additional comments in) 214.78 509.33 T 3 F (File name component handling) 333.05 509.33 T 0 F ( on page 69.) 457.69 509.33 T FMENDPAGE %%EndPage: "15" 20 %%Page: "16" 20 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (16) 300.44 35.33 T (Version 3) 495.01 35.33 T (Server Procedures) 72 713.33 T 0 F 0.48 (The following sections define the RPC procedures that are supplied by an NFS version 3 protocol server. The RPC) 72 695.33 P -0.24 (procedure number is given at the top of the page with the name and version. The SYNOPSIS provides the name of the) 72 683.33 P 0.08 (procedure, the list of the names of the arguments, the list of the names of the results, followed by the XDR argument) 72 671.33 P 0.48 (declarations and results declarations. The information in the SYNOPSIS is specified in RPC Data Description Lan-) 72 659.33 P 0.32 (guage as defined in) 72 647.33 P 3 F 0.32 ([RFC1014]) 153.23 647.33 P 0 F 0.32 (. The DESCRIPTION section tells what the procedure is expected to do and how its) 199.87 647.33 P -0.25 (arguments and results are used. The ERRORS section lists the errors returned for specific types of failures. These lists) 72 635.33 P -0.18 (are not intended to be the definitive statement of all of the errors which can be returned by any specific procedure, but) 72 623.33 P -0.44 (as a guide for the more common errors which may be returned. Client implementations should be prepared to deal with) 72 611.33 P 0.02 (unexpected errors coming from a server. The IMPLEMENTATION field gives information about how the procedure) 72 599.33 P (is expected to work and how it should be used by clients.) 72 587.33 T 8 F (The list of procedures) 72 565.33 T 4 F (program NFS_PROGRAM {) 90 549.33 T (version NFS_V3 {) 108 538.33 T (void) 126 527.33 T ( NFSPROC3_NULL\050void\051) 126 516.33 T (= 0;) 360 516.33 T (GETATTR3res) 126 505.33 T ( NFSPROC3_GETATTR\050GETATTR3args\051) 126 494.33 T (= 1;) 360 494.33 T (SETATTR3res) 126 483.33 T ( NFSPROC3_SETATTR\050SETATTR3args\051) 126 472.33 T (= 2;) 360 472.33 T (LOOKUP3res) 126 461.33 T ( NFSPROC3_LOOKUP\050LOOKUP3args\051) 126 450.33 T (= 3;) 360 450.33 T (ACCESS3res) 126 439.33 T ( NFSPROC3_ACCESS\050ACCESS3args\051) 126 428.33 T (= 4;) 360 428.33 T (READLINK3res) 126 417.33 T ( NFSPROC3_READLINK\050READLINK3args\051) 126 406.33 T (= 5;) 360 406.33 T (READ3res) 126 395.33 T ( NFSPROC3_READ\050READ3args\051) 126 384.33 T (= 6;) 360 384.33 T (WRITE3res) 126 373.33 T ( NFSPROC3_WRITE\050WRITE3args\051) 126 362.33 T (= 7;) 360 362.33 T (CREATE3res) 126 351.33 T ( NFSPROC3_CREATE\050CREATE3args\051) 126 340.33 T (= 8;) 360 340.33 T (MKDIR3res) 126 329.33 T ( NFSPROC3_MKDIR\050MKDIR3args\051) 126 318.33 T (= 9;) 360 318.33 T (SYMLINK3res) 126 307.33 T ( NFSPROC3_SYMLINK\050SYMLINK3args\051) 126 296.33 T (= 10;) 360 296.33 T (MKNOD3res) 126 285.33 T ( NFSPROC3_MKNOD\050MKNOD3args\051) 126 274.33 T (= 11;) 360 274.33 T (REMOVE3res) 126 263.33 T ( NFSPROC3_REMOVE\050REMOVE3args\051) 126 252.33 T (= 12;) 360 252.33 T (RMDIR3res) 126 241.33 T ( NFSPROC3_RMDIR\050RMDIR3args\051) 126 230.33 T (= 13;) 360 230.33 T (RENAME3res) 126 219.33 T ( NFSPROC3_RENAME\050RENAME3args\051) 126 208.33 T (= 14;) 360 208.33 T (LINK3res) 126 197.33 T ( NFSPROC3_LINK\050LINK3args\051) 126 186.33 T (= 15;) 360 186.33 T (READDIR3res) 126 175.33 T ( NFSPROC3_READDIR\050READDIR3args\051) 126 164.33 T (= 16;) 360 164.33 T (READDIRPLUS3res) 126 153.33 T ( NFSPROC3_READDIRPLUS\050READDIRPLUS3args\051) 126 142.33 T (= 17;) 359.87 142.33 T (FSSTAT3res) 126 131.33 T ( NFSPROC3_FSSTAT\050FSSTAT3args\051) 126 120.33 T (= 18;) 360 120.33 T (FSINFO3res) 126 109.33 T ( NFSPROC3_FSINFO\050FSINFO3args\051) 126 98.33 T (= 19;) 360 98.33 T (PATHCONF3res) 126 87.33 T ( NFSPROC3_PATHCONF\050PATHCONF3args\051) 126 76.33 T (= 20;) 360 76.33 T FMENDPAGE %%EndPage: "16" 21 %%Page: "17" 21 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (17) 300.44 35.33 T 4 F (COMMIT3res) 126 713.33 T ( NFSPROC3_COMMIT\050COMMIT3args\051) 126 702.33 T (= 21;) 360 702.33 T (} = 3;) 108 691.33 T (} = 100003;) 90 680.33 T 0 F (Out of range \050undefined\051 procedure numbers result in RPC errors. Refer to) 72 663.33 T 3 F ([RFC1057]) 373.15 663.33 T 0 F ( for more detail.) 419.8 663.33 T 8 F (General comments on attributes and consistency data on failure) 72 641.33 T 0 F -0.18 (For those procedures that return either) 72 623.33 P 5 F -0.43 (post_op_attr) 226.36 623.33 P 0 F -0.18 ( or) 298.32 623.33 P 5 F -0.43 (wcc_data) 311.28 623.33 P 0 F -0.18 ( structures on failure, the discriminated union) 359.26 623.33 P -0.39 (may contain the pre-operation attributes of the object or object parent directory. This depends on the error encountered) 72 611.33 P -0.61 (and may also depend on the particular server implementation. Implementors are) 72 599.33 P 6 F -0.61 (strongly) 387.32 599.33 P 0 F -0.61 ( encouraged to return as much) 422.3 599.33 P 0.26 (attribute data as possible upon failure, but client implementors need to be aware that their implementation must cor-) 72 587.33 P (rectly handle the variant return instance where no attributes or consistency data is returned.) 72 575.33 T 8 F (General comments on filenames) 72 553.33 T 0 F -0.31 (The following comments apply to all NFS version 3 protocol procedures in which the client provides one or more file-) 72 535.33 P (names in the arguments:) 72 523.33 T 4 F (LOOKUP) 171.93 523.33 T 0 F (,) 207.91 523.33 T 4 F (CREATE) 212.91 523.33 T 0 F (,) 248.89 523.33 T 4 F (MKDIR) 253.89 523.33 T 0 F (,) 283.87 523.33 T 4 F (SYMLINK) 288.87 523.33 T 0 F (,) 330.85 523.33 T 4 F (MKNOD) 335.85 523.33 T 0 F (,) 365.83 523.33 T 4 F (REMOVE) 370.83 523.33 T 0 F (,) 406.81 523.33 T 4 F (RMDIR) 411.8 523.33 T 0 F (,) 441.79 523.33 T 4 F (RENAME) 446.78 523.33 T 0 F (, and) 482.76 523.33 T 4 F (LINK) 504.69 523.33 T 0 F (.) 528.68 523.33 T 1 F (1.) 90 507.33 T 0 F 2.12 (The filename must not be null nor may it be the null string. The server should return the error,) 108 507.33 P 4 F 0.18 (NFS3ERR_ACCES) 108 495.33 P 0 F 0.08 (, if it receives such a filename. On some clients, the filename, \324\324\325\325 or a null string, is) 185.96 495.33 P 0.47 (assumed to be an alias for the current directory. Clients which require this functionality should imple-) 108 483.33 P (ment it for themselves and not depend upon the server to support such semantics.) 108 471.33 T 1 F (2.) 90 457.33 T 0 F 0.55 ( A filename having the value of \322) 108 457.33 P 4 F 1.33 (.) 245.38 457.33 P 0 F 0.55 (\323 is assumed to be an alias for the current directory. Clients which) 251.38 457.33 P 0.08 (require this functionality should implement it for themselves and not depend upon the server to support) 108 445.33 P (such semantics. However, the server should be able to handle such a filename correctly.) 108 433.33 T 1 F (3.) 90 419.33 T 0 F -0.27 (A filename having the value of \322) 108 419.33 P 4 F -0.65 (..) 237.37 419.33 P 0 F -0.27 (\323 is assumed to be an alias for the parent of the current directory, i.e..) 249.37 419.33 P -0.43 (the directory which contains the current directory. The server should be prepared to handle this semantic,) 108 407.33 P (if it supports directories, even if those directories do not contain UNIX-style \322) 108 395.33 T 4 F (.) 420.28 395.33 T 0 F (\323 or \322) 426.27 395.33 T 4 F (..) 448.47 395.33 T 0 F (\323 entries.) 460.47 395.33 T 1 F (4.) 90 381.33 T 0 F -0.43 (If the filename is longer than the maximum for the file system \050see) 108 381.33 P 4 F -1.03 (PATHCONF) 371.93 381.33 P 0 F -0.43 ( on page 62) 419.9 381.33 P 4 F -1.03 (,) 464.96 381.33 P 0 F -0.43 (specifically) 475.92 381.33 P 4 F 2.72 (name_max) 108 369.33 P 0 F 1.13 (\051, the result depends on the value of the) 155.97 369.33 P 4 F 2.72 (PATHCONF) 326.06 369.33 P 0 F 1.13 ( flag,) 374.03 369.33 P 5 F 2.72 (no_trunc) 399.33 369.33 P 0 F 1.13 (. If) 447.31 369.33 P 5 F 2.72 (no_trunc) 463.73 369.33 P 0 F 1.13 ( is) 511.7 369.33 P 4 F -0.78 (FALSE) 108 357.33 P 0 F -0.32 (, the filename will be silently truncated to) 137.98 357.33 P 5 F -0.78 (name_max) 304.45 357.33 P 0 F -0.32 ( bytes. If) 352.42 357.33 P 5 F -0.78 (no_trunc) 389.2 357.33 P 0 F -0.32 ( is) 437.18 357.33 P 4 F -0.78 (TRUE) 448.19 357.33 P 0 F -0.32 ( and the file-) 472.18 357.33 P 0.31 (name exceeds the server\325s file system maximum filename length, the operation will fail with the error,) 108 345.33 P 4 F (NFS3ERR_NAMETOOLONG) 108 333.33 T 0 F (.) 221.94 333.33 T 1 F (5.) 90 319.33 T 0 F 0.01 (In general, there will be characters that a server will not be able to handle as part of a filename. This set) 108 319.33 P -0.18 (of characters will vary from server to server and from implementation to implementation. In most cases,) 108 307.33 P 0.46 (it is the server which will control the client\325s view of the file system. If the server receives a filename) 108 295.33 P 0.43 (containing characters that it can not handle, the error,) 108 283.33 P 4 F 1.03 (NFS3ERR_EACCES) 327.51 283.33 P 0 F 0.43 (, should be returned. Client) 411.47 283.33 P (implementations should be prepared to handle this side affect of heterogeneity.) 108 271.33 T (See also comments in) 72 253.33 T 3 F (File name component handling) 161.39 253.33 T 0 F ( on page 69.) 286.03 253.33 T FMENDPAGE %%EndPage: "17" 22 %%Page: "18" 22 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (18) 300.44 35.33 T (Version 3) 495.01 35.33 T 2 12 Q (Procedure) 72 712 T (0) 153.17 712 T (NULL) 289.29 712 T 2 10 Q (NULL: Do nothing) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (void) 90 651.33 T (NFSPROC3_NULL\050void\051 = 0;) 90 639.33 T 8 F (DESCRIPTION) 72 617.33 T 0 F (Procedure) 72 599.33 T 4 F (NULL) 115.02 599.33 T 0 F ( does not do any work. It is made available to allow server response testing and timing.) 139 599.33 T 8 F (IMPLEMENTATION) 72 577.33 T 0 F -0.09 (It is important that this procedure do no work at all so that it can be used to measure the overhead of processing a ser-) 72 559.33 P -0.2 (vice request. By convention, the) 72 547.33 P 4 F -0.48 (NULL) 202.29 547.33 P 0 F -0.2 ( procedure should never require any authentication. A server may choose to ig-) 226.28 547.33 P 0.27 (nore this convention, in a more secure implementation, where responding to the) 72 535.33 P 4 F 0.65 (NULL) 396.7 535.33 P 0 F 0.27 ( procedure call acknowledges) 420.68 535.33 P (the existence of a resource to an unauthenticated client.) 72 523.33 T 8 F (ERRORS) 72 501.33 T 0 F -0.52 (Since the) 72 483.33 P 4 F -1.24 (NULL) 110.39 483.33 P 0 F -0.52 ( procedure takes no NFS version 3 protocol arguments and returns no NFS version 3 protocol response,) 134.37 483.33 P -0.28 (it can not return an NFS version 3 protocol error. However, it is possible that some server implementations may return) 72 471.33 P (RPC errors based on security and authentication requirements.) 72 459.33 T FMENDPAGE %%EndPage: "18" 23 %%Page: "19" 23 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (19) 300.44 35.33 T 4 F (GETATTR) 498.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (1) 152.84 710.67 T (GETATTR) 272.51 710.67 T 2 10 Q (GETATTR: Get file attributes) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (GETATTR3res) 90 649.33 T (NFSPROC3_GETATTR\050GETATTR3args\051 = 1;) 90 637.33 T (struct GETATTR3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (object;) 162 601.33 T (};) 90 589.33 T (struct GETATTR3resok {) 90 565.33 T (fattr3) 108 553.33 T (obj_attributes;) 162 553.33 T (};) 90 541.33 T (union GETATTR3res switch \050nfsstat3 status\051 {) 90 517.33 T (case NFS3_OK:) 90 505.33 T (GETATTR3resok) 108 493.33 T (resok;) 198 493.33 T (default:) 90 481.33 T (void;) 108 469.33 T (};) 90 457.33 T 8 F (DESCRIPTION) 72 435.33 T 0 F -0.27 (Procedure) 72 417.33 P 4 F -0.64 (GETATTR) 114.75 417.33 P 0 F -0.27 ( retrieves the attributes for a specified file system object.) 156.73 417.33 P -0.27 (The object is identified by the file han-) 386.15 417.33 P 1.79 (dle that the server returned as part of the response from a) 72 405.33 P 4 F 4.3 (LOOKUP) 323.84 405.33 P 0 F 1.79 (,) 359.82 405.33 P 4 F 4.3 (CREATE) 366.6 405.33 P 0 F 1.79 (,) 402.58 405.33 P 4 F 4.3 (MKDIR) 409.37 405.33 P 0 F 1.79 (,) 439.35 405.33 P 4 F 4.3 (SYMLINK) 446.14 405.33 P 0 F 1.79 (,) 488.12 405.33 P 4 F 4.3 (MKNOD) 494.9 405.33 P 0 F 1.79 (, or) 524.89 405.33 P 4 F 8.23 (READDIRPLUS) 72 393.33 P 0 F 3.43 ( procedure \050or from the) 137.96 393.33 P 4 F 8.23 (MOUNT) 250.85 393.33 P 0 F 3.43 ( service, described elsewhere\051. On entry, the arguments in) 280.83 393.33 P 5 F (GETATTR3args) 72 381.33 T 0 F ( are) 143.96 381.33 T 5 F (:) 158.66 381.33 T (object) 90 365.33 T 0 F (The file handle of an object whose attributes are to be retrieved.) 216 365.33 T (On successful return,) 72 347.33 T 5 F (GETATTR3res.status) 159.15 347.33 T 0 F ( is) 267.09 347.33 T 4 F (NFS3_OK) 278.76 347.33 T 0 F ( and) 320.73 347.33 T 5 F (GETATTR3res.resok) 340.16 347.33 T 0 F ( contains:) 442.11 347.33 T 5 F (obj_attributes) 90 331.33 T 0 F (The attributes for the object.) 216 331.33 T (Otherwise,) 72 313.33 T 5 F (GETATTR3res.status) 118.07 313.33 T 0 F ( contains the error on failure and no other results are returned.) 226.01 313.33 T 8 F (IMPLEMENTATION) 72 291.33 T 0 F 0.71 (The attributes of file system objects is a point of major disagreement between different operating systems. Servers) 72 273.33 P -0.19 (should make a best attempt to support all of the attributes in the) 72 261.33 P 5 F -0.47 (fattr3) 326.27 261.33 P 0 F -0.19 (structure so that clients can count on this as) 367.78 261.33 P (a common ground. Some mapping may be required to map local attributes to those in the) 72 249.33 T 5 F (fattr3) 430.38 249.33 T 0 F ( structure.) 466.36 249.33 T 0.41 (Today, most client NFS version 3 protocol implementations implement a time-bounded attribute caching scheme to) 72 231.33 P (reduce over-the-wire attribute checks.) 72 219.33 T 8 F (ERRORS) 72 197.33 T 4 F (NFS3ERR_IO) 90 181.33 T (NFS3ERR_STALE) 90 169.33 T (NFS3ERR_BADHANDLE) 90 157.33 T (NFS3ERR_SERVERFAULT) 90 145.33 T 8 F (SEE ALSO) 72 123.33 T 4 F (ACCESS on page 24.) 72 105.33 T FMENDPAGE %%EndPage: "19" 24 %%Page: "20" 24 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (SETATTR) 72 35.33 T 2 F (20) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (2) 152.84 710.67 T (SETATTR) 274.06 710.67 T 2 10 Q (SETATTR: Set file attributes) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (SETATTR3res) 90 649.33 T (NFSPROC3_SETATTR\050SETATTR3args\051 = 2;) 90 637.33 T (union sattrguard3 switch \050bool check\051 {) 90 613.33 T (case TRUE:) 90 601.33 T (nfstime3) 108 589.33 T (obj_ctime;) 180 589.33 T (case FALSE:) 90 577.33 T (void;) 108 565.33 T (};) 90 553.33 T (struct SETATTR3args {) 90 529.33 T (nfs_fh3) 108 517.33 T (object;) 180 517.33 T (sattr3) 108 505.33 T (new_attributes;) 180 505.33 T (sattrguard3) 108 493.33 T (guard;) 180 493.33 T (};) 90 481.33 T (struct SETATTR3resok {) 90 457.33 T (wcc_data) 108 445.33 T (obj_wcc;) 180 445.33 T (};) 90 433.33 T (struct SETATTR3resfail {) 90 409.33 T (wcc_data) 108 397.33 T (obj_wcc;) 180 397.33 T (};) 90 385.33 T (union SETATTR3res switch \050nfsstat3 status\051 {) 90 361.33 T (case NFS3_OK:) 90 349.33 T (SETATTR3resok) 108 337.33 T (resok;) 216.72 337.33 T (default:) 90 325.33 T (SETATTR3resfail) 108 313.33 T (resfail;) 216.72 313.33 T (};) 90 301.33 T 8 F (DESCRIPTION) 72 279.33 T 0 F -0.33 (Procedure) 72 261.33 P 4 F -0.8 (SETATTR) 114.68 261.33 P 0 F -0.33 ( changes one or more of the attributes of a file system object on the server. The new attributes are) 156.66 261.33 P (specified by a) 72 249.33 T 5 F (sattr3) 130.01 249.33 T 0 F ( structure. On entry, the arguments in) 165.99 249.33 T 5 F (SETATTR3args) 317.83 249.33 T 0 F ( are) 389.79 249.33 T 5 F (:) 404.49 249.33 T (object) 90 233.33 T 0 F (The file handle for the object.) 216 233.33 T 5 F (new_attributes) 90 221.33 T 0 F 1.44 (A) 216 221.33 P 5 F 3.45 (sattr3) 227.15 221.33 P 0 F 1.44 ( structure containing booleans and enumerations describing the at-) 263.13 221.33 P (tributes to be set and the new values for those attributes.) 216 209.33 T 5 F (guard) 90 197.33 T 0 F (A) 216 197.33 T 5 F (sattrguard3) 225.71 197.33 T 0 F ( union:) 291.68 197.33 T 5 F (check) 108 185.33 T 4 F -0.51 (TRUE) 216 185.33 P 0 F -0.21 ( if the server is to verify that) 239.99 185.33 P 5 F -0.51 (guard.obj_ctime) 354.31 185.33 P 0 F -0.21 ( matches the) 444.26 185.33 P 5 F -0.51 (ctime) 496.08 185.33 P 0 F -0.21 ( for) 526.06 185.33 P (the object;) 216 173.33 T 4 F (FALSE) 260.42 173.33 T 0 F ( otherwise.) 290.4 173.33 T 0.01 (A client may request that the server check that the object is in an expected state before performing the) 72 155.33 P 4 F 0.03 (SETATTR) 482.19 155.33 P 0 F 0.01 ( op-) 524.17 155.33 P 3.36 (eration. To do this, it sets the argument) 72 143.33 P 5 F 8.06 (guard.check) 257.67 143.33 P 0 F 3.36 ( to) 323.63 143.33 P 4 F 8.06 (TRUE) 343.13 143.33 P 0 F 3.36 ( and the client passes a time value in) 367.11 143.33 P 5 F 1.27 (guard.obj_ctime) 72 131.33 P 0 F 0.53 (. If) 161.95 131.33 P 5 F 1.27 (guard.check) 177.16 131.33 P 0 F 0.53 ( is) 243.13 131.33 P 4 F 1.27 (TRUE) 255.85 131.33 P 0 F 0.53 (, the server must compare the value of) 279.84 131.33 P 5 F 1.27 (guard.obj_ctime) 439.24 131.33 P 0 F 0.53 ( to) 529.19 131.33 P 0.6 (the current) 72 119.33 P 5 F 1.44 (ctime) 118.72 119.33 P 0 F 0.6 ( of the object. If the values are different, the server must preserve the object attributes and must) 148.7 119.33 P (return a status of) 72 107.33 T 4 F (NFS3ERR_NOT_SYNC) 141.39 107.33 T 0 F (. If) 237.34 107.33 T 5 F (guard.check) 251.49 107.33 T 0 F ( is) 317.45 107.33 T 4 F (FALSE) 329.12 107.33 T 0 F (, the server will not perform this check.) 359.1 107.33 T (On successful return,) 72 89.33 T 5 F (SETATTR3res.status) 159.15 89.33 T 0 F ( is) 267.09 89.33 T 4 F (NFS3_OK) 278.76 89.33 T 0 F ( and) 320.73 89.33 T 5 F (SETATTR3res.resok) 340.16 89.33 T 0 F ( contains:) 442.11 89.33 T FMENDPAGE %%EndPage: "20" 25 %%Page: "21" 25 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (21) 300.44 35.33 T 4 F (SETATTR) 498.02 35.33 T 5 F (obj_wcc) 90 713.33 T 0 F (A) 216 713.33 T 5 F (wcc_data) 225.71 713.33 T 0 F ( structure containing the old and new attributes for the object.) 273.69 713.33 T 4 F -1.28 (Otherwise,) 72 695.33 P 5 F -1.28 ( SETATTR3res.status) 131.97 695.33 P 0 F -0.53 ( contains the error on failure and) 244.63 695.33 P 5 F -1.28 (SETATTR3res.resfail) 373.85 695.33 P 0 F -0.53 (contains the) 492.51 695.33 P (following:) 72 683.33 T 5 F (obj_wcc) 90 667.33 T 0 F (A) 216 667.33 T 5 F (wcc_data) 225.71 667.33 T 0 F ( structure containing the old and new attributes for the object.) 273.69 667.33 T 8 F (IMPLEMENTATION) 72 645.33 T 0 F 0.47 (The) 72 627.33 P 5 F 1.12 (guard.check) 90.51 627.33 P 0 F 0.47 ( mechanism allows the client to avoid changing the attributes of an object on the basis of stale) 156.47 627.33 P 0.2 (attributes. It does) 72 615.33 P 7 F 0.2 (not) 144.24 615.33 P 0 F 0.2 ( guarantee exactly-once semantics. In particular, if a reply is lost and the server does not detect) 157.57 615.33 P 0.41 (the retransmission of the request, the procedure can fail with the error,) 72 603.33 P 4 F 0.98 (NFS3ERR_NOT_SYNC) 360.54 603.33 P 0 F 0.41 (, even though the at-) 456.49 603.33 P -0.49 (tribute setting was previously performed successfully. The client can attempt to recover from this error by getting fresh) 72 591.33 P -0.34 (attributes from the server and sending a new) 72 579.33 P 4 F -0.82 (SETATTR) 249.12 579.33 P 0 F -0.34 ( request using the new) 291.1 579.33 P 5 F -0.82 (ctime) 381.27 579.33 P 0 F -0.34 (. The client can optionally check) 411.25 579.33 P -0.29 (the attributes to avoid the second) 72 567.33 P 4 F -0.71 (SETATTR) 204.59 567.33 P 0 F -0.29 ( request if the new attributes show that the attributes have already been set) 246.56 567.33 P (as desired \050though it may not have been the issuing client that set the attributes\051.) 72 555.33 T -0.22 (The) 72 537.33 P 5 F -0.51 (new_attributes.size) 89.83 537.33 P 0 F -0.22 ( field is used to request changes to the size of a file. A value of) 203.76 537.33 P 4 F -0.51 (0) 453.75 537.33 P 0 F -0.22 ( causes the file to be) 459.75 537.33 P -0.02 (truncated, a value less than the current size of the file causes data from new size to the end of the file to be discarded,) 72 525.33 P 0.06 (and a size greater than the current size of the file causes logically zeroed data bytes to be added to the end of the file.) 72 513.33 P 0.06 (Servers are free to implement this using holes or actual zero data bytes. Clients should not make any assumptions re-) 72 501.33 P -0.08 (garding a server\325s implementation of this feature, beyond that the bytes returned will be zeroed. Servers must support) 72 489.33 P (extending the file size via) 72 477.33 T 4 F (SETATTR) 177.2 477.33 T 0 F (.) 219.18 477.33 T 4 F (SETATTR) 72 459.33 T 0 F ( is not guaranteed atomic. A failed) 113.98 459.33 T 4 F (SETATTR) 254.43 459.33 T 0 F ( may partially change a file\325s attributes.) 296.41 459.33 T -0.59 (Changing the size of a file with) 72 441.33 P 4 F -1.41 (SETATTR) 195.87 441.33 P 0 F -0.59 ( indirectly changes the) 237.84 441.33 P 5 F -1.41 (mtime) 328.21 441.33 P 0 F -0.59 (. A client must account for this as size changes) 358.19 441.33 P (can result in data deletion.) 72 429.33 T -0.57 (If server and client times differ, programs that compare client time to file times can break. A time maintenance protocol) 72 411.33 P (should be used to limit client/server time skew.) 72 399.33 T 1.46 (In a heterogeneous environment, it is quite possible that the server will not be able to support the full range of) 72 381.33 P 4 F 0.17 (SETATTR) 72 369.33 P 0 F 0.07 ( requests. The error,) 113.98 369.33 P 4 F 0.17 (NFS3ERR_INVAL) 196.96 369.33 P 0 F 0.07 (, may be returned if the server can not store a uid or gid in its own) 274.92 369.33 P -0.27 (representation of uids or gids, respectively. If the server can only support) 72 357.33 P 4 F -0.64 (32) 363.56 357.33 P 0 F -0.27 ( bit offsets and sizes, a) 375.55 357.33 P 4 F -0.64 (SETATTR) 466.93 357.33 P 0 F -0.27 ( request) 508.9 357.33 P (to set the size of a file to larger than can be represented in) 72 345.33 T 4 F (32) 305.14 345.33 T 0 F ( bits will be rejected with this same error.) 317.14 345.33 T 8 F (ERRORS) 72 323.33 T 4 F (NFS3ERR_PERM) 90 307.33 T (NFS3ERR_IO) 90 295.33 T (NFS3ERR_ACCES) 90 283.33 T (NFS3ERR_INVAL) 90 271.33 T (NFS3ERR_NOSPC) 90 259.33 T (NFS3ERR_ROFS) 90 247.33 T (NFS3ERR_DQUOT) 90 235.33 T (NFS3ERR_NOT_SYNC) 90 223.33 T (NFS3ERR_STALE) 90 211.33 T (NFS3ERR_BADHANDLE) 90 199.33 T (NFS3ERR_SERVERFAULT) 90 187.33 T 8 F (SEE ALSO) 72 165.33 T 4 F (CREATE) 72 147.33 T 0 F ( on page 33) 107.98 147.33 T (,) 154.34 147.33 T 4 F (MKDIR) 159.33 147.33 T 0 F ( on page 36) 189.32 147.33 T (,) 235.67 147.33 T 4 F (SYMLINK) 240.67 147.33 T 0 F ( on page 38) 282.64 147.33 T (, and) 329 147.33 T 4 F (MKNOD) 350.93 147.33 T 0 F ( on page 40) 380.91 147.33 T (.) 427.27 147.33 T FMENDPAGE %%EndPage: "21" 26 %%Page: "22" 26 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (LOOKUP) 72 35.33 T 2 F (22) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (3) 152.84 710.67 T (LOOKUP) 276.4 710.67 T 2 10 Q (LOOKUP: Lookup filename) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (LOOKUP3res) 90 649.33 T (NFSPROC3_LOOKUP\050LOOKUP3args\051 = 3;) 90 637.33 T (struct LOOKUP3args {) 90 613.33 T (diropargs3) 108 601.33 T (what;) 180 601.33 T (};) 90 589.33 T (struct LOOKUP3resok {) 90 565.33 T (nfs_fh3) 108 553.33 T (object;) 198 553.33 T (post_op_attr) 108 541.33 T (obj_attributes;) 198 541.33 T (post_op_attr) 108 529.33 T (dir_attributes;) 198 529.33 T (};) 90 517.33 T (struct LOOKUP3resfail {) 90 493.33 T (post_op_attr) 108 481.33 T (dir_attributes;) 198 481.33 T (};) 90 469.33 T (union LOOKUP3res switch \050nfsstat3 status\051 {) 90 445.33 T (case NFS3_OK:) 90 433.33 T (LOOKUP3resok) 108 421.33 T (resok;) 198 421.33 T (default:) 90 409.33 T (LOOKUP3resfail) 108 397.33 T (resfail;) 198 397.33 T (};) 90 385.33 T 8 F (DESCRIPTION) 72 363.33 T 0 F -0.08 (Procedure) 72 345.33 P 4 F -0.2 (LOOKUP) 114.93 345.33 P 0 F -0.08 ( searches a directory for a specific name and returns the file handle for the corresponding file sys-) 150.91 345.33 P (tem object. On entry, the arguments in) 72 333.33 T 5 F (LOOKUP3args) 228.28 333.33 T 0 F ( are) 294.25 333.33 T 5 F (:) 308.95 333.33 T (what) 90 317.33 T 0 F (Object to look up.) 216 317.33 T 5 F (dir) 108 305.33 T 0 F (The file handle for the directory to search.) 216 305.33 T 5 F (name) 108 293.33 T 0 F -0.4 (The filename to be searched for. Refer to) 216 293.33 P 3 F -0.4 (General comments on filenames) 379.61 293.33 P 0 F -0.4 ( on page) 506.93 293.33 P (17.) 216 281.33 T (On successful return,) 72 263.33 T 5 F (LOOKUP3res.status) 159.15 263.33 T 0 F ( is) 261.1 263.33 T 4 F (NFS3_OK) 272.76 263.33 T 0 F ( and) 314.74 263.33 T 5 F (LOOKUP3res.resok) 334.17 263.33 T 0 F ( contains:) 430.11 263.33 T 5 F (object) 90 247.33 T 0 F (The file handle of the object corresponding to) 216 247.33 T 5 F (what.name) 401.42 247.33 T 0 F (.) 455.39 247.33 T 5 F (obj_attributes) 90 235.33 T 0 F (The attributes of the object corresponding to) 216 235.33 T 5 F (what.name) 396.15 235.33 T 0 F (.) 450.12 235.33 T 5 F (dir_attributes) 90 223.33 T 0 F (The post-operation attributes of the directory,) 216 223.33 T 5 F (what.dir) 400.59 223.33 T 0 F (.) 448.56 223.33 T -0.31 (Otherwise,) 72 205.33 P 5 F -0.73 (LOOKUP3res.status) 117.77 205.33 P 0 F -0.31 ( contains the error on failure and) 219.71 205.33 P 5 F -0.73 (LOOKUP3res.resfail) 350.53 205.33 P 0 F -0.31 ( contains the follow-) 458.47 205.33 P (ing:) 72 193.33 T 5 F (dir_attributes) 90 177.33 T 0 F (The post-operation attributes for the directory,) 216 177.33 T 5 F (what.dir) 403.92 177.33 T 0 F (.) 451.89 177.33 T 8 F (IMPLEMENTATION) 72 155.33 T 0 F -0.14 (At first glance, in the case where) 72 137.33 P 5 F -0.34 (what.name) 204.77 137.33 P 0 F -0.14 ( refers to a mount point on the server, two different replies seem possi-) 258.74 137.33 P -0.24 (ble. The server can return either the file handle for the underlying directory that is mounted on or the file handle of the) 72 125.33 P 0.22 (root of the mounted directory. This ambiguity is simply resolved. A server will only return the file handle for an ex-) 72 113.33 P -0.38 (ported local file system object. If a remote file system is mounted over a directory, the server will return the file handle) 72 101.33 P -0.57 (for the underlying local directory. If a local file system is mounted over a directory, the server will return the file handle) 72 89.33 P -0.05 (for the local file system covering the directory, if it is exported. Otherwise, it will return the file handle for the under-) 72 77.33 P FMENDPAGE %%EndPage: "22" 27 %%Page: "23" 27 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (23) 300.44 35.33 T 4 F (LOOKUP) 504.02 35.33 T 0 F -0.5 (lying directory. A given server implementation may refine these rules given capabilities or limitations particular to that) 72 713.33 P (implementation. Refer to) 72 701.33 T 3 F ([X/OpenNFS]) 174.71 701.33 T 0 F ( for a discussion on exporting file systems.) 230.79 701.33 T -0.25 (Two filenames are distinguished, as in the NFS version 2 protocol. The name, \322) 72 683.33 P 4 F -0.59 (.) 387.5 683.33 P 0 F -0.25 (\323, is an alias for the) 393.49 683.33 P 3 F -0.25 (current) 472.24 683.33 P 0 F -0.25 ( directory) 501.67 683.33 P 0.01 (and the name, \322) 72 671.33 P 4 F 0.03 (..) 134.76 671.33 P 0 F 0.01 (\323, is an alias for the) 146.75 671.33 P 3 F 0.01 (parent) 227.04 671.33 P 0 F 0.01 ( directory; that is, the directory that includes the specified directory as a) 253.13 671.33 P -0.03 (member. There is no facility for dealing with a multiparented directory and NFS assumes a hierarchical organization,) 72 659.33 P (organized as a single-rooted tree.) 72 647.33 T -0.42 (Note that this procedure does not follow symbolic links. The client is responsible for all parsing of filenames including) 72 629.33 P (filenames that are modified by symbolic links encountered during the lookup process.) 72 617.33 T 8 F (ERRORS) 72 595.33 T 4 F (NFS3ERR_IO) 90 579.33 T (NFS3ERR_NOENT) 90 567.33 T (NFS3ERR_ACCES) 90 555.33 T (NFS3ERR_NOTDIR) 90 543.33 T (NFS3ERR_NAMETOOLONG) 90 531.33 T (NFS3ERR_STALE) 90 519.33 T (NFS3ERR_BADHANDLE) 90 507.33 T (NFS3ERR_SERVERFAULT) 90 495.33 T 8 F (SEE ALSO) 72 473.33 T 4 F -0.85 (CREATE) 72 455.33 P 0 F -0.35 ( on page 33) 107.98 455.33 P -0.35 (,) 153.27 455.33 P 4 F -0.85 (MKDIR) 157.92 455.33 P 0 F -0.35 ( on page 36) 187.9 455.33 P -0.35 (,) 233.19 455.33 P 4 F -0.85 (SYMLINK) 237.84 455.33 P 0 F -0.35 ( on page 38) 279.81 455.33 P -0.35 (,) 325.11 455.33 P 4 F -0.85 (MKNOD) 329.75 455.33 P 0 F -0.35 ( on page 40) 359.73 455.33 P -0.35 (,) 405.02 455.33 P 4 F -0.85 (READDIRPLUS) 409.67 455.33 P 0 F -0.35 ( on page 54) 475.63 455.33 P -0.35 (, and) 520.92 455.33 P 4 F (PATHCONF) 72 443.33 T 0 F ( on page 62) 119.97 443.33 T (.) 166.33 443.33 T FMENDPAGE %%EndPage: "23" 28 %%Page: "24" 28 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (ACCESS) 72 35.33 T 2 F (24) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (4) 152.84 710.67 T (ACCESS) 279.12 710.67 T 2 10 Q (ACCESS: Check Access Permission) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (ACCESS3res) 90 649.33 T (NFSPROC3_ACCESS\050ACCESS3args\051 = 4;) 90 637.33 T (const ACCESS3_READ) 90 613.33 T (= 0x0001;) 216.72 613.33 T (const ACCESS3_LOOKUP) 90 601.33 T (= 0x0002;) 216.72 601.33 T (const ACCESS3_MODIFY) 90 589.33 T (= 0x0004;) 216.72 589.33 T (const ACCESS3_EXTEND) 90 577.33 T (= 0x0008;) 216.72 577.33 T (const ACCESS3_DELETE) 90 565.33 T (= 0x0010;) 216.72 565.33 T (const ACCESS3_EXECUTE) 90 553.33 T (= 0x0020;) 216.72 553.33 T (struct ACCESS3args {) 90 529.33 T (nfs_fh3) 108 517.33 T (object;) 162 517.33 T (uint32) 108 505.33 T (access;) 162 505.33 T (};) 90 493.33 T (struct ACCESS3resok {) 90 469.33 T (post_op_attr) 108 457.33 T (obj_attributes;) 198 457.33 T (uint32) 108 445.33 T (access;) 198 445.33 T (};) 90 433.33 T (struct ACCESS3resfail {) 90 409.33 T (post_op_attr) 108 397.33 T (obj_attributes;) 198 397.33 T (};) 90 385.33 T (union ACCESS3res switch \050nfsstat3 status\051 {) 90 361.33 T (case NFS3_OK:) 90 349.33 T (ACCESS3resok) 108 337.33 T (resok;) 198 337.33 T (default:) 90 325.33 T (ACCESS3resfail) 108 313.33 T (resfail;) 198 313.33 T (};) 90 301.33 T 8 F (DESCRIPTION) 72 279.33 T 0 F 0.5 (Procedure) 72 261.33 P 4 F 1.2 (ACCESS) 115.52 261.33 P 0 F 0.5 ( determines the access rights that a user, as identified by the credentials in the request, has with) 151.5 261.33 P -0.47 (respect to a file system object. The client encodes the set of permissions that are to be checked in a bit mask. The server) 72 249.33 P -0.2 (checks the permissions encoded in the bit mask. A status of) 72 237.33 P 4 F -0.48 (NFS3_OK) 310.21 237.33 P 0 F -0.2 ( is returned along with a bit mask encoded with) 352.19 237.33 P (the permissions that the client is allowed.) 72 225.33 T -0.59 (The results of this procedure are necessarily advisory in nature. That is, a return status of) 72 207.33 P 4 F -1.41 (NFS3_OK) 420.12 207.33 P 0 F -0.59 ( and the appropriate) 462.1 207.33 P -0.04 (bit set in the bit mask does not imply that such access will be allowed to the file system object in the future, as access) 72 195.33 P (rights can be revoked by the server at any time.) 72 183.33 T (On entry, the arguments in) 72 163.33 T 5 F (ACCESS3args) 181.37 163.33 T 0 F ( are:) 247.33 163.33 T 5 F (object) 90 151.33 T 0 F (The file handle for the file system object to which access is to be checked.) 216 151.33 T 5 F (access) 90 139.33 T 0 F (A bit mask of access permissions to check.) 216 139.33 T (The following access permissions may be requested:) 72 119.33 T 4 F (ACCESS3_READ) 90 107.33 T 0 F (Read data from file or read a directory.) 216 107.33 T 4 F (ACCESS3_LOOKUP) 90 95.33 T 0 F (Look up a name in a directory \050no meaning for non-directory objects\051.) 216 95.33 T 4 F (ACCESS3_MODIFY) 90 83.33 T 0 F (Rewrite existing file data or modify existing directory entries.) 216 83.33 T FMENDPAGE %%EndPage: "24" 29 %%Page: "25" 29 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (25) 300.44 35.33 T 4 F (ACCESS) 504.02 35.33 T (ACCESS3_EXTEND) 90 713.33 T 0 F (Write new data or add directory entries.) 216 713.33 T 4 F (ACCESS3_DELETE) 90 701.33 T 0 F (Delete an existing directory entry.) 216 701.33 T 4 F (ACCESS3_EXECUTE) 90 689.33 T 0 F (Execute file \050no meaning for a directory\051.) 216 689.33 T 0.01 (On successful return,) 72 671.33 P 5 F 0.01 (ACCESS3res.status) 159.17 671.33 P 0 F 0.01 ( is) 261.11 671.33 P 4 F 0.01 (NFS3_OK) 272.79 671.33 P 0 F 0.01 (. The server should return a status of) 314.77 671.33 P 4 F 0.01 (NFS3_OK) 463.31 671.33 P 0 F 0.01 ( if no er-) 505.29 671.33 P -0.44 (rors occurred that prevented the server from making the required access checks. The results in) 72 659.33 P 5 F -1.04 (ACCESS3res.resok) 444.05 659.33 P 0 F (are:) 72 647.33 T 5 F (obj_attributes) 90 631.33 T 0 F (The post-operation attributes of) 216 631.33 T 5 F (object) 344.8 631.33 T 0 F (.) 380.78 631.33 T 5 F (access) 90 619.33 T 0 F 0.66 (A bit mask of access permissions indicating access rights for the authentication) 216 619.33 P (credentials provided with the request.) 216 607.33 T -0.55 (Otherwise,) 72 589.33 P 5 F -1.33 ( ACCESS3res.status) 115.58 589.33 P 0 F -0.55 ( contains the error on failure and) 222.19 589.33 P 5 F -1.33 (ACCESS3res.resfail) 351.27 589.33 P 0 F -0.55 ( contains the follow-) 459.21 589.33 P (ing:) 72 577.33 T 5 F (obj_attributes) 90 561.33 T 0 F (The attributes of) 216 561.33 T 5 F (object) 284.56 561.33 T 0 F (\321if access to attributes is permitted.) 320.54 561.33 T 8 F (IMPLEMENTATION) 72 539.33 T 0 F 0.16 (In general, it is not sufficient for the client to attempt to deduce access permissions by inspecting the) 72 521.33 P 5 F 0.38 (uid) 479.28 521.33 P 0 F 0.16 (,) 497.27 521.33 P 5 F 0.38 (gid) 502.42 521.33 P 0 F 0.16 (, and) 520.41 521.33 P 5 F -0.78 (mode) 72 509.33 P 0 F -0.33 ( fields in the file attributes, since the server may perform uid or gid mapping or enforce additional access control) 95.99 509.33 P -0.15 (restrictions. It is also possible that the NFS version 3 protocol server may not be in the same ID space as the NFS ver-) 72 497.33 P 0.1 (sion 3 protocol client. In these cases \050and perhaps others\051, the NFS version 3 protocol client can not reliably perform) 72 485.33 P (an access check with only current file attributes.) 72 473.33 T 0.05 (In the NFS version 2 protocol, the only reliable way to determine whether an operation was allowed was to try it and) 72 455.33 P -0.11 (see if it succeeded or failed. Using the) 72 443.33 P 4 F -0.27 (ACCESS) 226.25 443.33 P 0 F -0.11 ( procedure in the NFS version 3 protocol, the client can ask the server) 262.23 443.33 P -0.4 (to indicate whether or not one or more classes of operations are permitted. The) 72 431.33 P 4 F -0.97 (ACCESS) 383.61 431.33 P 0 F -0.4 ( operation is provided to allow) 419.59 431.33 P -0.2 (clients to check before doing a series of operations. This is useful in operating systems \050such as UNIX\051 where permis-) 72 419.33 P 0.54 (sion checking is done only when a file or directory is opened. This procedure is also invoked by NFS client access) 72 407.33 P 0.11 (procedure \050called possibly through) 72 395.33 P 3 F 0.11 (access\0502\051) 214 395.33 P 0 F 0.11 (\051. The intent is to make the behavior of opening a remote file more con-) 251.74 395.33 P (sistent with the behavior of opening a local file.) 72 383.33 T -0.44 (The information returned by the server in response to an) 72 365.33 P 4 F -1.06 (ACCESS) 295.17 365.33 P 0 F -0.44 ( call is not permanent. It was correct at the exact time) 331.15 365.33 P 0.22 (that the server performed the checks, but not necessarily afterwards. The server can revoke access permission at any) 72 353.33 P (time.) 72 341.33 T -0.03 (The NFS version 3 protocol client should use the effective credentials of the user to build the authentication informa-) 72 323.33 P -0.12 (tion in the) 72 311.33 P 4 F -0.28 (ACCESS) 114.68 311.33 P 0 F -0.12 ( request used to determine access rights. It is the effective user and group credentials that are used) 150.66 311.33 P 0.11 (in subsequent read and write operations. See the comments in) 72 299.33 P 3 F 0.11 (Permission issues) 322.06 299.33 P 0 F 0.11 ( on page 67 for more information on) 393.52 299.33 P (this topic.) 72 287.33 T -0.57 (Many implementations do not directly support the) 72 269.33 P 4 F -1.36 (ACCESS3_DELETE) 270.96 269.33 P 0 F -0.57 ( permission. Operating systems like UNIX will) 354.91 269.33 P 0.06 (ignore the) 72 257.33 P 4 F 0.13 (ACCESS3_DELETE) 114.86 257.33 P 0 F 0.06 ( bit if set on an access request on a non-directory object. In these systems, delete per-) 198.81 257.33 P 0.35 (mission on a file is determined by the access permissions on the directory in which the file resides, instead of being) 72 245.33 P 2.09 (determined by the permissions of the file itself. Thus, the bit mask returned for such a request will have the) 72 233.33 P 4 F (ACCESS3_DELETE) 72 221.33 T 0 F ( bit set to) 155.95 221.33 T 4 F (0) 195.38 221.33 T 0 F (, indicating that the client does not have this permission.) 201.38 221.33 T 8 F (ERRORS) 72 199.33 T 4 F (NFS3ERR_IO) 90 183.33 T (NFS3ERR_STALE) 90 171.33 T (NFS3ERR_BADHANDLE) 90 159.33 T (NFS3ERR_SERVERFAULT) 90 147.33 T 8 F (SEE ALSO) 72 125.33 T 4 F (GETATTR on page 19.) 72 107.33 T FMENDPAGE %%EndPage: "25" 30 %%Page: "26" 30 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (READLINK) 72 35.33 T 2 F (26) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (5) 152.84 710.67 T (READLINK) 269.02 710.67 T 2 10 Q (READLINK: Read from symbolic link) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (READLINK3res) 90 649.33 T (NFSPROC3_READLINK\050READLINK3args\051 = 5;) 90 637.33 T (struct READLINK3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (symlink;) 162 601.33 T (};) 90 589.33 T (struct READLINK3resok {) 90 565.33 T (post_op_attr) 108 553.33 T (symlink_attributes;) 198 553.33 T (nfspath3) 108 541.33 T (data;) 198 541.33 T (};) 90 529.33 T (struct READLINK3resfail {) 90 505.33 T (post_op_attr) 108 493.33 T (symlink_attributes;) 198 493.33 T (};) 90 481.33 T (union READLINK3res switch \050nfsstat3 status\051 {) 90 457.33 T (case NFS3_OK:) 90 445.33 T (READLINK3resok) 108 433.33 T (resok;) 216.72 433.33 T (default:) 90 421.33 T (READLINK3resfail) 108 409.33 T (resfail;) 216.72 409.33 T (};) 90 397.33 T 8 F (DESCRIPTION) 72 375.33 T 0 F -0.3 (Procedure) 72 357.33 P 4 F -0.73 (READLINK) 114.71 357.33 P 0 F -0.3 ( reads the data associated with a symbolic link. The data is an ASCII string that is opaque to the) 162.69 357.33 P 0.02 (server. That is, whether created by the NFS version 3 protocol software from a client or created locally on the server,) 72 345.33 P 2.16 (the data in a symbolic link is not interpreted when created, but is simply stored. On entry, the arguments in) 72 333.33 P 5 F (READLINK3args) 72 321.33 T 0 F ( are) 149.96 321.33 T 5 F (:) 164.66 321.33 T (symlink) 90 305.33 T 0 F (The file handle for a symbolic link \050file system object of type) 216 305.33 T 4 F (NF3LNK\051) 464.16 305.33 T 0 F (.) 506.14 305.33 T (On successful return,) 72 287.33 T 5 F ( READLINK3res.status) 156.65 287.33 T 0 F ( is) 276.59 287.33 T 4 F (NFS3_OK) 288.25 287.33 T 0 F ( and) 330.23 287.33 T 5 F (READLINK3res.resok) 349.66 287.33 T 0 F ( contains:) 457.6 287.33 T 5 F (data) 90 271.33 T 0 F (The data associated with the symbolic link.) 216 271.33 T 5 F (symlink_attributes) 90 259.33 T 0 F (The post-operation attributes for the symbolic link.) 216 259.33 T -0.46 (Otherwise) 72 241.33 P 4 F -1.11 (,) 113.08 241.33 P 5 F -1.11 (READLINK3res.status) 123.96 241.33 P 0 F -0.46 ( contains the error on failure and) 237.9 241.33 P 5 F -1.11 (READLINK3res.resfail) 367.61 241.33 P 0 F -0.46 (contains the) 492.44 241.33 P (following:) 72 229.33 T 5 F (symlink_attributes) 90 213.33 T 0 F (The post-operation attributes for the symbolic link.) 216 213.33 T 8 F (IMPLEMENTATION) 72 191.33 T 0 F -0.48 (A symbolic link is nominally a pointer to another file. The) 72 173.33 P 5 F -1.15 (data) 302.7 173.33 P 0 F -0.48 ( is not necessarily interpreted by the server, just stored) 326.69 173.33 P -0.09 (in the file. It is possible for a client implementation to store a path name that is not meaningful to the server operating) 72 161.33 P -0.33 (system in a symbolic link. A) 72 149.33 P 4 F -0.79 (READLINK) 186.92 149.33 P 0 F -0.33 ( operation returns the) 234.89 149.33 P 5 F -0.79 (data) 321.29 149.33 P 0 F -0.33 ( to the client for interpretation. If different imple-) 345.27 149.33 P -0.57 (mentations want to share access to symbolic links, then they must agree on the interpretation of the data in the symbolic) 72 137.33 P (link.) 72 125.33 T 2.58 (The) 72 107.33 P 4 F 6.19 (READLINK) 92.62 107.33 P 0 F 2.58 ( operation is only allowed on objects of type,) 140.59 107.33 P 4 F 6.19 (NF3LNK) 346.45 107.33 P 0 F 2.58 (. The server should return the error,) 382.43 107.33 P 4 F -0.88 (NFS3ERR_INVAL) 72 95.33 P 0 F -0.37 (, if the object is not of type,) 149.96 95.33 P 4 F -0.88 (NF3LNK) 259.72 95.33 P 0 F -0.37 (. \050Note: The X/Open XNFS Specification for the NFS version) 295.7 95.33 P (2 protocol defined the error status in this case as) 72 83.33 T 4 F (NFSERR_NXIO) 267.41 83.33 T 0 F (. This is inconsistent with existing server practice.\051) 333.38 83.33 T FMENDPAGE %%EndPage: "26" 31 %%Page: "27" 31 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (27) 300.44 35.33 T 4 F (READLINK) 492.03 35.33 T 8 F (ERRORS) 72 713.33 T 4 F (NFS3ERR_IO) 90 697.33 T (NFS3ERR_INVAL) 90 685.33 T (NFS3ERR_ACCES) 90 673.33 T (NFS3ERR_STALE) 90 661.33 T (NFS3ERR_BADHANDLE) 90 649.33 T (NFS3ERR_NOTSUPP) 90 637.33 T (NFS3ERR_SERVERFAULT) 90 625.33 T 8 F (SEE ALSO) 72 603.33 T 4 F (READLINK) 72 585.33 T 0 F ( on page 26) 119.97 585.33 T ( and) 166.33 585.33 T 4 F (SYMLINK) 185.76 585.33 T 0 F ( on page 38) 227.73 585.33 T (.) 274.09 585.33 T FMENDPAGE %%EndPage: "27" 32 %%Page: "28" 32 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (READ) 72 35.33 T 2 F (28) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (6) 152.84 710.67 T (READ) 286.9 710.67 T 2 10 Q (READ: Read From file) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (READ3res) 90 649.33 T (NFSPROC3_READ\050READ3args\051 = 6;) 90 637.33 T (struct READ3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (file;) 180 601.33 T (offset3) 108 589.33 T (offset;) 180 589.33 T (count3) 108 577.33 T (count;) 180 577.33 T (};) 90 565.33 T (struct READ3resok {) 90 541.33 T (post_op_attr) 108 529.33 T (file_attributes;) 198 529.33 T (count3) 108 517.33 T (count;) 198 517.33 T (bool) 108 505.33 T (eof;) 198 505.33 T (opaque) 108 493.33 T (data<>;) 198 493.33 T (};) 90 481.33 T (struct READ3resfail {) 90 457.33 T (post_op_attr) 108 445.33 T (file_attributes;) 198 445.33 T (};) 90 433.33 T (union READ3res switch \050nfsstat3 status\051 {) 90 409.33 T (case NFS3_OK:) 90 397.33 T (READ3resok) 108 385.33 T (resok;) 198 385.33 T (default:) 90 373.33 T (READ3resfail) 108 361.33 T (resfail;) 198 361.33 T (};) 90 349.33 T 8 F (DESCRIPTION) 72 327.33 T 0 F (Procedure) 72 309.33 T 4 F (READ) 115.02 309.33 T 0 F ( reads data from a file.) 139 309.33 T (On entry, the arguments in) 72 291.33 T 5 F (READ3args) 181.37 291.33 T 0 F ( are:) 235.34 291.33 T 5 F (file) 90 275.33 T 0 F 0.12 (The file handle of the file from which data is to be read. This must identify a file) 216 275.33 P (system object of type,) 216 263.33 T 4 F (NF3REG) 306.22 263.33 T 0 F (.) 342.2 263.33 T 5 F (offset) 90 251.33 T 0 F -0.19 (The position within the file at which the read is to begin. An) 216 251.33 P 5 F -0.46 (offset) 457.24 251.33 P 0 F -0.19 ( of) 493.22 251.33 P 4 F -0.46 (0) 506.16 251.33 P 0 F -0.19 ( means) 512.16 251.33 P -0.47 (to read data starting at the beginning of the file. If) 216 239.33 P 5 F -1.14 (offset) 412.3 239.33 P 0 F -0.47 ( is greater than or equal) 448.28 239.33 P 0.2 (to the size of the file, the status,) 216 227.33 P 4 F 0.47 (NFS3_OK) 346.93 227.33 P 0 F 0.2 (, is returned with) 388.91 227.33 P 5 F 0.47 (count) 459.93 227.33 P 0 F 0.2 ( set to) 489.91 227.33 P 4 F 0.47 (0) 516.88 227.33 P 0 F 0.2 ( and) 522.87 227.33 P 5 F (eof) 216 215.33 T 0 F ( set to) 233.99 215.33 T 4 F (TRUE) 260.37 215.33 T 0 F (, subject to access permissions checking.) 284.35 215.33 T 5 F (count) 90 203.33 T 0 F -0.32 (The number of bytes of data that are to be read. If) 216 203.33 P 5 F -0.77 (count) 413.38 203.33 P 0 F -0.32 ( is) 443.36 203.33 P 4 F -0.77 (0) 454.39 203.33 P 0 F -0.32 (, the) 460.38 203.33 P 4 F -0.77 (READ) 479.45 203.33 P 0 F -0.32 ( will suc-) 503.44 203.33 P 0.41 (ceed and return) 216 191.33 P 4 F 0.98 (0) 281.33 191.33 P 0 F 0.41 ( bytes of data, subject to access permissions checking.) 287.33 191.33 P 5 F 0.98 (count) 510.02 191.33 P 0 F 0.37 (must be less than or equal to the value of the) 216 179.33 P 5 F 0.9 (rtmax) 400.83 179.33 P 0 F 0.37 ( field in the) 430.81 179.33 P 4 F 0.9 (FSINFO) 480.61 179.33 P 0 F 0.37 ( reply) 516.59 179.33 P 0.17 (structure for the file system that contains) 216 167.33 P 5 F 0.41 (file) 382.9 167.33 P 0 F 0.17 (. If greater, the server may return) 406.89 167.33 P (only) 216 155.33 T 5 F (rtmax) 236.27 155.33 T 0 F ( bytes, resulting in a short read.) 266.25 155.33 T (On successful return,) 72 137.33 T 5 F (READ3res.status) 159.15 137.33 T 0 F ( is) 249.1 137.33 T 4 F (NFS3_OK) 260.77 137.33 T 0 F ( and) 302.74 137.33 T 5 F (READ3res.resok) 322.17 137.33 T 0 F ( contains:) 406.13 137.33 T 5 F (file_attributes) 90 121.33 T 0 F (The attributes of the file on completion of the read.) 216 121.33 T 5 F (count) 90 109.33 T 0 F (The number of bytes of data returned by the read.) 216 109.33 T 5 F (eof) 90 97.33 T 0 F -0.21 (If the read ended at the end-of-file \050formally, in a correctly formed) 216 97.33 P 4 F -0.51 (READ) 482.36 97.33 P 0 F -0.21 ( request,) 506.35 97.33 P -0 (if) 216 85.33 P 5 F -0.01 (READ3args.offset) 224.6 85.33 P 0 F -0 ( plus) 320.55 85.33 P 5 F -0.01 (READ3resok.count) 342.2 85.33 P 0 F -0 ( is equal to the size of the) 438.15 85.33 P FMENDPAGE %%EndPage: "28" 33 %%Page: "29" 33 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (29) 300.44 35.33 T 4 F (READ) 516.01 35.33 T 0 F 0.23 (file\051,) 216 713.33 P 5 F 0.55 (eof) 237.88 713.33 P 0 F 0.23 ( is returned as) 255.87 713.33 P 4 F 0.55 (TRUE) 315.08 713.33 P 0 F 0.23 (; otherwise it is) 339.06 713.33 P 4 F 0.55 (FALSE) 403.83 713.33 P 0 F 0.23 (. A successful) 433.82 713.33 P 4 F 0.55 (READ) 492.8 713.33 P 0 F 0.23 ( of an) 516.78 713.33 P (empty file will always return) 216 701.33 T 5 F (eof) 333.98 701.33 T 0 F ( as) 351.96 701.33 T 4 F (TRUE) 365.29 701.33 T 0 F (.) 389.27 701.33 T 5 F (data) 90 689.33 T 0 F (The counted data read from the file.) 216 689.33 T 4 F 0.14 (Otherwise,) 72 671.33 P 5 F 0.14 (READ3res.status) 138.11 671.33 P 0 F 0.06 ( contains the error on failure and) 228.06 671.33 P 5 F 0.14 (READ3res.resfail) 361.43 671.33 P 0 F 0.06 ( contains the follow-) 457.37 671.33 P (ing:) 72 659.33 T 5 F (file_attributes) 90 643.33 T 0 F (The post-operation attributes of the file.) 216 643.33 T 8 F (IMPLEMENTATION) 72 621.33 T 0 F -0.19 (The) 72 603.33 P 5 F -0.45 (nfsdata) 89.85 603.33 P 0 F -0.19 ( type used for the) 131.83 603.33 P 4 F -0.45 (READ) 202.79 603.33 P 0 F -0.19 ( and) 226.78 603.33 P 4 F -0.45 (WRITE) 245.84 603.33 P 0 F -0.19 ( operations in the NFS version 2 protocol defining the data portion) 275.82 603.33 P -0.09 (of a request or reply has been changed to a variable-length opaque byte array. The maximum size allowed by the pro-) 72 591.33 P 0.11 (tocol is now limited by what XDR and underlying transports will allow. There are no artificial limits imposed by the) 72 579.33 P (NFS version 3 protocol. Consult the) 72 567.33 T 4 F (FSINFO) 218.87 567.33 T 0 F ( procedure description for details.) 254.85 567.33 T -0.39 (It is possible for the server to return fewer than) 72 549.33 P 5 F -0.94 (count) 258.51 549.33 P 0 F -0.39 ( bytes of data. If the server returns less than the) 288.49 549.33 P 5 F -0.94 (count) 475.71 549.33 P 0 F -0.39 ( request-) 505.7 549.33 P 0.37 (ed and) 72 537.33 P 5 F 0.88 (eof) 101.6 537.33 P 0 F 0.37 ( set to) 119.59 537.33 P 4 F 0.88 (FALSE) 147.06 537.33 P 0 F 0.37 (, the client should issue another) 177.05 537.33 P 4 F 0.88 (READ) 307.78 537.33 P 0 F 0.37 ( to get the remaining data. A server may return less) 331.76 537.33 P -0.23 (data than requested under several circumstances. The file may have been truncated by another client or perhaps on the) 72 525.33 P -0.44 (server itself, changing the file size from what the requesting client believes to be the case. This would reduce the actual) 72 513.33 P 0.17 (amount of data available to the client. It is possible that the server may back off the transfer size and reduce the read) 72 501.33 P (request return. Server resource exhaustion may also occur necessitating a smaller read return.) 72 489.33 T 0.15 (Some NFS version 2 protocol client implementations chose to interpret a short read response as indicating) 72 471.33 P 4 F 0.36 (EOF) 501.32 471.33 P 0 F 0.15 (. The) 519.31 471.33 P (addition of the) 72 459.33 T 5 F (eof) 132.8 459.33 T 0 F ( flag in the NFS version 3 protocol provides a correct way of handling) 150.79 459.33 T 4 F (EOF) 433.92 459.33 T 0 F (.) 451.91 459.33 T 0.05 (Some NFS version 2 protocol server implementations incorrectly returned) 72 441.33 P 4 F 0.13 (NFSERR_ISDIR) 371.45 441.33 P 0 F 0.05 ( if the file system object) 443.41 441.33 P (type was not a regular file. The correct return value for the NFS version 3 protocol is) 72 429.33 T 4 F (NFS3ERR_INVAL) 413.96 429.33 T 0 F (.) 491.92 429.33 T 8 F (ERRORS) 72 407.33 T 4 F (NFS3ERR_IO) 90 391.33 T (NFS3ERR_NXIO) 90 379.33 T (NFS3ERR_ACCES) 90 367.33 T (NFS3ERR_INVAL) 90 355.33 T (NFS3ERR_STALE) 90 343.33 T (NFS3ERR_BADHANDLE) 90 331.33 T (NFS3ERR_SERVERFAULT) 90 319.33 T 8 F (SEE ALSO) 72 297.33 T 4 F (READLINK) 72 279.33 T 0 F ( on page 26) 119.97 279.33 T (.) 166.33 279.33 T FMENDPAGE %%EndPage: "29" 34 %%Page: "30" 34 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (WRITE) 72 35.33 T 2 F (30) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (7) 152.84 710.67 T (WRITE) 282.62 710.67 T 2 10 Q (WRITE: Write to file) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (WRITE3res) 90 649.33 T (NFSPROC3_WRITE\050WRITE3args\051 = 7;) 90 637.33 T (enum stable_how {) 90 613.33 T (UNSTABLE = 0,) 108 601.33 T (DATA_SYNC = 1,) 108 589.33 T (FILE_SYNC = 2) 108 577.33 T (};) 90 565.33 T (struct WRITE3args {) 90 541.33 T (nfs_fh3) 108 529.33 T (file;) 180 529.33 T (offset3) 108 517.33 T (offset;) 180 517.33 T (count3) 108 505.33 T (count;) 180 505.33 T (stable_how) 108 493.33 T (stable;) 180 493.33 T (opaque) 108 481.33 T (data<>;) 180 481.33 T (};) 90 469.33 T (struct WRITE3resok {) 90 445.33 T (wcc_data) 108 433.33 T (file_wcc;) 180 433.33 T (count3) 108 421.33 T (count;) 180 421.33 T (stable_how) 108 409.33 T (committed;) 180 409.33 T (writeverf3) 108 397.33 T (verf;) 180 397.33 T (};) 90 385.33 T (struct WRITE3resfail {) 90 361.33 T (wcc_data) 108 349.33 T (file_wcc;) 180 349.33 T (};) 90 337.33 T (union WRITE3res switch \050nfsstat3 status\051 {) 90 313.33 T (case NFS3_OK:) 90 301.33 T (WRITE3resok) 108 289.33 T (resok;) 198 289.33 T (default:) 90 277.33 T (WRITE3resfail) 108 265.33 T (resfail;) 198 265.33 T (};) 90 253.33 T 8 F (DESCRIPTION) 72 231.33 T 0 F (Procedure) 72 213.33 T 4 F (WRITE) 115.02 213.33 T 0 F ( writes data to a file. On entry, the arguments in) 145 213.33 T 5 F (WRITE3args) 338.47 213.33 T 0 F ( are:) 398.44 213.33 T 5 F (file) 90 197.33 T 0 F -0.05 (The file handle for the file to which data is to be written. This must identify a file) 216 197.33 P (system object of type,) 216 185.33 T 4 F (NF3REG) 306.22 185.33 T 0 F (.) 342.2 185.33 T 5 F (offset) 90 173.33 T 0 F -0.4 (The position within the file at which the write is to begin. An) 216 173.33 P 5 F -0.96 (offset) 457.87 173.33 P 0 F -0.4 ( of) 493.85 173.33 P 4 F -0.96 (0) 506.37 173.33 P 0 F -0.4 ( means) 512.36 173.33 P (to write data starting at the beginning of the file.) 216 161.33 T 5 F (count) 90 149.33 T 0 F -0.35 (The number of bytes of data to be written. If) 216 149.33 P 5 F -0.85 (count) 392.6 149.33 P 0 F -0.35 ( is) 422.59 149.33 P 4 F -0.85 (0) 433.54 149.33 P 0 F -0.35 (, the) 439.54 149.33 P 4 F -0.85 (WRITE) 458.54 149.33 P 0 F -0.35 ( will succeed) 488.53 149.33 P -0.05 (and return a) 216 137.33 P 5 F -0.11 (count) 266.1 137.33 P 0 F -0.05 ( of) 296.08 137.33 P 4 F -0.11 (0) 309.31 137.33 P 0 F -0.05 (, barring errors due to permissions checking. The size of) 315.31 137.33 P 5 F 0.38 (data) 216 125.33 P 0 F 0.16 ( must be less than or equal to the value of the) 239.99 125.33 P 5 F 0.38 (wtmax) 425.1 125.33 P 0 F 0.16 ( field in the) 455.08 125.33 P 4 F 0.38 (FSINFO) 504.02 125.33 P 0 F 0.43 (reply structure for the file system that contains) 216 113.33 P 5 F 1.02 (file) 408.16 113.33 P 0 F 0.43 (. If greater, the server may) 432.14 113.33 P (write only) 216 101.33 T 5 F (wtmax) 259.31 101.33 T 0 F ( bytes, resulting in a short write.) 289.29 101.33 T 5 F (stable) 90 89.33 T 0 F 0.11 (If) 216 89.33 P 5 F 0.26 (stable) 225.26 89.33 P 0 F 0.11 ( is) 261.24 89.33 P 4 F 0.26 (FILE_SYNC) 273.13 89.33 P 0 F 0.11 (, the server) 327.1 89.33 P 7 F 0.11 (must) 374.05 89.33 P 0 F 0.11 ( commit the data written plus all file) 394.05 89.33 P -0.37 (system metadata to stable storage before returning results. This corresponds to the) 216 77.33 P FMENDPAGE %%EndPage: "30" 35 %%Page: "31" 35 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (31) 300.44 35.33 T 4 F (WRITE) 510.02 35.33 T 0 F -0.07 (NFS version 2 protocol semantics. Any other behavior constitutes a protocol vio-) 216 713.33 P -0.28 (lation. If) 216 701.33 P 5 F -0.67 (stable) 252.36 701.33 P 0 F -0.28 ( is) 288.34 701.33 P 4 F -0.67 (DATA_SYNC) 299.45 701.33 P 0 F -0.28 (,) 353.42 701.33 P -0.28 (then the server must commit all of the data to) 361.24 701.33 P 0.79 (stable storage and enough of the metadata to retrieve the data before returning.) 216 689.33 P -0.17 (The server implementor is free to implement) 216 677.33 P 4 F -0.4 (DATA_SYNC) 396.09 677.33 P 0 F -0.17 ( in the same fashion as) 450.06 677.33 P 4 F 0.89 (FILE_SYNC) 216 665.33 P 0 F 0.37 (, but with a possible performance drop. If) 269.97 665.33 P 5 F 0.89 (stable) 441.14 665.33 P 0 F 0.37 ( is) 477.12 665.33 P 4 F 0.89 (UNSTABLE) 489.53 665.33 P 0 F 0.37 (,) 537.5 665.33 P -0.34 (the server is free to commit any part of the data and the metadata to stable storage,) 216 653.33 P 0.03 (including all or none, before returning a reply to the client. There is no guarantee) 216 641.33 P -0.05 (whether or when any uncommitted data will subsequently be committed to stable) 216 629.33 P 0.6 (storage. The only guarantees made by the server are that it will not destroy any) 216 617.33 P -0.04 (data without changing the value of) 216 605.33 P 5 F -0.1 (verf) 356.76 605.33 P 0 F -0.04 ( and that it will not commit the data and) 380.75 605.33 P 0.8 (metadata at a level less than that requested by the client. See the discussion on) 216 593.33 P 4 F -1.31 (COMMIT) 216 581.33 P 0 F -0.55 ( on page 64) 251.98 581.33 P -0.55 ( for more information on if and when data is committed to sta-) 296.7 581.33 P (ble storage.) 216 569.33 T 5 F (data) 90 557.33 T 0 F (The data to be written to the file.) 216 557.33 T (On successful return,) 72 539.33 T 5 F (WRITE3res.status) 162.65 539.33 T 0 F ( is) 258.6 539.33 T 4 F (NFS3_OK) 270.26 539.33 T 0 F ( and) 312.24 539.33 T 5 F (WRITE3res.resok) 331.67 539.33 T 0 F ( contains:) 421.62 539.33 T 5 F (file_wcc) 90 523.33 T 0 F 0.17 (Weak cache consistency data for the file. For a client that requires only the post-) 216 523.33 P (write file attributes, these can be found in) 216 511.33 T 5 F (file_wcc.after) 384.49 511.33 T 0 F (.) 468.44 511.33 T 5 F (count) 90 499.33 T 0 F 0.03 (The number of bytes of data written to the file. The server may write fewer bytes) 216 499.33 P 1.81 (than requested. If so, the actual number of bytes written starting at location,) 216 487.33 P 5 F (offset) 216 475.33 T 0 F (, is returned.) 251.98 475.33 T 5 F (committed) 90 463.33 T 0 F -0.09 (The server should return an indication of the level of commitment of the data and) 216 463.33 P -0.42 (metadata via) 216 451.33 P 5 F -1.01 (committed) 268.45 451.33 P 0 F -0.42 (. If the server committed all data and metadata to stable) 322.42 451.33 P 0.23 (storage,) 216 439.33 P 5 F 0.56 (committed) 250.1 439.33 P 0 F 0.23 ( should be set to) 304.07 439.33 P 4 F 0.56 (FILE_SYNC) 372.7 439.33 P 0 F 0.23 (. If the level of commitment) 426.68 439.33 P 2.39 (was at least as strong as) 216 427.33 P 4 F 5.74 (DATA_SYNC) 328.05 427.33 P 0 F 2.39 (, then) 382.02 427.33 P 5 F 5.74 (committed) 411.5 427.33 P 0 F 2.39 ( should be set to) 465.48 427.33 P 4 F 6.71 (DATA_SYNC) 216 415.33 P 0 F 2.8 (. Otherwise,) 269.97 415.33 P 5 F 6.71 (committed) 326.63 415.33 P 0 F 2.8 ( must be returned as) 380.6 415.33 P 4 F 6.71 (UNSTABLE) 477.58 415.33 P 0 F 2.8 (. If) 525.55 415.33 P 5 F 0.76 (stable) 216 403.33 P 0 F 0.32 ( was) 251.98 403.33 P 4 F 0.76 (FILE_SYNC) 273.15 403.33 P 0 F 0.32 (, then) 327.12 403.33 P 5 F 0.76 (committed) 352.46 403.33 P 0 F 0.32 ( must also be) 406.43 403.33 P 4 F 0.76 (FILE_SYNC) 462.67 403.33 P 0 F 0.32 (: any-) 516.65 403.33 P 1.25 (thing else constitutes a protocol violation. If) 216 391.33 P 5 F 3.01 (stable) 403.55 391.33 P 0 F 1.25 ( was) 439.53 391.33 P 4 F 3.01 (DATA_SYNC) 462.57 391.33 P 0 F 1.25 (, then) 516.54 391.33 P 5 F 1.1 (committed) 216 379.33 P 0 F 0.46 ( may be) 269.97 379.33 P 4 F 1.1 (FILE_SYNC) 305.49 379.33 P 0 F 0.46 ( or) 359.46 379.33 P 4 F 1.1 (DATA_SYNC) 373.7 379.33 P 0 F 0.46 (: anything else constitutes a) 427.67 379.33 P -0.16 (protocol violation. If) 216 367.33 P 5 F -0.38 (stable) 301.03 367.33 P 0 F -0.16 ( was) 337.01 367.33 P 4 F -0.38 (UNSTABLE) 357.24 367.33 P 0 F -0.16 (, then) 405.21 367.33 P 5 F -0.38 (committed) 429.6 367.33 P 0 F -0.16 ( may be either) 483.57 367.33 P 4 F (FILE_SYNC) 216 355.33 T 0 F (,) 269.97 355.33 T 4 F (DATA_SYNC) 274.97 355.33 T 0 F (, or) 328.94 355.33 T 4 F (UNSTABLE) 344.76 355.33 T 0 F (.) 392.73 355.33 T 5 F (verf) 90 343.33 T 0 F -0.59 (This is a cookie that the client can use to determine whether the server has changed) 216 343.33 P -0.31 (state between a call to) 216 331.33 P 4 F -0.73 (WRITE) 305.23 331.33 P 0 F -0.31 ( and a subsequent call to either) 335.22 331.33 P 4 F -0.73 (WRITE) 458.83 331.33 P 0 F -0.31 ( or) 488.81 331.33 P 4 F -0.73 (COMMIT) 501.52 331.33 P 0 F -0.31 (.) 537.5 331.33 P -0.1 (This cookie must be consistent during a single instance of the NFS version 3 pro-) 216 319.33 P -0.29 (tocol service and must be unique between instances of the NFS version 3 protocol) 216 307.33 P (server, where uncommitted data may be lost.) 216 295.33 T -0.57 (Otherwise,) 72 277.33 P 5 F -1.37 (WRITE3res.status) 120.2 277.33 P 0 F -0.57 ( contains the error on failure and) 216.15 277.33 P 5 F -1.37 (WRITE3res.resfail) 345.1 277.33 P 0 F -0.57 ( contains the following:) 447.04 277.33 P 5 F (file_wcc) 90 261.33 T 0 F 0.17 (Weak cache consistency data for the file. For a client that requires only the post-) 216 261.33 P 0.09 (write file attributes, these can be found in) 216 249.33 P 5 F 0.23 (file_wcc.after) 385.25 249.33 P 0 F 0.09 (. Even though the) 469.2 249.33 P 0.17 (write failed, full) 216 237.33 P 5 F 0.41 (wcc_data) 283.69 237.33 P 0 F 0.17 ( is returned to allow the client to determine whether) 331.66 237.33 P (the failed write resulted in any change to the file.) 216 225.33 T -0.04 (If a client writes data to the server with the) 72 207.33 P 5 F -0.09 (stable) 245.36 207.33 P 0 F -0.04 ( argument set to) 281.34 207.33 P 4 F -0.09 (UNSTABLE) 347.8 207.33 P 0 F -0.04 ( and the reply yields a) 395.78 207.33 P 5 F -0.09 (committed) 486.03 207.33 P 0 F 0.12 (response of) 72 195.33 P 4 F 0.3 (DATA_SYNC) 120.54 195.33 P 0 F 0.12 ( or) 174.51 195.33 P 4 F 0.3 (UNSTABLE) 188.08 195.33 P 0 F 0.12 (, the client will follow up some time in the future with a) 236.06 195.33 P 4 F 0.3 (COMMIT) 463.65 195.33 P 0 F 0.12 ( operation) 499.63 195.33 P 0.07 (to synchronize outstanding asynchronous data and metadata with the server\325s stable storage, barring client error. It is) 72 183.33 P (possible that due to client crash or other error that a subsequent) 72 171.33 T 4 F (COMMIT) 327.37 171.33 T 0 F ( will not be received by the server.) 363.35 171.33 T 8 F (IMPLEMENTATION) 72 149.33 T 0 F -0.19 (The) 72 131.33 P 5 F -0.45 (nfsdata) 89.85 131.33 P 0 F -0.19 ( type used for the) 131.83 131.33 P 4 F -0.45 (READ) 202.79 131.33 P 0 F -0.19 ( and) 226.78 131.33 P 4 F -0.45 (WRITE) 245.84 131.33 P 0 F -0.19 ( operations in the NFS version 2 protocol defining the data portion) 275.82 131.33 P -0.09 (of a request or reply has been changed to a variable-length opaque byte array. The maximum size allowed by the pro-) 72 119.33 P 0.11 (tocol is now limited by what XDR and underlying transports will allow. There are no artificial limits imposed by the) 72 107.33 P (NFS version 3 protocol. Consult the) 72 95.33 T 4 F (FSINFO) 218.87 95.33 T 0 F ( procedure description for details.) 254.85 95.33 T -0.06 (It is possible for the server to write fewer than) 72 77.33 P 5 F -0.14 (count) 258.48 77.33 P 0 F -0.06 ( bytes of data. In this case, the server should not return an error) 288.47 77.33 P FMENDPAGE %%EndPage: "31" 36 %%Page: "32" 36 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (WRITE) 72 35.33 T 2 F (32) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F -0.09 (unless no data was written at all. If the server writes less than) 72 713.33 P 5 F -0.22 (count) 318.38 713.33 P 0 F -0.09 ( bytes, the client should issue another) 348.36 713.33 P 4 F -0.22 (WRITE) 499.83 713.33 P 0 F -0.09 ( to) 529.82 713.33 P (write the remaining data.) 72 701.33 T -0.16 (It is assumed that the act of writing data to a file will cause the) 72 683.33 P 5 F -0.39 (mtime) 322.45 683.33 P 0 F -0.16 ( of the file to be updated. However, the) 352.43 683.33 P 5 F -0.39 (mtime) 510.02 683.33 P 0 F 0.12 (of the file should not be changed unless the contents of the file are changed. Thus, a) 72 671.33 P 4 F 0.28 (WRITE) 411.83 671.33 P 0 F 0.12 ( request with) 441.81 671.33 P 5 F 0.28 (count) 496.3 671.33 P 0 F 0.12 ( set) 526.28 671.33 P (to) 72 659.33 T 4 F (0) 82.27 659.33 T 0 F ( should not cause the) 88.27 659.33 T 5 F (mtime) 174.6 659.33 T 0 F ( of the file to be updated.) 204.59 659.33 T 0.61 (The NFS version 3 protocol introduces) 72 641.33 P 3 F 0.61 (safe asynchronous writes) 233.9 641.33 P 0 F 0.61 (. The combination of) 336.17 641.33 P 4 F 1.47 (WRITE) 424.95 641.33 P 0 F 0.61 ( with) 454.93 641.33 P 5 F 1.47 (stable) 478.92 641.33 P 0 F 0.61 ( set to) 514.9 641.33 P 4 F 1.11 (UNSTABLE) 72 629.33 P 0 F 0.46 ( followed by a) 119.97 629.33 P 4 F 1.11 (COMMIT) 181.77 629.33 P 0 F 0.46 ( addresses the performance bottleneck found in the NFS version 2 protocol, the) 217.75 629.33 P (need to synchronously commit all writes to stable storage.) 72 617.33 T -0.36 (The definition of stable storage has been historically a point of contention. The following expected properties of stable) 72 599.33 P (storage may help in resolving design issues in the implementation. Stable storage is persistent storage that survives:) 72 587.33 T 1 F (1.) 90 571.33 T 0 F (Repeated power failures.) 108 571.33 T 1 F (2.) 90 557.33 T 0 F (Hardware failures \050of any board, power supply, and so on) 108 557.33 T 3 F (.) 338.64 557.33 T 0 F (\051.) 341.14 557.33 T 1 F (3.) 90 543.33 T 0 F (Repeated software crashes, including reboot cycle.) 108 543.33 T (This definition does not address failure of the stable storage module itself.) 72 525.33 T 0.66 (A cookie,) 72 507.33 P 5 F 1.59 (verf) 114.68 507.33 P 0 F 0.66 (, is defined to allow a client to detect different instances of an NFS version 3 protocol server over) 138.67 507.33 P 0.2 (which cached, uncommitted data may be lost. In the most likely case, the) 72 495.33 P 5 F 0.49 (verf) 369.43 495.33 P 0 F 0.2 ( allows the client to detect server re-) 393.42 495.33 P 0.32 (boots. This information is required so that the client can safely determine whether the server could have lost cached) 72 483.33 P 0.23 (data. If the server fails unexpectedly and the client has uncommitted data from previous) 72 471.33 P 4 F 0.55 (WRITE) 428.55 471.33 P 0 F 0.23 ( requests \050done with) 458.54 471.33 P 0.22 (the) 72 459.33 P 5 F 0.52 (stable) 86.93 459.33 P 0 F 0.22 ( argument set to) 122.91 459.33 P 4 F 0.52 (UNSTABLE) 190.4 459.33 P 0 F 0.22 ( and in which the result) 238.38 459.33 P 5 F 0.52 (committed) 335.73 459.33 P 0 F 0.22 ( was returned as) 389.7 459.33 P 4 F 0.52 (UNSTABLE) 457.73 459.33 P 0 F 0.22 ( as well\051) 505.7 459.33 P 0.06 (it may not have flushed cached data to stable storage. The burden of recovery is on the client and the client will need) 72 447.33 P (to retransmit the data to the server.) 72 435.33 T 0.22 (A suggested) 72 417.33 P 5 F 0.53 (verf) 124.08 417.33 P 0 F 0.22 ( cookie would be to use the time that the server was booted or the time the server was last started) 148.06 417.33 P (\050if restarting the server without a reboot results in lost buffers\051.) 72 405.33 T 0.69 (The) 72 387.33 P 5 F 1.67 (committed) 90.74 387.33 P 0 F 0.69 ( field in the results allows the client to do more effective caching. If the server is committing all) 144.71 387.33 P 4 F -0.39 (WRITE) 72 375.33 P 0 F -0.16 ( requests to stable storage, then it should return with) 101.98 375.33 P 5 F -0.39 (committed) 311.62 375.33 P 0 F -0.16 ( set to) 365.59 375.33 P 4 F -0.39 (FILE_SYNC) 391.48 375.33 P 0 F -0.16 (, regardless of the value) 445.45 375.33 P -0.54 (of the) 72 363.33 P 5 F -1.28 (stable) 96.47 363.33 P 0 F -0.54 ( field in the arguments. A server that uses an NVRAM accelerator may choose to implement this policy.) 132.45 363.33 P -0.14 (The client can use this to increase the effectiveness of the cache by discarding cached data that has already been com-) 72 351.33 P (mitted on the server.) 72 339.33 T -0.46 (Some implementations may return) 72 321.33 P 4 F -1.11 (NFS3ERR_NOSPC) 210.62 321.33 P 0 F -0.46 ( instead of) 288.58 321.33 P 4 F -1.11 (NFS3ERR_DQUOT) 331.32 321.33 P 0 F -0.46 ( when a user\325s quota is exceeded.) 409.28 321.33 P 0.05 (Some NFS version 2 protocol server implementations incorrectly returned) 72 303.33 P 4 F 0.13 (NFSERR_ISDIR) 371.45 303.33 P 0 F 0.05 ( if the file system object) 443.41 303.33 P (type was not a regular file. The correct return value for the NFS version 3 protocol is) 72 291.33 T 4 F (NFS3ERR_INVAL) 413.96 291.33 T 0 F (.) 491.92 291.33 T 8 F (ERRORS) 72 269.33 T 4 F (NFS3ERR_IO) 90 253.33 T (NFS3ERR_ACCES) 90 241.33 T (NFS3ERR_FBIG) 90 229.33 T (NFS3ERR_DQUOT) 90 217.33 T (NFS3ERR_NOSPC) 90 205.33 T (NFS3ERR_ROFS) 90 193.33 T (NFS3ERR_INVAL) 90 181.33 T (NFS3ERR_STALE) 90 169.33 T (NFS3ERR_BADHANDLE) 90 157.33 T (NFS3ERR_SERVERFAULT) 90 145.33 T 8 F (SEE ALSO) 72 123.33 T 4 F (COMMIT) 72 105.33 T 0 F ( on page 64) 107.98 105.33 T (.) 154.34 105.33 T FMENDPAGE %%EndPage: "32" 37 %%Page: "33" 37 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (33) 300.44 35.33 T 4 F (CREATE) 504.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (8) 152.84 710.67 T (CREATE) 277.57 710.67 T 2 10 Q (CREATE: Create a file) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (CREATE3res) 90 649.33 T (NFSPROC3_CREATE\050CREATE3args\051 = 8;) 90 637.33 T (enum createmode3 {) 90 613.33 T (UNCHECKED = 0,) 108 601.33 T (GUARDED = 1,) 108 589.33 T (EXCLUSIVE = 2) 108 577.33 T (};) 90 565.33 T (union createhow3 switch \050createmode3 mode\051 {) 90 541.33 T (case UNCHECKED:) 90 529.33 T (case GUARDED:) 90 517.33 T (sattr3) 108 505.33 T (obj_attributes;) 198 505.33 T (case EXCLUSIVE:) 90 493.33 T (createverf3) 108 481.33 T (verf;) 198 481.33 T (};) 90 469.33 T (struct CREATE3args {) 90 445.33 T (diropargs3) 108 433.33 T (where;) 180 433.33 T (createhow3) 108 421.33 T (how;) 180 421.33 T (};) 90 409.33 T (struct CREATE3resok {) 90 385.33 T (post_op_fh3) 108 373.33 T (obj;) 198 373.33 T (post_op_attr) 108 361.33 T (obj_attributes;) 198 361.33 T (wcc_data) 108 349.33 T (dir_wcc;) 198 349.33 T (};) 90 337.33 T (struct CREATE3resfail {) 90 313.33 T (wcc_data) 108 301.33 T (dir_wcc;) 180 301.33 T (};) 90 289.33 T (union CREATE3res switch \050nfsstat3 status\051 {) 90 265.33 T (case NFS3_OK:) 90 253.33 T (CREATE3resok) 108 241.33 T (resok;) 198 241.33 T (default:) 90 229.33 T (CREATE3resfail) 108 217.33 T (resfail;) 198 217.33 T (};) 90 205.33 T 8 F (DESCRIPTION) 72 183.33 T 0 F (Procedure) 72 165.33 T 4 F (CREATE) 115.02 165.33 T 0 F ( creates a regular file. On entry, the arguments in) 151 165.33 T 5 F (CREATE3args) 349.17 165.33 T 0 F ( are:) 415.13 165.33 T 5 F (where) 90 149.33 T 0 F (The location of the file to be created:) 216 149.33 T 5 F (dir) 108 137.33 T 0 F (The file handle for the directory in which the file is to be created.) 216 137.33 T 5 F (name) 108 125.33 T 0 F -0.39 (The name that is to be associated with the created file. Refer to) 216 125.33 P 3 F -0.39 (General comments) 465.17 125.33 P (on filenames) 216 113.33 T 0 F ( on page 17.) 266.8 113.33 T (When creating a regular file, there are three ways to create the file as defined by:) 72 95.33 T 5 F (how) 90 79.33 T 0 F 1.28 (A discriminated union describing how the server is to handle the file creation) 216 79.33 P FMENDPAGE %%EndPage: "33" 38 %%Page: "34" 38 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (CREATE) 72 35.33 T 2 F (34) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F (along with the appropriate attributes:) 216 713.33 T 5 F (mode) 108 701.33 T 0 F -0.22 (One of) 216 701.33 P 4 F -0.54 (UNCHECKED) 245.52 701.33 P 0 F -0.22 (,) 299.49 701.33 P 4 F -0.54 (GUARDED) 304.27 701.33 P 0 F -0.22 (, and) 346.24 701.33 P 4 F -0.54 (EXCLUSIVE) 367.72 701.33 P 0 F -0.22 (.) 421.69 701.33 P 4 F -0.54 (UNCHECKED) 426.47 701.33 P 0 F -0.22 ( means that the) 480.44 701.33 P 0.03 (file should be created without checking for the existence of a duplicate file in the) 216 689.33 P 0.36 (same directory. In this case,) 216 677.33 P 5 F 0.87 (how.obj_attributes) 331.89 677.33 P 0 F 0.36 ( is a) 439.83 677.33 P 5 F 0.87 (sattr3) 459.52 677.33 P 0 F 0.36 ( describing) 495.5 677.33 P 0.25 (the initial attributes for the file.) 216 665.33 P 4 F 0.61 (GUARDED) 344.95 665.33 P 0 F 0.25 ( specifies that the server should check) 386.92 665.33 P -0.41 (for the presence of a duplicate file before performing the create and should fail the) 216 653.33 P -0.27 (request with) 216 641.33 P 4 F -0.65 (NFS3ERR_EXIST) 267.09 641.33 P 0 F -0.27 ( if a duplicate file exists. If the file does not exist,) 345.05 641.33 P 0.94 (the request is performed as described for) 216 629.33 P 4 F 2.25 (UNCHECKED) 387.71 629.33 P 0 F 0.94 (.) 441.68 629.33 P 4 F 2.25 (EXCLUSIVE) 447.62 629.33 P 0 F 0.94 ( specifies) 501.59 629.33 P 0.28 (that the server is to follow exclusive creation semantics, using the verifier to en-) 216 617.33 P 0.43 (sure exclusive creation of the target. No attributes may be provided in this case,) 216 605.33 P -0.16 (since the server may use the target file metadata to store the) 216 593.33 P 5 F -0.38 (createverf3) 455.6 593.33 P 0 F -0.16 ( ver-) 521.57 593.33 P (ifier.) 216 581.33 T (On successful return,) 72 563.33 T 5 F (CREATE3res.status) 159.15 563.33 T 0 F ( is) 261.1 563.33 T 4 F (NFS3_OK) 272.76 563.33 T 0 F ( and the results in) 314.74 563.33 T 5 F (CREATE3res.resok) 387.75 563.33 T 0 F ( are:) 483.69 563.33 T 5 F (obj) 90 547.33 T 0 F (The file handle of the newly created regular file.) 216 547.33 T 5 F (obj_attributes) 90 535.33 T 0 F (The attributes of the regular file just created.) 216 535.33 T 5 F (dir_wcc) 90 523.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 523.33 P 5 F -0.17 (where.dir) 404.78 523.33 P 0 F -0.07 (. For a client that re-) 458.75 523.33 P 4.57 (quires on the post-) 216 511.33 P 4 F 10.97 (CREATE) 303.83 511.33 P 0 F 4.57 ( directory attributes, these can be found in) 339.81 511.33 P 5 F (dir_wcc.after) 216 499.33 T 0 F (.) 293.96 499.33 T -0.31 (Otherwise,) 72 481.33 P 5 F -0.73 (CREATE3res.status) 117.77 481.33 P 0 F -0.31 ( contains the error on failure and) 219.71 481.33 P 5 F -0.73 (CREATE3res.resfail) 350.53 481.33 P 0 F -0.31 ( contains the follow-) 458.47 481.33 P (ing:) 72 469.33 T 5 F (dir_wcc) 90 453.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 453.33 P 5 F -0.17 (where.dir) 404.78 453.33 P 0 F -0.07 (. For a client that re-) 458.75 453.33 P 3.79 (quires only the post-) 216 441.33 P 4 F 9.1 (CREATE) 309.27 441.33 P 0 F 3.79 ( directory attributes, these can be found in) 345.25 441.33 P 5 F -0.67 (dir_wcc.after) 216 429.33 P 0 F -0.28 (. Even though the) 293.96 429.33 P 4 F -0.67 (CREATE) 365.85 429.33 P 0 F -0.28 ( failed, full) 401.83 429.33 P 5 F -0.67 (wcc_data) 447.62 429.33 P 0 F -0.28 ( is returned) 495.6 429.33 P 1.79 (to allow the client to determine whether the failing) 216 417.33 P 4 F 4.31 (CREATE) 437.29 417.33 P 0 F 1.79 ( resulted in any) 473.27 417.33 P (change to the directory.) 216 405.33 T 8 F (IMPLEMENTATION) 72 383.33 T 0 F -0.29 (Unlike the NFS version 2 protocol, in which certain fields in the initial attributes structure were overloaded to indicate) 72 365.33 P -0.45 (creation of devices and FIFOs in addition to regular files, this procedure only supports the creation of regular files. The) 72 353.33 P 4 F (MKNOD) 72 341.33 T 0 F ( procedure was introduced in the NFS version 3 protocol to handle creation of devices and FIFOs. Implemen-) 101.98 341.33 T (tations should have no reason in the NFS version 3 protocol to overload) 72 329.33 T 4 F (CREATE) 361.54 329.33 T 0 F ( semantics.) 397.52 329.33 T -0.01 (One aspect of the NFS version 3 protocol) 72 311.33 P 4 F -0.02 (CREATE) 240.15 311.33 P 0 F -0.01 ( procedure warrants particularly careful consideration: the mecha-) 276.13 311.33 P 1.16 (nism introduced to support the reliable exclusive creation of regular files. The mechanism comes into play when) 72 299.33 P 5 F -1.02 (how.mode) 72 287.33 P 0 F -0.43 ( is) 119.97 287.33 P 4 F -1.02 (EXCLUSIVE) 130.79 287.33 P 0 F -0.43 (. In this case,) 184.76 287.33 P 5 F -1.02 (how.verf) 238.02 287.33 P 0 F -0.43 ( contains a verifier that can reasonably be expected to be unique.) 285.99 287.33 P -0.08 (A combination of a client identifier, perhaps the client network address, and a unique number generated by the client,) 72 275.33 P (perhaps the RPC transaction identifier, may be appropriate.) 72 263.33 T -0.11 (If the file does not exist, the server creates the file and stores the verifier in stable storage. For file systems that do not) 72 245.33 P 0.46 (provide a mechanism for the storage of arbitrary file attributes, the server may use one or more elements of the file) 72 233.33 P -0.05 (metadata to store the verifier. The verifier must be stored in stable storage to prevent erroneous failure on retransmis-) 72 221.33 P 0.11 (sion of the request. It is assumed that an exclusive create is being performed because exclusive semantics are critical) 72 209.33 P -0.24 (to the application. Because of the expected usage, exclusive) 72 197.33 P 4 F -0.58 (CREATE) 311.59 197.33 P 0 F -0.24 ( does not rely solely on the normally volatile du-) 347.57 197.33 P -0.38 (plicate request cache for storage of the verifier. The duplicate request cache in volatile storage does not survive a crash) 72 185.33 P 0.09 (and may actually flush on a long network partition, opening failure windows. In the UNIX local file system environ-) 72 173.33 P -0.46 (ment, the expected storage location for the verifier on creation is the metadata \050time stamps\051 of the file. For this reason,) 72 161.33 P (an exclusive file create may not include initial attributes because the server would have nowhere to store the verifier.) 72 149.33 T -0.08 (If the server can not support these exclusive create semantics, possibly because of the requirement to commit the ver-) 72 131.33 P (ifier to stable storage, it should fail the) 72 119.33 T 4 F (CREATE) 228.84 119.33 T 0 F ( request with the error,) 264.82 119.33 T 4 F (NFS3ERR_NOTSUPP) 358.08 119.33 T 0 F (.) 448.03 119.33 T -0.2 (During an exclusive) 72 101.33 P 4 F -0.49 (CREATE) 154.38 101.33 P 0 F -0.2 ( request, if the file already exists, the server reconstructs the file\325s verifier and compares) 190.36 101.33 P 0.17 (it with the verifier in the request. If they match, the server treats the request as a success. The request is presumed to) 72 89.33 P -0.07 (be a duplicate of an earlier, successful request for which the reply was lost and that the server duplicate request cache) 72 77.33 P FMENDPAGE %%EndPage: "34" 39 %%Page: "35" 39 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (35) 300.44 35.33 T 4 F (CREATE) 504.02 35.33 T 0 F (mechanism did not detect. If the verifiers do not match, the request is rejected with the status,) 72 713.33 T 4 F (NFS3ERR_EXIST) 448.4 713.33 T 0 F (.) 526.36 713.33 T -0.15 (Once the client has performed a successful exclusive create, it must issue a) 72 695.33 P 4 F -0.35 (SETATTR) 372.06 695.33 P 0 F -0.15 ( to set the correct file attributes.) 414.04 695.33 P -0.36 (Until it does so, it should not rely upon any of the file attributes, since the server implementation may need to overload) 72 683.33 P (file metadata to store the verifier.) 72 671.33 T 0.09 (Use of the) 72 653.33 P 4 F 0.2 (GUARDED) 115.83 653.33 P 0 F 0.09 ( attribute does) 157.81 653.33 P 7 F 0.09 (not) 217.19 653.33 P 0 F 0.09 (provide exactly-once semantics. In particular, if a reply is lost and the server) 233.11 653.33 P -0.22 (does not detect the retransmission of the request, the procedure can fail with) 72 641.33 P 4 F -0.54 (NFS3ERR_EXIST) 376.07 641.33 P 0 F -0.22 (, even though the cre-) 454.03 641.33 P (ate was performed successfully.) 72 629.33 T (Refer to) 72 611.33 T 3 F (General comments on filenames) 106.97 611.33 T 0 F ( on page 17.) 235.49 611.33 T 8 F (ERRORS) 72 589.33 T 4 F (NFS3ERR_IO) 90 573.33 T (NFS3ERR_ACCES) 90 561.33 T (NFS3ERR_EXIST) 90 549.33 T (NFS3ERR_NOTDIR) 90 537.33 T (NFS3ERR_NOSPC) 90 525.33 T (NFS3ERR_ROFS) 90 513.33 T (NFS3ERR_NAMETOOLONG) 90 501.33 T (NFS3ERR_DQUOT) 90 489.33 T (NFS3ERR_STALE) 90 477.33 T (NFS3ERR_BADHANDLE) 90 465.33 T (NFS3ERR_NOTSUPP) 90 453.33 T (NFS3ERR_SERVERFAULT) 90 441.33 T 8 F (SEE ALSO) 72 419.33 T 4 F (MKDIR) 72 401.33 T 0 F ( on page 36) 101.98 401.33 T (,) 148.34 401.33 T 4 F (SYMLINK) 153.34 401.33 T 0 F ( on page 38) 195.31 401.33 T (,) 241.67 401.33 T 4 F (MKNOD) 246.66 401.33 T 0 F ( on page 40) 276.65 401.33 T (, and) 323 401.33 T 4 F (PATHCONF) 344.93 401.33 T 0 F ( on page 62) 392.9 401.33 T (.) 439.26 401.33 T FMENDPAGE %%EndPage: "35" 40 %%Page: "36" 40 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (MKDIR) 72 35.33 T 2 F (36) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (9) 152.84 710.67 T (MKDIR) 281.85 710.67 T 2 10 Q (MKDIR: Create a directory) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (MKDIR3res) 90 649.33 T (NFSPROC3_MKDIR\050MKDIR3args\051 = 9;) 90 637.33 T (struct MKDIR3args {) 90 613.33 T (diropargs3) 108 601.33 T (where;) 180 601.33 T (sattr3) 108 589.33 T (attributes;) 180 589.33 T (};) 90 577.33 T (struct MKDIR3resok {) 90 553.33 T (post_op_fh3) 108 541.33 T (obj;) 198 541.33 T (post_op_attr) 108 529.33 T (obj_attributes;) 198 529.33 T (wcc_data) 108 517.33 T (dir_wcc;) 198 517.33 T (};) 90 505.33 T (struct MKDIR3resfail {) 90 481.33 T (wcc_data) 108 469.33 T (dir_wcc;) 180 469.33 T (};) 90 457.33 T (union MKDIR3res switch \050nfsstat3 status\051 {) 90 433.33 T (case NFS3_OK:) 90 421.33 T (MKDIR3resok) 108 409.33 T (resok;) 198 409.33 T (default:) 90 397.33 T (MKDIR3resfail) 108 385.33 T (resfail;) 198 385.33 T (};) 90 373.33 T 8 F (DESCRIPTION) 72 351.33 T 0 F (Procedure) 72 333.33 T 4 F (MKDIR) 115.02 333.33 T 0 F ( creates a new subdirectory. On entry, the arguments in) 145 333.33 T 5 F (MKDIR3args) 368.16 333.33 T 0 F ( are:) 428.12 333.33 T 5 F (where) 90 317.33 T 0 F (The location of the subdirectory to be created:) 216 317.33 T 5 F (dir) 108 305.33 T 0 F (The file handle for the directory in which the subdirectory is to be created.) 216 305.33 T 5 F (name) 108 293.33 T 0 F 0.03 (The name that is to be associated with the created subdirectory. Refer to) 216 293.33 P 3 F 0.03 (General) 507.25 293.33 P (comments on filenames) 216 281.33 T 0 F ( on page 17.) 309.27 281.33 T 5 F (attributes) 90 269.33 T 0 F (The initial attributes for the subdirectory.) 216 269.33 T (On successful return,) 72 251.33 T 5 F (MKDIR3res.status) 159.15 251.33 T 0 F ( is) 255.1 251.33 T 4 F (NFS3_OK) 266.76 251.33 T 0 F ( and the results in) 308.74 251.33 T 5 F (MKDIR3res.resok) 381.75 251.33 T 0 F ( are:) 471.7 251.33 T 5 F (obj) 90 235.33 T 0 F (The file handle for the newly created directory.) 216 235.33 T 5 F (obj_attributes) 90 223.33 T 0 F (The attributes for the newly created subdirectory.) 216 223.33 T 5 F (dir_wcc) 90 211.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 211.33 P 5 F -0.17 (where.dir) 404.78 211.33 P 0 F -0.07 (. For a client that re-) 458.75 211.33 P 4.39 (quires only the post-) 216 199.33 P 4 F 10.54 (MKDIR) 311.07 199.33 P 0 F 4.39 ( directory attributes, these can be found in) 341.05 199.33 P 5 F (dir_wcc.after) 216 187.33 T 0 F -0.33 (Otherwise,) 72 169.33 P 5 F -0.78 (MKDIR3res.status) 117.75 169.33 P 0 F -0.33 ( contains the error on failure and) 213.7 169.33 P 5 F -0.78 (MKDIR3res.resfail) 344.36 169.33 P 0 F -0.33 ( contains the following:) 446.31 169.33 P 5 F (dir_wcc) 90 153.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 153.33 P 5 F -0.17 (where.dir) 404.78 153.33 P 0 F -0.07 (. For a client that re-) 458.75 153.33 P 4.39 (quires only the post-) 216 141.33 P 4 F 10.54 (MKDIR) 311.07 141.33 P 0 F 4.39 ( directory attributes, these can be found in) 341.05 141.33 P 5 F 0.93 (dir_wcc.after) 216 129.33 P 0 F 0.39 (. Even though the) 293.96 129.33 P 4 F 0.93 (MKDIR) 368.51 129.33 P 0 F 0.39 ( failed, full) 398.49 129.33 P 5 F 0.93 (wcc_data) 446.29 129.33 P 0 F 0.39 ( is returned) 494.26 129.33 P -0.25 (to allow the client to determine whether the failing) 216 117.33 P 4 F -0.6 (MKDIR) 418.87 117.33 P 0 F -0.25 ( resulted in any change) 448.86 117.33 P (to the directory.) 216 105.33 T FMENDPAGE %%EndPage: "36" 41 %%Page: "37" 41 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (37) 300.44 35.33 T 4 F (MKDIR) 510.02 35.33 T 8 F (IMPLEMENTATION) 72 713.33 T 0 F 0.13 (Many server implementations will not allow the filenames, \322) 72 695.33 P 4 F 0.32 (.) 315.97 695.33 P 0 F 0.13 (\323 or \322) 321.96 695.33 P 4 F 0.32 (..) 344.43 695.33 P 0 F 0.13 (\323, to be used as targets in a) 356.42 695.33 P 4 F 0.32 (MKDIR) 467.14 695.33 P 0 F 0.13 ( operation.) 497.12 695.33 P (In this case, the server should return) 72 683.33 T 4 F (NFS3ERR_EXIST) 219.11 683.33 T 0 F (. Refer to) 297.07 683.33 T 3 F (General comments on filenames) 337.03 683.33 T 0 F ( on page 17.) 465.55 683.33 T 8 F (ERRORS) 72 661.33 T 4 F (NFS3ERR_IO) 90 645.33 T (NFS3ERR_ACCES) 90 633.33 T (NFS3ERR_EXIST) 90 621.33 T (NFS3ERR_NOTDIR) 90 609.33 T (NFS3ERR_NOSPC) 90 597.33 T (NFS3ERR_ROFS) 90 585.33 T (NFS3ERR_NAMETOOLONG) 90 573.33 T (NFS3ERR_DQUOT) 90 561.33 T (NFS3ERR_STALE) 90 549.33 T (NFS3ERR_BADHANDLE) 90 537.33 T (NFS3ERR_NOTSUPP) 90 525.33 T (NFS3ERR_SERVERFAULT) 90 513.33 T 8 F (SEE ALSO) 72 491.33 T 4 F (CREATE) 72 473.33 T 0 F ( on page 33) 107.98 473.33 T (,) 154.34 473.33 T 4 F (SYMLINK) 159.33 473.33 T 0 F ( on page 38) 201.31 473.33 T (,) 247.66 473.33 T 4 F (MKNOD) 252.66 473.33 T 0 F ( on page 40) 282.64 473.33 T (, and) 329 473.33 T 4 F (PATHCONF) 350.93 473.33 T 0 F ( on page 62) 398.9 473.33 T (.) 445.26 473.33 T FMENDPAGE %%EndPage: "37" 42 %%Page: "38" 42 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (SYMLINK) 72 35.33 T 2 F (38) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (10) 145.85 710.67 T (SYMLINK) 273.29 710.67 T 2 10 Q (SYMLINK: Create a symbolic link) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (SYMLINK3res) 90 649.33 T (NFSPROC3_SYMLINK\050SYMLINK3args\051 = 10;) 90 637.33 T (struct symlinkdata3 {) 90 613.33 T (sattr3) 108 601.33 T (symlink_attributes;) 162 601.33 T (nfspath3) 108 589.33 T (symlink_data;) 162 589.33 T (};) 90 577.33 T (struct SYMLINK3args {) 90 553.33 T (diropargs3) 108 541.33 T (where;) 198 541.33 T (symlinkdata3) 108 529.33 T (symlink;) 198 529.33 T (};) 90 517.33 T (struct SYMLINK3resok {) 90 493.33 T (post_op_fh3) 108 481.33 T (obj;) 198 481.33 T (post_op_attr) 108 469.33 T (obj_attributes;) 198 469.33 T (wcc_data) 108 457.33 T (dir_wcc;) 198 457.33 T (};) 90 445.33 T (struct SYMLINK3resfail {) 90 421.33 T (wcc_data) 108 409.33 T (dir_wcc;) 180 409.33 T (};) 90 397.33 T (union SYMLINK3res switch \050nfsstat3 status\051 {) 90 373.33 T (case NFS3_OK:) 90 361.33 T (SYMLINK3resok) 108 349.33 T (resok;) 216.72 349.33 T (default:) 90 337.33 T (SYMLINK3resfail) 108 325.33 T (resfail;) 216.72 325.33 T (};) 90 313.33 T 8 F (DESCRIPTION) 72 291.33 T 0 F (Procedure) 72 273.33 T 4 F (SYMLINK) 115.02 273.33 T 0 F ( creates a new symbolic link. On entry, the arguments in) 156.99 273.33 T 5 F (SYMLINK3args) 384.89 273.33 T 0 F ( are:) 456.85 273.33 T 5 F (where) 90 257.33 T 0 F (The location of the symbolic link to be created:) 216 257.33 T 5 F (dir) 108 245.33 T 0 F (The file handle for the directory in which the symbolic link is to be created.) 216 245.33 T 5 F (name) 108 233.33 T 0 F -0.31 (The name that is to be associated with the created symbolic link. Refer to) 216 233.33 P 3 F -0.31 (General) 507.25 233.33 P (comments on filenames) 216 221.33 T 0 F ( on page 17.) 309.27 221.33 T 5 F (symlink) 90 209.33 T 0 F (The symbolic link to create:) 216 209.33 T 5 F (symlink_attributes) 108 197.33 T 0 F (The initial attributes for the symbolic link.) 216 185.33 T 5 F (symlink_data) 108 173.33 T 0 F (The string containing the symbolic link data.) 216 173.33 T (On successful return,) 72 155.33 T 5 F (SYMLINK3res.status) 159.15 155.33 T 0 F ( is) 267.09 155.33 T 4 F (NFS3_OK) 278.76 155.33 T 0 F ( and) 320.73 155.33 T 5 F (SYMLINK3res.resok) 340.16 155.33 T 0 F ( contains:) 442.11 155.33 T 5 F (obj) 90 139.33 T 0 F (The file handle for the newly created symbolic link.) 216 139.33 T 5 F (obj_attributes) 90 127.33 T 0 F (The attributes for the newly created symbolic link.) 216 127.33 T 5 F (dir_wcc) 90 115.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 115.33 P 5 F -0.17 (where.dir) 404.78 115.33 P 0 F -0.07 (. For a client that re-) 458.75 115.33 P 3.19 (quires only the post-) 216 103.33 P 4 F 7.66 (SYMLINK) 307.47 103.33 P 0 F 3.19 ( directory attributes, these can be found in) 349.45 103.33 P 5 F (dir_wcc.after) 216 91.33 T 0 F (.) 293.96 91.33 T FMENDPAGE %%EndPage: "38" 43 %%Page: "39" 43 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (39) 300.44 35.33 T 4 F (SYMLINK) 498.02 35.33 T 0 F -0.03 (Otherwise,) 72 713.33 P 5 F -0.08 (SYMLINK3res.status) 118.04 713.33 P 0 F -0.03 ( contains the error on failure and) 225.98 713.33 P 5 F -0.08 (SYMLINK3res.resfail) 358.71 713.33 P 0 F -0.03 ( contains the fol-) 472.64 713.33 P (lowing:) 72 701.33 T 5 F (dir_wcc) 90 685.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 685.33 P 5 F -0.17 (where.dir) 404.78 685.33 P 0 F -0.07 (. For a client that re-) 458.75 685.33 P 3.19 (quires only the post-) 216 673.33 P 4 F 7.66 (SYMLINK) 307.47 673.33 P 0 F 3.19 ( directory attributes, these can be found in) 349.45 673.33 P 5 F 3.65 (dir_wcc.after) 216 661.33 P 0 F 1.52 (. Even though the) 293.96 661.33 P 4 F 3.65 (SYMLINK) 373.05 661.33 P 0 F 1.52 ( failed, full) 415.03 661.33 P 5 F 3.65 (wcc_data) 466.23 661.33 P 0 F 1.52 ( is re-) 514.2 661.33 P -0.14 (turned to allow the client to determine whether the failing) 216 649.33 P 4 F -0.33 (SYMLINK) 447.79 649.33 P 0 F -0.14 ( changed the) 489.76 649.33 P (directory.) 216 637.33 T 8 F (IMPLEMENTATION) 72 615.33 T 0 F (Refer to) 72 597.33 T 3 F (General comments on filenames) 106.97 597.33 T 0 F ( on page 17.) 235.49 597.33 T -0.28 (For symbolic links, the actual file system node and its contents are expected to be created in a single atomic operation.) 72 579.33 P -0.58 (That is, once the symbolic link is visible, there must not be a window where a) 72 567.33 P 4 F -1.39 (READLINK) 376.41 567.33 P 0 F -0.58 ( would fail or return incorrect) 424.38 567.33 P (data.) 72 555.33 T 8 F (ERRORS) 72 533.33 T 4 F (NFS3ERR_IO) 90 517.33 T (NFS3ERR_ACCES) 90 505.33 T (NFS3ERR_EXIST) 90 493.33 T (NFS3ERR_NOTDIR) 90 481.33 T (NFS3ERR_NOSPC) 90 469.33 T (NFS3ERR_ROFS) 90 457.33 T (NFS3ERR_NAMETOOLONG) 90 445.33 T (NFS3ERR_DQUOT) 90 433.33 T (NFS3ERR_STALE) 90 421.33 T (NFS3ERR_BADHANDLE) 90 409.33 T (NFS3ERR_NOTSUPP) 90 397.33 T (NFS3ERR_SERVERFAULT) 90 385.33 T 8 F (SEE ALSO) 72 363.33 T 4 F 2.03 (READLINK) 72 345.33 P 0 F 0.85 ( on page 26) 119.97 345.33 P 0.85 (,) 168.86 345.33 P 4 F 2.03 (CREATE) 174.71 345.33 P 0 F 0.85 ( on page 33) 210.69 345.33 P 0.85 (,) 259.58 345.33 P 4 F 2.03 (MKDIR) 265.42 345.33 P 0 F 0.85 ( on page 36) 295.4 345.33 P 0.85 (,) 344.29 345.33 P 4 F 2.03 (MKNOD) 350.14 345.33 P 0 F 0.85 ( on page 40) 380.12 345.33 P 0.85 (,) 429.01 345.33 P 9 F 2.03 (FSINFO) 434.85 345.33 P 0 F 0.85 ( on page 59) 470.83 345.33 P 0.85 (, and) 519.72 345.33 P 4 F (PATHCONF) 72 333.33 T 0 F ( on page 62.) 119.97 333.33 T FMENDPAGE %%EndPage: "39" 44 %%Page: "40" 44 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (MKNOD) 72 35.33 T 2 F (40) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (11) 145.85 710.67 T (MKNOD) 279.13 710.67 T 2 10 Q (MKNOD: Create a special device) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (MKNOD3res) 90 649.33 T (NFSPROC3_MKNOD\050MKNOD3args\051 = 11;) 90 637.33 T (struct devicedata3 {) 90 613.33 T (sattr3) 108 601.33 T (dev_attributes;) 180 601.33 T (specdata3) 108 589.33 T (spec;) 180 589.33 T (};) 90 577.33 T (union mknoddata3 switch \050ftype3 type\051 {) 90 553.33 T (case NF3CHR:) 90 541.33 T (case NF3BLK:) 90 529.33 T (devicedata3) 108 517.33 T (device;) 180 517.33 T (case NF3SOCK:) 90 505.33 T (case NF3FIFO:) 90 493.33 T (sattr3) 108 481.33 T (pipe_attributes;) 180 481.33 T (default:) 90 469.33 T (void;) 108 457.33 T (};) 90 445.33 T (struct MKNOD3args {) 90 421.33 T (diropargs3) 108 409.33 T (where;) 180 409.33 T (mknoddata3) 108 397.33 T (what;) 180 397.33 T (};) 90 385.33 T (struct MKNOD3resok {) 90 361.33 T (post_op_fh3) 108 349.33 T (obj;) 198 349.33 T (post_op_attr) 108 337.33 T (obj_attributes;) 198 337.33 T (wcc_data) 108 325.33 T (dir_wcc;) 198 325.33 T (};) 90 313.33 T (struct MKNOD3resfail {) 90 289.33 T (wcc_data) 108 277.33 T (dir_wcc;) 180 277.33 T (};) 90 265.33 T (union MKNOD3res switch \050nfsstat3 status\051 {) 90 241.33 T (case NFS3_OK:) 90 229.33 T (MKNOD3resok) 108 217.33 T (resok;) 198 217.33 T (default:) 90 205.33 T (MKNOD3resfail) 108 193.33 T (resfail;) 198 193.33 T (};) 90 181.33 T 8 F (DESCRIPTION) 72 159.33 T 0 F -0.44 (Procedure) 72 141.33 P 4 F -1.06 (MKNOD) 114.57 141.33 P 0 F -0.44 ( creates a new special file of the type,) 144.56 141.33 P 5 F -1.06 (what.type) 293.22 141.33 P 0 F -0.44 (. Special files can be device files or named pipes.) 347.19 141.33 P (On entry, the arguments in) 72 129.33 T 5 F (MKNOD3args) 181.37 129.33 T 0 F ( are:) 241.34 129.33 T 5 F (where) 90 113.33 T 0 F (The location of the special file to be created:) 216 113.33 T 5 F (dir) 108 101.33 T 0 F (The file handle for the directory in which the special file is to be created.) 216 101.33 T 5 F (name) 108 89.33 T 0 F 0.48 (The name that is to be associated with the created special file. Refer to) 216 89.33 P 3 F 0.48 (General) 507.25 89.33 P (comments on filenames) 216 77.33 T 0 F ( on page 17.) 309.27 77.33 T FMENDPAGE %%EndPage: "40" 45 %%Page: "41" 45 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (41) 300.44 35.33 T 4 F (MKNOD) 510.02 35.33 T 5 F (what) 90 713.33 T 0 F 0.3 (A discriminated union identifying the type of the special file to be created along) 216 713.33 P (with the data and attributes appropriate to the type of the special file:) 216 701.33 T 5 F (type) 108 689.33 T 0 F (The type of the object to be created.) 216 689.33 T 0.3 (When creating a character special file \050) 72 671.33 P 5 F 0.71 (what.type) 230.29 671.33 P 0 F 0.3 ( is) 284.26 671.33 P 4 F 0.71 (NF3CHR) 296.52 671.33 P 0 F 0.3 (\051 or a block special file \050) 332.49 671.33 P 5 F 0.71 (what.type) 431.97 671.33 P 0 F 0.3 ( is) 485.94 671.33 P 4 F 0.71 (NF3BLK) 498.19 671.33 P 0 F 0.3 (\051,) 534.17 671.33 P 5 F (what) 72 659.33 T 0 F ( includes:) 95.99 659.33 T 5 F (device) 90 643.33 T 0 F (A structure) 216 643.33 T 5 F (devicedata3) 263.18 643.33 T 0 F ( with the following components:) 329.15 643.33 T 5 F (dev_attributes) 108 631.33 T 0 F (The initial attributes for the special file.) 216 631.33 T 5 F (spec) 108 619.33 T 0 F 0.26 (The major number stored in) 216 619.33 P 5 F 0.63 (device.spec.specdata1) 331.4 619.33 P 0 F 0.26 ( and the minor num-) 457.33 619.33 P (ber stored in) 216 607.33 T 5 F (device.spec.specdata2) 268.46 607.33 T 0 F (.) 394.39 607.33 T (When creating a socket \050) 72 589.33 T 5 F (what.type) 171.35 589.33 T 0 F ( is) 225.33 589.33 T 4 F (NF3SOCK) 236.99 589.33 T 0 F (\051 or a FIFO \050) 278.97 589.33 T 5 F (what.type) 330.04 589.33 T 0 F ( is) 384.01 589.33 T 4 F (NF3FIFO) 395.67 589.33 T 0 F (\051,) 437.65 589.33 T 5 F (what) 445.97 589.33 T 0 F ( includes:) 469.96 589.33 T 5 F (pipe_attributes) 90 573.33 T 0 F (The initial attributes for the special file.) 216 573.33 T (On successful return,) 72 555.33 T 5 F (MKNOD3res.status) 159.15 555.33 T 0 F ( is) 255.1 555.33 T 4 F (NFS3_OK) 266.76 555.33 T 0 F ( and) 308.74 555.33 T 5 F (MKNOD3res.resok) 328.17 555.33 T 0 F ( contains:) 418.12 555.33 T 5 F (obj) 90 539.33 T 0 F (The file handle for the newly created special file.) 216 539.33 T 5 F (obj_attributes) 90 527.33 T 0 F (The attributes for the newly created special file.) 216 527.33 T 5 F (dir_wcc) 90 515.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 515.33 P 5 F -0.17 (where.dir) 404.78 515.33 P 0 F -0.07 (. For a client that re-) 458.75 515.33 P 4.39 (quires only the post-) 216 503.33 P 4 F 10.54 (MKNOD) 311.07 503.33 P 0 F 4.39 ( directory attributes, these can be found in) 341.05 503.33 P 5 F (dir_wcc.after) 216 491.33 T 0 F (.) 293.96 491.33 T -0.33 (Otherwise,) 72 473.33 P 5 F -0.78 (MKNOD3res.status) 117.75 473.33 P 0 F -0.33 ( contains the error on failure and) 213.7 473.33 P 5 F -0.78 (MKNOD3res.resfail) 344.36 473.33 P 0 F -0.33 ( contains the following:) 446.31 473.33 P 5 F (dir_wcc) 90 457.33 T 0 F -0.07 (Weak cache consistency data for the directory,) 216 457.33 P 5 F -0.17 (where.dir) 404.78 457.33 P 0 F -0.07 (. For a client that re-) 458.75 457.33 P 4.39 (quires only the post-) 216 445.33 P 4 F 10.54 (MKNOD) 311.07 445.33 P 0 F 4.39 ( directory attributes, these can be found in) 341.05 445.33 P 5 F 0.93 (dir_wcc.after) 216 433.33 P 0 F 0.39 (. Even though the) 293.96 433.33 P 4 F 0.93 (MKNOD) 368.51 433.33 P 0 F 0.39 ( failed, full) 398.49 433.33 P 5 F 0.93 (wcc_data) 446.29 433.33 P 0 F 0.39 ( is returned) 494.26 433.33 P -0.23 (to allow the client to determine whether the failing) 216 421.33 P 4 F -0.54 (MKNOD) 419.1 421.33 P 0 F -0.23 ( changed the directory.) 449.09 421.33 P 8 F (IMPLEMENTATION) 72 399.33 T 0 F (Refer to) 72 381.33 T 3 F (General comments on filenames) 106.97 381.33 T 0 F ( on page 17.) 235.49 381.33 T -0.01 (Without explicit support for special file type creation in the NFS version 2 protocol, fields in the) 72 363.33 P 4 F -0.03 (CREATE) 459.89 363.33 P 0 F -0.01 ( arguments) 495.88 363.33 P 0.02 (were overloaded to indicate creation of certain types of objects. This overloading is not necessary in the NFS version) 72 351.33 P (3 protocol.) 72 339.33 T -0.56 (If the server does not support any of the defined types, the error,) 72 321.33 P 4 F -1.33 (NFS3ERR_NOTSUPP) 324.31 321.33 P 0 F -0.56 (, should be returned. Otherwise,) 414.26 321.33 P 0.38 (if the server does not support the target type or the target type is illegal, the error,) 72 309.33 P 4 F 0.91 (NFS3ERR_BADTYPE) 405.7 309.33 P 0 F 0.38 (, should be) 495.65 309.33 P -0.16 (returned. Note that) 72 297.33 P 4 F -0.38 (NF3REG) 149.25 297.33 P 0 F -0.16 (,) 185.23 297.33 P 4 F -0.38 (NF3DIR) 190.07 297.33 P 0 F -0.16 (, and) 226.05 297.33 P 4 F -0.38 (NF3LNK) 247.67 297.33 P 0 F -0.16 ( are illegal types for) 283.65 297.33 P 4 F -0.38 (MKNOD) 365.3 297.33 P 0 F -0.16 (. The procedures,) 395.28 297.33 P 4 F -0.38 (CREATE) 466.7 297.33 P 0 F -0.16 (,) 502.68 297.33 P 4 F -0.38 (MKDIR) 507.52 297.33 P 0 F -0.16 (,) 537.5 297.33 P (and) 72 285.33 T 4 F (SYMLINK) 88.93 285.33 T 0 F ( should be used to create these file types, respectively, instead of) 130.91 285.33 T 4 F (MKNOD) 391.82 285.33 T 0 F (.) 421.81 285.33 T 8 F (ERRORS) 72 263.33 T 4 F (NFS3ERR_IO) 90 247.33 T (NFS3ERR_ACCES) 90 235.33 T (NFS3ERR_EXIST) 90 223.33 T (NFS3ERR_NOTDIR) 90 211.33 T (NFS3ERR_NOSPC) 90 199.33 T (NFS3ERR_ROFS) 90 187.33 T (NFS3ERR_NAMETOOLONG) 90 175.33 T (NFS3ERR_DQUOT) 90 163.33 T (NFS3ERR_STALE) 90 151.33 T (NFS3ERR_BADHANDLE) 90 139.33 T (NFS3ERR_NOTSUPP) 90 127.33 T (NFS3ERR_SERVERFAULT) 90 115.33 T (NFS3ERR_BADTYPE) 90 103.33 T FMENDPAGE %%EndPage: "41" 46 %%Page: "42" 46 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (MKNOD) 72 35.33 T 2 F (42) 300.44 35.33 T (Version 3) 495.01 35.33 T 8 F (SEE ALSO) 72 713.33 T 4 F (CREATE) 72 695.33 T 0 F ( on page 33) 107.98 695.33 T (,) 154.34 695.33 T 4 F (MKDIR) 159.33 695.33 T 0 F ( on page 36) 189.32 695.33 T (,) 235.67 695.33 T 4 F (SYMLINK) 240.67 695.33 T 0 F ( on page 38) 282.64 695.33 T (, and) 329 695.33 T 4 F (PATHCONF) 350.93 695.33 T 0 F ( on page 62) 398.9 695.33 T (.) 445.26 695.33 T FMENDPAGE %%EndPage: "42" 47 %%Page: "43" 47 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (43) 300.44 35.33 T 4 F (REMOVE) 504.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (12) 145.85 710.67 T (REMOVE) 275.24 710.67 T 2 10 Q (REMOVE: Remove a File) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (REMOVE3res) 90 649.33 T (NFSPROC3_REMOVE\050REMOVE3args\051 = 12;) 90 637.33 T (struct REMOVE3args {) 90 613.33 T (diropargs3) 108 601.33 T (object;) 180 601.33 T (};) 90 589.33 T (struct REMOVE3resok {) 90 565.33 T (wcc_data) 108 553.33 T (dir_wcc;) 180 553.33 T (};) 90 541.33 T (struct REMOVE3resfail {) 90 517.33 T (wcc_data) 108 505.33 T (dir_wcc;) 180 505.33 T (};) 90 493.33 T (union REMOVE3res switch \050nfsstat3 status\051 {) 90 469.33 T (case NFS3_OK:) 90 457.33 T (REMOVE3resok) 108 445.33 T (resok;) 198 445.33 T (default:) 90 433.33 T (REMOVE3resfail) 108 421.33 T (resfail;) 198 421.33 T (};) 90 409.33 T 8 F (DESCRIPTION) 72 387.33 T 0 F 0.07 (Procedure) 72 369.33 P 4 F 0.16 (REMOVE) 115.08 369.33 P 0 F 0.07 ( removes \050deletes\051 an entry from a directory. If the entry in the directory was the last reference to) 151.06 369.33 P (the corresponding file system object, the object may be destroyed. On entry, the arguments in) 72 357.33 T 5 F (REMOVE3args) 448.4 357.33 T 0 F ( are:) 514.37 357.33 T 5 F (object) 90 341.33 T 0 F (A) 216 341.33 T 5 F (diropargs3) 225.71 341.33 T 0 F ( structure identifying the entry to be removed:) 285.68 341.33 T 5 F (dir) 108 329.33 T 0 F (The file handle for the directory from which the entry is to be removed.) 216 329.33 T 5 F (name) 108 317.33 T 0 F -0.35 (The name of the entry to be removed. Refer to) 216 317.33 P 3 F -0.35 (General comments on filenames) 400.39 317.33 P 0 F -0.35 ( on) 527.86 317.33 P (page 17.) 216 305.33 T (On successful return,) 72 287.33 T 5 F (REMOVE3res.status) 159.15 287.33 T 0 F ( is) 261.1 287.33 T 4 F (NFS3_OK) 272.76 287.33 T 0 F ( and) 314.74 287.33 T 5 F (REMOVE3res.resok) 334.17 287.33 T 0 F ( contains:) 430.11 287.33 T 5 F (dir_wcc) 90 271.33 T 0 F 0.61 (Weak cache consistency data for the directory,) 216 271.33 P 5 F 1.47 (object.dir) 409.57 271.33 P 0 F 0.61 (. For a client that) 469.54 271.33 P 3.02 (requires only the post-) 216 259.33 P 4 F 7.24 (REMOVE) 314.71 259.33 P 0 F 3.02 ( directory attributes, these can be found in) 350.69 259.33 P 5 F (dir_wcc.after) 216 247.33 T 0 F (.) 293.96 247.33 T -0.31 (Otherwise,) 72 229.33 P 5 F -0.73 (REMOVE3res.status) 117.77 229.33 P 0 F -0.31 ( contains the error on failure and) 219.71 229.33 P 5 F -0.73 (REMOVE3res.resfail) 350.53 229.33 P 0 F -0.31 ( contains the follow-) 458.47 229.33 P (ing:) 72 217.33 T 5 F (dir_wcc) 90 201.33 T 0 F 0.61 (Weak cache consistency data for the directory,) 216 201.33 P 5 F 1.47 (object.dir) 409.57 201.33 P 0 F 0.61 (. For a client that) 469.54 201.33 P 3.02 (requires only the post-) 216 189.33 P 4 F 7.24 (REMOVE) 314.71 189.33 P 0 F 3.02 ( directory attributes, these can be found in) 350.69 189.33 P 5 F -0.67 (dir_wcc.after) 216 177.33 P 0 F -0.28 (. Even though the) 293.96 177.33 P 4 F -0.67 (REMOVE) 365.85 177.33 P 0 F -0.28 ( failed, full) 401.83 177.33 P 5 F -0.67 (wcc_data) 447.62 177.33 P 0 F -0.28 ( is returned) 495.6 177.33 P -0.1 (to allow the client to determine whether the failing) 216 165.33 P 4 F -0.24 (REMOVE) 420.23 165.33 P 0 F -0.1 ( changed the directo-) 456.21 165.33 P (ry.) 216 153.33 T 8 F (IMPLEMENTATION) 72 131.33 T 0 F 0.16 (In general,) 72 113.33 P 4 F 0.38 (REMOVE) 117.56 113.33 P 0 F 0.16 ( is intended to remove non-directory file objects and) 153.54 113.33 P 4 F 0.38 (RMDIR) 366.77 113.33 P 0 F 0.16 ( is to be used to remove directories.) 396.76 113.33 P -0.09 (However,) 72 101.33 P 4 F -0.21 (REMOVE) 113.54 101.33 P 0 F -0.09 ( can be used to remove directories, subject to restrictions imposed by either the client or server in-) 149.52 101.33 P (terfaces. This had been a source of confusion in the NFS version 2 protocol.) 72 89.33 T FMENDPAGE %%EndPage: "43" 48 %%Page: "44" 48 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (REMOVE) 72 35.33 T 2 F (44) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F 0.34 (The concept of) 72 713.33 P 3 F 0.34 (last reference) 135.46 713.33 P 0 F 0.34 ( is server specific. However, if the) 190.47 713.33 P 5 F 0.81 (nlink) 332.44 713.33 P 0 F 0.34 ( field in the previous attributes of the object) 362.42 713.33 P 0.24 (had the value) 72 701.33 P 4 F 0.59 (1) 128.52 701.33 P 0 F 0.24 (, the client should not rely on referring to the object via a file handle. Likewise, the client should not) 134.52 701.33 P 0.2 (rely on the resources \050disk space, directory entry, and so on) 72 689.33 P 3 F 0.2 (.) 311.56 689.33 P 0 F 0.2 (\051 formerly associated with the object becoming immedi-) 314.06 689.33 P -0.38 (ately available. Thus, if a client needs to be able to continue to access a file after using) 72 677.33 P 4 F -0.92 (REMOVE) 413.21 677.33 P 0 F -0.38 ( to remove it, the client) 449.19 677.33 P 0.51 (should take steps to make sure that the file will still be accessible. The usual mechanism used is to use) 72 665.33 P 4 F 1.21 (RENAME) 493.24 665.33 P 0 F 0.51 ( to) 529.22 665.33 P (rename the file from its old name to a new) 72 653.33 T 3 F (hidden) 244.1 653.33 T 0 F ( name.) 271.3 653.33 T (Refer to) 72 635.33 T 3 F (General comments on filenames) 106.97 635.33 T 0 F ( on page 17.) 235.49 635.33 T 8 F (ERRORS) 72 613.33 T 4 F (NFS3ERR_NOENT) 90 597.33 T (NFS3ERR_IO) 90 585.33 T (NFS3ERR_ACCES) 90 573.33 T (NFS3ERR_NOTDIR) 90 561.33 T (NFS3ERR_NAMETOOLONG) 90 549.33 T (NFS3ERR_ROFS) 90 537.33 T (NFS3ERR_STALE) 90 525.33 T (NFS3ERR_BADHANDLE) 90 513.33 T (NFS3ERR_SERVERFAULT) 90 501.33 T 8 F (SEE ALSO) 72 479.33 T 4 F (RMDIR) 72 461.33 T 0 F ( on page 45) 101.98 461.33 T ( and) 148.34 461.33 T 4 F (RENAME) 167.77 461.33 T 0 F ( on page 47.) 203.75 461.33 T FMENDPAGE %%EndPage: "44" 49 %%Page: "45" 49 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (45) 300.44 35.33 T 4 F (RMDIR) 510.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (13) 145.85 710.67 T (RMDIR) 282.24 710.67 T 2 10 Q (RMDIR: Remove a Directory) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (RMDIR3res) 90 649.33 T (NFSPROC3_RMDIR\050RMDIR3args\051 = 13;) 90 637.33 T (struct RMDIR3args {) 90 613.33 T (diropargs3) 108 601.33 T (object;) 180 601.33 T (};) 90 589.33 T (struct RMDIR3resok {) 90 565.33 T (wcc_data) 108 553.33 T (dir_wcc;) 180 553.33 T (};) 90 541.33 T (struct RMDIR3resfail {) 90 517.33 T (wcc_data) 108 505.33 T (dir_wcc;) 180 505.33 T (};) 90 493.33 T (union RMDIR3res switch \050nfsstat3 status\051 {) 90 469.33 T (case NFS3_OK:) 90 457.33 T (RMDIR3resok) 108 445.33 T (resok;) 198 445.33 T (default:) 90 433.33 T (RMDIR3resfail) 108 421.33 T (resfail;) 198 421.33 T (};) 90 409.33 T 8 F (DESCRIPTION) 72 387.33 T 0 F 0.3 (Procedure) 72 369.33 P 4 F 0.71 (RMDIR) 115.31 369.33 P 0 F 0.3 ( removes \050deletes\051 a subdirectory from a directory. If the directory entry of the subdirectory is the) 145.3 369.33 P (last reference to the subdirectory, the subdirectory may be destroyed. On entry, the arguments in) 72 357.33 T 5 F (RMDIR3args) 460.04 357.33 T 0 F ( are:) 520 357.33 T 5 F (object) 90 341.33 T 0 F (A) 216 341.33 T 5 F (diropargs3) 225.71 341.33 T 0 F ( structure identifying the directory entry to be removed:) 285.68 341.33 T 5 F (dir) 108 329.33 T 0 F (The file handle for the directory from which the subdirectory is to be removed.) 216 329.33 T 5 F (name) 108 317.33 T 0 F 0.03 (The name of the subdirectory to be removed. Refer to) 216 317.33 P 3 F 0.03 (General comments on file-) 433.61 317.33 P (names) 216 305.33 T 0 F ( on page 17.) 241.54 305.33 T (On successful return,) 72 287.33 T 5 F (RMDIR3res.status) 159.15 287.33 T 0 F ( is) 255.1 287.33 T 4 F (NFS3_OK) 266.76 287.33 T 0 F ( and) 308.74 287.33 T 5 F (RMDIR3res.resok) 328.17 287.33 T 0 F ( contains:) 418.12 287.33 T 5 F (dir_wcc) 90 271.33 T 0 F 0.61 (Weak cache consistency data for the directory,) 216 271.33 P 5 F 1.47 (object.dir) 409.57 271.33 P 0 F 0.61 (. For a client that) 469.54 271.33 P 3.62 (requires only the post-) 216 259.33 P 4 F 8.68 (RMDIR) 316.51 259.33 P 0 F 3.62 ( directory attributes, these can be found in) 346.49 259.33 P 5 F (dir_wcc.after) 216 247.33 T 0 F (.) 293.96 247.33 T -0.33 (Otherwise,) 72 229.33 P 5 F -0.78 (RMDIR3res.status) 117.75 229.33 P 0 F -0.33 ( contains the error on failure and) 213.7 229.33 P 5 F -0.78 (RMDIR3res.resfail) 344.36 229.33 P 0 F -0.33 ( contains the following:) 446.31 229.33 P 5 F (dir_wcc) 90 213.33 T 0 F 0.61 (Weak cache consistency data for the directory,) 216 213.33 P 5 F 1.47 (object.dir) 409.57 213.33 P 0 F 0.61 (. For a client that) 469.54 213.33 P 3.62 (requires only the post-) 216 201.33 P 4 F 8.68 (RMDIR) 316.51 201.33 P 0 F 3.62 ( directory attributes, these can be found in) 346.49 201.33 P 5 F 0.37 (dir_wcc.after) 216 189.33 P 0 F 0.15 (. Note that even though the) 293.96 189.33 P 4 F 0.37 (RMDIR) 405.63 189.33 P 0 F 0.15 ( failed, full) 435.62 189.33 P 5 F 0.37 (wcc_data) 482.71 189.33 P 0 F 0.15 ( is) 530.68 189.33 P 0.21 (returned to allow the client to determine whether the failing) 216 177.33 P 4 F 0.51 (RMDIR) 459.08 177.33 P 0 F 0.21 ( changed the) 489.06 177.33 P (directory.) 216 165.33 T 8 F (IMPLEMENTATION) 72 143.33 T 0 F (Note that on some servers, removal of a non-empty directory is disallowed.) 72 125.33 T -0.59 (On some servers, the filename, \322) 72 107.33 P 4 F -1.42 (.) 199.76 107.33 P 0 F -0.59 (\323, is illegal. These servers will return the error,) 205.76 107.33 P 4 F -1.42 (NFS3ERR_INVAL) 389.71 107.33 P 0 F -0.59 (. On some servers,) 467.67 107.33 P 0.24 (the filename, \322) 72 95.33 P 4 F 0.57 (..) 131.6 95.33 P 0 F 0.24 (\323, is illegal. These servers will return the error,) 143.59 95.33 P 4 F 0.57 (NFS3ERR_EXIST) 335.04 95.33 P 0 F 0.24 (. This would seem inconsistent,) 413 95.33 P 0.1 (but allows these servers to comply with their own specific interface definitions. Clients should be prepared to handle) 72 83.33 P FMENDPAGE %%EndPage: "45" 50 %%Page: "46" 50 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (RMDIR) 72 35.33 T 2 F (46) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F (both cases.) 72 713.33 T -0.23 (The client should not rely on the resources \050disk space, directory entry, and so on) 72 695.33 P 3 F -0.23 (.) 393.5 695.33 P 0 F -0.23 (\051 formerly associated with the direc-) 396 695.33 P (tory becoming immediately available.) 72 683.33 T 8 F (ERRORS) 72 661.33 T 4 F (NFS3ERR_NOENT) 90 645.33 T (NFS3ERR_IO) 90 633.33 T (NFS3ERR_ACCES) 90 621.33 T (NFS3ERR_INVAL) 90 609.33 T (NFS3ERR_EXIST) 90 597.33 T (NFS3ERR_NOTDIR) 90 585.33 T (NFS3ERR_NAMETOOLONG) 90 573.33 T (NFS3ERR_ROFS) 90 561.33 T (NFS3ERR_NOTEMPTY) 90 549.33 T (NFS3ERR_STALE) 90 537.33 T (NFS3ERR_BADHANDLE) 90 525.33 T (NFS3ERR_NOTSUPP) 90 513.33 T (NFS3ERR_SERVERFAULT) 90 501.33 T 8 F (SEE ALSO) 72 479.33 T 4 F (REMOVE) 72 461.33 T 0 F ( on page 43) 107.98 461.33 T (.) 154.34 461.33 T FMENDPAGE %%EndPage: "46" 51 %%Page: "47" 51 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (47) 300.44 35.33 T 4 F (RENAME) 504.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (14) 145.85 710.67 T (RENAME) 275.63 710.67 T 2 10 Q (RENAME: Rename a File or Directory) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (RENAME3res) 90 649.33 T (NFSPROC3_RENAME\050RENAME3args\051 = 14;) 90 637.33 T (struct RENAME3args {) 90 613.33 T (diropargs3) 108 601.33 T (from;) 180 601.33 T (diropargs3) 108 589.33 T (to;) 180 589.33 T (};) 90 577.33 T (struct RENAME3resok {) 90 553.33 T (wcc_data) 108 541.33 T (fromdir_wcc;) 180 541.33 T (wcc_data) 108 529.33 T (todir_wcc;) 180 529.33 T (};) 90 517.33 T (struct RENAME3resfail {) 90 493.33 T (wcc_data) 108 481.33 T (fromdir_wcc;) 180 481.33 T (wcc_data) 108 469.33 T (todir_wcc;) 180 469.33 T (};) 90 457.33 T (union RENAME3res switch \050nfsstat3 status\051 {) 90 433.33 T (case NFS3_OK:) 90 421.33 T (RENAME3resok) 108 409.33 T (resok;) 198 409.33 T (default:) 90 397.33 T (RENAME3resfail) 108 385.33 T (resfail;) 198 385.33 T (};) 90 373.33 T 8 F (DESCRIPTION) 72 351.33 T 0 F 0.03 (Procedure) 72 333.33 P 4 F 0.08 (RENAME) 115.05 333.33 P 0 F 0.03 ( renames the file identified by) 151.03 333.33 P 5 F 0.08 (from.name) 273.36 333.33 P 0 F 0.03 ( in the directory,) 327.33 333.33 P 5 F 0.08 (from.dir) 396.02 333.33 P 0 F 0.03 (, to) 444 333.33 P 5 F 0.08 (to.name) 459.33 333.33 P 0 F 0.03 ( in the di-) 501.31 333.33 P 0.41 (rectory,) 72 321.33 P 5 F 1 (to.dir) 105.72 321.33 P 0 F 0.41 (. The operation is required to be atomic to the client.) 141.7 321.33 P 5 F 1 (To.dir) 358.62 321.33 P 0 F 0.41 ( and) 394.6 321.33 P 5 F 1 (from.dir) 414.86 321.33 P 0 F 0.41 ( must reside on the) 462.83 321.33 P (same file system and server. On entry, the arguments in) 72 309.33 T 5 F (RENAME3args) 296.84 309.33 T 0 F ( are:) 362.8 309.33 T 5 F (from) 90 293.33 T 0 F 0.03 (A) 216 293.33 P 5 F 0.07 (diropargs3) 225.74 293.33 P 0 F 0.03 ( structure identifying the source \050the file system object to be re-) 285.71 293.33 P (named\051:) 216 281.33 T 5 F (from.dir) 108 269.33 T 0 F (The file handle for the directory from which the entry is to be renamed.) 216 269.33 T 5 F (from.name) 108 257.33 T 0 F 0.36 (The name of the entry that identifies the object to be renamed. Refer to) 216 257.33 P 3 F 0.36 (General) 507.25 257.33 P (comments on filenames) 216 245.33 T 0 F ( on page 17.) 309.27 245.33 T 5 F (to) 90 233.33 T 0 F (A) 216 233.33 T 5 F (diropargs3) 225.71 233.33 T 0 F ( structure identifying the target \050the new name of the object\051:) 285.68 233.33 T 5 F (to.dir) 108 221.33 T 0 F (The file handle for the directory to which the object is to be renamed.) 216 221.33 T 5 F (to.name) 108 209.33 T 0 F -0.57 (The new name for the object. Refer to) 216 209.33 P 3 F -0.57 (General comments on filenames) 366.04 209.33 P 0 F -0.57 ( on page 17.) 492.85 209.33 P 0.13 (If the directory,) 72 191.33 P 5 F 0.32 (to.dir) 137.35 191.33 P 0 F 0.13 (, already contains an entry with the name,) 173.33 191.33 P 5 F 0.32 (to.name) 343.71 191.33 P 0 F 0.13 (, the source object must be compatible) 385.69 191.33 P -0.01 (with the target: either both are non-directories or both are directories and the target must be empty. If compatible, the) 72 179.33 P 0.4 (existing target is removed before the rename occurs. If they are not compatible or if the target is a directory but not) 72 167.33 P (empty, the server should return the error,) 72 155.33 T 4 F (NFS3ERR_EXIST) 238.26 155.33 T 0 F (.) 316.22 155.33 T (On successful return,) 72 137.33 T 5 F (RENAME3res.status) 159.15 137.33 T 0 F ( is) 261.1 137.33 T 4 F (NFS3_OK) 272.76 137.33 T 0 F ( and) 314.74 137.33 T 5 F (RENAME3res.resok) 334.17 137.33 T 0 F ( contains:) 430.11 137.33 T 5 F (fromdir_wcc) 90 121.33 T 0 F (Weak cache consistency data for the directory,) 216 121.33 T 5 F (from.dir) 405.28 121.33 T 0 F (.) 453.25 121.33 T 5 F (todir_wcc) 90 109.33 T 0 F (Weak cache consistency data for the directory,) 216 109.33 T 5 F (to.dir) 405.28 109.33 T 0 F (.) 441.26 109.33 T -0.31 (Otherwise,) 72 91.33 P 5 F -0.73 (RENAME3res.status) 117.77 91.33 P 0 F -0.31 ( contains the error on failure and) 219.71 91.33 P 5 F -0.73 (RENAME3res.resfail) 350.53 91.33 P 0 F -0.31 ( contains the follow-) 458.47 91.33 P (ing:) 72 79.33 T FMENDPAGE %%EndPage: "47" 52 %%Page: "48" 52 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (RENAME) 72 35.33 T 2 F (48) 300.44 35.33 T (Version 3) 495.01 35.33 T 5 F (fromdir_wcc) 90 713.33 T 0 F (Weak cache consistency data for the directory,) 216 713.33 T 5 F (from.dir) 405.28 713.33 T 0 F (.) 453.25 713.33 T 5 F (todir_wcc) 90 701.33 T 0 F (Weak cache consistency data for the directory,) 216 701.33 T 5 F (to.dir) 405.28 701.33 T 0 F (.) 441.26 701.33 T 8 F (IMPLEMENTATION) 72 679.33 T 0 F -0.41 (The) 72 661.33 P 4 F -0.99 (RENAME) 89.63 661.33 P 0 F -0.41 ( operation must be atomic to the client. The message \322) 125.61 661.33 P 5 F -0.99 (to.dir) 340.94 661.33 P 0 F -0.41 ( and) 376.92 661.33 P 5 F -0.99 (from.dir) 395.53 661.33 P 0 F -0.41 ( must reside on the same) 443.51 661.33 P -0.35 (file system on the server, [or the operation will fail]\323 means that the) 72 649.33 P 5 F -0.84 (fsid) 341.16 649.33 P 0 F -0.35 ( fields in the attributes for the directories are) 365.14 649.33 P 0.08 (the same. If they reside on different file systems, the error,) 72 637.33 P 4 F 0.19 (NFS3ERR_XDEV) 309.35 637.33 P 0 F 0.08 (, is returned. Even though the operation) 381.3 637.33 P -0.52 (is atomic, the status,) 72 625.33 P 4 F -1.24 (NFS3ERR_MLINK) 153.78 625.33 P 0 F -0.52 (, may be returned if the server used a \322unlink/link/unlink\323 sequence internally.) 231.74 625.33 P 0.37 (A file handle may or may not become stale on a rename. However, server implementors are) 72 607.33 P 7 F 0.37 (strongly) 447.1 607.33 P 0 F 0.37 ( encouraged to) 480.42 607.33 P (attempt to keep file handles from becoming stale in this fashion.) 72 595.33 T 0.52 (On some servers, the filenames, \322) 72 577.33 P 4 F 1.24 (.) 209.2 577.33 P 0 F 0.52 (\323 and \322) 215.2 577.33 P 4 F 1.24 (..) 244.53 577.33 P 0 F 0.52 (\323, are illegal as either) 256.53 577.33 P 5 F 1.24 (from.name) 346.81 577.33 P 0 F 0.52 ( or) 400.78 577.33 P 5 F 1.24 (to.name) 415.14 577.33 P 0 F 0.52 (. In addition, neither) 457.11 577.33 P 5 F 0.3 (from.name) 72 565.33 P 0 F 0.13 ( nor) 125.97 565.33 P 5 F 0.3 (to.name) 144.54 565.33 P 0 F 0.13 ( can be an alias for) 186.52 565.33 P 5 F 0.3 (from.dir) 264.98 565.33 P 0 F 0.13 (. These servers will return the error,) 312.95 565.33 P 4 F 0.3 (NFS3ERR_INVAL) 459.54 565.33 P 0 F 0.13 (,) 537.5 565.33 P (in these cases.) 72 553.33 T (Refer to) 72 535.33 T 3 F (General comments on filenames) 106.97 535.33 T 0 F ( on page 17.) 235.49 535.33 T 8 F (ERRORS) 72 513.33 T 4 F (NFS3ERR_NOENT) 90 497.33 T (NFS3ERR_IO) 90 485.33 T (NFS3ERR_ACCES) 90 473.33 T (NFS3ERR_EXIST) 90 461.33 T (NFS3ERR_XDEV) 90 449.33 T (NFS3ERR_NOTDIR) 90 437.33 T (NFS3ERR_ISDIR) 90 425.33 T (NFS3ERR_INVAL) 90 413.33 T (NFS3ERR_NOSPC) 90 401.33 T (NFS3ERR_ROFS) 90 389.33 T (NFS3ERR_MLINK) 90 377.33 T (NFS3ERR_NAMETOOLONG) 90 365.33 T (NFS3ERR_NOTEMPTY) 90 353.33 T (NFS3ERR_DQUOT) 90 341.33 T (NFS3ERR_STALE) 90 329.33 T (NFS3ERR_BADHANDLE) 90 317.33 T (NFS3ERR_NOTSUPP) 90 305.33 T (NFS3ERR_SERVERFAULT) 90 293.33 T 8 F (SEE ALSO) 72 271.33 T 4 F (REMOVE) 72 253.33 T 0 F ( on page 43) 107.98 253.33 T ( and) 154.34 253.33 T 4 F (LINK) 173.76 253.33 T 0 F ( on page 49) 197.75 253.33 T (.) 244.1 253.33 T FMENDPAGE %%EndPage: "48" 53 %%Page: "49" 53 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (49) 300.44 35.33 T 4 F (LINK) 516.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (15) 145.85 710.67 T (LINK) 288.84 710.67 T 2 10 Q (LINK: Create Link to an object) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (LINK3res) 90 649.33 T (NFSPROC3_LINK\050LINK3args\051 = 15;) 90 637.33 T (struct LINK3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (file;) 180 601.33 T (diropargs3) 108 589.33 T (link;) 180 589.33 T (};) 90 577.33 T (struct LINK3resok {) 90 553.33 T (post_op_attr) 108 541.33 T (file_attributes;) 198 541.33 T (wcc_data) 108 529.33 T (linkdir_wcc;) 198 529.33 T (};) 90 517.33 T (struct LINK3resfail {) 90 493.33 T (post_op_attr) 108 481.33 T (file_attributes;) 198 481.33 T (wcc_data) 108 469.33 T (linkdir_wcc;) 198 469.33 T (};) 90 457.33 T (union LINK3res switch \050nfsstat3 status\051 {) 90 433.33 T (case NFS3_OK:) 90 421.33 T (LINK3resok) 108 409.33 T (resok;) 198 409.33 T (default:) 90 397.33 T (LINK3resfail) 108 385.33 T (resfail;) 198 385.33 T (};) 90 373.33 T 8 F (DESCRIPTION) 72 351.33 T 0 F -0.32 (Procedure) 72 333.33 P 4 F -0.76 (LINK) 114.7 333.33 P 0 F -0.32 ( creates a hard link from) 138.69 333.33 P 5 F -0.76 (file) 236.7 333.33 P 0 F -0.32 ( to) 260.69 333.33 P 5 F -0.76 (link.name) 272.83 333.33 P 0 F -0.32 (, in the directory,) 326.8 333.33 P 5 F -0.76 (link.dir) 396.59 333.33 P 0 F -0.32 (.) 444.56 333.33 P 5 F -0.76 (file) 449.24 333.33 P 0 F -0.32 ( and) 473.23 333.33 P 5 F -0.76 (link.dir) 492.03 333.33 P 0 F (must reside on the same file system and server. On entry, the arguments in) 72 321.33 T 5 F (LINK3args) 372.35 321.33 T 0 F ( are:) 426.32 321.33 T 5 F (file) 90 305.33 T 0 F (The file handle for the existing file system object.) 216 305.33 T 5 F (link) 90 293.33 T 0 F (The location of the link to be created:) 216 293.33 T 5 F (link.dir) 108 281.33 T 0 F (The file handle for the directory in which the link is to be created.) 216 281.33 T 5 F (link.name) 108 269.33 T 0 F -0.55 (The name that is to be associated with the created link. Refer to) 216 269.33 P 3 F -0.55 (General comments) 465.33 269.33 P (on filenames) 216 257.33 T 0 F ( on page 17.) 266.8 257.33 T (On successful return,) 72 239.33 T 5 F (LINK3res.status) 159.15 239.33 T 0 F ( is) 249.1 239.33 T 4 F (NFS3_OK) 260.77 239.33 T 0 F ( and) 302.74 239.33 T 5 F (LINK3res.resok) 322.17 239.33 T 0 F ( contains:) 406.13 239.33 T 5 F (file_attributes) 90 223.33 T 0 F (The post-operation attributes of the file system object identified by file.) 216 223.33 T 5 F (linkdir_wcc) 90 211.33 T 0 F (Weak cache consistency data for the directory,) 216 211.33 T 5 F (link.dir) 405.28 211.33 T 0 F (.) 453.25 211.33 T (Otherwise,) 72 193.33 T 5 F (LINK3res.status) 118.07 193.33 T 0 F ( contains the error on failure and) 208.02 193.33 T 5 F (LINK3res.resfail) 340.97 193.33 T 0 F ( contains the following:) 436.92 193.33 T 5 F (file_attributes) 90 177.33 T 0 F (The post-operation attributes of the file system object identified by) 216 177.33 T 5 F (file) 485.82 177.33 T 0 F (.) 509.81 177.33 T 5 F (linkdir_wcc) 90 165.33 T 0 F (Weak cache consistency data for the directory,) 216 165.33 T 5 F (link.dir) 405.28 165.33 T 0 F (.) 453.25 165.33 T 8 F (IMPLEMENTATION) 72 143.33 T 0 F 0.17 (Changes to any property of the hard-linked files are reflected in all of the linked files. When a hard link is made to a) 72 125.33 P (file, the attributes for the file should have a value for) 72 113.33 T 5 F (nlink) 285.17 113.33 T 0 F ( that is one greater than the value before the) 315.16 113.33 T 4 F (LINK) 492.79 113.33 T 0 F (.) 516.78 113.33 T 0.49 (The comments under) 72 95.33 P 4 F 1.16 (RENAME) 160.34 95.33 P 0 F 0.49 ( regarding object and target residing on the same file system apply here as well. The) 196.32 95.33 P (comments regarding the target name applies as well. Refer to) 72 83.33 T 3 F (General comments on filenames) 319.31 83.33 T 0 F ( on page 17.) 447.83 83.33 T FMENDPAGE %%EndPage: "49" 54 %%Page: "50" 54 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (LINK) 72 35.33 T 2 F (50) 300.44 35.33 T (Version 3) 495.01 35.33 T 8 F (ERRORS) 72 713.33 T 4 F (NFS3ERR_IO) 90 697.33 T (NFS3ERR_ACCES) 90 685.33 T (NFS3ERR_EXIST) 90 673.33 T (NFS3ERR_XDEV) 90 661.33 T (NFS3ERR_NOTDIR) 90 649.33 T (NFS3ERR_INVAL) 90 637.33 T (NFS3ERR_NOSPC) 90 625.33 T (NFS3ERR_ROFS) 90 613.33 T (NFS3ERR_MLINK) 90 601.33 T (NFS3ERR_NAMETOOLONG) 90 589.33 T (NFS3ERR_DQUOT) 90 577.33 T (NFS3ERR_STALE) 90 565.33 T (NFS3ERR_BADHANDLE) 90 553.33 T (NFS3ERR_NOTSUPP) 90 541.33 T (NFS3ERR_SERVERFAULT) 90 529.33 T 8 F (SEE ALSO) 72 507.33 T 4 F (SYMLINK) 72 489.33 T 0 F ( on page 38) 113.98 489.33 T (,) 160.33 489.33 T 4 F (RENAME) 165.33 489.33 T 0 F ( on page 47) 201.31 489.33 T (, and) 247.66 489.33 T 4 F (FSINFO) 269.59 489.33 T 0 F ( on page 59) 305.57 489.33 T (.) 351.93 489.33 T FMENDPAGE %%EndPage: "50" 55 %%Page: "51" 55 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (51) 300.44 35.33 T 4 F (READDIR) 498.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (16) 145.85 710.67 T (READDIR) 274.08 710.67 T 2 10 Q (READDIR: Read From Directory) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (READDIR3res) 90 649.33 T (NFSPROC3_READDIR\050READDIR3args\051 = 16;) 90 637.33 T (struct READDIR3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (dir;) 180 601.33 T (cookie3) 108 589.33 T (cookie;) 180 589.33 T (cookieverf3) 108 577.33 T (cookieverf;) 180 577.33 T (count3) 108 565.33 T (count;) 180 565.33 T (};) 90 553.33 T (struct entry3 {) 90 529.33 T (fileid3) 108 517.33 T (fileid;) 180 517.33 T (filename3) 108 505.33 T (name;) 180 505.33 T (cookie3) 108 493.33 T (cookie;) 180 493.33 T (entry3) 108 481.33 T (*nextentry;) 180 481.33 T (};) 90 469.33 T (struct dirlist3 {) 90 445.33 T (entry3) 108 433.33 T (*entries;) 162 433.33 T (bool) 108 421.33 T (eof;) 162 421.33 T (};) 90 409.33 T (struct READDIR3resok {) 90 385.33 T (post_op_attr) 108 373.33 T (dir_attributes;) 198 373.33 T (cookieverf3) 108 361.33 T (cookieverf;) 198 361.33 T (dirlist3) 108 349.33 T (reply;) 198 349.33 T (};) 90 337.33 T (struct READDIR3resfail {) 90 313.33 T (post_op_attr) 108 301.33 T (dir_attributes;) 198 301.33 T (};) 90 289.33 T (union READDIR3res switch \050nfsstat3 status\051 {) 90 265.33 T (case NFS3_OK:) 90 253.33 T (READDIR3resok) 108 241.33 T (resok;) 216.72 241.33 T (default:) 90 229.33 T (READDIR3resfail) 108 217.33 T (resfail;) 216.72 217.33 T (};) 90 205.33 T 8 F (DESCRIPTION) 72 183.33 T 0 F 0.39 (Procedure) 72 163.33 P 4 F 0.94 (READDIR) 115.41 163.33 P 0 F 0.39 ( retrieves a variable number of entries, in sequence, from a directory and returns the name and) 157.38 163.33 P 1.04 (file identifier for each, with information to allow the client to request additional directory entries in a subsequent) 72 151.33 P 4 F (READDIR) 72 139.33 T 0 F ( request. On entry, the arguments in) 113.98 139.33 T 5 F (READDIR3args) 259.71 139.33 T 0 F ( are:) 331.67 139.33 T 5 F (dir) 90 127.33 T 0 F (The file handle for the directory to be read.) 216 127.33 T 5 F (cookie) 90 115.33 T 0 F -0.2 (This should be set to) 216 115.33 P 4 F -0.47 (0) 300.24 115.33 P 0 F -0.2 ( in the first request to read the directory. On subsequent re-) 306.24 115.33 P (quests, it should be a) 216 103.33 T 5 F (cookie) 302.06 103.33 T 0 F ( as returned by the server.) 338.04 103.33 T 5 F (cookieverf) 90 91.33 T 0 F -0.2 (This should be set to) 216 91.33 P 4 F -0.47 (0) 300.24 91.33 P 0 F -0.2 ( in the first request to read the directory. On subsequent re-) 306.24 91.33 P -0.48 (quests, it should be a) 216 79.33 P 5 F -1.16 (cookieverf) 299.65 79.33 P 0 F -0.48 ( as returned by the server. The) 359.62 79.33 P 5 F -1.16 (cookieverf) 480.03 79.33 P FMENDPAGE %%EndPage: "51" 56 %%Page: "52" 56 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (READDIR) 72 35.33 T 2 F (52) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F (must match that returned by the) 216 713.33 T 4 F (READDIR) 345.36 713.33 T 0 F ( in which the) 387.34 713.33 T 5 F (cookie) 441.75 713.33 T 0 F ( was acquired.) 477.73 713.33 T 5 F (count) 90 701.33 T 0 F -0.55 (The maximum size of the) 216 701.33 P 5 F -1.31 (READDIR3resok) 317.92 701.33 P 0 F -0.55 ( structure, in bytes. The size must in-) 395.87 701.33 P 0.84 (clude all XDR overhead. The server is free to return less than) 216 689.33 P 5 F 2.01 (count) 473.92 689.33 P 0 F 0.84 ( bytes of) 503.9 689.33 P (data.) 216 677.33 T (On successful return,) 72 659.33 T 5 F (READDIR3res.status) 159.15 659.33 T 0 F ( is) 267.09 659.33 T 4 F (NFS3_OK) 278.76 659.33 T 0 F ( and) 320.73 659.33 T 5 F (READDIR3res.resok) 340.16 659.33 T 0 F ( contains:) 442.11 659.33 T 5 F (dir_attributes) 90 643.33 T 0 F (The attributes of the directory,) 216 643.33 T 5 F (dir) 340.35 643.33 T 0 F (.) 358.34 643.33 T 5 F (cookieverf) 90 631.33 T 0 F (The cookie verifier.) 216 631.33 T 5 F (reply) 90 619.33 T 0 F (The directory list:) 216 619.33 T 5 F (entries) 108 607.33 T 0 F (Zero or more directory \050) 216 607.33 T 5 F (entry3) 313.14 607.33 T 0 F (\051 entries.) 349.12 607.33 T 5 F (eof) 108 595.33 T 4 F -0.67 (TRUE) 216 595.33 P 0 F -0.28 ( if the last member of) 239.99 595.33 P 5 F -0.67 (reply.entries) 326.59 595.33 P 0 F -0.28 ( is the last entry in the directory or) 404.54 595.33 P -0.35 (the list) 216 583.33 P 5 F -0.85 (reply.entries) 244.72 583.33 P 0 F -0.35 ( is empty and the cookie corresponded to the end of the) 322.68 583.33 P (directory. If) 216 571.33 T 4 F (FALSE) 266.23 571.33 T 0 F (, there may be more entries to read.) 296.22 571.33 T -0.03 (Otherwise,) 72 553.33 P 5 F -0.08 (READDIR3res.status) 118.04 553.33 P 0 F -0.03 ( contains the error on failure and) 225.98 553.33 P 5 F -0.08 (READDIR3res.resfail) 358.71 553.33 P 0 F -0.03 ( contains the fol-) 472.64 553.33 P (lowing:) 72 541.33 T 5 F (dir_attributes) 90 525.33 T 0 F (The attributes of the directory,) 216 525.33 T 5 F (dir) 340.35 525.33 T 0 F (.) 358.34 525.33 T 8 F (IMPLEMENTATION) 72 503.33 T 0 F -0.07 (In the NFS version 2 protocol, each directory entry returned included a cookie identifying a point in the directory. By) 72 483.33 P -0.59 (including this cookie in a subsequent) 72 471.33 P 4 F -1.41 (READDIR) 218.94 471.33 P 0 F -0.59 (, the client could resume the directory read at any point in the directory.) 260.92 471.33 P 0.44 (One problem with this scheme was that there was no easy way for a server to verify that a cookie was valid. If two) 72 459.33 P 4 F -1.06 (READDIR) 72 447.33 P 0 F -0.44 (s were separated by one or more operations that changed the directory in some way \050for example, reordering) 113.98 447.33 P -0.05 (or compressing it\051, it was possible that the second) 72 435.33 P 4 F -0.11 (READDIR) 273.11 435.33 P 0 F -0.05 ( could miss entries, or process entries more than once. If) 315.09 435.33 P 0.15 (the cookie was no longer usable, for example, pointing into the middle of a directory entry, the server would have to) 72 423.33 P 0.28 (either round the cookie down to the cookie of the previous entry or round it up to the cookie of the next entry in the) 72 411.33 P -0.17 (directory. Either way would possibly lead to incorrect results and the client would be unaware that any problem exist-) 72 399.33 P (ed.) 72 387.33 T 0.05 (In the NFS version 3 protocol, each) 72 367.33 P 4 F 0.13 (READDIR) 217.27 367.33 P 0 F 0.05 ( request includes both a cookie and a cookie verifier. For the first call,) 259.25 367.33 P -0.32 (both are set to) 72 355.33 P 4 F -0.76 (0) 129.58 355.33 P 0 F -0.32 (. The response includes a new cookie verifier, with a cookie per entry. For subsequent) 135.58 355.33 P 4 F -0.76 (READDIR) 477.24 355.33 P 0 F -0.32 (s, the) 519.22 355.33 P 0.5 (client must present both the cookie and the corresponding cookie verifier. If the server detects that the cookie is no) 72 343.33 P -0.52 (longer valid, the server will reject the) 72 331.33 P 4 F -1.25 (READDIR) 220.47 331.33 P 0 F -0.52 (request with the status,) 267.19 331.33 P 4 F -1.25 (NFS3ERR_BAD_COOKIE) 359.22 331.33 P 0 F -0.52 (. The client should) 467.16 331.33 P 1.37 (be careful to avoid holding directory entry cookies across operations that modify the directory contents, such as) 72 319.33 P 4 F (REMOVE) 72 307.33 T 0 F ( and) 107.98 307.33 T 4 F (CREATE) 127.41 307.33 T 0 F (.) 163.39 307.33 T 0.19 (One implementation of the cookie-verifier mechanism might be for the server to use the modification time of the di-) 72 287.33 P -0.03 (rectory. This might be overly restrictive, however. A better approach would be to record the time of the last directory) 72 275.33 P 0.7 (modification that changed the directory organization in a way that would make it impossible to reliably interpret a) 72 263.33 P (cookie. Servers in which directory cookies are always valid are free to use zero as the verifier always.) 72 251.33 T 0.54 (The server may return fewer than) 72 233.33 P 5 F 1.3 (count) 211.23 233.33 P 0 F 0.54 ( bytes of XDR-encoded entries. The) 241.22 233.33 P 5 F 1.3 (count) 391.29 233.33 P 0 F 0.54 ( specified by the client in the) 421.28 233.33 P (request should be greater than or equal to) 72 221.33 T 4 F (FSINFO) 239.65 221.33 T 5 F (dtpref) 278.13 221.33 T 0 F (.) 314.11 221.33 T 0.47 (Since UNIX clients give a special meaning to the) 72 203.33 P 5 F 1.14 (fileid) 275.85 203.33 P 0 F 0.47 ( value zero, UNIX clients should be careful to map zero) 311.83 203.33 P 5 F (fileid) 72 191.33 T 0 F ( values to some other value and servers should try to avoid sending a zero) 107.98 191.33 T 5 F (fileid) 405.27 191.33 T 0 F (.) 441.25 191.33 T FMENDPAGE %%EndPage: "52" 57 %%Page: "53" 57 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (53) 300.44 35.33 T 4 F (READDIR) 498.02 35.33 T 8 F (ERRORS) 72 713.33 T 4 F (NFS3ERR_IO) 90 697.33 T (NFS3ERR_ACCES) 90 685.33 T (NFS3ERR_NOTDIR) 90 673.33 T (NFS3ERR_BAD_COOKIE) 90 661.33 T (NFS3ERR_TOOSMALL) 90 649.33 T (NFS3ERR_STALE) 90 637.33 T (NFS3ERR_BADHANDLE) 90 625.33 T (NFS3ERR_SERVERFAULT) 90 613.33 T 8 F (SEE ALSO) 72 591.33 T 4 F (READDIRPLUS) 72 573.33 T 0 F ( on page 54 and) 137.96 573.33 T 4 F (FSINFO) 203.75 573.33 T 0 F ( on page 59.) 239.73 573.33 T FMENDPAGE %%EndPage: "53" 58 %%Page: "54" 58 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (READDIRPLUS) 72 35.33 T 2 F (54) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (17) 145.85 710.67 T (READDIRPLUS) 256.19 710.67 T 2 10 Q (READDIRPLUS: Extended read from directory) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (READDIRPLUS3res) 90 649.33 T (NFSPROC3_READDIRPLUS\050READDIRPLUS3args\051 = 17;) 90 637.33 T (struct READDIRPLUS3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (dir;) 180 601.33 T (cookie3) 108 589.33 T (cookie;) 180 589.33 T (cookieverf3) 108 577.33 T (cookieverf;) 180 577.33 T (count3) 108 565.33 T (dircount;) 180 565.33 T (count3) 108 553.33 T (maxcount;) 180 553.33 T (};) 90 541.33 T (struct entryplus3 {) 90 517.33 T (fileid3) 108 505.33 T (fileid;) 198 505.33 T (filename3) 108 493.33 T (name;) 198 493.33 T (cookie3) 108 481.33 T (cookie;) 198 481.33 T (post_op_attr) 108 469.33 T (name_attributes;) 198 469.33 T (post_op_fh3) 108 457.33 T (name_handle;) 198 457.33 T (entryplus3) 108 445.33 T (*nextentry;) 198 445.33 T (};) 90 433.33 T (struct dirlistplus3 {) 90 409.33 T (entryplus3) 108 397.33 T (*entries;) 180 397.33 T (bool) 108 385.33 T (eof;) 180 385.33 T (};) 90 373.33 T (struct READDIRPLUS3resok {) 90 349.33 T (post_op_attr) 108 337.33 T (dir_attributes;) 198 337.33 T (cookieverf3) 108 325.33 T (cookieverf;) 198 325.33 T (dirlistplus3) 108 313.33 T (reply;) 198 313.33 T (};) 90 301.33 T (struct READDIRPLUS3resfail {) 90 277.33 T (post_op_attr) 108 265.33 T (dir_attributes;) 198 265.33 T (};) 90 253.33 T (union READDIRPLUS3res switch \050nfsstat3 status\051 {) 90 229.33 T (case NFS3_OK:) 90 217.33 T (READDIRPLUS3resok) 108 205.33 T (resok;) 234 205.33 T (default:) 90 193.33 T (READDIRPLUS3resfail) 108 181.33 T (resfail;) 234 181.33 T (};) 90 169.33 T 8 F (DESCRIPTION) 72 147.33 T 0 F 0.51 (Procedure) 72 127.33 P 4 F 1.22 (READDIRPLUS) 115.53 127.33 P 0 F 0.51 ( retrieves a variable number of entries from a file system directory and returns complete) 181.49 127.33 P -0.57 (information about each along with information to allow the client to request additional directory entries in a subsequent) 72 115.33 P 4 F 0.26 (READDIRPLUS) 72 103.33 P 0 F 0.11 (.) 137.96 103.33 P 4 F 0.26 (READDIRPLUS) 143.07 103.33 P 0 F 0.11 ( differs from) 209.03 103.33 P 4 F 0.26 (READDIR) 262.38 103.33 P 0 F 0.11 ( only in the amount of information returned for each entry.) 304.35 103.33 P -0.52 (In) 72 91.33 P 4 F -1.25 (READDIR) 82.3 91.33 P 0 F -0.52 (, each entry returns the filename and the fileid. In) 124.28 91.33 P 4 F -1.25 (READDIRPLUS) 318.92 91.33 P 0 F -0.52 (, each entry returns the name, the fileid,) 384.88 91.33 P (attributes \050including the fileid\051, and file handle. On entry, the arguments in) 72 79.33 T 5 F (READDIRPLUS3args) 373.18 79.33 T 0 F ( are:) 469.13 79.33 T FMENDPAGE %%EndPage: "54" 59 %%Page: "55" 59 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (55) 300.44 35.33 T 4 F (READDIRPLUS) 474.04 35.33 T 5 F (dir) 90 713.33 T 0 F (The file handle for the directory to be read.) 216 713.33 T 5 F (cookie) 90 701.33 T 0 F 0.15 (This should be set to) 216 701.33 P 4 F 0.36 (0) 301.98 701.33 P 0 F 0.15 ( on the first request to read a directory. On subsequent re-) 307.98 701.33 P (quests, it should be a) 216 689.33 T 5 F (cookie) 302.06 689.33 T 0 F ( as returned by the server.) 338.04 689.33 T 5 F (cookieverf) 90 677.33 T 0 F 0.15 (This should be set to) 216 677.33 P 4 F 0.36 (0) 301.98 677.33 P 0 F 0.15 ( on the first request to read a directory. On subsequent re-) 307.98 677.33 P -0.48 (quests, it should be a) 216 665.33 P 5 F -1.16 (cookieverf) 299.65 665.33 P 0 F -0.48 ( as returned by the server. The) 359.62 665.33 P 5 F -1.16 (cookieverf) 480.03 665.33 P 0 F 0.28 (must match that returned by the) 216 653.33 P 4 F 0.66 (READDIRPLUS) 347.02 653.33 P 0 F 0.28 ( call in which the) 412.98 653.33 P 5 F 0.66 (cookie) 485.7 653.33 P 0 F 0.28 ( was) 521.68 653.33 P (acquired.) 216 641.33 T 5 F (dircount) 90 629.33 T 0 F 0.73 (The maximum number of bytes of directory information returned. This number) 216 629.33 P (should not include the size of the attributes and file handle portions of the result.) 216 617.33 T 5 F (maxcount) 90 605.33 T 0 F 0.5 (The maximum size of the) 216 605.33 P 5 F 1.2 (READDIRPLUS3resok) 323.14 605.33 P 0 F 0.5 ( structure, in bytes. The size) 425.09 605.33 P 3.43 (must include all XDR overhead. The server is free to return fewer than) 216 593.33 P 5 F (maxcount) 216 581.33 T 0 F ( bytes of data.) 263.97 581.33 T (On successful return,) 72 563.33 T 5 F (READDIRPLUS3res.status) 159.15 563.33 T 0 F ( is) 291.08 563.33 T 4 F (NFS3_OK) 302.74 563.33 T 0 F ( and) 344.72 563.33 T 5 F (READDIRPLUS3res.resok) 364.15 563.33 T 0 F ( contains:) 490.08 563.33 T 5 F (dir_attributes) 90 547.33 T 0 F (The attributes of the directory,) 216 547.33 T 5 F (dir) 340.35 547.33 T 0 F (.) 358.34 547.33 T 5 F (cookieverf) 90 535.33 T 0 F (The cookie verifier.) 216 535.33 T 5 F (reply) 90 523.33 T 0 F (The directory list:) 216 523.33 T 5 F (entries) 108 511.33 T 0 F (Zero or more directory \050) 216 511.33 T 5 F (entryplus3) 313.14 511.33 T 0 F (\051 entries.) 373.1 511.33 T 5 F (eof) 108 499.33 T 4 F -0.67 (TRUE) 216 499.33 P 0 F -0.28 ( if the last member of) 239.99 499.33 P 5 F -0.67 (reply.entries) 326.59 499.33 P 0 F -0.28 ( is the last entry in the directory or) 404.54 499.33 P -0.35 (the list) 216 487.33 P 5 F -0.85 (reply.entries) 244.72 487.33 P 0 F -0.35 ( is empty and the cookie corresponded to the end of the) 322.68 487.33 P (directory. If) 216 475.33 T 4 F (FALSE) 266.23 475.33 T 0 F (, there may be more entries to read.) 296.22 475.33 T -0.13 (Otherwise,) 72 457.33 P 5 F -0.3 (READDIRPLUS3res.status) 117.95 457.33 P 0 F -0.13 ( contains the error on failure and) 249.88 457.33 P 5 F -0.3 (READDIRPLUS3res.resfail) 381.94 457.33 P 0 F -0.13 ( con-) 519.87 457.33 P (tains the following:) 72 445.33 T 5 F (dir_attributes) 90 429.33 T 0 F (The attributes of the directory,) 216 429.33 T 5 F (dir) 340.35 429.33 T 0 F (.) 358.34 429.33 T 8 F (IMPLEMENTATION) 72 407.33 T 0 F -0.22 (Issues that need to be understood for this procedure include increased cache flushing activity on the client \050as new file) 72 389.33 P 0.5 (handles are returned with names which are entered into caches\051 and over-the-wire overhead versus expected subse-) 72 377.33 P 0.08 (quent) 72 365.33 P 4 F 0.19 (LOOKUP) 96.79 365.33 P 0 F 0.08 ( elimination. It is thought that this procedure may improve performance for directory browsing where) 132.77 365.33 P (attributes are always required as on the Apple Macintosh operating system and for MS-DOS.) 72 353.33 T 0.13 (The) 72 335.33 P 5 F 0.32 (dircount) 90.17 335.33 P 0 F 0.13 ( and) 138.15 335.33 P 5 F 0.32 (maxcount) 157.85 335.33 P 0 F 0.13 ( fields are included as an optimization. Consider a) 205.82 335.33 P 4 F 0.32 (READDIRPLUS) 409.67 335.33 P 0 F 0.13 ( call on a UNIX) 475.63 335.33 P -0.45 (operating system implementation for) 72 323.33 P 4 F -1.07 (1048) 220.12 323.33 P 0 F -0.45 ( bytes; the reply does not contain many entries because of the overhead due) 244.1 323.33 P 0.35 (to attributes and file handles. An alternative is to issue a) 72 311.33 P 4 F 0.83 (READDIRPLUS) 302.32 311.33 P 0 F 0.35 ( call for) 368.28 311.33 P 4 F 0.83 (8192) 402.9 311.33 P 0 F 0.35 ( bytes and then only use the) 426.89 311.33 P 0.15 (first) 72 299.33 P 4 F 0.36 (1048) 90.75 299.33 P 0 F 0.15 ( bytes of directory information. However, the server doesn\325t know that all that is needed is) 114.74 299.33 P 4 F 0.36 (1048) 481.29 299.33 P 0 F 0.15 ( bytes of) 505.28 299.33 P -0.51 (directory information \050as would be returned by) 72 287.33 P 4 F -1.22 (READDIR) 258.57 287.33 P 0 F -0.51 (\051. It sees the) 300.54 287.33 P 4 F -1.22 (8192) 349.3 287.33 P 0 F -0.51 ( byte request and issues a) 373.28 287.33 P 5 F -1.22 (VOP_READDIR) 474.04 287.33 P 0 F -0.21 (for) 72 275.33 P 4 F -0.5 (8192) 85.94 275.33 P 0 F -0.21 ( bytes. It then steps through all of those directory entries, obtaining attributes and file handles for each entry.) 109.93 275.33 P -0.22 (When it encodes the result, the server only encodes until it gets) 72 263.33 P 4 F -0.51 (8192) 324.52 263.33 P 0 F -0.22 ( bytes of results which include the attributes and) 348.51 263.33 P -0.26 (file handles. Thus, it has done a larger) 72 251.33 P 5 F -0.62 (VOP_READDIR) 224.82 251.33 P 0 F -0.26 ( and many more attribute fetches than it needed to. The ratio of) 290.79 251.33 P -0.01 (the directory entry size to the size of the attributes plus the size of the file handle is usually at least) 72 239.33 P 4 F -0.03 (8) 467.83 239.33 P 0 F -0.01 ( to) 473.83 239.33 P 4 F -0.03 (1) 486.58 239.33 P 0 F -0.01 (. The server) 492.57 239.33 P (has done much more work than it needed to.) 72 227.33 T 0.41 (The solution to this problem is for the client to provide two counts to the server. The first is the number of bytes of) 72 209.33 P -0.14 (directory information that the client really wants,) 72 197.33 P 5 F -0.33 (dircount) 269.79 197.33 P 0 F -0.14 (. The second is the maximum number of bytes in the re-) 317.77 197.33 P 0.2 (sult, including the attributes and file handles,) 72 185.33 P 5 F 0.49 (maxcount) 255.81 185.33 P 0 F 0.2 (. Thus, the server will issue a) 303.79 185.33 P 5 F 0.49 (VOP_READDIR) 424.29 185.33 P 0 F 0.2 ( for only the) 490.26 185.33 P 0.94 (number of bytes that the client really wants to get, not an inflated number. This should help to reduce the size of) 72 173.33 P 5 F 1.42 (VOP_READDIR) 72 161.33 P 0 F 0.59 ( requests on the server, thus reducing the amount of work done there, and to reduce the number of) 137.96 161.33 P 5 F (VOP_LOOKUP) 72 149.33 T 0 F (,) 131.97 149.33 T 5 F (VOP_GETATTR) 136.96 149.33 T 0 F (, and other calls done by the server to construct attributes and file handles.) 202.93 149.33 T FMENDPAGE %%EndPage: "55" 60 %%Page: "56" 60 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (READDIRPLUS) 72 35.33 T 2 F (56) 300.44 35.33 T (Version 3) 495.01 35.33 T 8 F (ERRORS) 72 713.33 T 4 F (NFS3ERR_IO) 90 697.33 T (NFS3ERR_ACCES) 90 685.33 T (NFS3ERR_NOTDIR) 90 673.33 T (NFS3ERR_BAD_COOKIE) 90 661.33 T (NFS3ERR_TOOSMALL) 90 649.33 T (NFS3ERR_STALE) 90 637.33 T (NFS3ERR_BADHANDLE) 90 625.33 T (NFS3ERR_NOTSUPP) 90 613.33 T (NFS3ERR_SERVERFAULT) 90 601.33 T 8 F (SEE ALSO) 72 579.33 T 4 F (READDIR) 72 561.33 T 0 F ( on page 51) 113.98 561.33 T (.) 160.33 561.33 T FMENDPAGE %%EndPage: "56" 61 %%Page: "57" 61 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (57) 300.44 35.33 T 4 F (FSSTAT) 504.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (18) 145.85 710.67 T (FSSTAT) 280.28 710.67 T 2 10 Q (FSSTAT: Get dynamic file system information) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (FSSTAT3res) 90 649.33 T (NFSPROC3_FSSTAT\050FSSTAT3args\051 = 18;) 90 637.33 T (struct FSSTAT3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (fsroot;) 162 601.33 T (};) 90 589.33 T (struct FSSTAT3resok {) 90 565.33 T (post_op_attr) 108 553.33 T (obj_attributes;) 198 553.33 T (size3) 108 541.33 T (tbytes;) 198 541.33 T (size3) 108 529.33 T (fbytes;) 198 529.33 T (size3) 108 517.33 T (abytes;) 198 517.33 T (size3) 108 505.33 T (tfiles;) 198 505.33 T (size3) 108 493.33 T (ffiles;) 198 493.33 T (size3) 108 481.33 T (afiles;) 198 481.33 T (uint32) 108 469.33 T (invarsec;) 198 469.33 T (};) 90 457.33 T (struct FSSTAT3resfail {) 90 433.33 T (post_op_attr) 108 421.33 T (obj_attributes;) 198 421.33 T (};) 90 409.33 T (union FSSTAT3res switch \050nfsstat3 status\051 {) 90 385.33 T (case NFS3_OK:) 90 373.33 T (FSSTAT3resok) 108 361.33 T (resok;) 216.72 361.33 T (default:) 90 349.33 T (FSSTAT3resfail) 108 337.33 T (resfail;) 216.72 337.33 T (};) 90 325.33 T 8 F (DESCRIPTION) 72 303.33 T 0 F (Procedure) 72 283.33 T 4 F (FSSTAT) 115.02 283.33 T 0 F ( retrieves volatile file system state information. On entry, the arguments in) 151 283.33 T 5 F (FSSTAT3args) 451.35 283.33 T 0 F ( are:) 517.32 283.33 T 5 F (fsroot) 90 271.33 T 0 F -0.13 (A file handle identifying a object in the file system. This is normally a file handle) 216 271.33 P -0.31 (for a mount point for a file system, as originally obtained from the) 216 259.33 P 4 F -0.75 (MOUNT) 479.53 259.33 P 0 F -0.31 ( service) 509.51 259.33 P (on the server.) 216 247.33 T (On successful return,) 72 229.33 T 5 F (FSSTAT3res.status) 159.15 229.33 T 0 F ( is) 261.1 229.33 T 4 F (NFS3_OK) 272.76 229.33 T 0 F ( and) 314.74 229.33 T 5 F (FSSTAT3res.resok) 334.17 229.33 T 0 F ( contains:) 430.11 229.33 T 5 F (obj_attributes) 90 213.33 T 0 F (The attributes of the file system object specified in) 216 213.33 T 5 F (fsroot) 421.14 213.33 T 0 F (.) 457.12 213.33 T 5 F (tbytes) 90 201.33 T 0 F (The total size, in bytes, of the file system.) 216 201.33 T 5 F (fbytes) 90 189.33 T 0 F (The amount of free space, in bytes, in the file system.) 216 189.33 T 5 F (abytes) 90 177.33 T 0 F 0.03 (The amount of free space, in bytes, available to the user identified by the authen-) 216 177.33 P 0.71 (tication information in the RPC. \050This reflects space that is reserved by the file) 216 165.33 P (system; it does not reflect any quota system implemented by the server.\051) 216 153.33 T 5 F (tfiles) 90 141.33 T 0 F -0.4 (The total number of file slots in the file system. \050On a UNIX server, this often cor-) 216 141.33 P (responds to the number of inodes configured.\051) 216 129.33 T 5 F (ffiles) 90 117.33 T 0 F (The number of free file slots in the file system.) 216 117.33 T 5 F (afiles) 90 105.33 T 0 F -0.33 (The number of free file slots that are available to the user corresponding to the au-) 216 105.33 P 0.51 (thentication information in the RPC. \050This reflects slots that are reserved by the) 216 93.33 P (file system; it does not reflect any quota system implemented by the server.\051) 216 81.33 T FMENDPAGE %%EndPage: "57" 62 %%Page: "58" 62 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (FSSTAT) 72 35.33 T 2 F (58) 300.44 35.33 T (Version 3) 495.01 35.33 T 5 F (invarsec) 90 713.33 T 0 F -0.51 (A measure of file system volatility: this is the number of seconds for which the file) 216 713.33 P 0.47 (system is not expected to change. For a volatile, frequently updated file system,) 216 701.33 P 0.43 (this will be) 216 689.33 P 4 F 1.04 (0) 264.23 689.33 P 0 F 0.43 (. For an immutable file system, such as a CD-ROM, this would be) 270.22 689.33 P 0.56 (the largest unsigned integer. For file systems that are infrequently modified, for) 216 677.33 P -0.05 (example, one containing local executable programs and on-line documentation, a) 216 665.33 P -0.31 (value corresponding to a few hours or days might be used. The client may use this) 216 653.33 P -0.08 (as a hint in tuning its cache management. Note however, this measure is assumed) 216 641.33 P (to be dynamic and may change at any time.) 216 629.33 T -0.31 (Otherwise,) 72 611.33 P 5 F -0.73 (FSSTAT3res.status) 117.77 611.33 P 0 F -0.31 ( contains the error on failure and) 219.71 611.33 P 5 F -0.73 (FSSTAT3res.resfail) 350.53 611.33 P 0 F -0.31 ( contains the follow-) 458.47 611.33 P (ing:) 72 599.33 T 5 F (obj_attributes) 90 583.33 T 0 F (The attributes of the file system object specified in) 216 583.33 T 5 F (fsroot) 421.14 583.33 T 0 F (.) 457.12 583.33 T 8 F (IMPLEMENTATION) 72 561.33 T 0 F 0.43 (Not all implementations can support the entire list of attributes. It is expected that servers will make a best effort at) 72 543.33 P (supporting all the attributes.) 72 531.33 T 8 F (ERRORS) 72 509.33 T 4 F (NFS3ERR_IO) 90 493.33 T (NFS3ERR_STALE) 90 481.33 T (NFS3ERR_BADHANDLE) 90 469.33 T (NFS3ERR_SERVERFAULT) 90 457.33 T 8 F (SEE ALSO) 72 435.33 T 4 F (FSINFO) 72 417.33 T 0 F ( on page 59) 107.98 417.33 T (.) 154.34 417.33 T FMENDPAGE %%EndPage: "58" 63 %%Page: "59" 63 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (59) 300.44 35.33 T 4 F (FSINFO) 504.02 35.33 T 6 14 Q (Procedure) 72 710.67 T (19) 145.85 710.67 T (FSINFO) 281.07 710.67 T 2 10 Q (FSINFO: Get static) 72 687.33 T (file system) 163.08 687.33 T ( Information) 214.74 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (FSINFO3res) 90 649.33 T (NFSPROC3_FSINFO\050FSINFO3args\051 = 19;) 90 637.33 T (const FSF3_LINK) 90 613.33 T (= 0x0001;) 234 613.33 T (const FSF3_SYMLINK) 90 601.33 T (= 0x0002;) 234 601.33 T (const FSF3_HOMOGENEOUS) 90 589.33 T (= 0x0008;) 234 589.33 T (const FSF3_CANSETTIME) 90 577.33 T (= 0x0010;) 234 577.33 T (struct FSINFOargs {) 90 553.33 T (nfs_fh3) 108 541.33 T (fsroot;) 162 541.33 T (};) 90 529.33 T (struct FSINFO3resok {) 90 505.33 T (post_op_attr) 108 493.33 T (obj_attributes;) 198 493.33 T (uint32) 108 481.33 T (rtmax;) 198 481.33 T (uint32) 108 469.33 T (rtpref;) 198 469.33 T (uint32) 108 457.33 T (rtmult;) 198 457.33 T (uint32) 108 445.33 T (wtmax;) 198 445.33 T (uint32) 108 433.33 T (wtpref;) 198 433.33 T (uint32) 108 421.33 T (wtmult;) 198 421.33 T (uint32) 108 409.33 T (dtpref;) 198 409.33 T (size3) 108 397.33 T (maxfilesize;) 198 397.33 T (nfstime3) 108 385.33 T (time_delta;) 198 385.33 T (uint32) 108 373.33 T (properties;) 198 373.33 T (};) 90 361.33 T (struct FSINFO3resfail {) 90 337.33 T (post_op_attr) 108 325.33 T (obj_attributes;) 198 325.33 T (};) 90 313.33 T (union FSINFO3res switch \050nfsstat3 status\051 {) 90 289.33 T (case NFS3_OK:) 90 277.33 T (FSINFO3resok) 108 265.33 T (resok;) 216.72 265.33 T (default:) 90 253.33 T (FSINFO3resfail) 108 241.33 T (resfail;) 216.72 241.33 T (};) 90 229.33 T 8 F (DESCRIPTION) 72 207.33 T 0 F -0.19 (Procedure) 72 187.33 P 4 F -0.46 (FSINFO) 114.82 187.33 P 0 F -0.19 ( retrieves nonvolatile file system state information and general information about the NFS version) 150.8 187.33 P (3 protocol server implementation. On entry, the arguments in) 72 175.33 T 5 F (FSINFO3args) 319.33 175.33 T 0 F ( are:) 385.3 175.33 T 5 F (fsroot) 90 163.33 T 0 F -0.24 (A file handle identifying a file object. Normal usage is to provide a file handle for) 216 163.33 P -0.19 (a mount point for a file system, as originally obtained from the) 216 151.33 P 4 F -0.47 (MOUNT) 467.11 151.33 P 0 F -0.19 ( service on) 497.09 151.33 P (the server.) 216 139.33 T (On successful return,) 72 121.33 T 5 F (FSINFO3res.status) 159.15 121.33 T 0 F ( is) 261.1 121.33 T 4 F (NFS3_OK) 272.76 121.33 T 0 F ( and) 314.74 121.33 T 5 F (FSINFO3res.resok) 334.17 121.33 T 0 F ( contains:) 430.11 121.33 T 5 F (obj_attributes) 90 105.33 T 0 F (The attributes of the file system object specified in) 216 105.33 T 5 F (fsroot) 421.14 105.33 T 0 F (.) 457.12 105.33 T 5 F (rtmax) 90 93.33 T 0 F -0.49 (The maximum size in bytes of a) 216 93.33 P 4 F -1.17 (READ) 343.33 93.33 P 0 F -0.49 ( request supported by the server. Any) 367.32 93.33 P 4 F -1.17 (READ) 516.01 93.33 P 0 F 0.26 (with a number greater than) 216 81.33 P 5 F 0.63 (rtmax) 327.51 81.33 P 0 F 0.26 ( will result in a short read of) 357.49 81.33 P 5 F 0.63 (rtmax) 475.07 81.33 P 0 F 0.26 ( bytes or) 505.05 81.33 P FMENDPAGE %%EndPage: "59" 64 %%Page: "60" 64 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (FSINFO) 72 35.33 T 2 F (60) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F (less.) 216 713.33 T 5 F (rtpref) 90 701.33 T 0 F 0.23 (The preferred size of a) 216 701.33 P 4 F 0.56 (READ) 310.14 701.33 P 0 F 0.23 ( request. This should be the same as) 334.12 701.33 P 5 F 0.56 (rtmax) 482.3 701.33 P 0 F 0.23 ( unless) 512.28 701.33 P (there is a clear benefit in performance or efficiency.) 216 689.33 T 5 F (rtmult) 90 677.33 T 0 F (The suggested multiple for the size of a) 216 677.33 T 4 F (READ) 376.44 677.33 T 0 F ( request.) 400.43 677.33 T 5 F (wtmax) 90 665.33 T 0 F 0.56 (The maximum size of a) 216 665.33 P 4 F 1.35 (WRITE) 315.68 665.33 P 0 F 0.56 ( request supported by the server. In general, the) 345.67 665.33 P 0.3 (client is limited by) 216 653.33 P 5 F 0.72 (wtmax) 294.39 653.33 P 0 F 0.3 ( since there is no guarantee that a server can handle a) 324.38 653.33 P 0.44 (larger write. Any) 216 641.33 P 4 F 1.06 (WRITE) 288.37 641.33 P 0 F 0.44 ( with a count greater than) 318.36 641.33 P 5 F 1.06 (wtmax) 425.36 641.33 P 0 F 0.44 ( will result in a short) 455.34 641.33 P (write of at most) 216 629.33 T 5 F (wtmax) 281.51 629.33 T 0 F ( bytes.) 311.5 629.33 T 5 F (wtpref) 90 617.33 T 0 F -0.19 (The preferred size of a) 216 617.33 P 4 F -0.46 (WRITE) 307.99 617.33 P 0 F -0.19 ( request. This should be the same as) 337.98 617.33 P 5 F -0.46 (wtmax) 482.72 617.33 P 0 F -0.19 ( unless) 512.71 617.33 P (there is a clear benefit in performance or efficiency.) 216 605.33 T 5 F (wtmult) 90 593.33 T 0 F (The suggested multiple for the size of a) 216 593.33 T 4 F (WRITE) 376.44 593.33 T 0 F ( request.) 406.42 593.33 T 5 F (dtpref) 90 581.33 T 0 F (The preferred size of a) 216 581.33 T 4 F (READDIR) 308.96 581.33 T 0 F ( request.) 350.94 581.33 T 5 F (maxfilesize) 90 569.33 T 0 F (The maximum size of a file on the file system.) 216 569.33 T 5 F (time_delta) 90 557.33 T 0 F 0.09 (The server time granularity. When setting a file time using) 216 557.33 P 4 F 0.22 (SETATTR) 453.71 557.33 P 0 F 0.09 (, the server) 495.69 557.33 P -0.16 (guarantees only to preserve times to this accuracy. If this is {) 216 545.33 P 4 F -0.38 (0) 458.34 545.33 P 0 F -0.16 (,) 464.34 545.33 P 4 F -0.38 (1) 469.18 545.33 P 0 F -0.16 (}, the server can) 475.18 545.33 P -0.44 (support nanosecond times, {) 216 533.33 P 4 F -1.04 (0) 328.31 533.33 P 0 F -0.44 (,) 334.31 533.33 P 4 F -1.04 (1000000) 338.87 533.33 P 0 F -0.44 (} denotes millisecond precision, and {) 380.85 533.33 P 4 F -1.04 (1) 531.5 533.33 P 0 F -0.44 (,) 537.5 533.33 P 4 F (0) 216 521.33 T 0 F (} indicates that times are accurate only to the nearest second.) 222 521.33 T 5 F (properties) 90 509.33 T 0 F (A bit mask of file system properties. The following values are defined:) 216 509.33 T 5 F (FSF_LINK) 108 497.33 T 0 F (If this bit is) 216 497.33 T 4 F (1) 264.31 497.33 T 0 F ( \050) 270.31 497.33 T 4 F (TRUE) 276.14 497.33 T 0 F (\051, the file system supports hard links.) 300.12 497.33 T 5 F (FSF_SYMLINK) 108 485.33 T 0 F (If this bit is) 216 485.33 T 4 F (1) 264.31 485.33 T 0 F ( \050) 270.31 485.33 T 4 F (TRUE) 276.14 485.33 T 0 F (\051, the file system supports symbolic links.) 300.12 485.33 T 5 F (FSF_HOMOGENEOUS) 108 473.33 T 0 F -0.33 (If this bit is) 216 473.33 P 4 F -0.79 (1) 262.99 473.33 P 0 F -0.33 ( \050) 268.99 473.33 P 4 F -0.79 (TRUE) 274.49 473.33 P 0 F -0.33 (\051, the information returned by) 298.47 473.33 P 4 F -0.79 (PATHCONF) 417.85 473.33 P 0 F -0.33 ( is identical for ev-) 465.82 473.33 P 0.48 (ery file and directory in the file system. If it is) 216 461.33 P 4 F 1.15 (0) 407.81 461.33 P 0 F 0.48 ( \050) 413.8 461.33 P 4 F 1.15 (FALSE) 420.11 461.33 P 0 F 0.48 (\051, the client should re-) 450.09 461.33 P (trieve) 216 449.33 T 4 F (PATHCONF) 241.26 449.33 T 0 F ( information for each file and directory as required.) 289.23 449.33 T 5 F (FSF_CANSETTIME) 108 437.33 T 0 F 0.2 (If this bit is) 216 437.33 P 4 F 0.48 (1) 265.11 437.33 P 0 F 0.2 ( \050) 271.11 437.33 P 4 F 0.48 (TRUE) 277.14 437.33 P 0 F 0.2 (\051, the server will set the times for a file via) 301.12 437.33 P 4 F 0.48 (SETATTR) 475.42 437.33 P 0 F 0.2 ( if re-) 517.4 437.33 P -0.5 (quested \050to the accuracy indicated by) 216 425.33 P 5 F -1.2 (time_delta) 364 425.33 P 0 F -0.5 (\051. If it is) 423.96 425.33 P 4 F -1.2 (0) 456.67 425.33 P 0 F -0.5 ( \050) 462.67 425.33 P 4 F -1.2 (FALSE) 468 425.33 P 0 F -0.5 (\051, the serv-) 497.98 425.33 P (er cannot set times as requested.) 216 413.33 T -0.31 (Otherwise,) 72 395.33 P 5 F -0.73 (FSINFO3res.status) 117.77 395.33 P 0 F -0.31 ( contains the error on failure and) 219.71 395.33 P 5 F -0.73 (FSINFO3res.resfail) 350.53 395.33 P 0 F -0.31 ( contains the follow-) 458.47 395.33 P (ing:) 72 383.33 T 5 F (attributes) 90 367.33 T 0 F (The attributes of the file system object specified in) 216 367.33 T 5 F (fsroot) 421.14 367.33 T 0 F (.) 457.12 367.33 T 8 F (IMPLEMENTATION) 72 345.33 T 0 F 0.26 (Not all implementations can support the entire list of attributes. It is expected that a server will make a best effort at) 72 327.33 P (supporting all the attributes.) 72 315.33 T 0.04 (The file handle provided is expected to be the file handle of the file system root, as returned to the) 72 297.33 P 4 F 0.1 (MOUNT) 467.23 297.33 P 0 F 0.04 ( operation.) 497.21 297.33 P -0.15 (Since mounts may occur anywhere within an exported tree, the server should expect) 72 285.33 P 4 F -0.36 (FSINFO) 409.26 285.33 P 0 F -0.15 ( requests specifying file) 445.24 285.33 P 0.2 (handles within the exported file system. A server may export different types of file systems with different attributes) 72 273.33 P 0.53 (returned to the) 72 261.33 P 4 F 1.28 (FSINFO) 134.39 261.33 P 0 F 0.53 ( call. The client should retrieve) 170.37 261.33 P 4 F 1.28 (FSINFO) 300.42 261.33 P 0 F 0.53 ( information for each mount completed. Though a) 336.4 261.33 P -0.07 (server may return different) 72 249.33 P 4 F -0.17 (FSINFO) 181.62 249.33 P 0 F -0.07 ( information for different files within a file system, there is no requirement that a) 217.6 249.33 P (client obtain) 72 237.33 T 4 F (FSINFO) 124.19 237.33 T 0 F ( information for other than the file handle returned at mount.) 160.17 237.33 T 0.03 (The) 72 219.33 P 5 F 0.07 (maxfilesize) 90.07 219.33 P 0 F 0.03 ( field determines whether a server\325s particular file system uses) 156.04 219.33 P 4 F 0.07 (32) 408.36 219.33 P 0 F 0.03 ( bit sizes and offsets or) 420.36 219.33 P 4 F 0.07 (64) 514.92 219.33 P 0 F 0.03 ( bit) 526.92 219.33 P (file sizes and offsets. This may affect a client\325s processing.) 72 207.33 T 0.57 (The preferred sizes for requests are nominally tied to an exported file system mounted by a client. A surmountable) 72 189.33 P 0.22 (issue arises in that the transfer size for an NFS version 3 protocol request is not only dependent on characteristics of) 72 177.33 P 0.12 (the file system but also on characteristics of the network interface, particularly the maximum transfer unit \050MTU\051. A) 72 165.33 P 0.23 (server implementation can advertise different transfer sizes \050for the fields,) 72 153.33 P 5 F 0.56 (rtmax) 372.71 153.33 P 0 F 0.23 (,) 402.7 153.33 P 5 F 0.56 (rtpref) 407.93 153.33 P 0 F 0.23 (,) 443.91 153.33 P 5 F 0.56 (wtmax) 449.14 153.33 P 0 F 0.23 (,) 479.12 153.33 P 5 F 0.56 (wtpref) 484.36 153.33 P 0 F 0.23 (, and) 520.34 153.33 P 5 F (dtpref) 72 141.33 T 0 F (\051 depending on the interface on which the) 107.98 141.33 T 4 F (FSINFO) 276.74 141.33 T 0 F ( request is received. This is an implementation issue.) 312.72 141.33 T 8 F (ERRORS) 72 119.33 T 4 F (NFS3ERR_STALE) 90 103.33 T (NFS3ERR_BADHANDLE) 90 91.33 T (NFS3ERR_SERVERFAULT) 90 79.33 T FMENDPAGE %%EndPage: "60" 65 %%Page: "61" 65 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (61) 300.44 35.33 T 4 F (FSINFO) 504.02 35.33 T 8 F (SEE ALSO) 72 713.33 T 4 F -0.85 (READLINK) 72 695.33 P 0 F -0.35 ( on page 26) 119.97 695.33 P -0.35 (,) 165.27 695.33 P 4 F -0.85 (WRITE) 169.91 695.33 P 0 F -0.35 ( on page 30) 199.89 695.33 P -0.35 (,) 245.19 695.33 P 4 F -0.85 (READDIR) 249.83 695.33 P 0 F -0.35 ( on page 51) 291.81 695.33 P -0.35 (,) 337.1 695.33 P 4 F -0.85 (FSSTAT) 341.74 695.33 P 0 F -0.35 ( on page 57) 377.72 695.33 P -0.35 (, and) 423.02 695.33 P 4 F -0.85 (PATHCONF) 444.23 695.33 P 0 F -0.35 ( on page 62) 492.21 695.33 P -0.35 (.) 537.5 695.33 P FMENDPAGE %%EndPage: "61" 66 %%Page: "62" 66 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (PATHCONF) 72 35.33 T 2 F (62) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (20) 145.85 710.67 T (PATHCONF) 267.46 710.67 T 2 10 Q (PATHCONF: Retrieve POSIX information) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (PATHCONF3res) 90 649.33 T (NFSPROC3_PATHCONF\050PATHCONF3args\051 = 20;) 90 637.33 T (struct PATHCONF3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (object;) 162 601.33 T (};) 90 589.33 T (struct PATHCONF3resok {) 90 565.33 T (post_op_attr) 108 553.33 T (obj_attributes;) 198 553.33 T (uint32) 108 541.33 T (linkmax;) 198 541.33 T (uint32) 108 529.33 T (name_max;) 198 529.33 T (bool) 108 517.33 T (no_trunc;) 198 517.33 T (bool) 108 505.33 T (chown_restricted;) 198 505.33 T (bool) 108 493.33 T (case_insensitive;) 198 493.33 T (bool) 108 481.33 T (case_preserving;) 198 481.33 T (};) 90 469.33 T (struct PATHCONF3resfail {) 90 445.33 T (post_op_attr) 108 433.33 T (obj_attributes;) 198 433.33 T (};) 90 421.33 T (union PATHCONF3res switch \050nfsstat3 status\051 {) 90 397.33 T (case NFS3_OK:) 90 385.33 T (PATHCONF3resok) 108 373.33 T (resok;) 216.72 373.33 T (default:) 90 361.33 T (PATHCONF3resfail) 108 349.33 T (resfail;) 216.72 349.33 T (};) 90 337.33 T 8 F (DESCRIPTION) 72 315.33 T 0 F -0.17 (Procedure) 72 297.33 P 4 F -0.41 (PATHCONF) 114.85 297.33 P 0 F -0.17 ( retrieves the) 162.82 297.33 P 3 F -0.17 (pathconf) 216.43 297.33 P 0 F -0.17 ( information for a file or directory. If the) 251.41 297.33 P 4 F -0.41 (FSF_HOMOGENEOUS) 414.74 297.33 P 0 F -0.17 ( bit is set) 504.69 297.33 P 0.58 (in) 72 285.33 P 5 F 1.4 (FSFINFO3resok.properties) 82.86 285.33 P 0 F 0.58 (, the pathconf information will be the same for all files and directories in the) 226.78 285.33 P (exported file system in which this file or directory resides. On entry, the arguments in) 72 273.33 T 5 F (PATHCONF3args) 417.04 273.33 T 0 F ( are:) 495 273.33 T 5 F (object) 90 257.33 T 0 F (The file handle for the file system object.) 216 257.33 T (On successful return,) 72 239.33 T 5 F (PATHCONF3res.status) 159.15 239.33 T 0 F ( is) 273.09 239.33 T 4 F (NFS3_OK) 284.75 239.33 T 0 F ( and) 326.73 239.33 T 5 F (PATHCONF3res.resok) 346.16 239.33 T 0 F ( contains:) 454.1 239.33 T 5 F (obj_attributes) 90 223.33 T 0 F (The attributes of the object specified by) 216 223.33 T 5 F (object) 377.27 223.33 T 0 F (.) 413.25 223.33 T 5 F (linkmax) 90 211.33 T 0 F (The maximum number of hard links to an object.) 216 211.33 T 5 F (name_max) 90 199.33 T 0 F (The maximum length of a component of a filename.) 216 199.33 T 5 F (no_trunc) 90 187.33 T 0 F 1.81 (If) 216 187.33 P 4 F 4.35 (TRUE) 226.97 187.33 P 0 F 1.81 (, the server will reject any request that includes a name longer than) 250.95 187.33 P 5 F 2.74 (name_max) 216 175.33 P 0 F 1.14 ( with the error,) 263.97 175.33 P 4 F 2.74 (NFS3ERR_NAMETOOLONG) 330.44 175.33 P 0 F 1.14 (. If) 444.38 175.33 P 4 F 2.74 (FALSE) 460.82 175.33 P 0 F 1.14 (, any length) 490.8 175.33 P (name over) 216 163.33 T 5 F (name_max) 260.41 163.33 T 0 F ( bytes will be silently truncated to) 308.38 163.33 T 5 F (name_max) 446.35 163.33 T 0 F ( bytes.) 494.33 163.33 T 5 F (chown_restricted) 90 151.33 T 0 F -0.28 (If) 216 151.33 P 4 F -0.67 (TRUE) 224.88 151.33 P 0 F -0.28 (, the server will reject any request to change either the owner or the group) 248.86 151.33 P (associated with a file if the caller is not the privileged user. \050Uid) 216 139.33 T 4 F (0) 475.26 139.33 T 0 F (.\051) 481.25 139.33 T 5 F (case_insensitive) 90 127.33 T 0 F -0.28 (If) 216 127.33 P 4 F -0.68 (TRUE) 224.87 127.33 P 0 F -0.28 (, the server file system does not distinguish case when interpreting filena-) 248.86 127.33 P (mes.) 216 115.33 T 5 F (case_preserving) 90 103.33 T 0 F -0.44 (If) 216 103.33 P 4 F -1.05 (TRUE) 224.72 103.33 P 0 F -0.44 (, the server file system will preserve the case of a name during a) 248.7 103.33 P 4 F -1.05 (CREATE) 501.52 103.33 P 0 F -0.44 (,) 537.5 103.33 P 4 F (MKDIR) 216 91.33 T 0 F (,) 245.98 91.33 T 4 F (MKNOD) 250.98 91.33 T 0 F (,) 280.96 91.33 T 4 F (SYMLINK) 285.96 91.33 T 0 F (,) 327.94 91.33 T 4 F (RENAME) 332.94 91.33 T 0 F (, or) 368.92 91.33 T 4 F (LINK) 384.74 91.33 T 0 F ( operation.) 408.72 91.33 T FMENDPAGE %%EndPage: "62" 67 %%Page: "63" 67 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (63) 300.44 35.33 T 4 F (PATHCONF) 492.03 35.33 T 0 F 0.46 (Otherwise,) 72 713.33 P 5 F 1.1 (PATHCONF3res.status) 118.53 713.33 P 0 F 0.46 ( contains the error on failure and) 232.47 713.33 P 5 F 1.1 (PATHCONF3res.resfail) 368.63 713.33 P 0 F 0.46 ( contains the) 488.56 713.33 P (following:) 72 701.33 T 5 F (obj_attributes) 90 685.33 T 0 F (The attributes of the object specified by) 216 685.33 T 5 F (object) 377.27 685.33 T 0 F (.) 413.25 685.33 T 8 F (IMPLEMENTATION) 72 663.33 T 0 F -0.33 (In some implementations of the NFS version 2 protocol,) 72 645.33 P 3 F -0.33 (pathconf) 296.67 645.33 P 0 F -0.33 ( information was obtained at mount time through the) 331.65 645.33 P (MOUNT protocol. The proper place to obtain it, is as here, in the NFS version 3 protocol itself.) 72 633.33 T 8 F (ERRORS) 72 611.33 T 4 F (NFS3ERR_STALE) 90 595.33 T (NFS3ERR_BADHANDLE) 90 583.33 T (NFS3ERR_SERVERFAULT) 90 571.33 T 8 F (SEE ALSO) 72 549.33 T 4 F 0.16 (LOOKUP) 72 531.33 P 0 F 0.07 ( on page 22,) 107.98 531.33 P 4 F 0.16 (CREATE) 159.6 531.33 P 0 F 0.07 ( on page 33,) 195.58 531.33 P 4 F 0.16 (MKDIR) 247.21 531.33 P 0 F 0.07 ( on page 36,) 277.19 531.33 P 4 F 0.16 (SYMLINK) 328.81 531.33 P 0 F 0.07 ( on page 38,) 370.79 531.33 P 4 F 0.16 (MKNOD) 422.41 531.33 P 0 F 0.07 ( on page 40,) 452.4 531.33 P 4 F 0.16 (RENAME) 504.02 531.33 P 0 F (on page 47,) 72 519.33 T 4 F (LINK) 120.85 519.33 T 0 F ( on page 49, and) 144.84 519.33 T 4 F (FSINFO) 213.12 519.33 T 0 F ( on page 59.) 249.1 519.33 T FMENDPAGE %%EndPage: "63" 68 %%Page: "64" 68 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (COMMIT) 72 35.33 T 2 F (64) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 14 Q (Procedure) 72 710.67 T (21) 145.85 710.67 T (COMMIT) 275.63 710.67 T 2 10 Q (COMMIT: Commit cached data on a server to stable storage) 72 687.33 T 8 F (SYNOPSIS) 72 665.33 T 4 F (COMMIT3res) 90 649.33 T (NFSPROC3_COMMIT\050COMMIT3args\051 = 21;) 90 637.33 T (struct COMMIT3args {) 90 613.33 T (nfs_fh3) 108 601.33 T (file;) 180 601.33 T (offset3) 108 589.33 T (offset;) 180 589.33 T (count3) 108 577.33 T (count;) 180 577.33 T (};) 90 565.33 T (struct COMMIT3resok {) 90 541.33 T (wcc_data) 108 529.33 T (file_wcc;) 180 529.33 T (writeverf3) 108 517.33 T (verf;) 180 517.33 T (};) 90 505.33 T (struct COMMIT3resfail {) 90 481.33 T (wcc_data) 108 469.33 T (file_wcc;) 180 469.33 T (};) 90 457.33 T (union COMMIT3res switch \050nfsstat3 status\051 {) 90 433.33 T (case NFS3_OK:) 90 421.33 T (COMMIT3resok) 108 409.33 T (resok;) 198 409.33 T (default:) 90 397.33 T (COMMIT3resfail) 108 385.33 T (resfail;) 198 385.33 T (};) 90 373.33 T 8 F (DESCRIPTION) 72 339.33 T 0 F 0.22 (Procedure) 72 321.33 P 4 F 0.53 (COMMIT) 115.24 321.33 P 0 F 0.22 ( forces or flushes data to stable storage that was previously written with a) 151.22 321.33 P 4 F 0.53 (WRITE) 450.19 321.33 P 0 F 0.22 ( procedure call) 480.17 321.33 P (with the) 72 309.33 T 5 F (stable) 106.98 309.33 T 0 F ( field set to) 142.96 309.33 T 4 F (UNSTABLE) 190.15 309.33 T 0 F (. On entry, the arguments in) 238.13 309.33 T 5 F (COMMIT3args) 352.5 309.33 T 0 F ( are:) 418.46 309.33 T 5 F (file) 90 293.33 T 0 F 0.17 (The file handle for the file to which data is to be flushed \050committed\051. This must) 216 293.33 P (identify a file system object of type,) 216 281.33 T 4 F (NF3REG) 362.57 281.33 T 0 F (.) 398.55 281.33 T 5 F (offset) 90 269.33 T 0 F -0.37 (The position within the file at which the flush is to begin. An) 216 269.33 P 5 F -0.88 (offset) 457.76 269.33 P 0 F -0.37 ( of) 493.74 269.33 P 4 F -0.88 (0) 506.33 269.33 P 0 F -0.37 ( means) 512.33 269.33 P (to flush data starting at the beginning of the file.) 216 257.33 T 5 F (count) 90 245.33 T 0 F -0.05 (The number of bytes of data to flush. If) 216 245.33 P 5 F -0.12 (count) 375.44 245.33 P 0 F -0.05 ( is) 405.42 245.33 P 4 F -0.12 (0) 416.98 245.33 P 0 F -0.05 (, a flush from) 422.98 245.33 P 5 F -0.12 (offset) 479.13 245.33 P 0 F -0.05 ( to the) 515.11 245.33 P (end of file is done.) 216 233.33 T (On successful return,) 72 215.33 T 5 F (COMMIT3res.status) 159.15 215.33 T 0 F ( is) 261.1 215.33 T 4 F (NFS3_OK) 272.76 215.33 T 0 F ( and) 314.74 215.33 T 5 F (COMMIT3res.resok) 334.17 215.33 T 0 F ( contains:) 430.11 215.33 T 5 F (file_wcc) 90 199.33 T 0 F 0.17 (Weak cache consistency data for the file. For a client that requires only the post-) 216 199.33 P (operation file attributes, these can be found in) 216 187.33 T 5 F (file_wcc.after) 401.7 187.33 T 0 F (.) 485.65 187.33 T 5 F (verf) 90 175.33 T 0 F -0.1 (This is a cookie that the client can use to determine whether the server has reboo-) 216 175.33 P -0.07 (ted between a call to) 216 163.33 P 4 F -0.16 (WRITE) 300.31 163.33 P 0 F -0.07 ( and a subsequent call to) 330.3 163.33 P 4 F -0.16 (COMMIT) 430.37 163.33 P 0 F -0.07 (. This cookie must) 466.35 163.33 P 0.26 (be consistent during a single boot session and must be unique between instances) 216 151.33 P (of the NFS version 3 protocol server where uncommitted data may be lost.) 216 139.33 T -0.55 (Otherwise,) 72 121.33 P 5 F -1.33 (COMMIT3res.status) 117.52 121.33 P 0 F -0.55 ( contains the error on failure and) 219.47 121.33 P 5 F -1.33 (COMMIT3res.resfail) 348.55 121.33 P 0 F -0.55 (contains the follow-) 461.16 121.33 P (ing:) 72 109.33 T 5 F (file_wcc) 90 93.33 T 0 F 0.17 (Weak cache consistency data for the file. For a client that requires only the post-) 216 93.33 P 0.09 (write file attributes, these can be found in) 216 81.33 P 5 F 0.23 (file_wcc.after) 385.25 81.33 P 0 F 0.09 (. Even though the) 469.2 81.33 P FMENDPAGE %%EndPage: "64" 69 %%Page: "65" 69 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (65) 300.44 35.33 T 4 F (COMMIT) 504.02 35.33 T 4.65 (COMMIT) 216 713.33 P 0 F 1.94 ( failed, full) 251.98 713.33 P 5 F 4.65 (wcc_data) 304.42 713.33 P 0 F 1.94 ( is returned to allow the client to determine) 352.4 713.33 P (whether the file changed on the server between calls to) 216 701.33 T 4 F (WRITE) 438.04 701.33 T 0 F ( and) 468.02 701.33 T 4 F (COMMIT) 487.45 701.33 T 0 F (.) 523.43 701.33 T 8 F (IMPLEMENTATION) 72 679.33 T 0 F -0.01 (Procedure) 72 661.33 P 4 F -0.03 (COMMIT) 115.01 661.33 P 0 F -0.01 ( is similar in operation and semantics to the POSIX) 150.99 661.33 P 3 F -0.01 (fsync\0502\051) 358.53 661.33 P 0 F -0.01 ( system call that synchronizes a file\325s) 390.73 661.33 P 0.48 (state with the disk, that is it flushes the file\325s data and metadatato disk.) 72 649.33 P 4 F 1.14 (COMMIT) 363.49 649.33 P 0 F 0.48 ( performs the same operation for a) 399.48 649.33 P 0.65 (client, flushing any unsynchronized data and metadata on the server to the server\325s disk for the specified file. Like) 72 637.33 P 3 F -0.04 (fsync\0502\051) 72 625.33 P 0 F -0.04 (, it may be that there is some modified data or no modified data to synchronize. The data may have been syn-) 104.19 625.33 P -0.21 (chronized by the server\325s normal periodic buffer synchronization activity.) 72 613.33 P 4 F -0.51 (COMMIT) 367.62 613.33 P 0 F -0.21 ( will always return) 403.6 613.33 P 4 F -0.51 (NFS3_OK) 479.92 613.33 P 0 F -0.21 (, un-) 521.89 613.33 P (less there has been an unexpected error.) 72 601.33 T 4 F -0.14 (COMMIT) 72 583.33 P 0 F -0.06 ( differs from) 107.98 583.33 P 3 F -0.06 (fsync\0502\051) 160.82 583.33 P 0 F -0.06 ( in that it is possible for the client to flush a range of the file \050most likely triggered by a) 193.01 583.33 P (buffer-reclamation scheme on the client before file has been completely written\051.) 72 571.33 T 0.01 (The server implementation of) 72 553.33 P 4 F 0.03 (COMMIT) 193.07 553.33 P 0 F 0.01 ( is reasonably simple. If the server receives a full file) 229.05 553.33 P 4 F 0.03 (COMMIT) 443.46 553.33 P 0 F 0.01 ( request, that is) 479.45 553.33 P -0.17 (starting at) 72 541.33 P 5 F -0.4 (offset) 113.87 541.33 P 4 F -0.4 (0) 152.18 541.33 P 0 F -0.17 ( and) 158.18 541.33 P 5 F -0.4 (count) 177.28 541.33 P 4 F -0.4 (0) 209.59 541.33 P 0 F -0.17 (, it should do the equivalent of) 215.59 541.33 P 3 F -0.17 (fsync) 338.81 541.33 P 0 F -0.17 (\050\051\325ing the file. Otherwise, it should arrange to) 359.35 541.33 P -0.09 (have the cached data in the range specified by) 72 529.33 P 5 F -0.21 (offset) 257.45 529.33 P 0 F -0.09 ( and) 293.43 529.33 P 5 F -0.21 (count) 312.69 529.33 P 0 F -0.09 ( to be flushed to stable storage. In both cases, any) 342.67 529.33 P 0.42 (metadata associated with the file must be flushed to stable storage before returning. It is not an error for there to be) 72 517.33 P 0.79 (nothing to flush on the server. This means that the data and metadata that needed to be flushed have already been) 72 505.33 P (flushed or lost during the last server failure.) 72 493.33 T -0.02 (The client implementation of) 72 475.33 P 4 F -0.06 (COMMIT) 190.72 475.33 P 0 F -0.02 ( is a little more complex. There are two reasons for wanting to commit a client) 226.7 475.33 P -0.14 (buffer to stable storage. The first is that the client wants to reuse a buffer. In this case, the) 72 463.33 P 5 F -0.34 (offset) 429.63 463.33 P 0 F -0.14 ( and) 465.61 463.33 P 5 F -0.34 (count) 484.76 463.33 P 0 F -0.14 ( of the) 514.74 463.33 P 0.42 (buffer are sent to the server in the) 72 451.33 P 4 F 1 (COMMIT) 212.43 451.33 P 0 F 0.42 ( request. The server then flushes any cached data based on the) 248.41 451.33 P 5 F 1 (offset) 504.02 451.33 P 0 F -0.23 (and) 72 439.33 P 5 F -0.55 (count) 88.7 439.33 P 0 F -0.23 (, and flushes any metadata associated with the file. It then returns the status of the flush and the) 118.68 439.33 P 5 F -0.55 (verf) 497.65 439.33 P 0 F -0.23 ( ver-) 521.64 439.33 P -0.08 (ifier. The other reason for the client to generate a) 72 427.33 P 4 F -0.2 (COMMIT) 269.6 427.33 P 0 F -0.08 ( is for a full file flush, such as may be done at close. In this) 305.58 427.33 P 0.31 (case, the client would gather all of the buffers for this file that contain uncommitted data, do the) 72 415.33 P 4 F 0.75 (COMMIT) 463.46 415.33 P 0 F 0.31 ( operation) 499.44 415.33 P -0.15 (with an) 72 403.33 P 5 F -0.35 (offset) 103.91 403.33 P 0 F -0.15 ( of) 139.89 403.33 P 4 F -0.35 (0) 152.91 403.33 P 0 F -0.15 ( and) 158.91 403.33 P 5 F -0.35 (count) 178.04 403.33 P 0 F -0.15 ( of) 208.03 403.33 P 4 F -0.35 (0) 221.05 403.33 P 0 F -0.15 (, and then free all of those buffers. Any other dirty buffers would be sent to the) 227.05 403.33 P (server in the normal fashion.) 72 391.33 T 0.32 (This implementation will require some modifications to the buffer cache on the client. After a buffer is written with) 72 373.33 P 5 F -0.24 (stable) 72 361.33 P 4 F -0.24 (UNSTABLE) 110.38 361.33 P 0 F -0.1 (, it must be considered as dirty by the client system until it is either flushed via a) 158.35 361.33 P 4 F -0.24 (COMMIT) 480.53 361.33 P 0 F -0.1 ( oper-) 516.51 361.33 P -0.3 (ation or written via a) 72 349.33 P 4 F -0.72 (WRITE) 156.27 349.33 P 0 F -0.3 ( operation with) 186.25 349.33 P 5 F -0.72 (stable) 248.37 349.33 P 0 F -0.3 ( set to) 284.35 349.33 P 4 F -0.72 (FILE_SYNC) 309.82 349.33 P 0 F -0.3 ( or) 363.79 349.33 P 4 F -0.72 (DATA_SYNC) 376.51 349.33 P 0 F -0.3 (. This is done to prevent the) 430.48 349.33 P (buffer from being freed and reused before the data can be flushed to stable storage on the server.) 72 337.33 T 0.57 (When a response comes back from either a) 72 319.33 P 4 F 1.37 (WRITE) 250.87 319.33 P 0 F 0.57 ( or a) 280.85 319.33 P 4 F 1.37 (COMMIT) 302.83 319.33 P 0 F 0.57 ( operation that contains an unexpected) 338.81 319.33 P 5 F 1.37 (verf) 498.23 319.33 P 0 F 0.57 (, the) 522.22 319.33 P 0.51 (client will need to retransmit all of the buffers containing uncommitted cached data to the server. How this is to be) 72 307.33 P 0.49 (done is up to the implementor. If there is only one buffer of interest, then it should probably be sent back over in a) 72 295.33 P 4 F -0.65 (WRITE) 72 283.33 P 0 F -0.27 ( request with the appropriate) 101.98 283.33 P 5 F -0.65 (stable) 217.48 283.33 P 0 F -0.27 ( flag. If there more than one, it might be worthwhile retransmitting all of) 253.46 283.33 P -0.44 (the buffers in) 72 271.33 P 4 F -1.06 (WRITE) 126.46 271.33 P 0 F -0.44 ( requests with) 156.44 271.33 P 5 F -1.06 (stable) 213.13 271.33 P 0 F -0.44 ( set to) 249.11 271.33 P 4 F -1.06 (UNSTABLE) 274.15 271.33 P 0 F -0.44 ( and then retransmitting the) 322.13 271.33 P 4 F -1.06 (COMMIT) 432.34 271.33 P 0 F -0.44 ( operation to flush) 468.32 271.33 P (all of the data on the server to stable storage. The timing of these retransmissions is left to the implementor.) 72 259.33 T 0.16 (The above description applies to page-cache-based systems as well as buffer-cache-based systems. In those systems,) 72 241.33 P (the virtual memory system will need to be modified instead of the buffer cache.) 72 229.33 T (See additional comments on) 72 211.33 T 4 F (WRITE) 187.49 211.33 T 0 F ( on page 30) 217.47 211.33 T (.) 263.83 211.33 T 8 F (ERRORS) 72 189.33 T 4 F (NFS3ERR_IO) 90 173.33 T (NFS3ERR_STALE) 90 161.33 T (NFS3ERR_BADHANDLE) 90 149.33 T (NFS3ERR_SERVERFAULT) 90 137.33 T 8 F (SEE ALSO) 72 115.33 T 4 F (WRITE on page 30.) 72 97.33 T FMENDPAGE %%EndPage: "65" 70 %%Page: "66" 70 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 4 F (COMMIT) 72 35.33 T 2 F (66) 300.44 35.33 T (Version 3) 495.01 35.33 T FMENDPAGE %%EndPage: "66" 71 %%Page: "67" 71 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (67) 300.44 35.33 T (Implementation issues) 72 713.33 T 0 F 0.4 (The NFS version 3 protocol was designed to allow different operating systems to share files. However, since it was) 72 695.33 P -0.05 (designed in a UNIX environment, many operations have semantics similar to the operations of the UNIX file system.) 72 683.33 P -0.56 (This section discusses some of the general implementation-specific details and semantic issues. Procedure descriptions) 72 671.33 P (have implementation comments specific to that procedure.) 72 659.33 T 0.56 (A number of papers have been written describing issues encountered when constructing an NFS version 2 protocol) 72 641.33 P -0.52 (implementation. The best overview paper is still) 72 629.33 P 3 F -0.52 ([Sandberg]) 263.81 629.33 P 0 F -0.52 (.) 309.89 629.33 P 3 F -0.52 ([Israel]) 314.37 629.33 P 0 F -0.52 (,) 345.46 629.33 P 3 F -0.52 ([Macklem]) 349.95 629.33 P 0 F -0.52 (, and) 394.35 629.33 P 3 F -0.52 ([Pawlowski]) 415.24 629.33 P 0 F -0.52 ( describe other im-) 466.33 629.33 P -0.36 (plementations.) 72 617.33 P 3 F -0.36 ([X/OpenNFS]) 132.72 617.33 P 0 F -0.36 ( provides a complete description of the NFS version 2 protocol and supporting protocols,) 188.8 617.33 P 0.13 (as well as a discussion on implementation issues and procedure and error semantics. Many of the issues encountered) 72 605.33 P -0.06 (when constructing an NFS version 2 protocol implementation will be encountered when constructing an NFS version) 72 593.33 P (3 protocol implementation.) 72 581.33 T 2 F (Multiple version support) 72 559.33 T 0 F -0.39 (The RPC protocol provides explicit support for versioning of a service. Client and server implementations of NFS ver-) 72 541.33 P -0.23 (sion 3 protocol should support both versions, for full backwards compatibility, when possible. Default behavior of the) 72 529.33 P -0.38 (RPC binding protocol is the client and server bind using the highest version number they both support. Client or server) 72 517.33 P 0.22 (implementations that cannot easily support both versions \050for example, because of memory restrictions\051 will have to) 72 505.33 P 0.56 (choose what version to support. The NFS version 2 protocol would be a safe choice since fully capable clients and) 72 493.33 P -0.03 (servers should support both versions. However, this choice would need to be made keeping) 72 481.33 P 3 F -0.03 (all) 439.05 481.33 P 0 F -0.03 ( requirements in mind.) 449.6 481.33 P 2 F (Server/client relationship) 72 459.33 T 0 F 0.09 (The NFS version 3 protocol is designed to allow servers to be as simple and general as possible. Sometimes the sim-) 72 441.33 P (plicity of the server can be a problem, if the client implements complicated file system semantics.) 72 429.33 T -0.01 (For example, some operating systems allow removal of open files. A process can open a file and, while it is open, re-) 72 411.33 P 0.06 (move it from the directory. The file can be read and written as long as the process keeps it open, even though the file) 72 399.33 P 0.12 (has no name in the file system. It is impossible for a stateless server to implement these semantics. The client can do) 72 387.33 P -0.28 (some tricks such as renaming the file on remove \050to a) 72 375.33 P 3 F -0.28 (hidden) 285.17 375.33 P 0 F -0.28 ( name\051, and only physically deleting it on close. The NFS) 312.37 375.33 P (version 3 protocol provides sufficient functionality to implement most file system semantics on a client.) 72 363.33 T 0.26 (Every NFS version 3 protocol client can also potentially be a server, and remote and local mounted file systems can) 72 345.33 P -0.26 (be freely mixed. This leads to some problems when a client travels down the directory tree of a remote file system and) 72 333.33 P -0.17 (reaches the mount point on the server for another remote file system. Allowing the server to follow the second remote) 72 321.33 P 0.41 (mount would require loop detection, server lookup, and user revalidation. Instead, both NFS version 2 protocol and) 72 309.33 P 0.14 (NFS version 3 protocol implementations do not typically let clients cross a server\325s mount point. When a client does) 72 297.33 P -0.56 (a) 72 285.33 P 4 F -1.35 (LOOKUP) 78.37 285.33 P 0 F -0.56 ( on a directory on which the server has mounted a file system, the client sees the underlying directory instead) 114.35 285.33 P (of the mounted directory.) 72 273.33 T 0.9 (For example, if a server has a file system called) 72 255.33 P 4 F 2.16 (/usr) 273.89 255.33 P 0 F 0.9 ( and mounts another file system on) 297.88 255.33 P 4 F 2.16 (/usr/src) 446.58 255.33 P 0 F 0.9 (, if a client) 494.56 255.33 P 0.49 (mounts) 72 243.33 P 4 F 1.18 (/usr) 104.42 243.33 P 0 F 0.49 (, it does) 128.41 243.33 P 3 F 0.49 (not) 163.76 243.33 P 0 F 0.49 ( see the mounted version of) 176.53 243.33 P 4 F 1.18 (/usr/src) 292.17 243.33 P 0 F 0.49 (. A client could do remote mounts that match the) 340.15 243.33 P -0.11 (server\325s mount points to maintain the server\325s view. In this example, the client would also have to mount) 72 231.33 P 4 F -0.26 (/usr/src) 492.03 231.33 P 0 F (in addition to) 72 219.33 T 4 F (/usr) 127.81 219.33 T 0 F (, even if they are from the same server.) 151.8 219.33 T 2 F (Path name interpretation) 72 197.33 T 0 F -0.28 (There are a few complications to the rule that path names are always parsed on the client. For example, symbolic links) 72 179.33 P (could have different interpretations on different clients. There is no answer to this problem in this specification.) 72 167.33 T -0.49 (Another common problem for non-UNIX implementations is the special interpretation of the pathname, \322) 72 149.33 P 4 F -1.16 (..) 487.62 149.33 P 0 F -0.49 (\323, to mean) 499.61 149.33 P -0.61 (the parent of a given directory. A future revision of the protocol may use an explicit flag to indicate the parent instead\321) 72 137.33 P (however it is not a problem as many working non-UNIX implementations exist.) 72 125.33 T 2 F (Permission issues) 72 103.33 T 0 F 0.21 (The NFS version 3 protocol, strictly speaking, does not define the permission checking used by servers. However, it) 72 85.33 P FMENDPAGE %%EndPage: "67" 72 %%Page: "68" 72 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (68) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F -0.58 (is expected that a server will do normal operating system permission checking using) 72 713.33 P 4 F -1.39 (AUTH_UNIX) 406.68 713.33 P 0 F -0.58 ( style authentication) 460.65 713.33 P 2.67 (as the basis of its protection mechanism, or another stronger form of authentication such as) 72 701.33 P 4 F 6.42 (AUTH_DES) 478.53 701.33 P 0 F 2.67 ( or) 526.5 701.33 P 4 F -0.97 (AUTH_KERB) 72 689.33 P 0 F -0.4 (. With) 125.97 689.33 P 4 F -0.97 (AUTH_UNIX) 152.65 689.33 P 0 F -0.4 ( authentication, the server gets the client\325s effective) 206.62 689.33 P 3 F -0.4 (uid) 411.83 689.33 P 0 F -0.4 (, effective) 424.6 689.33 P 3 F -0.4 (gid) 466.25 689.33 P 0 F -0.4 (, and) 479.03 689.33 P 3 F -0.4 (groups) 500.15 689.33 P 0 F -0.4 ( on) 527.91 689.33 P -0.3 (each call and uses them to check permission. These are the so-called) 72 677.33 P 3 F -0.3 (UNIX credentials) 344.59 677.33 P 0 F -0.3 (.) 414.52 677.33 P 4 F -0.72 (AUTH_DES) 419.22 677.33 P 0 F -0.3 ( and) 467.2 677.33 P 4 F -0.72 (AUTH_KERB) 486.03 677.33 P 0 F -0.22 (use a) 72 665.33 P 3 F -0.22 (network name) 94.32 665.33 P 0 F -0.22 (, or) 150.46 665.33 P 3 F -0.22 (netname) 165.84 665.33 P 0 F -0.22 (, as the basis for identification \050from which a UNIX server derives the necessary stan-) 199.71 665.33 P (dard UNIX credentials\051. There are problems with this method that have been solved.) 72 653.33 T -0.04 (Using) 72 635.33 P 3 F -0.04 (uid) 98.34 635.33 P 0 F -0.04 ( and) 111.11 635.33 P 3 F -0.04 (gid) 130.46 635.33 P 0 F -0.04 ( implies that the client and server share the same) 143.24 635.33 P 3 F -0.04 (uid) 339.37 635.33 P 0 F -0.04 ( list. Every server and client pair must have the) 352.15 635.33 P -0.04 (same mapping from user to) 72 623.33 P 3 F -0.04 (uid) 183.68 623.33 P 0 F -0.04 ( and from group to) 196.46 623.33 P 3 F -0.04 (gid) 273.72 623.33 P 0 F -0.04 (. Since every client can also be a server, this tends to imply that) 286.49 623.33 P -0.23 (the whole network shares the same) 72 611.33 P 3 F -0.23 (uid/gid) 212.75 611.33 P 0 F -0.23 ( space. If this is not the case, then it usually falls upon the server to perform) 241.07 611.33 P -0.57 (some custom mapping of credentials from one authentication domain into another. A discussion of techniques for man-) 72 599.33 P (aging a shared user space or for providing mechanisms for user id mapping is beyond the scope of this specification.) 72 587.33 T 0.19 (Another problem arises due to the usually stateful open operation. Most operating systems check permission at open) 72 569.33 P -0.45 (time, and then check that the file is open on each read and write request. With stateless servers, the server cannot detect) 72 557.33 P 0.49 (that the file is open and must do permission checking on each read and write call. UNIX client semantics of access) 72 545.33 P 0.02 (permission checking on open can be provided with the) 72 533.33 P 4 F 0.05 (ACCESS) 292.87 533.33 P 0 F 0.02 ( procedure call in this revision, which allows a client) 328.85 533.33 P -0.31 (to explicitly check access permissions without resorting to trying the operation. On a local file system, a user can open) 72 521.33 P 0.49 (a file and then change the permissions so that no one is allowed to touch it, but will still be able to write to the file) 72 509.33 P -0.05 (because it is open. On a remote file system, by contrast, the write would fail. To get around this problem, the server\325s) 72 497.33 P 0.08 (permission checking algorithm should allow the owner of a file to access it regardless of the permission setting. This) 72 485.33 P -0.32 (is needed in a practical NFS version 3 protocol server implementation, but it does depart from correct local file system) 72 473.33 P 0.06 (semantics. This should not affect the return result of access permissions as returned by the) 72 461.33 P 4 F 0.14 (ACCESS) 435.91 461.33 P 0 F 0.06 ( procedure, how-) 471.89 461.33 P (ever.) 72 449.33 T 0.54 (A similar problem has to do with paging in an executable program over the network. The operating system usually) 72 431.33 P -0.11 (checks for execute permission before opening a file for demand paging, and then reads blocks from the open file. In a) 72 419.33 P 0.02 (local UNIX file system, an executable file does not need read permission to execute \050pagein\051. An NFS version 3 pro-) 72 407.33 P -0.05 (tocol server can not tell the difference between a normal file read \050where the read permission bit is meaningful\051 and a) 72 395.33 P 0.23 (demand pagein read \050where the server should allow access to the executable file if the execute bit is set for that user) 72 383.33 P -0.13 (or group or public\051. To make this work, the server allows reading of files if the) 72 371.33 P 3 F -0.13 (uid) 387.43 371.33 P 0 F -0.13 ( given in the call has either execute) 400.2 371.33 P -0.51 (or read permission on the file, through ownership, group membership or public access. Again, this departs from correct) 72 359.33 P (local file system semantics.) 72 347.33 T -0.39 (In most operating systems, a particular user \050on UNIX, the) 72 329.33 P 3 F -0.39 (uid) 305.14 329.33 P 4 F -0.94 (0) 320.02 329.33 P 0 F -0.39 (\051 has access to all files, no matter what permission and) 326.01 329.33 P -0.12 (ownership they have. This) 72 317.33 P 3 F -0.12 (superuser) 179.49 317.33 P 0 F -0.12 ( permission may not be allowed on the server, since anyone who can become) 218.91 317.33 P 3 F -0.12 (su-) 527.79 317.33 P 0.22 (peruser) 72 305.33 P 0 F 0.22 ( on their client could gain access to all remote files. A UNIX server by default maps) 102.53 305.33 P 3 F 0.22 (uid) 444.85 305.33 P 4 F 0.52 (0) 460.33 305.33 P 0 F 0.22 ( to a distinguished) 466.33 305.33 P -0.12 (value \050) 72 293.33 P 4 F -0.29 (UID_NOBODY) 99.35 293.33 P 0 F -0.12 (\051, as well as mapping the groups list, before doing its access checking. A server implementation) 159.32 293.33 P 0.57 (may provide a mechanism to change this mapping. This works except for NFS version 3 protocol root file systems) 72 281.33 P 0.24 (\050required for diskless NFS version 3 protocol client support\051, where) 72 269.33 P 3 F 0.24 (superuser) 347.85 269.33 P 0 F 0.24 ( access cannot be avoided. Export op-) 387.27 269.33 P (tions are used, on the server, to restrict the set of clients allowed) 72 257.33 T 3 F (superuser) 330.98 257.33 T 0 F ( access.) 370.4 257.33 T 2 F (Duplicate request cache) 72 235.33 T 0 F -0.26 (The typical NFS version 3 protocol failure recovery model uses client time-out and retry to handle server crashes, net-) 72 217.33 P (work partitions, and lost server replies. A retried request is called a) 72 205.33 T 3 F (duplicate) 342.35 205.33 T 0 F ( of the original.) 379.55 205.33 T -0.1 (When used in a file server context, the term) 72 187.33 P 3 F -0.1 (idempotent) 248.16 187.33 P 0 F -0.1 ( can be used to distinguish between operation types. An idem-) 292.58 187.33 P 0.18 (potent request is one that a server can perform more than once with equivalent results \050though it may in fact change,) 72 175.33 P 0.27 (as a side effect, the access time on a file, say for) 72 163.33 P 4 F 0.65 (READ) 270.09 163.33 P 0 F 0.27 (\051. Some NFS operations are obviously non-idempotent. They) 294.08 163.33 P 0.02 (cannot be reprocessed without special attention simply because they may fail if tried a second time. The) 72 151.33 P 4 F 0.05 (CREATE) 490.4 151.33 P 0 F 0.02 ( re-) 526.39 151.33 P -0.29 (quest, for example, can be used to create a file for which the owner does not have write permission. A duplicate of this) 72 139.33 P (request cannot succeed if the original succeeded. Likewise, a file can be removed only once.) 72 127.33 T -0.05 (The side effects caused by performing a duplicate non-idempotent request can be destructive \050for example, a truncate) 72 109.33 P -0.39 (operation causing lost writes\051. The combination of a stateless design with the common choice of an unreliable network) 72 97.33 P -0.5 (transport \050UDP\051 implies the possibility of destructive replays of non-idempotent requests. Though to be more accurate,) 72 85.33 P FMENDPAGE %%EndPage: "68" 73 %%Page: "69" 73 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (69) 300.44 35.33 T 0 F -0.17 (it is the inherent stateless design of the NFS version 3 protocol on top of an unreliable RPC mechanism that yields the) 72 713.33 P 0.36 (possibility of destructive replays of non-idempotent requests, since even in an implementation of the NFS version 3) 72 701.33 P -0.3 (protocol over a reliable connection-oriented transport, a connection break with automatic reestablishment requires du-) 72 689.33 P -0.26 (plicate request processing \050the client will retransmit the request, and the server needs to deal with a potential duplicate) 72 677.33 P (non-idempotent request\051.) 72 665.33 T -0.54 (Most NFS version 3 protocol server implementations use a cache of recent requests \050called the duplicate request cache\051) 72 647.33 P 0.42 (for the processing of duplicate non-idempotent requests. The duplicate request cache provides a) 72 635.33 P 3 F 0.42 (short-term memory) 462.69 635.33 P 0 F -0.26 (mechanism in which the original completion status of a request is) 72 623.33 P 3 F -0.26 (remembered) 333.67 623.33 P 0 F -0.26 ( and the operation attempted only once.) 383.63 623.33 P (If a duplicate copy of this request is received, then the original completion status is returned.) 72 611.33 T -0.02 (The duplicate-request cache mechanism has been useful in reducing destructive side effects caused by duplicate NFS) 72 593.33 P -0.05 (version 3 protocol requests. This mechanism, however, does not guarantee against these destructive side effects in all) 72 581.33 P 0.44 (failure modes. Most servers store the duplicate request cache in RAM, so the contents are lost if the server crashes.) 72 569.33 P 0.54 (The exception to this may possibly occur in a redundant server approach to high availability, where the file system) 72 557.33 P -0.01 (itself may be used to share the duplicate request cache state. Even if the cache survives server reboots \050or failovers in) 72 545.33 P 0.04 (the high availability case\051, its effectiveness is a function of its size. A network partition can cause a cache entry to be) 72 533.33 P -0.19 (reused before a client receives a reply for the corresponding request. If this happens, the duplicate request will be pro-) 72 521.33 P (cessed as a new one, possibly with destructive side effects.) 72 509.33 T (A good description of the implementation and use of a duplicate request cache can be found in) 72 491.33 T 3 F ([Juszczak]) 452.55 491.33 T 0 F (.) 495.3 491.33 T 2 F (File name component handling) 72 469.33 T 0 F -0.15 (Server implementations of NFS version 3 protocol will frequently impose restrictions on the names which can be cre-) 72 451.33 P -0.1 (ated. Many servers will also forbid the use of names that contain certain characters, such as the path component sepa-) 72 439.33 P 0.41 (rator used by the server operating system. For example, the UFS file system will reject a name which contains \322) 72 427.33 P 4 F 1 (/) 527.07 427.33 P 0 F 0.41 (\323,) 533.06 427.33 P -0.45 (while \322) 72 415.33 P 4 F -1.07 (.) 100.7 415.33 P 0 F -0.45 (\323 and \322) 106.69 415.33 P 4 F -1.07 (..) 134.1 415.33 P 0 F -0.45 (\323 are distinguished in UFS, and may not be specified as the name when creating a file system object.) 146.1 415.33 P 0.54 (The exact error status values return for these errors is specified in the description of each procedure argument. The) 72 403.33 P -0.06 (values \050which conform to NFS version 2 protocol server practice\051 are not necessarily obvious, nor are they consistent) 72 391.33 P (from one procedure to the next.) 72 379.33 T 2 F (Synchronous modifying operations) 72 357.33 T 0 F -0.25 (Data-modifying operations in the NFS version 3 protocol are synchronous. When a procedure returns to the client, the) 72 339.33 P (client can assume that the operation has completed and any data associated with the request is now on stable storage.) 72 327.33 T 2 F (Stable storage) 72 305.33 T 0 F -0.12 (NFS version 3 protocol servers must be able to recover without data loss from multiple power failures \050including cas-) 72 287.33 P -0.52 (cading power failures, that is, several power failures in quick succession\051, operating system failures, and hardware fail-) 72 275.33 P (ure of components other than the storage medium itself \050for example, disk, nonvolatile RAM\051.) 72 263.33 T (Some examples of stable storage that are allowable for an NFS server include:) 72 245.33 T 1 F (1.) 90 229.33 T 0 F -0.05 (Media commit of data, that is, the modified data has been successfully written to the disk media, for ex-) 108 229.33 P (ample, the disk platter.) 108 217.33 T 1 F (2.) 90 203.33 T 0 F -0.52 (An immediate reply disk drive with battery-backed on-drive intermediate storage or uninterruptible pow-) 108 203.33 P (er system \050UPS\051.) 108 191.33 T 1 F (3.) 90 177.33 T 0 F (Server commit of data with battery-backed intermediate storage and recovery software.) 108 177.33 T 1 F (4.) 90 163.33 T 0 F (Cache commit with uninterruptible power system \050UPS\051 and recovery software.) 108 163.33 T (Conversely, the following are not examples of stable storage:) 72 145.33 T 1 F (1.) 90 129.33 T 0 F 0.37 (An immediate reply disk drive without battery-backed on-drive intermediate storage or uninterruptible) 108 129.33 P (power system \050UPS\051.) 108 117.33 T 1 F (2.) 90 103.33 T 0 F (Cache commit without both uninterruptible power system \050UPS\051 and recovery software.) 108 103.33 T -0.45 (The) 72 85.33 P 3 F -0.45 (only) 89.59 85.33 P 0 F -0.45 ( exception to this \050introduced in this protocol revision\051 is as described under the) 106.8 85.33 P 4 F -1.09 (WRITE) 421.91 85.33 P 0 F -0.45 ( procedure on the han-) 451.89 85.33 P FMENDPAGE %%EndPage: "69" 74 %%Page: "70" 74 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (70) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F 0.18 (dling of the) 72 713.33 P 5 F 0.44 (stable) 121.13 713.33 P 0 F 0.18 ( bit, and the use of the) 157.11 713.33 P 4 F 0.44 (COMMIT) 249.44 713.33 P 0 F 0.18 ( procedure. It is the use of the synchronous) 285.42 713.33 P 4 F 0.44 (COMMIT) 461.38 713.33 P 0 F 0.18 ( procedure) 497.36 713.33 P (that provides the necessary semantic support in the NFS version 3 protocol.) 72 701.33 T 2 F (Lookups and name resolution) 72 679.33 T 0 F 0.46 (A common objection to the NFS version 3 protocol is the philosophy of component-by-component) 72 661.33 P 4 F 1.09 (LOOKUP) 475.9 661.33 P 0 F 0.46 ( by the) 511.89 661.33 P -0.2 (client in resolving a name. The objection is that this is inefficient, as latencies for component-by-component) 72 649.33 P 4 F -0.49 (LOOKUP) 504.02 649.33 P 0 F (would be unbearable.) 72 637.33 T -0.05 (Implementation practice solves this issue. A name cache, providing component to file-handle mapping, is kept on the) 72 619.33 P -0.1 (client to short circuit actual) 72 607.33 P 4 F -0.24 (LOOKUP) 183.36 607.33 P 0 F -0.1 ( invocations over the wire. The cache is subject to cache timeout parameters that) 219.34 607.33 P (bound attributes.) 72 595.33 T 2 F (Adaptive retransmission) 72 573.33 T 0 F -0.08 (Most client implementations use either an exponential back-off strategy to some maximum retransmission value, or a) 72 555.33 P -0.43 (more adaptive strategy that attempts congestion avoidance. Congestion avoidance schemes in NFS request retransmis-) 72 543.33 P 0.97 (sion are modelled on the work presented in) 72 531.33 P 3 F 0.97 ([Jacobson]) 254.65 531.33 P 0 F 0.97 (.) 300.18 531.33 P 3 F 0.97 ([Nowicki]) 306.14 531.33 P 0 F 0.97 ( and) 346.68 531.33 P 3 F 0.97 ([Macklem]) 368.06 531.33 P 0 F 0.97 ( describe congestion avoidance) 412.46 531.33 P (schemes for NFS over UDP.) 72 519.33 T 2 F (Caching policies) 72 497.33 T 0 F -0.56 (The NFS version 3 protocol does not define a policy for caching on the client or server. In particular, there is no support) 72 479.33 P -0.09 (for strict cache consistency between a client and server, nor between different clients. See) 72 467.33 P 3 F -0.09 ([Kazar]) 432.09 467.33 P 0 F -0.09 ( for a discussion of) 464.3 467.33 P (the issues of cache synchronization and mechanisms in several distributed file systems.) 72 455.33 T 2 F (Stable versus unstable writes) 72 433.33 T 0 F -0.19 (The setting of the) 72 415.33 P 5 F -0.45 (stable) 143.99 415.33 P 0 F -0.19 ( field in the) 179.97 415.33 P 4 F -0.45 (WRITE) 227.53 415.33 P 0 F -0.19 ( arguments, that is whether or not to do asynchronous) 257.51 415.33 P 4 F -0.45 (WRITE) 472.45 415.33 P 0 F -0.19 ( requests,) 502.44 415.33 P -0.16 (is straightforward on a UNIX client. If the NFS version 3 protocol client receives a write request that is not marked as) 72 403.33 P 0.42 (being asynchronous, it should generate the RPC with) 72 391.33 P 5 F 1.01 (stable) 289.97 391.33 P 0 F 0.42 ( set to) 325.95 391.33 P 4 F 1.01 (TRUE) 353.59 391.33 P 0 F 0.42 (. If the request is marked as being asyn-) 377.58 391.33 P -0.53 (chronous, the RPC should be generated with) 72 379.33 P 5 F -1.26 (stable) 248.76 379.33 P 0 F -0.53 ( set to) 284.74 379.33 P 4 F -1.26 (FALSE) 309.54 379.33 P 0 F -0.53 (. If the response comes back with the) 339.52 379.33 P 5 F -1.26 (committed) 486.03 379.33 P 0 F -0.61 (field set to) 72 367.33 P 4 F -1.45 (TRUE) 114.88 367.33 P 0 F -0.61 (, the client should just mark the write request as done and no further action is required. If) 138.86 367.33 P 5 F -1.45 (committed) 486.03 367.33 P 0 F -0.28 (is set to) 72 355.33 P 4 F -0.67 (FALSE) 104.21 355.33 P 0 F -0.28 (, indicating that the buffer was not synchronized with the server\325s disk, the client will need to mark the) 134.19 355.33 P 0.05 (buffer in some way which indicates that a copy of the buffer lives on the server and that a new copy does not need to) 72 343.33 P (be sent to the server, but that a commit is required.) 72 331.33 T -0.08 (Note that this algorithm introduces a new state for buffers, thus there are now three states for buffers. The three states) 72 313.33 P 0.04 (are dirty, done but needs to be committed, and done. This extra state on the client will likely require modifications to) 72 301.33 P (the system outside of the NFS version 3 protocol client.) 72 289.33 T -0.11 (One proposal that was rejected was the addition of a boolean) 72 271.33 P 5 F -0.27 (commit) 316.42 271.33 P 0 F -0.11 ( argument to the) 352.4 271.33 P 4 F -0.27 (WRITE) 419.69 271.33 P 0 F -0.11 ( operation. It would be) 449.67 271.33 P -0.41 (used to indicate whether the server should do a full file commit after doing the write. This seems as if it could be useful) 72 259.33 P -0.17 (if the client knew that it was doing the) 72 247.33 P 3 F -0.17 (last) 226.22 247.33 P 0 F -0.17 ( write on the file. It is difficult to see how this could be used, given existing) 240.66 247.33 P (client architectures though.) 72 235.33 T -0.26 (The asynchronous write opens up the window of problems associated with write sharing. For example: client A writes) 72 217.33 P 0.26 (some data asynchronously. Client A is still holding the buffers cached, waiting to commit them later. Client B reads) 72 205.33 P 0.22 (the modified data and writes it back to the server. The server then crashes. When it comes back up, client A issues a) 72 193.33 P 4 F 0.02 (COMMIT) 72 181.33 P 0 F 0.01 ( operation which returns with a different cookie as well as changed attributes. In this case, the correct action) 107.98 181.33 P -0.44 (may or may not be to retransmit the cached buffers. Unfortunately, client A can\325t tell for sure, so it will need to retrans-) 72 169.33 P -0.23 (mit the buffers, thus overwriting the changes from client B. Fortunately, write sharing is rare and the solution matches) 72 157.33 P (the current write sharing situation. Without using locking for synchronization, the behaviour will be indeterminate.) 72 145.33 T 0.23 (In a high availability \050redundant system\051 server implementation, two cases exist which relate to the) 72 127.33 P 5 F 0.56 (verf) 474.14 127.33 P 0 F 0.23 ( changing.) 498.13 127.33 P -0.33 (If the high availability server implementation does not use a shared-memory scheme, then the) 72 115.33 P 5 F -0.8 (verf) 444.56 115.33 P 0 F -0.33 ( should change on) 468.55 115.33 P -0.03 (failover, since the unsynchronized data is not available to the second processor and there is no guarantee that the sys-) 72 103.33 P -0.29 (tem which had the data cached was able to flush it to stable storage before going down. The client will need to retrans-) 72 91.33 P 0.92 (mit the data to be safe. In a shared-memory high availability server implementation, the) 72 79.33 P 5 F 2.2 (verf) 437.94 79.33 P 0 F 0.92 ( would not need to) 461.93 79.33 P FMENDPAGE %%EndPage: "70" 75 %%Page: "71" 75 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (71) 300.44 35.33 T 0 F -0.23 (change because the server would still have the cached data available to it to be flushed. The exact policy regarding the) 72 713.33 P 5 F (verf) 72 701.33 T 0 F ( in a shared memory high availability implementation, however, is up to the server implementor.) 95.99 701.33 T 2 F (32 bit clients/servers and 64 bit clients/servers) 72 679.33 T 0 F -0.07 (The) 72 661.33 P 4 F -0.16 (64) 89.97 661.33 P 0 F -0.07 ( bit nature of the NFS version 3 protocol introduces several compatibility problems. The most notable two are) 101.97 661.33 P (mismatched clients and servers, that is, a) 72 649.33 T 4 F (32) 237.72 649.33 T 0 F ( bit client and a) 249.71 649.33 T 4 F (64) 313.84 649.33 T 0 F ( bit server or a) 325.83 649.33 T 4 F (64) 386.06 649.33 T 0 F ( bit client and a) 398.05 649.33 T 4 F (32) 462.18 649.33 T 0 F ( bit server.) 474.17 649.33 T -0.18 (The problems of a) 72 631.33 P 4 F -0.44 (64) 146.77 631.33 P 0 F -0.18 ( bit client and a) 158.77 631.33 P 4 F -0.44 (32) 221.99 631.33 P 0 F -0.18 ( bit server are easy to handle. The client will never encounter a file that it can) 233.98 631.33 P -0.2 (not handle. If it sends a request to the server that the server can not handle, the server should reject the request with an) 72 619.33 P (appropriate error.) 72 607.33 T 0.44 (The problems of a) 72 589.33 P 4 F 1.06 (32) 149.27 589.33 P 0 F 0.44 ( bit client and a) 161.26 589.33 P 4 F 1.06 (64) 227.59 589.33 P 0 F 0.44 ( bit server are much harder to handle. In this situation, the server does not) 239.59 589.33 P 0.19 (have a problem because it can handle anything that the client can generate. However, the client may encounter a file) 72 577.33 P -0.12 (that it can not handle. The client will not be able to handle a file whose size can not be expressed in) 72 565.33 P 4 F -0.3 (32) 469.24 565.33 P 0 F -0.12 ( bits. Thus, the) 481.24 565.33 P -0.03 (client will not be able to properly decode the size of the file into its local attributes structure.Also, a file can grow be-) 72 553.33 P (yond the limit of the client while the client is accessing the file.) 72 541.33 T -0.44 (The solutions to these problems are left up to the individual implementor. However, there are two common approaches) 72 523.33 P -0.37 (used to resolve this situation. The implementor can choose between them or even can invent a new solution altogether.) 72 511.33 P -0.16 (The most common solution is for the client to deny access to any file whose size can not be expressed in) 72 493.33 P 4 F -0.38 (32) 488.62 493.33 P 0 F -0.16 ( bits. This) 500.61 493.33 P 0.41 (is probably the safest, but does introduce some strange semantics when the file grows beyond the limit of the client) 72 481.33 P (while it is being access by that client. The file becomes inaccessible even while it is being accessed.) 72 469.33 T -0.14 (The second solution is for the client to map any size greater than it can handle to the maximum size that it can handle.) 72 451.33 P 0.45 (Effectively, it is lying to the application program. This allows the application access as much of the file as possible) 72 439.33 P -0 (given the) 72 427.33 P 4 F -0.01 (32) 111.41 427.33 P 0 F -0 ( bit offset restriction. This eliminates the strange semantic of the file effectively disappearing after it has) 123.41 427.33 P (been accessed, but does introduce other problems. The client will not be able to access the entire file.) 72 415.33 T -0.26 (Currently, the first solution is the recommended solution. However, client implementors are encouraged to do the best) 72 397.33 P (that they can to reduce the effects of this situation.) 72 385.33 T FMENDPAGE %%EndPage: "71" 76 %%Page: "72" 76 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (72) 300.44 35.33 T (Version 3) 495.01 35.33 T FMENDPAGE %%EndPage: "72" 77 %%Page: "73" 77 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (73) 300.44 35.33 T 2 12 Q (Appendix I: Mount protocol) 72 712 T 0 10 Q 0.11 (The changes from the NFS version 2 protocol to the NFS version 3 protocol have required some changes to be made) 72 693.33 P -0.28 (in the MOUNT protocol. To meet the needs of the NFS version 3 protocol, a new version of the MOUNT protocol has) 72 681.33 P 0.1 (been defined. This new protocol satisfies the requirements of the NFS version 3 protocol and addresses several other) 72 669.33 P (current market requirements.) 72 657.33 T FMENDPAGE %%EndPage: "73" 78 %%Page: "74" 78 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (74) 300.44 35.33 T (Version 3) 495.01 35.33 T 2 12 Q (RPC Information) 72 712 T 2 10 Q (Authentication) 72 693.33 T 0 F 1.85 (The MOUNT service uses) 72 675.33 P 4 F 4.44 (AUTH_NONE) 187.09 675.33 P 0 F 1.85 ( in the) 241.06 675.33 P 4 F 4.44 (NULL) 274.09 675.33 P 0 F 1.85 ( procedure.) 298.07 675.33 P 4 F 4.44 (AUTH_UNIX) 349.23 675.33 P 0 F 1.85 (,) 403.2 675.33 P 4 F 4.44 (AUTH_SHORT) 410.04 675.33 P 0 F 1.85 (,) 470.01 675.33 P 4 F 4.44 (AUTH_DES) 476.86 675.33 P 0 F 1.85 (, or) 524.83 675.33 P 4 F (AUTH_KERB) 72 663.33 T 0 F ( are used for all other procedures. Other authentication types may be supported in the future.) 125.97 663.33 T 2 F (Constants) 72 645.33 T 0 F (These are the RPC constants needed to call the MOUNT service. They are given in decimal.) 72 627.33 T 4 F (PROGRAM) 90 611.33 T ( 100005) 131.98 611.33 T (VERSION) 90 599.33 T ( 3) 131.98 599.33 T 2 F (Transport address) 72 581.33 T 0 F -0.2 (The MOUNT service is normally supported over the TCP and UDP protocols. The rpcbind daemon should be queried) 72 563.33 P (for the correct transport address.) 72 551.33 T 2 F (Sizes) 72 533.33 T 4 F (const MNTPATHLEN) 90 517.33 T (= 1024;) 198 517.33 T (/* Maximum bytes in a path name */) 288 517.33 T (const MNTNAMLEN) 90 505.33 T (= 255;) 198 505.33 T (/* Maximum bytes in a name */) 288 505.33 T (const FHSIZE3) 90 493.33 T (= 64;) 198 493.33 T (/* Maximum bytes in a V3 file handle */) 288 493.33 T 2 F (Basic Data Types) 72 475.33 T 4 F (typedef opaque fhandle3;) 90 459.33 T (typedef string dirpath;) 90 447.33 T (typedef string name;) 90 435.33 T (enum mountstat3 {) 90 411.33 T (MNT3_OK) 108 399.33 T (= 0,) 234 399.33 T (/* no error */) 288 399.33 T (MNT3ERR_PERM) 108 387.33 T (= 1,) 234 387.33 T (/* Not owner */) 288 387.33 T (MNT3ERR_NOENT) 108 375.33 T (= 2,) 234 375.33 T (/* No such file or directory */) 288 375.33 T (MNT3ERR_IO) 108 363.33 T (= 5,) 234 363.33 T (/* I/O error */) 288 363.33 T (MNT3ERR_ACCES) 108 351.33 T (= 13,) 234 351.33 T (/* Permission denied */) 288 351.33 T (MNT3ERR_NOTDIR) 108 339.33 T (= 20,) 234 339.33 T (/* Not a directory */) 288 339.33 T (MNT3ERR_INVAL) 108 327.33 T (= 22,) 234 327.33 T (/* Invalid argument */) 288 327.33 T (MNT3ERR_NAMETOOLONG) 108 315.33 T (= 63,) 234 315.33 T (/* Filename too long */) 288 315.33 T (MNT3ERR_NOTSUPP) 108 303.33 T (= 10004,) 234 303.33 T (/* Operation not supported */) 288 303.33 T (MNT3ERR_SERVERFAULT) 108 291.33 T (= 10006) 234 291.33 T (/* A failure on the server */) 288 291.33 T (};) 90 279.33 T FMENDPAGE %%EndPage: "74" 79 %%Page: "75" 79 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (75) 300.44 35.33 T (Server Procedures) 72 713.33 T 0 F -0.17 (The following sections define the RPC procedures supplied by a MOUNT version 3 protocol server. The RPC proce-) 72 695.33 P -0.09 (dure number is given at the top of the page with the name and version. The SYNOPSIS provides the name of the pro-) 72 683.33 P -0.22 (cedure, the list of the names of the arguments, the list of the names of the results, followed by the XDR argument dec-) 72 671.33 P 0.04 (larations and results declarations. The information in the SYNOPSIS is specified in RPC Data Description Language) 72 659.33 P 0.48 (as defined in) 72 647.33 P 3 F 0.48 ([RFC1014]) 127 647.33 P 0 F 0.48 (. The DESCRIPTION section tells what the procedure is expected to do and how its argu-) 173.65 647.33 P 0.25 (ments and results are used. The ERRORS section lists the errors returned for specific types of failures. The IMPLE-) 72 635.33 P (MENTATION field describes how the procedure is expected to work and how it should be used by clients.) 72 623.33 T 4 F (program MOUNT_PROGRAM {) 90 607.33 T (version MOUNT_V3 {) 108 596.33 T (void) 126 585.33 T ( MOUNTPROC3_NULL\050void\051) 126 574.33 T (= 0;) 288 574.33 T (mountres3) 126 563.33 T ( MOUNTPROC3_MNT\050dirpath\051) 126 552.33 T (= 1;) 288 552.33 T (mountlist) 126 541.33 T ( MOUNTPROC3_DUMP\050void\051) 126 530.33 T (= 2;) 288 530.33 T (void) 126 519.33 T ( MOUNTPROC3_UMNT\050dirpath\051) 126 508.33 T (= 3;) 288 508.33 T (void) 126 497.33 T ( MOUNTPROC3_UMNTALL\050void\051) 126 486.33 T (= 4;) 288 486.33 T (exports) 126 475.33 T ( MOUNTPROC3_EXPORT\050void\051) 126 464.33 T (= 5;) 288 464.33 T (} = 3;) 108 453.33 T (} = 100005;) 90 442.33 T FMENDPAGE %%EndPage: "75" 80 %%Page: "76" 80 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (76) 300.44 35.33 T (Version 3) 495.01 35.33 T 2 12 Q (Procedure) 72 712 T (0) 153.17 712 T (NULL) 290.73 712 T 2 10 Q (Null: Do nothing) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (void) 90 651.33 T (MOUNTPROC3_NULL\050void\051 = 0;) 90 639.33 T 8 F (DESCRIPTION) 72 617.33 T 0 F (Procedure) 72 599.33 T 4 F (NULL) 115.02 599.33 T 0 F ( does not do any work. It is made available to allow server response testing and timing.) 139 599.33 T 8 F (IMPLEMENTATION) 72 577.33 T 0 F -0.09 (It is important that this procedure do no work at all so that it can be used to measure the overhead of processing a ser-) 72 559.33 P -0.2 (vice request. By convention, the) 72 547.33 P 4 F -0.48 (NULL) 202.29 547.33 P 0 F -0.2 ( procedure should never require any authentication. A server may choose to ig-) 226.28 547.33 P 0.27 (nore this convention, in a more secure implementation, where responding to the) 72 535.33 P 4 F 0.65 (NULL) 396.7 535.33 P 0 F 0.27 ( procedure call acknowledges) 420.68 535.33 P (the existence of a resource to an unauthenticated client.) 72 523.33 T 8 F (ERRORS) 72 501.33 T 0 F -0.4 (Since the) 72 483.33 P 4 F -0.96 (NULL) 110.62 483.33 P 0 F -0.4 ( procedure takes no MOUNT protocol arguments and returns no MOUNT protocol response, it can not) 134.61 483.33 P 0.83 (return a MOUNT protocol error. However, it is possible that some server implementations may return RPC errors) 72 471.33 P (based on security and authentication requirements.) 72 459.33 T FMENDPAGE %%EndPage: "76" 81 %%Page: "77" 81 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (77) 300.44 35.33 T 2 12 Q (Procedure) 72 712 T (1) 153.17 712 T (MNT) 293.73 712 T 2 10 Q (Mount: Add mount entry) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (mountres3) 90 651.33 T (MOUNTPROC3_MNT\050dirpath\051 = 1;) 90 639.33 T (struct mountres3_ok {) 90 615.33 T (fhandle3) 108 603.33 T (fhandle;) 180 603.33 T (int) 108 591.33 T (auth_flavors<>;) 180 591.33 T (};) 90 579.33 T (union mountres3 switch \050mountstat3 fhs_status\051 {) 90 555.33 T (case MNT_OK:) 90 543.33 T (mountres3_ok mountinfo;) 108 531.33 T (default:) 90 519.33 T (void;) 108 507.33 T (};) 90 495.33 T 8 F (DESCRIPTION) 72 473.33 T 0 F 0.2 (Procedure) 72 455.33 P 4 F 0.48 (MNT) 115.22 455.33 P 0 F 0.2 ( maps a pathname on the server to a file handle. The pathname is an ASCII string that describes a di-) 133.21 455.33 P -0.29 (rectory on the server. If the call is successful \050) 72 443.33 P 4 F -0.7 (MNT3_OK) 253.65 443.33 P 0 F -0.29 (\051, the server returns an NFS version 3 protocol file handle and) 295.63 443.33 P 0.36 (a vector of RPC authentication flavors that are supported with the client\325s use of the file handle \050or any file handles) 72 431.33 P (derived from it\051. The authentication flavors are defined in Section 7.2 and section 9 of Internet RFC 1057.) 72 419.33 T 8 F (IMPLEMENTATION) 72 397.33 T 0 F -0.29 (If) 72 379.33 P 5 F -0.71 (mountres3.fhs_status) 80.86 379.33 P 0 F -0.29 ( is) 200.79 379.33 P 4 F -0.71 (MNT3_OK) 211.87 379.33 P 0 F -0.29 (, then) 253.85 379.33 P 5 F -0.71 (mountres3.mountinfo) 277.96 379.33 P 0 F -0.29 ( contains the file handle for the direc-) 391.9 379.33 P 0.22 (tory and a list of acceptable authentication flavors. This file handle may only be used in the NFS version 3 protocol.) 72 367.33 P -0.15 (This procedure also results in the server adding a new entry to its mount list recording that this client has mounted the) 72 355.33 P (directory.) 72 343.33 T 4 F (AUTH_UNIX) 113.08 343.33 T 0 F ( authentication or better is required.) 167.05 343.33 T 8 F (ERRORS) 72 321.33 T 4 F (MNT3ERR_NOENT) 90 305.33 T (MNT3ERR_IO) 90 293.33 T (MNT3ERR_ACCES) 90 281.33 T (MNT3ERR_NOTDIR) 90 269.33 T (MNT3ERR_NAMETOOLONG) 90 257.33 T FMENDPAGE %%EndPage: "77" 82 %%Page: "78" 82 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (78) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 12 Q (Procedure) 72 712 T (2) 153.84 712 T (DUMP) 288.74 712 T 2 10 Q (Dump: Return mount entries) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (mountlist) 90 651.33 T (MOUNTPROC3_DUMP\050void\051 = 2;) 90 639.33 T (typedef struct mountbody *mountlist;) 90 615.33 T (struct mountbody {) 90 591.33 T (name) 108 579.33 T (ml_hostname;) 180 579.33 T (dirpath) 108 567.33 T (ml_directory;) 180 567.33 T (mountlist) 108 555.33 T (ml_next;) 180 555.33 T (};) 90 543.33 T 8 F (DESCRIPTION) 72 521.33 T 0 F 0.51 (Procedure) 72 503.33 P 4 F 1.24 (DUMP) 115.53 503.33 P 0 F 0.51 ( returns the list of remotely mounted file systems. The mountlist contains one entry for each client) 139.52 503.33 P (host name and directory pair.) 72 491.33 T 8 F (IMPLEMENTATION) 72 469.33 T 0 F -0.1 (This list is derived from a list maintained on the server of clients that have requested file handles with the) 72 451.33 P 4 F -0.25 (MNT) 494.09 451.33 P 0 F -0.1 ( proce-) 512.08 451.33 P -0.59 (dure. Entries are removed from this list only when a client calls the) 72 439.33 P 4 F -1.42 (UMNT) 335.21 439.33 P 0 F -0.59 ( or) 359.2 439.33 P 4 F -1.42 (UMNTALL) 371.33 439.33 P 0 F -0.59 ( procedure. Entries may become) 413.31 439.33 P 0.12 (stale if a client crashes and does not issue either) 72 427.33 P 4 F 0.29 (UMNT) 266.95 427.33 P 0 F 0.12 ( calls for all of the file systems that it had previously mounted) 290.93 427.33 P (or a) 72 415.33 T 4 F (UMNTALL) 89.76 415.33 T 0 F ( to remove all entries that existed for it on the server.) 131.74 415.33 T 8 F (ERRORS) 72 393.33 T 0 F 0.44 (There are no MOUNT protocol errors which can be returned from this procedure. However, RPC errors may be re-) 72 375.33 P (turned for authentication or other RPC failures.) 72 363.33 T FMENDPAGE %%EndPage: "78" 83 %%Page: "79" 83 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (79) 300.44 35.33 T 2 12 Q (Procedure) 72 712 T (3) 153.17 712 T (UMNT) 289.4 712 T 2 10 Q (Unmount: Remove mount entry) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (void) 90 651.33 T (MOUNTPROC3_UMNT\050dirpath\051 = 3;) 90 639.33 T 8 F (DESCRIPTION) 72 617.33 T 0 F -0.16 (Procedure) 72 599.33 P 4 F -0.38 (UMNT) 114.86 599.33 P 0 F -0.16 ( removes the mount list entry for the directory that was previously the subject of a) 138.85 599.33 P 4 F -0.38 (MNT) 466.68 599.33 P 0 F -0.16 ( call from this) 484.67 599.33 P (client.) 72 587.33 T 4 F (AUTH_UNIX) 99.21 587.33 T 0 F ( authentication or better is required.) 153.18 587.33 T 8 F (IMPLEMENTATION) 72 565.33 T 0 F -0 (Typically, server implementations have maintained a list of clients which have file systems mounted. In the past, this) 72 547.33 P (list has been used to inform clients that the server was going to be shutdown.) 72 535.33 T 8 F (ERRORS) 72 513.33 T 0 F 0.44 (There are no MOUNT protocol errors which can be returned from this procedure. However, RPC errors may be re-) 72 495.33 P (turned for authentication or other RPC failures.) 72 483.33 T FMENDPAGE %%EndPage: "79" 84 %%Page: "80" 84 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (80) 300.44 35.33 T (Version 3) 495.01 35.33 T 6 12 Q (Procedure) 72 712 T (4) 153.84 712 T (UMNTALL) 276.07 712 T 2 10 Q (Unmount all: Remove all mount entries) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (void) 90 651.33 T (MOUNTPROC3_UMNTALL\050void\051 = 4;) 90 639.33 T 8 F (DESCRIPTION) 72 617.33 T 0 F -0.56 (Procedure) 72 599.33 P 4 F -1.35 (UMNTALL) 114.45 599.33 P 0 F -0.56 ( removes all of the mount entries for this client previously recorded by calls to) 156.43 599.33 P 4 F -1.35 (MNT) 463.61 599.33 P 0 F -0.56 (.) 481.6 599.33 P 4 F -1.35 (AUTH_UNIX) 486.03 599.33 P 0 F (authentication or better is required.) 72 587.33 T 8 F (IMPLEMENTATION) 72 565.33 T 0 F 0.56 (This procedure should be used by clients when they are recovering after a system shutdown. If the client could not) 72 547.33 P -0.25 (successfully unmount all of its file systems before being shutdown or the client crashed because of a software or hard-) 72 535.33 P -0.03 (ware problem, there may be servers which still have mount entries for this client. This is an easy way for the client to) 72 523.33 P 0.19 (inform all servers at once that it does not have any mounted file systems. However, since this procedure is generally) 72 511.33 P (implemented using broadcast RPC, it is only of limited usefullness.) 72 499.33 T 8 F (ERRORS) 72 477.33 T 0 F 0.44 (There are no MOUNT protocol errors which can be returned from this procedure. However, RPC errors may be re-) 72 459.33 P (turned for authentication or other RPC failures.) 72 447.33 T FMENDPAGE %%EndPage: "80" 85 %%Page: "81" 85 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (81) 300.44 35.33 T 2 12 Q (Procedure) 72 712 T (5) 153.17 712 T (EXPORT) 282.06 712 T 2 10 Q (Export: Return export list) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (exports) 90 651.33 T (MOUNTPROC3_EXPORT\050void\051 = 5;) 90 639.33 T (typedef struct groupnode *groups;) 90 615.33 T (struct groupnode {) 90 591.33 T (name) 108 579.33 T (gr_name;) 162 579.33 T (groups) 108 567.33 T (gr_next;) 162 567.33 T (};) 90 555.33 T (typedef struct exportnode *exports;) 90 531.33 T (struct exportnode {) 90 507.33 T (dirpath) 108 495.33 T (ex_dir;) 162 495.33 T (groups) 108 483.33 T (ex_groups;) 162 483.33 T (exports) 108 471.33 T (ex_next;) 162 471.33 T (};) 90 459.33 T 8 F (DESCRIPTION) 72 437.33 T 0 F -0.31 (Procedure) 72 419.33 P 4 F -0.75 (EXPORT) 114.7 419.33 P 0 F -0.31 ( returns a list of all the exported file systems and which clients are allowed to mount each one. The) 150.68 419.33 P -0.42 (names in the group list are implementation-specific and cannot be directly interpreted by clients. These names can rep-) 72 407.33 P (resent hosts or groups of hosts.) 72 395.33 T 8 F (IMPLEMENTATION) 72 373.33 T 0 F 0.41 (This procedure generally returns the contents of a list of) 72 355.33 P 3 F 0.41 (shared) 302.59 355.33 P 0 F 0.41 ( or) 329.8 355.33 P 3 F 0.41 (exported) 343.94 355.33 P 0 F 0.41 ( file systems. These are the file systems) 378.91 355.33 P (which are made available to NFS version 3 protocol clients.) 72 343.33 T 8 F (ERRORS) 72 321.33 T 0 F 0.44 (There are no MOUNT protocol errors which can be returned from this procedure. However, RPC errors may be re-) 72 303.33 P (turned for authentication or other RPC failures.) 72 291.33 T FMENDPAGE %%EndPage: "81" 86 %%Page: "82" 86 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (82) 300.44 35.33 T (Version 3) 495.01 35.33 T FMENDPAGE %%EndPage: "82" 87 %%Page: "83" 87 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (83) 300.44 35.33 T 2 12 Q (Appendix II: Lock manager protocol) 72 712 T 0 10 Q 0.5 (Because the NFS version 2 protocol as well as the NFS version 3 protocol is stateless, an additional Network Lock) 72 693.33 P -0.21 (Manager \050NLM\051 protocol is required to support locking of NFS-mounted files. The NLM version 3 protocol, which is) 72 681.33 P (used with the NFS version 2 protocol, is documented in) 72 669.33 T 3 F ([X/OpenNFS]) 297.15 669.33 T 0 F (.) 353.23 669.33 T 0.1 (Some of the changes in the NFS version 3 protocol require a new version of the NLM protocol. This new protocol is) 72 651.33 P (the NLM version 4 protocol. The following table summarizes the correspondence between NFS and NLM versions.) 72 639.33 T 0.29 (This appendix only discusses the differences between the NLM version 3 protocol and the NLM version 4 protocol.) 72 501.33 P 0.16 (As in the NFS version 3 protocol, almost all the names in the NLM version 4 protocol have been changed to include) 72 489.33 P (a version number. This appendix does not discuss changes that consist solely of a name change.) 72 477.33 T 6 12 Q (NFS and NLM pr) 209.82 616 T (otocol compatibility) 300.57 616 T 0 F (NFS) 259 590 T (version) 252.35 576 T (NLM) 328.67 590 T (version) 324.35 576 T (2) 267 552 T (1, 3) 333.01 552 T (3) 267 530 T (4) 339 530 T 234 605.75 234 522.25 2 L V 0.5 H 0 Z N 306 606.25 306 521.75 2 L V N 378 605.75 378 522.25 2 L V N 233.75 606 378.25 606 2 L V N 234.25 567.25 377.75 567.25 2 L V N 234.25 564.75 377.75 564.75 2 L V N 233.75 544 378.25 544 2 L V N 233.75 522 378.25 522 2 L V N FMENDPAGE %%EndPage: "83" 88 %%Page: "84" 88 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (84) 300.44 35.33 T (Version 3) 495.01 35.33 T 2 12 Q (RPC Information) 72 712 T 2 10 Q (Authentication) 72 689.33 T 0 F 2.54 (The NLM service uses) 72 671.33 P 4 F 6.1 (AUTH_NONE) 175.43 671.33 P 0 F 2.54 ( in the) 229.4 671.33 P 4 F 6.1 (NULL) 264.51 671.33 P 0 F 2.54 ( procedure.) 288.5 671.33 P 4 F 6.1 (AUTH_UNIX) 341.04 671.33 P 0 F 2.54 (,) 395.01 671.33 P 4 F 6.1 (AUTH_SHORT) 402.55 671.33 P 0 F 2.54 (,) 462.51 671.33 P 4 F 6.1 (AUTH_DES) 470.05 671.33 P 0 F 2.54 (, and) 518.03 671.33 P 4 F (AUTH_KERB) 72 659.33 T 0 F ( are used for all other procedures. Other authentication types may be supported in the future.) 125.97 659.33 T 2 F (Constants) 72 637.33 T 0 F (These are the RPC constants needed to call the NLM service. They are given in decimal.) 72 619.33 T 4 F (PROGRAM) 90 603.33 T (100021) 144.72 603.33 T (VERSION) 90 591.33 T (4) 144.72 591.33 T 2 F (Transport Address) 72 569.33 T 0 F -0.17 (The NLM service is normally supported over the TCP and UDP protocols. The rpcbind daemon should be queried for) 72 551.33 P (the correct transport address.) 72 539.33 T 2 F (Basic Data Types) 72 517.33 T 5 F (uint64) 72 495.33 T 4 F (typedef unsigned hyper uint64;) 90 483.33 T 5 F (int64) 72 461.33 T 4 F (typedef hyper int64;) 90 449.33 T 5 F (uint32) 72 427.33 T 4 F (typedef unsigned long uint32;) 90 415.33 T 5 F (int32) 72 393.33 T 4 F (typedef long int32;) 90 381.33 T 0 F (These types are new for the NLM version 4 protocol. They are the same as in the NFS version 3 protocol.) 72 363.33 T 5 F (nlm4_stats) 72 341.33 T 4 F (enum nlm4_stats {) 90 329.33 T (NLM4_GRANTED) 108 317.33 T (= 0,) 270 317.33 T (NLM4_DENIED) 108 305.33 T (= 1,) 270 305.33 T (NLM4_DENIED_NOLOCKS) 108 293.33 T (= 2,) 270 293.33 T (NLM4_BLOCKED) 108 281.33 T (= 3,) 270 281.33 T (NLM4_DENIED_GRACE_PERIOD) 108 269.33 T (= 4,) 270 269.33 T (NLM4_DEADLCK) 108 257.33 T (= 5,) 270 257.33 T (NLM4_ROFS) 108 245.33 T (= 6,) 270 245.33 T (NLM4_STALE_FH) 108 233.33 T (= 7,) 270 233.33 T (NLM4_FBIG) 108 221.33 T (= 8,) 270 221.33 T (NLM4_FAILED) 108 209.33 T (= 9) 270 209.33 T (};) 90 197.33 T 5 F 0.15 (Nlm4_stats) 72 179.33 P 0 F 0.06 ( indicates the success or failure of a call. This version contains several new error codes, so that clients) 131.97 179.33 P (can provide more precise failure information to applications.) 72 167.33 T 4 F (NLM4_GRANTED) 90 151.33 T 0 F (The call completed successfully.) 113.04 139.33 T 4 F (NLM4_DENIED) 90 125.33 T 0 F 0.56 (The call failed. For attempts to set a lock, this status implies that if the client retries the call later, it may) 113.04 113.33 P (succeed.) 113.04 101.33 T 4 F (NLM4_DENIED_NOLOCKS) 90 87.33 T 0 F (The call failed because the server could not allocate the necessary resources.) 113.04 75.33 T FMENDPAGE %%EndPage: "84" 89 %%Page: "85" 89 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (85) 300.44 35.33 T 4 F (NLM4_BLOCKED) 90 713.33 T 0 F -0.2 (Indicates that a blocking request cannot be granted immediately. The server will issue an) 113.04 701.33 P 4 F -0.48 (NLM4_GRANTED) 468.04 701.33 P 0 F (callback to the client when the lock is granted.) 113.04 689.33 T 4 F (NLM4_DENIED_GRACE_PERIOD) 90 675.33 T 0 F 0.49 (The call failed because the server is reestablishing old locks after a reboot and is not yet ready to resume) 113.04 663.33 P (normal service.) 113.04 651.33 T 4 F (NLM4_DEADLCK) 90 637.33 T 0 F (The request could not be granted and blocking would cause a deadlock.) 113.04 625.33 T 4 F (NLM4_ROFS) 90 611.33 T 0 F -0.61 (The call failed because the remote file system is read-only. For example, some server implementations might) 113.04 599.33 P (not support exclusive locks on read-only file systems.) 113.04 587.33 T 4 F (NLM4_STALE_FH) 90 573.33 T 0 F -0.55 (The call failed because it uses an invalid file handle. This can happen if the file has been removed or if access) 113.04 561.33 P (to the file has been revoked on the server.) 113.04 549.33 T 4 F (NLM4_FBIG) 90 535.33 T 0 F (The call failed because it specified a length or offset that exceeds the range supported by the server.) 113.04 523.33 T 4 F (NLM4_FAILED) 90 509.33 T 0 F 0.35 (The call failed for some reason not already listed. The client should take this status as a strong hint not to) 113.04 497.33 P (retry the request.) 113.04 485.33 T 5 F (nlm4_holder) 72 463.33 T 4 F (struct nlm4_holder {) 90 451.33 T (bool exclusive;) 108 439.33 T (int32 svid;) 108 427.33 T (netobj oh;) 108 415.33 T (uint64 l_offset;) 108 403.33 T (uint64 l_len;) 108 391.33 T (};) 90 379.33 T 0 F 0.08 (This structure indicates the holder of a lock. The) 72 361.33 P 5 F 0.2 (exclusive) 269.26 361.33 P 0 F 0.08 ( field tells whether the holder has an exclusive lock or) 323.23 361.33 P -0.42 (a shared lock. The) 72 349.33 P 5 F -1.02 (svid) 146.07 349.33 P 0 F -0.42 ( field identifies the process that is holding the lock. The) 170.06 349.33 P 5 F -1.02 (oh) 390.24 349.33 P 0 F -0.42 ( field is an opaque object that iden-) 402.24 349.33 P 0.1 (tifies the host that is holding the lock. The) 72 337.33 P 5 F 0.23 (l_len) 243.89 337.33 P 0 F 0.1 ( and) 273.88 337.33 P 5 F 0.23 (l_off) 293.5 337.33 P 0.23 (set) 323.48 337.33 P 0 F 0.1 ( fields identify the region that is locked. The only) 341.47 337.33 P -0.43 (difference between the NLM version 3 protocol and the NLM version 4 protocol is that in the NLM version 3 protocol,) 72 325.33 P (the) 72 313.33 T 5 F (l_len) 86.71 313.33 T 0 F ( and) 116.69 313.33 T 5 F (l_offset) 136.12 313.33 T 0 F ( fields are) 184.1 313.33 T 4 F (32) 226.01 313.33 T 0 F ( bits wide, while they are) 238 313.33 T 4 F (64) 340.98 313.33 T 0 F ( bits wide in the NLM version 4 protocol.) 352.98 313.33 T 5 F (nlm4_lock) 72 291.33 T 4 F (struct nlm4_lock {) 90 279.33 T (string caller_name;) 108 267.33 T (netobj fh;) 108 255.33 T (netobj oh;) 108 243.33 T (int32 svid;) 108 231.33 T (uint64 l_offset;) 108 219.33 T (uint64 l_len;) 108 207.33 T (};) 90 195.33 T 0 F 0.35 (This structure describes a lock request. The) 72 177.33 P 5 F 0.84 (caller_name) 250.41 177.33 P 0 F 0.35 ( field identifies the host that is making the request. The) 316.38 177.33 P 5 F 0.1 (fh) 72 165.33 P 0 F 0.04 ( field identifies the file to lock. The) 83.99 165.33 P 5 F 0.1 (oh) 228.42 165.33 P 0 F 0.04 ( field is an opaque object that identifies the host that is making the request,) 240.41 165.33 P 0.34 (and the) 72 153.33 P 5 F 0.8 (svid) 104.31 153.33 P 0 F 0.34 ( field identifies the process that is making the request. The) 128.3 153.33 P 5 F 0.8 (l_offset) 367.93 153.33 P 0 F 0.34 ( and) 415.9 153.33 P 5 F 0.8 (l_len) 436 153.33 P 0 F 0.34 ( fields identify the) 465.99 153.33 P (region of the file that the lock controls. A) 72 141.33 T 5 F (l_len) 240.22 141.33 T 0 F ( of) 270.2 141.33 T 4 F (0) 283.52 141.33 T 0 F ( means \322to end of file\323.) 289.52 141.33 T -0.28 (There are two differences between the NLM version 3 protocol and the NLM version 4 protocol versions of this struc-) 72 123.33 P 0.3 (ture. First, in the NLM version 3 protocol, the length and offset are) 72 111.33 P 4 F 0.71 (32) 346.22 111.33 P 0 F 0.3 ( bits wide, while they are) 358.21 111.33 P 4 F 0.71 (64) 462.97 111.33 P 0 F 0.3 ( bits wide in the) 474.96 111.33 P -0.01 (NLM version 4 protocol. Second, in the NLM version 3 protocol, the file handle is a fixed-length NFS version 2 pro-) 72 99.33 P 0.42 (tocol file handle, which is encoded as a byte count followed by a byte array. In the NFS version 3 protocol, the file) 72 87.33 P 0.18 (handle is already variable-length, so it is copied directly into the) 72 75.33 P 5 F 0.44 (fh) 333.29 75.33 P 0 F 0.18 ( field. That is, the first four bytes of the) 345.28 75.33 P 5 F 0.44 (fh) 507 75.33 P 0 F 0.18 ( field) 519 75.33 P FMENDPAGE %%EndPage: "85" 90 %%Page: "86" 90 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (86) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 F -0.27 (are the same as the byte count in an NFS version 3 protocol) 72 713.33 P 5 F -0.65 (nfs_fh3) 309.15 713.33 P 0 F -0.27 (. The rest of the) 351.13 713.33 P 5 F -0.65 (fh) 415.28 713.33 P 0 F -0.27 ( field contains the byte array) 427.27 713.33 P (from the NFS version 3 protocol) 72 701.33 T 5 F (nfs_fh3) 204.7 701.33 T 0 F (.) 246.67 701.33 T 5 F (nlm4_share) 72 679.33 T 4 F (struct nlm4_share {) 90 667.33 T (string caller_name;) 108 655.33 T (netobj fh;) 108 643.33 T (netobj oh;) 108 631.33 T (fsh4_mode mode;) 108 619.33 T (fsh4_access access;) 108 607.33 T (};) 90 595.33 T 0 F (This structure is used to support DOS file sharing. The) 72 573.33 T 5 F (caller_name) 293.25 573.33 T 0 F ( field identifies the host making the request.) 359.21 573.33 T -0.53 (The) 72 561.33 P 5 F -1.26 (fh) 89.51 561.33 P 0 F -0.53 ( field identifies the file to be operated on. The) 101.51 561.33 P 5 F -1.26 (oh) 281.94 561.33 P 0 F -0.53 ( field is an opaque object that identifies the host that is making) 293.94 561.33 P (the request. The) 72 549.33 T 5 F (mode) 138.61 549.33 T 0 F ( and) 162.6 549.33 T 5 F (access) 182.03 549.33 T 0 F ( fields specify the file-sharing and access modes. The encoding of) 218.01 549.33 T 5 F (fh) 483.91 549.33 T 0 F ( is a byte) 495.91 549.33 T (count, followed by the file handle byte array. See the description of) 72 537.33 T 5 F (nlm4_lock) 344.02 537.33 T 0 F ( for more details.) 397.99 537.33 T FMENDPAGE %%EndPage: "86" 91 %%Page: "87" 91 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (87) 300.44 35.33 T (NLM Procedures) 72 713.33 T 0 F -0.21 (The procedures in the NLM version 4 protocol are semantically the same as those in the NLM version 3 protocol. The) 72 695.33 P -0.27 (only semantic difference is the addition of a) 72 683.33 P 4 F -0.64 (NULL) 248.06 683.33 P 0 F -0.27 ( procedure that can be used to test for server responsiveness. A syn-) 272.05 683.33 P -0.17 (tactic change is that the procedures were renamed to avoid name conflicts with the values of) 72 671.33 P 5 F -0.41 (nlm4_stats) 440.67 671.33 P 0 F -0.17 (. Thus the) 500.64 671.33 P (procedure definition is as follows.) 72 659.33 T 4 F (version NLM4_VERS {) 108 643.33 T (void) 126 631.33 T (NLMPROC4_NULL\050void\051) 144.72 619.33 T (= 0;) 378 619.33 T (nlm4_testres) 126 607.33 T (NLMPROC4_TEST\050nlm4_testargs\051) 144.72 595.33 T (= 1;) 378 595.33 T (nlm4_res) 126 583.33 T (NLMPROC4_LOCK\050nlm4_lockargs\051) 144.72 571.33 T (= 2;) 378 571.33 T (nlm4_res) 126 559.33 T (NLMPROC4_CANCEL\050nlm4_cancargs\051) 144.72 547.33 T (= 3;) 378 547.33 T (nlm4_res) 126 535.33 T (NLMPROC4_UNLOCK\050nlm4_unlockargs\051) 144.72 523.33 T (= 4;) 378 523.33 T (nlm4_res) 126 511.33 T (NLMPROC4_GRANTED\050nlm4_testargs\051) 144.72 499.33 T (= 5;) 378 499.33 T (void) 126 487.33 T (NLMPROC4_TEST_MSG\050nlm4_testargs\051) 144.72 475.33 T (= 6;) 378 475.33 T (void) 126 463.33 T (NLMPROC4_LOCK_MSG\050nlm4_lockargs\051) 144.72 451.33 T (= 7;) 378 451.33 T (void) 126 439.33 T (NLMPROC4_CANCEL_MSG\050nlm4_cancargs\051) 144.72 427.33 T (= 8;) 378 427.33 T (void) 126 415.33 T (NLMPROC4_UNLOCK_MSG\050nlm4_unlockargs\051) 144.72 403.33 T (= 9;) 378 403.33 T (void) 126 391.33 T (NLMPROC4_GRANTED_MSG\050nlm4_testargs\051) 144.72 379.33 T (= 10;) 378 379.33 T (void) 126 367.33 T (NLMPROC4_TEST_RES\050nlm4_testres\051) 144.72 355.33 T (= 11;) 378 355.33 T (void) 126 343.33 T (NLMPROC4_LOCK_RES\050nlm4_res\051) 144.72 331.33 T (= 12;) 378 331.33 T (void) 126 319.33 T (NLMPROC4_CANCEL_RES\050nlm4_res\051) 144.72 307.33 T (= 13;) 378 307.33 T (void) 126 295.33 T (NLMPROC4_UNLOCK_RES\050nlm4_res\051) 144.72 283.33 T (= 14;) 378 283.33 T (void) 126 271.33 T (NLMPROC4_GRANTED_RES\050nlm4_res\051) 144.72 259.33 T (= 15;) 378 259.33 T (nlm4_shareres) 126 247.33 T (NLMPROC4_SHARE\050nlm4_shareargs\051) 144.72 235.33 T (= 20;) 378 235.33 T (nlm4_shareres) 126 223.33 T (NLMPROC4_UNSHARE\050nlm4_shareargs\051) 144.72 211.33 T (= 21;) 378 211.33 T (nlm4_res) 126 199.33 T (NLMPROC4_NM_LOCK\050nlm4_lockargs\051) 144.72 187.33 T (= 22;) 378 187.33 T (void) 126 175.33 T (NLMPROC4_FREE_ALL\050nlm4_notify\051) 144.72 163.33 T (= 23;) 378 163.33 T (} = 4;) 108 151.33 T FMENDPAGE %%EndPage: "87" 92 %%Page: "88" 92 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (88) 300.44 35.33 T (Version 3) 495.01 35.33 T 2 12 Q (Procedure) 72 712 T (0) 153.17 712 T (NULL) 289.29 712 T 2 10 Q (NULL: Do nothing) 72 689.33 T 8 F (SYNOPSIS) 72 667.33 T 4 F (void) 90 651.33 T (NLMPROC4_NULL\050void\051 = 0;) 90 639.33 T 8 F (DESCRIPTION) 72 617.33 T 0 F -0.56 (The) 72 599.33 P 4 F -1.35 (NULL) 89.48 599.33 P 0 F -0.56 ( procedure does no work. It is made available in all RPC services to allow server response testing and timing.) 113.47 599.33 P 8 F (IMPLEMENTATION) 72 577.33 T 0 F -0.09 (It is important that this procedure do no work at all so that it can be used to measure the overhead of processing a ser-) 72 559.33 P (vice request. By convention, the) 72 547.33 T 4 F (NULL) 203.3 547.33 T 0 F ( procedure should never require any authentication.) 227.29 547.33 T 8 F (ERRORS) 72 525.33 T 0 F 0.31 (It is possible that some server implementations may return RPC errors based on security and authentication require-) 72 507.33 P (ments.) 72 495.33 T FMENDPAGE %%EndPage: "88" 93 %%Page: "89" 93 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (89) 300.44 35.33 T (Implementation issues) 72 713.33 T 8 F (64-bit offsets and lengths) 72 691.33 T 0 F -0.12 (Some NFS version 3 protocol servers can only support requests where the file offset or length fits in) 72 673.33 P 4 F -0.29 (32) 472.86 673.33 P 0 F -0.12 ( or fewer bits.) 484.86 673.33 P 0.56 (For these servers, the lock manager will have the same restriction. If such a lock manager receives a request that it) 72 661.33 P (cannot handle \050because the offset or length uses more than) 72 649.33 T 4 F (32) 308.48 649.33 T 0 F ( bits\051, it should return the error,) 320.47 649.33 T 4 F (NLM4_FBIG) 448.44 649.33 T 0 F (.) 502.41 649.33 T 8 F (file handles) 72 627.33 T 0 F 0.19 (The change in the file handle format from the NFS version 2 protocol to the NFS version 3 protocol complicates the) 72 609.33 P -0.2 (lock manager. First, the lock manager needs some way to tell when an NFS version 2 protocol file handle refers to the) 72 597.33 P -0.49 (same file as an NFS version 3 protocol file handle. \050This is assuming that the lock manager supports both NLM version) 72 585.33 P -0.56 (3 protocol clients and NLM version 4 protocol clients.\051 Second, if the lock manager runs the file handle through a hash-) 72 573.33 P -0.13 (ing function, the hashing function may need to be retuned to work with NFS version 3 protocol file handles as well as) 72 561.33 P (NFS version 2 protocol file handles.) 72 549.33 T FMENDPAGE %%EndPage: "89" 94 %%Page: "90" 94 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (90) 300.44 35.33 T (Version 3) 495.01 35.33 T FMENDPAGE %%EndPage: "90" 95 %%Page: "91" 95 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T (Version 3) 72 35.33 T (91) 300.44 35.33 T 2 12 Q (Appendix III: Bibliography) 72 712 T 0 10 Q ([Corbin]) 72 691.33 T (Corbin, John,) 171 691.33 T 2.28 (The Art of Distributed Programming\321Programming T) 171 680.33 P 2.28 (echniques for Remote Procedure) 402.42 680.33 P (Calls) 171 669.33 T (Springer) 171 658.33 T (-V) 205.22 658.33 T (erlag, New Y) 214.66 658.33 T (ork, New Y) 267.22 658.33 T (ork. 1991.) 313.12 658.33 T 3 F -0.16 (Basic description of RPC and XDR and how to pr) 171 647.33 P -0.16 (ogram distributed applications using them.) 368.23 647.33 P 0 F ([Glover]) 72 628.33 T (Glover) 171 628.33 T (, Fred,) 198.35 628.33 T (\322TNFS Protocol Speci\336cation,\323) 171 617.33 T (T) 171 606.33 T (rusted System Interest Group, INTERNET) 176.76 606.33 T (-DRAFT) 346.55 606.33 T (, May 24, 1992.) 381.9 606.33 T 3 F (Pr) 171 595.33 T (oposed draft standar) 180.62 595.33 T (d for security extensions to NFS.) 263.55 595.33 T 0 F ([Israel]) 72 576.33 T (Israel, Robert K., Sandra Jett, James Pownell, Geor) 171 576.33 T (ge M. Ericson,) 376.23 576.33 T (\322Eliminating Data Copies in UNIX-based NFS Servers,\323) 171 565.33 T 3 F (Uniforum Confer) 171 554.33 T (ence Pr) 239.76 554.33 T (oceedings) 270.2 554.33 T 0 F (, San Francisco, CA, February 27 - March 2, 1989.) 310.16 554.33 T 3 F (Describes two methods for reducing data copies in NFS server code.) 171 543.33 T 0 F ([Jacobson]) 72 524.33 T (Jacobson, V) 171 524.33 T (.,) 218.56 524.33 T (\322Congestion Control and A) 171 513.33 T (voidance,\323) 279.92 513.33 T 3 F (Pr) 171 502.33 T (oc. ACM SIGCOMM \32488) 180.62 502.33 T 0 F (, Stanford, CA, August 1988) 280.55 502.33 T (.) 395.21 502.33 T 3 F 1.64 (The paper describing impr) 171 491.33 P 1.64 (ovements to TCP to allow use over W) 282.43 491.33 P 1.64 (ide Ar) 443.56 491.33 P 1.64 (ea Networks and) 469.54 491.33 P 0.59 (thr) 171 480.33 P 0.59 (ough gateways connecting networks of varying capacity) 182.29 480.33 P 0.59 (. This work was a starting point) 409.57 480.33 P (for the NFS Dynamic Retransmission work.) 171 469.33 T 0 F ([Juszczak]) 72 450.33 T (Juszczak, Chet,) 171 450.33 T (\322Improving the Performance and Correctness of an NFS Server) 171 439.33 T (,\323) 424.29 439.33 T 3 F 1.12 (USENIX Confer) 171 428.33 P 1.12 (ence Pr) 236.43 428.33 P 1.12 (oceedings) 267.99 428.33 P 0 F 1.12 (, USENIX Association, Berkeley) 307.96 428.33 P 1.12 (, CA, June 1990, pages) 443.08 428.33 P (53-63.) 171 417.33 T 3 F 0.38 (Describes r) 171 406.33 P 0.38 (eply cache implementation that avoids work in the server by handling duplicate) 217.37 406.33 P 2.97 (r) 171 395.33 P 2.97 (equests. Mor) 174.52 395.33 P 2.97 (e important, though listed as a side-effect, the r) 228.75 395.33 P 2.97 (eply cache aids in the) 441.51 395.33 P (avoidance of destructive non-idempotent operation r) 171 384.33 T (e-application\321impr) 381.32 384.33 T (oving corr) 462.02 384.33 T (ectness.) 503.57 384.33 T 0 F ([Kazar]) 72 365.33 T (Kazar) 171 365.33 T (, Michael Leon,) 194.46 365.33 T (\322Synchronization and Caching Issues in the Andrew File System,\323) 171 354.33 T 3 F -0.19 (USENIX Confer) 171 343.33 P -0.19 (ence Pr) 235.12 343.33 P -0.19 (oceedings) 265.36 343.33 P 0 F -0.19 (, USENIX Association, Berkeley) 305.33 343.33 P -0.19 (, CA, Dallas W) 436.51 343.33 P -0.19 (inter 1988,) 496.89 343.33 P (pages 27-36.) 171 332.33 T 3 F 0.07 (A description of the cache consistency scheme in AFS. Contrasted with other distributed \336le) 171 321.33 P (systems.) 171 310.33 T 0 F ([Macklem]) 72 291.33 T (Macklem, Rick,) 171 291.33 T (\322Lessons Learned T) 171 280.33 T (uning the 4.3BSD Reno Implementation of the NFS Protocol,\323) 251.14 280.33 T 3 F 2.3 (W) 171 269.33 P 2.3 (inter USENIX Confer) 178.78 269.33 P 2.3 (ence Pr) 269.07 269.33 P 2.3 (oceedings) 301.81 269.33 P 0 F 2.3 (, USENIX Association, Berkeley) 341.77 269.33 P 2.3 (, CA, January) 480.44 269.33 P (1991.) 171 258.33 T 3 F 1.37 (Describes performance work in tuning the 4.3BSD Reno NFS implementation. Describes) 171 247.33 P (performance impr) 171 236.33 T (ovement \050r) 243.08 236.33 T (educed CPU loading\051 thr) 285.73 236.33 T (ough elimination of data copies.) 386.68 236.33 T 0 F ([Mogul]) 72 217.33 T (Mogul, Jef) 171 217.33 T (frey C.,) 214.13 217.33 T (\322A Recovery Protocol for Spritely NFS,\323) 171 206.33 T 3 F 3.59 (USENIX File System W) 171 195.33 P 3.59 (orkshop Pr) 274.95 195.33 P 3.59 (oceedings) 322.87 195.33 P 0 F 3.59 (, Ann Arbor) 362.83 195.33 P 3.59 (, MI, USENIX Association,) 418.19 195.33 P (Berkeley) 171 184.33 T (, CA, May 1992.) 206.43 184.33 T 3 F 2.45 (Second paper on Spritely NFS pr) 171 173.33 P 2.45 (oposes a lease-based scheme for r) 315.3 173.33 P 2.45 (ecovering state of) 464.04 173.33 P (consistency pr) 171 162.33 T (otocol.) 228.09 162.33 T 0 F ([Nowicki]) 72 143.33 T (Nowicki, Bill,) 171 143.33 T (\322T) 171 132.33 T (ransport Issues in the Network File System,\323) 181.19 132.33 T (ACM SIGCOMM newsletter) 171 121.33 T 3 F (Computer Communication Review) 290.1 121.33 T 0 F (, April 1989.) 427.79 121.33 T 3 F (A brief description of the basis for the dynamic r) 171 110.33 T (etransmission work.) 365.24 110.33 T 0 F ([Pawlowski]) 72 91.33 T (Pawlowski, Brian, Ron Hixon, Mark Stein, Joseph T) 171 91.33 T (umminaro,) 381.36 91.33 T (\322Network Computing in the UNIX and IBM Mainframe Environment,\323) 171 80.33 T FMENDPAGE %%EndPage: "91" 96 %%Page: "92" 96 612 792 0 FMBEGINPAGE 0 X 0 K 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 10 Q (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T (92) 300.44 35.33 T (Version 3) 495.01 35.33 T 3 F (Uniforum \32489 Conf. Pr) 171 713.33 T (oc.) 262.25 713.33 T 0 F (, \0501989\051) 274.18 713.33 T 3 F (Description of an NFS server implementation for IBM\325) 171 702.33 T (s MVS operating system.) 389.85 702.33 T 0 F ([RFC1014]) 72 683.33 T (Sun Microsystems, Inc.,) 171 683.33 T (\322External Data Representation Speci\336cation,\323) 171 672.33 T (RFC-1014, DDN Network Information Center) 171 661.33 T (, SRI International, Menlo Park, CA) 356.31 661.33 T (.) 501.22 661.33 T 3 F (Pr) 171 650.33 T (oposed standar) 180.62 650.33 T (d for canonical format for data exchange, used with RPC.) 241.61 650.33 T 0 F ([RFC1057]) 72 631.33 T (Sun Microsystems, Inc.,) 171 631.33 T (\322Remote Procedure Call Speci\336cation,\323) 171 620.33 T (RFC-1057, DDN Network Information Center) 171 609.33 T (, SRI International, Menlo Park, CA) 356.31 609.33 T (.) 501.22 609.33 T 3 F (Remote pr) 171 598.33 T (ocedur) 211.99 598.33 T (e pr) 239.37 598.33 T (otocol speci\336cation.) 254.82 598.33 T 0 F ([RFC1094]) 72 579.33 T (Sun Microsystems, Inc.,) 171 579.33 T (\322Network Filesystem Speci\336cation,\323) 171 568.33 T (RFC-1094, DDN Network Information Center) 171 557.33 T (, SRI International, Menlo Park, CA) 356.31 557.33 T (.) 501.22 557.33 T 3 F (NFS version 2 pr) 171 546.33 T (otocol speci\336cation.) 239.2 546.33 T 0 F ([Sandber) 72 527.33 T (g]) 107.9 527.33 T (Sandber) 171 527.33 T (g, R., D. Goldber) 203.57 527.33 T (g, S. Kleiman, D. W) 272.51 527.33 T (alsh, B. L) 353.33 527.33 T (yon,) 391.65 527.33 T (\322Design and Implementation of the Sun Network Filesystem,\323) 171 516.33 T 3 F (USENIX Confer) 171 505.33 T (ence Pr) 235.32 505.33 T (oceedings) 265.75 505.33 T 0 F (, USENIX Association, Berkeley) 305.72 505.33 T (, CA, Summer 1985.) 437.47 505.33 T 3 F 0.78 (The basic paper describing the SunOS implementation of the NFS version 2 pr) 171 494.33 P 0.78 (otocol, and) 494.24 494.33 P (discusses the goals, pr) 171 483.33 T (otocol speci\336cation and trade-offs) 260.58 483.33 T (.) 397.45 483.33 T 0 F ([Srinivasan]) 72 464.33 T (Srinivasan, V) 171 464.33 T (., Jef) 224.12 464.33 T (frey C. Mogul,) 243.09 464.33 T (\322Spritely NFS: Implementation and Performance of Cache Consistency Protocols\323,) 171 453.33 T 0.54 (WRL Research Report 89/5, Digital Equipment Corporation W) 171 442.33 P 0.54 (estern Research Laboratory) 427.17 442.33 P 0.54 (,) 537.5 442.33 P (100 Hamilton A) 171 431.33 T (ve., Palo Alto, CA, 94301, May 1989.) 235.23 431.33 T 3 F 1.96 (This paper analyzes the effect of applying a Sprite-like consistency pr) 171 420.33 P 1.96 (otocol applied to) 468.35 420.33 P (standar) 171 409.33 T (d NFS. The issues of r) 201.17 409.33 T (ecovery in a stateful envir) 289.1 409.33 T (onment ar) 392.54 409.33 T (e cover) 432.98 409.33 T (ed in [Mogul].) 461.74 409.33 T 0 F ([X/OpenNFS]) 72 390.33 T (X/Open Company) 171 390.33 T (, Ltd.,) 243.36 390.33 T (X/Open CAE Speci\336cation: Protocols for X/Open Internetworking: XNFS,) 171 379.33 T 0.55 (X/Open Company) 171 368.33 P 0.55 (, Ltd., Apex Plaza, Forbury Road, Reading Berkshire, RG1 1AX, United) 243.91 368.33 P (Kingdom, 1991.) 171 357.33 T 3 F 0.22 (This is an indispensable r) 171 346.33 P 0.22 (efer) 274.24 346.33 P 0.22 (ence for NFS version 2 pr) 289.42 346.33 P 0.22 (otocol and accompanying pr) 393.69 346.33 P 0.22 (otocols,) 508.63 346.33 P (including the Lock Manager and the Portmapper) 171 335.33 T (.) 366.43 335.33 T 0 F ([X/OpenPCNFS]) 72 316.33 T (X/Open Company) 171 316.33 T (, Ltd.,) 243.36 316.33 T 0.73 (X/Open CAE Speci\336cation: Protocols for X/Open Internetworking: \050PC\051NFS, Developer) 171 305.33 P 0.73 (\325) 533.33 305.33 P 0.73 (s) 536.11 305.33 P (Speci\336cation,) 171 294.33 T 0.55 (X/Open Company) 171 283.33 P 0.55 (, Ltd., Apex Plaza, Forbury Road, Reading Berkshire, RG1 1AX, United) 243.91 283.33 P (Kingdom, 1991.) 171 272.33 T 3 F 0.22 (This is an indispensable r) 171 261.33 P 0.22 (efer) 274.24 261.33 P 0.22 (ence for NFS version 2 pr) 289.42 261.33 P 0.22 (otocol and accompanying pr) 393.69 261.33 P 0.22 (otocols,) 508.63 261.33 P (including the Lock Manager and the Portmapper) 171 250.33 T (.) 366.43 250.33 T FMENDPAGE %%EndPage: "92" 97 %%Page: "93" 97 612 792 0 FMBEGINPAGE 2 10 Q 0 X 0 K (Network File System Version 3 Protocol Specification) 72 752.33 T (2/16/94) 506.66 752.33 T 72 30 540 42 R 7 X V 0 X (Version 3) 72 35.33 T (93) 300.44 35.33 T 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 14 Q (L) 315 710.67 T 4 10 Q (LINK) 315 697.33 T 1 F ( procedure) 338.99 697.33 T 0 9 Q (49) 389.76 697.33 T 1 10 Q (lock manager) 315 686.33 T 0 9 Q (1) 377.98 686.33 T 4 10 Q (LOOKUP) 315 675.33 T 1 F ( procedure) 350.98 675.33 T 0 9 Q (22) 401.75 675.33 T 2 14 Q (M) 315 651.67 T 1 10 Q (meta-data) 315 638.33 T 0 9 Q (4) 362.99 638.33 T 0 12 Q (,) 367.49 638.33 T 0 9 Q (30) 373.48 638.33 T 4 10 Q (MKDIR) 315 627.33 T 1 F ( procedure) 344.98 627.33 T 0 9 Q (36) 395.76 627.33 T 4 10 Q (MKNOD) 315 616.33 T 1 F ( procedure) 344.98 616.33 T 0 9 Q (40) 395.76 616.33 T 1 10 Q (mode) 315 605.33 T (25) 342.99 605.33 T (mount) 315 594.33 T 0 9 Q (67) 345.77 594.33 T 1 10 Q (mount protocol) 315 583.33 T 0 9 Q (1) 384.1 583.33 T 4 10 Q (MOUNTPROC3_DUMP) 315 572.33 T 1 F ( procedure) 404.95 572.33 T 0 9 Q (78) 455.72 572.33 T 4 10 Q (MOUNTPROC3_EXPORT) 315 561.33 T 1 F ( procedure) 416.94 561.33 T 0 9 Q (81) 467.72 561.33 T 4 10 Q (MOUNTPROC3_MNT) 315 550.33 T 1 F ( procedure) 398.95 550.33 T 0 9 Q (77) 449.73 550.33 T 4 10 Q (MOUNTPROC3_NULL) 315 539.33 T 1 F ( procedure) 404.95 539.33 T 0 9 Q (76) 455.72 539.33 T 4 10 Q (MOUNTPROC3_UMNT) 315 528.33 T 1 F ( procedure) 404.95 528.33 T 0 9 Q (79) 455.72 528.33 T 4 10 Q (MOUNTPROC3_UMNTALL) 315 517.33 T 1 F ( procedure) 422.94 517.33 T 0 9 Q (80) 473.71 517.33 T 1 10 Q (MTU) 315 506.33 T 0 9 Q (60) 339.65 506.33 T 2 14 Q (N) 315 482.67 T 1 10 Q (non-idempotent request) 315 469.33 T (definition) 324 459 T 0 9 Q (68) 367 459 T 1 10 Q (destructive replay) 324 449 T 0 9 Q (68) 405.32 449 T 4 10 Q (NULL) 315 438.33 T 1 F ( procedure) 338.99 438.33 T 0 9 Q (18) 389.76 438.33 T 2 14 Q (P) 315 414.67 T 4 10 Q (PATHCONF) 315 401.33 T 1 F ( procedure) 362.97 401.33 T 0 9 Q (62) 413.75 401.33 T 1 10 Q (pathname) 315 390.33 T (interpretation) 324 380 T 0 9 Q (67) 385.33 380 T 1 10 Q (interpretation of) 324 370 T 4 F (..) 396.22 370 T 1 F (67) 411.21 370 T 2 14 Q (R) 315 346.67 T 4 10 Q (READ) 315 333.33 T 1 F ( procedure) 338.99 333.33 T 0 9 Q (28) 389.76 333.33 T 5 10 Q (nfsdata) 324 323 T 1 F (29) 368.98 323 T 0 12 Q (,) 380.09 323 T 1 10 Q (31) 386.09 323 T 4 F (READDIR) 315 312.33 T 1 F ( procedure) 356.98 312.33 T 0 9 Q (51) 407.75 312.33 T 4 10 Q (READDIRPLUS) 315 301.33 T 1 F ( procedure) 380.96 301.33 T 0 9 Q (54) 431.74 301.33 T 4 10 Q (READLINK) 315 290.33 T 1 F ( procedure) 362.97 290.33 T 0 9 Q (26) 413.75 290.33 T 1 10 Q (remote procedure call) 315 279.33 T 0 9 Q (2) 414.64 279.33 T 1 10 Q (authentication, see authentication) 324 269 T (remove) 315 258.33 T (of open files) 324 248 T 0 9 Q (67) 380.89 248 T 4 10 Q (REMOVE) 315 237.33 T 1 F ( procedure) 350.98 237.33 T 0 9 Q (43) 401.75 237.33 T 4 10 Q (RENAME) 315 226.33 T 1 F ( procedure) 350.98 226.33 T 0 9 Q (47) 401.75 226.33 T 4 10 Q (RMDIR) 315 215.33 T 1 F ( procedure) 344.98 215.33 T 0 9 Q (45) 395.76 215.33 T 1 10 Q (RPC, see remote procedure call) 315 204.33 T 2 14 Q (S) 315 180.67 T 1 10 Q (server) 315 167.33 T 0 9 Q (1) 345.76 167.33 T 4 10 Q (SETATTR) 315 156.33 T 1 F ( procedure) 356.98 156.33 T 0 9 Q (20) 407.75 156.33 T 5 10 Q (stable) 315 145.33 T 1 F ( bit) 350.98 145.33 T 0 9 Q (30) 367.31 145.33 T 1 10 Q (stable storage) 315 134.33 T 0 9 Q (4) 380.77 134.33 T 0 12 Q (,) 385.27 134.33 T 0 9 Q (31) 391.26 134.33 T 0 12 Q (,) 400.25 134.33 T 0 9 Q (64) 406.25 134.33 T 1 10 Q (state) 315 123.33 T (file system) 324 113 T 0 9 Q (4) 374.2 113 T 1 10 Q (stateless) 315 102.33 T 0 9 Q (4) 357.44 102.33 T 0 12 Q (,) 361.93 102.33 T 0 9 Q (67) 367.93 102.33 T 4 10 Q (SYMLINK) 315 91.33 T 1 F ( procedure) 356.98 91.33 T 0 9 Q (38) 407.75 91.33 T 1 10 Q (synchronous operations) 315 80.33 T 0 9 Q (4) 424.1 80.33 T 2 12 Q (Index) 72 712 T 2 14 Q (A) 72 686.67 T 4 10 Q (ACCESS) 72 673.33 T 1 F ( procedure) 107.98 673.33 T 0 9 Q (24) 158.75 673.33 T 1 10 Q (attributes) 72 662.33 T 0 9 Q (11) 116.11 662.33 T 5 10 Q (fattr3) 81 652 T 1 F (11) 119.98 652 T 5 F (sattr3) 81 642 T 1 F (14) 119.98 642 T (settable) 81 632 T 0 9 Q (14) 119 632 T 1 10 Q (authentication) 72 621.33 T 0 9 Q (3) 137.22 621.33 T 4 10 Q (AUTH_DES) 81 611 T 1 F (3) 131.97 611 T 0 12 Q (,) 137.53 611 T 1 10 Q (68) 143.53 611 T 4 F (AUTH_KERB) 81 601 T 1 F (3) 137.97 601 T 0 12 Q (,) 143.53 601 T 1 10 Q (68) 149.52 601 T 4 F (AUTH_NONE) 81 591 T 1 F (3) 137.97 591 T 4 F (AUTH_UNIX) 81 581 T 1 F (3) 137.97 581 T 0 12 Q (,) 143.53 581 T 1 10 Q (68) 149.52 581 T (netname) 81 571 T 0 9 Q (68) 122.89 571 T 1 10 Q (RPC) 81 561 T 0 9 Q (3) 105.1 561 T 2 14 Q (C) 72 537.67 T 1 10 Q (caching) 72 524.33 T 0 9 Q (4) 109.44 524.33 T 0 12 Q (,) 113.93 524.33 T 0 9 Q (70) 119.93 524.33 T 1 10 Q (client) 81 514 T 0 9 Q (4) 107.33 514 T 0 12 Q (,) 111.82 514 T 0 9 Q (5) 117.82 514 T 1 10 Q (consistency) 81 504 T 0 9 Q (12) 136.21 504 T 0 12 Q (,) 145.2 504 T 0 9 Q (13) 151.19 504 T 1 10 Q (server) 81 494 T 0 9 Q (4) 111.76 494 T 5 10 Q (wcc_data) 81 484 T 1 F (13) 131.97 484 T (client) 72 473.33 T 0 9 Q (1) 98.33 473.33 T 4 10 Q (COMMIT) 72 462.33 T 1 F ( procedure) 107.98 462.33 T 0 9 Q (64) 158.75 462.33 T 4 10 Q (CREATE) 72 451.33 T 1 F ( procedure) 107.98 451.33 T 0 9 Q (33) 158.75 451.33 T 1 10 Q (credentials) 72 440.33 T (for) 81 430 T 4 F (ACCESS) 95.44 430 T 1 F ( checking) 131.42 430 T 0 9 Q (24) 176.64 430 T 1 10 Q (UNIX) 81 420 T 0 9 Q (68) 107.88 420 T 2 14 Q (D) 72 396.67 T 1 10 Q (data consistency, see caching) 72 383.33 T (duplicate request cache) 72 372.33 T 0 9 Q (68) 180.55 372.33 T 0 12 Q (,) 189.54 372.33 T 0 9 Q (69) 195.53 372.33 T 2 14 Q (E) 72 348.67 T 1 10 Q (error) 72 335.33 T 4 F (NFS3ERR_NOTSUP) 81 325 T 1 F (3) 167.95 325 T (executable) 72 314.33 T (permissions issues) 81 304 T 0 9 Q (68) 168.41 304 T 1 10 Q (external data representation) 72 293.33 T 0 9 Q (2) 199.44 293.33 T 1 10 Q (discriminated union) 81 283 T 0 9 Q (2) 170.09 283 T 1 10 Q (hyper) 81 273 T 0 9 Q (2) 109 273 T 2 14 Q (F) 72 249.67 T 1 10 Q (file system) 72 236.33 T (export) 81 226 T 0 9 Q (22) 111.77 226 T 4 10 Q (FSINFO) 72 215.33 T 1 F ( procedure) 107.98 215.33 T 0 9 Q (59) 158.75 215.33 T 4 10 Q (FSSTAT) 72 204.33 T 1 F ( procedure) 107.98 204.33 T 0 9 Q (57) 158.75 204.33 T 2 14 Q (G) 72 180.67 T 4 10 Q (GETATTR) 72 167.33 T 1 F ( procedure) 113.98 167.33 T 0 9 Q (19) 164.75 167.33 T 5 10 Q (gid) 72 156.33 T 1 F (25) 92.99 156.33 T 2 14 Q (I) 72 132.67 T 1 10 Q (idempotent request) 72 119.33 T (definition) 81 109 T 0 9 Q (68) 124 109 T FMENDPAGE %%EndPage: "93" 98 %%Page: "94" 98 612 792 0 FMBEGINPAGE 2 10 Q 0 X 0 K (2/16/94) 72 755.33 T (Network File System Version 3 Protocol Specification) 285.17 755.33 T 72 30 540 42 R 7 X V 0 X (94) 300.44 35.33 T (Version 3) 495.01 35.33 T 0 153 36 -153 -36 774 180 BEGINPRINTCODE (DRAFT) /Helvetica-Bold /B +56 /LL .93 ENDPRINTCODE 2 14 Q (U) 72 710.67 T 1 10 Q (UID) 72 697.33 T 0 9 Q (68) 92.21 697.33 T 5 10 Q (uid) 72 686.33 T 1 F (25) 92.99 686.33 T 2 14 Q (W) 72 662.67 T 4 10 Q (WRITE) 72 649.33 T 1 F ( procedure) 101.98 649.33 T 0 9 Q (30) 152.76 649.33 T 2 14 Q (X) 72 625.67 T 1 10 Q (XDR, see external data representation) 72 612.33 T FMENDPAGE %%EndPage: "94" 99 %%Trailer %%BoundingBox: 0 0 612 792 %%Pages: 98 1 %%DocumentFonts: Times-Roman %%+ Helvetica %%+ Helvetica-Bold %%+ Times-Italic %%+ Courier %%+ Courier-Bold %%+ Times-Bold %%+ Times-BoldItalic %%+ Helvetica-Oblique %%+ Courier-Oblique