1 .\" Copyright (c) 2003,2004 The DragonFly Project. All rights reserved.
3 .\" This code is derived from software contributed to The DragonFly Project
4 .\" by Matthew Dillon <dillon@backplane.com>
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in
15 .\" the documentation and/or other materials provided with the
17 .\" 3. Neither the name of The DragonFly Project nor the names of its
18 .\" contributors may be used to endorse or promote products derived
19 .\" from this software without specific, prior written permission.
21 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
22 .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
23 .\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
24 .\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
25 .\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
26 .\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING,
27 .\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
28 .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
29 .\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
30 .\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
31 .\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" $DragonFly: src/sbin/mountctl/mountctl.8,v 1.3 2005/03/08 20:29:55 swildner Exp $
41 .Nd control journaling and other features on mounted file systems
45 .Op Ar tag/mountpt | mountpt:tag
48 .Op Fl w Ar output_path
51 .Op Fl o Ar option ...
55 .Op Ar tag/mountpt | mountpt:tag
59 .Op Fl o Ar option ...
60 .Op Ar tag/mountpt | mountpt:tag
63 .Op Ar tag/mountpt | mountpt:tag
68 utility manages journaling and (eventually) other features on a mounted
70 Note that a mount point path must begin with '/', and tag names must not
75 will list all installed journals in the system or on a particular mount point
76 or tag, including their current state of operation.
80 will add a new journal to a mount point. A mount may have any number of
81 journals associated with it. If no output path is specified the journal
82 will be written to the standard output. Options may be specified as
83 described in the OPTION KEYWORDS section.
84 The tag is required and must be unique
85 relative to any given mount, but you can use the same tag on multiple
86 mount points if you wish (and control them all together by referencing that
88 The output path may represent any streamable entity. You can, for example,
89 output to a pipe into a program which does further buffering or processing
92 A stalled journaling descriptor will stall the filesystem. Eventually a
93 kernel-implemented swap backing will be available for journals but that is
94 not the case at the moment.
98 will remove the specified journal(s). A mount point, a tag, or both may be
99 specified. This function will operate on all matching journals.
103 will modify the options associated with an existing journal. Options are
104 specified in the OPTION KEYWORDS section.
106 .Bl -tag -width indent
108 Flush a journal, equivalent to the 'flush' keyword.
112 Freeze a journal, equivalent to the 'freeze' keyword.
121 Start or restart a journal, equivalent to the 'start' keyword.
125 Close a journal, equivalent to the 'close' keyword.
129 Abort a journal, equivalent to the 'abort' keyword.
132 .It Fl w Ar output_path
133 Change a journal's stream descriptor to the specified path.
142 Change a journal's stream descriptor to the specified file descriptor number.
152 Options keywords may be comma delimited without whitespace within a single
156 options. Some keywords require a value which is specified as
158 Any option may be prefixed with 'no' or 'non' to turn off the option.
159 Some options are one-shot and have no 'no' or 'non' equivalent.
161 The options are as follows:
162 .Bl -tag -width indent
164 Generate a reversable journaling stream. This allows the target to run
165 the journal backwards as well as forwards to 'undo' operations. This is the
168 Indicate that the journaling stream is a two-way stream and that transaction
169 id acknowledgements will be returned.
170 .It Ar memfifo=size[k,m]
171 Specify the size of the in-kernel memory FIFO used to buffer the journaling
172 stream between processes doing filesystem operations and the worker thread
173 writing out the journal. Since the kernel has limited virtual memory
174 buffers larger then 4MB are not recommended.
175 .It Ar swapfifo=size[k,m,g]
176 Specify the size of the kernel-managed swap-backed FIFO used to buffer
179 Switch the journal's output stream to a new file. This feature is typically
180 used to restart a dead stream.
183 option is equivalent to specifying the path option. Both should not be
186 Switch the journal's output stream to a file descriptor specified by number.
187 Use file descriptor 1 if you wish to reopen the journal to the current
188 stdout. This feature is typically used to restart a dead stream (for example
189 if a TCP stream fails).
192 option is equivalent to specifying the path option. Both should not be
195 Freeze the worker thread. This may cause the filesystem to stall once
196 the memory fifo has filled up. A freeze point record will be written to
197 the journal. If used as part of the creation of a new journal via
199 this option will prevent any initial output to the journal and a freeze
200 point record will NOT be written. Again, the filesystem will stall if
201 the memory fifo fills up.
203 Start or restart the worker thread after a freeze.
205 Close the journal. Any transactions still under way will be allowed to
206 complete, a closing record will be generated, and the journaling descriptor
207 will be closed. If the connection is two-way the journal will away a final
208 acknowledgement of the closing record before closing the descriptor.
210 Close the journal. Any currently buffered data will be aborted. No close
211 record is written. The journaling stream is immediately closed.
213 Flush the journal. All currently buffered data is flushed. The command
214 does not return until the write suceeds and, if the connection is two-way,
215 and acknowledgement has been returned for journaled data buffered at the
216 time the flush was issued.
224 This utility is currently under construction and not all features have been
225 implemented yet. In fact, most have not.
229 utility first appeared in DragonFly .