From 360a6ebf990f3ff4219ae8037a34cc0555075e79 Mon Sep 17 00:00:00 2001 From: Warren Block Date: Wed, 8 Jan 2014 18:58:16 +0000 Subject: [PATCH] Whitespace-only fixes, translators please ignore. --- .../books/handbook/disks/chapter.xml | 615 +++++++++++------- 1 file changed, 379 insertions(+), 236 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.xml b/en_US.ISO8859-1/books/handbook/disks/chapter.xml index 29483496cb..1e2f061afd 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.xml @@ -4,16 +4,19 @@ $FreeBSD$ --> - + + + Storage Synopsis - This chapter covers the use of disks in &os;. This - includes memory-backed disks, network-attached disks, - standard SCSI/IDE storage devices, and devices using the USB - interface. + This chapter covers the use of disks in &os;. This includes + memory-backed disks, network-attached disks, standard SCSI/IDE + storage devices, and devices using the USB interface. After reading this chapter, you will know: @@ -112,6 +115,7 @@ acd or cd + SCSI hard drives and USB Mass storage devices @@ -165,14 +169,19 @@ - Adding Disks - - DavidO'BrienOriginally contributed by - - - + + Adding Disks - + + + + David + O'Brien + + Originally contributed by + + + disks @@ -183,8 +192,9 @@ SATA disk to a machine that currently only has a single drive. First, turn off the computer and install the drive in the computer following the instructions of the - computer, controller, and drive manufacturers. Reboot - the system and become root. + computer, controller, and drive manufacturers. Reboot the + system and become + root. Inspect /var/run/dmesg.boot to ensure the new disk was found. In this example, the newly added @@ -197,7 +207,8 @@ For this example, a single large partition will be created - on the new disk. The + on the new disk. The GPT partitioning scheme will be used in preference to the older and less versatile MBR scheme. @@ -242,14 +253,19 @@ - USB Storage Devices - - MarcFonvieilleContributed by - - - + + USB Storage Devices - + + + + Marc + Fonvieille + + Contributed by + + + USB @@ -263,9 +279,9 @@ Configuration - The USB mass storage devices driver, &man.umass.4;, - is built into the GENERIC kernel - and provides support for USB storage devices. For a custom + The USB mass storage devices driver, &man.umass.4;, is + built into the GENERIC kernel and + provides support for USB storage devices. For a custom kernel, be sure that the following lines are present in the kernel configuration file: @@ -337,8 +353,9 @@ da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) To make the device mountable as a normal user, one solution is to make all users of the device a member of the - operator group using &man.pw.8;. - Next, ensure that the operator group is + operator group + using &man.pw.8;. Next, ensure that the + operator group is able to read and write the device by adding these lines to /etc/devfs.rules: @@ -354,7 +371,8 @@ add path 'da*' mode 0660 group operator This will exclude the first three SCSI disks (da0 to da2)from belonging to the - operator group. + operator + group. Next, enable the &man.devfs.rules.5; ruleset in @@ -375,12 +393,12 @@ add path 'da*' mode 0660 group operator The final step is to create a directory where the file system is to be mounted. This directory needs to be owned by the user that is to mount the file system. One way to do that - is for root to create a subdirectory - owned by that user as /mnt/username. - In the following example, replace - username with the login name of the - user and usergroup with the user's - primary group: + is for root to + create a subdirectory owned by that user as + /mnt/username. In the following example, + replace username with the login + name of the user and usergroup with + the user's primary group: &prompt.root; mkdir /mnt/username &prompt.root; chown username:usergroup /mnt/username @@ -417,14 +435,19 @@ umass0: detached - Creating and Using CD Media - - MikeMeyerContributed by - - - + + Creating and Using CD Media - + + + + Mike + Meyer + + Contributed by + + + CD-ROMs @@ -476,18 +499,17 @@ umass0: detached Which tool to use to burn the CD depends on whether the CD burner is ATAPI or something else. ATAPI CD burners use - burncd - which is part of the base system. SCSI and USB CD burners - should use cdrecord from the - sysutils/cdrtools port. - It is also possible to use cdrecord and other tools - for SCSI drives on ATAPI hardware with the ATAPI/CAM module. + burncd which is part of the base system. + SCSI and USB CD burners should use cdrecord + from the sysutils/cdrtools port. It is + also possible to use cdrecord and other + tools for SCSI drives on ATAPI hardware with the + ATAPI/CAM module. For CD burning software with a graphical user interface, consider X-CD-Roast or K3b. These tools are available as - packages or from the - sysutils/xcdroast and + packages or from the sysutils/xcdroast and sysutils/k3b ports. X-CD-Roast and K3b require the @@ -549,15 +571,16 @@ umass0: detached in producing an El Torito bootable CD. This option takes an argument which is the path to a boot image from the top of the tree being written to the CD. By default, - &man.mkisofs.8; creates an ISO image in floppy disk - emulation mode, and thus expects the boot image to - be exactly 1200, 1440 or 2880 KB in size. Some boot - loaders, like the one used by the &os; distribution disks, do - not use emulation mode. In this case, + &man.mkisofs.8; creates an ISO image in + floppy disk emulation mode, and thus expects + the boot image to be exactly 1200, 1440 or 2880 KB in + size. Some boot loaders, like the one used by the &os; + distribution disks, do not use emulation mode. In this case, should be used. So, if - /tmp/myboot holds a - bootable &os; system with the boot image in /tmp/myboot/boot/cdboot, this - command would produce the image of an ISO 9660 file system as + /tmp/myboot holds a bootable &os; system + with the boot image in + /tmp/myboot/boot/cdboot, this command + would produce the image of an ISO 9660 file system as /tmp/bootable.iso: &prompt.root; mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot @@ -569,8 +592,8 @@ umass0: detached &prompt.root; mdconfig -a -t vnode -f /tmp/bootable.iso -u 0 &prompt.root; mount -t cd9660 /dev/md0 /mnt - One can then verify that /mnt and /tmp/myboot are - identical. + One can then verify that /mnt and + /tmp/myboot are identical. There are many other options available for &man.mkisofs.8; to fine-tune its behavior. Refer to @@ -606,11 +629,12 @@ umass0: detached For systems without an ATAPI CD burner, cdrecord can be used to burn CDs. cdrecord is not part of the base system and - must be installed from either the sysutils/cdrtools package or port. - Changes to the base system can cause binary versions of this - program to fail, possibly resulting in a - coaster. It is recommended to either upgrade - the port when the system is upgraded, or for users + must be installed from either the + sysutils/cdrtools package or port. Changes + to the base system can cause binary versions of this program + to fail, possibly resulting in a coaster. It + is recommended to either upgrade the port when the system is + upgraded, or for users tracking -STABLE, to upgrade the port when a new version becomes available. @@ -686,7 +710,8 @@ scsibus1: &prompt.user; cdrecord -v dev=2,0 -dao -useinfo *.wav Make sure that 2,0 is set - appropriately, as described in . + appropriately, as described in + . @@ -786,11 +811,11 @@ scsibus1: &prompt.root; mount_cd9660 /dev/cd0 /mnt - 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, - but the &os; CD9660 driver is able to convert Unicode + 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, but the &os; CD9660 driver is able to convert Unicode characters on the fly. If some non-English characters show up as question marks, specify the local charset with . For more information, refer to @@ -817,8 +842,9 @@ scsibus1: that a media is present, so be patient. 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 + have enough time to answer the bus reset. To resolve this, + add the following option to the kernel configuration and + rebuild the kernel. options SCSI_DELAY=15000 @@ -843,22 +869,28 @@ scsibus1: &prompt.root; tar xzvf /dev/acd1 - This type of disk can not be mounted as a normal CD-ROM and - the data cannot be read under any operating system except + 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 described above. - Using the ATAPI/CAM Driver + + Using the ATAPI/CAM Driver + - MarcFonvieilleContributed by + + + Marc + Fonvieille + + Contributed by + - - CD burner ATAPI/CAM driver @@ -911,8 +943,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c &prompt.root; mount -t cd9660 /dev/cd0 /mnt - As root, run the following command - to get the SCSI address of the burner: + As root, run the + following command to get the SCSI address of the + burner: &prompt.root; camcontrol devlist <MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0) @@ -927,17 +960,28 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - Creating and Using DVD Media - - MarcFonvieilleContributed by - - - AndyPolyakovWith inputs from - - - + + Creating and Using DVD Media - + + + + Marc + Fonvieille + + Contributed by + + + + + + Andy + Polyakov + + With inputs from + + + DVD @@ -1009,8 +1053,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Configuration To perform DVD recording, use &man.growisofs.1;. This - command is part of the sysutils/dvd+rw-tools utilities - which support all DVD media types. + command is part of the + sysutils/dvd+rw-tools utilities which + support all DVD media types. These tools use the SCSI subsystem to access the devices, therefore ATAPI/CAM support @@ -1026,13 +1071,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c hw.ata.atapi_dma="1" Before attempting to use - dvd+rw-tools, consult the - Hardware + dvd+rw-tools, consult the Hardware Compatibility Notes. - For a graphical user interface, consider using sysutils/k3b which provides a - user friendly interface to &man.growisofs.1; and many other + For a graphical user interface, consider using + sysutils/k3b which provides a user + friendly interface to &man.growisofs.1; and many other burning tools. @@ -1040,7 +1086,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Burning Data DVDs - Since &man.growisofs.1; is a front-end to mkisofs, it will invoke + Since &man.growisofs.1; is a front-end to + mkisofs, it will invoke &man.mkisofs.8; to create the file system layout and perform the write on the DVD. This means that an image of the data does not need to be created before the burning process. @@ -1098,11 +1145,12 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c additional options are required for &man.growisofs.1; to burn that image on a disk. - Be sure to use an up-to-date version of sysutils/cdrtools, which - contains &man.mkisofs.8;, as an older version may not - contain large files support. If the latest version does - not work, install sysutils/cdrtools-devel and read - its &man.mkisofs.8;. + Be sure to use an up-to-date version of + sysutils/cdrtools, which contains + &man.mkisofs.8;, as an older version may not contain large + files support. If the latest version does not work, install + sysutils/cdrtools-devel and read its + &man.mkisofs.8;. @@ -1117,14 +1165,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c A DVD-Video is a specific file layout based on the ISO 9660 and micro-UDF (M-UDF) specifications. Since DVD-Video presents a specific data structure hierarchy, a particular - program such as multimedia/dvdauthor is needed to - author the DVD. + program such as multimedia/dvdauthor is + needed to author the DVD. If an image of the DVD-Video file system already exists, it can be burned in the same way as any other image. If dvdauthor was used to make the DVD and the - result is in /path/to/video, the following - command should be used to burn the DVD-Video: + result is in /path/to/video, the + following command should be used to burn the DVD-Video: &prompt.root; growisofs -Z /dev/cd0 -dvd-video /path/to/video @@ -1296,9 +1344,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c More information about dvd+rw-tools can be found in - &man.growisofs.1;, on the dvd+rw-tools - web site, and in the cdwrite mailing - list archives. + &man.growisofs.1;, on the dvd+rw-tools + web site, and in the cdwrite + mailing list archives. When creating a problem report related to the use of @@ -1357,18 +1407,29 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - Creating and Using Floppy Disks - - JulioMerinoOriginal work by - - - - MartinKarlssonRewritten by - - - + + Creating and Using Floppy Disks - + + + + Julio + Merino + + Original work by + + + + + + + Martin + Karlsson + + Rewritten by + + + Storing data on floppy disks is sometimes useful, for example when one does not have any other removable storage media @@ -1536,7 +1597,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Using &man.dump.8; and &man.restore.8; to Create and Restore Backups - A simple backup of /usr with &man.dump.8;: + A simple backup of /usr with + &man.dump.8;: &prompt.root; dump -0aL -b64 -f /dev/nsa0 /usr @@ -1560,14 +1622,19 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - Backup Strategies - - LowellGilbertOriginal work by - - - + + Backup Strategies - + + + + Lowell + Gilbert + + Original work by + + + The first requirement in devising a backup plan is to make sure that all of the following problems are covered: @@ -1617,12 +1684,13 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Copies of whole file systems or disks which can be - created with a periodic net/rsync of the whole machine. - This is generally most useful in networks with unique - requirements. For general protection against disk failure, - this is usually inferior to RAID. For - restoring accidentally deleted files, it can be comparable - to UFS snapshots. + created with a periodic net/rsync of the + whole machine. This is generally most useful in networks + with unique requirements. For general protection against + disk failure, this is usually inferior to + RAID. For restoring accidentally deleted + files, it can be comparable to UFS + snapshots. @@ -1682,9 +1750,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c dump does not write files and directories, but rather writes the raw data blocks that comprise files and directories. When used to extract data, - restore stores temporary - files in /tmp/ by - default. When using a recovery disk with a small /tmp, set + restore stores temporary files in + /tmp/ by default. When using a recovery + disk with a small /tmp, set TMPDIR to a directory with more free space in order for the restore to succeed. @@ -1768,7 +1836,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c tar To tar to an Exabyte tape drive - connected to a host called komodo: + connected to a host called + komodo: &prompt.root; tar cf - . | rsh komodo dd of=tape-device obs=20b @@ -1925,7 +1994,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c unwritable files, devices, files that change size during the backup, files that are created/deleted during the backup and more. She presented the results at LISA V in Oct. 1991. See - torture-testing + torture-testing Backup and Archive Programs. @@ -1954,7 +2024,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c &man.restore.8;, &man.fdisk.8;, &man.bsdlabel.8;, &man.newfs.8;, &man.mount.8;, and more. The livefs CD image for &os;/&arch.i386; &rel2.current;-RELEASE is - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. Livefs CD images are not available for @@ -1963,7 +2034,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c images may be used to recover a system. The memstick image for &os;/&arch.i386; &rel.current;-RELEASE is available - from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img. + from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img. Third, create backup tapes regularly. Any changes that @@ -2040,12 +2112,19 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - Network, Memory, and File-Backed File Systems + + Network, Memory, and File-Backed File Systems + - MarcFonvieilleReorganized and enhanced by + + + Marc + Fonvieille + + Reorganized and enhanced by + - virtual disks @@ -2054,8 +2133,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c In addition to physical disks such as floppies, CDs, and - hard drives, &os; also supports virtual - disks. + hard drives, &os; also supports + virtual disks. NFS Coda @@ -2235,14 +2314,19 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - File System Snapshots - - TomRhodesContributed by - - - + + File System Snapshots - + + + + Tom + Rhodes + + Contributed by + + + file systems @@ -2323,19 +2407,19 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - The frozen /var is - now available through /mnt. Everything will initially - be in the same state it was during the snapshot creation time. - The only exception is that any earlier snapshots will appear as - zero length files. To unmount the snapshot, use: + The frozen /var is now available + through /mnt. Everything will initially be + in the same state it was during the snapshot creation time. The + only exception is that any earlier snapshots will appear as zero + length files. To unmount the snapshot, use: &prompt.root; umount /mnt &prompt.root; mdconfig -d -u 4 For more information about and file system snapshots, including technical papers, visit - Marshall Kirk McKusick's website at - http://www.mckusick.com/. + Marshall Kirk McKusick's website at http://www.mckusick.com/. @@ -2365,13 +2449,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on options QUOTA - Before &os; 9.2, - the GENERIC kernel usually did not include this - option. sysctl kern.features.ufs_quota - can be used to test whether the current kernel supports - quotas. If the option is not present, a custom kernel must be - compiled. Refer to for more information on - kernel configuration. + Before &os; 9.2, the GENERIC + kernel usually did not include this option. + sysctl kern.features.ufs_quota can be used + to test whether the current kernel supports quotas. If the + option is not present, a custom kernel must be compiled. + Refer to for more information + on kernel configuration. Next, enable disk quotas in /etc/rc.conf: @@ -2510,11 +2594,11 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on Sometimes it is desirable to set quota limits on a range of UIDs. This can be done by passing to &man.edquota.8;. First, assign the desired quota limit to a - user, then run edquota -p protouser - startuid-enduid. For example, if - test has the desired quota limits, the - following command will duplicate those quota limits for UIDs - 10,000 through 19,999: + user, then run + edquota -p protouser startuid-enduid. For + example, if test has + the desired quota limits, the following command will duplicate + those quota limits for UIDs 10,000 through 19,999: &prompt.root; edquota -p test 10000-19999 @@ -2548,10 +2632,12 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on /usr/var 0 50 75 0 50 60 grace period + In this example, the user is currently 15 kbytes over the - soft limit of 50 kbytes on /usr and has 5 days of grace - period left. The asterisk * indicates that - the user is currently over the quota limit. + soft limit of 50 kbytes on /usr and has 5 + days of grace period left. The asterisk * + indicates that the user is currently over the quota + limit. Normally, file systems that the user is not using any disk space on will not show in the output of &man.quota.1;, even if @@ -2584,16 +2670,24 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - Encrypting Disk Partitions - - LuckyGreenContributed by -
shamrock@cypherpunks.to
- - - - + + Encrypting Disk Partitions - + + + + Lucky + Green + + Contributed by + +
+ shamrock@cypherpunks.to +
+ + + + disks @@ -2601,7 +2695,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on &os; offers excellent online protections against - unauthorized data access. File permissions and Mandatory Access Control (MAC) help + unauthorized data access. File permissions and + Mandatory Access Control (MAC) help prevent unauthorized users from accessing data while the operating system is active and the computer is powered up. However, the permissions enforced by the operating system are @@ -2725,7 +2820,8 @@ sector_size = 2048 gbde to protect data depends entirely on the quality of the passphrase. For tips on how to select a secure passphrase that is easy to - remember, see the Diceware + remember, see the Diceware Passphrase website. gbde initcreates a lock file for @@ -2828,7 +2924,8 @@ Filesystem Size Used Avail Capacity Mounted on After each boot, any encrypted file systems must be re-attached to the kernel, checked for errors, and mounted, before the file systems can be used. The required commands - must be executed as root. + must be executed as + root. @@ -2919,14 +3016,19 @@ gbde_lockdir="/etc/gbde" - Disk Encryption with <command>geli</command> - - DanielGerzoContributed by - - - + + Disk Encryption with <command>geli</command> - + + + + Daniel + Gerzo + + Contributed by + + + An alternative cryptographic GEOM class is available through &man.geli.8;. geli differs from @@ -3131,14 +3233,20 @@ geli_da2_flags="-p -k /root/da2.key" - Encrypting Swap Space + + Encrypting Swap Space + - ChristianBrüfferWritten by + + + Christian + Brüffer + + Written by + - - swap encrypting @@ -3147,12 +3255,12 @@ geli_da2_flags="-p -k /root/da2.key" Like the encryption of disk partitions, encryption of swap space is used to protect sensitive information. Consider an application that deals with passwords. As long as these - passwords stay in physical memory, these passwords will not - be written to disk and be cleared after a reboot. If &os; - starts swapping out memory pages to free - space for other applications, the passwords may be written to - the disk platters unencrypted. Encrypting swap space can be a - solution for this scenario. + passwords stay in physical memory, these passwords will not be + written to disk and be cleared after a reboot. If &os; starts + swapping out memory pages to free space for other applications, + the passwords may be written to the disk platters unencrypted. + Encrypting swap space can be a solution for this + scenario. The &man.gbde.8; or &man.geli.8; encryption systems may be used for swap encryption. Both systems use the @@ -3233,20 +3341,50 @@ Device 1K-blocks Used Avail Capacity - Highly Available Storage (HAST) - - DanielGerzoContributed by - - - FreddieCashWith inputs from - Pawel JakubDawidek - Michael W.Lucas - ViktorPetersson - - - + + Highly Available Storage (HAST) - + + + + Daniel + Gerzo + + Contributed by + + + + + + + Freddie + Cash + + With inputs from + + + + + Pawel Jakub + Dawidek + + + + + + Michael W. + Lucas + + + + + + Viktor + Petersson + + + + HAST @@ -3261,8 +3399,8 @@ Device 1K-blocks Used Avail Capacity a key component in such environments. Highly Available STorage, or HASTHighly Available STorage, was developed by - &a.pjd.email; as a framework which allows transparent storage of the - same data across several physically separated machines + &a.pjd.email; as a framework which allows transparent storage + of the same data across several physically separated machines connected by a TCP/IP network. HAST can be understood as a network-based RAID1 (mirror), and is similar to the DRBD® storage system known from the GNU/&linux; @@ -3295,23 +3433,28 @@ Device 1K-blocks Used Avail Capacity - Understand &unix; and &os; basics. + Understand &unix; and + &os; basics. - Know how to configure network + Know how to + configure network interfaces and other core &os; subsystems. - Have a good understanding of &os; + Have a good understanding of + &os; networking. The HAST project was sponsored by The - &os; Foundation with support from OMCnet Internet Service - GmbH and TransIP + &os; Foundation with support from + OMCnet Internet Service + GmbH and TransIP BV. @@ -3436,7 +3579,8 @@ Device 1K-blocks Used Avail Capacity before actually storing the data. The data on the remote node will be stored directly after sending the acknowledgement. This mode is intended to reduce - latency, but still provides very good reliability. + latency, but still provides very good + reliability. @@ -3496,16 +3640,15 @@ Device 1K-blocks Used Avail Capacity primary-secondary operation using HAST to replicate the data between the two. The nodes will be called - hasta with an IP - address of 172.16.0.1 and - hastb with an IP - of address 172.16.0.2. Both nodes - will have a dedicated hard drive - /dev/ad6 - of the same size for HAST operation. The + hasta with an IP address of + 172.16.0.1 and + hastb with an IP of address + 172.16.0.2. Both nodes will have a + dedicated hard drive /dev/ad6 of the same + size for HAST operation. The HAST pool, sometimes also referred to as a - resource or the GEOM provider in /dev/hast/, will be - called + resource or the GEOM provider in + /dev/hast/, will be called test. Configuration of HAST is done using @@ -3820,8 +3963,8 @@ esac More detailed information with additional examples can - be found in the - HAST Wiki + be found in the HAST Wiki page.