1994-05-26 06:35:07 +00:00
|
|
|
/*
|
2017-11-20 19:49:47 +00:00
|
|
|
* SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
|
*
|
2009-01-28 09:33:00 +00:00
|
|
|
* Copyright (c) 2009 Robert N. M. Watson
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* This software was developed at the University of Cambridge Computer
|
|
|
|
|
* Laboratory with support from a grant from Google, Inc.
|
|
|
|
|
*
|
2002-06-21 06:18:05 +00:00
|
|
|
* Copyright (c) 2002 Networks Associates Technology, Inc.
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* This software was developed for the FreeBSD Project by Marshall
|
|
|
|
|
* Kirk McKusick and Network Associates Laboratories, the Security
|
|
|
|
|
* Research Division of Network Associates, Inc. under DARPA/SPAWAR
|
|
|
|
|
* contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA CHATS
|
2003-02-14 21:08:14 +00:00
|
|
|
* research program.
|
2002-06-21 06:18:05 +00:00
|
|
|
*
|
1994-05-26 06:35:07 +00:00
|
|
|
* Copyright (c) 1983, 1992, 1993
|
|
|
|
|
* 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.
|
2017-02-28 23:42:47 +00:00
|
|
|
* 3. Neither the name of the University nor the names of its contributors
|
1994-05-26 06:35:07 +00: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.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef lint
|
1998-06-15 07:00:01 +00:00
|
|
|
static const char copyright[] =
|
1994-05-26 06:35:07 +00:00
|
|
|
"@(#) Copyright (c) 1983, 1992, 1993\n\
|
|
|
|
|
The Regents of the University of California. All rights reserved.\n";
|
|
|
|
|
#endif /* not lint */
|
|
|
|
|
|
|
|
|
|
#ifndef lint
|
1998-06-15 07:00:01 +00:00
|
|
|
#if 0
|
1997-03-11 12:12:26 +00:00
|
|
|
static char sccsid[] = "@(#)dumpfs.c 8.5 (Berkeley) 4/29/95";
|
1998-06-15 07:00:01 +00:00
|
|
|
#endif
|
|
|
|
|
static const char rcsid[] =
|
1999-08-28 00:22:10 +00:00
|
|
|
"$FreeBSD$";
|
1994-05-26 06:35:07 +00:00
|
|
|
#endif /* not lint */
|
|
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
|
#include <sys/time.h>
|
2002-05-12 21:37:08 +00:00
|
|
|
#include <sys/disklabel.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2002-06-21 06:18:05 +00:00
|
|
|
#include <ufs/ufs/dinode.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <ufs/ffs/fs.h>
|
|
|
|
|
|
1997-03-11 12:12:26 +00:00
|
|
|
#include <err.h>
|
2002-10-22 19:55:44 +00:00
|
|
|
#include <errno.h>
|
1997-03-11 12:12:26 +00:00
|
|
|
#include <fcntl.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <fstab.h>
|
2002-07-11 21:44:03 +00:00
|
|
|
#include <libufs.h>
|
2011-07-14 17:43:23 +00:00
|
|
|
#include <paths.h>
|
2003-01-19 10:25:11 +00:00
|
|
|
#include <stdint.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <stdio.h>
|
|
|
|
|
#include <stdlib.h>
|
1997-03-11 12:12:26 +00:00
|
|
|
#include <unistd.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2002-07-11 21:44:03 +00:00
|
|
|
#define afs disk.d_fs
|
2003-01-19 01:31:49 +00:00
|
|
|
#define acg disk.d_cg
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2011-11-04 13:36:02 +00:00
|
|
|
static struct uufsd disk;
|
2002-06-21 06:18:05 +00:00
|
|
|
|
2021-07-02 14:18:17 -08:00
|
|
|
static int dumpfs(const char *, int);
|
2011-12-13 09:01:44 +00:00
|
|
|
static int dumpfsid(void);
|
|
|
|
|
static int dumpcg(void);
|
|
|
|
|
static int dumpfreespace(const char *, int);
|
|
|
|
|
static void dumpfreespacecg(int);
|
|
|
|
|
static int marshal(const char *);
|
|
|
|
|
static void pbits(void *, int);
|
|
|
|
|
static void pblklist(void *, int, off_t, int);
|
|
|
|
|
static void ufserr(const char *);
|
|
|
|
|
static void usage(void) __dead2;
|
1994-05-26 06:35:07 +00:00
|
|
|
|
|
|
|
|
int
|
2002-03-20 22:57:10 +00:00
|
|
|
main(int argc, char *argv[])
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2003-01-19 10:25:11 +00:00
|
|
|
const char *name;
|
2021-07-02 14:18:17 -08:00
|
|
|
int ch, dofreespace, domarshal, dolabel, dosb, eval;
|
2003-01-19 01:02:25 +00:00
|
|
|
|
2021-07-02 14:18:17 -08:00
|
|
|
dofreespace = domarshal = dolabel = dosb = eval = 0;
|
2003-01-19 01:02:25 +00:00
|
|
|
|
2021-07-02 14:18:17 -08:00
|
|
|
while ((ch = getopt(argc, argv, "lfms")) != -1) {
|
2003-01-19 10:25:11 +00:00
|
|
|
switch (ch) {
|
2009-01-28 09:33:00 +00:00
|
|
|
case 'f':
|
|
|
|
|
dofreespace++;
|
|
|
|
|
break;
|
2003-01-19 10:25:11 +00:00
|
|
|
case 'm':
|
|
|
|
|
domarshal = 1;
|
|
|
|
|
break;
|
2011-07-14 08:06:03 +00:00
|
|
|
case 'l':
|
|
|
|
|
dolabel = 1;
|
|
|
|
|
break;
|
2021-07-02 14:18:17 -08:00
|
|
|
case 's':
|
|
|
|
|
dosb = 1;
|
|
|
|
|
break;
|
2003-01-19 10:25:11 +00:00
|
|
|
case '?':
|
|
|
|
|
default:
|
|
|
|
|
usage();
|
|
|
|
|
}
|
|
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
argc -= optind;
|
|
|
|
|
argv += optind;
|
|
|
|
|
|
|
|
|
|
if (argc < 1)
|
|
|
|
|
usage();
|
2009-01-28 09:33:00 +00:00
|
|
|
if (dofreespace && domarshal)
|
|
|
|
|
usage();
|
|
|
|
|
if (dofreespace > 2)
|
|
|
|
|
usage();
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2003-01-19 10:25:11 +00:00
|
|
|
while ((name = *argv++) != NULL) {
|
Move the ability to search for alternate UFS superblocks from fsck_ffs(8)
into ffs_sbsearch() to allow use by other parts of the system.
Historically only fsck_ffs(8), the UFS filesystem checker, had code
to track down and use alternate UFS superblocks. Since fsdb(8) used
much of the fsck_ffs(8) implementation it had some ability to track
down alternate superblocks.
This change extracts the code to track down alternate superblocks
from fsck_ffs(8) and puts it into a new function ffs_sbsearch() in
sys/ufs/ffs/ffs_subr.c. Like ffs_sbget() and ffs_sbput() also found
in ffs_subr.c, these functions can be used directly by the kernel
subsystems. Additionally they are exported to the UFS library,
libufs(8) so that they can be used by user-level programs. The new
functions added to libufs(8) are sbfind(3) that is an alternative
to sbread(3) and sbsearch(3) that is an alternative to sbget(3).
See their manual pages for further details.
The utilities that have been changed to search for superblocks are
dumpfs(8), fsdb(8), ffsinfo(8), and fsck_ffs(8). Also, the prtblknos(8)
tool found in tools/diag/prtblknos searches for superblocks.
The UFS specific mount code uses the superblock search interface
when mounting the root filesystem and when the administrator doing
a mount(8) command specifies the force flag (-f). The standalone UFS
boot code (found in stand/libsa/ufs.c) uses the superblock search
code in the hope of being able to get the system up and running so
that fsck_ffs(8) can be used to get the filesystem cleaned up.
The following utilities have not been changed to search for
superblocks: clri(8), tunefs(8), snapinfo(8), fstyp(8), quot(8),
dump(8), fsirand(8), growfs(8), quotacheck(8), gjournal(8), and
glabel(8). When these utilities fail, they do report the cause of
the failure. The one exception is the tasting code used to try and
figure what a given disk contains. The tasting code will remain
silent so as not to put out a slew of messages as it trying to taste
every new mass storage device that shows up.
Reviewed by: kib
Reviewed by: Warner Losh
Tested by: Peter Holm
Differential Revision: https://reviews.freebsd.org/D36053
Sponsored by: The FreeBSD Foundation
2022-08-13 12:41:53 -07:00
|
|
|
if (ufs_disk_fillout_blank(&disk, name) == -1 ||
|
|
|
|
|
sbfind(&disk, 0) == -1) {
|
2003-01-19 10:25:11 +00:00
|
|
|
ufserr(name);
|
|
|
|
|
eval |= 1;
|
|
|
|
|
continue;
|
|
|
|
|
}
|
2009-01-28 09:33:00 +00:00
|
|
|
if (dofreespace)
|
|
|
|
|
eval |= dumpfreespace(name, dofreespace);
|
|
|
|
|
else if (domarshal)
|
2003-01-19 10:25:11 +00:00
|
|
|
eval |= marshal(name);
|
2011-07-14 08:06:03 +00:00
|
|
|
else if (dolabel)
|
|
|
|
|
eval |= dumpfsid();
|
2003-01-19 10:25:11 +00:00
|
|
|
else
|
2021-07-02 14:18:17 -08:00
|
|
|
eval |= dumpfs(name, dosb);
|
2003-01-19 10:25:11 +00:00
|
|
|
ufs_disk_close(&disk);
|
|
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
exit(eval);
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static int
|
2011-07-14 08:06:03 +00:00
|
|
|
dumpfsid(void)
|
|
|
|
|
{
|
|
|
|
|
|
2011-07-14 17:43:23 +00:00
|
|
|
printf("%sufsid/%08x%08x\n", _PATH_DEV, afs.fs_id[0], afs.fs_id[1]);
|
2011-07-14 08:06:03 +00:00
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static int
|
2021-07-02 14:18:17 -08:00
|
|
|
dumpfs(const char *name, int dosb)
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2020-05-02 00:10:25 +00:00
|
|
|
time_t fstime, fsmtime;
|
2002-06-21 06:18:05 +00:00
|
|
|
int64_t fssize;
|
2003-01-24 00:07:40 +00:00
|
|
|
int32_t fsflags;
|
2002-07-11 21:46:12 +00:00
|
|
|
int i;
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2002-08-11 15:38:51 +00:00
|
|
|
switch (disk.d_ufs) {
|
|
|
|
|
case 2:
|
2002-06-21 06:18:05 +00:00
|
|
|
fssize = afs.fs_size;
|
2003-01-19 12:13:47 +00:00
|
|
|
fstime = afs.fs_time;
|
2020-05-02 00:10:25 +00:00
|
|
|
fsmtime = afs.fs_mtime;
|
|
|
|
|
printf("magic\t%x (UFS2)\n", afs.fs_magic);
|
|
|
|
|
printf("last mounted time\t%s", ctime(&fsmtime));
|
|
|
|
|
printf("last modified time\t%s", ctime(&fstime));
|
2015-05-26 18:27:38 +00:00
|
|
|
printf("superblock location\t%jd\tid\t[ %08x %08x ]\n",
|
2003-11-14 13:13:23 +00:00
|
|
|
(intmax_t)afs.fs_sblockloc, afs.fs_id[0], afs.fs_id[1]);
|
|
|
|
|
printf("ncg\t%d\tsize\t%jd\tblocks\t%jd\n",
|
|
|
|
|
afs.fs_ncg, (intmax_t)fssize, (intmax_t)afs.fs_dsize);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
case 1:
|
2002-06-21 06:18:05 +00:00
|
|
|
fssize = afs.fs_old_size;
|
2003-01-19 12:13:47 +00:00
|
|
|
fstime = afs.fs_old_time;
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("magic\t%x (UFS1)\ttime\t%s",
|
2003-01-19 12:13:47 +00:00
|
|
|
afs.fs_magic, ctime(&fstime));
|
2010-01-06 14:01:28 +00:00
|
|
|
printf("id\t[ %08x %08x ]\n", afs.fs_id[0], afs.fs_id[1]);
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("ncg\t%d\tsize\t%jd\tblocks\t%jd\n",
|
|
|
|
|
afs.fs_ncg, (intmax_t)fssize, (intmax_t)afs.fs_dsize);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
default:
|
2003-01-19 12:13:47 +00:00
|
|
|
goto err;
|
2002-06-21 06:18:05 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
printf("bsize\t%d\tshift\t%d\tmask\t0x%08x\n",
|
|
|
|
|
afs.fs_bsize, afs.fs_bshift, afs.fs_bmask);
|
|
|
|
|
printf("fsize\t%d\tshift\t%d\tmask\t0x%08x\n",
|
|
|
|
|
afs.fs_fsize, afs.fs_fshift, afs.fs_fmask);
|
|
|
|
|
printf("frag\t%d\tshift\t%d\tfsbtodb\t%d\n",
|
|
|
|
|
afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb);
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("minfree\t%d%%\toptim\t%s\tsymlinklen %d\n",
|
1994-05-26 06:35:07 +00:00
|
|
|
afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time",
|
2002-06-21 06:18:05 +00:00
|
|
|
afs.fs_maxsymlinklen);
|
2002-08-11 15:38:51 +00:00
|
|
|
switch (disk.d_ufs) {
|
|
|
|
|
case 2:
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("%s %d\tmaxbpg\t%d\tmaxcontig %d\tcontigsumsize %d\n",
|
|
|
|
|
"maxbsize", afs.fs_maxbsize, afs.fs_maxbpg,
|
|
|
|
|
afs.fs_maxcontig, afs.fs_contigsumsize);
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("nbfree\t%jd\tndir\t%jd\tnifree\t%jd\tnffree\t%jd\n",
|
2013-05-16 19:39:11 +00:00
|
|
|
(intmax_t)afs.fs_cstotal.cs_nbfree,
|
2003-11-14 13:13:23 +00:00
|
|
|
(intmax_t)afs.fs_cstotal.cs_ndir,
|
2013-05-16 19:39:11 +00:00
|
|
|
(intmax_t)afs.fs_cstotal.cs_nifree,
|
2003-11-14 13:13:23 +00:00
|
|
|
(intmax_t)afs.fs_cstotal.cs_nffree);
|
2006-10-31 22:02:24 +00:00
|
|
|
printf("bpg\t%d\tfpg\t%d\tipg\t%d\tunrefs\t%jd\n",
|
|
|
|
|
afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg,
|
|
|
|
|
(intmax_t)afs.fs_unrefs);
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("nindir\t%d\tinopb\t%d\tmaxfilesize\t%ju\n",
|
2013-05-16 19:39:11 +00:00
|
|
|
afs.fs_nindir, afs.fs_inopb,
|
2003-11-14 13:13:23 +00:00
|
|
|
(uintmax_t)afs.fs_maxfilesize);
|
2003-01-19 12:13:47 +00:00
|
|
|
printf("sbsize\t%d\tcgsize\t%d\tcsaddr\t%jd\tcssize\t%d\n",
|
|
|
|
|
afs.fs_sbsize, afs.fs_cgsize, (intmax_t)afs.fs_csaddr,
|
|
|
|
|
afs.fs_cssize);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
case 1:
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("maxbpg\t%d\tmaxcontig %d\tcontigsumsize %d\n",
|
|
|
|
|
afs.fs_maxbpg, afs.fs_maxcontig, afs.fs_contigsumsize);
|
|
|
|
|
printf("nbfree\t%d\tndir\t%d\tnifree\t%d\tnffree\t%d\n",
|
|
|
|
|
afs.fs_old_cstotal.cs_nbfree, afs.fs_old_cstotal.cs_ndir,
|
|
|
|
|
afs.fs_old_cstotal.cs_nifree, afs.fs_old_cstotal.cs_nffree);
|
|
|
|
|
printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n",
|
|
|
|
|
afs.fs_old_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg,
|
|
|
|
|
afs.fs_ipg);
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("nindir\t%d\tinopb\t%d\tnspf\t%d\tmaxfilesize\t%ju\n",
|
2002-06-21 06:18:05 +00:00
|
|
|
afs.fs_nindir, afs.fs_inopb, afs.fs_old_nspf,
|
2003-11-14 13:13:23 +00:00
|
|
|
(uintmax_t)afs.fs_maxfilesize);
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("sbsize\t%d\tcgsize\t%d\tcgoffset %d\tcgmask\t0x%08x\n",
|
|
|
|
|
afs.fs_sbsize, afs.fs_cgsize, afs.fs_old_cgoffset,
|
|
|
|
|
afs.fs_old_cgmask);
|
2022-07-24 17:33:19 -07:00
|
|
|
printf("csaddr\t%jd\tcssize\t%d\n",
|
|
|
|
|
(intmax_t)afs.fs_csaddr, afs.fs_cssize);
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("rotdelay %dms\trps\t%d\ttrackskew %d\tinterleave %d\n",
|
|
|
|
|
afs.fs_old_rotdelay, afs.fs_old_rps, afs.fs_old_trackskew,
|
|
|
|
|
afs.fs_old_interleave);
|
|
|
|
|
printf("nsect\t%d\tnpsect\t%d\tspc\t%d\n",
|
|
|
|
|
afs.fs_old_nsect, afs.fs_old_npsect, afs.fs_old_spc);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
default:
|
2003-01-19 12:13:47 +00:00
|
|
|
goto err;
|
2002-06-21 06:18:05 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
printf("sblkno\t%d\tcblkno\t%d\tiblkno\t%d\tdblkno\t%d\n",
|
|
|
|
|
afs.fs_sblkno, afs.fs_cblkno, afs.fs_iblkno, afs.fs_dblkno);
|
1994-08-20 16:57:45 +00:00
|
|
|
printf("cgrotor\t%d\tfmod\t%d\tronly\t%d\tclean\t%d\n",
|
|
|
|
|
afs.fs_cgrotor, afs.fs_fmod, afs.fs_ronly, afs.fs_clean);
|
2013-03-22 21:45:28 +00:00
|
|
|
printf("metaspace %jd\tavgfpdir %d\tavgfilesize %d\n",
|
|
|
|
|
afs.fs_metaspace, afs.fs_avgfpdir, afs.fs_avgfilesize);
|
1999-07-18 02:33:05 +00:00
|
|
|
printf("flags\t");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (afs.fs_old_flags & FS_FLAGS_UPDATED)
|
|
|
|
|
fsflags = afs.fs_flags;
|
|
|
|
|
else
|
|
|
|
|
fsflags = afs.fs_old_flags;
|
|
|
|
|
if (fsflags == 0)
|
1999-07-18 02:33:05 +00:00
|
|
|
printf("none");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags & FS_UNCLEAN)
|
|
|
|
|
printf("unclean ");
|
|
|
|
|
if (fsflags & FS_DOSOFTDEP)
|
2010-04-24 07:05:35 +00:00
|
|
|
printf("soft-updates%s ", (fsflags & FS_SUJ) ? "+journal" : "");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags & FS_NEEDSFSCK)
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
printf("needs-fsck-run ");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags & FS_INDEXDIRS)
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
printf("indexed-directories ");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags & FS_ACLS)
|
|
|
|
|
printf("acls ");
|
|
|
|
|
if (fsflags & FS_MULTILABEL)
|
|
|
|
|
printf("multilabel ");
|
2006-10-31 22:02:24 +00:00
|
|
|
if (fsflags & FS_GJOURNAL)
|
|
|
|
|
printf("gjournal ");
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags & FS_FLAGS_UPDATED)
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
printf("fs_flags-expanded ");
|
2009-12-21 19:39:10 +00:00
|
|
|
if (fsflags & FS_NFS4ACLS)
|
|
|
|
|
printf("nfsv4acls ");
|
2010-12-29 12:31:18 +00:00
|
|
|
if (fsflags & FS_TRIM)
|
|
|
|
|
printf("trim ");
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
fsflags &= ~(FS_UNCLEAN | FS_DOSOFTDEP | FS_NEEDSFSCK | FS_METACKHASH |
|
2009-12-21 19:39:10 +00:00
|
|
|
FS_ACLS | FS_MULTILABEL | FS_GJOURNAL | FS_FLAGS_UPDATED |
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
FS_NFS4ACLS | FS_SUJ | FS_TRIM | FS_INDEXDIRS);
|
2003-01-24 00:07:40 +00:00
|
|
|
if (fsflags != 0)
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
printf("unknown-flags (%#x)", fsflags);
|
1999-07-18 02:33:05 +00:00
|
|
|
putchar('\n');
|
The goal of this change is to prevent accidental foot shooting by
folks running filesystems created on check-hash enabled kernels
(which I will call "new") on a non-check-hash enabled kernels (which
I will call "old). The idea here is to detect when a filesystem is
run on an old kernel and flag the filesystem so that when it gets
moved back to a new kernel, it will not start getting a slew of
check-hash errors.
Back when the UFS version 2 filesystem was created, it added a file
flag FS_INDEXDIRS that was to be set on any filesystem that kept
some sort of on-disk indexing for directories. The idea was precisely
to solve the issue we have today. Specifically that a newer kernel
that supported indexing would be able to tell that the filesystem
had been run on an older non-indexing kernel and that the indexes
should not be used until they had been rebuilt. Since we have never
implemented on-disk directory indicies, the FS_INDEXDIRS flag is
cleared every time any UFS version 2 filesystem ever created is
mounted for writing.
This commit repurposes the FS_INDEXDIRS flag as the FS_METACKHASH
flag. Thus, the FS_METACKHASH is definitively known to have always
been cleared. The FS_INDEXDIRS flag has been moved to a new block
of flags that will always be cleared starting with this commit
(until they get used to implement some future feature which needs
to detect that the filesystem was mounted on a kernel that predates
the new feature).
If a filesystem with check-hashes enabled is mounted on an old
kernel the FS_METACKHASH flag is cleared. When that filesystem is
mounted on a new kernel it will see that the FS_METACKHASH has been
cleared and clears all of the fs_metackhash flags. To get them
re-enabled the user must run fsck (in interactive mode without the
-y flag) which will ask for each supported check hash whether it
should be rebuilt and enabled. When fsck is run in its default preen
mode, it will just ignore the check hashes so they will remain
disabled.
The kernel has always disabled any check hash functions that it
does not support, so as more types of check hashes are added, we
will get a non-surprising result. Specifically if filesystems get
moved to kernels supporting fewer of the check hashes, those that
are not supported will be disabled. If the filesystem is moved back
to a kernel with more of the check-hashes available and fsck is run
interactively to rebuild them, then their checking will resume.
Otherwise just the smaller subset will be checked.
A side effect of this commit is that filesystems running with
cylinder-group check hashes will stop having them checked until
fsck is run to re-enable them (since none of them currently have
the FS_METACKHASH flag set). So, if you want check hashes enabled
on your filesystems after booting a kernel with these changes, you
need to run fsck to enable them. Any newly created filesystems will
have check hashes enabled. If in doubt as to whether you have check
hashes emabled, run dumpfs and look at the list of enabled flags
at the end of the superblock details.
2018-02-08 23:06:58 +00:00
|
|
|
if (afs.fs_flags & FS_METACKHASH) {
|
|
|
|
|
printf("check hashes\t");
|
|
|
|
|
fsflags = afs.fs_metackhash;
|
|
|
|
|
if (fsflags == 0)
|
|
|
|
|
printf("none");
|
|
|
|
|
if (fsflags & CK_SUPERBLOCK)
|
|
|
|
|
printf("superblock ");
|
|
|
|
|
if (fsflags & CK_CYLGRP)
|
|
|
|
|
printf("cylinder-groups ");
|
|
|
|
|
if (fsflags & CK_INODE)
|
|
|
|
|
printf("inodes ");
|
|
|
|
|
if (fsflags & CK_INDIR)
|
|
|
|
|
printf("indirect-blocks ");
|
|
|
|
|
if (fsflags & CK_DIR)
|
|
|
|
|
printf("directories ");
|
|
|
|
|
}
|
2017-09-22 12:45:15 +00:00
|
|
|
fsflags &= ~(CK_SUPERBLOCK | CK_CYLGRP | CK_INODE | CK_INDIR | CK_DIR);
|
|
|
|
|
if (fsflags != 0)
|
|
|
|
|
printf("unknown flags (%#x)", fsflags);
|
|
|
|
|
putchar('\n');
|
2003-02-01 04:17:10 +00:00
|
|
|
printf("fsmnt\t%s\n", afs.fs_fsmnt);
|
2012-10-30 21:32:10 +00:00
|
|
|
printf("volname\t%s\tswuid\t%ju\tprovidersize\t%ju\n",
|
|
|
|
|
afs.fs_volname, (uintmax_t)afs.fs_swuid,
|
|
|
|
|
(uintmax_t)afs.fs_providersize);
|
1994-05-26 06:35:07 +00:00
|
|
|
printf("\ncs[].cs_(nbfree,ndir,nifree,nffree):\n\t");
|
|
|
|
|
for (i = 0; i < afs.fs_ncg; i++) {
|
|
|
|
|
struct csum *cs = &afs.fs_cs(&afs, i);
|
|
|
|
|
if (i && i % 4 == 0)
|
|
|
|
|
printf("\n\t");
|
|
|
|
|
printf("(%d,%d,%d,%d) ",
|
|
|
|
|
cs->cs_nbfree, cs->cs_ndir, cs->cs_nifree, cs->cs_nffree);
|
|
|
|
|
}
|
|
|
|
|
printf("\n");
|
2002-06-21 06:18:05 +00:00
|
|
|
if (fssize % afs.fs_fpg) {
|
2002-08-11 15:38:51 +00:00
|
|
|
if (disk.d_ufs == 1)
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("cylinders in last group %d\n",
|
|
|
|
|
howmany(afs.fs_old_size % afs.fs_fpg,
|
|
|
|
|
afs.fs_old_spc / afs.fs_old_nspf));
|
2003-01-19 12:13:47 +00:00
|
|
|
printf("blocks in last group %ld\n\n",
|
|
|
|
|
(long)((fssize % afs.fs_fpg) / afs.fs_frag));
|
1994-05-26 06:35:07 +00:00
|
|
|
}
|
2021-07-02 14:18:17 -08:00
|
|
|
if (dosb)
|
|
|
|
|
return (0);
|
2003-01-19 05:51:36 +00:00
|
|
|
while ((i = cgread(&disk)) != 0) {
|
|
|
|
|
if (i == -1 || dumpcg())
|
1994-05-26 06:35:07 +00:00
|
|
|
goto err;
|
2003-01-19 05:51:36 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
return (0);
|
|
|
|
|
|
2003-01-19 10:25:11 +00:00
|
|
|
err: ufserr(name);
|
1994-05-26 06:35:07 +00:00
|
|
|
return (1);
|
2002-07-11 21:46:12 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static int
|
2003-01-19 05:51:36 +00:00
|
|
|
dumpcg(void)
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2003-01-19 12:13:47 +00:00
|
|
|
time_t cgtime;
|
1994-05-26 06:35:07 +00:00
|
|
|
off_t cur;
|
|
|
|
|
int i, j;
|
|
|
|
|
|
2003-01-19 05:51:36 +00:00
|
|
|
printf("\ncg %d:\n", disk.d_lcg);
|
|
|
|
|
cur = fsbtodb(&afs, cgtod(&afs, disk.d_lcg)) * disk.d_bsize;
|
2002-08-11 15:38:51 +00:00
|
|
|
switch (disk.d_ufs) {
|
|
|
|
|
case 2:
|
2003-01-19 12:13:47 +00:00
|
|
|
cgtime = acg.cg_time;
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("magic\t%x\ttell\t%jx\ttime\t%s",
|
|
|
|
|
acg.cg_magic, (intmax_t)cur, ctime(&cgtime));
|
2006-10-31 22:02:24 +00:00
|
|
|
printf("cgx\t%d\tndblk\t%d\tniblk\t%d\tinitiblk %d\tunrefs %d\n",
|
|
|
|
|
acg.cg_cgx, acg.cg_ndblk, acg.cg_niblk, acg.cg_initediblk,
|
|
|
|
|
acg.cg_unrefs);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
case 1:
|
2003-01-19 12:13:47 +00:00
|
|
|
cgtime = acg.cg_old_time;
|
2003-11-14 13:13:23 +00:00
|
|
|
printf("magic\t%x\ttell\t%jx\ttime\t%s",
|
|
|
|
|
acg.cg_magic, (intmax_t)cur, ctime(&cgtime));
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("cgx\t%d\tncyl\t%d\tniblk\t%d\tndblk\t%d\n",
|
|
|
|
|
acg.cg_cgx, acg.cg_old_ncyl, acg.cg_old_niblk,
|
|
|
|
|
acg.cg_ndblk);
|
2002-08-11 15:38:51 +00:00
|
|
|
break;
|
|
|
|
|
default:
|
|
|
|
|
break;
|
2002-06-21 06:18:05 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
printf("nbfree\t%d\tndir\t%d\tnifree\t%d\tnffree\t%d\n",
|
|
|
|
|
acg.cg_cs.cs_nbfree, acg.cg_cs.cs_ndir,
|
|
|
|
|
acg.cg_cs.cs_nifree, acg.cg_cs.cs_nffree);
|
|
|
|
|
printf("rotor\t%d\tirotor\t%d\tfrotor\t%d\nfrsum",
|
|
|
|
|
acg.cg_rotor, acg.cg_irotor, acg.cg_frotor);
|
|
|
|
|
for (i = 1, j = 0; i < afs.fs_frag; i++) {
|
|
|
|
|
printf("\t%d", acg.cg_frsum[i]);
|
|
|
|
|
j += i * acg.cg_frsum[i];
|
|
|
|
|
}
|
|
|
|
|
printf("\nsum of frsum: %d", j);
|
|
|
|
|
if (afs.fs_contigsumsize > 0) {
|
|
|
|
|
for (i = 1; i < afs.fs_contigsumsize; i++) {
|
|
|
|
|
if ((i - 1) % 8 == 0)
|
|
|
|
|
printf("\nclusters %d-%d:", i,
|
2016-05-02 01:40:31 +00:00
|
|
|
MIN(afs.fs_contigsumsize - 1, i + 7));
|
1994-05-26 06:35:07 +00:00
|
|
|
printf("\t%d", cg_clustersum(&acg)[i]);
|
|
|
|
|
}
|
|
|
|
|
printf("\nclusters size %d and over: %d\n",
|
|
|
|
|
afs.fs_contigsumsize,
|
|
|
|
|
cg_clustersum(&acg)[afs.fs_contigsumsize]);
|
|
|
|
|
printf("clusters free:\t");
|
|
|
|
|
pbits(cg_clustersfree(&acg), acg.cg_nclusterblks);
|
|
|
|
|
} else
|
|
|
|
|
printf("\n");
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("inodes used:\t");
|
1994-05-26 06:35:07 +00:00
|
|
|
pbits(cg_inosused(&acg), afs.fs_ipg);
|
2002-06-21 06:18:05 +00:00
|
|
|
printf("blks free:\t");
|
1994-05-26 06:35:07 +00:00
|
|
|
pbits(cg_blksfree(&acg), afs.fs_fpg);
|
|
|
|
|
return (0);
|
2002-07-11 21:46:12 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static int
|
2009-01-28 09:33:00 +00:00
|
|
|
dumpfreespace(const char *name, int fflag)
|
|
|
|
|
{
|
|
|
|
|
int i;
|
|
|
|
|
|
|
|
|
|
while ((i = cgread(&disk)) != 0) {
|
|
|
|
|
if (i == -1)
|
|
|
|
|
goto err;
|
|
|
|
|
dumpfreespacecg(fflag);
|
|
|
|
|
}
|
|
|
|
|
return (0);
|
|
|
|
|
err:
|
|
|
|
|
ufserr(name);
|
|
|
|
|
return (1);
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static void
|
2009-01-28 09:33:00 +00:00
|
|
|
dumpfreespacecg(int fflag)
|
|
|
|
|
{
|
|
|
|
|
|
|
|
|
|
pblklist(cg_blksfree(&acg), afs.fs_fpg, disk.d_lcg * afs.fs_fpg,
|
|
|
|
|
fflag);
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static int
|
2003-01-19 10:25:11 +00:00
|
|
|
marshal(const char *name)
|
|
|
|
|
{
|
|
|
|
|
struct fs *fs;
|
|
|
|
|
|
|
|
|
|
fs = &disk.d_fs;
|
|
|
|
|
|
|
|
|
|
printf("# newfs command for %s (%s)\n", name, disk.d_name);
|
|
|
|
|
printf("newfs ");
|
2003-06-09 09:26:02 +00:00
|
|
|
if (fs->fs_volname[0] != '\0')
|
|
|
|
|
printf("-L %s ", fs->fs_volname);
|
2003-01-19 10:25:11 +00:00
|
|
|
printf("-O %d ", disk.d_ufs);
|
|
|
|
|
if (fs->fs_flags & FS_DOSOFTDEP)
|
|
|
|
|
printf("-U ");
|
|
|
|
|
printf("-a %d ", fs->fs_maxcontig);
|
|
|
|
|
printf("-b %d ", fs->fs_bsize);
|
|
|
|
|
/* -c is dumb */
|
|
|
|
|
printf("-d %d ", fs->fs_maxbsize);
|
|
|
|
|
printf("-e %d ", fs->fs_maxbpg);
|
|
|
|
|
printf("-f %d ", fs->fs_fsize);
|
|
|
|
|
printf("-g %d ", fs->fs_avgfilesize);
|
|
|
|
|
printf("-h %d ", fs->fs_avgfpdir);
|
2013-05-16 20:07:08 +00:00
|
|
|
printf("-i %jd ", fragroundup(fs, lblktosize(fs, fragstoblks(fs,
|
|
|
|
|
fs->fs_fpg)) / fs->fs_ipg));
|
2011-03-23 08:33:12 +00:00
|
|
|
if (fs->fs_flags & FS_SUJ)
|
|
|
|
|
printf("-j ");
|
2012-10-22 03:00:20 +00:00
|
|
|
if (fs->fs_flags & FS_GJOURNAL)
|
|
|
|
|
printf("-J ");
|
2013-05-16 20:07:08 +00:00
|
|
|
printf("-k %jd ", fs->fs_metaspace);
|
|
|
|
|
if (fs->fs_flags & FS_MULTILABEL)
|
|
|
|
|
printf("-l ");
|
2003-01-19 10:25:11 +00:00
|
|
|
printf("-m %d ", fs->fs_minfree);
|
|
|
|
|
/* -n unimplemented */
|
|
|
|
|
printf("-o ");
|
|
|
|
|
switch (fs->fs_optim) {
|
|
|
|
|
case FS_OPTSPACE:
|
|
|
|
|
printf("space ");
|
|
|
|
|
break;
|
|
|
|
|
case FS_OPTTIME:
|
|
|
|
|
printf("time ");
|
|
|
|
|
break;
|
|
|
|
|
default:
|
|
|
|
|
printf("unknown ");
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
/* -p..r unimplemented */
|
2009-10-19 14:04:19 +00:00
|
|
|
printf("-s %jd ", (intmax_t)fsbtodb(fs, fs->fs_size));
|
2011-03-23 08:33:12 +00:00
|
|
|
if (fs->fs_flags & FS_TRIM)
|
|
|
|
|
printf("-t ");
|
2003-01-19 10:25:11 +00:00
|
|
|
printf("%s ", disk.d_name);
|
|
|
|
|
printf("\n");
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static void
|
2002-03-20 22:57:10 +00:00
|
|
|
pbits(void *vp, int max)
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2002-03-20 17:55:10 +00:00
|
|
|
int i;
|
|
|
|
|
char *p;
|
1994-05-26 06:35:07 +00:00
|
|
|
int count, j;
|
|
|
|
|
|
|
|
|
|
for (count = i = 0, p = vp; i < max; i++)
|
|
|
|
|
if (isset(p, i)) {
|
|
|
|
|
if (count)
|
|
|
|
|
printf(",%s", count % 6 ? " " : "\n\t");
|
|
|
|
|
count++;
|
|
|
|
|
printf("%d", i);
|
|
|
|
|
j = i;
|
|
|
|
|
while ((i+1)<max && isset(p, i+1))
|
|
|
|
|
i++;
|
|
|
|
|
if (i != j)
|
|
|
|
|
printf("-%d", i);
|
|
|
|
|
}
|
|
|
|
|
printf("\n");
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static void
|
2009-01-28 09:33:00 +00:00
|
|
|
pblklist(void *vp, int max, off_t offset, int fflag)
|
|
|
|
|
{
|
|
|
|
|
int i, j;
|
|
|
|
|
char *p;
|
|
|
|
|
|
|
|
|
|
for (i = 0, p = vp; i < max; i++) {
|
|
|
|
|
if (isset(p, i)) {
|
|
|
|
|
printf("%jd", (intmax_t)(i + offset));
|
|
|
|
|
if (fflag < 2) {
|
|
|
|
|
j = i;
|
|
|
|
|
while ((i+1)<max && isset(p, i+1))
|
|
|
|
|
i++;
|
|
|
|
|
if (i != j)
|
2009-01-28 12:08:19 +00:00
|
|
|
printf("-%jd", (intmax_t)(i + offset));
|
2009-01-28 09:33:00 +00:00
|
|
|
}
|
|
|
|
|
printf("\n");
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static void
|
2003-01-19 10:25:11 +00:00
|
|
|
ufserr(const char *name)
|
|
|
|
|
{
|
|
|
|
|
if (disk.d_error != NULL)
|
|
|
|
|
warnx("%s: %s", name, disk.d_error);
|
|
|
|
|
else if (errno)
|
|
|
|
|
warn("%s", name);
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 09:01:44 +00:00
|
|
|
static void
|
2002-03-20 22:57:10 +00:00
|
|
|
usage(void)
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2011-12-26 16:47:45 +00:00
|
|
|
(void)fprintf(stderr, "usage: dumpfs [-flm] filesys | device\n");
|
1994-05-26 06:35:07 +00:00
|
|
|
exit(1);
|
|
|
|
|
}
|
