An error occurred fetching the project authors.
  1. 01 Oct, 2012 2 commits
    • Chuck Lever's avatar
      NFS: Add nfs4_unique_id boot parameter · 6f2ea7f2
      Chuck Lever authored
      An optional boot parameter is introduced to allow client
      administrators to specify a string that the Linux NFS client can
      insert into its nfs_client_id4 id string, to make it both more
      globally unique, and to ensure that it doesn't change even if the
      client's nodename changes.
      
      If this boot parameter is not specified, the client's nodename is
      used, as before.
      
      Client installation procedures can create a unique string (typically,
      a UUID) which remains unchanged during the lifetime of that client
      instance.  This works just like creating a UUID for the label of the
      system's root and boot volumes.
      Signed-off-by: default avatarChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
      6f2ea7f2
    • Chuck Lever's avatar
      NFS: Introduce "migration" mount option · 89652617
      Chuck Lever authored
      Currently, the Linux client uses a unique nfs_client_id4.id string
      when identifying itself to distinct NFS servers.
      
      To support transparent state migration, the Linux client will have to
      use the same nfs_client_id4 string for all servers it communicates
      with (also known as the "uniform client string" approach).  Otherwise
      NFS servers can not recognize that open and lock state need to be
      merged after a file system transition.
      
      Unfortunately, there are some NFSv4.0 servers currently in the field
      that do not tolerate the uniform client string approach.
      
      Thus, by default, our NFSv4.0 mounts will continue to use the current
      approach, and we introduce a mount option that switches them to use
      the uniform model.  Client administrators must identify which servers
      can be mounted with this option.  Eventually most NFSv4.0 servers will
      be able to handle the uniform approach, and we can change the default.
      
      The first mount of a server controls the behavior for all subsequent
      mounts for the lifetime of that set of mounts of that server.  After
      the last mount of that server is gone, the client erases the data
      structure that tracks the lease.  A subsequent lease may then honor
      a different "migration" setting.
      
      This patch adds only the infrastructure for parsing the new mount
      option.  Support for uniform client strings is added in a subsequent
      patch.
      Signed-off-by: default avatarChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
      89652617
  2. 04 Sep, 2012 1 commit
  3. 16 Aug, 2012 2 commits
  4. 30 Jul, 2012 9 commits
  5. 17 Jul, 2012 2 commits
  6. 14 Jul, 2012 1 commit
  7. 10 Jul, 2012 1 commit
  8. 29 Jun, 2012 2 commits
  9. 09 Jun, 2012 1 commit
  10. 05 Jun, 2012 1 commit
  11. 22 May, 2012 1 commit
  12. 16 May, 2012 1 commit
  13. 15 May, 2012 13 commits
  14. 27 Apr, 2012 1 commit
  15. 20 Apr, 2012 1 commit
    • Jan Kara's avatar
      nfs: Enclose hostname in brackets when needed in nfs_do_root_mount · 98a2139f
      Jan Kara authored
      When hostname contains colon (e.g. when it is an IPv6 address) it needs
      to be enclosed in brackets to make parsing of NFS device string possible.
      Fix nfs_do_root_mount() to enclose hostname properly when needed. NFS code
      actually does not need this as it does not parse the string passed by
      nfs_do_root_mount() but the device string is exposed to userspace in
      /proc/mounts.
      
      CC: Josh Boyer <jwboyer@redhat.com>
      CC: Trond Myklebust <Trond.Myklebust@netapp.com>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
      98a2139f
  16. 28 Mar, 2012 1 commit