summaryrefslogtreecommitdiffstats
path: root/sbin/dumpfs
Commit message (Collapse)AuthorAgeFilesLines
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-1/+1
|
* Mechanically kill hard sentence breaks.ru2004-07-021-1/+2
|
* Remove advertising clause from University of California Regent's license,markm2004-04-092-8/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Reinstate 1.40 -- swap avgfilesize and avgfpdir column order.truckman2003-12-071-2/+2
| | | | MFC after: 3 days
* I forgot about the code freeze, so back this out.truckman2003-12-011-2/+2
|
* Swap avgfilesize and avgfpdir order to give better column alignment.truckman2003-12-011-2/+2
|
* Print the dirpref avgfilesize and avgfpdir parameters.truckman2003-11-171-0/+2
| | | | MFC after: 2 weeks
* Make this WARNS=2 clean byjohan2003-11-142-20/+22
| | | | | | - using (intmax_t) and %j instead of %q Tested by: make universe
* Marshal newfs -L (filesystem volume names), the names are not marshalledjmallett2003-06-091-0/+2
| | | | with any quoting, but that should be OK for re-input, regardless.
* mdoc(7) police: markup laundry.ru2003-02-231-2/+2
|
* Correct lines incorrectly added to the copyright message. Add missing period.mckusick2003-02-141-4/+1
| | | | | Submitted by: Bruce Evans <bde@zeta.org.au> Sponsored by: DARPA & NAI Labs.
* Bring in support for volume labels to the filesystem utilities.gordon2003-02-011-0/+3
| | | | Reviewed by: mckusick
* Spell libufs correctly in DPADD.ru2003-01-261-1/+1
| | | | Reviewed by: juli
* Parse both old flags location and new one. Print out new flags includingnjl2003-01-241-14/+24
| | | | acls, multilabel, and location updated.
* Add libufs to dependencies.jmallett2003-01-201-1/+2
|
* Kill initialisation and shadow warnings. Half-hearted cleanup (e.g. only thejmallett2003-01-191-20/+21
| | | | | | | more important ones) of format warnings. XXX Lots of this assumes int32 can be printed with %d. Yuck. Reviewed by: bde
* Add support to marshal a filesystem to a newfs(8) command that could be usedjmallett2003-01-192-18/+94
| | | | | | to create it. A small number of options are not marshalled as they are things it would be dumb to spit out, as they are used by internal computations, and newfs may change them, or they may not be directly apparent.
* Let libufs handle all the work with regard to going through a list of cgs, now.jmallett2003-01-191-8/+7
|
* Use libufs to read one cylinder group from the disk at a time.jmallett2003-01-191-7/+2
|
* Simplify the main function now that libufs will hunt for the disk for us.jmallett2003-01-191-13/+7
|
* Simplify conditional.jmallett2003-01-181-6/+4
|
* Create a new 32-bit fs_flags word in the superblock. Add code to movemckusick2002-11-271-1/+1
| | | | | | | | | | | | | | | | | the old 8-bit fs_old_flags to the new location the first time that the filesystem is mounted by a new kernel. One of the unused flags in fs_old_flags is used to indicate that the flags have been moved. Leave the fs_old_flags word intact so that it will work properly if used on an old kernel. Change the fs_sblockloc superblock location field to be in units of bytes instead of in units of filesystem fragments. The old units did not work properly when the fragment size exceeeded the superblock size (8192). Update old fs_sblockloc values at the same time that the flags are moved. Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk> Sponsored by: DARPA & NAI Labs.
* Deal with the possibility that time_t != int32_t. Otherwise ia64 thoughtpeter2002-11-171-2/+4
| | | | the fs_old_size was the half part of fs_old_time etc.
* Use more non-b0rked error reporting. Print the disk we are trying to openjmallett2002-11-051-3/+6
| | | | | | and (we have the disk error from libufs? the disk error: the errno). Requested by: bde, <many>
* Forgot to include <errno.h> when using 'errno' here.jmallett2002-10-221-0/+1
|
* When errno is not set, do not use warn(3).jmallett2002-10-221-1/+2
|
* Use the libufs_printerror() function, which hopefully will deconfuse usersjmallett2002-10-221-1/+2
| | | | | | getting error cases in a libufsificated dumpfs(8). Poked by: kkenn
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-211-4/+4
|
* Simplify some things to use libufs-provided functionality here, such as thejmallett2002-08-111-21/+28
| | | | | | version of UFS on a disk, and bread() instead of other types of idiocy. Obtained from: jmallett_libufs Perforce branch.
* Remove unused variables due to libufs(3) commit. Clean up extraneous use ofjmallett2002-07-111-4/+3
| | | | semicolon at closing paren of a function body.
* Convert dumpfs(8) to libufs(3), rather than rolling local functions for ajmallett2002-07-112-39/+14
| | | | number of things.
* The .Nm utilitycharnier2002-07-061-3/+4
|
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-211-106/+128
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability to use jumbo blocks per inode to allow extent like pointer density, and space for extended attributes (up to twice the filesystem block size worth of attributes, e.g., on a 16K filesystem, there is space for 32K of attributes). UFS2 fully supports and runs existing UFS1 filesystems. New filesystems built using newfs can be built in either UFS1 or UFS2 format using the -O option. In this commit UFS1 is the default format, so if you want to build UFS2 format filesystems, you must specify -O 2. This default will be changed to UFS2 when UFS2 proves itself to be stable. In this commit the boot code for reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c) as there is insufficient space in the boot block. Once the size of the boot block is increased, this code can be defined. Things to note: the definition of SBSIZE has changed to SBLOCKSIZE. The header file <ufs/ufs/dinode.h> must be included before <ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and ufs_lbn_t. Still TODO: Verify that the first level bootstraps work for all the architectures. Convert the utility ffsinfo to understand UFS2 and test growfs. Add support for the extended attribute storage. Update soft updates to ensure integrity of extended attribute storage. Switch the current extended attribute interfaces to use the extended attribute storage. Add the extent like functionality (framework is there, but is currently never used). Sponsored by: DARPA & NAI Labs. Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
* more file system > filesystemtrhodes2002-05-161-4/+4
|
* Sigh, more BBSIZE related breakage.phk2002-05-121-0/+1
| | | | Sponsored by: DARPA & NAI Labs.
* o __P removedimp2002-03-201-16/+9
| | | | | | | o ansi function prototypes o unifdef -D__STDC__ o __dead2 on usage prototype o remove now-bogus main prototype
* Remove 'register' keyword.obrien2002-03-201-4/+4
| | | | | | It does not help modern compilers, and some may take some hit from it. (I also found several functions that listed *every* of its 10 local vars with "register" -- just how many free registers do people think machines have?)
* Default to WARNS=2.obrien2001-12-041-0/+1
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for sbin/ to 8.ru2001-03-201-1/+1
|
* The ffs superblock includes a 128-byte region for use by temporaryiedowse2001-01-151-2/+2
| | | | | | | | | | | | | | | | | | | | in-core pointers to summary information. An array in this region (fs_csp) could overflow on filesystems with a very large number of cylinder groups (~16000 on i386 with 8k blocks). When this happens, other fields in the superblock get corrupted, and fsck refuses to check the filesystem. Solve this problem by replacing the fs_csp array in 'struct fs' with a single pointer, and add padding to keep the length of the 128-byte region fixed. Update the kernel and userland utilities to use just this single pointer. With this change, the kernel no longer makes use of the superblock fields 'fs_csshift' and 'fs_csmask'. Add a comment to newfs/mkfs.c to indicate that these fields must be calculated for compatibility with older kernels. Reviewed by: mckusick
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-1/+1
|
* $Id$ -> $FreeBSD$peter1999-08-282-2/+2
|
* Print out the fields that are set in fs_flags.mpp1999-07-181-1/+12
|
* Print out the fs_id field.phk1999-06-271-1/+2
|
* Add rcsid. Remove unused #includes.charnier1998-06-151-4/+5
|
* Check bytes read to prevent random error message.rnordier1998-04-201-1/+8
|
* Print fs_maxfilesize.bde1997-06-291-2/+2
|
* Make this compile after the fsirand changes that deleted two fields.peter1997-03-281-2/+2
| | | | | | | | | I was not sure whether the fs_id fields should be printed in the clear in case of sniffing over a network login etc. It might be an idea to have somebody with spare time go through and find any other missing fields that should be reported. Definate 2.2.x/2.1.x candidate since it breaks the build.
OpenPOWER on IntegriCloud