2005-03-31 15:43:14 +04:00
|
|
|
.\" $NetBSD: mount_lfs.8,v 1.15 2005/03/31 11:43:14 wiz Exp $
|
1995-03-18 17:54:19 +03:00
|
|
|
.\"
|
1994-06-08 22:57:30 +04:00
|
|
|
.\" Copyright (c) 1993, 1994
|
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
|
.\"
|
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
|
.\" are met:
|
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
2003-08-07 14:04:22 +04:00
|
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
1994-06-08 22:57:30 +04:00
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
|
.\"
|
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
|
.\"
|
1994-06-14 02:50:46 +04:00
|
|
|
.\" @(#)mount_lfs.8 8.5 (Berkeley) 3/30/94
|
1994-06-08 22:57:30 +04:00
|
|
|
.\"
|
2005-03-31 07:07:38 +04:00
|
|
|
.Dd March 31, 2005
|
1994-06-08 22:57:30 +04:00
|
|
|
.Dt MOUNT_LFS 8
|
2001-06-05 15:22:41 +04:00
|
|
|
.Os
|
1994-06-08 22:57:30 +04:00
|
|
|
.Sh NAME
|
|
|
|
|
.Nm mount_lfs
|
|
|
|
|
.Nd mount a log-structured file system
|
|
|
|
|
.Sh SYNOPSIS
|
2003-02-25 13:34:36 +03:00
|
|
|
.Nm
|
2005-03-31 15:43:14 +04:00
|
|
|
.Op Fl bdins
|
Various bug-fixes to LFS, to wit:
Kernel:
* Add runtime quantity lfs_ravail, the number of disk-blocks reserved
for writing. Writes to the filesystem first reserve a maximum amount
of blocks before their write is allowed to proceed; after the blocks
are allocated the reserved total is reduced by a corresponding amount.
If the lfs_reserve function cannot immediately reserve the requested
number of blocks, the inode is unlocked, and the thread sleeps until
the cleaner has made enough space available for the blocks to be
reserved. In this way large files can be written to the filesystem
(or, smaller files can be written to a nearly-full but thoroughly
clean filesystem) and the cleaner can still function properly.
* Remove explicit switching on dlfs_minfreeseg from the kernel code; it
is now merely a fs-creation parameter used to compute dlfs_avail and
dlfs_bfree (and used by fsck_lfs(8) to check their accuracy). Its
former role is better assumed by a properly computed dlfs_avail.
* Bounds-check inode numbers submitted through lfs_bmapv and lfs_markv.
This prevents a panic, but, if the cleaner is feeding the filesystem
the wrong data, you are still in a world of hurt.
* Cleanup: remove explicit references of DEV_BSIZE in favor of
btodb()/dbtob().
lfs_cleanerd:
* Make -n mean "send N segments' blocks through a single call to
lfs_markv". Previously it had meant "clean N segments though N calls
to lfs_markv, before looking again to see if more need to be cleaned".
The new behavior gives better packing of direct data on disk with as
little metadata as possible, largely alleviating the problem that the
cleaner can consume more disk through inefficient use of metadata than
it frees by moving dirty data away from clean "holes" to produce
entirely clean segments.
* Make -b mean "read as many segments as necessary to write N segments
of dirty data back to disk", rather than its former meaning of "read
as many segments as necessary to free N segments worth of space". The
new meaning, combined with the new -n behavior described above,
further aids in cleaning storage efficiency as entire segments can be
written at once, using as few blocks as possible for segment summaries
and inode blocks.
* Make the cleaner take note of segments which could not be cleaned due
to error, and not attempt to clean them until they are entirely free
of dirty blocks. This prevents the case in which a cleanerd running
with -n 1 and without -b (formerly the default) would spin trying
repeatedly to clean a corrupt segment, while the remaining space
filled and deadlocked the filesystem.
* Update the lfs_cleanerd manual page to describe all the options,
including the changes mentioned here (in particular, the -b and -n
flags were previously undocumented).
fsck_lfs:
* Check, and optionally fix, lfs_avail (to an exact figure) and
lfs_bfree (within a margin of error) in pass 5.
newfs_lfs:
* Reduce the default dlfs_minfreeseg to 1/20 of the total segments.
* Add a warning if the sgs disklabel field is 16 (the default for FFS'
cpg, but not usually desirable for LFS' sgs: 5--8 is a better range).
* Change the calculation of lfs_avail and lfs_bfree, corresponding to
the kernel changes mentioned above.
mount_lfs:
* Add -N and -b options to pass corresponding -n and -b options to
lfs_cleanerd.
* Default to calling lfs_cleanerd with "-b -n 4".
[All of these changes were largely tested in the 1.5 branch, with the
idea that they (along with previous un-pulled-up work) could be applied
to the branch while it was still in ALPHA2; however my test system has
experienced corruption on another filesystem (/dev/console has gone
missing :^), and, while I believe this unrelated to the LFS changes, I
cannot with good conscience request that the changes be pulled up.]
2000-09-09 08:49:54 +04:00
|
|
|
.Op Fl N Ar nsegs
|
1994-06-08 22:57:30 +04:00
|
|
|
.Op Fl o Ar options
|
|
|
|
|
.Ar special
|
|
|
|
|
.Ar node
|
|
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
The
|
1997-09-15 08:47:17 +04:00
|
|
|
.Nm
|
1994-06-08 22:57:30 +04:00
|
|
|
command attaches a log-structured file system
|
|
|
|
|
.Ar special
|
|
|
|
|
device on to the file system tree at the point
|
|
|
|
|
.Ar node .
|
2005-01-31 08:19:18 +03:00
|
|
|
Both
|
|
|
|
|
.Ar special
|
|
|
|
|
and
|
|
|
|
|
.Ar node
|
|
|
|
|
are converted to absolute paths before use.
|
1994-06-08 22:57:30 +04:00
|
|
|
In addition, the
|
|
|
|
|
.Xr lfs_cleanerd 8
|
|
|
|
|
utility is invoked to clean the file system periodically.
|
|
|
|
|
.Pp
|
|
|
|
|
This command is normally executed by
|
|
|
|
|
.Xr mount 8
|
|
|
|
|
at boot time.
|
|
|
|
|
.Pp
|
|
|
|
|
The options are as follows:
|
|
|
|
|
.Bl -tag -width Ds
|
Various bug-fixes to LFS, to wit:
Kernel:
* Add runtime quantity lfs_ravail, the number of disk-blocks reserved
for writing. Writes to the filesystem first reserve a maximum amount
of blocks before their write is allowed to proceed; after the blocks
are allocated the reserved total is reduced by a corresponding amount.
If the lfs_reserve function cannot immediately reserve the requested
number of blocks, the inode is unlocked, and the thread sleeps until
the cleaner has made enough space available for the blocks to be
reserved. In this way large files can be written to the filesystem
(or, smaller files can be written to a nearly-full but thoroughly
clean filesystem) and the cleaner can still function properly.
* Remove explicit switching on dlfs_minfreeseg from the kernel code; it
is now merely a fs-creation parameter used to compute dlfs_avail and
dlfs_bfree (and used by fsck_lfs(8) to check their accuracy). Its
former role is better assumed by a properly computed dlfs_avail.
* Bounds-check inode numbers submitted through lfs_bmapv and lfs_markv.
This prevents a panic, but, if the cleaner is feeding the filesystem
the wrong data, you are still in a world of hurt.
* Cleanup: remove explicit references of DEV_BSIZE in favor of
btodb()/dbtob().
lfs_cleanerd:
* Make -n mean "send N segments' blocks through a single call to
lfs_markv". Previously it had meant "clean N segments though N calls
to lfs_markv, before looking again to see if more need to be cleaned".
The new behavior gives better packing of direct data on disk with as
little metadata as possible, largely alleviating the problem that the
cleaner can consume more disk through inefficient use of metadata than
it frees by moving dirty data away from clean "holes" to produce
entirely clean segments.
* Make -b mean "read as many segments as necessary to write N segments
of dirty data back to disk", rather than its former meaning of "read
as many segments as necessary to free N segments worth of space". The
new meaning, combined with the new -n behavior described above,
further aids in cleaning storage efficiency as entire segments can be
written at once, using as few blocks as possible for segment summaries
and inode blocks.
* Make the cleaner take note of segments which could not be cleaned due
to error, and not attempt to clean them until they are entirely free
of dirty blocks. This prevents the case in which a cleanerd running
with -n 1 and without -b (formerly the default) would spin trying
repeatedly to clean a corrupt segment, while the remaining space
filled and deadlocked the filesystem.
* Update the lfs_cleanerd manual page to describe all the options,
including the changes mentioned here (in particular, the -b and -n
flags were previously undocumented).
fsck_lfs:
* Check, and optionally fix, lfs_avail (to an exact figure) and
lfs_bfree (within a margin of error) in pass 5.
newfs_lfs:
* Reduce the default dlfs_minfreeseg to 1/20 of the total segments.
* Add a warning if the sgs disklabel field is 16 (the default for FFS'
cpg, but not usually desirable for LFS' sgs: 5--8 is a better range).
* Change the calculation of lfs_avail and lfs_bfree, corresponding to
the kernel changes mentioned above.
mount_lfs:
* Add -N and -b options to pass corresponding -n and -b options to
lfs_cleanerd.
* Default to calling lfs_cleanerd with "-b -n 4".
[All of these changes were largely tested in the 1.5 branch, with the
idea that they (along with previous un-pulled-up work) could be applied
to the branch while it was still in ALPHA2; however my test system has
experienced corruption on another filesystem (/dev/console has gone
missing :^), and, while I believe this unrelated to the LFS changes, I
cannot with good conscience request that the changes be pulled up.]
2000-09-09 08:49:54 +04:00
|
|
|
.It Fl b
|
|
|
|
|
Instruct the cleaner to count bytes written, rather than segments read,
|
|
|
|
|
to determine how many segments to clean at once.
|
1994-06-08 22:57:30 +04:00
|
|
|
.It Fl d
|
|
|
|
|
Run
|
|
|
|
|
.Xr lfs_cleanerd 8
|
|
|
|
|
in debug mode.
|
2005-03-31 07:07:38 +04:00
|
|
|
.It Fl i
|
|
|
|
|
Instruct the cleaner to use filesystem idle time as the criterion
|
|
|
|
|
for aggressive cleaning, instead of system load.
|
1994-06-08 22:57:30 +04:00
|
|
|
.It Fl o
|
|
|
|
|
Options are specified with a
|
|
|
|
|
.Fl o
|
|
|
|
|
flag followed by a comma separated string of options.
|
|
|
|
|
See the
|
|
|
|
|
.Xr mount 8
|
|
|
|
|
man page for possible options and their meanings.
|
Various bug-fixes to LFS, to wit:
Kernel:
* Add runtime quantity lfs_ravail, the number of disk-blocks reserved
for writing. Writes to the filesystem first reserve a maximum amount
of blocks before their write is allowed to proceed; after the blocks
are allocated the reserved total is reduced by a corresponding amount.
If the lfs_reserve function cannot immediately reserve the requested
number of blocks, the inode is unlocked, and the thread sleeps until
the cleaner has made enough space available for the blocks to be
reserved. In this way large files can be written to the filesystem
(or, smaller files can be written to a nearly-full but thoroughly
clean filesystem) and the cleaner can still function properly.
* Remove explicit switching on dlfs_minfreeseg from the kernel code; it
is now merely a fs-creation parameter used to compute dlfs_avail and
dlfs_bfree (and used by fsck_lfs(8) to check their accuracy). Its
former role is better assumed by a properly computed dlfs_avail.
* Bounds-check inode numbers submitted through lfs_bmapv and lfs_markv.
This prevents a panic, but, if the cleaner is feeding the filesystem
the wrong data, you are still in a world of hurt.
* Cleanup: remove explicit references of DEV_BSIZE in favor of
btodb()/dbtob().
lfs_cleanerd:
* Make -n mean "send N segments' blocks through a single call to
lfs_markv". Previously it had meant "clean N segments though N calls
to lfs_markv, before looking again to see if more need to be cleaned".
The new behavior gives better packing of direct data on disk with as
little metadata as possible, largely alleviating the problem that the
cleaner can consume more disk through inefficient use of metadata than
it frees by moving dirty data away from clean "holes" to produce
entirely clean segments.
* Make -b mean "read as many segments as necessary to write N segments
of dirty data back to disk", rather than its former meaning of "read
as many segments as necessary to free N segments worth of space". The
new meaning, combined with the new -n behavior described above,
further aids in cleaning storage efficiency as entire segments can be
written at once, using as few blocks as possible for segment summaries
and inode blocks.
* Make the cleaner take note of segments which could not be cleaned due
to error, and not attempt to clean them until they are entirely free
of dirty blocks. This prevents the case in which a cleanerd running
with -n 1 and without -b (formerly the default) would spin trying
repeatedly to clean a corrupt segment, while the remaining space
filled and deadlocked the filesystem.
* Update the lfs_cleanerd manual page to describe all the options,
including the changes mentioned here (in particular, the -b and -n
flags were previously undocumented).
fsck_lfs:
* Check, and optionally fix, lfs_avail (to an exact figure) and
lfs_bfree (within a margin of error) in pass 5.
newfs_lfs:
* Reduce the default dlfs_minfreeseg to 1/20 of the total segments.
* Add a warning if the sgs disklabel field is 16 (the default for FFS'
cpg, but not usually desirable for LFS' sgs: 5--8 is a better range).
* Change the calculation of lfs_avail and lfs_bfree, corresponding to
the kernel changes mentioned above.
mount_lfs:
* Add -N and -b options to pass corresponding -n and -b options to
lfs_cleanerd.
* Default to calling lfs_cleanerd with "-b -n 4".
[All of these changes were largely tested in the 1.5 branch, with the
idea that they (along with previous un-pulled-up work) could be applied
to the branch while it was still in ALPHA2; however my test system has
experienced corruption on another filesystem (/dev/console has gone
missing :^), and, while I believe this unrelated to the LFS changes, I
cannot with good conscience request that the changes be pulled up.]
2000-09-09 08:49:54 +04:00
|
|
|
.It Fl N Ar nsegs
|
|
|
|
|
Clean
|
|
|
|
|
.Ar nsegs
|
|
|
|
|
segments (or bytes' worth of segments if
|
|
|
|
|
.Fl b
|
|
|
|
|
is also specified) at a time.
|
1994-06-08 22:57:30 +04:00
|
|
|
.It Fl n
|
|
|
|
|
Don't start
|
|
|
|
|
.Xr lfs_cleanerd 8
|
|
|
|
|
on the file system.
|
|
|
|
|
.It Fl s
|
|
|
|
|
Cause
|
|
|
|
|
.Xr lfs_cleanerd 8
|
|
|
|
|
to read data in small chunks when cleaning the file system.
|
|
|
|
|
.El
|
|
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr mount 2 ,
|
|
|
|
|
.Xr unmount 2 ,
|
|
|
|
|
.Xr fstab 5 ,
|
2000-11-08 22:40:04 +03:00
|
|
|
.Xr dump_lfs 8 ,
|
1994-06-08 22:57:30 +04:00
|
|
|
.Xr lfs_cleanerd 8 ,
|
2000-11-08 22:40:04 +03:00
|
|
|
.Xr mount 8 ,
|
|
|
|
|
.Xr newfs_lfs 8
|
1994-06-08 22:57:30 +04:00
|
|
|
.Rs
|
|
|
|
|
.%A Ousterhout and Douglis
|
|
|
|
|
.%D 1989
|
|
|
|
|
.%T "Beating the I/O Bottleneck: A Case for Log-structured File Systems"
|
|
|
|
|
.%J "Operating Systems Review"
|
|
|
|
|
.%V Vol. 23
|
|
|
|
|
.%N No. 1
|
|
|
|
|
.%P pp. 11-27
|
|
|
|
|
.%O "also available as Technical Report UCB/CSD 88/467"
|
|
|
|
|
.Re
|
|
|
|
|
.Rs
|
|
|
|
|
.%A Rosenblum and Ousterhout
|
|
|
|
|
.%D 1991
|
|
|
|
|
.%T "The Design and Implementation of a Log-Structured File System"
|
|
|
|
|
.%J "ACM SIGOPS Operating Systems Review"
|
|
|
|
|
.%V Vol. 25
|
|
|
|
|
.%N No. 5
|
|
|
|
|
.Re
|
|
|
|
|
.Rs
|
|
|
|
|
.%A Seltzer
|
|
|
|
|
.%D 1992
|
|
|
|
|
.%T "File System Performance and Transaction Support"
|
|
|
|
|
.%B "PhD Thesis, University of California, Berkeley"
|
|
|
|
|
.%O "also available as Technical Report UCB/ERL M92"
|
|
|
|
|
.Re
|
|
|
|
|
.Rs
|
|
|
|
|
.%A Seltzer, Bostic, McKusick and Staelin
|
|
|
|
|
.%D 1993
|
|
|
|
|
.%T "An Implementation of a Log-Structured File System for UNIX"
|
|
|
|
|
.%J "Proc. of the Winter 1993 USENIX Conf."
|
|
|
|
|
.%P pp. 315-331
|
|
|
|
|
.Re
|
|
|
|
|
.Sh HISTORY
|
|
|
|
|
The
|
1997-09-15 08:47:17 +04:00
|
|
|
.Nm
|
1998-02-06 08:54:12 +03:00
|
|
|
function first appeared in
|
|
|
|
|
.Bx 4.4 .
|