os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add 2017Q3 pNFS entry from rmacklem

Browse source
This commit is contained in:
Benjamin Kaduk 2017-11-30 04:41:30 +00:00
parent 1946c3fd4f
commit 3e2c4d5e14
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=51238
1 changed files with 51 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

51
en_US.ISO8859-1/htdocs/news/status/report-2017-07-2017-09.xml
View file

@ -1069,4 +1069,55 @@
to find out how we support &os; and how we can help you!</p>
</body>
</project>
<project cat="kern">
<title>pNFS Server Plan B</title>
<contact>
<person>
<name>
<given>Rick</given>
<common>Macklem</common>
</name>
<email>rmacklem@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt">Instructions for Testing</url>
</links>
<body>
<p>A pNFS server allows an NFS service to be spread over
multiple servers, separating the MetaData operations from the
Data operations (Read/Write). This project will add the
capability of using &os; systems to create a pNFS service
consisting of a single MetaData Server, plus a set of Data
Servers. The Data Servers can be mirrored, so that redundant
copies of the file data are maintained.</p>
<p>The support for non-mirrored Data Servers is now believed
to be complete. Support for mirrored Data Servers using the
Flexible File Layout, which will soon be published as an RFC,
is implemented. However, there is still significant work to
be done, since the current implementation of mirrored Data
Servers does not handle failed Data Servers or their
resilvering/recovery. It is hoped that support for
failure/recovery of Data Servers will be implemented in the
next six months.</p>
<p>The patched &os; sources may now be accessed for testing
via either Subversion or download of a gzipped tarball.
They consist of a patched kernel plus nfsd daemon and can be
used on any &os; 11 or later system. The installation
procedure is covered in the linked document.</p>
</body>
<help>
<task>Testing by others will be needed, now that the
implementation is available.</task>
<task>Implementation and testing of mirror failure/recovery.</task>
</help>
</project>
</report>