summaryrefslogtreecommitdiffstats
path: root/sbin/dump
Commit message (Collapse)AuthorAgeFilesLines
* MFC r271411:hrs2014-10-091-1/+6
| | | | | | Fix a bug which could break extended attributes in a dump output. This occurred when a file was >892kB long and had a large data (>1kB) in the extended attributes.
* Mark non-returning function as sucheadler2012-11-291-1/+1
| | | | | | PR: bin/172978 Approved by: cperciva MFC after: 3 days
* Fix sbin/ build with a 64-bit ino_t.mdf2012-09-271-5/+6
| | | | Original code by: Gleb Kurtsou
* mdoc: move two sentences from synopsis to description (where they reallyjoel2012-05-231-10/+8
| | | | belong). With this change, mandoc now formats these manpages properly.
* Replace index() and rindex() calls with strchr() and strrchr().ed2012-01-031-1/+1
| | | | | | | | | | The index() and rindex() functions were marked LEGACY in the 2001 revision of POSIX and were subsequently removed from the 2008 revision. The strchr() and strrchr() functions are part of the C standard. This makes the source code a lot more consistent, as most of these C files also call into other str*() routines. In fact, about a dozen already perform strchr() calls.
* The current /etc/dumpdates file restricts device names to 32 characters.mckusick2011-10-182-3/+7
| | | | | | | | | | | | | | | | | With the addition of various GEOM layers some device names now exceed this length, for example /dev/mirror/encrypted.elig.journal. This change expands the field to 53 bytes which brings the /etc/dumpdates lines to 80 characters. Exceeding 80 characters makes the /etc/dumpdates file much less human readable. A test is added to dump so that it verifies that the device name will fit in the 53 character field failing the dump if it is too long. This change has been checked to verify that its /etc/dumpdates file is compatible with older versions of dump. Reported by: Martin Sugioarto <martin@sugioarto.com> PR: kern/160678 MFC after: 3 weeks
* The dump, fsck_ffs, fsdb, fsirand, newfs, makefs, and quot utilitiesmckusick2011-01-244-4/+4
| | | | | | | | | | | | | | include sys/time.h instead of time.h. This include is incorrect as per the manpages for the APIs and the POSIX definitions. This commit replaces sys/time.h where necessary with time.h. The commit also includes some minor style(9) header fixup in newfs. This commit is part of a larger effort by Garrett Cooper started in //depot/user/gcooper/posix-conformance-work/ -- to make FreeBSD more POSIX compliant. Submitted by: Garrett Cooper yanegomi at gmail dot com
* Plug two memory leaks in error case.delphij2010-02-032-2/+5
| | | | MFC after: 1 month
* Switch the default WARNS level for sbin/ to 6.ru2009-10-191-0/+1
| | | | Submitted by: Ulrich Spörlein
* Make dump -W show the level correctly.brian2009-05-291-1/+1
| | | | | | PR: 129110 Submitted by: Mike Voorhis <mvoorhis@cs.wpi.edu> MFC after: 3 weeks
* Verify that the filesystem being referenced in fstab is indeed a UFScy2009-03-021-2/+3
| | | | | | | | filesystem. This avoids confusion with nullfs and unionfs filesystems which reference the root of a UFS filesystem as a target. PR: 116849 Approved by: kib
* Expand dump to allow MAX_INT dump levels.mckusick2008-05-243-14/+21
| | | | | PR: bin/100732 Submitted by: Matthew Vincenz <msvincen@midway.uchicago.edu>
* When using dump to generate level 0 dumps which are then rsync'edmckusick2008-05-234-4/+51
| | | | | | | | | | | | to a remote machine, the fact that the dump date is stored with each header (inode) record makes rsync significantly less efficient than necessary. This also applies to inode access times when they are not important data to retain. When implementing an offsite backup solution of this type, these dates in particular are not important, especially if it prevents effective offsite backups. PR: bin/91049 Submitted by: Forrest W Christian <fwc@mt.net>
* (bread): For a read that is contained entirely within a block, never copythomas2007-04-051-1/+1
| | | | | | | | out more than size bytes to the caller's buffer. PR: bin/111191 Reviewed by: pb MFC after: 1 week
* Fix an error in dumping large sparse files containing extended attributes.mckusick2007-02-271-2/+2
|
* Update the dump program to save extended attributes. Updatemckusick2007-02-262-20/+166
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | the restore program to restore all dumped extended attributes. If the restore is running as root, it will always be able to restore all extended attributes. If it is not running as root, it makes a best effort to set them. Using the -v command line flag or the `verbose' command in interactive mode will display all the extended attributes being set on files (and at the end on directories) that are being restored. It will note any extended attributes that could not be set. The extended attributes are placed on the dump image immediately following each file's data. Older versions of restore can work with the newer dump images. Old versions of restore will correctly restore the file data and then (silently) skip over the extended attribute data and proceed to the next file. This resolves PR 93085 which will be closed once the code has been MFC'ed. Note that this code will not compile until these header files have been updated: <protocols/dumprestore.h> and <sys/extattr.h>. PR: bin/93085 Comments from: Poul-Henning Kamp and Robert Watson MFC after: 3 weeks
* Make "dump /filesystem" (without options) work.ru2006-10-121-2/+5
| | | | | PR: docs/84408 MFC after: 3 days
* Markup fixes.ru2006-09-181-7/+11
|
* 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
OpenPOWER on IntegriCloud