Uniformly refer to a file system as "file system".
Approved by: re
This commit is contained in:
parent
e66cdcd7e0
commit
8d5d039f80
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=107788
@ -82,8 +82,8 @@
|
|||||||
.Ar ...
|
.Ar ...
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
.Nm Amd
|
.Nm Amd
|
||||||
is a daemon that automatically mounts filesystems whenever a file or directory
|
is a daemon that automatically mounts file systems whenever a file or directory
|
||||||
within that filesystem is accessed. Filesystems are automatically unmounted
|
within that file system is accessed. File systems are automatically unmounted
|
||||||
when they appear to be quiescent.
|
when they appear to be quiescent.
|
||||||
.Pp
|
.Pp
|
||||||
.Nm Amd
|
.Nm Amd
|
||||||
@ -97,7 +97,7 @@ are handled by
|
|||||||
which uses the map defined by
|
which uses the map defined by
|
||||||
.Ar mapname
|
.Ar mapname
|
||||||
to determine how to resolve the lookup. Generally, this will be a host name,
|
to determine how to resolve the lookup. Generally, this will be a host name,
|
||||||
some filesystem information and some mount options for the given filesystem.
|
some file system information and some mount options for the given file system.
|
||||||
.Pp
|
.Pp
|
||||||
In the first form depicted above,
|
In the first form depicted above,
|
||||||
.Nm amd
|
.Nm amd
|
||||||
@ -171,7 +171,7 @@ to standard output where it can be saved into a file.
|
|||||||
.It Fl r
|
.It Fl r
|
||||||
Restart existing mounts.
|
Restart existing mounts.
|
||||||
.Nm Amd
|
.Nm Amd
|
||||||
will scan the mount file table to determine which filesystems
|
will scan the mount file table to determine which file systems
|
||||||
are currently mounted. Whenever one of these would have
|
are currently mounted. Whenever one of these would have
|
||||||
been auto-mounted,
|
been auto-mounted,
|
||||||
.Nm amd
|
.Nm amd
|
||||||
@ -197,7 +197,7 @@ Version. Displays version and configuration information on standard error.
|
|||||||
.It Fl w Ar interval
|
.It Fl w Ar interval
|
||||||
Specify an
|
Specify an
|
||||||
.Ar interval ,
|
.Ar interval ,
|
||||||
in seconds, between attempts to dismount filesystems that have exceeded their
|
in seconds, between attempts to dismount file systems that have exceeded their
|
||||||
cached times. The default is 2 minutes.
|
cached times. The default is 2 minutes.
|
||||||
.It Fl x Ar options
|
.It Fl x Ar options
|
||||||
Specify run-time logging options. The options are a comma separated list
|
Specify run-time logging options. The options are a comma separated list
|
||||||
@ -286,7 +286,7 @@ will not be processed.
|
|||||||
.Sh FILES
|
.Sh FILES
|
||||||
.Bl -tag -width /axx
|
.Bl -tag -width /axx
|
||||||
.It Pa /.amd_mnt
|
.It Pa /.amd_mnt
|
||||||
directory under which filesystems are dynamically mounted
|
directory under which file systems are dynamically mounted
|
||||||
.It Pa /etc/amd.conf
|
.It Pa /etc/amd.conf
|
||||||
default configuration file
|
default configuration file
|
||||||
.El
|
.El
|
||||||
@ -295,7 +295,7 @@ Some care may be required when creating a mount map.
|
|||||||
.Pp
|
.Pp
|
||||||
Symbolic links on an
|
Symbolic links on an
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
filesystem can be incredibly inefficient.
|
file system can be incredibly inefficient.
|
||||||
In most implementations of
|
In most implementations of
|
||||||
.Tn NFS ,
|
.Tn NFS ,
|
||||||
their interpolations are not cached by
|
their interpolations are not cached by
|
||||||
|
@ -66,14 +66,14 @@ program.
|
|||||||
Communication is by
|
Communication is by
|
||||||
.Tn RPC .
|
.Tn RPC .
|
||||||
Three modes of operation are supported by the current protocol.
|
Three modes of operation are supported by the current protocol.
|
||||||
By default a list of mount points and auto-mounted filesystems
|
By default a list of mount points and auto-mounted file systems
|
||||||
is output.
|
is output.
|
||||||
An alternative host can be specified using the
|
An alternative host can be specified using the
|
||||||
.Fl h
|
.Fl h
|
||||||
option.
|
option.
|
||||||
.Pp
|
.Pp
|
||||||
If directory names are given, as output by default,
|
If directory names are given, as output by default,
|
||||||
then per-filesystem information is displayed.
|
then per file system information is displayed.
|
||||||
.Sh OPTIONS
|
.Sh OPTIONS
|
||||||
.Bl -tag -width Ds
|
.Bl -tag -width Ds
|
||||||
.It Fl f
|
.It Fl f
|
||||||
@ -97,8 +97,8 @@ refresh
|
|||||||
open file handle on the log file, so that it can be rotated and compressed via
|
open file handle on the log file, so that it can be rotated and compressed via
|
||||||
daily cron jobs.
|
daily cron jobs.
|
||||||
.It Fl m
|
.It Fl m
|
||||||
Request the automounter to provide a list of mounted filesystems,
|
Request the automounter to provide a list of mounted file systems,
|
||||||
including the number of references to each filesystem and any error
|
including the number of references to each file system and any error
|
||||||
which occurred while mounting.
|
which occurred while mounting.
|
||||||
.It Fl p
|
.It Fl p
|
||||||
Return the process ID of the remote or locally running
|
Return the process ID of the remote or locally running
|
||||||
@ -112,9 +112,9 @@ script.
|
|||||||
.It Fl s
|
.It Fl s
|
||||||
Request the automounter to provide system-wide mount statistics.
|
Request the automounter to provide system-wide mount statistics.
|
||||||
.It Fl u
|
.It Fl u
|
||||||
Request the automounter to unmount the named filesystems
|
Request the automounter to unmount the named file systems
|
||||||
instead of providing information about them. Unmounts are requested,
|
instead of providing information about them. Unmounts are requested,
|
||||||
not forced. They merely cause the mounted filesystem to timeout,
|
not forced. They merely cause the mounted file system to timeout,
|
||||||
which will be picked up by
|
which will be picked up by
|
||||||
.Nm amd Ns \'s
|
.Nm amd Ns \'s
|
||||||
main scheduler thus causing the normal timeout action to be taken.
|
main scheduler thus causing the normal timeout action to be taken.
|
||||||
|
@ -83,9 +83,9 @@ found. The remote mount table is not changed.
|
|||||||
.It Fl A
|
.It Fl A
|
||||||
Issues a command to the remote mountd declaring that
|
Issues a command to the remote mountd declaring that
|
||||||
.Em all
|
.Em all
|
||||||
of its filesystems have been unmounted. This should be used with caution, as
|
of its file systems have been unmounted. This should be used with caution, as
|
||||||
it removes all remote mount entries pertaining to the local system, whether or
|
it removes all remote mount entries pertaining to the local system, whether or
|
||||||
not any filesystems are still mounted locally.
|
not any file systems are still mounted locally.
|
||||||
.It Fl v
|
.It Fl v
|
||||||
Be quiet. Suppresses error messages due to timeouts and
|
Be quiet. Suppresses error messages due to timeouts and
|
||||||
.Dq Program not Registered ,
|
.Dq Program not Registered ,
|
||||||
@ -135,7 +135,7 @@ and verifying the resulting path).
|
|||||||
Symbolic links on the server will cause the path in the remote entry to differ
|
Symbolic links on the server will cause the path in the remote entry to differ
|
||||||
from the one in
|
from the one in
|
||||||
.Pa /etc/mtab .
|
.Pa /etc/mtab .
|
||||||
To catch those cases, a filesystem is also deemed mounted if its
|
To catch those cases, a file system is also deemed mounted if its
|
||||||
.Em local
|
.Em local
|
||||||
mount point is identical to the remote entry.
|
mount point is identical to the remote entry.
|
||||||
I.e., on a SunOS diskless client,
|
I.e., on a SunOS diskless client,
|
||||||
|
@ -41,7 +41,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm fsinfo
|
.Nm fsinfo
|
||||||
.Nd co-ordinate site-wide filesystem information
|
.Nd co-ordinate site-wide file system information
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.Nm
|
.Nm
|
||||||
.Op Fl qv
|
.Op Fl qv
|
||||||
@ -124,7 +124,7 @@ For each machine defined in the configuration files, a
|
|||||||
file is created with the file name determined by prefixing this
|
file is created with the file name determined by prefixing this
|
||||||
.Ar fstabs_prefix
|
.Ar fstabs_prefix
|
||||||
string with the name of the machine. These files contain entries
|
string with the name of the machine. These files contain entries
|
||||||
for filesystems and partitions to mount at boot time.
|
for file systems and partitions to mount at boot time.
|
||||||
.It Fl h Ar hostname
|
.It Fl h Ar hostname
|
||||||
Defines the hostname of the destination machine to process for.
|
Defines the hostname of the destination machine to process for.
|
||||||
If this is not specified, it defaults to the local machine name,
|
If this is not specified, it defaults to the local machine name,
|
||||||
|
@ -70,7 +70,7 @@
|
|||||||
.Op linkname Op subdir
|
.Op linkname Op subdir
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
.Nm
|
.Nm
|
||||||
is a daemon which implements a filesystem containing a symbolic link to
|
is a daemon which implements a file system containing a symbolic link to
|
||||||
subdirectory within a user's home directory, depending on the user
|
subdirectory within a user's home directory, depending on the user
|
||||||
which accessed that link. It was primarily designed to redirect
|
which accessed that link. It was primarily designed to redirect
|
||||||
incoming mail to users' home directories, so that it can read from
|
incoming mail to users' home directories, so that it can read from
|
||||||
|
@ -662,7 +662,7 @@ will attempt to unmount all file systems which it knows about. Normally
|
|||||||
leaves all
|
leaves all
|
||||||
(esp.\&)
|
(esp.\&)
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
mounted filesystems intact. Note that
|
mounted file systems intact. Note that
|
||||||
.Nm amd
|
.Nm amd
|
||||||
does not know about file systems mounted before it starts up, unless the
|
does not know about file systems mounted before it starts up, unless the
|
||||||
.Ar restart_mounts
|
.Ar restart_mounts
|
||||||
|
@ -228,7 +228,7 @@ Begin at
|
|||||||
in the archive.
|
in the archive.
|
||||||
.It Fl l
|
.It Fl l
|
||||||
.It Fl -one-file-system
|
.It Fl -one-file-system
|
||||||
Stay in local filesystem when creating an archive (do not cross mount
|
Stay in local file system when creating an archive (do not cross mount
|
||||||
points).
|
points).
|
||||||
.It Fl L Ar number
|
.It Fl L Ar number
|
||||||
.It Fl -tape-length Ar number
|
.It Fl -tape-length Ar number
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm getvfsbyname
|
.Nm getvfsbyname
|
||||||
.Nd get information about a filesystem
|
.Nd get information about a file system
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -49,9 +49,9 @@
|
|||||||
The
|
The
|
||||||
.Fn getvfsbyname
|
.Fn getvfsbyname
|
||||||
function provides access to information about a
|
function provides access to information about a
|
||||||
filesystem module that is configured in the kernel.
|
file system module that is configured in the kernel.
|
||||||
If successful,
|
If successful,
|
||||||
the requested filesystem
|
the requested file system
|
||||||
.Fa xvfsconf
|
.Fa xvfsconf
|
||||||
is returned in the location pointed to by
|
is returned in the location pointed to by
|
||||||
.Fa vfc .
|
.Fa vfc .
|
||||||
@ -61,11 +61,11 @@ are defined as follows:
|
|||||||
.Pp
|
.Pp
|
||||||
.Bl -tag -compact -width vfc_refcount
|
.Bl -tag -compact -width vfc_refcount
|
||||||
.It vfc_name
|
.It vfc_name
|
||||||
the name of the filesystem
|
the name of the file system
|
||||||
.It vfc_typenum
|
.It vfc_typenum
|
||||||
the filesystem type number assigned by the kernel
|
the file system type number assigned by the kernel
|
||||||
.It vfc_refcount
|
.It vfc_refcount
|
||||||
the number of active mount points using the filesystem
|
the number of active mount points using the file system
|
||||||
.It vfc_flags
|
.It vfc_flags
|
||||||
flag bits, as described below
|
flag bits, as described below
|
||||||
.El
|
.El
|
||||||
@ -98,7 +98,7 @@ pointer contains an invalid address.
|
|||||||
.It Bq Er ENOENT
|
.It Bq Er ENOENT
|
||||||
The
|
The
|
||||||
.Fa name
|
.Fa name
|
||||||
specifies a filesystem that is unknown or not configured in the kernel.
|
specifies a file system that is unknown or not configured in the kernel.
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr mount 2 ,
|
.Xr mount 2 ,
|
||||||
|
@ -11,7 +11,7 @@
|
|||||||
.Nm endvfsent ,
|
.Nm endvfsent ,
|
||||||
.Nm vfsisloadable ,
|
.Nm vfsisloadable ,
|
||||||
.Nm vfsload
|
.Nm vfsload
|
||||||
.Nd manage virtual filesystem modules
|
.Nd manage virtual file system modules
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -31,21 +31,21 @@
|
|||||||
The
|
The
|
||||||
.Fn getvfsent
|
.Fn getvfsent
|
||||||
function provides convenient access to a list of installed virtual
|
function provides convenient access to a list of installed virtual
|
||||||
filesystem modules managed by the kernel. It steps through the
|
file system modules managed by the kernel. It steps through the
|
||||||
list of filesystems one at a time. A null pointer is returned when
|
list of file systems one at a time. A null pointer is returned when
|
||||||
no more data is available. The fields in a
|
no more data is available. The fields in a
|
||||||
.Dq Li struct ovfsconf
|
.Dq Li struct ovfsconf
|
||||||
are as follows:
|
are as follows:
|
||||||
.Pp
|
.Pp
|
||||||
.Bl -tag -compact -width vfc_refcount
|
.Bl -tag -compact -width vfc_refcount
|
||||||
.It vfc_name
|
.It vfc_name
|
||||||
the name of the filesystem
|
the name of the file system
|
||||||
.It vfc_index
|
.It vfc_index
|
||||||
the filesystem type number assigned by the kernel and used in calls to
|
the file system type number assigned by the kernel and used in calls to
|
||||||
.Xr mount 2
|
.Xr mount 2
|
||||||
.It vfc_refcount
|
.It vfc_refcount
|
||||||
the number of references to this filesystem
|
the number of references to this file system
|
||||||
(usually the number of mounts, but one greater for filesystems which
|
(usually the number of mounts, but one greater for file systems which
|
||||||
cannot be unloaded or which are statically linked into the kernel)
|
cannot be unloaded or which are statically linked into the kernel)
|
||||||
.It vfc_flags
|
.It vfc_flags
|
||||||
flag bits
|
flag bits
|
||||||
@ -72,7 +72,7 @@ The
|
|||||||
.Fn setvfsent
|
.Fn setvfsent
|
||||||
and
|
and
|
||||||
.Fn endvfsent
|
.Fn endvfsent
|
||||||
functions are used to control caching of the filesystem list, which is
|
functions are used to control caching of the file system list, which is
|
||||||
obtained in toto from the kernel via
|
obtained in toto from the kernel via
|
||||||
.Xr sysctl 3 .
|
.Xr sysctl 3 .
|
||||||
If the
|
If the
|
||||||
@ -107,9 +107,9 @@ to succeed.
|
|||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Fn vfsload
|
.Fn vfsload
|
||||||
function attempts to load a kernel module implementing filesystem
|
function attempts to load a kernel module implementing file system
|
||||||
.Fa name .
|
.Fa name .
|
||||||
It returns zero if the filesystem module was successfully located and
|
It returns zero if the file system module was successfully located and
|
||||||
loaded, or non-zero otherwise. It should only be called in the
|
loaded, or non-zero otherwise. It should only be called in the
|
||||||
following circumstances:
|
following circumstances:
|
||||||
.Bl -enum
|
.Bl -enum
|
||||||
@ -172,7 +172,7 @@ may be set to one of the values documented for
|
|||||||
.Xr mount 8
|
.Xr mount 8
|
||||||
.Sh AUTHORS
|
.Sh AUTHORS
|
||||||
.An -nosplit
|
.An -nosplit
|
||||||
The loadable filesystem support was written by
|
The loadable file system support was written by
|
||||||
.An Garrett A. Wollman ,
|
.An Garrett A. Wollman ,
|
||||||
based on generic loadable kernel module support by
|
based on generic loadable kernel module support by
|
||||||
.An Terry Lambert .
|
.An Terry Lambert .
|
||||||
|
@ -34,7 +34,7 @@
|
|||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm statvfs ,
|
.Nm statvfs ,
|
||||||
.Nm fstatvfs
|
.Nm fstatvfs
|
||||||
.Nd retrieve filesystem information
|
.Nd retrieve file system information
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -51,17 +51,17 @@ and
|
|||||||
functions fill the structure pointed to by
|
functions fill the structure pointed to by
|
||||||
.Fa buf
|
.Fa buf
|
||||||
with garbage.
|
with garbage.
|
||||||
This garbage will occasionally bear resemblance to filesystem
|
This garbage will occasionally bear resemblance to file system
|
||||||
statistics, but portable applications must not depend on this.
|
statistics, but portable applications must not depend on this.
|
||||||
Applications must pass a pathname or file descriptor which refers to a
|
Applications must pass a pathname or file descriptor which refers to a
|
||||||
file on the filesystem in which they are interested.
|
file on the file system in which they are interested.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Vt statvfs
|
.Vt statvfs
|
||||||
structure contains the following members:
|
structure contains the following members:
|
||||||
.Bl -tag -offset indent -width ".Va f_namemax"
|
.Bl -tag -offset indent -width ".Va f_namemax"
|
||||||
.It Va f_namemax
|
.It Va f_namemax
|
||||||
The maximum length in bytes of a file name on this filesystem.
|
The maximum length in bytes of a file name on this file system.
|
||||||
Applications should use
|
Applications should use
|
||||||
.Xr pathconf 3
|
.Xr pathconf 3
|
||||||
instead.
|
instead.
|
||||||
@ -69,19 +69,19 @@ instead.
|
|||||||
Not meaningful in this implementation.
|
Not meaningful in this implementation.
|
||||||
.It Va f_frsize
|
.It Va f_frsize
|
||||||
The size in bytes of the minimum unit of allocation on this
|
The size in bytes of the minimum unit of allocation on this
|
||||||
filesystem.
|
file system.
|
||||||
(This corresponds to the
|
(This corresponds to the
|
||||||
.Va f_bsize
|
.Va f_bsize
|
||||||
member of
|
member of
|
||||||
.Vt "struct statfs" . )
|
.Vt "struct statfs" . )
|
||||||
.It Va f_bsize
|
.It Va f_bsize
|
||||||
The preferred length of I/O requests for files on this filesystem.
|
The preferred length of I/O requests for files on this file system.
|
||||||
(Corresponds to the
|
(Corresponds to the
|
||||||
.Va f_iosize
|
.Va f_iosize
|
||||||
member of
|
member of
|
||||||
.Vt "struct statfs" . )
|
.Vt "struct statfs" . )
|
||||||
.It Va f_flag
|
.It Va f_flag
|
||||||
Flags describing mount options for this filesystem; see below.
|
Flags describing mount options for this file system; see below.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
In addition, there are three members of type
|
In addition, there are three members of type
|
||||||
@ -108,14 +108,14 @@ There are two flags defined for the
|
|||||||
member:
|
member:
|
||||||
.Bl -tag -offset indent -width ".Dv ST_NOSUID"
|
.Bl -tag -offset indent -width ".Dv ST_NOSUID"
|
||||||
.It Dv ST_RDONLY
|
.It Dv ST_RDONLY
|
||||||
The filesystem is mounted read-only.
|
The file system is mounted read-only.
|
||||||
.It Dv ST_NOSUID
|
.It Dv ST_NOSUID
|
||||||
The semantics of the
|
The semantics of the
|
||||||
.Dv S_ISUID
|
.Dv S_ISUID
|
||||||
and
|
and
|
||||||
.Dv S_ISGID
|
.Dv S_ISGID
|
||||||
file mode bits
|
file mode bits
|
||||||
are not supported by, or are disabled on, this filesystem.
|
are not supported by, or are disabled on, this file system.
|
||||||
.El
|
.El
|
||||||
.Sh IMPLEMENTATION NOTES
|
.Sh IMPLEMENTATION NOTES
|
||||||
The
|
The
|
||||||
@ -152,7 +152,7 @@ and
|
|||||||
functions may also fail for the following reason:
|
functions may also fail for the following reason:
|
||||||
.Bl -tag -width Er
|
.Bl -tag -width Er
|
||||||
.It Bq Er EOVERFLOW
|
.It Bq Er EOVERFLOW
|
||||||
One or more of the filesystem statistics has a value which cannot be
|
One or more of the file system statistics has a value which cannot be
|
||||||
represented by the data types used in
|
represented by the data types used in
|
||||||
.Vt "struct statvfs" .
|
.Vt "struct statvfs" .
|
||||||
.El
|
.El
|
||||||
@ -169,7 +169,7 @@ functions conform to
|
|||||||
As standardized, portable applications cannot depend on these functions
|
As standardized, portable applications cannot depend on these functions
|
||||||
returning any valid information at all.
|
returning any valid information at all.
|
||||||
This implementation attempts to provide as much useful information as
|
This implementation attempts to provide as much useful information as
|
||||||
is provided by the underlying filesystem, subject to the limitations
|
is provided by the underlying file system, subject to the limitations
|
||||||
of the specified data types.
|
of the specified data types.
|
||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
The
|
The
|
||||||
|
@ -188,7 +188,7 @@ listed here, and described in separate sections below.
|
|||||||
.Bl -column CTLXMACHDEPXXX "Next level namesXXXXXX" -offset indent
|
.Bl -column CTLXMACHDEPXXX "Next level namesXXXXXX" -offset indent
|
||||||
.It Sy "Name Next level names Description"
|
.It Sy "Name Next level names Description"
|
||||||
.It "CTL\_DEBUG sys/sysctl.h Debugging"
|
.It "CTL\_DEBUG sys/sysctl.h Debugging"
|
||||||
.It "CTL\_VFS sys/mount.h Filesystem"
|
.It "CTL\_VFS sys/mount.h File system"
|
||||||
.It "CTL\_HW sys/sysctl.h Generic CPU, I/O"
|
.It "CTL\_HW sys/sysctl.h Generic CPU, I/O"
|
||||||
.It "CTL\_KERN sys/sysctl.h High kernel limits"
|
.It "CTL\_KERN sys/sysctl.h High kernel limits"
|
||||||
.It "CTL\_MACHDEP sys/sysctl.h Machine dependent"
|
.It "CTL\_MACHDEP sys/sysctl.h Machine dependent"
|
||||||
@ -251,21 +251,21 @@ struct ctldebug debug5 = { "dospecialcheck", &dospecialcheck };
|
|||||||
.Ed
|
.Ed
|
||||||
.Ss CTL_VFS
|
.Ss CTL_VFS
|
||||||
A distinguished second level name, VFS_GENERIC,
|
A distinguished second level name, VFS_GENERIC,
|
||||||
is used to get general information about all filesystems.
|
is used to get general information about all file systems.
|
||||||
One of its third level identifiers is VFS_MAXTYPENUM
|
One of its third level identifiers is VFS_MAXTYPENUM
|
||||||
that gives the highest valid filesystem type number.
|
that gives the highest valid file system type number.
|
||||||
Its other third level identifier is VFS_CONF that
|
Its other third level identifier is VFS_CONF that
|
||||||
returns configuration information about the filesystem
|
returns configuration information about the file system
|
||||||
type given as a fourth level identifier (see
|
type given as a fourth level identifier (see
|
||||||
.Xr getvfsbyname 3
|
.Xr getvfsbyname 3
|
||||||
as an example of its use).
|
as an example of its use).
|
||||||
The remaining second level identifiers are the
|
The remaining second level identifiers are the
|
||||||
filesystem type number returned by a
|
file system type number returned by a
|
||||||
.Xr statfs 2
|
.Xr statfs 2
|
||||||
call or from VFS_CONF.
|
call or from VFS_CONF.
|
||||||
The third level identifiers available for each filesystem
|
The third level identifiers available for each file system
|
||||||
are given in the header file that defines the mount
|
are given in the header file that defines the mount
|
||||||
argument structure for that filesystem.
|
argument structure for that file system.
|
||||||
.Ss CTL_HW
|
.Ss CTL_HW
|
||||||
The string and integer information available for the CTL_HW level
|
The string and integer information available for the CTL_HW level
|
||||||
is detailed below.
|
is detailed below.
|
||||||
|
@ -52,7 +52,7 @@ the
|
|||||||
function undoes the aforementioned operation,
|
function undoes the aforementioned operation,
|
||||||
and converts a human-readable string representing a namespace to a
|
and converts a human-readable string representing a namespace to a
|
||||||
namespace identifier.
|
namespace identifier.
|
||||||
Although a filesystem may implement arbitrary namespaces,
|
Although a file system may implement arbitrary namespaces,
|
||||||
these functions only support the
|
these functions only support the
|
||||||
.Dv EXTATTR_NAMESPACE_USER
|
.Dv EXTATTR_NAMESPACE_USER
|
||||||
.Pq Dq user
|
.Pq Dq user
|
||||||
|
@ -1426,7 +1426,7 @@ which may be
|
|||||||
.Dv RPC_ANYSOCK ,
|
.Dv RPC_ANYSOCK ,
|
||||||
in which case a new socket is created.
|
in which case a new socket is created.
|
||||||
.Fa *path
|
.Fa *path
|
||||||
is a variable-length filesystem pathname of
|
is a variable-length file system pathname of
|
||||||
at most 104 characters.
|
at most 104 characters.
|
||||||
This file is
|
This file is
|
||||||
.Em not
|
.Em not
|
||||||
|
@ -473,7 +473,7 @@ and
|
|||||||
functions conform to
|
functions conform to
|
||||||
.St -isoC .
|
.St -isoC .
|
||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
The present allocation implementation started out as a filesystem for a
|
The present allocation implementation started out as a file system for a
|
||||||
drum attached to a 20bit binary challenged computer which was built
|
drum attached to a 20bit binary challenged computer which was built
|
||||||
with discrete germanium transistors.
|
with discrete germanium transistors.
|
||||||
It has since graduated to
|
It has since graduated to
|
||||||
|
@ -112,7 +112,7 @@ The
|
|||||||
VM system totally ignores the sticky bit
|
VM system totally ignores the sticky bit
|
||||||
.Pq Dv ISVTX
|
.Pq Dv ISVTX
|
||||||
for executables.
|
for executables.
|
||||||
On UFS-based filesystems (FFS, LFS) the sticky
|
On UFS-based file systems (FFS, LFS) the sticky
|
||||||
bit may only be set upon directories.
|
bit may only be set upon directories.
|
||||||
.Pp
|
.Pp
|
||||||
If mode
|
If mode
|
||||||
@ -127,7 +127,7 @@ For more details of the properties of the sticky bit, see
|
|||||||
.Xr sticky 8 .
|
.Xr sticky 8 .
|
||||||
.Pp
|
.Pp
|
||||||
If mode ISUID (set UID) is set on a directory,
|
If mode ISUID (set UID) is set on a directory,
|
||||||
and the MNT_SUIDDIR option was used in the mount of the filesystem,
|
and the MNT_SUIDDIR option was used in the mount of the file system,
|
||||||
then the owner of any new files and sub-directories
|
then the owner of any new files and sub-directories
|
||||||
created within this directory are set
|
created within this directory are set
|
||||||
to be the same as the owner of that directory.
|
to be the same as the owner of that directory.
|
||||||
@ -145,7 +145,7 @@ It provides security holes for shell users and as
|
|||||||
such should not be used on shell machines, especially on home directories.
|
such should not be used on shell machines, especially on home directories.
|
||||||
This option requires the SUIDDIR
|
This option requires the SUIDDIR
|
||||||
option in the kernel to work.
|
option in the kernel to work.
|
||||||
Only UFS filesystems support this option.
|
Only UFS file systems support this option.
|
||||||
For more details of the suiddir mount option, see
|
For more details of the suiddir mount option, see
|
||||||
.Xr mount 8 .
|
.Xr mount 8 .
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -139,7 +139,7 @@ the namespace in which the extended attribute resides; see
|
|||||||
the name of the extended attribute
|
the name of the extended attribute
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
Named extended attribute semantics vary by filesystem implementing the call.
|
Named extended attribute semantics vary by file system implementing the call.
|
||||||
Not all operations may be supported for a particular attribute.
|
Not all operations may be supported for a particular attribute.
|
||||||
Additionally, the format of the data in
|
Additionally, the format of the data in
|
||||||
.Fa data
|
.Fa data
|
||||||
@ -174,7 +174,7 @@ is set to indicate the error.
|
|||||||
.Rv -std extattr_delete_file
|
.Rv -std extattr_delete_file
|
||||||
.Sh ERRORS
|
.Sh ERRORS
|
||||||
The following errors may be returned by the system calls themselves.
|
The following errors may be returned by the system calls themselves.
|
||||||
Additionally, the filesystem implementing the call may return any
|
Additionally, the file system implementing the call may return any
|
||||||
other errors it desires.
|
other errors it desires.
|
||||||
.Bl -tag -width Er
|
.Bl -tag -width Er
|
||||||
.It Bq Er EFAULT
|
.It Bq Er EFAULT
|
||||||
|
@ -38,7 +38,7 @@
|
|||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm getdirentries ,
|
.Nm getdirentries ,
|
||||||
.Nm getdents
|
.Nm getdents
|
||||||
.Nd "get directory entries in a filesystem independent format"
|
.Nd "get directory entries in a file system independent format"
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -58,7 +58,7 @@ referenced by the file descriptor
|
|||||||
.Fa fd
|
.Fa fd
|
||||||
into the buffer pointed to by
|
into the buffer pointed to by
|
||||||
.Fa buf ,
|
.Fa buf ,
|
||||||
in a filesystem independent format.
|
in a file system independent format.
|
||||||
Up to
|
Up to
|
||||||
.Fa nbytes
|
.Fa nbytes
|
||||||
of data will be transferred.
|
of data will be transferred.
|
||||||
@ -68,7 +68,7 @@ argument must be greater than or equal to the
|
|||||||
block size associated with the file,
|
block size associated with the file,
|
||||||
see
|
see
|
||||||
.Xr stat 2 .
|
.Xr stat 2 .
|
||||||
Some filesystems may not support these functions
|
Some file systems may not support these functions
|
||||||
with buffers smaller than this size.
|
with buffers smaller than this size.
|
||||||
.Pp
|
.Pp
|
||||||
The data in the buffer is a series of
|
The data in the buffer is a series of
|
||||||
@ -85,7 +85,7 @@ char d_name[MAXNAMELEN + 1]; /* see below */
|
|||||||
The
|
The
|
||||||
.Fa d_fileno
|
.Fa d_fileno
|
||||||
entry is a number which is unique for each
|
entry is a number which is unique for each
|
||||||
distinct file in the filesystem.
|
distinct file in the file system.
|
||||||
Files that are linked by hard links (see
|
Files that are linked by hard links (see
|
||||||
.Xr link 2 )
|
.Xr link 2 )
|
||||||
have the same
|
have the same
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm getfsstat
|
.Nm getfsstat
|
||||||
.Nd get list of all mounted filesystems
|
.Nd get list of all mounted file systems
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -48,7 +48,7 @@
|
|||||||
.Fn getfsstat "struct statfs *buf" "long bufsize" "int flags"
|
.Fn getfsstat "struct statfs *buf" "long bufsize" "int flags"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
.Fn Getfsstat
|
.Fn Getfsstat
|
||||||
returns information about all mounted filesystems.
|
returns information about all mounted file systems.
|
||||||
.Fa Buf
|
.Fa Buf
|
||||||
is a pointer to
|
is a pointer to
|
||||||
.Xr statfs
|
.Xr statfs
|
||||||
@ -73,53 +73,53 @@ struct statfs {
|
|||||||
long f_files; /* total file nodes in file system */
|
long f_files; /* total file nodes in file system */
|
||||||
long f_ffree; /* free file nodes in fs */
|
long f_ffree; /* free file nodes in fs */
|
||||||
fsid_t f_fsid; /* file system id */
|
fsid_t f_fsid; /* file system id */
|
||||||
uid_t f_owner; /* user that mounted the filesystem */
|
uid_t f_owner; /* user that mounted the file system */
|
||||||
int f_type; /* type of filesystem (see below) */
|
int f_type; /* type of file system (see below) */
|
||||||
int f_flags; /* copy of mount flags */
|
int f_flags; /* copy of mount flags */
|
||||||
long f_spare[2]; /* spare for later */
|
long f_spare[2]; /* spare for later */
|
||||||
char f_fstypename[MFSNAMELEN];/* fs type name */
|
char f_fstypename[MFSNAMELEN];/* fs type name */
|
||||||
char f_mntonname[MNAMELEN];/* directory on which mounted */
|
char f_mntonname[MNAMELEN];/* directory on which mounted */
|
||||||
char f_mntfromname[MNAMELEN];/* mounted filesystem */
|
char f_mntfromname[MNAMELEN];/* mounted file system */
|
||||||
};
|
};
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
The flags that may be returned include:
|
The flags that may be returned include:
|
||||||
.Bl -tag -width MNT_ASYNCHRONOUS
|
.Bl -tag -width MNT_ASYNCHRONOUS
|
||||||
.It Dv MNT_RDONLY
|
.It Dv MNT_RDONLY
|
||||||
The filesystem is mounted read-only;
|
The file system is mounted read-only;
|
||||||
Even the super-user may not write on it.
|
Even the super-user may not write on it.
|
||||||
.It Dv MNT_NOEXEC
|
.It Dv MNT_NOEXEC
|
||||||
Files may not be executed from the filesystem.
|
Files may not be executed from the file system.
|
||||||
.It Dv MNT_NOSUID
|
.It Dv MNT_NOSUID
|
||||||
Setuid and setgid bits on files are not honored when they are executed.
|
Setuid and setgid bits on files are not honored when they are executed.
|
||||||
.It Dv MNT_NODEV
|
.It Dv MNT_NODEV
|
||||||
Special files in the filesystem may not be opened.
|
Special files in the file system may not be opened.
|
||||||
.It Dv MNT_SYNCHRONOUS
|
.It Dv MNT_SYNCHRONOUS
|
||||||
All I/O to the filesystem is done synchronously.
|
All I/O to the file system is done synchronously.
|
||||||
.It Dv MNT_ASYNCHRONOUS
|
.It Dv MNT_ASYNCHRONOUS
|
||||||
No filesystem I/O is done synchronously.
|
No file system I/O is done synchronously.
|
||||||
.It Dv MNT_LOCAL
|
.It Dv MNT_LOCAL
|
||||||
The filesystem resides locally.
|
The file system resides locally.
|
||||||
.It Dv MNT_QUOTA
|
.It Dv MNT_QUOTA
|
||||||
The filesystem has quotas enabled on it.
|
The file system has quotas enabled on it.
|
||||||
.It Dv MNT_ROOTFS
|
.It Dv MNT_ROOTFS
|
||||||
Identifies the root filesystem.
|
Identifies the root file system.
|
||||||
.It Dv MNT_EXRDONLY
|
.It Dv MNT_EXRDONLY
|
||||||
The filesystem is exported read-only.
|
The file system is exported read-only.
|
||||||
.It Dv MNT_EXPORTED
|
.It Dv MNT_EXPORTED
|
||||||
The filesystem is exported for both reading and writing.
|
The file system is exported for both reading and writing.
|
||||||
.It Dv MNT_DEFEXPORTED
|
.It Dv MNT_DEFEXPORTED
|
||||||
The filesystem is exported for both reading and writing to any Internet host.
|
The file system is exported for both reading and writing to any Internet host.
|
||||||
.It Dv MNT_EXPORTANON
|
.It Dv MNT_EXPORTANON
|
||||||
The filesystem maps all remote accesses to the anonymous user.
|
The file system maps all remote accesses to the anonymous user.
|
||||||
.It Dv MNT_EXKERB
|
.It Dv MNT_EXKERB
|
||||||
The filesystem is exported with Kerberos uid mapping.
|
The file system is exported with Kerberos uid mapping.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
Fields that are undefined for a particular filesystem are set to -1.
|
Fields that are undefined for a particular file system are set to -1.
|
||||||
The buffer is filled with an array of
|
The buffer is filled with an array of
|
||||||
.Fa fsstat
|
.Fa fsstat
|
||||||
structures, one for each mounted filesystem
|
structures, one for each mounted file system
|
||||||
up to the size specified by
|
up to the size specified by
|
||||||
.Fa bufsize .
|
.Fa bufsize .
|
||||||
.Pp
|
.Pp
|
||||||
@ -127,7 +127,7 @@ If
|
|||||||
.Fa buf
|
.Fa buf
|
||||||
is given as NULL,
|
is given as NULL,
|
||||||
.Fn getfsstat
|
.Fn getfsstat
|
||||||
returns just the number of mounted filesystems.
|
returns just the number of mounted file systems.
|
||||||
.Pp
|
.Pp
|
||||||
Normally
|
Normally
|
||||||
.Fa flags
|
.Fa flags
|
||||||
@ -139,10 +139,10 @@ is set to
|
|||||||
.Dv MNT_NOWAIT ,
|
.Dv MNT_NOWAIT ,
|
||||||
.Fn getfsstat
|
.Fn getfsstat
|
||||||
will return the information it has available without requesting
|
will return the information it has available without requesting
|
||||||
an update from each filesystem.
|
an update from each file system.
|
||||||
Thus, some of the information will be out of date, but
|
Thus, some of the information will be out of date, but
|
||||||
.Fn getfsstat
|
.Fn getfsstat
|
||||||
will not block waiting for information from a filesystem that is
|
will not block waiting for information from a file system that is
|
||||||
unable to respond.
|
unable to respond.
|
||||||
.Sh RETURN VALUES
|
.Sh RETURN VALUES
|
||||||
Upon successful completion, the number of
|
Upon successful completion, the number of
|
||||||
@ -161,7 +161,7 @@ points to an invalid address.
|
|||||||
.It Bq Er EIO
|
.It Bq Er EIO
|
||||||
An
|
An
|
||||||
.Tn I/O
|
.Tn I/O
|
||||||
error occurred while reading from or writing to the filesystem.
|
error occurred while reading from or writing to the file system.
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr statfs 2 ,
|
.Xr statfs 2 ,
|
||||||
|
@ -394,7 +394,7 @@ was exhausted.
|
|||||||
.It Er 70 ESTALE Em "Stale NFS file handle" .
|
.It Er 70 ESTALE Em "Stale NFS file handle" .
|
||||||
An attempt was made to access an open file (on an
|
An attempt was made to access an open file (on an
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
filesystem)
|
file system)
|
||||||
which is now unavailable as referenced by the file descriptor.
|
which is now unavailable as referenced by the file descriptor.
|
||||||
This may indicate the file was deleted on the
|
This may indicate the file was deleted on the
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
@ -432,11 +432,11 @@ the wrong format.
|
|||||||
.It Er 80 EAUTH Em "Authentication error" .
|
.It Er 80 EAUTH Em "Authentication error" .
|
||||||
Attempted to use an invalid authentication ticket to mount a
|
Attempted to use an invalid authentication ticket to mount a
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
filesystem.
|
file system.
|
||||||
.It Er 81 ENEEDAUTH Em "Need authenticator" .
|
.It Er 81 ENEEDAUTH Em "Need authenticator" .
|
||||||
An authentication ticket must be obtained before the given
|
An authentication ticket must be obtained before the given
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
filesystem may be mounted.
|
file system may be mounted.
|
||||||
.It Er 82 EIDRM Em "Identifier removed" .
|
.It Er 82 EIDRM Em "Identifier removed" .
|
||||||
An IPC identifier was removed while the current process was waiting on it.
|
An IPC identifier was removed while the current process was waiting on it.
|
||||||
.It Er 83 ENOMSG Em "No message of desired type" .
|
.It Er 83 ENOMSG Em "No message of desired type" .
|
||||||
|
@ -164,5 +164,5 @@ function call appeared in
|
|||||||
The
|
The
|
||||||
.Fn link
|
.Fn link
|
||||||
system call traditionally allows the super-user to link directories which
|
system call traditionally allows the super-user to link directories which
|
||||||
corrupts the filesystem coherency. This implementation no longer permits
|
corrupts the file system coherency. This implementation no longer permits
|
||||||
it.
|
it.
|
||||||
|
@ -104,8 +104,8 @@ modified again.
|
|||||||
.It Dv MADV_NOSYNC
|
.It Dv MADV_NOSYNC
|
||||||
Request that the system not flush the data associated with this map to
|
Request that the system not flush the data associated with this map to
|
||||||
physical backing store unless it needs to. Typically this prevents the
|
physical backing store unless it needs to. Typically this prevents the
|
||||||
filesystem update daemon from gratuitously writing pages dirtied
|
file system update daemon from gratuitously writing pages dirtied
|
||||||
by the VM system to physical disk. Note that VM/filesystem coherency is
|
by the VM system to physical disk. Note that VM/file system coherency is
|
||||||
always maintained, this feature simply ensures that the mapped data is
|
always maintained, this feature simply ensures that the mapped data is
|
||||||
only flush when it needs to be, usually by the system pager.
|
only flush when it needs to be, usually by the system pager.
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -45,7 +45,7 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn mknod "const char *path" "mode_t mode" "dev_t dev"
|
.Fn mknod "const char *path" "mode_t mode" "dev_t dev"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The filesystem node
|
The file system node
|
||||||
.Fa path
|
.Fa path
|
||||||
is created with the file type and access permissions specified in
|
is created with the file type and access permissions specified in
|
||||||
.Fa mode .
|
.Fa mode .
|
||||||
|
@ -145,7 +145,7 @@ this option any VM pages you dirty may be flushed to disk every so often
|
|||||||
(every 30-60 seconds usually) which can create performance problems if you
|
(every 30-60 seconds usually) which can create performance problems if you
|
||||||
do not need that to occur (such as when you are using shared file-backed
|
do not need that to occur (such as when you are using shared file-backed
|
||||||
mmap regions for IPC purposes).
|
mmap regions for IPC purposes).
|
||||||
Note that VM/filesystem coherency is
|
Note that VM/file system coherency is
|
||||||
maintained whether you use
|
maintained whether you use
|
||||||
.Dv MAP_NOSYNC
|
.Dv MAP_NOSYNC
|
||||||
or not.
|
or not.
|
||||||
@ -197,9 +197,9 @@ The
|
|||||||
.Xr msync 2
|
.Xr msync 2
|
||||||
system call is obsolete since
|
system call is obsolete since
|
||||||
.Bx
|
.Bx
|
||||||
implements a coherent filesystem buffer cache.
|
implements a coherent file system buffer cache.
|
||||||
However, it may be
|
However, it may be
|
||||||
used to associate dirty VM pages with filesystem buffers and thus cause
|
used to associate dirty VM pages with file system buffers and thus cause
|
||||||
them to be flushed to physical media sooner rather then later.
|
them to be flushed to physical media sooner rather then later.
|
||||||
.It Dv MAP_PRIVATE
|
.It Dv MAP_PRIVATE
|
||||||
Modifications are private.
|
Modifications are private.
|
||||||
@ -346,8 +346,8 @@ this gives
|
|||||||
.Fx
|
.Fx
|
||||||
a maximum of 8TB filesizes.
|
a maximum of 8TB filesizes.
|
||||||
It is actually bugs in
|
It is actually bugs in
|
||||||
the filesystem code that causes the limit to be further restricted to
|
the file system code that causes the limit to be further restricted to
|
||||||
1TB (loss of precision when doing blockno calculations).
|
1TB (loss of precision when doing blockno calculations).
|
||||||
.Pp
|
.Pp
|
||||||
Another reason for the 2GB limit is that filesystem metadata can
|
Another reason for the 2GB limit is that file system metadata can
|
||||||
reside at negative offsets.
|
reside at negative offsets.
|
||||||
|
@ -38,7 +38,7 @@
|
|||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm mount ,
|
.Nm mount ,
|
||||||
.Nm unmount
|
.Nm unmount
|
||||||
.Nd mount or dismount a filesystem
|
.Nd mount or dismount a file system
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -52,12 +52,12 @@
|
|||||||
The
|
The
|
||||||
.Fn mount
|
.Fn mount
|
||||||
function grafts
|
function grafts
|
||||||
a filesystem object onto the system file tree
|
a file system object onto the system file tree
|
||||||
at the point
|
at the point
|
||||||
.Ar dir .
|
.Ar dir .
|
||||||
The argument
|
The argument
|
||||||
.Ar data
|
.Ar data
|
||||||
describes the filesystem object to be mounted.
|
describes the file system object to be mounted.
|
||||||
The argument
|
The argument
|
||||||
.Ar type
|
.Ar type
|
||||||
tells the kernel how to interpret
|
tells the kernel how to interpret
|
||||||
@ -65,41 +65,41 @@ tells the kernel how to interpret
|
|||||||
(See
|
(See
|
||||||
.Ar type
|
.Ar type
|
||||||
below).
|
below).
|
||||||
The contents of the filesystem
|
The contents of the file system
|
||||||
become available through the new mount point
|
become available through the new mount point
|
||||||
.Ar dir .
|
.Ar dir .
|
||||||
Any files in
|
Any files in
|
||||||
.Ar dir
|
.Ar dir
|
||||||
at the time
|
at the time
|
||||||
of a successful mount are swept under the carpet so to speak, and
|
of a successful mount are swept under the carpet so to speak, and
|
||||||
are unavailable until the filesystem is unmounted.
|
are unavailable until the file system is unmounted.
|
||||||
.Pp
|
.Pp
|
||||||
The following
|
The following
|
||||||
.Ar flags
|
.Ar flags
|
||||||
may be specified to
|
may be specified to
|
||||||
suppress default semantics which affect filesystem access.
|
suppress default semantics which affect file system access.
|
||||||
.Bl -tag -width MNT_SYNCHRONOUS
|
.Bl -tag -width MNT_SYNCHRONOUS
|
||||||
.It Dv MNT_RDONLY
|
.It Dv MNT_RDONLY
|
||||||
The filesystem should be treated as read-only;
|
The file system should be treated as read-only;
|
||||||
Even the super-user may not write on it.
|
Even the super-user may not write on it.
|
||||||
Specifying MNT_UPDATE without this option will upgrade
|
Specifying MNT_UPDATE without this option will upgrade
|
||||||
a read-only filesystem to read/write.
|
a read-only file system to read/write.
|
||||||
.It Dv MNT_NOEXEC
|
.It Dv MNT_NOEXEC
|
||||||
Do not allow files to be executed from the filesystem.
|
Do not allow files to be executed from the file system.
|
||||||
.It Dv MNT_NOSUID
|
.It Dv MNT_NOSUID
|
||||||
Do not honor setuid or setgid bits on files when executing them.
|
Do not honor setuid or setgid bits on files when executing them.
|
||||||
.It Dv MNT_NOATIME
|
.It Dv MNT_NOATIME
|
||||||
Disable update of file access times.
|
Disable update of file access times.
|
||||||
.It Dv MNT_NODEV
|
.It Dv MNT_NODEV
|
||||||
Do not interpret special files on the filesystem.
|
Do not interpret special files on the file system.
|
||||||
.It Dv MNT_SUIDDIR
|
.It Dv MNT_SUIDDIR
|
||||||
Directories with the SUID bit set chown new files to their own owner.
|
Directories with the SUID bit set chown new files to their own owner.
|
||||||
.It Dv MNT_SYNCHRONOUS
|
.It Dv MNT_SYNCHRONOUS
|
||||||
All I/O to the filesystem should be done synchronously.
|
All I/O to the file system should be done synchronously.
|
||||||
.It Dv MNT_ASYNC
|
.It Dv MNT_ASYNC
|
||||||
All I/O to the filesystem should be done asynchronously.
|
All I/O to the file system should be done asynchronously.
|
||||||
.It Dv MNT_FORCE
|
.It Dv MNT_FORCE
|
||||||
Force a read-write mount even if the filesystem appears to be unclean.
|
Force a read-write mount even if the file system appears to be unclean.
|
||||||
Dangerous.
|
Dangerous.
|
||||||
.It Dv MNT_NOCLUSTERR
|
.It Dv MNT_NOCLUSTERR
|
||||||
Disable read clustering.
|
Disable read clustering.
|
||||||
@ -110,41 +110,41 @@ Disable write clustering.
|
|||||||
The flag
|
The flag
|
||||||
.Dv MNT_UPDATE
|
.Dv MNT_UPDATE
|
||||||
indicates that the mount command is being applied
|
indicates that the mount command is being applied
|
||||||
to an already mounted filesystem.
|
to an already mounted file system.
|
||||||
This allows the mount flags to be changed without requiring
|
This allows the mount flags to be changed without requiring
|
||||||
that the filesystem be unmounted and remounted.
|
that the file system be unmounted and remounted.
|
||||||
Some filesystems may not allow all flags to be changed.
|
Some file systems may not allow all flags to be changed.
|
||||||
For example,
|
For example,
|
||||||
many filesystems will not allow a change from read-write to read-only.
|
many file systems will not allow a change from read-write to read-only.
|
||||||
.Pp
|
.Pp
|
||||||
The flag
|
The flag
|
||||||
.Dv MNT_RELOAD
|
.Dv MNT_RELOAD
|
||||||
causes the vfs subsystem to update its data structures pertaining to
|
causes the vfs subsystem to update its data structures pertaining to
|
||||||
the specified already mounted filesystem.
|
the specified already mounted file system.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Fa type
|
.Fa type
|
||||||
argument names the filesystem.
|
argument names the file system.
|
||||||
The types of filesystems known to the system can be obtained with
|
The types of file systems known to the system can be obtained with
|
||||||
.Xr lsvfs 1 .
|
.Xr lsvfs 1 .
|
||||||
.Pp
|
.Pp
|
||||||
.Fa Data
|
.Fa Data
|
||||||
is a pointer to a structure that contains the type
|
is a pointer to a structure that contains the type
|
||||||
specific arguments to mount.
|
specific arguments to mount.
|
||||||
The format for these argument structures is described in the
|
The format for these argument structures is described in the
|
||||||
manual page for each filesystem.
|
manual page for each file system.
|
||||||
By convention filesystem manual pages are named
|
By convention file system manual pages are named
|
||||||
by prefixing ``mount_'' to the name of the filesystem as returned by
|
by prefixing ``mount_'' to the name of the file system as returned by
|
||||||
.Xr lsvfs 1 .
|
.Xr lsvfs 1 .
|
||||||
Thus the
|
Thus the
|
||||||
.Nm NFS
|
.Nm NFS
|
||||||
filesystem is described by the
|
file system is described by the
|
||||||
.Xr mount_nfs 8
|
.Xr mount_nfs 8
|
||||||
manual page.
|
manual page.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Fn unmount
|
.Fn unmount
|
||||||
function call disassociates the filesystem from the specified
|
function call disassociates the file system from the specified
|
||||||
mount point
|
mount point
|
||||||
.Fa dir .
|
.Fa dir .
|
||||||
.Pp
|
.Pp
|
||||||
@ -152,12 +152,12 @@ The
|
|||||||
.Fa flags
|
.Fa flags
|
||||||
argument may specify
|
argument may specify
|
||||||
.Dv MNT_FORCE
|
.Dv MNT_FORCE
|
||||||
to specify that the filesystem should be forcibly unmounted or made read-only
|
to specify that the file system should be forcibly unmounted or made read-only
|
||||||
(if MNT_UPDATE and MNT_RDONLY are also specified)
|
(if MNT_UPDATE and MNT_RDONLY are also specified)
|
||||||
even if files are still active.
|
even if files are still active.
|
||||||
Active special devices continue to work,
|
Active special devices continue to work,
|
||||||
but any further accesses to any other active files result in errors
|
but any further accesses to any other active files result in errors
|
||||||
even if the filesystem is later remounted.
|
even if the file system is later remounted.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Dv MNT_SUIDDIR
|
.Dv MNT_SUIDDIR
|
||||||
@ -203,7 +203,7 @@ points outside the process's allocated address space.
|
|||||||
.Pp
|
.Pp
|
||||||
The following errors can occur for a
|
The following errors can occur for a
|
||||||
.Em ufs
|
.Em ufs
|
||||||
filesystem mount:
|
file system mount:
|
||||||
.Bl -tag -width Er
|
.Bl -tag -width Er
|
||||||
.It Bq Er ENODEV
|
.It Bq Er ENODEV
|
||||||
A component of ufs_args
|
A component of ufs_args
|
||||||
@ -223,11 +223,11 @@ is already mounted.
|
|||||||
.It Bq Er EMFILE
|
.It Bq Er EMFILE
|
||||||
No space remains in the mount table.
|
No space remains in the mount table.
|
||||||
.It Bq Er EINVAL
|
.It Bq Er EINVAL
|
||||||
The super block for the filesystem had a bad magic
|
The super block for the file system had a bad magic
|
||||||
number or an out of range block size.
|
number or an out of range block size.
|
||||||
.It Bq Er ENOMEM
|
.It Bq Er ENOMEM
|
||||||
Not enough memory was available to read the cylinder
|
Not enough memory was available to read the cylinder
|
||||||
group information for the filesystem.
|
group information for the file system.
|
||||||
.It Bq Er EIO
|
.It Bq Er EIO
|
||||||
An I/O error occurred while reading the super block or
|
An I/O error occurred while reading the super block or
|
||||||
cylinder group information.
|
cylinder group information.
|
||||||
@ -238,7 +238,7 @@ points outside the process's allocated address space.
|
|||||||
.Pp
|
.Pp
|
||||||
The following errors can occur for a
|
The following errors can occur for a
|
||||||
.Em nfs
|
.Em nfs
|
||||||
filesystem mount:
|
file system mount:
|
||||||
.Bl -tag -width Er
|
.Bl -tag -width Er
|
||||||
.It Bq Er ETIMEDOUT
|
.It Bq Er ETIMEDOUT
|
||||||
.Em Nfs
|
.Em Nfs
|
||||||
@ -265,9 +265,9 @@ Too many symbolic links were encountered in translating the pathname.
|
|||||||
The requested directory is not in the mount table.
|
The requested directory is not in the mount table.
|
||||||
.It Bq Er EBUSY
|
.It Bq Er EBUSY
|
||||||
A process is holding a reference to a file located
|
A process is holding a reference to a file located
|
||||||
on the filesystem.
|
on the file system.
|
||||||
.It Bq Er EIO
|
.It Bq Er EIO
|
||||||
An I/O error occurred while writing cached filesystem information.
|
An I/O error occurred while writing cached file system information.
|
||||||
.It Bq Er EFAULT
|
.It Bq Er EFAULT
|
||||||
.Fa Dir
|
.Fa Dir
|
||||||
points outside the process's allocated address space.
|
points outside the process's allocated address space.
|
||||||
@ -275,7 +275,7 @@ points outside the process's allocated address space.
|
|||||||
.Pp
|
.Pp
|
||||||
A
|
A
|
||||||
.Em ufs
|
.Em ufs
|
||||||
mount can also fail if the maximum number of filesystems are currently
|
mount can also fail if the maximum number of file systems are currently
|
||||||
mounted.
|
mounted.
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr lsvfs 1 ,
|
.Xr lsvfs 1 ,
|
||||||
|
@ -48,7 +48,7 @@
|
|||||||
The
|
The
|
||||||
.Fn msync
|
.Fn msync
|
||||||
system call
|
system call
|
||||||
writes any modified pages back to the filesystem and updates
|
writes any modified pages back to the file system and updates
|
||||||
the file modification time.
|
the file modification time.
|
||||||
If
|
If
|
||||||
.Fa len
|
.Fa len
|
||||||
|
@ -151,7 +151,7 @@ for an exclusive lock.
|
|||||||
If creating a file with
|
If creating a file with
|
||||||
.Dv O_CREAT ,
|
.Dv O_CREAT ,
|
||||||
the request for the lock will never fail
|
the request for the lock will never fail
|
||||||
(provided that the underlying filesystem supports locking).
|
(provided that the underlying file system supports locking).
|
||||||
.Pp
|
.Pp
|
||||||
.Dv O_DIRECT
|
.Dv O_DIRECT
|
||||||
may be used to minimize or eliminate the cache effects of reading and writing.
|
may be used to minimize or eliminate the cache effects of reading and writing.
|
||||||
@ -243,7 +243,7 @@ operation was interrupted by a signal.
|
|||||||
.Dv O_SHLOCK
|
.Dv O_SHLOCK
|
||||||
or
|
or
|
||||||
.Dv O_EXLOCK
|
.Dv O_EXLOCK
|
||||||
is specified but the underlying filesystem does not support locking.
|
is specified but the underlying file system does not support locking.
|
||||||
.It Bq Er EWOULDBLOCK
|
.It Bq Er EWOULDBLOCK
|
||||||
.Dv O_NONBLOCK
|
.Dv O_NONBLOCK
|
||||||
and one of
|
and one of
|
||||||
|
@ -40,7 +40,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm quotactl
|
.Nm quotactl
|
||||||
.Nd manipulate filesystem quotas
|
.Nd manipulate file system quotas
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
@ -52,7 +52,7 @@
|
|||||||
The
|
The
|
||||||
.Fn quotactl
|
.Fn quotactl
|
||||||
call enables, disables and
|
call enables, disables and
|
||||||
manipulates filesystem quotas.
|
manipulates file system quotas.
|
||||||
A quota control command
|
A quota control command
|
||||||
given by
|
given by
|
||||||
.Fa cmd
|
.Fa cmd
|
||||||
@ -71,7 +71,7 @@ is discussed below with each command.
|
|||||||
.Pp
|
.Pp
|
||||||
Currently quotas are supported only for the
|
Currently quotas are supported only for the
|
||||||
.Dq ufs
|
.Dq ufs
|
||||||
filesystem.
|
file system.
|
||||||
For
|
For
|
||||||
.Dq ufs ,
|
.Dq ufs ,
|
||||||
a command is composed of a primary command (see below)
|
a command is composed of a primary command (see below)
|
||||||
@ -84,7 +84,7 @@ The
|
|||||||
specific commands are:
|
specific commands are:
|
||||||
.Bl -tag -width Q_QUOTAOFFxx
|
.Bl -tag -width Q_QUOTAOFFxx
|
||||||
.It Dv Q_QUOTAON
|
.It Dv Q_QUOTAON
|
||||||
Enable disk quotas for the filesystem specified by
|
Enable disk quotas for the file system specified by
|
||||||
.Fa path .
|
.Fa path .
|
||||||
The command type specifies the type of the quotas being enabled.
|
The command type specifies the type of the quotas being enabled.
|
||||||
The
|
The
|
||||||
@ -99,7 +99,7 @@ The
|
|||||||
argument is unused.
|
argument is unused.
|
||||||
Only the super-user may turn quotas on.
|
Only the super-user may turn quotas on.
|
||||||
.It Dv Q_QUOTAOFF
|
.It Dv Q_QUOTAOFF
|
||||||
Disable disk quotas for the filesystem specified by
|
Disable disk quotas for the file system specified by
|
||||||
.Fa path .
|
.Fa path .
|
||||||
The command type specifies the type of the quotas being disabled.
|
The command type specifies the type of the quotas being disabled.
|
||||||
The
|
The
|
||||||
@ -170,7 +170,7 @@ In
|
|||||||
.Dv Q_GETQUOTA
|
.Dv Q_GETQUOTA
|
||||||
and
|
and
|
||||||
.Dv Q_SETQUOTA ,
|
.Dv Q_SETQUOTA ,
|
||||||
quotas are not currently enabled for this filesystem.
|
quotas are not currently enabled for this file system.
|
||||||
.It Bq Er EACCES
|
.It Bq Er EACCES
|
||||||
In
|
In
|
||||||
.Dv Q_QUOTAON ,
|
.Dv Q_QUOTAON ,
|
||||||
@ -189,7 +189,7 @@ Too many symbolic links were encountered in translating a pathname.
|
|||||||
.It Bq Er EROFS
|
.It Bq Er EROFS
|
||||||
In
|
In
|
||||||
.Dv Q_QUOTAON ,
|
.Dv Q_QUOTAON ,
|
||||||
the quota file resides on a read-only filesystem.
|
the quota file resides on a read-only file system.
|
||||||
.It Bq Er EIO
|
.It Bq Er EIO
|
||||||
An
|
An
|
||||||
.Tn I/O
|
.Tn I/O
|
||||||
|
@ -51,7 +51,7 @@
|
|||||||
.Fn Statfs
|
.Fn Statfs
|
||||||
returns information about a mounted file system.
|
returns information about a mounted file system.
|
||||||
.Fa Path
|
.Fa Path
|
||||||
is the path name of any file within the mounted filesystem.
|
is the path name of any file within the mounted file system.
|
||||||
.Fa Buf
|
.Fa Buf
|
||||||
is a pointer to a
|
is a pointer to a
|
||||||
.Fn statfs
|
.Fn statfs
|
||||||
@ -75,8 +75,8 @@ long f_bavail; /* free blocks avail to non-superuser */
|
|||||||
long f_files; /* total file nodes in file system */
|
long f_files; /* total file nodes in file system */
|
||||||
long f_ffree; /* free file nodes in fs */
|
long f_ffree; /* free file nodes in fs */
|
||||||
fsid_t f_fsid; /* file system id */
|
fsid_t f_fsid; /* file system id */
|
||||||
uid_t f_owner; /* user that mounted the filesystem */
|
uid_t f_owner; /* user that mounted the file system */
|
||||||
int f_type; /* type of filesystem */
|
int f_type; /* type of file system */
|
||||||
int f_flags; /* copy of mount flags */
|
int f_flags; /* copy of mount flags */
|
||||||
long f_syncwrites; /* count of sync writes since mount */
|
long f_syncwrites; /* count of sync writes since mount */
|
||||||
long f_asyncwrites; /* count of async writes since mount */
|
long f_asyncwrites; /* count of async writes since mount */
|
||||||
@ -84,40 +84,40 @@ char f_fstypename[MFSNAMELEN];/* fs type name */
|
|||||||
char f_mntonname[MNAMELEN]; /* mount point */
|
char f_mntonname[MNAMELEN]; /* mount point */
|
||||||
long f_syncreads; /* count of sync reads since mount */
|
long f_syncreads; /* count of sync reads since mount */
|
||||||
long f_asyncreads; /* count of async reads since mount */
|
long f_asyncreads; /* count of async reads since mount */
|
||||||
char f_mntfromname[MNAMELEN]; /* mounted filesystem */
|
char f_mntfromname[MNAMELEN]; /* mounted file system */
|
||||||
};
|
};
|
||||||
.Ed
|
.Ed
|
||||||
The flags that may be returned include:
|
The flags that may be returned include:
|
||||||
.Bl -tag -width MNT_SYNCHRONOUS
|
.Bl -tag -width MNT_SYNCHRONOUS
|
||||||
.It Dv MNT_RDONLY
|
.It Dv MNT_RDONLY
|
||||||
The filesystem is mounted read-only;
|
The file system is mounted read-only;
|
||||||
Even the super-user may not write on it.
|
Even the super-user may not write on it.
|
||||||
.It Dv MNT_NOEXEC
|
.It Dv MNT_NOEXEC
|
||||||
Files may not be executed from the filesystem.
|
Files may not be executed from the file system.
|
||||||
.It Dv MNT_NOSUID
|
.It Dv MNT_NOSUID
|
||||||
Setuid and setgid bits on files are not honored when they are executed.
|
Setuid and setgid bits on files are not honored when they are executed.
|
||||||
.It Dv MNT_NODEV
|
.It Dv MNT_NODEV
|
||||||
Special files in the filesystem may not be opened.
|
Special files in the file system may not be opened.
|
||||||
.It Dv MNT_SYNCHRONOUS
|
.It Dv MNT_SYNCHRONOUS
|
||||||
All I/O to the filesystem is done synchronously.
|
All I/O to the file system is done synchronously.
|
||||||
.It Dv MNT_ASYNC
|
.It Dv MNT_ASYNC
|
||||||
No filesystem I/O is done synchronously.
|
No file system I/O is done synchronously.
|
||||||
.It Dv MNT_LOCAL
|
.It Dv MNT_LOCAL
|
||||||
The filesystem resides locally.
|
The file system resides locally.
|
||||||
.It Dv MNT_QUOTA
|
.It Dv MNT_QUOTA
|
||||||
The filesystem has quotas enabled on it.
|
The file system has quotas enabled on it.
|
||||||
.It Dv MNT_ROOTFS
|
.It Dv MNT_ROOTFS
|
||||||
Identifies the root filesystem.
|
Identifies the root file system.
|
||||||
.It Dv MNT_EXRDONLY
|
.It Dv MNT_EXRDONLY
|
||||||
The filesystem is exported read-only.
|
The file system is exported read-only.
|
||||||
.It Dv MNT_EXPORTED
|
.It Dv MNT_EXPORTED
|
||||||
The filesystem is exported for both reading and writing.
|
The file system is exported for both reading and writing.
|
||||||
.It Dv MNT_DEFEXPORTED
|
.It Dv MNT_DEFEXPORTED
|
||||||
The filesystem is exported for both reading and writing to any Internet host.
|
The file system is exported for both reading and writing to any Internet host.
|
||||||
.It Dv MNT_EXPORTANON
|
.It Dv MNT_EXPORTANON
|
||||||
The filesystem maps all remote accesses to the anonymous user.
|
The file system maps all remote accesses to the anonymous user.
|
||||||
.It Dv MNT_EXKERB
|
.It Dv MNT_EXKERB
|
||||||
The filesystem is exported with Kerberos uid mapping.
|
The file system is exported with Kerberos uid mapping.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
Fields that are undefined for a particular file system are set to -1.
|
Fields that are undefined for a particular file system are set to -1.
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm sync
|
.Nm sync
|
||||||
.Nd "schedule filesystem updates"
|
.Nd "schedule file system updates"
|
||||||
.Sh LIBRARY
|
.Sh LIBRARY
|
||||||
.Lb libc
|
.Lb libc
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
|
@ -51,15 +51,15 @@ The
|
|||||||
function attempts to recover the deleted file named by
|
function attempts to recover the deleted file named by
|
||||||
.Fa path .
|
.Fa path .
|
||||||
Currently, this works only when the named object
|
Currently, this works only when the named object
|
||||||
is a whiteout in a union filesystem.
|
is a whiteout in a union file system.
|
||||||
The system call removes the whiteout causing
|
The system call removes the whiteout causing
|
||||||
any objects in a lower layer of the
|
any objects in a lower layer of the
|
||||||
union stack to become visible once more.
|
union stack to become visible once more.
|
||||||
.Pp
|
.Pp
|
||||||
Eventually, the
|
Eventually, the
|
||||||
.Fn undelete
|
.Fn undelete
|
||||||
functionality may be expanded to other filesystems able to recover
|
functionality may be expanded to other file systems able to recover
|
||||||
deleted files such as the log-structured filesystem.
|
deleted files such as the log-structured file system.
|
||||||
.Sh RETURN VALUES
|
.Sh RETURN VALUES
|
||||||
.Rv -std undelete
|
.Rv -std undelete
|
||||||
.Sh ERRORS
|
.Sh ERRORS
|
||||||
|
@ -114,5 +114,5 @@ function call appeared in
|
|||||||
The
|
The
|
||||||
.Fn unlink
|
.Fn unlink
|
||||||
system call traditionally allows the super-user to unlink directories which
|
system call traditionally allows the super-user to unlink directories which
|
||||||
can damage the filesystem integrity. This implementation no longer permits
|
can damage the file system integrity. This implementation no longer permits
|
||||||
it.
|
it.
|
||||||
|
@ -75,7 +75,7 @@ is
|
|||||||
it is assumed to point to an array of two timeval structures.
|
it is assumed to point to an array of two timeval structures.
|
||||||
The access time is set to the value of the first element, and the
|
The access time is set to the value of the first element, and the
|
||||||
modification time is set to the value of the second element.
|
modification time is set to the value of the second element.
|
||||||
For filesystems that support file birth (creation) times (such as
|
For file systems that support file birth (creation) times (such as
|
||||||
.Dv UFS2 ) ,
|
.Dv UFS2 ) ,
|
||||||
the birth time will be set to the value of the second element
|
the birth time will be set to the value of the second element
|
||||||
if the second element is older than the currently set birth time.
|
if the second element is older than the currently set birth time.
|
||||||
|
@ -357,7 +357,7 @@ Similar to the behaviour as specified in
|
|||||||
except that file creation is not supported, so the mode parameter is not
|
except that file creation is not supported, so the mode parameter is not
|
||||||
required. The
|
required. The
|
||||||
.Fa flags
|
.Fa flags
|
||||||
argument may be one of O_RDONLY, O_WRONLY and O_RDWR (although no filesystems
|
argument may be one of O_RDONLY, O_WRONLY and O_RDWR (although no file systems
|
||||||
currently support writing).
|
currently support writing).
|
||||||
.It Xo
|
.It Xo
|
||||||
.Ft int
|
.Ft int
|
||||||
@ -378,7 +378,7 @@ Close all open files.
|
|||||||
.Fn write "int fd" "void *buf" "size_t len"
|
.Fn write "int fd" "void *buf" "size_t len"
|
||||||
.Xc
|
.Xc
|
||||||
.Pp
|
.Pp
|
||||||
(No filesystems currently support writing.)
|
(No file systems currently support writing.)
|
||||||
.It Xo
|
.It Xo
|
||||||
.Ft off_t
|
.Ft off_t
|
||||||
.Fn lseek "int fd" "off_t offset" "int whence"
|
.Fn lseek "int fd" "off_t offset" "int whence"
|
||||||
@ -403,9 +403,9 @@ functions only fill out the following fields in the
|
|||||||
.Fa sb
|
.Fa sb
|
||||||
structure: st_mode,st_nlink,st_uid,st_gid,st_size. The
|
structure: st_mode,st_nlink,st_uid,st_gid,st_size. The
|
||||||
.Nm tftp
|
.Nm tftp
|
||||||
filesystem cannot provide meaningful values for this call, and the
|
file system cannot provide meaningful values for this call, and the
|
||||||
.Nm cd9660
|
.Nm cd9660
|
||||||
filesystem always reports files having uid/gid of zero.
|
file system always reports files having uid/gid of zero.
|
||||||
.El
|
.El
|
||||||
.Sh PAGER
|
.Sh PAGER
|
||||||
.Nm
|
.Nm
|
||||||
@ -466,7 +466,7 @@ The following resources are consumed by
|
|||||||
The stack must be established before
|
The stack must be established before
|
||||||
.Nm
|
.Nm
|
||||||
functions can be invoked. Stack requirements vary depending on the functions
|
functions can be invoked. Stack requirements vary depending on the functions
|
||||||
and filesystems used by the consumer and the support layer functions detailed
|
and file systems used by the consumer and the support layer functions detailed
|
||||||
below.
|
below.
|
||||||
.Pp
|
.Pp
|
||||||
The heap must be established before calling
|
The heap must be established before calling
|
||||||
@ -567,36 +567,36 @@ Signal a fatal and unrecoverable error condition. The
|
|||||||
arguments are as for
|
arguments are as for
|
||||||
.Fn printf .
|
.Fn printf .
|
||||||
.El
|
.El
|
||||||
.Sh INTERNAL FILESYSTEMS
|
.Sh INTERNAL FILE SYSTEMS
|
||||||
Internal filesystems are enabled by the consumer exporting the array
|
Internal file systems are enabled by the consumer exporting the array
|
||||||
.Vt struct fs_ops *file_system[] ,
|
.Vt struct fs_ops *file_system[] ,
|
||||||
which should be initialised with pointers
|
which should be initialised with pointers
|
||||||
to
|
to
|
||||||
.Vt struct fs_ops
|
.Vt struct fs_ops
|
||||||
structures. The following filesystem handlers are supplied by
|
structures. The following file system handlers are supplied by
|
||||||
.Nm ,
|
.Nm ,
|
||||||
the consumer may supply other filesystems of their own:
|
the consumer may supply other file systems of their own:
|
||||||
.Bl -hang -width ".Va cd9660_fsops"
|
.Bl -hang -width ".Va cd9660_fsops"
|
||||||
.It Va ufs_fsops
|
.It Va ufs_fsops
|
||||||
The
|
The
|
||||||
.Bx
|
.Bx
|
||||||
UFS.
|
UFS.
|
||||||
.It Va ext2fs_fsops
|
.It Va ext2fs_fsops
|
||||||
Linux ext2fs filesystem.
|
Linux ext2fs file system.
|
||||||
.It Va tftp_fsops
|
.It Va tftp_fsops
|
||||||
File access via TFTP.
|
File access via TFTP.
|
||||||
.It Va nfs_fsops
|
.It Va nfs_fsops
|
||||||
File access via NFS.
|
File access via NFS.
|
||||||
.It Va cd9660_fsops
|
.It Va cd9660_fsops
|
||||||
ISO 9660 (CD-ROM) filesystem.
|
ISO 9660 (CD-ROM) file system.
|
||||||
.It Va zipfs_fsops
|
.It Va zipfs_fsops
|
||||||
Stacked filesystem supporting gzipped files.
|
Stacked file system supporting gzipped files.
|
||||||
When trying the zipfs filesystem,
|
When trying the zipfs file system,
|
||||||
.Nm
|
.Nm
|
||||||
appends
|
appends
|
||||||
.Li .gz
|
.Li .gz
|
||||||
to the end of the filename, and then tries to locate the file using the other
|
to the end of the filename, and then tries to locate the file using the other
|
||||||
filesystems. Placement of this filesystem in the
|
file systems. Placement of this file system in the
|
||||||
.Va file_system[]
|
.Va file_system[]
|
||||||
array determines whether gzipped files will be opened in preference to non-gzipped
|
array determines whether gzipped files will be opened in preference to non-gzipped
|
||||||
files. It is only possible to seek a gzipped file forwards, and
|
files. It is only possible to seek a gzipped file forwards, and
|
||||||
|
@ -42,11 +42,11 @@ The
|
|||||||
.Nm
|
.Nm
|
||||||
utility is a
|
utility is a
|
||||||
.Xr rpc 3
|
.Xr rpc 3
|
||||||
server which returns quotas for a user of a local filesystem
|
server which returns quotas for a user of a local file system
|
||||||
which is NFS-mounted onto a remote machine.
|
which is NFS-mounted onto a remote machine.
|
||||||
The
|
The
|
||||||
.Xr quota 1
|
.Xr quota 1
|
||||||
utility uses the results to display user quotas for remote filesystems.
|
utility uses the results to display user quotas for remote file systems.
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
utility is normally invoked by
|
utility is normally invoked by
|
||||||
|
@ -87,7 +87,7 @@ routine is called. Thus,
|
|||||||
can complete the link-editing process before the dynamic program calls upon
|
can complete the link-editing process before the dynamic program calls upon
|
||||||
services of any dynamic library.
|
services of any dynamic library.
|
||||||
.Pp
|
.Pp
|
||||||
To quickly locate the required shared objects in the filesystem,
|
To quickly locate the required shared objects in the file system,
|
||||||
.Nm
|
.Nm
|
||||||
may use a
|
may use a
|
||||||
.Dq hints
|
.Dq hints
|
||||||
@ -204,7 +204,7 @@ are recognized and have their usual meaning.
|
|||||||
.\" .It Ev LD_NOSTD_PATH
|
.\" .It Ev LD_NOSTD_PATH
|
||||||
.\" When set, do not include a set of built-in standard directory paths for
|
.\" When set, do not include a set of built-in standard directory paths for
|
||||||
.\" searching. This might be useful when running on a system with a completely
|
.\" searching. This might be useful when running on a system with a completely
|
||||||
.\" non-standard filesystem layout.
|
.\" non-standard file system layout.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
.Sh FILES
|
.Sh FILES
|
||||||
|
@ -67,7 +67,7 @@ After the dynamic linker has finished loading,
|
|||||||
relocating, and initializing the program and its required shared
|
relocating, and initializing the program and its required shared
|
||||||
objects, it transfers control to the entry point of the program.
|
objects, it transfers control to the entry point of the program.
|
||||||
.Pp
|
.Pp
|
||||||
To locate the required shared objects in the filesystem,
|
To locate the required shared objects in the file system,
|
||||||
.Nm
|
.Nm
|
||||||
may use a
|
may use a
|
||||||
.Dq hints
|
.Dq hints
|
||||||
|
@ -243,7 +243,7 @@ The
|
|||||||
flag allows you to specify an alternate path should you wish to
|
flag allows you to specify an alternate path should you wish to
|
||||||
store your
|
store your
|
||||||
.Tn NIS
|
.Tn NIS
|
||||||
maps in a different part of the filesystem. The
|
maps in a different part of the file system. The
|
||||||
.Tn NIS
|
.Tn NIS
|
||||||
server,
|
server,
|
||||||
.Xr ypserv 8 ,
|
.Xr ypserv 8 ,
|
||||||
|
@ -287,7 +287,7 @@ static char *dktypenames[] = {
|
|||||||
#endif
|
#endif
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Filesystem type and version.
|
* File system type and version.
|
||||||
* Used to interpret other file system-specific
|
* Used to interpret other file system-specific
|
||||||
* per-partition information.
|
* per-partition information.
|
||||||
*/
|
*/
|
||||||
|
@ -287,7 +287,7 @@ static char *dktypenames[] = {
|
|||||||
#endif
|
#endif
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Filesystem type and version.
|
* File system type and version.
|
||||||
* Used to interpret other file system-specific
|
* Used to interpret other file system-specific
|
||||||
* per-partition information.
|
* per-partition information.
|
||||||
*/
|
*/
|
||||||
|
@ -197,10 +197,10 @@ was compiled.)
|
|||||||
.It Fl L
|
.It Fl L
|
||||||
This option is to notify
|
This option is to notify
|
||||||
.Nm
|
.Nm
|
||||||
that it is dumping a live filesystem.
|
that it is dumping a live file system.
|
||||||
To obtain a consistent dump image,
|
To obtain a consistent dump image,
|
||||||
.Nm
|
.Nm
|
||||||
takes a snapshot of the filesystem and
|
takes a snapshot of the file system and
|
||||||
then does a dump of the snapshot.
|
then does a dump of the snapshot.
|
||||||
The snapshot is removed when the dump is complete.
|
The snapshot is removed when the dump is complete.
|
||||||
.It Fl n
|
.It Fl n
|
||||||
|
@ -88,7 +88,7 @@ that are mounted
|
|||||||
or
|
or
|
||||||
.Dq ro
|
.Dq ro
|
||||||
and that have non-zero pass number are checked.
|
and that have non-zero pass number are checked.
|
||||||
Filesystems with pass number 1 (normally just the root file system)
|
File systems with pass number 1 (normally just the root file system)
|
||||||
are always checked one at a time.
|
are always checked one at a time.
|
||||||
.Pp
|
.Pp
|
||||||
If not in preen mode, the remaining entries are checked in order of
|
If not in preen mode, the remaining entries are checked in order of
|
||||||
|
@ -53,7 +53,7 @@ The specified disk partitions and/or file systems are checked.
|
|||||||
In "preen" mode the clean flag of each file system's superblock is examined
|
In "preen" mode the clean flag of each file system's superblock is examined
|
||||||
and only those file systems that
|
and only those file systems that
|
||||||
are not marked clean are checked.
|
are not marked clean are checked.
|
||||||
Filesystems are marked clean when they are unmounted,
|
File systems are marked clean when they are unmounted,
|
||||||
when they have been mounted read-only, or when
|
when they have been mounted read-only, or when
|
||||||
.Nm
|
.Nm
|
||||||
runs on them successfully.
|
runs on them successfully.
|
||||||
|
@ -58,7 +58,7 @@ Before starting
|
|||||||
.Nm
|
.Nm
|
||||||
the disk must be labeled to a bigger size using
|
the disk must be labeled to a bigger size using
|
||||||
.Xr disklabel 8 .
|
.Xr disklabel 8 .
|
||||||
If you wish to grow a filesystem beyond the boundary of
|
If you wish to grow a file system beyond the boundary of
|
||||||
the slice it resides in, you must re-size the slice using
|
the slice it resides in, you must re-size the slice using
|
||||||
.Xr fdisk 8
|
.Xr fdisk 8
|
||||||
before running
|
before running
|
||||||
|
@ -230,7 +230,7 @@ is that vnode arguments must be manually mapped.
|
|||||||
UCLA Technical Report CSD-910056,
|
UCLA Technical Report CSD-910056,
|
||||||
.Em "Stackable Layers: an Architecture for File System Development" .
|
.Em "Stackable Layers: an Architecture for File System Development" .
|
||||||
.Sh BUGS
|
.Sh BUGS
|
||||||
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
||||||
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
||||||
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -125,7 +125,7 @@ sophisticated.
|
|||||||
.Xr mount 8 ,
|
.Xr mount 8 ,
|
||||||
.Xr mount_nullfs 8
|
.Xr mount_nullfs 8
|
||||||
.Sh BUGS
|
.Sh BUGS
|
||||||
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
||||||
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
||||||
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -182,7 +182,7 @@ accessible via
|
|||||||
.Xr mount 8 ,
|
.Xr mount 8 ,
|
||||||
.Xr mount_nullfs 8
|
.Xr mount_nullfs 8
|
||||||
.Sh BUGS
|
.Sh BUGS
|
||||||
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
|
||||||
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
|
||||||
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -146,7 +146,7 @@ as a hot spare for the device
|
|||||||
Make the RAID set auto-configurable. The RAID set will be
|
Make the RAID set auto-configurable. The RAID set will be
|
||||||
automatically configured at boot
|
automatically configured at boot
|
||||||
.Ar before
|
.Ar before
|
||||||
the root filesystem is
|
the root file system is
|
||||||
mounted. Note that all components of the set must be of type RAID in the
|
mounted. Note that all components of the set must be of type RAID in the
|
||||||
disklabel.
|
disklabel.
|
||||||
.It Fl A Ic no Ar dev
|
.It Fl A Ic no Ar dev
|
||||||
@ -195,7 +195,7 @@ the selected device. This
|
|||||||
be done for
|
be done for
|
||||||
.Ar all
|
.Ar all
|
||||||
RAID sets before the RAID device is labeled and before
|
RAID sets before the RAID device is labeled and before
|
||||||
filesystems are created on the RAID device.
|
file systems are created on the RAID device.
|
||||||
.It Fl I Ar serial_number Ar dev
|
.It Fl I Ar serial_number Ar dev
|
||||||
Initialize the component labels on each component of the device.
|
Initialize the component labels on each component of the device.
|
||||||
.Ar serial_number
|
.Ar serial_number
|
||||||
@ -394,7 +394,7 @@ for a more complete configuration file example.
|
|||||||
.Sh EXAMPLES
|
.Sh EXAMPLES
|
||||||
|
|
||||||
It is highly recommended that before using the RAID driver for real
|
It is highly recommended that before using the RAID driver for real
|
||||||
filesystems that the system administrator(s) become quite familiar
|
file systems that the system administrator(s) become quite familiar
|
||||||
with the use of
|
with the use of
|
||||||
.Nm ,
|
.Nm ,
|
||||||
and that they understand how the component reconstruction process
|
and that they understand how the component reconstruction process
|
||||||
@ -622,7 +622,7 @@ it is then safe to perform
|
|||||||
.Xr newfs 8 ,
|
.Xr newfs 8 ,
|
||||||
or
|
or
|
||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
on the device or its filesystems, and then to mount the filesystems
|
on the device or its file systems, and then to mount the file systems
|
||||||
for use.
|
for use.
|
||||||
.Pp
|
.Pp
|
||||||
Under certain circumstances (e.g. the additional component has not
|
Under certain circumstances (e.g. the additional component has not
|
||||||
@ -680,7 +680,7 @@ raidctl -P raid0
|
|||||||
is used. Note that re-writing the parity can be done while
|
is used. Note that re-writing the parity can be done while
|
||||||
other operations on the RAID set are taking place (e.g. while doing a
|
other operations on the RAID set are taking place (e.g. while doing a
|
||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
on a filesystem on the RAID set). However: for maximum effectiveness
|
on a file system on the RAID set). However: for maximum effectiveness
|
||||||
of the RAID set, the parity should be known to be correct before any
|
of the RAID set, the parity should be known to be correct before any
|
||||||
data on the set is modified.
|
data on the set is modified.
|
||||||
.Pp
|
.Pp
|
||||||
@ -734,7 +734,7 @@ are the component lines which read
|
|||||||
and the
|
and the
|
||||||
.Sq Parity status
|
.Sq Parity status
|
||||||
line which indicates that the parity is up-to-date. Note that if
|
line which indicates that the parity is up-to-date. Note that if
|
||||||
there are filesystems open on the RAID set, the individual components
|
there are file systems open on the RAID set, the individual components
|
||||||
will not be
|
will not be
|
||||||
.Sq clean
|
.Sq clean
|
||||||
but the set as a whole can still be clean.
|
but the set as a whole can still be clean.
|
||||||
@ -995,19 +995,19 @@ raidctl -A no raid0
|
|||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
RAID sets which are auto-configurable will be configured before the
|
RAID sets which are auto-configurable will be configured before the
|
||||||
root filesystem is mounted. These RAID sets are thus available for
|
root file system is mounted. These RAID sets are thus available for
|
||||||
use as a root filesystem, or for any other filesystem. A primary
|
use as a root file system, or for any other file system. A primary
|
||||||
advantage of using the auto-configuration is that RAID components
|
advantage of using the auto-configuration is that RAID components
|
||||||
become more independent of the disks they reside on. For example,
|
become more independent of the disks they reside on. For example,
|
||||||
SCSI ID's can change, but auto-configured sets will always be
|
SCSI ID's can change, but auto-configured sets will always be
|
||||||
configured correctly, even if the SCSI ID's of the component disks
|
configured correctly, even if the SCSI ID's of the component disks
|
||||||
have become scrambled.
|
have become scrambled.
|
||||||
.Pp
|
.Pp
|
||||||
Having a system's root filesystem (/) on a RAID set is also allowed,
|
Having a system's root file system (/) on a RAID set is also allowed,
|
||||||
with the
|
with the
|
||||||
.Sq a
|
.Sq a
|
||||||
partition of such a RAID set being used for /.
|
partition of such a RAID set being used for /.
|
||||||
To use raid0a as the root filesystem, simply use:
|
To use raid0a as the root file system, simply use:
|
||||||
.Bd -unfilled -offset indent
|
.Bd -unfilled -offset indent
|
||||||
raidctl -A root raid0
|
raidctl -A root raid0
|
||||||
.Ed
|
.Ed
|
||||||
@ -1019,9 +1019,9 @@ arguments.
|
|||||||
Note that kernels can only be directly read from RAID 1 components on
|
Note that kernels can only be directly read from RAID 1 components on
|
||||||
alpha and pmax architectures. On those architectures, the
|
alpha and pmax architectures. On those architectures, the
|
||||||
.Dv FS_RAID
|
.Dv FS_RAID
|
||||||
filesystem is recognized by the bootblocks, and will properly load the
|
file system is recognized by the bootblocks, and will properly load the
|
||||||
kernel directly from a RAID 1 component. For other architectures, or
|
kernel directly from a RAID 1 component. For other architectures, or
|
||||||
to support the root filesystem on other RAID sets, some other
|
to support the root file system on other RAID sets, some other
|
||||||
mechanism must be used to get a kernel booting. For example, a small
|
mechanism must be used to get a kernel booting. For example, a small
|
||||||
partition containing only the secondary boot-blocks and an alternate
|
partition containing only the secondary boot-blocks and an alternate
|
||||||
kernel (or two) could be used. Once a kernel is booting however, and
|
kernel (or two) could be used. Once a kernel is booting however, and
|
||||||
@ -1039,7 +1039,7 @@ NetBSD installation.
|
|||||||
.It
|
.It
|
||||||
wd1a - also contains a complete, bootable, basic NetBSD installation.
|
wd1a - also contains a complete, bootable, basic NetBSD installation.
|
||||||
.It
|
.It
|
||||||
wd0e and wd1e - a RAID 1 set, raid0, used for the root filesystem.
|
wd0e and wd1e - a RAID 1 set, raid0, used for the root file system.
|
||||||
.It
|
.It
|
||||||
wd0f and wd1f - a RAID 1 set, raid1, which will be used only for
|
wd0f and wd1f - a RAID 1 set, raid1, which will be used only for
|
||||||
swap space.
|
swap space.
|
||||||
@ -1051,7 +1051,7 @@ wd0h and wd0h - a RAID 1 set, raid3, if desired.
|
|||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
RAID sets raid0, raid1, and raid2 are all marked as
|
RAID sets raid0, raid1, and raid2 are all marked as
|
||||||
auto-configurable. raid0 is marked as being a root filesystem.
|
auto-configurable. raid0 is marked as being a root file system.
|
||||||
When new kernels are installed, the kernel is not only copied to /,
|
When new kernels are installed, the kernel is not only copied to /,
|
||||||
but also to wd0a and wd1a. The kernel on wd0a is required, since that
|
but also to wd0a and wd1a. The kernel on wd0a is required, since that
|
||||||
is the kernel the system boots from. The kernel on wd1a is also
|
is the kernel the system boots from. The kernel on wd1a is also
|
||||||
@ -1059,9 +1059,9 @@ required, since that will be the kernel used should wd0 fail. The
|
|||||||
important point here is to have redundant copies of the kernel
|
important point here is to have redundant copies of the kernel
|
||||||
available, in the event that one of the drives fail.
|
available, in the event that one of the drives fail.
|
||||||
.Pp
|
.Pp
|
||||||
There is no requirement that the root filesystem be on the same disk
|
There is no requirement that the root file system be on the same disk
|
||||||
as the kernel. For example, obtaining the kernel from wd0a, and using
|
as the kernel. For example, obtaining the kernel from wd0a, and using
|
||||||
da0s1e and da1s1e for raid0, and the root filesystem, is fine. It
|
da0s1e and da1s1e for raid0, and the root file system, is fine. It
|
||||||
.Ar is
|
.Ar is
|
||||||
critical, however, that there be multiple kernels available, in the
|
critical, however, that there be multiple kernels available, in the
|
||||||
event of media failure.
|
event of media failure.
|
||||||
@ -1110,7 +1110,7 @@ Distribution of components among controllers
|
|||||||
.It
|
.It
|
||||||
IO bandwidth
|
IO bandwidth
|
||||||
.It
|
.It
|
||||||
Filesystem access patterns
|
File system access patterns
|
||||||
.It
|
.It
|
||||||
CPU speed
|
CPU speed
|
||||||
.El
|
.El
|
||||||
@ -1155,7 +1155,7 @@ problem in the real world, it may be useful to ensure that stripe
|
|||||||
sizes are small enough that a
|
sizes are small enough that a
|
||||||
.Sq large IO
|
.Sq large IO
|
||||||
from the system will use exactly one large stripe write. As is seen
|
from the system will use exactly one large stripe write. As is seen
|
||||||
later, there are some filesystem dependencies which may come into play
|
later, there are some file system dependencies which may come into play
|
||||||
here as well.
|
here as well.
|
||||||
.Pp
|
.Pp
|
||||||
Since the size of a
|
Since the size of a
|
||||||
@ -1167,13 +1167,13 @@ data per stripe is 64 blocks (32K) or 128 blocks (64K). Again,
|
|||||||
empirical measurement will provide the best indicators of which
|
empirical measurement will provide the best indicators of which
|
||||||
values will yeild better performance.
|
values will yeild better performance.
|
||||||
.Pp
|
.Pp
|
||||||
The parameters used for the filesystem are also critical to good
|
The parameters used for the file system are also critical to good
|
||||||
performance. For
|
performance. For
|
||||||
.Xr newfs 8 ,
|
.Xr newfs 8 ,
|
||||||
for example, increasing the block size to 32K or 64K may improve
|
for example, increasing the block size to 32K or 64K may improve
|
||||||
performance dramatically. As well, changing the cylinders-per-group
|
performance dramatically. As well, changing the cylinders-per-group
|
||||||
parameter from 16 to 32 or higher is often not only necessary for
|
parameter from 16 to 32 or higher is often not only necessary for
|
||||||
larger filesystems, but may also have positive performance
|
larger file systems, but may also have positive performance
|
||||||
implications.
|
implications.
|
||||||
.Pp
|
.Pp
|
||||||
.Ss Summary
|
.Ss Summary
|
||||||
@ -1225,13 +1225,13 @@ disklabel -R -r raid0 /tmp/label
|
|||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
.It
|
.It
|
||||||
Create the filesystem:
|
Create the file system:
|
||||||
.Bd -unfilled -offset indent
|
.Bd -unfilled -offset indent
|
||||||
newfs /dev/rraid0e
|
newfs /dev/rraid0e
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
.It
|
.It
|
||||||
Mount the filesystem:
|
Mount the file system:
|
||||||
.Bd -unfilled -offset indent
|
.Bd -unfilled -offset indent
|
||||||
mount /dev/raid0e /mnt
|
mount /dev/raid0e /mnt
|
||||||
.Ed
|
.Ed
|
||||||
@ -1251,7 +1251,7 @@ the /etc/rc scripts.
|
|||||||
Certain RAID levels (1, 4, 5, 6, and others) can protect against some
|
Certain RAID levels (1, 4, 5, 6, and others) can protect against some
|
||||||
data loss due to component failure. However the loss of two
|
data loss due to component failure. However the loss of two
|
||||||
components of a RAID 4 or 5 system, or the loss of a single component
|
components of a RAID 4 or 5 system, or the loss of a single component
|
||||||
of a RAID 0 system will result in the entire filesystem being lost.
|
of a RAID 0 system will result in the entire file system being lost.
|
||||||
RAID is
|
RAID is
|
||||||
.Ar NOT
|
.Ar NOT
|
||||||
a substitute for good backup practices.
|
a substitute for good backup practices.
|
||||||
|
@ -120,6 +120,6 @@ code is implemented in the
|
|||||||
It is not the most throughly tested code.
|
It is not the most throughly tested code.
|
||||||
It is also my first attempt to write in Forth.
|
It is also my first attempt to write in Forth.
|
||||||
.Pp
|
.Pp
|
||||||
Finally, it does some evil things like writing to the filesystem before it
|
Finally, it does some evil things like writing to the file system before it
|
||||||
has been checked.
|
has been checked.
|
||||||
If it scrambles your filesystem, do not blame me.
|
If it scrambles your file system, do not blame me.
|
||||||
|
@ -104,7 +104,7 @@ The remote system returned something that was
|
|||||||
during a protocol exchange.
|
during a protocol exchange.
|
||||||
.It Sy EX_NOPERM Pq 77
|
.It Sy EX_NOPERM Pq 77
|
||||||
You did not have sufficient permission to perform the operation. This
|
You did not have sufficient permission to perform the operation. This
|
||||||
is not intended for filesystem problems, which should use
|
is not intended for file system problems, which should use
|
||||||
.Sy EX_NOINPUT
|
.Sy EX_NOINPUT
|
||||||
or
|
or
|
||||||
.Sy EX_CANTCREAT ,
|
.Sy EX_CANTCREAT ,
|
||||||
|
@ -175,7 +175,7 @@ Note that a one-disk
|
|||||||
.Nm
|
.Nm
|
||||||
is not the same as the original partition.
|
is not the same as the original partition.
|
||||||
In particular, this means
|
In particular, this means
|
||||||
if you have a filesystem on a two-disk mirrored
|
if you have a file system on a two-disk mirrored
|
||||||
.Nm
|
.Nm
|
||||||
and one of the disks fail, you cannot mount and use the remaining
|
and one of the disks fail, you cannot mount and use the remaining
|
||||||
partition as itself; you have to configure it as a one-disk
|
partition as itself; you have to configure it as a one-disk
|
||||||
@ -188,7 +188,7 @@ then restoring the partition.
|
|||||||
If just one (or more) of the disks in a
|
If just one (or more) of the disks in a
|
||||||
.Nm
|
.Nm
|
||||||
fails, the entire
|
fails, the entire
|
||||||
filesystem will be lost unless you are mirroring the disks.
|
file system will be lost unless you are mirroring the disks.
|
||||||
.Pp
|
.Pp
|
||||||
If one of the disks in a mirror is lost, you should still
|
If one of the disks in a mirror is lost, you should still
|
||||||
be able to back up your data.
|
be able to back up your data.
|
||||||
|
@ -67,7 +67,7 @@ partitioning scheme,
|
|||||||
.Xr disklabel 5 ,
|
.Xr disklabel 5 ,
|
||||||
which is used to subdivide the
|
which is used to subdivide the
|
||||||
.Fx
|
.Fx
|
||||||
slices into areas for individual filesystems and swap spaces.
|
slices into areas for individual file systems and swap spaces.
|
||||||
For more information, see
|
For more information, see
|
||||||
.Xr fdisk 8
|
.Xr fdisk 8
|
||||||
and
|
and
|
||||||
@ -105,7 +105,7 @@ and allows the device to reorganize writes to increase efficiency and
|
|||||||
performance. This performance gain comes at a price. Should the device
|
performance. This performance gain comes at a price. Should the device
|
||||||
lose power while its cache contains uncommitted write operations, these
|
lose power while its cache contains uncommitted write operations, these
|
||||||
writes will be lost. The effect of a loss of write transactions on
|
writes will be lost. The effect of a loss of write transactions on
|
||||||
a filesystem is non-deterministic and can cause corruption. Most
|
a file system is non-deterministic and can cause corruption. Most
|
||||||
devices age write transactions to limit vulnerability to a few transactions
|
devices age write transactions to limit vulnerability to a few transactions
|
||||||
recently reported as complete, but it is none-the-less recommended that
|
recently reported as complete, but it is none-the-less recommended that
|
||||||
systems with write cache enabled devices reside on an Uninterruptible
|
systems with write cache enabled devices reside on an Uninterruptible
|
||||||
|
@ -225,7 +225,7 @@ some kind of structure or identifying byte sequences.
|
|||||||
.Pp
|
.Pp
|
||||||
Certain file formats like ELF contain multiple distinct sections, and it
|
Certain file formats like ELF contain multiple distinct sections, and it
|
||||||
would be possible to locate things just right in such a way that a device
|
would be possible to locate things just right in such a way that a device
|
||||||
contains a partition with a filesystem with a large executable,
|
contains a partition with a file system with a large executable,
|
||||||
.Pq Dq "a backup copy of my kernel"
|
.Pq Dq "a backup copy of my kernel"
|
||||||
where a non-loaded ELF section is laid out
|
where a non-loaded ELF section is laid out
|
||||||
consecutively on the device and thereby could be used to contain a
|
consecutively on the device and thereby could be used to contain a
|
||||||
|
@ -236,7 +236,7 @@ to be instantiated between a consumer and a provider attached to
|
|||||||
each other and to remove it again.
|
each other and to remove it again.
|
||||||
.Pp
|
.Pp
|
||||||
To understand the utility of this, imagine a provider with
|
To understand the utility of this, imagine a provider with
|
||||||
being mounted as a filesystem.
|
being mounted as a file system.
|
||||||
Between the DEVFS geoms consumer and its provider we insert
|
Between the DEVFS geoms consumer and its provider we insert
|
||||||
a mirror module which configures itself with one mirror
|
a mirror module which configures itself with one mirror
|
||||||
copy and consequently is transparent to the I/O requests
|
copy and consequently is transparent to the I/O requests
|
||||||
@ -244,7 +244,7 @@ on the path.
|
|||||||
We can now configure yet a mirror copy on the mirror geom,
|
We can now configure yet a mirror copy on the mirror geom,
|
||||||
request a synchronization, and finally drop the first mirror
|
request a synchronization, and finally drop the first mirror
|
||||||
copy.
|
copy.
|
||||||
We have now in essence moved a mounted filesystem from one
|
We have now in essence moved a mounted file system from one
|
||||||
disk to another while it was being used.
|
disk to another while it was being used.
|
||||||
At this point the mirror geom can be deleted from the path
|
At this point the mirror geom can be deleted from the path
|
||||||
again, it has served its purpose.
|
again, it has served its purpose.
|
||||||
|
@ -71,7 +71,7 @@ sometimes also called
|
|||||||
.Em special files .
|
.Em special files .
|
||||||
They are usually located under the directory
|
They are usually located under the directory
|
||||||
.Pa /dev
|
.Pa /dev
|
||||||
in the filesystem hierarchy
|
in the file system hierarchy
|
||||||
(see also
|
(see also
|
||||||
.Xr hier 7 ) .
|
.Xr hier 7 ) .
|
||||||
.Pp
|
.Pp
|
||||||
@ -106,7 +106,7 @@ and
|
|||||||
as the file type identification in the output of
|
as the file type identification in the output of
|
||||||
.Ql ls -l .
|
.Ql ls -l .
|
||||||
Buffered devices are being accessed through the buffer cache of the
|
Buffered devices are being accessed through the buffer cache of the
|
||||||
operating system, and they are solely intended to layer a filesystem
|
operating system, and they are solely intended to layer a file system
|
||||||
on top of them. They are normally implemented for disks and disk-like
|
on top of them. They are normally implemented for disks and disk-like
|
||||||
devices only and, for historical reasons, for tape devices.
|
devices only and, for historical reasons, for tape devices.
|
||||||
.Pp
|
.Pp
|
||||||
@ -121,7 +121,7 @@ denotes the raw device for the first SCSI disk, while
|
|||||||
is the corresponding device node for the buffered device.
|
is the corresponding device node for the buffered device.
|
||||||
.Pp
|
.Pp
|
||||||
Unbuffered devices should be used for all actions that are not related
|
Unbuffered devices should be used for all actions that are not related
|
||||||
to filesystem operations, even if the device in question is a disk
|
to file system operations, even if the device in question is a disk
|
||||||
device. This includes making backups of entire disk partitions, or
|
device. This includes making backups of entire disk partitions, or
|
||||||
to
|
to
|
||||||
.Em raw
|
.Em raw
|
||||||
|
@ -52,7 +52,7 @@ unloading.
|
|||||||
The
|
The
|
||||||
.Fx
|
.Fx
|
||||||
system makes extensive use of loadable kernel modules, and provides loadable
|
system makes extensive use of loadable kernel modules, and provides loadable
|
||||||
versions of most filesystems, the
|
versions of most file systems, the
|
||||||
.Tn NFS
|
.Tn NFS
|
||||||
client and server, all the screen-savers, and the
|
client and server, all the screen-savers, and the
|
||||||
.Tn iBCS2
|
.Tn iBCS2
|
||||||
|
@ -61,7 +61,7 @@ or
|
|||||||
.Dq low
|
.Dq low
|
||||||
security level, attached to it,
|
security level, attached to it,
|
||||||
and these labels of integrity will be managed with a system cognizant
|
and these labels of integrity will be managed with a system cognizant
|
||||||
of IPC (signals, debugging, sockets, pipes), path-based filesystem
|
of IPC (signals, debugging, sockets, pipes), path-based file system
|
||||||
labels, virtual memory objects, and privileged system calls.
|
labels, virtual memory objects, and privileged system calls.
|
||||||
A process (or set of vmspace-sharing processes) will initially inherit
|
A process (or set of vmspace-sharing processes) will initially inherit
|
||||||
the integrity level of its parent, which, at the point of
|
the integrity level of its parent, which, at the point of
|
||||||
@ -84,8 +84,8 @@ operation performed after it has been initialized.
|
|||||||
Pre-existing jail or chroot environments may not necessarily work
|
Pre-existing jail or chroot environments may not necessarily work
|
||||||
completely.
|
completely.
|
||||||
.Nm Ns 's
|
.Nm Ns 's
|
||||||
filesystem should correctly respect the caching behavior of any of the
|
file system should correctly respect the caching behavior of any of the
|
||||||
system's filesystems, and so work for any
|
system's file systems, and so work for any
|
||||||
.Dq normal
|
.Dq normal
|
||||||
or
|
or
|
||||||
.Dq synthetic
|
.Dq synthetic
|
||||||
@ -99,7 +99,7 @@ See
|
|||||||
.Pa /sys/security/lomac/policy_plm.h
|
.Pa /sys/security/lomac/policy_plm.h
|
||||||
for specific information on exactly how
|
for specific information on exactly how
|
||||||
.Nm
|
.Nm
|
||||||
has been compiled to control access to the filesystem.
|
has been compiled to control access to the file system.
|
||||||
.Sh COMPATIBILITY
|
.Sh COMPATIBILITY
|
||||||
Some programs, for example
|
Some programs, for example
|
||||||
.Xr syslogd 8 ,
|
.Xr syslogd 8 ,
|
||||||
|
@ -113,7 +113,7 @@ or loaded as a module.
|
|||||||
.It Pa /compat/linux
|
.It Pa /compat/linux
|
||||||
minimal Linux run-time environment
|
minimal Linux run-time environment
|
||||||
.It Pa /compat/linux/proc
|
.It Pa /compat/linux/proc
|
||||||
limited Linux process filesystem
|
limited Linux process file system
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr brandelf 1 ,
|
.Xr brandelf 1 ,
|
||||||
|
@ -113,7 +113,7 @@ or loaded as a module.
|
|||||||
.It Pa /compat/linux
|
.It Pa /compat/linux
|
||||||
minimal Linux run-time environment
|
minimal Linux run-time environment
|
||||||
.It Pa /compat/linux/proc
|
.It Pa /compat/linux/proc
|
||||||
limited Linux process filesystem
|
limited Linux process file system
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr brandelf 1 ,
|
.Xr brandelf 1 ,
|
||||||
|
@ -132,7 +132,7 @@ accesses
|
|||||||
.Bx
|
.Bx
|
||||||
partition on the disc.
|
partition on the disc.
|
||||||
Normally, there is only
|
Normally, there is only
|
||||||
one filesystem on a CD-ROM disc.
|
one file system on a CD-ROM disc.
|
||||||
.It Pa /dev/(r)mcd0c
|
.It Pa /dev/(r)mcd0c
|
||||||
accesses raw device.
|
accesses raw device.
|
||||||
.El
|
.El
|
||||||
|
@ -52,7 +52,7 @@ accesses
|
|||||||
.Bx
|
.Bx
|
||||||
partition on the disc.
|
partition on the disc.
|
||||||
Normally, there is only
|
Normally, there is only
|
||||||
one filesystem on a CDROM disc.
|
one file system on a CDROM disc.
|
||||||
.It Pa /dev/[r]scd0c
|
.It Pa /dev/[r]scd0c
|
||||||
accesses the raw device.
|
accesses the raw device.
|
||||||
.El
|
.El
|
||||||
|
@ -44,7 +44,7 @@ For backwards compatibility the type
|
|||||||
is also recognized.
|
is also recognized.
|
||||||
If the kernel is created with option
|
If the kernel is created with option
|
||||||
.Dv MD_ROOT
|
.Dv MD_ROOT
|
||||||
the first preloaded image found will become the root filesystem.
|
the first preloaded image found will become the root file system.
|
||||||
.It Cm vnode
|
.It Cm vnode
|
||||||
A regular file is used as backing store.
|
A regular file is used as backing store.
|
||||||
This allows for mounting ISO images without the tedious
|
This allows for mounting ISO images without the tedious
|
||||||
|
@ -136,21 +136,21 @@ will configure normally.
|
|||||||
Component labels are also used to support the auto-detection and
|
Component labels are also used to support the auto-detection and
|
||||||
auto-configuration of RAID sets. A RAID set can be flagged as
|
auto-configuration of RAID sets. A RAID set can be flagged as
|
||||||
auto-configurable, in which case it will be configured automatically
|
auto-configurable, in which case it will be configured automatically
|
||||||
during the kernel boot process. RAID filesystems which are
|
during the kernel boot process. RAID file systems which are
|
||||||
automatically configured are also eligible to be the root filesystem.
|
automatically configured are also eligible to be the root file system.
|
||||||
There is currently only limited support (alpha and pmax architectures)
|
There is currently only limited support (alpha and pmax architectures)
|
||||||
for booting a kernel directly from a RAID 1 set, and no support for
|
for booting a kernel directly from a RAID 1 set, and no support for
|
||||||
booting from any other RAID sets. To use a RAID set as the root
|
booting from any other RAID sets. To use a RAID set as the root
|
||||||
filesystem, a kernel is usually obtained from a small non-RAID
|
file system, a kernel is usually obtained from a small non-RAID
|
||||||
partition, after which any auto-configuring RAID set can be used for the
|
partition, after which any auto-configuring RAID set can be used for the
|
||||||
root filesystem. See
|
root file system. See
|
||||||
.Xr raidctl 8
|
.Xr raidctl 8
|
||||||
for more information on auto-configuration of RAID sets.
|
for more information on auto-configuration of RAID sets.
|
||||||
.Pp
|
.Pp
|
||||||
The driver supports
|
The driver supports
|
||||||
.Sq hot spares ,
|
.Sq hot spares ,
|
||||||
disks which are on-line, but are not
|
disks which are on-line, but are not
|
||||||
actively used in an existing filesystem. Should a disk fail, the
|
actively used in an existing file system. Should a disk fail, the
|
||||||
driver is capable of reconstructing the failed disk onto a hot spare
|
driver is capable of reconstructing the failed disk onto a hot spare
|
||||||
or back onto a replacement drive.
|
or back onto a replacement drive.
|
||||||
If the components are hot swapable, the failed disk can then be
|
If the components are hot swapable, the failed disk can then be
|
||||||
@ -185,10 +185,10 @@ before doing a
|
|||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
or a
|
or a
|
||||||
.Xr newfs 8 ,
|
.Xr newfs 8 ,
|
||||||
filesystem integrity and parity integrity can be ensured. It bears
|
file system integrity and parity integrity can be ensured. It bears
|
||||||
repeating again that parity recomputation is
|
repeating again that parity recomputation is
|
||||||
.Ar required
|
.Ar required
|
||||||
before any filesystems are created or used on the RAID device. If the
|
before any file systems are created or used on the RAID device. If the
|
||||||
parity is not correct, then missing data cannot be correctly recovered.
|
parity is not correct, then missing data cannot be correctly recovered.
|
||||||
.Pp
|
.Pp
|
||||||
RAID levels may be combined in a hierarchical fashion. For example, a RAID 0
|
RAID levels may be combined in a hierarchical fashion. For example, a RAID 0
|
||||||
@ -259,7 +259,7 @@ result in data loss.
|
|||||||
Certain RAID levels (1, 4, 5, 6, and others) can protect against some
|
Certain RAID levels (1, 4, 5, 6, and others) can protect against some
|
||||||
data loss due to component failure. However the loss of two
|
data loss due to component failure. However the loss of two
|
||||||
components of a RAID 4 or 5 system, or the loss of a single component
|
components of a RAID 4 or 5 system, or the loss of a single component
|
||||||
of a RAID 0 system, will result in the entire filesystems on that RAID
|
of a RAID 0 system, will result in the entire file systems on that RAID
|
||||||
device being lost.
|
device being lost.
|
||||||
RAID is
|
RAID is
|
||||||
.Ar NOT
|
.Ar NOT
|
||||||
|
@ -29,14 +29,14 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm syncer
|
.Nm syncer
|
||||||
.Nd filesystem synchronizer kernel process
|
.Nd file system synchronizer kernel process
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.Nm
|
.Nm
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
kernel process helps protect the integrity of disk volumes
|
kernel process helps protect the integrity of disk volumes
|
||||||
by flushing volatile cached filesystem data to disk.
|
by flushing volatile cached file system data to disk.
|
||||||
.Pp
|
.Pp
|
||||||
The kernel places all
|
The kernel places all
|
||||||
.Xr vnode 9 Ns 's
|
.Xr vnode 9 Ns 's
|
||||||
@ -87,5 +87,5 @@ process first appeared in
|
|||||||
It is possible on some systems that a
|
It is possible on some systems that a
|
||||||
.Xr sync 2
|
.Xr sync 2
|
||||||
occurring simultaneously with a crash may cause
|
occurring simultaneously with a crash may cause
|
||||||
filesystem damage. See
|
file system damage. See
|
||||||
.Xr fsck 8 .
|
.Xr fsck 8 .
|
||||||
|
@ -98,11 +98,11 @@ Write a disklabel to the Zip drive (see
|
|||||||
.Nm vpo
|
.Nm vpo
|
||||||
for the
|
for the
|
||||||
.Nm disktab
|
.Nm disktab
|
||||||
entry), creates the filesystem and mounts the new filesystem on /mnt.
|
entry), creates the file system and mounts the new file system on /mnt.
|
||||||
.Pp
|
.Pp
|
||||||
.Dl newfs_msdos /dev/da0
|
.Dl newfs_msdos /dev/da0
|
||||||
.Pp
|
.Pp
|
||||||
Create a new FAT type filesystem.
|
Create a new FAT type file system.
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr ohci 4 ,
|
.Xr ohci 4 ,
|
||||||
.Xr uhci 4 ,
|
.Xr uhci 4 ,
|
||||||
|
@ -56,10 +56,10 @@ family supports the
|
|||||||
and
|
and
|
||||||
.Dv SOCK_DGRAM
|
.Dv SOCK_DGRAM
|
||||||
socket types and uses
|
socket types and uses
|
||||||
filesystem pathnames for addressing.
|
file system pathnames for addressing.
|
||||||
.Sh ADDRESSING
|
.Sh ADDRESSING
|
||||||
.Ux Ns -domain
|
.Ux Ns -domain
|
||||||
addresses are variable-length filesystem pathnames of
|
addresses are variable-length file system pathnames of
|
||||||
at most 104 characters.
|
at most 104 characters.
|
||||||
The include file
|
The include file
|
||||||
.Aq Pa sys/un.h
|
.Aq Pa sys/un.h
|
||||||
@ -76,7 +76,7 @@ Binding a name to a
|
|||||||
.Ux Ns -domain
|
.Ux Ns -domain
|
||||||
socket with
|
socket with
|
||||||
.Xr bind 2
|
.Xr bind 2
|
||||||
causes a socket file to be created in the filesystem.
|
causes a socket file to be created in the file system.
|
||||||
This file is
|
This file is
|
||||||
.Em not
|
.Em not
|
||||||
removed when the socket is closed \(em
|
removed when the socket is closed \(em
|
||||||
@ -93,7 +93,7 @@ All addresses are absolute- or relative-pathnames
|
|||||||
of other
|
of other
|
||||||
.Ux Ns -domain
|
.Ux Ns -domain
|
||||||
sockets.
|
sockets.
|
||||||
Normal filesystem access-control mechanisms are also
|
Normal file system access-control mechanisms are also
|
||||||
applied when referencing pathnames; e.g., the destination
|
applied when referencing pathnames; e.g., the destination
|
||||||
of a
|
of a
|
||||||
.Xr connect 2
|
.Xr connect 2
|
||||||
|
@ -85,10 +85,10 @@ By attaching an
|
|||||||
additional plex and subsequently detaching one of the older plexes, data can be
|
additional plex and subsequently detaching one of the older plexes, data can be
|
||||||
moved on-line without compromising access.
|
moved on-line without compromising access.
|
||||||
.It
|
.It
|
||||||
An additional plex can be used to obtain a consistent dump of a filesystem.
|
An additional plex can be used to obtain a consistent dump of a file system.
|
||||||
By
|
By
|
||||||
attaching an additional plex and detaching at a specific time, the detached plex
|
attaching an additional plex and detaching at a specific time, the detached plex
|
||||||
becomes an accurate snapshot of the filesystem at the time of detachment.
|
becomes an accurate snapshot of the file system at the time of detachment.
|
||||||
.\" Make sure to flush!
|
.\" Make sure to flush!
|
||||||
.El
|
.El
|
||||||
.It
|
.It
|
||||||
@ -163,7 +163,7 @@ devices.
|
|||||||
offers automatic startup.
|
offers automatic startup.
|
||||||
Unlike
|
Unlike
|
||||||
.Ux
|
.Ux
|
||||||
filesystems,
|
file systems,
|
||||||
.Nm
|
.Nm
|
||||||
volumes contain all the configuration information needed to ensure that they are
|
volumes contain all the configuration information needed to ensure that they are
|
||||||
started correctly when the subsystem is enabled.
|
started correctly when the subsystem is enabled.
|
||||||
@ -385,7 +385,7 @@ flag to
|
|||||||
.Xr newfs 8 .
|
.Xr newfs 8 .
|
||||||
For example, if you have a volume
|
For example, if you have a volume
|
||||||
.Pa concat ,
|
.Pa concat ,
|
||||||
use the following command to create a UFS filesystem on it:
|
use the following command to create a UFS file system on it:
|
||||||
.Pp
|
.Pp
|
||||||
.Dl "newfs -v /dev/vinum/concat"
|
.Dl "newfs -v /dev/vinum/concat"
|
||||||
.Sh OBJECT NAMING
|
.Sh OBJECT NAMING
|
||||||
|
@ -51,11 +51,11 @@ transferring data.
|
|||||||
.Pp
|
.Pp
|
||||||
DOS and
|
DOS and
|
||||||
.Fx
|
.Fx
|
||||||
filesystems are supported.
|
file systems are supported.
|
||||||
When mounting a DOS filesystem or
|
When mounting a DOS file system or
|
||||||
formating a
|
formating a
|
||||||
.Fx
|
.Fx
|
||||||
filesystem, check the slice of the disk with the
|
file system, check the slice of the disk with the
|
||||||
.Xr fdisk 8
|
.Xr fdisk 8
|
||||||
utility.
|
utility.
|
||||||
.Pp
|
.Pp
|
||||||
|
@ -43,18 +43,18 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm devfs
|
.Nm devfs
|
||||||
.Nd device filesystem
|
.Nd device file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
devfs /dev devfs rw 0 0
|
devfs /dev devfs rw 0 0
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The device filesystem, or
|
The device file system, or
|
||||||
.Nm ,
|
.Nm ,
|
||||||
provides access to kernel's device
|
provides access to kernel's device
|
||||||
namespace in the global filesystem namespace.
|
namespace in the global file system namespace.
|
||||||
The conventional mount point is
|
The conventional mount point is
|
||||||
.Pa /dev .
|
.Pa /dev .
|
||||||
.Pp
|
.Pp
|
||||||
The filesystem includes several directories, links, symbolic links
|
The file system includes several directories, links, symbolic links
|
||||||
and devices, some of which can also be written. In a chroot'ed
|
and devices, some of which can also be written. In a chroot'ed
|
||||||
environment,
|
environment,
|
||||||
.Nm
|
.Nm
|
||||||
@ -73,7 +73,7 @@ mount point.
|
|||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
filesystem first appeared in
|
file system first appeared in
|
||||||
.Fx 2.0 .
|
.Fx 2.0 .
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
|
@ -54,7 +54,7 @@ Directory entries may contain other directories
|
|||||||
as well as plain files; such nested directories are referred to as
|
as well as plain files; such nested directories are referred to as
|
||||||
subdirectories.
|
subdirectories.
|
||||||
A hierarchy of directories and files is formed in this manner
|
A hierarchy of directories and files is formed in this manner
|
||||||
and is called a filesystem (or referred to as a filesystem tree).
|
and is called a file system (or referred to as a file system tree).
|
||||||
.\" An entry in this tree,
|
.\" An entry in this tree,
|
||||||
.\" nested or not nested,
|
.\" nested or not nested,
|
||||||
.\" is a pathname.
|
.\" is a pathname.
|
||||||
@ -72,7 +72,7 @@ the system root directory
|
|||||||
has no parent and dot-dot points to itself like dot.
|
has no parent and dot-dot points to itself like dot.
|
||||||
.Pp
|
.Pp
|
||||||
File system nodes are ordinary directory files on which has
|
File system nodes are ordinary directory files on which has
|
||||||
been grafted a filesystem object, such as a physical disk or a
|
been grafted a file system object, such as a physical disk or a
|
||||||
partitioned area of such a disk.
|
partitioned area of such a disk.
|
||||||
(See
|
(See
|
||||||
.Xr mount 2
|
.Xr mount 2
|
||||||
@ -152,7 +152,7 @@ struct dirent {
|
|||||||
.Sh BUGS
|
.Sh BUGS
|
||||||
The usage of the member d_type of struct dirent is unportable as it is
|
The usage of the member d_type of struct dirent is unportable as it is
|
||||||
.Fx Ns -specific .
|
.Fx Ns -specific .
|
||||||
It also may fail on certain filesystems, for example the cd9660 filesystem.
|
It also may fail on certain file systems, for example the cd9660 file system.
|
||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
A
|
A
|
||||||
.Nm
|
.Nm
|
||||||
|
@ -118,7 +118,7 @@ default
|
|||||||
.It "\&ph num Size of partition `h' in sectors"
|
.It "\&ph num Size of partition `h' in sectors"
|
||||||
.It "\&ta str Partition type of partition `a'"
|
.It "\&ta str Partition type of partition `a'"
|
||||||
.Pf ( Bx 4.2
|
.Pf ( Bx 4.2
|
||||||
filesystem, swap, etc)
|
file system, swap, etc)
|
||||||
.It "\&tb str Partition type of partition `b'"
|
.It "\&tb str Partition type of partition `b'"
|
||||||
.It "\&tc str Partition type of partition `c'"
|
.It "\&tc str Partition type of partition `c'"
|
||||||
.It "\&td str Partition type of partition `d'"
|
.It "\&td str Partition type of partition `d'"
|
||||||
|
@ -43,18 +43,18 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm fdescfs
|
.Nm fdescfs
|
||||||
.Nd file-descriptor filesystem
|
.Nd file-descriptor file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
fdescfs /dev/fd fdescfs rw 0 0
|
fdescfs /dev/fd fdescfs rw 0 0
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The file-descriptor filesystem, or
|
The file-descriptor file system, or
|
||||||
.Nm ,
|
.Nm ,
|
||||||
provides access to the per-process file descriptor
|
provides access to the per-process file descriptor
|
||||||
namespace in the global filesystem namespace.
|
namespace in the global file system namespace.
|
||||||
The conventional mount point is
|
The conventional mount point is
|
||||||
.Pa /dev/fd .
|
.Pa /dev/fd .
|
||||||
.Pp
|
.Pp
|
||||||
The filesystem's contents
|
The file system's contents
|
||||||
appear as a list of numbered files
|
appear as a list of numbered files
|
||||||
which correspond to the open files of the process reading the
|
which correspond to the open files of the process reading the
|
||||||
directory.
|
directory.
|
||||||
@ -95,7 +95,7 @@ are ignored.
|
|||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
filesystem first appeared in
|
file system first appeared in
|
||||||
.Bx 4.4 .
|
.Bx 4.4 .
|
||||||
The
|
The
|
||||||
.Nm
|
.Nm
|
||||||
|
@ -38,7 +38,7 @@
|
|||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm fs ,
|
.Nm fs ,
|
||||||
.Nm inode
|
.Nm inode
|
||||||
.Nd format of filesystem volume
|
.Nd format of file system volume
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In ufs/ffs/fs.h
|
.In ufs/ffs/fs.h
|
||||||
@ -54,10 +54,10 @@ and
|
|||||||
.Aq Pa inode.h
|
.Aq Pa inode.h
|
||||||
declare several structures, defined variables and macros
|
declare several structures, defined variables and macros
|
||||||
which are used to create and manage the underlying format of
|
which are used to create and manage the underlying format of
|
||||||
filesystem objects on random access devices (disks).
|
file system objects on random access devices (disks).
|
||||||
.Pp
|
.Pp
|
||||||
The block size and number of blocks which
|
The block size and number of blocks which
|
||||||
comprise a filesystem are parameters of the filesystem.
|
comprise a file system are parameters of the file system.
|
||||||
Sectors beginning at
|
Sectors beginning at
|
||||||
.Dv BBLOCK
|
.Dv BBLOCK
|
||||||
and continuing for
|
and continuing for
|
||||||
@ -66,7 +66,7 @@ are used
|
|||||||
for a disklabel and for some hardware primary
|
for a disklabel and for some hardware primary
|
||||||
and secondary bootstrapping programs.
|
and secondary bootstrapping programs.
|
||||||
.Pp
|
.Pp
|
||||||
The actual filesystem begins at sector
|
The actual file system begins at sector
|
||||||
.Dv SBLOCK
|
.Dv SBLOCK
|
||||||
with the
|
with the
|
||||||
.Em super-block
|
.Em super-block
|
||||||
@ -77,10 +77,10 @@ from the file
|
|||||||
.Aq Pa ufs/ffs/fs.h :
|
.Aq Pa ufs/ffs/fs.h :
|
||||||
.Bd -literal
|
.Bd -literal
|
||||||
/*
|
/*
|
||||||
* Super block for an FFS filesystem.
|
* Super block for an FFS file system.
|
||||||
*/
|
*/
|
||||||
struct fs {
|
struct fs {
|
||||||
int32_t fs_firstfield; /* historic filesystem linked list, */
|
int32_t fs_firstfield; /* historic file system linked list, */
|
||||||
int32_t fs_unused_1; /* used for incore super blocks */
|
int32_t fs_unused_1; /* used for incore super blocks */
|
||||||
ufs_daddr_t fs_sblkno; /* addr of super-block in filesys */
|
ufs_daddr_t fs_sblkno; /* addr of super-block in filesys */
|
||||||
ufs_daddr_t fs_cblkno; /* offset of cyl-block in filesys */
|
ufs_daddr_t fs_cblkno; /* offset of cyl-block in filesys */
|
||||||
@ -123,7 +123,7 @@ struct fs {
|
|||||||
int32_t fs_interleave; /* hardware sector interleave */
|
int32_t fs_interleave; /* hardware sector interleave */
|
||||||
int32_t fs_trackskew; /* sector 0 skew, per track */
|
int32_t fs_trackskew; /* sector 0 skew, per track */
|
||||||
/* fs_id takes the space of the unused fs_headswitch and fs_trkseek fields */
|
/* fs_id takes the space of the unused fs_headswitch and fs_trkseek fields */
|
||||||
int32_t fs_id[2]; /* unique filesystem id*/
|
int32_t fs_id[2]; /* unique file system id*/
|
||||||
/* sizes determined by number of cylinder groups and their sizes */
|
/* sizes determined by number of cylinder groups and their sizes */
|
||||||
ufs_daddr_t fs_csaddr; /* blk addr of cyl grp summary area */
|
ufs_daddr_t fs_csaddr; /* blk addr of cyl grp summary area */
|
||||||
int32_t fs_cssize; /* size of cyl grp summary area */
|
int32_t fs_cssize; /* size of cyl grp summary area */
|
||||||
@ -133,7 +133,7 @@ struct fs {
|
|||||||
int32_t fs_nsect; /* sectors per track */
|
int32_t fs_nsect; /* sectors per track */
|
||||||
int32_t fs_spc; /* sectors per cylinder */
|
int32_t fs_spc; /* sectors per cylinder */
|
||||||
/* this comes from the disk driver partitioning */
|
/* this comes from the disk driver partitioning */
|
||||||
int32_t fs_ncyl; /* cylinders in filesystem */
|
int32_t fs_ncyl; /* cylinders in file system */
|
||||||
/* these fields can be computed from the others */
|
/* these fields can be computed from the others */
|
||||||
int32_t fs_cpg; /* cylinders per group */
|
int32_t fs_cpg; /* cylinders per group */
|
||||||
int32_t fs_ipg; /* inodes per group */
|
int32_t fs_ipg; /* inodes per group */
|
||||||
@ -142,7 +142,7 @@ struct fs {
|
|||||||
struct csum fs_cstotal;/* cylinder summary information */
|
struct csum fs_cstotal;/* cylinder summary information */
|
||||||
/* these fields are cleared at mount time */
|
/* these fields are cleared at mount time */
|
||||||
int8_t fs_fmod; /* super block modified flag */
|
int8_t fs_fmod; /* super block modified flag */
|
||||||
int8_t fs_clean; /* filesystem is clean flag */
|
int8_t fs_clean; /* file system is clean flag */
|
||||||
int8_t fs_ronly; /* mounted read-only flag */
|
int8_t fs_ronly; /* mounted read-only flag */
|
||||||
int8_t fs_flags; /* currently unused flag */
|
int8_t fs_flags; /* currently unused flag */
|
||||||
u_char fs_fsmnt[MAXMNTLEN]; /* name mounted on */
|
u_char fs_fsmnt[MAXMNTLEN]; /* name mounted on */
|
||||||
@ -170,9 +170,9 @@ struct fs {
|
|||||||
};
|
};
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Filesystem identification
|
* File system identification
|
||||||
*/
|
*/
|
||||||
#define FS_MAGIC 0x011954 /* the fast filesystem magic number */
|
#define FS_MAGIC 0x011954 /* the fast file system magic number */
|
||||||
#define FS_OKAY 0x7c269d38 /* superblock checksum */
|
#define FS_OKAY 0x7c269d38 /* superblock checksum */
|
||||||
#define FS_42INODEFMT -1 /* 4.2BSD inode format */
|
#define FS_42INODEFMT -1 /* 4.2BSD inode format */
|
||||||
#define FS_44INODEFMT 2 /* 4.4BSD inode format */
|
#define FS_44INODEFMT 2 /* 4.4BSD inode format */
|
||||||
@ -189,14 +189,14 @@ struct fs {
|
|||||||
#define FS_DYNAMICPOSTBLFMT 1 /* dynamic rotational table format */
|
#define FS_DYNAMICPOSTBLFMT 1 /* dynamic rotational table format */
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
Each disk drive contains some number of filesystems.
|
Each disk drive contains some number of file systems.
|
||||||
A filesystem consists of a number of cylinder groups.
|
A file system consists of a number of cylinder groups.
|
||||||
Each cylinder group has inodes and data.
|
Each cylinder group has inodes and data.
|
||||||
.Pp
|
.Pp
|
||||||
A filesystem is described by its super-block, which in turn
|
A file system is described by its super-block, which in turn
|
||||||
describes the cylinder groups. The super-block is critical
|
describes the cylinder groups. The super-block is critical
|
||||||
data and is replicated in each cylinder group to protect against
|
data and is replicated in each cylinder group to protect against
|
||||||
catastrophic loss. This is done at filesystem creation
|
catastrophic loss. This is done at file system creation
|
||||||
time and the critical
|
time and the critical
|
||||||
super-block data does not change, so the copies need not be
|
super-block data does not change, so the copies need not be
|
||||||
referenced further unless disaster strikes.
|
referenced further unless disaster strikes.
|
||||||
@ -216,17 +216,17 @@ unit.
|
|||||||
Large files consist of exclusively large data blocks. To avoid
|
Large files consist of exclusively large data blocks. To avoid
|
||||||
undue wasted disk space, the last data block of a small file is
|
undue wasted disk space, the last data block of a small file is
|
||||||
allocated as only as many fragments of a large block as are
|
allocated as only as many fragments of a large block as are
|
||||||
necessary. The filesystem format retains only a single pointer
|
necessary. The file system format retains only a single pointer
|
||||||
to such a fragment, which is a piece of a single large block that
|
to such a fragment, which is a piece of a single large block that
|
||||||
has been divided. The size of such a fragment is determinable from
|
has been divided. The size of such a fragment is determinable from
|
||||||
information in the inode, using the
|
information in the inode, using the
|
||||||
.Fn blksize fs ip lbn
|
.Fn blksize fs ip lbn
|
||||||
macro.
|
macro.
|
||||||
.Pp
|
.Pp
|
||||||
The filesystem records space availability at the fragment level;
|
The file system records space availability at the fragment level;
|
||||||
to determine block availability, aligned fragments are examined.
|
to determine block availability, aligned fragments are examined.
|
||||||
.Pp
|
.Pp
|
||||||
The root inode is the root of the filesystem.
|
The root inode is the root of the file system.
|
||||||
Inode 0 can't be used for normal purposes and
|
Inode 0 can't be used for normal purposes and
|
||||||
historically bad blocks were linked to inode 1,
|
historically bad blocks were linked to inode 1,
|
||||||
thus the root inode is 2 (inode 1 is no longer used for
|
thus the root inode is 2 (inode 1 is no longer used for
|
||||||
@ -235,7 +235,7 @@ assumption, so we are stuck with it).
|
|||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Fa fs_minfree
|
.Fa fs_minfree
|
||||||
element gives the minimum acceptable percentage of filesystem
|
element gives the minimum acceptable percentage of file system
|
||||||
blocks that may be free.
|
blocks that may be free.
|
||||||
If the freelist drops below this level
|
If the freelist drops below this level
|
||||||
only the super-user may continue to allocate blocks.
|
only the super-user may continue to allocate blocks.
|
||||||
@ -244,7 +244,7 @@ The
|
|||||||
element
|
element
|
||||||
may be set to 0 if no reserve of free blocks is deemed necessary,
|
may be set to 0 if no reserve of free blocks is deemed necessary,
|
||||||
however severe performance degradations will be observed if the
|
however severe performance degradations will be observed if the
|
||||||
filesystem is run at greater than 90% full; thus the default
|
file system is run at greater than 90% full; thus the default
|
||||||
value of
|
value of
|
||||||
.Fa fs_minfree
|
.Fa fs_minfree
|
||||||
is 10%.
|
is 10%.
|
||||||
@ -256,15 +256,15 @@ of the block size.
|
|||||||
.Pp
|
.Pp
|
||||||
The element
|
The element
|
||||||
.Fa fs_optim
|
.Fa fs_optim
|
||||||
specifies whether the filesystem should try to minimize the time spent
|
specifies whether the file system should try to minimize the time spent
|
||||||
allocating blocks, or if it should attempt to minimize the space
|
allocating blocks, or if it should attempt to minimize the space
|
||||||
fragmentation on the disk.
|
fragmentation on the disk.
|
||||||
If the value of fs_minfree (see above) is less than 10%,
|
If the value of fs_minfree (see above) is less than 10%,
|
||||||
then the filesystem defaults to optimizing for space to avoid
|
then the file system defaults to optimizing for space to avoid
|
||||||
running out of full sized blocks.
|
running out of full sized blocks.
|
||||||
If the value of minfree is greater than or equal to 10%,
|
If the value of minfree is greater than or equal to 10%,
|
||||||
fragmentation is unlikely to be problematical, and
|
fragmentation is unlikely to be problematical, and
|
||||||
the filesystem defaults to optimizing for time.
|
the file system defaults to optimizing for time.
|
||||||
.Pp
|
.Pp
|
||||||
.Em Cylinder group related limits :
|
.Em Cylinder group related limits :
|
||||||
Each cylinder keeps track of the availability of blocks at different
|
Each cylinder keeps track of the availability of blocks at different
|
||||||
@ -284,7 +284,7 @@ the default value for
|
|||||||
.Fa fs_rotdelay
|
.Fa fs_rotdelay
|
||||||
is 2ms.
|
is 2ms.
|
||||||
.Pp
|
.Pp
|
||||||
Each filesystem has a statically allocated number of inodes.
|
Each file system has a statically allocated number of inodes.
|
||||||
An inode is allocated for each
|
An inode is allocated for each
|
||||||
.Dv NBPI
|
.Dv NBPI
|
||||||
bytes of disk space.
|
bytes of disk space.
|
||||||
@ -306,12 +306,12 @@ must keep its size within
|
|||||||
Note that super-blocks are never more than size
|
Note that super-blocks are never more than size
|
||||||
.Dv SBSIZE .
|
.Dv SBSIZE .
|
||||||
.Pp
|
.Pp
|
||||||
The path name on which the filesystem is mounted is maintained in
|
The path name on which the file system is mounted is maintained in
|
||||||
.Fa fs_fsmnt .
|
.Fa fs_fsmnt .
|
||||||
.Dv MAXMNTLEN
|
.Dv MAXMNTLEN
|
||||||
defines the amount of space allocated in
|
defines the amount of space allocated in
|
||||||
the super-block for this name.
|
the super-block for this name.
|
||||||
The limit on the amount of summary information per filesystem
|
The limit on the amount of summary information per file system
|
||||||
is defined by
|
is defined by
|
||||||
.Dv MAXCSBUFS .
|
.Dv MAXCSBUFS .
|
||||||
For a 4096 byte block size, it is currently parameterized for a
|
For a 4096 byte block size, it is currently parameterized for a
|
||||||
@ -333,14 +333,14 @@ the
|
|||||||
macro to work.
|
macro to work.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
.Em "Super-block for a filesystem" :
|
.Em "Super-block for a file system" :
|
||||||
The size of the rotational layout tables
|
The size of the rotational layout tables
|
||||||
is limited by the fact that the super-block is of size
|
is limited by the fact that the super-block is of size
|
||||||
.Dv SBSIZE .
|
.Dv SBSIZE .
|
||||||
The size of these tables is
|
The size of these tables is
|
||||||
.Em inversely
|
.Em inversely
|
||||||
proportional to the block
|
proportional to the block
|
||||||
size of the filesystem.
|
size of the file system.
|
||||||
The size of the tables is
|
The size of the tables is
|
||||||
increased when sector sizes are not powers of two,
|
increased when sector sizes are not powers of two,
|
||||||
as this increases the number of cylinders
|
as this increases the number of cylinders
|
||||||
@ -361,7 +361,7 @@ The
|
|||||||
.Em Inode :
|
.Em Inode :
|
||||||
The inode is the focus of all file activity in the
|
The inode is the focus of all file activity in the
|
||||||
.Ux
|
.Ux
|
||||||
filesystem.
|
file system.
|
||||||
There is a unique inode allocated
|
There is a unique inode allocated
|
||||||
for each active file,
|
for each active file,
|
||||||
each current directory, each mounted-on file,
|
each current directory, each mounted-on file,
|
||||||
@ -372,6 +372,6 @@ For further information, see the include file
|
|||||||
.Sh HISTORY
|
.Sh HISTORY
|
||||||
A super-block structure named filsys appeared in
|
A super-block structure named filsys appeared in
|
||||||
.At v6 .
|
.At v6 .
|
||||||
The filesystem described in this manual appeared
|
The file system described in this manual appeared
|
||||||
in
|
in
|
||||||
.Bx 4.2 .
|
.Bx 4.2 .
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm fstab
|
.Nm fstab
|
||||||
.Nd static information about the filesystems
|
.Nd static information about the file systems
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In fstab.h
|
.In fstab.h
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
@ -49,7 +49,7 @@ systems.
|
|||||||
is only read by programs, and not written;
|
is only read by programs, and not written;
|
||||||
it is the duty of the system administrator to properly create
|
it is the duty of the system administrator to properly create
|
||||||
and maintain this file.
|
and maintain this file.
|
||||||
Each filesystem is described on a separate line;
|
Each file system is described on a separate line;
|
||||||
fields on each line are separated by tabs or spaces.
|
fields on each line are separated by tabs or spaces.
|
||||||
The order of records in
|
The order of records in
|
||||||
.Nm
|
.Nm
|
||||||
@ -65,8 +65,8 @@ doing their thing.
|
|||||||
The first field,
|
The first field,
|
||||||
.Pq Fa fs_spec ,
|
.Pq Fa fs_spec ,
|
||||||
describes the block special device or
|
describes the block special device or
|
||||||
remote filesystem to be mounted.
|
remote file system to be mounted.
|
||||||
For filesystems of type
|
For file systems of type
|
||||||
.Em ufs ,
|
.Em ufs ,
|
||||||
the special file name is the block special file name,
|
the special file name is the block special file name,
|
||||||
and not the character special file name.
|
and not the character special file name.
|
||||||
@ -76,46 +76,46 @@ last ``/'' in the special file name.
|
|||||||
.Pp
|
.Pp
|
||||||
The second field,
|
The second field,
|
||||||
.Pq Fa fs_file ,
|
.Pq Fa fs_file ,
|
||||||
describes the mount point for the filesystem.
|
describes the mount point for the file system.
|
||||||
For swap partitions, this field should be specified as ``none''.
|
For swap partitions, this field should be specified as ``none''.
|
||||||
.Pp
|
.Pp
|
||||||
The third field,
|
The third field,
|
||||||
.Pq Fa fs_vfstype ,
|
.Pq Fa fs_vfstype ,
|
||||||
describes the type of the filesystem.
|
describes the type of the file system.
|
||||||
The system can support various filesystem types.
|
The system can support various file system types.
|
||||||
Only the root, /usr, and /tmp filesystems need be statically
|
Only the root, /usr, and /tmp file systems need be statically
|
||||||
compiled into the kernel;
|
compiled into the kernel;
|
||||||
everything else will be automatically loaded at mount
|
everything else will be automatically loaded at mount
|
||||||
time. (Exception: the UFS family - FFS and LFS cannot
|
time. (Exception: the UFS family - FFS and LFS cannot
|
||||||
currently be demand-loaded.) Some people still prefer to statically
|
currently be demand-loaded.) Some people still prefer to statically
|
||||||
compile other filesystems as well.
|
compile other file systems as well.
|
||||||
.Pp
|
.Pp
|
||||||
The fourth field,
|
The fourth field,
|
||||||
.Pq Fa fs_mntops ,
|
.Pq Fa fs_mntops ,
|
||||||
describes the mount options associated with the filesystem.
|
describes the mount options associated with the file system.
|
||||||
It is formatted as a comma separated list of options.
|
It is formatted as a comma separated list of options.
|
||||||
It contains at least the type of mount (see
|
It contains at least the type of mount (see
|
||||||
.Fa fs_type
|
.Fa fs_type
|
||||||
below) plus any additional options
|
below) plus any additional options
|
||||||
appropriate to the filesystem type. See the options flag
|
appropriate to the file system type. See the options flag
|
||||||
.Pq Fl o
|
.Pq Fl o
|
||||||
in the
|
in the
|
||||||
.Xr mount 8
|
.Xr mount 8
|
||||||
page and the filesystem specific page, such as
|
page and the file system specific page, such as
|
||||||
.Xr mount_nfs 8 ,
|
.Xr mount_nfs 8 ,
|
||||||
for additional options that may be specified.
|
for additional options that may be specified.
|
||||||
.Pp
|
.Pp
|
||||||
If the options ``userquota'' and/or ``groupquota'' are specified,
|
If the options ``userquota'' and/or ``groupquota'' are specified,
|
||||||
the filesystem is automatically processed by the
|
the file system is automatically processed by the
|
||||||
.Xr quotacheck 8
|
.Xr quotacheck 8
|
||||||
command, and user and/or group disk quotas are enabled with
|
command, and user and/or group disk quotas are enabled with
|
||||||
.Xr quotaon 8 .
|
.Xr quotaon 8 .
|
||||||
By default,
|
By default,
|
||||||
filesystem quotas are maintained in files named
|
file system quotas are maintained in files named
|
||||||
.Pa quota.user
|
.Pa quota.user
|
||||||
and
|
and
|
||||||
.Pa quota.group
|
.Pa quota.group
|
||||||
which are located at the root of the associated filesystem.
|
which are located at the root of the associated file system.
|
||||||
These defaults may be overridden by putting an equal sign
|
These defaults may be overridden by putting an equal sign
|
||||||
and an alternative absolute pathname following the quota option.
|
and an alternative absolute pathname following the quota option.
|
||||||
Thus, if the user quota file for
|
Thus, if the user quota file for
|
||||||
@ -127,9 +127,9 @@ this location can be specified as:
|
|||||||
userquota=/var/quotas/tmp.user
|
userquota=/var/quotas/tmp.user
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
If the option ``noauto'' is specified, the filesystem will not be automatically
|
If the option ``noauto'' is specified, the file system will not be automatically
|
||||||
mounted at system startup.
|
mounted at system startup.
|
||||||
Note that, for network filesystems
|
Note that, for network file systems
|
||||||
of third party types
|
of third party types
|
||||||
(i.e. types supported by additional software
|
(i.e. types supported by additional software
|
||||||
not included in the base system)
|
not included in the base system)
|
||||||
@ -139,7 +139,7 @@ the
|
|||||||
.Xr rc.conf 5
|
.Xr rc.conf 5
|
||||||
variable must be used to extend the
|
variable must be used to extend the
|
||||||
.Xr rc 8
|
.Xr rc 8
|
||||||
startup script's list of network filesystem types.
|
startup script's list of network file system types.
|
||||||
.Pp
|
.Pp
|
||||||
The type of the mount is extracted from the
|
The type of the mount is extracted from the
|
||||||
.Fa fs_mntops
|
.Fa fs_mntops
|
||||||
@ -150,7 +150,7 @@ field (it is not deleted from the
|
|||||||
field).
|
field).
|
||||||
If
|
If
|
||||||
.Fa fs_type
|
.Fa fs_type
|
||||||
is ``rw'' or ``ro'' then the filesystem whose name is given in the
|
is ``rw'' or ``ro'' then the file system whose name is given in the
|
||||||
.Fa fs_file
|
.Fa fs_file
|
||||||
field is normally mounted read-write or read-only on the
|
field is normally mounted read-write or read-only on the
|
||||||
specified special file.
|
specified special file.
|
||||||
@ -172,31 +172,31 @@ This is useful to show disk partitions which are currently unused.
|
|||||||
.Pp
|
.Pp
|
||||||
The fifth field,
|
The fifth field,
|
||||||
.Pq Fa fs_freq ,
|
.Pq Fa fs_freq ,
|
||||||
is used for these filesystems by the
|
is used for these file systems by the
|
||||||
.Xr dump 8
|
.Xr dump 8
|
||||||
command to determine which filesystems need to be dumped.
|
command to determine which file systems need to be dumped.
|
||||||
If the fifth field is not present, a value of zero is returned and
|
If the fifth field is not present, a value of zero is returned and
|
||||||
.Nm dump
|
.Nm dump
|
||||||
will assume that the filesystem does not need to be dumped.
|
will assume that the file system does not need to be dumped.
|
||||||
.Pp
|
.Pp
|
||||||
The sixth field,
|
The sixth field,
|
||||||
.Pq Fa fs_passno ,
|
.Pq Fa fs_passno ,
|
||||||
is used by the
|
is used by the
|
||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
program to determine the order in which filesystem checks are done
|
program to determine the order in which file system checks are done
|
||||||
at reboot time.
|
at reboot time.
|
||||||
The root filesystem should be specified with a
|
The root file system should be specified with a
|
||||||
.Fa fs_passno
|
.Fa fs_passno
|
||||||
of 1, and other filesystems should have a
|
of 1, and other file systems should have a
|
||||||
.Fa fs_passno
|
.Fa fs_passno
|
||||||
of 2.
|
of 2.
|
||||||
Filesystems within a drive will be checked sequentially,
|
File systems within a drive will be checked sequentially,
|
||||||
but filesystems on different drives will be checked at the
|
but file systems on different drives will be checked at the
|
||||||
same time to utilize parallelism available in the hardware.
|
same time to utilize parallelism available in the hardware.
|
||||||
If the sixth field is not present or is zero,
|
If the sixth field is not present or is zero,
|
||||||
a value of zero is returned and
|
a value of zero is returned and
|
||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
will assume that the filesystem does not need to be checked.
|
will assume that the file system does not need to be checked.
|
||||||
.Bd -literal
|
.Bd -literal
|
||||||
#define FSTAB_RW "rw" /* read/write device */
|
#define FSTAB_RW "rw" /* read/write device */
|
||||||
#define FSTAB_RQ "rq" /* read/write with quotas */
|
#define FSTAB_RQ "rq" /* read/write with quotas */
|
||||||
@ -206,7 +206,7 @@ will assume that the filesystem does not need to be checked.
|
|||||||
|
|
||||||
struct fstab {
|
struct fstab {
|
||||||
char *fs_spec; /* block special device name */
|
char *fs_spec; /* block special device name */
|
||||||
char *fs_file; /* filesystem path prefix */
|
char *fs_file; /* file system path prefix */
|
||||||
char *fs_vfstype; /* File system type, ufs, nfs */
|
char *fs_vfstype; /* File system type, ufs, nfs */
|
||||||
char *fs_mntops; /* Mount options ala -o */
|
char *fs_mntops; /* Mount options ala -o */
|
||||||
char *fs_type; /* FSTAB_* from fs_mntops */
|
char *fs_type; /* FSTAB_* from fs_mntops */
|
||||||
|
@ -530,7 +530,7 @@ structures define the layout of the library hints, normally found in
|
|||||||
which is used by
|
which is used by
|
||||||
.Nm ld.so
|
.Nm ld.so
|
||||||
to quickly locate the shared object images in the
|
to quickly locate the shared object images in the
|
||||||
filesystem.
|
file system.
|
||||||
The organization of the hints file is not unlike that of an
|
The organization of the hints file is not unlike that of an
|
||||||
.Dq a.out
|
.Dq a.out
|
||||||
object file, in that it contains a header determining the offset and size
|
object file, in that it contains a header determining the offset and size
|
||||||
|
@ -7,15 +7,15 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm linprocfs
|
.Nm linprocfs
|
||||||
.Nd Linux process filesystem
|
.Nd Linux process file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.Bd -literal
|
.Bd -literal
|
||||||
linproc /compat/linux/proc linprocfs rw 0 0
|
linproc /compat/linux/proc linprocfs rw 0 0
|
||||||
.Ed
|
.Ed
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The Linux process filesystem, or
|
The Linux process file system, or
|
||||||
.Nm ,
|
.Nm ,
|
||||||
emulates a subset of Linux' process filesystem and is required for
|
emulates a subset of Linux' process file system and is required for
|
||||||
the complete operation of some Linux binaries.
|
the complete operation of some Linux binaries.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
|
@ -449,14 +449,14 @@ the previous day's values.
|
|||||||
.Pq Vt bool
|
.Pq Vt bool
|
||||||
Set to
|
Set to
|
||||||
.Dq YES
|
.Dq YES
|
||||||
to check for changes mounted filesystems to the previous day's values.
|
to check for changes mounted file systems to the previous day's values.
|
||||||
.It Va daily_status_security_noamd
|
.It Va daily_status_security_noamd
|
||||||
.Pq Vt bool
|
.Pq Vt bool
|
||||||
Set to
|
Set to
|
||||||
.Dq YES
|
.Dq YES
|
||||||
if you want to ignore
|
if you want to ignore
|
||||||
.Xr amd 8
|
.Xr amd 8
|
||||||
mounts when comparing against yesterdays filesystem mounts in the
|
mounts when comparing against yesterdays file system mounts in the
|
||||||
.Va daily_status_security_chkmounts_enable
|
.Va daily_status_security_chkmounts_enable
|
||||||
check.
|
check.
|
||||||
.It Va daily_status_security_chkuid0_enable
|
.It Va daily_status_security_chkuid0_enable
|
||||||
|
@ -7,15 +7,15 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm procfs
|
.Nm procfs
|
||||||
.Nd process filesystem
|
.Nd process file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.Bd -literal
|
.Bd -literal
|
||||||
proc /proc procfs rw 0 0
|
proc /proc procfs rw 0 0
|
||||||
.Ed
|
.Ed
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The process filesystem, or
|
The process file system, or
|
||||||
.Nm ,
|
.Nm ,
|
||||||
implements a view of the system process table inside the filesystem.
|
implements a view of the system process table inside the file system.
|
||||||
It is normally mounted on
|
It is normally mounted on
|
||||||
.Pa /proc ,
|
.Pa /proc ,
|
||||||
and is required for the complete operation of programs such as
|
and is required for the complete operation of programs such as
|
||||||
|
@ -28,13 +28,13 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm quota.user , quota.group
|
.Nm quota.user , quota.group
|
||||||
.Nd per-filesystem quota database
|
.Nd per file system quota database
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
Each filesystem with active quotas should contain a
|
Each file system with active quotas should contain a
|
||||||
.Pa quota.user
|
.Pa quota.user
|
||||||
and
|
and
|
||||||
.Pa quota.group
|
.Pa quota.group
|
||||||
file in the filesystem root.
|
file in the file system root.
|
||||||
These files are created by
|
These files are created by
|
||||||
.Xr quotacheck 8 ,
|
.Xr quotacheck 8 ,
|
||||||
and should be edited with
|
and should be edited with
|
||||||
|
@ -726,7 +726,7 @@ If set to
|
|||||||
will be run with the
|
will be run with the
|
||||||
.Fl y
|
.Fl y
|
||||||
flag if the initial preen
|
flag if the initial preen
|
||||||
of the filesystems fails.
|
of the file systems fails.
|
||||||
.It Va background_fsck
|
.It Va background_fsck
|
||||||
.Pq Vt bool
|
.Pq Vt bool
|
||||||
If set to
|
If set to
|
||||||
@ -739,19 +739,19 @@ in the background where possible.
|
|||||||
If set to something other than
|
If set to something other than
|
||||||
.Dq Li NO
|
.Dq Li NO
|
||||||
(the default),
|
(the default),
|
||||||
this variable extends the list of filesystem types
|
this variable extends the list of file system types
|
||||||
for which automatic mounting at startup by
|
for which automatic mounting at startup by
|
||||||
.Xr rc 8
|
.Xr rc 8
|
||||||
should be delayed until the network is initialized.
|
should be delayed until the network is initialized.
|
||||||
It should contain
|
It should contain
|
||||||
a whitespace-separated list of network filesystem descriptor pairs,
|
a whitespace-separated list of network file system descriptor pairs,
|
||||||
each consisting of a filesystem type as passed to
|
each consisting of a file system type as passed to
|
||||||
.Xr mount 8
|
.Xr mount 8
|
||||||
and a human-readable, one-word description,
|
and a human-readable, one-word description,
|
||||||
joined with a colon
|
joined with a colon
|
||||||
.Pq Ql \&: .
|
.Pq Ql \&: .
|
||||||
Extending the default list in this way is only necessary
|
Extending the default list in this way is only necessary
|
||||||
when third party filesystem types are used.
|
when third party file system types are used.
|
||||||
.It Va syslogd_enable
|
.It Va syslogd_enable
|
||||||
.Pq Vt bool
|
.Pq Vt bool
|
||||||
If set to
|
If set to
|
||||||
|
@ -35,7 +35,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm ffs
|
.Nm ffs
|
||||||
.Nd Berkeley fast filesystem
|
.Nd Berkeley fast file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
In the kernel configuration file:
|
In the kernel configuration file:
|
||||||
.Cd "options FFS"
|
.Cd "options FFS"
|
||||||
@ -53,21 +53,21 @@ In
|
|||||||
/dev/disk0a /mnt ufs rw 1 1
|
/dev/disk0a /mnt ufs rw 1 1
|
||||||
.Ed
|
.Ed
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
The Berkeley fast filesystem
|
The Berkeley fast file system
|
||||||
provides facilities to store filesystem data onto a disk device.
|
provides facilities to store file system data onto a disk device.
|
||||||
.Nm
|
.Nm
|
||||||
has been optimized over the years
|
has been optimized over the years
|
||||||
for speed and reliability
|
for speed and reliability
|
||||||
and is the default
|
and is the default
|
||||||
.Fx
|
.Fx
|
||||||
filesystem.
|
file system.
|
||||||
.Ss Quotas
|
.Ss Quotas
|
||||||
.Bl -tag -width 2n
|
.Bl -tag -width 2n
|
||||||
.It Cd "options QUOTA"
|
.It Cd "options QUOTA"
|
||||||
This option allows system administrators
|
This option allows system administrators
|
||||||
to set limits on disk usage
|
to set limits on disk usage
|
||||||
on a per-user basis.
|
on a per-user basis.
|
||||||
Quotas can be used only on filesystems
|
Quotas can be used only on file systems
|
||||||
mounted with the
|
mounted with the
|
||||||
.Cm quota
|
.Cm quota
|
||||||
option;
|
option;
|
||||||
@ -82,11 +82,11 @@ and
|
|||||||
The soft updates feature tracks writes to the disk
|
The soft updates feature tracks writes to the disk
|
||||||
and enforces metadata update dependencies
|
and enforces metadata update dependencies
|
||||||
(e.g., updating free block maps)
|
(e.g., updating free block maps)
|
||||||
to ensure that the filesystem remains consistent.
|
to ensure that the file system remains consistent.
|
||||||
.Pp
|
.Pp
|
||||||
To enable soft updates on an
|
To enable soft updates on an
|
||||||
.Em unmounted
|
.Em unmounted
|
||||||
filesystem, use the following command:
|
file system, use the following command:
|
||||||
.Pp
|
.Pp
|
||||||
.D1 Nm tunefs Fl n Cm enable Ar fs
|
.D1 Nm tunefs Fl n Cm enable Ar fs
|
||||||
.Pp
|
.Pp
|
||||||
@ -108,7 +108,7 @@ on networks including
|
|||||||
and
|
and
|
||||||
.Tn "Apple Macintosh"
|
.Tn "Apple Macintosh"
|
||||||
computers,
|
computers,
|
||||||
this option allows files on filesystems
|
this option allows files on file systems
|
||||||
mounted with the
|
mounted with the
|
||||||
.Cm suiddir
|
.Cm suiddir
|
||||||
option
|
option
|
||||||
@ -127,7 +127,7 @@ This option requires the presence of the
|
|||||||
option, and it is recommended that
|
option, and it is recommended that
|
||||||
.Dv UFS_EXTATTR_AUTOSTART
|
.Dv UFS_EXTATTR_AUTOSTART
|
||||||
is included as well,
|
is included as well,
|
||||||
so that ACLs are enabled atomically upon mounting the filesystem.
|
so that ACLs are enabled atomically upon mounting the file system.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
In order to enable support for ACLs,
|
In order to enable support for ACLs,
|
||||||
@ -139,11 +139,11 @@ which holds the access ACL,
|
|||||||
and
|
and
|
||||||
.Pa posix1e.acl_default ,
|
.Pa posix1e.acl_default ,
|
||||||
which holds the default ACL for directories.
|
which holds the default ACL for directories.
|
||||||
If you are using filesystem extended attributes,
|
If you are using file system extended attributes,
|
||||||
the following commands may be used to
|
the following commands may be used to
|
||||||
allocate space for and create the necessary EA backing files
|
allocate space for and create the necessary EA backing files
|
||||||
for ACLs in the root of each filesystem.
|
for ACLs in the root of each file system.
|
||||||
In these examples, the root filesystem is used;
|
In these examples, the root file system is used;
|
||||||
see
|
see
|
||||||
.Sx "Extended Attributes"
|
.Sx "Extended Attributes"
|
||||||
for more details.
|
for more details.
|
||||||
@ -154,7 +154,7 @@ extattrctl initattr -p / 388 posix1e.acl_access
|
|||||||
extattrctl initattr -p / 388 posix1e.acl_default
|
extattrctl initattr -p / 388 posix1e.acl_default
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
On the next mount of the root filesystem,
|
On the next mount of the root file system,
|
||||||
the attributes will be automatically started
|
the attributes will be automatically started
|
||||||
(if
|
(if
|
||||||
.Dv UFS_EXTATTR_AUTOSTART
|
.Dv UFS_EXTATTR_AUTOSTART
|
||||||
@ -179,9 +179,9 @@ If this option is defined,
|
|||||||
.Nm
|
.Nm
|
||||||
will search for a
|
will search for a
|
||||||
.Pa .attribute
|
.Pa .attribute
|
||||||
subdirectory of the filesystem root during the mount operation.
|
subdirectory of the file system root during the mount operation.
|
||||||
If found, extended attribute support will be
|
If found, extended attribute support will be
|
||||||
automatically started for that filesystem.
|
automatically started for that file system.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
The following
|
The following
|
||||||
@ -191,7 +191,7 @@ MIBs are defined for use with
|
|||||||
.Bl -hang -width ".Va vfs.ffs.doreallocblk"
|
.Bl -hang -width ".Va vfs.ffs.doreallocblk"
|
||||||
.It Va vfs.ffs.doasyncfree
|
.It Va vfs.ffs.doasyncfree
|
||||||
Asynchronously write out modified i-node and indirect blocks
|
Asynchronously write out modified i-node and indirect blocks
|
||||||
upon reallocating filesystem blocks to be contiguous.
|
upon reallocating file system blocks to be contiguous.
|
||||||
(Default: 1.)
|
(Default: 1.)
|
||||||
.It Va vfs.ffs.doreallocblks
|
.It Va vfs.ffs.doreallocblks
|
||||||
Enable support for the rearrangement of blocks
|
Enable support for the rearrangement of blocks
|
||||||
|
@ -37,12 +37,12 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm hier
|
.Nm hier
|
||||||
.Nd layout of filesystems
|
.Nd layout of file systems
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
A sketch of the filesystem hierarchy.
|
A sketch of the file system hierarchy.
|
||||||
.Bl -tag -width "/stand/"
|
.Bl -tag -width "/stand/"
|
||||||
.It Pa /
|
.It Pa /
|
||||||
root directory of the filesystem
|
root directory of the file system
|
||||||
.It Pa /bin/
|
.It Pa /bin/
|
||||||
user utilities fundamental to both single-user and multi-user environments
|
user utilities fundamental to both single-user and multi-user environments
|
||||||
.It Pa /boot/
|
.It Pa /boot/
|
||||||
@ -143,7 +143,7 @@ OpenSSL configuration files
|
|||||||
empty directory commonly used by
|
empty directory commonly used by
|
||||||
system administrators as a temporary mount point
|
system administrators as a temporary mount point
|
||||||
.It Pa /proc/
|
.It Pa /proc/
|
||||||
process filesystem;
|
process file system;
|
||||||
see
|
see
|
||||||
.Xr procfs 5 ,
|
.Xr procfs 5 ,
|
||||||
.Xr mount_procfs 8
|
.Xr mount_procfs 8
|
||||||
@ -208,28 +208,28 @@ WaveLAN driver
|
|||||||
.It Pa fs/
|
.It Pa fs/
|
||||||
.Bl -tag -width "kerberosIV/" -compact
|
.Bl -tag -width "kerberosIV/" -compact
|
||||||
.It Pa fdescfs/
|
.It Pa fdescfs/
|
||||||
per-process file descriptors filesystem
|
per-process file descriptors file system
|
||||||
.It Pa fifofs/
|
.It Pa fifofs/
|
||||||
.St -p1003.1
|
.St -p1003.1
|
||||||
FIFOs filesystem
|
FIFOs file system
|
||||||
.It Pa msdosfs/
|
.It Pa msdosfs/
|
||||||
MS-DOS filesystem
|
MS-DOS file system
|
||||||
.It Pa ntfs/
|
.It Pa ntfs/
|
||||||
NTFS filesystem
|
NTFS file system
|
||||||
.It Pa nullfs/
|
.It Pa nullfs/
|
||||||
loopback filesystem
|
loopback file system
|
||||||
.It Pa nwfs/
|
.It Pa nwfs/
|
||||||
NetWare filesystem
|
NetWare file system
|
||||||
.It Pa portalfs/
|
.It Pa portalfs/
|
||||||
portal filesystem
|
portal file system
|
||||||
.It Pa procfs/
|
.It Pa procfs/
|
||||||
process filesystem
|
process file system
|
||||||
.It Pa smbfs/
|
.It Pa smbfs/
|
||||||
SMB/CIFS filesystem
|
SMB/CIFS file system
|
||||||
.It Pa umapfs/
|
.It Pa umapfs/
|
||||||
alternate uid/gid mappings filesystem
|
alternate uid/gid mappings file system
|
||||||
.It Pa unionfs
|
.It Pa unionfs
|
||||||
union filesystem
|
union file system
|
||||||
.El
|
.El
|
||||||
.It Pa g++/
|
.It Pa g++/
|
||||||
GNU C++ include files
|
GNU C++ include files
|
||||||
@ -242,7 +242,7 @@ ISC utility library libisc include files
|
|||||||
.It Pa isofs/
|
.It Pa isofs/
|
||||||
.Bl -tag -width "kerberosIV/" -compact
|
.Bl -tag -width "kerberosIV/" -compact
|
||||||
.It Pa cd9660/
|
.It Pa cd9660/
|
||||||
iso9660 filesystem
|
iso9660 file system
|
||||||
.El
|
.El
|
||||||
.It Pa kerberosIV/
|
.It Pa kerberosIV/
|
||||||
C include files for kerberos authentication package;
|
C include files for kerberos authentication package;
|
||||||
@ -327,9 +327,9 @@ system C include files (kernel data structures)
|
|||||||
C include files for UFS (The U-word File System)
|
C include files for UFS (The U-word File System)
|
||||||
.Bl -tag -width "kerberosIV/" -compact
|
.Bl -tag -width "kerberosIV/" -compact
|
||||||
.It Pa ffs/
|
.It Pa ffs/
|
||||||
Fast filesystem
|
Fast file system
|
||||||
.It Pa ufs/
|
.It Pa ufs/
|
||||||
UFS filesystem
|
UFS file system
|
||||||
.El
|
.El
|
||||||
.It Pa vm/
|
.It Pa vm/
|
||||||
virtual memory;
|
virtual memory;
|
||||||
@ -719,7 +719,7 @@ system messages database;
|
|||||||
see
|
see
|
||||||
.Xr msgs 1
|
.Xr msgs 1
|
||||||
.It Pa quotas/
|
.It Pa quotas/
|
||||||
filesystem quota information files
|
file system quota information files
|
||||||
.It Pa run/
|
.It Pa run/
|
||||||
system information files describing various info about
|
system information files describing various info about
|
||||||
system since it was booted
|
system since it was booted
|
||||||
@ -779,7 +779,7 @@ the NIS maps
|
|||||||
.Sh NOTES
|
.Sh NOTES
|
||||||
This manual page documents the default
|
This manual page documents the default
|
||||||
.Fx
|
.Fx
|
||||||
filesystem layout, but
|
file system layout, but
|
||||||
the actual hierarchy on a given system is defined at the system
|
the actual hierarchy on a given system is defined at the system
|
||||||
administrator's discretion.
|
administrator's discretion.
|
||||||
A well-maintained installation will include a customized version of
|
A well-maintained installation will include a customized version of
|
||||||
|
@ -79,7 +79,7 @@ Uses
|
|||||||
.Dq Li "make installworld"
|
.Dq Li "make installworld"
|
||||||
to install a clean system into a
|
to install a clean system into a
|
||||||
.Xr chroot 8
|
.Xr chroot 8
|
||||||
environment on the filesystem.
|
environment on the file system.
|
||||||
Checks out the specified version of the source code and then rebuilds
|
Checks out the specified version of the source code and then rebuilds
|
||||||
the entire system in the clean environment with
|
the entire system in the clean environment with
|
||||||
.Dq Li "make world" .
|
.Dq Li "make world" .
|
||||||
@ -153,7 +153,7 @@ Sets up a suitable area to build CD-ROM images in
|
|||||||
.It Cm iso.1
|
.It Cm iso.1
|
||||||
Builds two ISO images (installation and
|
Builds two ISO images (installation and
|
||||||
.Dq live
|
.Dq live
|
||||||
filesystem) from the CD-ROM release area
|
file system) from the CD-ROM release area
|
||||||
(disabled by default, see
|
(disabled by default, see
|
||||||
.Va MAKE_ISOS
|
.Va MAKE_ISOS
|
||||||
below).
|
below).
|
||||||
@ -189,7 +189,7 @@ environment for the entire release build.
|
|||||||
.\" XXX: "we don't know how much space you'll need, but make sure you have
|
.\" XXX: "we don't know how much space you'll need, but make sure you have
|
||||||
.\" XXX: at least 3 GB to be safe" (I know i'm still hardcoding a number,
|
.\" XXX: at least 3 GB to be safe" (I know i'm still hardcoding a number,
|
||||||
.\" XXX: but at least it looks less like a decree and more like an estimate.
|
.\" XXX: but at least it looks less like a decree and more like an estimate.
|
||||||
This filesystem should have at least 2.3 gigabytes of free space on the
|
This file system should have at least 2.3 gigabytes of free space on the
|
||||||
i386 architecture.
|
i386 architecture.
|
||||||
.It Va CVSROOT
|
.It Va CVSROOT
|
||||||
The location of the
|
The location of the
|
||||||
@ -440,7 +440,7 @@ used a manual checklist, compiled by
|
|||||||
.An Rod Grimes ,
|
.An Rod Grimes ,
|
||||||
to produce a release.
|
to produce a release.
|
||||||
Apart from being incomplete, the list put a lot of specific demands on
|
Apart from being incomplete, the list put a lot of specific demands on
|
||||||
available filesystems and was quite torturous to execute.
|
available file systems and was quite torturous to execute.
|
||||||
.Pp
|
.Pp
|
||||||
As part of the
|
As part of the
|
||||||
.Fx 2.0
|
.Fx 2.0
|
||||||
|
@ -122,7 +122,7 @@ Securing user accounts
|
|||||||
.It
|
.It
|
||||||
Securing the password file
|
Securing the password file
|
||||||
.It
|
.It
|
||||||
Securing the kernel core, raw devices, and filesystems
|
Securing the kernel core, raw devices, and file systems
|
||||||
.It
|
.It
|
||||||
Quick detection of inappropriate changes made to the system
|
Quick detection of inappropriate changes made to the system
|
||||||
.It
|
.It
|
||||||
@ -319,7 +319,7 @@ the password file
|
|||||||
(see
|
(see
|
||||||
.Sq Checking file integrity
|
.Sq Checking file integrity
|
||||||
below).
|
below).
|
||||||
.Sh SECURING THE KERNEL CORE, RAW DEVICES, AND FILESYSTEMS
|
.Sh SECURING THE KERNEL CORE, RAW DEVICES, AND FILE SYSTEMS
|
||||||
If an attacker breaks root he can do just about anything, but there
|
If an attacker breaks root he can do just about anything, but there
|
||||||
are certain conveniences. For example, most modern kernels have a
|
are certain conveniences. For example, most modern kernels have a
|
||||||
packet sniffing device driver built in. Under
|
packet sniffing device driver built in. Under
|
||||||
@ -384,7 +384,7 @@ limited-access box significant access to the other machines in the business,
|
|||||||
usually either by doing a read-only NFS export of the other machines to the
|
usually either by doing a read-only NFS export of the other machines to the
|
||||||
limited-access box, or by setting up ssh keypairs to allow the limit-access
|
limited-access box, or by setting up ssh keypairs to allow the limit-access
|
||||||
box to ssh to the other machines. Except for its network traffic, NFS is
|
box to ssh to the other machines. Except for its network traffic, NFS is
|
||||||
the least visible method - allowing you to monitor the filesystems on each
|
the least visible method - allowing you to monitor the file systems on each
|
||||||
client box virtually undetected. If your
|
client box virtually undetected. If your
|
||||||
limited-access server is connected to the client boxes through a switch,
|
limited-access server is connected to the client boxes through a switch,
|
||||||
the NFS method is often the better choice. If your limited-access server
|
the NFS method is often the better choice. If your limited-access server
|
||||||
|
@ -15,13 +15,13 @@ When using
|
|||||||
.Xr disklabel 8
|
.Xr disklabel 8
|
||||||
or
|
or
|
||||||
.Xr sysinstall 8
|
.Xr sysinstall 8
|
||||||
to lay out your filesystems on a hard disk it is important to remember
|
to lay out your file systems on a hard disk it is important to remember
|
||||||
that hard drives can transfer data much more quickly from outer tracks
|
that hard drives can transfer data much more quickly from outer tracks
|
||||||
than they can from inner tracks.
|
than they can from inner tracks.
|
||||||
To take advantage of this you should
|
To take advantage of this you should
|
||||||
try to pack your smaller filesystems and swap closer to the outer tracks,
|
try to pack your smaller file systems and swap closer to the outer tracks,
|
||||||
follow with the larger filesystems, and end with the largest filesystems.
|
follow with the larger file systems, and end with the largest file systems.
|
||||||
It is also important to size system standard filesystems such that you
|
It is also important to size system standard file systems such that you
|
||||||
will not be forced to resize them later as you scale the machine up.
|
will not be forced to resize them later as you scale the machine up.
|
||||||
I usually create, in order, a 128M root, 1G swap, 128M
|
I usually create, in order, a 128M root, 1G swap, 128M
|
||||||
.Pa /var ,
|
.Pa /var ,
|
||||||
@ -85,7 +85,7 @@ Also note that sysinstall will create a
|
|||||||
.Pa /tmp
|
.Pa /tmp
|
||||||
directory.
|
directory.
|
||||||
Dedicating a partition for temporary file storage is important for
|
Dedicating a partition for temporary file storage is important for
|
||||||
two reasons: first, it reduces the possibility of filesystem corruption
|
two reasons: first, it reduces the possibility of file system corruption
|
||||||
in a crash, and second it reduces the chance of a runaway process that
|
in a crash, and second it reduces the chance of a runaway process that
|
||||||
fills up
|
fills up
|
||||||
.Oo Pa /var Oc Ns Pa /tmp
|
.Oo Pa /var Oc Ns Pa /tmp
|
||||||
@ -155,7 +155,7 @@ Then I do not have to worry about undersizing things!
|
|||||||
Well, there are several reasons this is not a good idea.
|
Well, there are several reasons this is not a good idea.
|
||||||
First,
|
First,
|
||||||
each partition has different operational characteristics and separating them
|
each partition has different operational characteristics and separating them
|
||||||
allows the filesystem to tune itself to those characteristics.
|
allows the file system to tune itself to those characteristics.
|
||||||
For example,
|
For example,
|
||||||
the root and
|
the root and
|
||||||
.Pa /usr
|
.Pa /usr
|
||||||
@ -198,8 +198,8 @@ and
|
|||||||
.Em cylinders/group .
|
.Em cylinders/group .
|
||||||
.Pp
|
.Pp
|
||||||
.Fx
|
.Fx
|
||||||
performs best when using 8K or 16K filesystem block sizes.
|
performs best when using 8K or 16K file system block sizes.
|
||||||
The default filesystem block size is 16K,
|
The default file system block size is 16K,
|
||||||
which provides best performance for most applications,
|
which provides best performance for most applications,
|
||||||
with the exception of those that perform random access on large files
|
with the exception of those that perform random access on large files
|
||||||
(such as database server software).
|
(such as database server software).
|
||||||
@ -211,9 +211,9 @@ can cause fragmentation of the buffer cache and
|
|||||||
lead to lower performance.
|
lead to lower performance.
|
||||||
.Pp
|
.Pp
|
||||||
The defaults may be unsuitable
|
The defaults may be unsuitable
|
||||||
for a filesystem that requires a very large number of i-nodes
|
for a file system that requires a very large number of i-nodes
|
||||||
or is intended to hold a large number of very small files.
|
or is intended to hold a large number of very small files.
|
||||||
Such a filesystem should be created with an 8K or 4K block size.
|
Such a file system should be created with an 8K or 4K block size.
|
||||||
This also requires you to specify a smaller
|
This also requires you to specify a smaller
|
||||||
fragment size.
|
fragment size.
|
||||||
We recommend always using a fragment size that is 1/8
|
We recommend always using a fragment size that is 1/8
|
||||||
@ -229,12 +229,12 @@ as database files, you can increase the
|
|||||||
ratio which reduces the number of i-nodes (maximum number of files and
|
ratio which reduces the number of i-nodes (maximum number of files and
|
||||||
directories that can be created) for that partition.
|
directories that can be created) for that partition.
|
||||||
Decreasing the number
|
Decreasing the number
|
||||||
of i-nodes in a filesystem can greatly reduce
|
of i-nodes in a file system can greatly reduce
|
||||||
.Xr fsck 8
|
.Xr fsck 8
|
||||||
recovery times after a crash.
|
recovery times after a crash.
|
||||||
Do not use this option
|
Do not use this option
|
||||||
unless you are actually storing large files on the partition, because if you
|
unless you are actually storing large files on the partition, because if you
|
||||||
overcompensate you can wind up with a filesystem that has lots of free
|
overcompensate you can wind up with a file system that has lots of free
|
||||||
space remaining but cannot accommodate any more files.
|
space remaining but cannot accommodate any more files.
|
||||||
Using 32768, 65536, or 262144 bytes/i-node is recommended.
|
Using 32768, 65536, or 262144 bytes/i-node is recommended.
|
||||||
You can go higher but
|
You can go higher but
|
||||||
@ -245,13 +245,13 @@ For example,
|
|||||||
.Dq Li "newfs -i 32768 ..." .
|
.Dq Li "newfs -i 32768 ..." .
|
||||||
.Pp
|
.Pp
|
||||||
.Xr tunefs 8
|
.Xr tunefs 8
|
||||||
may be used to further tune a filesystem.
|
may be used to further tune a file system.
|
||||||
This command can be run in
|
This command can be run in
|
||||||
single-user mode without having to reformat the filesystem.
|
single-user mode without having to reformat the file system.
|
||||||
However, this is possibly the most abused program in the system.
|
However, this is possibly the most abused program in the system.
|
||||||
Many people attempt to
|
Many people attempt to
|
||||||
increase available filesystem space by setting the min-free percentage to 0.
|
increase available file system space by setting the min-free percentage to 0.
|
||||||
This can lead to severe filesystem fragmentation and we do not recommend
|
This can lead to severe file system fragmentation and we do not recommend
|
||||||
that you do this.
|
that you do this.
|
||||||
Really the only
|
Really the only
|
||||||
.Xr tunefs 8
|
.Xr tunefs 8
|
||||||
@ -267,27 +267,27 @@ option to
|
|||||||
.Xr newfs 8 ,
|
.Xr newfs 8 ,
|
||||||
and
|
and
|
||||||
.Xr sysinstall 8
|
.Xr sysinstall 8
|
||||||
will typically enable softupdates automatically for non-root filesystems).
|
will typically enable softupdates automatically for non-root file systems).
|
||||||
Softupdates drastically improves meta-data performance, mainly file
|
Softupdates drastically improves meta-data performance, mainly file
|
||||||
creation and deletion.
|
creation and deletion.
|
||||||
We recommend enabling softupdates on most filesystems; however, there
|
We recommend enabling softupdates on most file systems; however, there
|
||||||
are two limitations to softupdates that you should be aware of when
|
are two limitations to softupdates that you should be aware of when
|
||||||
determining whether to use it on a filesystem.
|
determining whether to use it on a file system.
|
||||||
First, softupdates guarantees filesystem consistency in the
|
First, softupdates guarantees file system consistency in the
|
||||||
case of a crash but could very easily be several seconds (even a minute!\&)
|
case of a crash but could very easily be several seconds (even a minute!\&)
|
||||||
behind on pending write to the physical disk.
|
behind on pending write to the physical disk.
|
||||||
If you crash you may lose more work
|
If you crash you may lose more work
|
||||||
than otherwise.
|
than otherwise.
|
||||||
Secondly, softupdates delays the freeing of filesystem
|
Secondly, softupdates delays the freeing of file system
|
||||||
blocks.
|
blocks.
|
||||||
If you have a filesystem (such as the root filesystem) which is
|
If you have a file system (such as the root file system) which is
|
||||||
close to full, doing a major update of it, e.g.\&
|
close to full, doing a major update of it, e.g.\&
|
||||||
.Dq Li "make installworld" ,
|
.Dq Li "make installworld" ,
|
||||||
can run it out of space and cause the update to fail.
|
can run it out of space and cause the update to fail.
|
||||||
For this reason, softupdates will not be enabled on the root filesystem
|
For this reason, softupdates will not be enabled on the root file system
|
||||||
during a typical install.
|
during a typical install.
|
||||||
There is no loss of performance since the root
|
There is no loss of performance since the root
|
||||||
filesystem is rarely written to.
|
file system is rarely written to.
|
||||||
.Pp
|
.Pp
|
||||||
A number of run-time
|
A number of run-time
|
||||||
.Xr mount 8
|
.Xr mount 8
|
||||||
@ -301,7 +301,7 @@ useful
|
|||||||
option is called
|
option is called
|
||||||
.Cm noatime .
|
.Cm noatime .
|
||||||
.Ux
|
.Ux
|
||||||
filesystems normally update the last-accessed time of a file or
|
file systems normally update the last-accessed time of a file or
|
||||||
directory whenever it is accessed.
|
directory whenever it is accessed.
|
||||||
This operation is handled in
|
This operation is handled in
|
||||||
.Fx
|
.Fx
|
||||||
@ -318,7 +318,7 @@ However, you should not gratuitously turn off atime
|
|||||||
updates everywhere.
|
updates everywhere.
|
||||||
For example, the
|
For example, the
|
||||||
.Pa /var
|
.Pa /var
|
||||||
filesystem customarily
|
file system customarily
|
||||||
holds mailboxes, and atime (in combination with mtime) is used to
|
holds mailboxes, and atime (in combination with mtime) is used to
|
||||||
determine whether a mailbox has new mail.
|
determine whether a mailbox has new mail.
|
||||||
You might as well leave
|
You might as well leave
|
||||||
@ -335,13 +335,13 @@ use the atime field for reporting.
|
|||||||
In larger systems you can stripe partitions from several drives together
|
In larger systems you can stripe partitions from several drives together
|
||||||
to create a much larger overall partition.
|
to create a much larger overall partition.
|
||||||
Striping can also improve
|
Striping can also improve
|
||||||
the performance of a filesystem by splitting I/O operations across two
|
the performance of a file system by splitting I/O operations across two
|
||||||
or more disks.
|
or more disks.
|
||||||
The
|
The
|
||||||
.Xr vinum 8
|
.Xr vinum 8
|
||||||
and
|
and
|
||||||
.Xr ccdconfig 8
|
.Xr ccdconfig 8
|
||||||
utilities may be used to create simple striped filesystems.
|
utilities may be used to create simple striped file systems.
|
||||||
Generally
|
Generally
|
||||||
speaking, striping smaller partitions such as the root and
|
speaking, striping smaller partitions such as the root and
|
||||||
.Pa /var/tmp ,
|
.Pa /var/tmp ,
|
||||||
@ -354,7 +354,7 @@ typically
|
|||||||
or custom partitions used to hold databases and web pages.
|
or custom partitions used to hold databases and web pages.
|
||||||
Choosing the proper stripe size is also
|
Choosing the proper stripe size is also
|
||||||
important.
|
important.
|
||||||
Filesystems tend to store meta-data on power-of-2 boundaries
|
File systems tend to store meta-data on power-of-2 boundaries
|
||||||
and you usually want to reduce seeking rather than increase seeking.
|
and you usually want to reduce seeking rather than increase seeking.
|
||||||
This
|
This
|
||||||
means you want to use a large off-center stripe size such as 1152 sectors
|
means you want to use a large off-center stripe size such as 1152 sectors
|
||||||
@ -400,7 +400,7 @@ sysctl defaults to 1 (on).
|
|||||||
This parameter controls how directories are cached
|
This parameter controls how directories are cached
|
||||||
by the system.
|
by the system.
|
||||||
Most directories are small and use but a single fragment
|
Most directories are small and use but a single fragment
|
||||||
(typically 1K) in the filesystem and even less (typically 512 bytes) in
|
(typically 1K) in the file system and even less (typically 512 bytes) in
|
||||||
the buffer cache.
|
the buffer cache.
|
||||||
However, when operating in the default mode the buffer
|
However, when operating in the default mode the buffer
|
||||||
cache will only cache a fixed number of directories even if you have a huge
|
cache will only cache a fixed number of directories even if you have a huge
|
||||||
@ -422,7 +422,7 @@ wasted memory but you should experiment to find out.
|
|||||||
The
|
The
|
||||||
.Va vfs.write_behind
|
.Va vfs.write_behind
|
||||||
sysctl defaults to 1 (on).
|
sysctl defaults to 1 (on).
|
||||||
This tells the filesystem to issue media
|
This tells the file system to issue media
|
||||||
writes as full clusters are collected, which typically occurs when writing
|
writes as full clusters are collected, which typically occurs when writing
|
||||||
large sequential files.
|
large sequential files.
|
||||||
The idea is to avoid saturating the buffer
|
The idea is to avoid saturating the buffer
|
||||||
@ -749,7 +749,7 @@ More and more programs are using the
|
|||||||
system call to transmit files over the network.
|
system call to transmit files over the network.
|
||||||
The
|
The
|
||||||
.Va kern.ipc.nsfbufs
|
.Va kern.ipc.nsfbufs
|
||||||
sysctl controls the number of filesystem buffers
|
sysctl controls the number of file system buffers
|
||||||
.Xr sendfile 2
|
.Xr sendfile 2
|
||||||
is allowed to use to perform its work.
|
is allowed to use to perform its work.
|
||||||
This parameter nominally scales
|
This parameter nominally scales
|
||||||
@ -818,7 +818,7 @@ With IDE write caching turned
|
|||||||
on, IDE hard drives will not only write data to disk out of order, they
|
on, IDE hard drives will not only write data to disk out of order, they
|
||||||
will sometimes delay some of the blocks indefinitely under heavy disk
|
will sometimes delay some of the blocks indefinitely under heavy disk
|
||||||
load.
|
load.
|
||||||
A crash or power failure can result in serious filesystem
|
A crash or power failure can result in serious file system
|
||||||
corruption.
|
corruption.
|
||||||
So our default was changed to be safe.
|
So our default was changed to be safe.
|
||||||
Unfortunately, the
|
Unfortunately, the
|
||||||
|
@ -58,7 +58,7 @@ and then invokes an automatic reboot procedure as
|
|||||||
described in
|
described in
|
||||||
.Xr reboot 8 .
|
.Xr reboot 8 .
|
||||||
Unless some unexpected inconsistency is encountered in the state
|
Unless some unexpected inconsistency is encountered in the state
|
||||||
of the filesystems due to hardware or software failure, the system
|
of the file systems due to hardware or software failure, the system
|
||||||
will then resume multi-user operations.
|
will then resume multi-user operations.
|
||||||
.Pp
|
.Pp
|
||||||
The system has a large number of internal consistency checks; if one
|
The system has a large number of internal consistency checks; if one
|
||||||
@ -78,12 +78,12 @@ error produced the message in some unexpected way.
|
|||||||
.Pp
|
.Pp
|
||||||
.Bl -diag -compact
|
.Bl -diag -compact
|
||||||
.It "cannot mount root"
|
.It "cannot mount root"
|
||||||
This panic message results from a failure to mount the root filesystem
|
This panic message results from a failure to mount the root file system
|
||||||
during the bootstrap process.
|
during the bootstrap process.
|
||||||
Either the root filesystem has been corrupted,
|
Either the root file system has been corrupted,
|
||||||
or the system is attempting to use the wrong device as root filesystem.
|
or the system is attempting to use the wrong device as root file system.
|
||||||
Usually, an alternate copy of the system binary or an alternate root
|
Usually, an alternate copy of the system binary or an alternate root
|
||||||
filesystem can be used to bring up the system to investigate.
|
file system can be used to bring up the system to investigate.
|
||||||
Most often
|
Most often
|
||||||
this is done by the use of the boot floppy you used to install the system,
|
this is done by the use of the boot floppy you used to install the system,
|
||||||
and then using the
|
and then using the
|
||||||
@ -95,7 +95,7 @@ This is not a panic message, as reboots are likely to be futile.
|
|||||||
Late in the bootstrap procedure, the system was unable to locate
|
Late in the bootstrap procedure, the system was unable to locate
|
||||||
and execute the initialization process,
|
and execute the initialization process,
|
||||||
.Xr init 8 .
|
.Xr init 8 .
|
||||||
The root filesystem is incorrect or has been corrupted, or the mode
|
The root file system is incorrect or has been corrupted, or the mode
|
||||||
or type of
|
or type of
|
||||||
.Pa /sbin/init
|
.Pa /sbin/init
|
||||||
forbids execution or is totally missing.
|
forbids execution or is totally missing.
|
||||||
@ -108,11 +108,11 @@ forbids execution or is totally missing.
|
|||||||
.It "blkfree: freeing free frag"
|
.It "blkfree: freeing free frag"
|
||||||
.It "ifree: freeing free inode"
|
.It "ifree: freeing free inode"
|
||||||
These panic messages are among those that may be produced
|
These panic messages are among those that may be produced
|
||||||
when filesystem inconsistencies are detected.
|
when file system inconsistencies are detected.
|
||||||
The problem generally results from a failure to repair damaged filesystems
|
The problem generally results from a failure to repair damaged file systems
|
||||||
after a crash, hardware failures, or other condition that should not
|
after a crash, hardware failures, or other condition that should not
|
||||||
normally occur.
|
normally occur.
|
||||||
A filesystem check will normally correct the problem.
|
A file system check will normally correct the problem.
|
||||||
.Pp
|
.Pp
|
||||||
.It "timeout table full"
|
.It "timeout table full"
|
||||||
This really should not be a panic, but until the data structure
|
This really should not be a panic, but until the data structure
|
||||||
|
@ -38,7 +38,7 @@ The ability to boot a machine over the network is useful for
|
|||||||
or
|
or
|
||||||
.Em dataless
|
.Em dataless
|
||||||
machines, or as a temporary measure while repairing or
|
machines, or as a temporary measure while repairing or
|
||||||
re-installing filesystems on a local disk.
|
re-installing file systems on a local disk.
|
||||||
This file provides a general description of the interactions between
|
This file provides a general description of the interactions between
|
||||||
a client and its server when a client is booting over the network.
|
a client and its server when a client is booting over the network.
|
||||||
.Sh OPERATION
|
.Sh OPERATION
|
||||||
@ -80,7 +80,7 @@ loaded using TFTP or NFS.
|
|||||||
.Pp
|
.Pp
|
||||||
In phase 3, the kernel uses again DHCP or BOOTP to acquire
|
In phase 3, the kernel uses again DHCP or BOOTP to acquire
|
||||||
configuration information, and proceeds to mount the
|
configuration information, and proceeds to mount the
|
||||||
root filesystem and start operation.
|
root file system and start operation.
|
||||||
Some specific actions performed during the startup
|
Some specific actions performed during the startup
|
||||||
of a diskless system are listed in
|
of a diskless system are listed in
|
||||||
.Pa /etc/rc.diskless1
|
.Pa /etc/rc.diskless1
|
||||||
@ -155,7 +155,7 @@ The files and subdirectories within
|
|||||||
.Pa /conf/default/etc
|
.Pa /conf/default/etc
|
||||||
are used to bootstrap the diskless environment's
|
are used to bootstrap the diskless environment's
|
||||||
.Pa /etc
|
.Pa /etc
|
||||||
memory filesystem.
|
memory file system.
|
||||||
Be sure and copy the entirety of
|
Be sure and copy the entirety of
|
||||||
.Pa /etc ,
|
.Pa /etc ,
|
||||||
and not just overrides.
|
and not just overrides.
|
||||||
@ -208,7 +208,7 @@ local startup files will not be used.
|
|||||||
.Pp
|
.Pp
|
||||||
While an
|
While an
|
||||||
.Xr md 4 Ns -backed
|
.Xr md 4 Ns -backed
|
||||||
filesystem is mounted on
|
file system is mounted on
|
||||||
.Pa /var
|
.Pa /var
|
||||||
by the startup scripts,
|
by the startup scripts,
|
||||||
some sites may want to disable the saving of entropy by setting
|
some sites may want to disable the saving of entropy by setting
|
||||||
@ -248,7 +248,7 @@ This manpage is probably incomplete.
|
|||||||
sometimes requires to write onto
|
sometimes requires to write onto
|
||||||
the root partition, so the startup scripts create and mount
|
the root partition, so the startup scripts create and mount
|
||||||
.Xr md 4 Ns -backed
|
.Xr md 4 Ns -backed
|
||||||
filesystems on some locations (e.g.\&
|
file systems on some locations (e.g.\&
|
||||||
.Pa /etc
|
.Pa /etc
|
||||||
and
|
and
|
||||||
.Pa /var ) ,
|
.Pa /var ) ,
|
||||||
|
@ -41,9 +41,9 @@
|
|||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
This section contains information related to system operation
|
This section contains information related to system operation
|
||||||
and maintenance.
|
and maintenance.
|
||||||
It describes commands used to create new filesystems,
|
It describes commands used to create new file systems,
|
||||||
.Xr newfs 8 ,
|
.Xr newfs 8 ,
|
||||||
verify the integrity of the filesystems,
|
verify the integrity of the file systems,
|
||||||
.Xr fsck 8 ,
|
.Xr fsck 8 ,
|
||||||
control disk usage,
|
control disk usage,
|
||||||
.Xr edquota 8 ,
|
.Xr edquota 8 ,
|
||||||
|
@ -30,15 +30,15 @@ in the server, it can be extremely useful to developers to
|
|||||||
test their code without having to reinstall the system.
|
test their code without having to reinstall the system.
|
||||||
.Pp
|
.Pp
|
||||||
The boot media (typically a floppy disk) contains a boot loader and a
|
The boot media (typically a floppy disk) contains a boot loader and a
|
||||||
compressed kernel which includes a memory filesystem.
|
compressed kernel which includes a memory file system.
|
||||||
Depending on the media, it might also contain a number of
|
Depending on the media, it might also contain a number of
|
||||||
additional files, which can be updated at run time, and are
|
additional files, which can be updated at run time, and are
|
||||||
used to override/update those in the memory filesystem.
|
used to override/update those in the memory file system.
|
||||||
.Pp
|
.Pp
|
||||||
The system loads the kernel in the normal way, uncompresses
|
The system loads the kernel in the normal way, uncompresses
|
||||||
the memory filesystem and mounts it as root.
|
the memory file system and mounts it as root.
|
||||||
It then updates the memory
|
It then updates the memory
|
||||||
filesystem with files from the boot media (if present),
|
file system with files from the boot media (if present),
|
||||||
and executes a specialized version of
|
and executes a specialized version of
|
||||||
.Pa /etc/rc .
|
.Pa /etc/rc .
|
||||||
The boot media (floppy, etc.) is
|
The boot media (floppy, etc.) is
|
||||||
@ -96,8 +96,8 @@ commands to be executed and waiting for user
|
|||||||
input before executing each of them.
|
input before executing each of them.
|
||||||
Useful for debugging.
|
Useful for debugging.
|
||||||
.It Fl -all_in_mfs
|
.It Fl -all_in_mfs
|
||||||
Put the entire contents of the filesystem in the
|
Put the entire contents of the file system in the
|
||||||
memory filesystem image which is contained in the
|
memory file system image which is contained in the
|
||||||
kernel.
|
kernel.
|
||||||
This is the default behaviour, and is
|
This is the default behaviour, and is
|
||||||
extremely useful as the kernel itself can be loaded,
|
extremely useful as the kernel itself can be loaded,
|
||||||
@ -233,7 +233,7 @@ option:
|
|||||||
options MD_ROOT_SIZE=4200 # same as def_sz
|
options MD_ROOT_SIZE=4200 # same as def_sz
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
This informs the script of the size of the memory filesystem and
|
This informs the script of the size of the memory file system and
|
||||||
provides a few other details on how to build the image.
|
provides a few other details on how to build the image.
|
||||||
.It Pa crunch.conf
|
.It Pa crunch.conf
|
||||||
.Xr crunchgen 1
|
.Xr crunchgen 1
|
||||||
@ -317,7 +317,7 @@ because only the files that are actually loaded from the image
|
|||||||
contribute to the memory usage.
|
contribute to the memory usage.
|
||||||
.It Va import_files
|
.It Va import_files
|
||||||
Contains a list of files to be imported in the floppy tree.
|
Contains a list of files to be imported in the floppy tree.
|
||||||
Absolute names refer to the standard filesystem, relative
|
Absolute names refer to the standard file system, relative
|
||||||
names refer to the root of the source tree being used
|
names refer to the root of the source tree being used
|
||||||
(i.e.\&
|
(i.e.\&
|
||||||
.Va SRC_PATH/.. ) .
|
.Va SRC_PATH/.. ) .
|
||||||
@ -494,7 +494,7 @@ ethernet.
|
|||||||
.Pp
|
.Pp
|
||||||
After booting,
|
After booting,
|
||||||
.Nm
|
.Nm
|
||||||
loads the root filesystem from the memory filesystem, starts
|
loads the root file system from the memory file system, starts
|
||||||
.Pa /sbin/init ,
|
.Pa /sbin/init ,
|
||||||
and passes control to a first startup script,
|
and passes control to a first startup script,
|
||||||
.Pa /etc/rc .
|
.Pa /etc/rc .
|
||||||
@ -504,7 +504,7 @@ and
|
|||||||
.Pa /root
|
.Pa /root
|
||||||
directories with the default files, then tries to identify the boot
|
directories with the default files, then tries to identify the boot
|
||||||
device (floppy, hard disk partition) and possibly override the contents
|
device (floppy, hard disk partition) and possibly override the contents
|
||||||
of the root filesystem with files read from the boot device.
|
of the root file system with files read from the boot device.
|
||||||
This allows you to store local configuration on the same media.
|
This allows you to store local configuration on the same media.
|
||||||
After this phase the boot device is no longer used, unless the
|
After this phase the boot device is no longer used, unless the
|
||||||
user specifically does it.
|
user specifically does it.
|
||||||
|
@ -379,7 +379,7 @@ the script does not do anything.
|
|||||||
The
|
The
|
||||||
.Nm rc.early
|
.Nm rc.early
|
||||||
script is run very early in the startup process, immediately before the
|
script is run very early in the startup process, immediately before the
|
||||||
filesystem check.
|
file system check.
|
||||||
The
|
The
|
||||||
.Nm rc.early
|
.Nm rc.early
|
||||||
script is deprecated.
|
script is deprecated.
|
||||||
|
@ -33,11 +33,11 @@
|
|||||||
.Dt VFS 9
|
.Dt VFS 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS
|
.Nm VFS
|
||||||
.Nd kernel interface to filesystems
|
.Nd kernel interface to file systems
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
Calls used to set or query filesystems for settings or information.
|
Calls used to set or query file systems for settings or information.
|
||||||
.Pp
|
.Pp
|
||||||
Filesystems that don't implement a VFS operation should use the appropriate
|
File systems that don't implement a VFS operation should use the appropriate
|
||||||
.Fa vfs_std
|
.Fa vfs_std
|
||||||
function from
|
function from
|
||||||
.Pa src/sys/kern/vfs_default.c
|
.Pa src/sys/kern/vfs_default.c
|
||||||
|
@ -29,7 +29,7 @@
|
|||||||
.Dt VFS_CHECKEXP 9
|
.Dt VFS_CHECKEXP 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_CHECKEXP
|
.Nm VFS_CHECKEXP
|
||||||
.Nd check if a filesystem is exported to a client
|
.Nd check if a file system is exported to a client
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -51,21 +51,21 @@ Return parameter for the export flags for this client.
|
|||||||
Return parameter for the anonymous credentials for this client.
|
Return parameter for the anonymous credentials for this client.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
This should be called on a filesystem's mount structure to determine if it
|
This should be called on a file system's mount structure to determine if it
|
||||||
is exported to a client whose address is contained in
|
is exported to a client whose address is contained in
|
||||||
.Fa nam .
|
.Fa nam .
|
||||||
.Pp
|
.Pp
|
||||||
It is generally called before
|
It is generally called before
|
||||||
.Xr VFS_FHTOVP 9
|
.Xr VFS_FHTOVP 9
|
||||||
to validate that a client has access to the filesystem.
|
to validate that a client has access to the file system.
|
||||||
.Pp
|
.Pp
|
||||||
The filesystem should call
|
The file system should call
|
||||||
.Xr vfs_export_lookup 9
|
.Xr vfs_export_lookup 9
|
||||||
with the address of an appropriate
|
with the address of an appropriate
|
||||||
.Dv netexport
|
.Dv netexport
|
||||||
structure and the address of the client,
|
structure and the address of the client,
|
||||||
.Fa nam ,
|
.Fa nam ,
|
||||||
to verify that the client can access this filesystem.
|
to verify that the client can access this file system.
|
||||||
.Sh RETURN VALUES
|
.Sh RETURN VALUES
|
||||||
The export flags and anonymous credentials specific to the client (returned
|
The export flags and anonymous credentials specific to the client (returned
|
||||||
by
|
by
|
||||||
|
@ -46,19 +46,19 @@ This is used by the NFS server to turn an NFS filehandle into a vnode.
|
|||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width vpp
|
.Bl -tag -width vpp
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
The filesystem.
|
The file system.
|
||||||
.It Ar fhp
|
.It Ar fhp
|
||||||
The filehandle to convert.
|
The filehandle to convert.
|
||||||
.It Ar vpp
|
.It Ar vpp
|
||||||
Return parameter for the new locked vnode.
|
Return parameter for the new locked vnode.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
The contents of the filehandle are defined by the filesystem and are
|
The contents of the filehandle are defined by the file system and are
|
||||||
not examined by any other part of the system. It should contain
|
not examined by any other part of the system. It should contain
|
||||||
enough information to uniquely identify a file within the filesystem
|
enough information to uniquely identify a file within the file system
|
||||||
as well as noticing when a file has been removed and the filesystem
|
as well as noticing when a file has been removed and the file system
|
||||||
resources have been reused for a new file. For instance, UFS
|
resources have been reused for a new file. For instance, UFS
|
||||||
filesystem stores the inode number and inode generation counter in its
|
file system stores the inode number and inode generation counter in its
|
||||||
filehandle.
|
filehandle.
|
||||||
.Pp
|
.Pp
|
||||||
A call to this function should generally be preceded by a call to
|
A call to this function should generally be preceded by a call to
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_INIT 9
|
.Dt VFS_INIT 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_INIT
|
.Nm VFS_INIT
|
||||||
.Nd initialize a filesystem
|
.Nd initialize a file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -41,10 +41,10 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_INIT
|
.Fn VFS_INIT
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
This function is called once to allow a filesystem to initialize any
|
This function is called once to allow a file system to initialize any
|
||||||
global data structures that it might have. It is either called when
|
global data structures that it might have. It is either called when
|
||||||
the operating system boots or, for dynamically loaded filesystems,
|
the operating system boots or, for dynamically loaded file systems,
|
||||||
when the kernel module containing the filesystem is loaded.
|
when the kernel module containing the file system is loaded.
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr VFS 9 ,
|
.Xr VFS 9 ,
|
||||||
.Xr vnode 9
|
.Xr vnode 9
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_MOUNT 9
|
.Dt VFS_MOUNT 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_MOUNT
|
.Nm VFS_MOUNT
|
||||||
.Nd mount a filesystem
|
.Nd mount a file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -41,44 +41,44 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_MOUNT "struct mount *mp" "char *path" "caddr_t data" "struct nameidata *ndp" "struct thread *td"
|
.Fn VFS_MOUNT "struct mount *mp" "char *path" "caddr_t data" "struct nameidata *ndp" "struct thread *td"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
Mount a filesystem into the system's namespace.
|
Mount a file system into the system's namespace.
|
||||||
.Pp
|
.Pp
|
||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width data
|
.Bl -tag -width data
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
Structure representing the filesystem.
|
Structure representing the file system.
|
||||||
.It Ar path
|
.It Ar path
|
||||||
Pathname where the filesystem is being mounted.
|
Pathname where the file system is being mounted.
|
||||||
.It Ar data
|
.It Ar data
|
||||||
Filesystem specific data. This should be read into the kernel using
|
File system specific data. This should be read into the kernel using
|
||||||
.Xr copyin 9 .
|
.Xr copyin 9 .
|
||||||
.It Ar ndp
|
.It Ar ndp
|
||||||
Contains the result of a
|
Contains the result of a
|
||||||
.Xr namei 9
|
.Xr namei 9
|
||||||
call on the pathname of the mountpoint.
|
call on the pathname of the mountpoint.
|
||||||
.It Ar td
|
.It Ar td
|
||||||
Thread which is mounting the filesystem.
|
Thread which is mounting the file system.
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
This is called both to mount new filesystems and to change the
|
This is called both to mount new file systems and to change the
|
||||||
attributes of an existing filesystem. If the
|
attributes of an existing file system. If the
|
||||||
.Dv MNT_UPDATE
|
.Dv MNT_UPDATE
|
||||||
flag is set in
|
flag is set in
|
||||||
.Fa mp->mnt_flag
|
.Fa mp->mnt_flag
|
||||||
then the filesystem should update its internal state from the value of
|
then the file system should update its internal state from the value of
|
||||||
.Fa mp->mnt_flag .
|
.Fa mp->mnt_flag .
|
||||||
This can be used, for instance, to convert a read-only filesystem to
|
This can be used, for instance, to convert a read-only file system to
|
||||||
read-write.
|
read-write.
|
||||||
It is also used by
|
It is also used by
|
||||||
.Xr mountd 8
|
.Xr mountd 8
|
||||||
to update the NFS export information for the filesystem.
|
to update the NFS export information for the file system.
|
||||||
.Pp
|
.Pp
|
||||||
If the
|
If the
|
||||||
.Dv MNT_UPDATE
|
.Dv MNT_UPDATE
|
||||||
flag is not specified, then this is a newly mounted filesystem. The
|
flag is not specified, then this is a newly mounted file system. The
|
||||||
filesystem code should allocate and initialize
|
file system code should allocate and initialize
|
||||||
any private data needed to represent
|
any private data needed to represent
|
||||||
the filesystem (it can use the
|
the file system (it can use the
|
||||||
.Fa mp->mnt_data
|
.Fa mp->mnt_data
|
||||||
field to store this information).
|
field to store this information).
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_QUOTACTL 9
|
.Dt VFS_QUOTACTL 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_QUOTACTL
|
.Nm VFS_QUOTACTL
|
||||||
.Nd manipulate filesystem quotas
|
.Nd manipulate file system quotas
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -41,7 +41,7 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_QUOTACTL "struct mount *mp" "int cmds" "uid_t uid" "caddr_t arg" "struct thread *td"
|
.Fn VFS_QUOTACTL "struct mount *mp" "int cmds" "uid_t uid" "caddr_t arg" "struct thread *td"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
Implement filesystem quotas. See
|
Implement file system quotas. See
|
||||||
.Xr quotactl 2
|
.Xr quotactl 2
|
||||||
for a description of the arguments.
|
for a description of the arguments.
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_ROOT 9
|
.Dt VFS_ROOT 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_ROOT
|
.Nm VFS_ROOT
|
||||||
.Nd return the root vnode of a filesystem
|
.Nd return the root vnode of a file system
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -41,12 +41,12 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_ROOT "struct mount *mp" "struct vnode **vpp"
|
.Fn VFS_ROOT "struct mount *mp" "struct vnode **vpp"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
Return a locked vnode for the root directory of the filesystem.
|
Return a locked vnode for the root directory of the file system.
|
||||||
.Pp
|
.Pp
|
||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width vpp
|
.Bl -tag -width vpp
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
The filesystem.
|
The file system.
|
||||||
.It Ar vpp
|
.It Ar vpp
|
||||||
Return parameter for the root vnode.
|
Return parameter for the root vnode.
|
||||||
.El
|
.El
|
||||||
|
@ -31,7 +31,7 @@
|
|||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_SET
|
.Nm VFS_SET
|
||||||
.Nd set up loadable filesystem
|
.Nd set up loadable file system
|
||||||
.Vt vfsconf
|
.Vt vfsconf
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_START 9
|
.Dt VFS_START 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_START
|
.Nm VFS_START
|
||||||
.Nd make a filesystem operational
|
.Nd make a file system operational
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -43,15 +43,15 @@
|
|||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
This is called after
|
This is called after
|
||||||
.Xr VFS_MOUNT 9
|
.Xr VFS_MOUNT 9
|
||||||
and before the first access to the filesystem.
|
and before the first access to the file system.
|
||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width flags
|
.Bl -tag -width flags
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
The filesystem.
|
The file system.
|
||||||
.It Ar flags
|
.It Ar flags
|
||||||
??
|
??
|
||||||
.It Ar td
|
.It Ar td
|
||||||
Thread which is starting the filesystem.
|
Thread which is starting the file system.
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr VFS 9 ,
|
.Xr VFS 9 ,
|
||||||
|
@ -33,7 +33,7 @@
|
|||||||
.Dt VFS_STATFS 9
|
.Dt VFS_STATFS 9
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
.Nm VFS_STATFS
|
.Nm VFS_STATFS
|
||||||
.Nd return filesystem status
|
.Nd return file system status
|
||||||
.Sh SYNOPSIS
|
.Sh SYNOPSIS
|
||||||
.In sys/param.h
|
.In sys/param.h
|
||||||
.In sys/mount.h
|
.In sys/mount.h
|
||||||
@ -41,17 +41,17 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_STATFS "struct mount *mp" "struct statfs *sbp" "struct thread *td"
|
.Fn VFS_STATFS "struct mount *mp" "struct statfs *sbp" "struct thread *td"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
This call returns various pieces of information about the filesystem,
|
This call returns various pieces of information about the file system,
|
||||||
including recommended I/O sizes, free space, free inodes, etc.
|
including recommended I/O sizes, free space, free inodes, etc.
|
||||||
.Pp
|
.Pp
|
||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width sbp
|
.Bl -tag -width sbp
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
The filesystem.
|
The file system.
|
||||||
.It Ar sbp
|
.It Ar sbp
|
||||||
Return parameter for the filesystem's status.
|
Return parameter for the file system's status.
|
||||||
.It Ar td
|
.It Ar td
|
||||||
The thread which is querying the filesystem.
|
The thread which is querying the file system.
|
||||||
.El
|
.El
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr VFS 9 ,
|
.Xr VFS 9 ,
|
||||||
|
@ -41,12 +41,12 @@
|
|||||||
.Ft int
|
.Ft int
|
||||||
.Fn VFS_SYNC "struct mount *mp" "int waitfor" "struct ucred *cred" "struct thread *td"
|
.Fn VFS_SYNC "struct mount *mp" "int waitfor" "struct ucred *cred" "struct thread *td"
|
||||||
.Sh DESCRIPTION
|
.Sh DESCRIPTION
|
||||||
This writes out all unwritten data in a filesystem.
|
This writes out all unwritten data in a file system.
|
||||||
.Pp
|
.Pp
|
||||||
Its arguments are:
|
Its arguments are:
|
||||||
.Bl -tag -width waitfor
|
.Bl -tag -width waitfor
|
||||||
.It Ar mp
|
.It Ar mp
|
||||||
The filesystem.
|
The file system.
|
||||||
.It Ar waitfor
|
.It Ar waitfor
|
||||||
Whether the function should wait for I/O to complete.
|
Whether the function should wait for I/O to complete.
|
||||||
Possible values are:
|
Possible values are:
|
||||||
@ -56,7 +56,7 @@ synchronously wait for I/O to complete
|
|||||||
.It Dv MNT_NOWAIT
|
.It Dv MNT_NOWAIT
|
||||||
start all I/O, but do not wait for it
|
start all I/O, but do not wait for it
|
||||||
.It Dv MNT_LAZY
|
.It Dv MNT_LAZY
|
||||||
push data not written by filesystem syncer
|
push data not written by file system syncer
|
||||||
.El
|
.El
|
||||||
.It Ar cred
|
.It Ar cred
|
||||||
The caller's credentials.
|
The caller's credentials.
|
||||||
@ -66,7 +66,7 @@ The calling thread.
|
|||||||
.Pp
|
.Pp
|
||||||
This would normally call
|
This would normally call
|
||||||
.Xr VOP_FSYNC 9
|
.Xr VOP_FSYNC 9
|
||||||
for all the vnodes in the filesystem.
|
for all the vnodes in the file system.
|
||||||
.Sh SEE ALSO
|
.Sh SEE ALSO
|
||||||
.Xr fsync 2 ,
|
.Xr fsync 2 ,
|
||||||
.Xr sync 2 ,
|
.Xr sync 2 ,
|
||||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user