1 .\" Copyright (c) 2000 Christoph Herrmann, Thomas-Henning von Kamptz
2 .\" Copyright (c) 1980, 1989, 1993 The Regents of the University of California.
3 .\" All rights reserved.
5 .\" This code is derived from software contributed to Berkeley by
6 .\" Christoph Herrmann and Thomas-Henning von Kamptz, Munich and Frankfurt.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" 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 the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgment:
18 .\" This product includes software developed by the University of
19 .\" California, Berkeley and its contributors, as well as Christoph
20 .\" Herrmann and Thomas-Henning von Kamptz.
21 .\" 4. Neither the name of the University nor the names of its contributors
22 .\" may be used to endorse or promote products derived from this software
23 .\" without specific prior written permission.
25 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
26 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
27 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
28 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
29 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
30 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
31 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
32 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
33 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
34 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
37 .\" $TSHeader: src/sbin/ffsinfo/ffsinfo.8,v 1.3 2000/12/12 19:30:55 tomsoft Exp $
38 .\" $FreeBSD: /repoman/r/ncvs/src/sbin/ffsinfo/ffsinfo.8,v 1.6.2.6 2004/01/29 15:48:26 cperciva Exp $
39 .\" $DragonFly: src/sbin/ffsinfo/ffsinfo.8,v 1.4 2004/07/08 17:59:01 cpressey Exp $
46 .Nd "dump all meta information of an existing ufs file system"
50 .Op Fl g Ar cylinder_group
62 The output is appended to the file
64 Also expect the output file to be rather large.
65 Up to 2 percent of the size of the specified file system is not uncommon.
67 The following options are available:
68 .Bl -tag -width indent
70 Specifying this option skips the tests of the disklabel.
71 This is done automatically, if the specified filename to dump is a plain file.
72 .It Fl g Ar cylinder_group
73 This restricts the dump to information about this cylinder group only.
76 means the first cylinder group and
80 This restricts the dump to information about this particular inode only.
81 Here the minimum acceptable inode is
83 If this option is omitted but a cylinder group is defined then only inodes
84 within that cylinder group are dumped.
86 The level of detail which will be dumped.
87 This value defaults to
91 of the following table:
93 .Bl -hang -width indent -compact
97 superblock copies in each cylinder group
99 cylinder group summary in initial cylinder group
101 cylinder group information
103 inode allocation bitmap
105 fragment allocation bitmap
107 cluster maps and summary
109 rotational layout tables
116 This allows to change the output filename where the dump is written to.
117 The current default is
118 .Pa /var/tmp/ffsinfo .
121 is provided, output will be sent to stdout.
124 .Dl ffsinfo -l 1023 /dev/vinum/testvol
127 .Pa /dev/vinum/testvol
128 with all available information.
132 can only dump unmounted file systems.
133 Do not try dumping a mounted file system, your system may panic and you will
134 not be able to use the file system any longer.
136 Also snapshots are handled like plain files.
137 They should get their own level to provide for independent control of the
138 amount of what gets dumped.
139 It probably also makes sense to some extend to dump the snapshot as a
150 .An Christoph Herrmann Aq chm@FreeBSD.org
151 .An Thomas-Henning von Kamptz Aq tomsoft@FreeBSD.org
152 .An The GROWFS team Aq growfs@Tomsoft.COM
156 utility first appeared in