OpenSolaris

You are not signed in. Sign in or register.

OpenSolaris Project: NFS version 4.1 pNFS

View the leaders for this project
Project Observers

Endorsing communities

HPC Developer
NFS
Storage

What's New?

  • March 26, 2008 – Code and BFU archives based off of Nevada build 85 and Draft 19 have been posted at our download page.
  • October 26, 2007 – Code and BFU archives based off of Nevada build 75 and Draft 13 have been posted at our download page.
  • October 17, 2007 – The NFS Team will host a bake-a-thon in Austin, Tx the week of Feb 18th 2008.
  • August 9, 2007 – Code and BFU archives based off of Nevada build 69 have been posted at our download page.
  • June 25, 2007 – Code and BFU archives based off of Nevada build 66 have been posted at our download page. Give it a whirl!
  • April 24, 2007 – We've created a demo showing the basics of pNFS.
  • We have put together some information focusing on the logistics of how we propose to run this project. Please feel free to check out the logistics and FAQ pages!

The Project

Mission Statement

  • To openly design and develop a NFSv4.1 parallel NFS (pNFS) implementation for OpenSolaris
  • To verify and provide feedback to the IETF NFSv4 working group about the NFSv4.1 specification
  • To understand the impacts and requirements of NFSv4.1 pNFS for OpenSolaris

Mailing List

Proposed Deliverables

Status

Current Information

  • We will be testing the Solaris pNFS client and server at the next interoperability event, the May 2008 ConnectAthon hosted by Sun and NetApp in San Jose, CA.

Past Information

  • The pNFS client prototype was taken to the NFSv4 Bakeathon held in Ann Arbor, MI, Sept. 11-15, 2006. The OpenSolaris pNFS client was able to successfully do parallel I/O against all of the files-based pNFS servers in attendance.
  • The pNFS client and server was taken to both the June 2007 Bakeathon in Austin, Texas and the October 2007 Bakeathon in Ann Arbor, MI.

The Technology

What is NFSv4.1?

  • NFSv4.1 is the first minor version of NFSv4. The major extensions included in NFSv4.1 are Sessions, Directory Delegations and parallel NFS.

What is pNFS?

  • The pNFS protocol allows us to separate a NFS file system's data and metadata paths. With a separate data path we are free to lay file data out in interesting ways like striping it across multiple different file servers. For more information, see the NFSv4.1 specification.

Links

  • Summary (including slides) of the September 2006 FROSUG Meeting where pNFS was presented.
  • NFSv4.1 Specification – Draft 17

Code…We like code…

  • Go to the Downloads page for our current installable bits.

Announcements

26 Mar 2008 New NFSv4.1 pNFS Source and Binaries posted
26 Oct 2007 New NFSv4.1 pNFS Source and Binaries posted
09 Aug 2007 New NFSv4.1 pNFS Source and Binaries posted
25 Jun 2007 NFSv4.1 pNFS Source and Binaries Posted - June 2007

Blogs

samf - smcup/rmcup: hate

Apr 2, 11:00 AM

Some terminals have the capability to save and restore themselves. Some programs take advantage of this, so that when you exit the program, your screen is restored to its previous state. In terms of ...

tdh - Followup om pNFS testing under VMWare

Mar 28, 1:03 PM

I got a pNFS community and client to run under VMWare on a XP box. Okay, so I made sure to make independent clones of the same machine as before. And this time I went from 512M to 1G of available ...

tdh - Trying to do pNFS testing under VMWare

Mar 28, 10:08 AM

I'm trying to get a NFSv4.1 (aka pNFS) DS, MDS, and client all running as VMWare machines on my XP box. I took a base nevada 85 system (with a Core Custom load - which only eats up 1.4G of disk ...

tdh - auth records will not load if no share enabled

Mar 20, 6:51 PM

If you fail to share a zfs pool on the mds, then nfs will not be enabled and therefore the mds auth records will not load. # mdsadm -o add -t auth -a ip=10.1.233.117 adding: IP Addr - 10.1.233.117 ...

tdh - Some behind the scenes tips for getting a community working

Mar 19, 10:21 AM

In no particular order... Do a banner of mds , client , and ds (or ds1, ds2, etc) and place it in /etc/motd for the respective hosts. It will help you more than you think. Especially after a core ...