summaryrefslogtreecommitdiffstats
path: root/sbin/dump
Commit message (Collapse)AuthorAgeFilesLines
* Clarify documentation of '-L' command line switch: the snapshot isthomas2006-08-161-1/+2
| | | | | | | | | unlinked as soon as the dump starts (and removed when the dump is completed, and the dump process exits). Previous wording was confusing because users might expect the snapshot to be visible in the .snap subdirectory while dump is running. MFC after: 1 week
* If rawname returns NULL, deal with it appropriately.mjacob2006-08-151-0/+2
| | | | | | PR: 94045 Submitted by: Andrey Elsukov MFC after: 1 week
* Eliminate a pair of unneeded parentheses slipped in from previous version ofmarck2006-08-061-1/+1
| | | | | | fix. Noticed by: ru
* strlen(3) returns size_t, which is not strictly equivalent to int an 64-bitmarck2006-08-061-3/+4
| | | | | | | archs, hence printf(3) warning. Fix this. Noticed by: tinderbox Approved by: rse
* Do not pass-through the tailing newline character from the ctime(3)rse2006-08-051-3/+5
| | | | | | | | output to setproctitle(3) in order to get rid of the ugly two-character escape sequence "\n" in the ps(1) output of a dump(8) process: << [...] finished in 0:00 at Sat Aug 5 14:44:39 2006\n (dump) >> [...] finished in 0:00 at Sat Aug 5 14:44:39 2006 (dump)
* Dump keeps a bitmap of the state of various inodes, which is sizeddwmalone2006-04-111-8/+20
| | | | | | | | | | to match the number of inodes on the disk. If we find a directory entry with a crazy inode number in it, don't look beyond the end of the bitmap to find that inode's state. Instead skip that directory entry and print a warning. Reviewed by: iedowse MFC after: 3 weeks
* Revert a minor glitch of revision 1.69keramida2006-02-241-2/+2
| | | | | Submitted by: Andriy Tkachuk <andrit@ukr.net> X-MFC after: RE approval
* Add the example that green@ used in his commit log for the dump to aimp2005-12-231-1/+8
| | | | | pipe functionality. I've done a cvs log main.c about a dozen times now. Maybe others will find this useful.
* Correct the description of the TAPE environment variable.ceri2005-07-311-1/+5
| | | | | | | | Based on: PR: docs/84200 Submitted by: Gary W. Swearingen <garys at opusnet dot com> MFC after: 1 week
* Make gcc4 happy by making consistent signedness.delphij2005-05-021-1/+1
|
* 'r' disk devices no longer exist, so don't try to create a pathnameimp2005-04-181-20/+10
| | | | | | | that has an 'r' in it. This also eliminates a bogus use of strlcat. PR: 80064
* Use a signal-safe type for two variables that are used to synchroniseiedowse2005-03-021-2/+2
| | | | | | with a signal handler. This fixes a race condition introduced by compiler reordering that caused dump to sometimes get stuck, especially while dumping large filesystems.
* va_list style tweaksobrien2005-02-161-1/+2
|
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-2/+2
|
* Improved error checking for existence of a .snap directory towes2005-01-212-18/+29
| | | | | | | | generate snapshots in when -L is requested. If the .snap directory does not exist, or is not a directory, issue a warning and revert to the non- live behavior. Obtained from: St. Bernard Software RAPID
* Sort sections.ru2005-01-181-11/+11
|
* Added the EXIT STATUS section where appropriate.ru2005-01-171-1/+1
|
* Clearer va-args usage.obrien2004-12-301-4/+3
| | | | Submitted by: bde
* o Do not dump core in -W if dumpdates was not readable and ddatev == NULL.maxim2004-12-022-5/+2
| | | | | | | | | PR: bin/69977 o Remove unused ddates_in. Obtained from: NetBSD MFC after: 3 weeks
* 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
OpenPOWER on IntegriCloud