summaryrefslogtreecommitdiffstats
path: root/sbin/dump
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Files in subdirectories of directories that have the nodump flag setobrien2001-12-051-2/+5
| | | | | | | | | | | | | are sometimes incorrectly being dumped. The problem arises because the subdirectory only gets its entry cleared from usedinomap if it is also present in dumpinomap, and it is the absence of a directory in usedinomap that internally indicates that the directory is under the effects of UF_NODUMP (either directly or inherited). PR: 32414 Submitted by: David C Lawrence <tale@dd.org>
* Default to WARNS=2.obrien2001-12-041-0/+1
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Zap a number of #ifdef sunos blocks, and all of the `register'iedowse2001-11-177-102/+53
| | | | keywords.
* Give a sensible error message when the filesystem to be dumped isiedowse2001-11-161-4/+7
| | | | | | | | | not listed in /etc/fstab. Previously, the user would be greeted with "DUMP: bad sblock magic number" when dump tried to parse the directory contents as an FFS filesystem. PR: bin/12789 Submitted by: Bob Willcox <bob@pmr.com>
* Make the protocol/dumprestore.h header match restore's idea of the dumpdillon2001-10-282-11/+28
| | | | | | | | header for the case where sizeof(time_t) != sizeof(int). dumprestore.h was embedding time_t when it should have been embedding int32_t. Use time_to_time32() and time32_to_time() to convert between the protocoll/file-format time and time_t.
* deltat declared time_t, msg("") call used %d (assumed time_t == int).dillon2001-10-281-1/+2
| | | | | | Changed deltat to be an int (result of delta time calculation). MFC after: 1 day
* SECURITY.ru2001-09-055-117/+15
| | | | | | | | Notify operators using wall(1)'s -g option. Drop ``setgid tty'' privilege. Obtained from: OpenBSD MFC after: 1 month
* Don't reinvent the wheel; use strptime(3).ru2001-09-041-44/+4
| | | | MFC after: 2 weeks
* Mark some functions as __printflike()kris2001-08-101-3/+3
| | | | MFC After: 1 week
* Sort options in DESCRIPTION.dd2001-07-151-14/+14
|
* Bump date for addition of -D.dd2001-07-151-1/+1
|
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* mdoc(7) police:ru2001-07-101-11/+25
| | | | | Restored .Pa for ``dumpdates'' (it's still a file). Also, removed duplicate ``file'' words.
* Add manual page and usage for dump -D (supplied by Dima Dorfman) (will alsodillon2001-07-092-10/+24
| | | | | | be MFC'd) Submitted by: Dima Dorfman <dima@unixfreak.org>
* Oops, forgot to add 'D' to the option morphing block.dillon2001-07-081-0/+1
|
* Add a -D option to dump, allowing the path for the /etc/dumpdates file to bedillon2001-07-081-2/+6
| | | | | | | changed, so independant entities backing up the same thing to different media can be made not to trip over each other. MFC after: 3 days
* Convert two instances of a lseek()+read() combination to a pread().mikeh2001-07-011-8/+4
| | | | | PR: bin/17640 MFC after: 2 weeks
* Since we use getopt (in rev. 1.12), there's no need for the case's fordd2001-06-091-2/+0
| | | | | | | | the individual options to increment argv and decrement argc. This caused the -T option to swallow an extra argument. PR: 27982 Submitted by: Samuel Greear <sgreear@vsni.com>
* Fix bogon with the nodump flag.jkh2001-04-191-5/+10
| | | | Submitted by: Dima Dorfman <dima@unixfreak.org>
* Remove two lint directives that aren't needed since rev 1.5.obrien2001-03-301-2/+0
|
* Make rev 1.5 better match the rest of dump(8)'s output.obrien2001-03-271-2/+2
|
* Do not exit if unable to read /etc/dumpdates or create it.obrien2001-03-271-2/+4
| | | | | | If one is trying to dump or repair an ill system, give the user a fighting chance. Refusing to operate w/o a very non-critical file (feature) is just plain stupid.
OpenPOWER on IntegriCloud