Lines Matching +full:slice +full:- +full:per +full:- +full:line

9 ufsdump \- incremental file system dump
24 mounted read-only. Attempting to dump a mounted, read-write file system might
27 you need a point-in-time image of a file system that is mounted.
32 a non-root user might result in the creation of an inconsistent dump.
35 \fIoptions\fR is a single string of one-letter \fBufsdump\fR options.
45 line. See \fBOPERANDS\fR for more information.
48 With most devices \fBufsdump\fR can automatically detect the end-of-media.
50 multi-volume dumps, unless \fBufsdump\fR does not understand the way the device
51 detects the end-of-media, or the files are to be restored on a system with an
79 Archive file. Archive a dump table-of-contents in the specified
92 blocks per write for tapes of density less than 6250BPI (bytes-per-inch). The
96 blocking factor is specified in terms of 512-byte blocks, for compatibility
107 Cartridge. Set the defaults for cartridge instead of the standard half-inch
109 \fBufsdump\fR can automatically detect the end-of-media, only the blocking
123 Tape density. Not normally required, as \fBufsdump\fR can detect end-of-media.
124 This parameter can be used to keep a running tab on the amount of tape used per
126 cartridge tape, in which case it is assumed to be 1000BPI per track. Typical
190 Autoload. When the end-of-tape is reached before the dump is complete, take the
208 \fBIBM\fR or \fBANSI\fR-standard tape labels.
235 contain no white space as defined in \fBscanf\fR(3C) and is case-sensitive.
245 Offline. Take the drive offline when the dump is complete or the end-of-media
260 \fBufsdump\fR can detect end-of-media. When the specified size is reached,
263 number of 1024-byte blocks for diskettes. The values should be a little smaller
264 than the actual physical size of the media (for example, 425 for a 450-foot
280 \fB60-Mbyte 1/4 inch cartridge\fR
290 \fB150-Mbyte 1/4 inch cartridge\fR
304 1422 blocks (Corresponds to a 1.44-Mbyte diskette, with one cylinder reserved
331 \fBufsdump\fR can detect end-of-media. The default is 9 tracks. The \fBt\fR
332 option is not compatible with the \fBD\fR option. Values for Sun-supported tape
337 \fB60-Mbyte 1/4 inch cartridge\fR
347 \fB150-Mbyte 1/4 inch cartridge\fR
437 running \fBufsdump\fR, as well as any explicitly-named files, are dumped. This
440 \fB-u\fR option has been specified. In all cases, the files must be contained
445 line.
462 on a 150-MByte cartridge tape unit \fB0\fR:
592 .SS "Process Per Reel"
614 performing a full dump, bring the machine down to single-user mode using
617 running in single-user mode.
628 backed-up version of a file can be located and restored. The following
629 four-week schedule offers a reasonable tradeoff between these goals.
656 Most disks contain one or more overlapping slices because slice 2 covers the
658 For example, a common configuration places \fBroot\fR on slice 0, \fBswap\fR on
659 slice 1, \fB/opt\fR on slice 5 and \fB/usr\fR on slice 6.
663 time. Given the above scenario where slice 0 and slice 2 have the same starting
664 offset, executing \fBufsdump\fR on slice 2 with the intent of dumping the
665 entire disk would instead dump only the \fBroot\fR file system on slice 0. To
666 dump the entire disk, the user must dump the file systems on each slice