summaryrefslogtreecommitdiffstats
path: root/sbin/dump
Commit message (Collapse)AuthorAgeFilesLines
* Remove reference to max block size. dump no longer limits the block size.grog2003-07-141-13/+1
|
* Add section number to .Xrcharnier2003-06-081-1/+1
|
* Dump is hard-wired to believe that it can read disks onmckusick2003-05-072-4/+48
| | | | | | | | | | | | | | | | | | 1024-byte boundaries. For many years this was a reasonable assumption. However, in recent years we have begun seeing devices with 2048-byte sectors. These devices return errors when dump tries to read starting in the middle of a sector or when it tries to read only the first half of a sector. Rather than change the native block size used by dump (and thus create an incompatible dump format), this fix checks for transfer requests that start and/or end on a non-sector boundary. When such a read is detected, the new code reads the entire sector and copies out just the part that dump needs. Reviewed by: Poul-Henning Kamp <phk@critter.freebsd.dk> Approved by: re (John Baldwin <jhb@FreeBSD.org>) Sponsored by: DARPA & NAI Labs.
* Removed all vestiges of KerberosIV.ru2003-05-013-7/+4
|
* Fixed the MLINKS assignment style.ru2003-05-011-1/+1
|
* De-Kerberise (KerberosIV). KerberosIV is no longer present, andmarkm2003-05-014-48/+4
| | | | | remote backups can still be done with Kerberos authentication using SSH and Kerberos 5.
* Avoid a name conflict with future functionality:mdodd2003-04-073-4/+4
| | | | getfstab() -> dump_getfstab()
* Sort options.ru2003-02-232-40/+53
|
* Readjust the cache initialization code to make it more obvious that thedillon2003-01-251-12/+7
| | | | cache is bypassed when disabled.
* really, this time for sure. Fix formatting in usage().dillon2003-01-131-2/+2
|
* Grr. I keep forgetting things. Include -C in dump's usage() .dillon2003-01-131-1/+1
|
* Add support for obsolete option form for -Cdillon2003-01-131-0/+1
|
* Add a caching option to dump. Use -C. Note that NetBSD has a caching optiondillon2003-01-136-6/+175
| | | | | | | | | | | | | | | | | | | called -r but it takes 512 byte blocks instead of megabytes, and I felt a megabytes specification would be far more useful so I did not use the same option character. This will *greatly* improve dump performance at the cost of possibly missing filesystem changes that occur between passes, and does a fairly good job making up for the loss of buffered block devices. Caching is disabled by default to retain historical behavior. In tests, dump performance improved by about 40% when dumping / or /usr. Beware that dump forks and the cache may wind up being larger then you specify, but a more complex shared memory implementation would not produce results that are all that much better so I kept it simple for now. MFC after: 3 days
* Add TAPE to the ENVIRONMENT section and standardize the section, using asheldonh2003-01-101-3/+6
| | | | | | list instead of prose. MFC after: 1 month
* Fixed the abuses of .Ql visible on stderr in troff mode.ru2002-12-231-1/+1
| | | | PR: docs/37176
* Uniformly refer to a file system as "file system".ru2002-12-121-2/+2
| | | | Approved by: re
* Add the `L' option to dump to notify it that it is dumping amckusick2002-12-032-15/+91
| | | | | | | | | | | | | | | live filesystem. To obtain a consistent dump image, dump takes a snapshot of the filesystem and then does a dump of the snapshot. The snapshot is removed when the dump is complete. Also add an operator warning that the `L' option should be used if dump is run on a live filesystem without the `L' option being specified. The alternative would be to silently use a snapshot any time that a live filesystem is dumped, but this change in dump semantics seemed too drastic at this time. Sponsored by: DARPA & NAI Labs. Approved by: re
* Correct the estimated block count calculated by dump to accountmckusick2002-12-032-2/+4
| | | | | | for the minimal amount of space used by a snapshot. Sponsored by: DARPA & NAI Labs.
* Properly handle UFS2 sparsely allocated inodes. The UFS2 filesystemmckusick2002-12-031-25/+66
| | | | | | | | | | only preallocates a small number of inodes. The dump program tries to scan through all the allocated inodes on a filesystem which causes bad behavior if they have never been allocated. Thus dump must calculate the set of inodes that have actually been allocated and scan only those inodes. Sponsored by: DARPA & NAI Labs.
* Mark snapshots so that dump will dump them as zero lengthmckusick2002-11-301-2/+8
| | | | | | regular files rather than trying to interpret the snapshot. Sponsored by: DARPA & NAI Labs.
* Create a new 32-bit fs_flags word in the superblock. Add code to movemckusick2002-11-271-2/+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.
* Changed "file system" back to "filesystem" in the usage message. Englishbde2002-10-011-3/+3
| | | | | | | | rules don't apply to tokens that are supposed to represent single args. This was only fixed in the man page. Fixed other differences between the man page and the usage message (1 formatting bug and 1 syntax bug).
* Use the standardized CHAR_BIT constant instead of NBBY in userland.mike2002-09-257-7/+16
|
* Fix some 'SYNOPSIS' and 'usage' messages.trhodes2002-08-271-1/+1
|
* Fix Synopsistrhodes2002-08-261-1/+1
|
* Replace various spelling with FALLTHROUGH which is lint()ablecharnier2002-08-251-2/+2
|
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-217-31/+31
|
* Change utimes to set the file creation time (for filesystems thatmckusick2002-07-171-4/+4
| | | | | | | | support creation times such as UFS2) to the value of the modification time if the value of the modification time is older than the current creation time. See utimes(2) for further details. Sponsored by: DARPA & NAI Labs.
* Oops, the previous revision (1.22) introduced a potential alignmentiedowse2002-07-081-15/+20
| | | | | | | | | issue, since the MAXBSIZE-sized buffers are accessed as arrays of block pointers, but were declared as char[] arrays. Use a union to avoid this, which also makes a number of casts unnecessary. Pointed out by: bde Reviewed by: bde
* - Do not include <utmp.h> for no reason.robert2002-07-082-4/+0
| | | | - Remove unneeded utmp path constant.
* Use a fixed MAXBSIZE-size auto array instead of a static pointeriedowse2002-07-081-6/+2
| | | | | | | | | to a malloc'd buffer in dmpindir() and dirindir(). These functions recursively call themselves to handle deeper levels of indirect blocks, so a single static buffer was not suitable. Bug tracked down by: Don Lewis <dl-freebsd@catspoiler.org> Approach suggested by: bde
* Replace the use of %qd with intmax_t/%jd and fix a number of -Walliedowse2002-07-084-20/+23
| | | | | | | and -Wformat warnings: o Include timeconv.h for the time conversion functions. o Remove unused variables. o Correct a few cases where %d was used when printing longs.
* Fix some printf format errors.iedowse2002-07-072-6/+6
| | | | Submitted by: Don Lewis <dl-freebsd@catspoiler.org>
* The .Nm utilitycharnier2002-07-061-13/+17
|
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-216-123/+250
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* s/daddr_t/ufs_daddr_t/gphk2002-06-063-19/+19
| | | | | | This should fix the issues which cropped up after daddr_t grew up. Sponsored by: DARPA & NAI Labs.
* mdoc(7) police: nits.ru2002-05-291-1/+2
|
* Move _PATH_WALL from dump and shutdown's local pathnames.h to paths.h.jmallett2002-05-171-1/+0
|
* more file system > filesystemtrhodes2002-05-164-7/+7
|
* Sigh, more BBSIZE related breakage.phk2002-05-121-0/+1
| | | | Sponsored by: DARPA & NAI Labs.
* Replaced exists() tests with two equivalent defined().ru2002-04-181-1/+1
| | | | | LIBDIR is defined in bsd.own.mk but sys.mk no longer includes bsd.own.mk as of revision 1.60.
* dump(8)'s manual page is confusing in its use of records, blocks,trhodes2002-04-171-13/+26
| | | | | | | | | | | blocksizes, etc does not give the default of -b only mentiones rdump in the NAME section uses both filesystem and file system in similar contexts PR: 34248 Submitted by: Gary W. Swearingen <swear@blarg.net> MFC after: 3 days
* o remove __Pimp2002-03-208-309/+155
| | | | | o Use ANSI function definitions o unifdef -D__STDC__
* mdoc(7) police: tiny fixes.ru2002-03-151-2/+3
|
* Add a new "-S" flag to dump to allow it just print out dump estimateiedowse2002-03-012-5/+20
| | | | | | | | | size and then exit. PR: bin/35450 Submitted by: Mark Hannon <markhannon@optushome.com.au> Obtained from: NetBSD MFC after: 1 week
* Supply progress information in dump's process title, which is usefuliedowse2002-02-164-7/+22
| | | | | | | | for monitoring automated backups. This is based on a patch by Mikhail Teterin, with some changes to make its operation clearer and to update the proctitle more frequently. PR: bin/32138
* On receipt of a SIGINFO, schedule an immediate printout of theiedowse2002-02-164-2/+16
| | | | | | | percentage complete and remaining time estimate. PR: bin/32138 Submitted by: mi
* Make dump's behaviour more sensible when the output file is a fifo.iedowse2002-02-111-0/+6
| | | | | | | | | | Normally trewind() performs a close-open-close cycle to rewind the tape when closing the device, but this is not ideal for fifos. We now skip the final open-close if the output descriptor is a fifo. PR: bin/25474 Submitted by: Alex Bakhtin <bakhtin@amt.ru> MFC after: 1 week
* Make it clear that dump(8)'s honoring of the UF_NODUMP flag is subjectdd2002-02-101-12/+6
| | | | | | | to the -h option. While here, xref chflags(1). PR: 33907 Submitted by: Gary W. Swearingen <swear@blarg.net>
* I've been meaning to do this for a while. Add an underscore to thedillon2002-01-192-7/+7
| | | | | | | | time_to_xxx() and xxx_to_time() functions. e.g. _time_to_xxx() instead of time_to_xxx(), to make it more obvious that these are stopgap functions & placemarkers and not meant to create a defacto standard. They will eventually be replaced when a real standard comes out of committee.
OpenPOWER on IntegriCloud