summaryrefslogtreecommitdiffstats
path: root/sbin/dump
Commit message (Collapse)AuthorAgeFilesLines
* Avoid casts as lvalues.kan2004-07-281-2/+8
|
* Print the `99.99% done, finished soon' message only as often as theiedowse2004-06-191-2/+5
| | | | | | | normal status messages. Previously a large number of these new messages could be spewed out towards the end of a dump. Reviewed by: imp
* Enter the 1990's and assume that the computer knows what time it is.imp2004-05-211-16/+23
| | | | | | Print the ETA of dump being finished, rather than a cryptic delta time. Also, if we have written more blocks than the tapesize, assume that we are 99.99% done and that we'll be finished 'soon'.
* Assorted markup, grammar, and spelling fixes.ru2004-05-171-14/+24
|
* Add -P arguments for dump(8) and restore(8) which allow the user togreen2004-04-134-20/+84
| | | | | | | | | | | use backup methods other than files and tapes. The -P argument is a normal sh(1) pipeline with either $DUMP_VOLUME or $RESTORE_VOLUME defined in the environment, respectively. For example, I can back up my home to three DVD+R[W]s as so: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2e 40028550 10093140 26733126 27% /home green# dump -0 -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /home
* Improve the warnings for dump -L and do not bother doing the snapshot ifgreen2004-04-122-3/+11
| | | | | | | it is specified for read-only filesystems. Submitted by: Jason Young <jyoung8607@hotmail.com> PR: 46672
* Fixed unformatting of copyright clause 4 in previous commit.bde2004-04-101-1/+1
|
* Remove advertising clause from University of California Regent's license,markm2004-04-0910-41/+1
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Add RSH to the list of enviroment variables.alex2004-01-151-0/+3
|
* Define _PATH_MKSNAP_FFS and use it in dump(8) instead of assumingiedowse2004-01-041-2/+2
| | | | | | that mksnap_ffs(8) can be found using the current $PATH. Reviewed by: mckusick
* Document that the live dump command (`dump -L') creates its snapshotmckusick2003-11-181-1/+12
| | | | | | | in the .snap directory in the root of the filesystem being dumped. Document that if the .snap directory is missing that it must be created manually and that it should be owned by user root and group operator and set to mode 770 before a live dump can be run.
* Convert the live dump command (`dump -L') to use mksnap_ffs insteadmckusick2003-11-161-12/+8
| | | | | | | | | | | | | | | of trying to directly create the snapshot itself. This change allows users logged into the system as operator to run live dumps. Note that dump no longer tries to create the snapshot in the root of the filesystem, but rather in a .snap directory in the root of the filesystem. The reason is that the operator is usually not permitted to write into the root of the filesystem. The newfs command and background fsck have both been modified to create a .snap directory in the root of the filesystem, but if neither of these have been run, then the .snap directory must be created manually by the superuser before a live dump can be run. The .snap directory should be owned by user root and group operator and set to mode 770.
* Make this WARNS=2 clean byjohan2003-11-143-5/+5
| | | | | | | | | | - using (intmax_t) and %j - giving a non-empty format string to msg() Include <stdint.h> directly instead of depending on <inttypes.h> to do it. Tested by: make universe
* - add explanation of what an active file system iskensmith2003-11-051-2/+14
| | | | | | | | - explain the reason for permitting 32 read errors for a dump PR: docs/35602 and docs/35607 Reviewed by: jhb Approved by: blackend (mentor)
* In mapdirs(), do not use the `dp' inode pointer after searchdir()iedowse2003-11-041-3/+3
| | | | | | | | | | | | | | has been called, since it points to a shared inode buffer that may be overwritten. The two cases where `dp' was used incorrectly appear to have been overlooked when "nodump" inheritance was first added in revision 1.12. This is reported to correct propagation of the nodump flag on directories that are larger than one block in size. PR: bin/58912 Submitted by: Volker Paepcke <vpaepcke@incore.de> MFC after: 1 week
* Add missing prototype for cread().iedowse2003-11-041-0/+1
|
* revert to version 1.25 and use va_copy to obtain another copy of theps2003-09-211-2/+5
| | | | | | | variable arguments. version 1.26 incorrectly truncated the message if the buffer was too long. Requested by: bde
* Fix improper use of varargs.ps2003-09-201-2/+2
| | | | Reviewed by: peter
* 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.
OpenPOWER on IntegriCloud