• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

NFS problems after upgrade to trunk

Scheduled Pinned Locked Moved Solved
FOG Problems
4
42
12.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    John Sartoris @Wayne Workman
    last edited by Feb 9, 2016, 8:45 PM

    @Wayne-Workman said:

    @John-Sartoris said:

    Edit - Correction, the master node is working, but the storage node still doesn’t mount…

    Am I mistaken, or was the problem exactly the opposite before?

    You are half right :), the nodes have swapped, but before was a “connection refused”, not it’s “operation not supported”

    1 Reply Last reply Reply Quote 0
    • J
      John Sartoris @george1421
      last edited by John Sartoris Feb 9, 2016, 3:18 PM Feb 9, 2016, 9:17 PM

      @george1421 @Wayne-Workman

      Both nodes are back online now. I had a left over “-T” in /etc/default/nfs-kernel-server on the storage node from my attempts to disable NFSv4. What I was reading said NFSv3 doesn’t use TCP and is only UDP. Well, however fog connects it needs TCP with v3.

      Here is where I ended, I don’t know if the RPCNFSCOUNT of 48 is needed to be increased from the default 8, but I read that this increases the threads for nfs workers.

      /etc/default/nfs-kernel-server

      # Number of servers to start up
      # To disable nfsv4 on the server, specify '--no-nfs-version 4' here
      RPCNFSDCOUNT='48 --no-nfs-version 4'
      
      # Runtime priority of server (see nice(1))
      RPCNFSDPRIORITY=0
      
      # Options for rpc.mountd.
      # If you have a port-based firewall, you might want to set up
      # a fixed port here using the --port option. For more information,
      # see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS
      # To disable NFSv4 on the server, specify '--no-nfs-version 4' here
      RPCMOUNTDOPTS='--manage-gids --no-nfs-version 4'
      
      # Do you want to start the svcgssd daemon? It is only required for Kerberos
      # exports. Valid alternatives are "yes" and "no"; the default is "no".
      NEED_SVCGSSD="no"
      
      # Options for rpc.svcgssd.
      RPCSVCGSSDOPTS=""
      
      # Options for rpc.nfsd.
      RPCNFSDOPTS=""
      

      /etc/idmapd.conf

      [General]
      
      Verbosity = 0
      Pipefs-Directory = /run/rpc_pipefs
      # set your own domain here, if id differs from FQDN minus hostname
       Domain = localdomain
      
      [Mapping]
      
      Nobody-User = nobody
      Nobody-Group = nogroup
      
      [Translation]
      Method = nsswitch
      

      /etc/default/nfs-common

      # If you do not set values for the NEED_ options, they will be attempted
      # autodetected; this should be sufficient for most people. Valid alternatives
      # for the NEED_ options are "yes" and "no".
      
      # Do you want to start the statd daemon? It is not needed for NFSv4.
      NEED_STATD=
      
      # Options for rpc.statd.
      #   Should rpc.statd listen on a specific port? This is especially useful
      #   when you have a port-based firewall. To use a fixed port, set this
      #   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
      #   For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
      STATDOPTS=
      
      # Do you want to start the gssd daemon? It is required for Kerberos mounts.
      NEED_GSSD=
      
      1 Reply Last reply Reply Quote 0
      • 1
      • 2
      • 3
      • 3 / 3
      3 / 3
      • First post
        41/42
        Last post

      215

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project