X-Git-Url: http://git.tuebingen.mpg.de/?p=aple.git;a=blobdiff_plain;f=Filesystems.m4;h=1a77ef882e9ebb6c412380add1c2787acc32a291;hp=903b0b35a4ebcda8ab3a18997c7cc77617368744;hb=HEAD;hpb=0d431cf6bd2cb41ec51041f4069711dbf2306d54;ds=sidebyside diff --git a/Filesystems.m4 b/Filesystems.m4 index 903b0b3..40dedd1 100644 --- a/Filesystems.m4 +++ b/Filesystems.m4 @@ -1385,7 +1385,7 @@ silly renames: An NFS4.1 server knows when it its safe to unlink a file and communicates this information to the client.

The file handle which an nfs client received through some earlier -rpc can become invalid at any time due to operations on a different +rpc can become invalid at any time due to operations on different hosts. This happens, for example, if the file was deleted on the server or on a different nfs client, or when the directory that contains the file is no longer exported by the server due to a configuration @@ -1432,7 +1432,7 @@ EXERCISES()

  • In an nfs-mounted directory (nfs version 4.0 or earlier), run cat > foo &. Note that the cat process automatically receives the STOP signal. Run rm foo; ls -ltra. Read - section D2 of the nfs HOWTO + section D2 of the nfs HOWTO for the explanation.
  • In an nfs-mounted directory, run { while :; do echo; sleep @@ -1441,7 +1441,7 @@ EXERCISES()
  • Discuss the pros and cons of hard vs. soft mounts.
  • -
  • Read section A10 of the nfs +
  • Read section A10 of the nfs HOWTO to learn about common reasons for stale nfs handles.
  • Can every local filesystem be exported via nfs?
  • @@ -1508,9 +1508,12 @@ SECTION(«Further Reading»)
  • Dominic Giampaolo: Practical File System Design
  • Cormen
  • Darrick Wong: XFS Filesystem Disk Structures
  • -
  • The xfs FAQ
  • Documentation/filesystems/path-lookup.rst
  • rfc 5531: Remote Procedure Call Protocol, Version 2 (2009)
  • Birell, A.D. and Nelson, B.J.: Implementing Remote Procedure Calls (1984)
  • +
  • NFS: the early + years and NFS: the new + millennium, two articles on the design and history of NFS by Neil + Brown.