OpenSolaris

You are not signed in. Sign in or register.

Release Notes for OpenSolaris pNFS — October 2007

Changes from the last release

  • Our project gate has been synced with build 75 of ONNV.
  • Our project gate is compliant with Draft 13 of the NFSv4.1 specification. Please note that there have been several protocol changes in Drafts 11-13, therefore, our older releases (June 2007 and August 2007) will not work with this release. When using this release, all clients and servers must be Draft 13 based.

General Information

These are the release notes for the October 2007 release of the source code and binaries for the OpenSolaris project "NFS version 4.1 pNFS". The purpose of this document is to give you information about this distribution, its capabilities, known problems, and installation instructions. A separate document contains directions on how to configure pNFS clients and servers.

We value your feedback and thank you for trying pNFS!

If you have questions or comments about this document, the software being released, the logistics of the pNFS project, please email them to nfsv41 dash discuss at opensolaris dot org.

If you run into problems or issues not mentioned in the known issue list below, please report them via the email address mentioned above. Provide the release name (on-pnfs-draft10-onnv75-bins-20071024) as well as information about the problem. Information that will help in determining the root cause of a problem is documented in the FAQ.

Although we will not be providing patches or fixes to this distribution, we will enter the issues into our tracking tool and evaluate each issue for inclusion in future releases of this project. If you are interested in contributing to the project, please contact us.

This release is based off of OS/Net (ON) Nevada Build 75.

Functionality

This release implements the basic elements needed for doing files-based pNFS as defined by draft 13 of the NFSv4.1 specification. This specification is owned by the IETF and the latest draft may be viewed on the IETF website. Various versions of the draft can also be viewed on the NFSv4.1 Editor's website.

At a high level, this distribution supports separation of data and metadata, parallel I/O from the pNFS clients to pNFS data servers, and Sessions, a mandatory-to-implement feature of the NFSv4.1 specification and a prerequisite for pNFS.

Since we are early in the development cycle, some features have yet to be implemented. We recommend this release for experimental or casual use (i.e., install it just to "play around" with pNFS).

This release is not to be used in production environments. There are known issues which will cause system crashes.

Known Issues

  • NEW!!! Starting lockd will cause a panic. For now we recommend the the following work around:
#svcadm mark -I maintenance lockmgr
Failure information:
panic[cpu0]/thread=c1872680: BAD TRAP: type=e (#pf Page fault) rp=c1afe9f8
addr=14 occurred in module "klmmod" due to a NULL pointer dereference
lockd: #pf Page fault
Bad kernel fault at addr=0x14
    …
c1afe94c unix:die+a6 (e, c1afe9f8, 14, 0)
c1afe9e4 unix:trap+135c (c1afe9f8, 14, 0)
c1afe9f8 unix:cmntrap+10b (c1af01b0, c1af0000,)
c1afeaa8 klmmod:lmsvc+466 (c1afeeec, c1afef8c,)
c1afef7c unix:stubscommoncode+3b (c, 80674f0, a82f, c)
  • The NFSv4.1/pNFS client will auto-negotiate the correct NFSv4 Minor Version for you. If you run your NFSv4.1 client against a NFSv4.0 server you will see messages like the one below. These messages are harmless and are just a side effect of the client negotiating the correct Minor Version.
NFS4 compound failed for <servername>: RPC: Server can't decode arguments
NOTICE: NFS4 mount (EXCHANGE_ID failed): Create Clientid failure
  • There is currently no way to remove data objects from the data server. Removal of files from the metadata server will work as normal, but this won't deallocate the space on the data server.
  • Accessing pNFS files directly at the MDS is not supported. The file's attributes, including size, will be correct, but the file's data will read as all zeros. Modifying the file's data locally at the MDS will succeed; however, the client will not see this data.
  • The Connectathon holey file test fails intermittently with a message like "non-zero data read back from hole (offset 41780)".
  • The use of Kerberos with NFSv4.1 mounts is untested and discouraged.
  • RDMA is not supported for NFSv4.1
  • Running the pNFS client in a non-global zone is not supported.
  • Running the MDS or DS in a non-global zone is not supported.
  • The mdsadm and dservadm commands are very preliminary and will be changed in the future. No man pages are available, but the "how to" document contains descriptions of them.

Instructions for Installing

The format for releasing pNFS binaries is BFU archives. To use BFU, check out the instructions on the OpenSolaris.org website. We recommend installing Solaris Express, Community Edition (CD, DVD), then using BFU to update your machine(s) with the BFU archives provided. A good summary of this process is documented at the ON download site. Pay attention to steps 1, 2 and 3b.