summaryrefslogtreecommitdiffstats
path: root/sbin/restore
Commit message (Collapse)AuthorAgeFilesLines
* rscid -> __FBSDID. Mark parameter as __unused when necessary.charnier2005-05-294-9/+13
|
* Remove debug from last commitimp2005-04-031-2/+0
|
* /*-imp2005-04-031-1/+1
|
* Revert bogus += -g change. I needed it to debug the problem.imp2005-03-251-1/+0
| | | | Noticed by: njl, Andrej Tobola
* Restore the ability to read FreeBSD 1 tapes (and I think any net2imp2005-03-253-0/+24
| | | | | | | | | | | | | | | based tapes, but I'm not sure where NFS_MAGIC was introduced after 4.3). When support for the pre-4.4 format was removed (the ability to read 4.2 and 4.3 BSD tapes), the old format inode conversion was junked as well. However, FreeBSD 1 dump tapes use the NFS_MAGIC format, but have this inode format. Before, restore would fail complaining that '.' wasn't found and the root directory wasn't on this tape. Since the conversion from the not so old format is relatively trivial, restore the code to make that conversion. FreeBSD 1 dumps are once again readable. MFC After: a few days
* dcvt is unused since the support for converting pre-4.4 tapes wasimp2005-03-252-25/+3
| | | | | | | removed. Go ahead and remove it and struct odirent since it too is unused. # FreeBSD 1.1.5 tapes are still unreadable, but 2.0 and newer work.
* c_tapea and c_firstrec are used for TS_TAPE blocks, so convert themimp2005-03-251-0/+2
| | | | | | | | | for the old (4.4-lite through FreeBSD 4.x and *BSD) format. It looks like they aren't used for TS_INODE, but conversion costs so little there that I've not removed them there (in case my grep was wrong). This makes at least some of the tapes work for me again. Now, to regresion test all my dusty tapes...
* In order to print out the dump dates correctly, the date and ddate fieldsimp2005-03-181-0/+4
| | | | also need to be convereted for old tapes for records of type TAPE.
* Sync usage and man page with reality. There's no '-c' command lineimp2005-03-182-19/+10
| | | | | flag today. Maybe we should still retain it, but I'll let others fight that windmill.
* Expand *n't contractions.ru2005-02-131-1/+1
|
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-4/+4
|
* Sort sections.ru2005-01-181-23/+23
|
* Mechanically kill hard sentence breaks.ru2004-07-021-4/+8
|
* Use the correct types for the functions rst_opendir(), glob_readdir() andstefanf2004-05-243-9/+11
| | | | | | | rst_closedir() which are called by glob(). Reviewed by: md5 Approved by: das (mentor)
* Include <timeconv.h> for time conversion functions.stefanf2004-05-241-0/+1
| | | | Approved by: das (mentor)
* Assorted markup, grammar, and spelling fixes.ru2004-05-171-1/+1
|
* Add -P arguments for dump(8) and restore(8) which allow the user togreen2004-04-134-19/+92
| | | | | | | | | | | 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
* Remove advertising clause from University of California Regent's license,markm2004-04-0910-40/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* style.Makefile(5):johan2004-02-231-1/+1
| | | | Use WARNS?= instead of WARNS=.
* Fix gcc warnings. If NAME_MAX is 255, and d_namlen is a uint8_t, thenpeter2003-10-261-2/+7
| | | | | d_namlen can never be > NAME_MAX. Stop gcc worrying about this by using a preprocessor test to see if NAME_MAX changes.
* Localize 'ls' outputache2003-08-062-4/+8
| | | | Don't set 8bit in quote processing
* Add section number to .Xrcharnier2003-06-081-1/+1
|
* Removed all vestiges of KerberosIV.ru2003-05-013-14/+11
|
* Style.ru2003-05-011-2/+3
|
* De-Kerberise (KerberosIV). KerberosIV is no longer present, andmarkm2003-05-013-29/+0
| | | | | remote backups can still be done with Kerberos authentication using SSH and Kerberos 5.
* Add TAPE to the ENVIRONMENT section.sheldonh2003-01-101-0/+2
| | | | MFC after: 1 month
* Add an ENVIRONMENT section so that the reader knows that the TMPDIR envarsheldonh2003-01-101-0/+5
| | | | | | | is honoured. Reported by: des MFC after: 1 month
* Fixed the abuses of .Ql visible on stderr in troff mode.ru2002-12-231-1/+1
| | | | PR: docs/37176
* Use the standardized CHAR_BIT constant instead of NBBY in userland.mike2002-09-258-2/+11
|
* Replace various spelling with FALLTHROUGH which is lint()ablecharnier2002-08-252-3/+3
|
* Use '0' instead of NULL when we mean the integer constant 0 and not aimp2002-08-211-1/+1
| | | | "null pointer expression".
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-215-21/+21
|
* Change utimes to set the file creation time (for filesystems thatmckusick2002-07-173-15/+33
| | | | | | | | 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.
* The .Nm utility.charnier2002-07-061-14/+19
|
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-215-240/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* more file system > filesystemtrhodes2002-05-166-21/+22
|
* Address a few minor style and consistency issues in revision 1.32.iedowse2002-05-061-23/+15
| | | | Submitted by: Joshua Goodall <joshua@roughtrade.net>
* Set the permissions on restored symbolic links.iedowse2002-05-021-1/+19
| | | | | PR: bin/37665 Submitted by: "Michael C. Adler" <mad1@tapil.com>
* 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.
* restore(8) manual page does not explain rrestore.trhodes2002-04-121-0/+4
| | | | | PR: 34234 Submitted by: Gary W. Swearingen <swear@blarg.net>
* o remove __Pimp2002-03-208-385/+221
| | | | | o Use ANSI function definitions o unifdef -D__STDC__
* Remove 'register' keyword.obrien2002-03-206-77/+77
| | | | | | It does not help modern compilers, and some may take some hit from it. (I also found several functions that listed *every* of its 10 local vars with "register" -- just how many free registers do people think machines have?)
* Use a more robust scheme for determining how many blocks to skipiedowse2002-02-181-15/+18
| | | | | | | | | after an EOT-terminated volume. We keep track of the current record number, and synchronise it with the c_tapea field each time we read a header. Avoid the use of c_firstrec because some bugs in dump can cause it to be set incorrectly. Move the initialisation of some variables to avoid compiler warnings.
* When we reach the end of the dump in findinode(), ask for anotheriedowse2002-02-181-9/+19
| | | | | | | | | | volume if we missed some earlier tapes (the user can still enter 'none' later if the tapes are unavailable). Previously with 'x' restores, we might not ask for all tapes if the tapes are supplied in reverse order. Clarify the message that describes what volume should be mounted first; reverse order is only efficient when extracting a few files.
* In createfiles(), properly handle a number of cases where no furtheriedowse2002-02-141-16/+24
| | | | | | | | | | | | | | | | | | | | | volumes are available, instead of getting stuck in a loop calling getvol(). Normally restore in 'x' or 'i' modes will ask for a new (earlier) volume when the current inode number on the tape is greater than the last inode to be restored, since there can be no further inodes of interest on that volume. However we don't want to change volumes in this case either if the user explicitly said that there are no more tapes, or if we are looking at the first volume. When no more volumes are available but there are still inodes that we have not found, we now just fall through to the code that prints out a list of any missing files, so the restore completes normally. Also simplify the logic a bit by always returning to the start of the main for(;;) loop whenever the volume has changed. This should completely fix the "Changing volumes on pipe input" bug that is often observed when restoring dumps of active filesystems. PR: bin/4176, bin/34604, misc/34675
* Fix a number of long-standing restore bugs in tape.c, mainly relatingiedowse2002-02-131-18/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | to multi-volume restores: - In findinode(), keep a copy of header->c_type so that we don't exit the do-while loop until we have processed the current header. Exiting too early leaves curfile.ino set to 0, which confuses the logic in createfiles(), so multi-volume restores with the 'x' command don't work if you follow the instructions and supply the tapes in reverse order. This appears to have been broken by CSRG revision 5.33 tape.c (Oct 1992). - The logic in getvol() for deciding how many records to skip after the volume header was confused; sometimes it would skip too few records and sometimes too many, leading to "resync restore" warnings and missing files. Skip to the next header only when the current action is not `USING'. Work around a dump bug that sets c_count incorrectly in the volume header of the first tape. Some of the problems here date back to at least 1991. - Back out revision 1.23. This appeared to avoid warnings about missing files in the 'rN' verification case, but it made the problems with the 'x' command worse by stopping getvol() from even attempting to find the first inode number on the newly inserted tape. The bug it addressed is fixed by correcting the skipping logic as described above. - Save the value of `tpblksread' in case the wrong volume is supplied, because it is incremented each time we read a volume header. We already saved `blksread' for the same reson.
* Don't refer to findinode()'s `complain' parameter in a comment; itiedowse2002-02-121-1/+1
| | | | was removed in 1986.
* I've been meaning to do this for a while. Add an underscore to thedillon2002-01-191-9/+9
| | | | | | | | 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.
* Default to WARNS=2.obrien2001-12-041-0/+1
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Fix a bug where restore(8) segfaults while trying to restore on atobez2001-10-301-0/+1
| | | | | | | | read-only FS. Reviewed by: audit silence Approved by: markm MFC after: 2 weeks
OpenPOWER on IntegriCloud