diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.xml b/en_US.ISO8859-1/books/handbook/disks/chapter.xml index b92339ed4c..fb95cb5eb6 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.xml @@ -51,19 +51,11 @@ How to create and burn CDs and DVDs on &os;. - - The various storage media options for backups. - - How to use the backup programs available under &os;. - - How to backup to floppy disks. - - What file system snapshots are and how to use them efficiently. @@ -84,7 +76,7 @@ Device Names The following is a list of physical storage devices - supported in &os;, and their associated device names. + supported in &os; and their associated device names. Physical Disk Naming Conventions @@ -100,14 +92,27 @@ IDE hard drives - ad + ad or + ada - IDE CDROM drives - acd + IDE CD-ROM drives + acd or + cd + + SATA hard drives + ad or + ada + + + + SATA CD-ROM drives + acd or + cd + SCSI hard drives and USB Mass storage devices @@ -115,12 +120,12 @@ - SCSI CDROM drives + SCSI CD-ROM drives cd - Assorted non-standard CDROM drives + Assorted non-standard CD-ROM drives mcd for Mitsumi CD-ROM and scd for Sony CD-ROM devices @@ -242,362 +247,6 @@ &prompt.root; mount /newdisk - - RAID - - - Software RAID - - - - - - Christopher - Shumway - Original work by - - - - - - Jim - Brown - Revised by - - - - - Concatenated Disk Driver (CCD) Configuration - - RAIDsoftware - RAIDCCD - - When choosing a mass storage solution, the most - important factors to consider are speed, reliability, and - cost. It is rare to have all three in balance. Normally a - fast, reliable mass storage device is expensive, and to cut - back on cost either speed or reliability must be - sacrificed. - - In designing the system described below, cost was - chosen as the most important factor, followed by speed, - then reliability. Data transfer speed for this system is - ultimately constrained by the network. While reliability is - very important, the CCD drive described below serves online - data that is already fully backed up and which can easily be - replaced. - - Defining the requirements is the first step in choosing - a mass storage solution. If the requirements prefer speed - or reliability over cost, the solution will differ from the - system described in this section. - - - Installing the Hardware - - In addition to the IDE system disk, three Western - Digital 30GB, 5400 RPM IDE disks form the core of the CCD - disk described below, providing approximately 90GB of - online storage. Ideally, each IDE disk would have its own - IDE controller and cable, but to minimize cost, additional - IDE controllers were not used. Instead, the disks were - configured with jumpers so that each IDE controller has - one master, and one slave. - - Upon reboot, the system BIOS was configured to - automatically detect the disks attached. More - importantly, &os; detected them on reboot: - - ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33 -ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33 -ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33 -ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 - - If &os; does not detect all the disks, consult - the drive documentation for proper setup and verify - that the controller is supported by &os;. - - - - Setting Up the CCD - - The &man.ccd.4; driver takes several identical disks - and concatenates them into one logical file system. In - order to use &man.ccd.4;, its kernel module must be - loaded using &man.ccd.4;. When using a custom kernel, - ensure that this line is compiled in: - - device ccd - - Before configuring &man.ccd.4;, use &man.bsdlabel.8; - to label the disks: - - bsdlabel -w ad1 auto -bsdlabel -w ad2 auto -bsdlabel -w ad3 auto - - This example creates a bsdlabel for - ad1c, - ad2c and - ad3c that spans the entire - disk. - - The next step is to change the disk label type. Use - &man.bsdlabel.8; to edit the disks: - - bsdlabel -e ad1 -bsdlabel -e ad2 -bsdlabel -e ad3 - - This opens up the current disk label on each disk with - the editor specified by the EDITOR - environment variable, typically &man.vi.1;. - - An unmodified disk label will look something like - this: - - 8 partitions: -# size offset fstype [fsize bsize bps/cpg] - c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) - - Add a new e partition for - &man.ccd.4; to use. This can usually be copied from the - c partition, but the - must be - 4.2BSD. The disk label should now - look something like this: - - 8 partitions: -# size offset fstype [fsize bsize bps/cpg] - c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) - e: 60074784 0 4.2BSD 0 0 0 # (Cyl. 0 - 59597) - - - - Building the File System - - Now that all the disks are labeled, build the - &man.ccd.4; using &man.ccdconfig.8;, with options similar - to the following: - - ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e - - The use and meaning of each option is described - below: - - - - The first argument is the device to configure, in - this case, /dev/ccd0c. The - /dev/ portion is optional. - - - - The interleave for the file system, which defines - the size of a stripe in disk blocks, each normally 512 - bytes. So, an interleave of 32 would be 16,384 - bytes. - - - - Flags for &man.ccdconfig.8;. For example, to - enable drive mirroring, specify a flag. This - configuration does not provide mirroring for - &man.ccd.4;, so it is set at 0 (zero). - - - - The final arguments to &man.ccdconfig.8; are the - devices to place into the array. Use the complete - path name for each device. - - - - After running &man.ccdconfig.8; the &man.ccd.4; is - configured and a file system can be installed. Refer to - &man.newfs.8; for options, or run: - - newfs /dev/ccd0c - - - - Making it All Automatic - - Generally, &man.ccd.4; should be configured to - automount upon each reboot. To do this, write out the - current configuration to - /etc/ccd.conf using the following - command: - - ccdconfig -g > /etc/ccd.conf - - During reboot, the script /etc/rc - runs ccdconfig -C if - /etc/ccd.conf exists. This - automatically configures the &man.ccd.4; so it can be - mounted. - - - When booting into single user mode, the following - command must be issued to configure the array before - the &man.ccd.4; can be mounted: - - ccdconfig -C - - - To automatically mount the &man.ccd.4;, place an entry - for the &man.ccd.4; in /etc/fstab so - it will be mounted at boot time: - - /dev/ccd0c /media ufs rw 2 2 - - - - - The Vinum Volume Manager - - - RAID - software - - - RAID - Vinum - - - The Vinum Volume Manager is a block device driver which - implements virtual disk drives. It isolates disk hardware - from the block device interface and maps data in ways which - result in an increase in flexibility, performance and - reliability compared to the traditional slice view of disk - storage. &man.vinum.4; implements the RAID-0, RAID-1 and - RAID-5 models, both individually and in combination. - - Refer to for more - information about &man.vinum.4;. - - - - - Hardware RAID - - - RAID - hardware - - - &os; also supports a variety of hardware - RAID controllers. These devices control a - RAID subsystem without the need for &os; - specific software to manage the array. - - Using an on-card BIOS, the card - controls most of the disk operations. The following is a - brief setup description using a Promise - IDE RAID controller. - When this card is installed and the system is started up, it - displays a prompt requesting information. Follow the - instructions to enter the card's setup screen and to combine - all the attached drives. After doing so, the disks will - look like a single drive to &os;. Other - RAID levels can be set up - accordingly. - - - - Rebuilding ATA RAID1 Arrays - - &os; supports the ability to hot-replace a failed disk in - an array. - - An error indicating a failed disk will appear in - /var/log/messages or in the &man.dmesg.8; - output: - - ad6 on monster1 suffered a hard error. -ad6: READ command timeout tag=0 serv=0 - resetting -ad6: trying fallback to PIO mode -ata3: resetting devices .. done -ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11)\\ -status=59 error=40 -ar0: WARNING - mirror lost - - Use &man.atacontrol.8; to check for further - information: - - &prompt.root; atacontrol list -ATA channel 0: - Master: no device present - Slave: acd0 <HL-DT-ST CD-ROM GCR-8520B/1.00> ATA/ATAPI rev 0 - -ATA channel 1: - Master: no device present - Slave: no device present - -ATA channel 2: - Master: ad4 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 - Slave: no device present - -ATA channel 3: - Master: ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 - Slave: no device present - -&prompt.root; atacontrol status ar0 -ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED - - - - First, detach the ata channel with the failed disk - so that it can be safely removed: - - &prompt.root; atacontrol detach ata3 - - - - Replace the disk. - - - - Reattach the ata channel: - - &prompt.root; atacontrol attach ata3 -Master: ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 -Slave: no device present - - - - Add the new disk to the array as a spare: - - &prompt.root; atacontrol addspare ar0 ad6 - - - - Rebuild the array: - - &prompt.root; atacontrol rebuild ar0 - - - - It is possible to check on the progress by issuing the - following command: - - &prompt.root; dmesg | tail -10 -[output removed] -ad6: removed from configuration -ad6: deleted from ar0 disk1 -ad6: inserted into ar0 disk1 as spare - -&prompt.root; atacontrol status ar0 -ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed - - - - Wait until this operation completes. - - - - - @@ -794,7 +443,7 @@ umass0: detached Creating and Using CD Media - CDROMs + CD-ROMs creating @@ -912,7 +561,7 @@ umass0: detached of ways. - CDROMs + CD-ROMs creating bootable The last option of general use is . @@ -955,7 +604,7 @@ umass0: detached <application>burncd</application> - CDROMs + CD-ROMs burning For an ATAPI CD burner, burncd can be @@ -1001,7 +650,7 @@ umass0: detached results like this: - CDROMs + CD-ROMs burning &prompt.root; cdrecord -scanbus @@ -1122,8 +771,8 @@ scsibus1: It is possible to copy a data CD to an image file that is functionally equivalent to the image file created with &man.mkisofs.8;, and then use it to duplicate any data CD. - The example given here assumes that the CDROM device is - acd0. Substitute the correct CDROM + The example given here assumes that the CD-ROM device is + acd0. Substitute the correct CD-ROM device. &prompt.root; dd if=/dev/acd0 of=file.iso bs=2048 @@ -1149,7 +798,7 @@ scsibus1: &man.mount.8; that the file system is of type ISO9660 by specifying to &man.mount.8;. For example, - to mount the CDROM device, /dev/cd0, + to mount the CD-ROM device, /dev/cd0, under /mnt, use: @@ -1162,7 +811,7 @@ scsibus1: &prompt.root; mount_cd9660 /dev/cd0 /mnt - While data CDROMs from any vendor can be mounted this way, + While data CD-ROMs from any vendor can be mounted this way, disks with certain ISO 9660 extensions might behave oddly. For example, Joliet disks store all filenames in two-byte Unicode characters. The &os; kernel does not speak Unicode, @@ -1186,13 +835,13 @@ scsibus1: Occasionally, Device not configured - will be displayed when trying to mount a CDROM. This - usually means that the CDROM drive thinks that there is no + will be displayed when trying to mount a CD-ROM. This + usually means that the CD-ROM drive thinks that there is no disk in the tray, or that the drive is not visible on the bus. - It can take a couple of seconds for a CDROM drive to realize + It can take a couple of seconds for a CD-ROM drive to realize that a media is present, so be patient. - Sometimes, a SCSI CDROM may be missed because it did not + Sometimes, a SCSI CD-ROM may be missed because it did not have enough time to answer the bus reset. To resolve this,add the following option to the kernel configuration and rebuild the @@ -1201,7 +850,7 @@ scsibus1: options SCSI_DELAY=15000 This tells the SCSI bus to pause 15 seconds during boot, - to give the CDROM drive every possible chance to answer the + to give the CD-ROM drive every possible chance to answer the bus reset. @@ -1220,7 +869,7 @@ scsibus1: &prompt.root; tar xzvf /dev/acd1 - This type of disk can not be mounted as a normal CDROM and + This type of disk can not be mounted as a normal CD-ROM and the data cannot be read under any operating system except &os;. In order to mount the CD, or to share the data with another operating system, &man.mkisofs.8; must be used as @@ -1968,105 +1617,6 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - - Backups to Floppies - - - Can I Use Floppies for Backing Up My Data? - - backup floppies - floppy disks - - Floppy disks are not a suitable media for making backups - as: - - - - The media is unreliable, especially over long periods - of time. - - - - Backing up and restoring is very slow. - - - - They have a very limited capacity. - - - - However, if no other method of backing up data is - available, floppy disks are better than no backup at - all. - - When backing up to floppy disks, ensure the floppies are - of good quality. Floppies that have been lying around the - office for a couple of years are a bad choice. Ideally, - use new ones from a reputable manufacturer. - - - - So How Do I Backup My Data to Floppies? - - The best way to backup to floppy disk is to use - &man.tar.1; with (multi-volume), which - allows backups to span multiple floppies. - - To backup all the files in the current directory and - sub-directory, use this as root: - - &prompt.root; tar Mcvf /dev/fd0 * - - When the first floppy is full, &man.tar.1; will prompt - to insert the next volume, which in this case is the next - floppy disk: - - Prepare volume #2 for /dev/fd0 and hit return: - - This is repeated, with the volume number incrementing, - until all the specified files have been archived. - - - - Can I Compress My Backups? - - - tar - - - gzip - - compression - - Unfortunately, &man.tar.1; does not support - for multi-volume archives. Instead, - &man.gzip.1; all the files, &man.tar.1; them to the floppies, - then &man.gunzip.1; the files. - - - - How Do I Restore My Backups? - - To restore the entire archive use: - - &prompt.root; tar Mxvf /dev/fd0 - - There are two methods to restore only specific files. The - first is to insert the first floppy and use: - - &prompt.root; tar Mxvf /dev/fd0 filename - - &man.tar.1; will prompt to insert subsequent floppies - until it finds the required file. - - Alternatively, if the floppy containing the file is known, - insert that floppy and use the same command. If the first - file on the floppy is a continuation from the previous one, - &man.tar.1; will warn that it cannot restore it, even if you - have not asked it to. - - - @@ -2476,7 +2026,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Livefs CD images are not available for &os; &rel.current;-RELEASE and later. In addition to - the CDROM installation images, flash drive installation + the CD-ROM installation images, flash drive installation images may be used to recover a system. The memstick image for &os;/&arch.i386; &rel.current;-RELEASE is available @@ -2517,10 +2067,10 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c livefs CD and boot the computer. The original install menu will be displayed on the screen. Select the correct country, then choose - Fixit -- Repair mode with CDROM/DVD/floppy or + Fixit -- Repair mode with CD-ROM/DVD/floppy or start a shell. then select - CDROM/DVD -- Use the live filesystem - CDROM/DVD. + CD-ROM/DVD -- Use the live filesystem + CD-ROM/DVD. restore and the other needed programs are located in /mnt2/rescue.