1FIXMOUNT(8)                 System Manager's Manual                FIXMOUNT(8)
2
3
4

NAME

6       fixmount - fix remote mount entries
7

SYNOPSIS

9       fixmount [ -adervq ] [ -h name ] host ...
10

DESCRIPTION

12       fixmount  is  a  variant  of  showmount(8)  that can delete bogus mount
13       entries in remote mountd(8) daemons.   The  actions  specified  by  the
14       options are performed for each host in turn.
15

OPTIONS

17       -a -d -e
18              These  options  work as in showmount(8) except that only entries
19              pertaining to the local host are printed.
20
21       -r     Removes those remote mount entries on host that  do  not  corre‐
22              spond  to current mounts, i.e., which are left-over from a crash
23              or are the result of improper mount protocol.  The actuality  of
24              mounts is verified using the entries in /etc/mtab.
25
26       -v     Verify  remote mounts.  Similar to -r except that only a notifi‐
27              cation message is printed  for  each  bogus  entry  found.   The
28              remote mount table is not changed.
29
30       -A     Issues  a command to the remote mountd declaring that ALL of its
31              filesystems have been unmounted.  This should be used with  cau‐
32              tion,  as  it removes all remote mount entries pertaining to the
33              local system, whether or not any filesystems are  still  mounted
34              locally.
35
36       -q     Be  quiet.   Suppresses error messages due to timeouts and "Pro‐
37              gram not registered", i.e., due to remote hosts  not  supporting
38              RPC or not running mountd.
39
40       -h name
41              Pretend  the  local  hostname is name.  This is useful after the
42              local hostname has been changed and rmtab entries using the  old
43              name  remain  on a remote machine.  Unfortunately, most mountd's
44              won't be able to successfully handle removal of such entries, so
45              this option is useful in combination with -v only.
46              This  option also saves time as comparisons of remotely recorded
47              and local hostnames by address are avoided.
48

FILES

50       /etc/mtab           List of current mounts.
51
52       /etc/rmtab          Backup file for remote mount entries on NFS server.
53

SEE ALSO

55       showmount(8), mtab(5), rmtab(5), mountd(8C).
56
57       ``am-utils'' info(1) entry.
58
59       Linux  NFS  and  Automounter  Administration  by   Erez   Zadok,   ISBN
60       0-7821-2739-8, (Sybex, 2001).
61
62       http://www.am-utils.org
63
64       Amd - The 4.4 BSD Automounter
65

BUGS

67       No attempt is made to verify the information in /etc/mtab itself.
68
69       Since  swap file mounts are not recorded in /etc/mtab, a heuristic spe‐
70       cific to SunOS is used to determine whether  such  a  mount  is  actual
71       (replacing  the  string  "swap" with "root" and verifying the resulting
72       path).
73
74       Symbolic links on the server will cause the path in the remote entry to
75       differ  from  the one in /etc/mtab.  To catch those cases, a filesystem
76       is also deemed mounted if its local mount point  is  identical  to  the
77       remote     entry.      I.e.,    on    a    SunOS    diskless    client,
78       server:/export/share/sunos.4.1.1 is  actually  /usr/share.   Since  the
79       local mount point is /usr/share as well this will be handled correctly.
80
81       There  is  no  way  to clear a stale entry in a remote mountd after the
82       local hostname (or whatever reverse name resolution returns for it) has
83       been  changed.  To take care of these cases, the remote /etc/rmtab file
84       has to be edited and mountd restarted.
85
86       The RPC timeouts for mountd calls can only be changed  by  recompiling.
87       The defaults are 2 seconds for client handle creation and 5 seconds for
88       RPC calls.
89

AUTHORS

91       Andreas Stolcke <stolcke@icsi.berkeley.edu>.
92
93       Erez Zadok  <ezk@cs.sunysb.edu>,  Computer  Science  Department,  Stony
94       Brook University, Stony Brook, New York, USA.
95
96       Other  authors  and  contributors to am-utils are listed in the AUTHORS
97       file distributed with am-utils.
98
99
100
101                                  26 Feb 1993                      FIXMOUNT(8)
Impressum