OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Build 101-105
      3. Builds 96-100
      4. Builds 91-95
      5. Builds 86-90
      6. Builds 81-85
      7. Builds 76-80
      8. Builds 71-75
      9. Builds 66-70
      10. Builds 61-65
      11. Builds 56-60
      12. Builds 51-55
      13. Builds 46-50
      14. Builds 41-45
      15. Builds 36-40
      16. Builds 31-35
      17. Builds 26-30
      18. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads up message for PSARC 2007/347 NFS/RDMA - Transport Version Update

Date: Thu, 21 Aug 2008 18:38:05 -0500
From: Robert Gordon <Robert.Gordon at sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads up message for PSARC 2007/347 NFS/RDMA - Transport Version Update


If you do not use NFS over Infiniband, you can delete this message now.

--

This integration brings the NFS/RDMA Solaris Implementation up to date  
with the latest IETF Drafts.  Specifically, it removes support for the  
initial NFS/RDMA implementation (version 0) and adds support for  
rpcrdma [1] and nfsdirect [2] (version 1).

Please note that if a version 0 client contacts a version 1 server,  
the client will revert to IP over IB without intervention from the  
administrator. If a version 1 client contacts a version 0 server, the  
client's mount will hang.  The "proto=tcp" mount option can be used,  
however, to allow the client to mount using IP over IB.


* Also note:

During our test cycle we hit this issue

6739454 system panics at sdpib:sdp_rts_announce

This issue is not related to this code integration, and this CR number  
is provided for your information should you hit the panic.

Thanks,
The NFS Team.

--
[1]: http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-rpcrdma-08.txt
[2]: http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-nfsdirect-08.txt