stablerestart(5) [freebsd man page]

STABLERESTART(5)					      BSD File Formats Manual						  STABLERESTART(5)

NAME

     nfs-stablerestart -- restart information for the NFSv4 server

SYNOPSIS

     nfs-stablerestart

DESCRIPTION

     The nfs-stablerestart file holds information that allows the NFSv4 server to restart without always returning the NFSERR_NOGRACE error, as
     described in the NFSv4 server specification; see Network File System (NFS) Version 4 Protocol RFC 3530, Section 8.6.3.

     The first record in the file, as defined by struct nfsf_rec in /usr/include/fs/nfs/nfsrvstate.h, holds the lease duration of the last incar-
     nation of the server and the number of boot times that follows.  Following this are the number of previous boot times listed in the first
     record.  The lease duration is used to set the grace period.  The boot times are used to avoid the unlikely occurrence of a boot time being
     reused, due to a TOD clock going backwards. This record and the previous boot times with this boot time added is re-written at the end of the
     grace period.

     The rest of the file are appended records, as defined by struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used represent one of
     two things. There are records which indicate that a client successfully acquired state and records that indicate a client's state was
     revoked.  State revoke records indicate that state information for a client was discarded, due to lease expiry and an otherwise conflicting
     open or lock request being made by a different client.  These records can be used to determine if clients might have done either of the edge
     conditions.

     If a client might have done either edge condition or this file is empty or corrupted, the server returns NFSERR_NOGRACE for any reclaim
     request from the client.

     For correct operation of the server, it must be ensured that the file is written to stable storage by the time a write op with IO_SYNC speci-
     fied has returned. This might require hardware level caching to be disabled for a local disk drive that holds the file, or similar.

FILES

     /var/db/nfs-stablerestart	    NFSv4 stable restart file
     /var/db/nfs-stablerestart.bak  backup copy of the file

SEE ALSO

     nfsv4(4), nfsd(8)

BUGS

     If the file is empty, the NFSv4 server has no choice but to return NFSERR_NOGRACE for all reclaim requests. Although correct, this is a
     highly undesirable occurrence, so the file should not be lost if at all possible. The backup copy of the file is maintained and used by the
     nfsd(8) to minimize the risk of this occurring.  To move the file, you must edit the nfsd sources and recompile it. This was done to discour-
     age accidental relocation of the file.

BSD
								  April 10, 2011							       BSD

lockd(1M)                                                 System Administration Commands                                                 lockd(1M)

NAME

       lockd - network lock daemon

SYNOPSIS

       /usr/lib/nfs/lockd [-g graceperiod] [-l listen_min_backlog] [-t timeout] [nthreads]

DESCRIPTION

       The  lockd  utility is part of the NFS lock manager, which supports record locking operations on NFS files. See fcntl(2) and lockf(3C). The
       lock manager provides the following two functions:

         o  It forwards fcntl(2) locking requests for NFS mounted file systems to the lock manager on the NFS server.

         o  It generates local file locking operations in response to requests forwarded from lock managers running on NFS client machines.

       State information kept by the lock manager about these locking requests can be lost if the lockd is  killed  or  the  operating  system  is
       rebooted.  Some of this information can be recovered as follows. When the server lock manager restarts, it waits for a grace period for all
       client-site lock managers to submit reclaim requests. Client-site lock managers, on the other hand, are notified by the status monitor dae-
       mon,  statd(1M),  of  the  restart  and promptly resubmit previously granted lock requests. If the lock daemon fails to secure a previously
       granted lock at the server site, then it sends SIGLOST to a process.

       Administrators can make changes to the startup parameters for lockd by logging in as  root  and  editing  the  /etc/default/nfs  file  (See
       nfs(4)).

OPTIONS

       The following options are supported:

       -g graceperiod          Deprecated  in  favor  of GRACE_PERIOD. Specify the number of seconds that all clients (both NLM and NFSv4) have to
                               reclaim locks after the server reboots. It also controls the NFSv4 lease interval. This option is equivalent to the
                               LOCKD_GRACE_PERIOD parameter.

       -l listen_min_backlog   Specify  the  listener  backlog  (listen_min_backlog).  listen_min_backlog  is the number connect requests that are
                               queued and waiting to be processed before new connect requests start to get dropped.

       -t timeout              Specify the number of seconds to wait before retransmitting a lock request to the remote server. The default  value
                               is 15 seconds. Equivalent of the LOCKD_RETRANSMIT_TIMEOUT parameter in the nfs file.

OPERANDS

       nthreads                Specify  the maximum number of concurrent threads that the server can handle. This concurrency is achieved by up to
                               nthreads threads created as needed in the kernel. nthreads should be based on the load expected on this server.  If
                               nthreads  is  not  specified,  the  maximum  number  of  concurrent  threads  will default to 20. Equivalent of the
                               LOCKD_SERVERS parameter in the nfs file.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWnfscu                    |
       +-----------------------------+-----------------------------+

SEE ALSO

       svcs(1), automountd(1M), clear_locks(1M), mount_nfs(1M), share(1M), share_nfs(1M),  statd(1M),  svcadm(1M),  fcntl(2),  lockf(3C),  nfs(4),
       attributes(5), smf(5)

NOTES

       The lockd service is managed by the service management facility, smf(5), under the service identifier:

       svc:/network/nfs/nlockmgr

       Administrative  actions  on  this  service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
       vice's status can be queried using the svcs(1) command.

       If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless  its        application/auto_enable  prop-
       erty is set to false.

       This daemon might not exist in a future release of Solaris.

SunOS 5.10                                                          17 Nov 2004                                                          lockd(1M)