From 3b5ef6601b586102b8eda5981614c28d774886be Mon Sep 17 00:00:00 2001 From: Marc Fonvieille Date: Sun, 1 Sep 2002 20:28:50 +0000 Subject: [PATCH] s/filesystem/file system/ it's in part a revert of a previous commit to respect our official wordlist. --- .../books/handbook/disks/chapter.sgml | 196 +++++++++--------- 1 file changed, 98 insertions(+), 98 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml index 95b5006641..db522384c2 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml @@ -20,11 +20,11 @@ The terminology FreeBSD uses to describe the organization of data on a physical disk (partitions and slices). - How to mount and unmount filesystems. + How to mount and unmount file systems. How to add additional hard disks to your system. - How to setup virtual filesystems, such as memory + How to setup virtual file systems, such as memory disks. How to use quotas to limit disk space usage. @@ -233,9 +233,9 @@ sysinstall's Label editor favors the e partition for non-root, non-swap partitions. Within the - Label editor, create a single filesystem by typing + Label editor, create a single file system by typing C. When prompted if this will be a FS - (filesystem) or swap, choose FS and type in a + (file system) or swap, choose FS and type in a mount point (e.g, /mnt). When adding a disk in post-install mode, sysinstall will not create entries @@ -243,7 +243,7 @@ you specify is not important. You are now ready to write the new label to the disk and - create a filesystem on it. Do this by typing + create a file system on it. Do this by typing W. Ignore any errors from sysinstall that it could not mount the new partition. Exit the Label Editor @@ -359,7 +359,7 @@ an easy one to answer. All of the data being put on this mass storage device was already backed up on CD-R's. This drive was primarily here for online live storage for easy access, so if a - drive went bad, I could just replace it, rebuild the filesystem, + drive went bad, I could just replace it, rebuild the file system, and copy back the data from CD-R's. To sum it up, I need something that will give me the most @@ -397,7 +397,7 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 The next consideration was how to attach them as part of - the filesystem. I did a little research on &man.vinum.8; + the file system. I did a little research on &man.vinum.8; () and &man.ccd.4;. In this particular configuration, &man.ccd.4; appeared to be a better choice mainly because it has fewer @@ -410,7 +410,7 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33CCD allows me to take several identical disks and concatenate them into one - logical filesystem. In order to use + logical file system. In order to use ccd, I need a kernel with ccd support built into it. I added this line to my kernel configuration file and rebuilt @@ -463,7 +463,7 @@ disklabel -e ad3 - Building the Filesystem + Building the File System Now that I have all of the disks labeled, I needed to build the ccd. To do that, I @@ -478,7 +478,7 @@ disklabel -e ad3 sh MAKEDEV ccd0 The next argument ccdconfig expects - is the interleave for the filesystem. The interleave + is the interleave for the file system. The interleave defines the size of a stripe in disk blocks, normally five hundred and twelve bytes. So, an interleave of thirty-two would be sixteen thousand three hundred and eighty-four @@ -497,7 +497,7 @@ sh MAKEDEV ccd0 ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e This configures the ccd. - I can now &man.newfs.8; the filesystem. + I can now &man.newfs.8; the file system. newfs /dev/ccd0c @@ -609,11 +609,11 @@ sh MAKEDEV ccd0 ISO 9660 - filesystems + file systems ISO-9660 - The ISO 9660 filesystem was designed to deal with these - differences. It unfortunately codifies filesystem limits that were + The ISO 9660 file system was designed to deal with these + differences. It unfortunately codifies file system limits that were common then. Fortunately, it provides an extension mechanism that allows properly written CDs to exceed those limits while still working with systems that do not support those extensions. @@ -647,42 +647,42 @@ sh MAKEDEV ccd0 mkisofs - sysutils/mkisofs produces an ISO 9660 filesystem - that is an image of a directory tree in the Unix filesystem name + sysutils/mkisofs produces an ISO 9660 file system + that is an image of a directory tree in the Unix file system name space. The simplest usage is: &prompt.root; mkisofs -o imagefile.iso /path/to/tree - filesystems + file systems ISO-9660 This command will create an imagefile - containing an ISO 9660 filesystem that is a copy of the tree at + containing an ISO 9660 file system that is a copy of the tree at /path/to/tree. In the process, it will map the file names to names that fit the limitations of the - standard ISO 9660 filesystem, and will exclude files that have - names uncharacteristic of ISO filesystems. + standard ISO 9660 file system, and will exclude files that have + names uncharacteristic of ISO file systems. - filesystems + file systems HFS - filesystems + file systems Joliet A number of options are available to overcome those restrictions. In particular, enables the Rock Ridge extensions common to Unix systems, enables Joliet extensions used by Microsoft systems, and - can be used to create HFS filesystems used + can be used to create HFS file systems used by MacOS. For CDs that are going to be used only on FreeBSD systems, can be used to disable all filename restrictions. When used with , it produces a - filesystem image that is identical to the FreeBSD tree you started + file system image that is identical to the FreeBSD tree you started from, though it may violate the ISO 9660 standard in a number of ways. @@ -698,13 +698,13 @@ sh MAKEDEV ccd0 /tmp/myboot holds a bootable FreeBSD system with the boot image in /tmp/myboot/boot/cdboot, you could produce the - image of an ISO 9660 filesystem in + image of an ISO 9660 file system in /tmp/bootable.iso like so: &prompt.root; mkisofs -U -R -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot Having done that, if you have vn - configured in your kernel, you can mount the filesystem with: + configured in your kernel, you can mount the file system with: &prompt.root; vnconfig -e vn0c /tmp/bootable.iso &prompt.root; mount -t cd9660 /dev/vn0c /mnt @@ -891,16 +891,16 @@ scsibus1: Now that you have created a standard data CDROM, you probably want to mount it and read the data on it. By - default, &man.mount.8; assumes that a filesystem is of type + default, &man.mount.8; assumes that a file system is of type ufs. If you try something like: &prompt.root; mount /dev/cd0c /mnt you will get a complaint about Incorrect super block, and no mount. The CDROM is not a - UFS filesystem, so attempts to mount it + UFS file system, so attempts to mount it as such will fail. You just need to tell &man.mount.8; that - the filesystem is of type ISO9660, and + the file system is of type ISO9660, and everything will work. You do this by specifying the option &man.mount.8;. For example, if you want to mount the CDROM device, @@ -952,7 +952,7 @@ scsibus1: Burning Raw Data CDs You can choose to burn a file directly to CD, without - creating an ISO 9660 filesystem. Some people do this for + creating an ISO 9660 file system. Some people do this for backup purposes. This runs more quickly than burning a standard CD: @@ -1077,25 +1077,25 @@ scsibus1: - The filesystem + The file system Now your floppy is ready to be high-level formated. This - will place a new filesystem on it, which will let FreeBSD read - and write to the disk. After creating the new filesystem, the + will place a new file system on it, which will let FreeBSD read + and write to the disk. After creating the new file system, the disklabel is destroyed, so if you want to reformat the disk, you will have to recreate the disklabel another time. - You can choose now which filesystem to use on your floppy. + You can choose now which file system to use on your floppy. You can use UFS or FAT, though UFS is not a good idea for floppies. Choose FAT which is nice for floppies. - To put a new filesystem on the floppy do this: + To put a new file system on the floppy do this: &prompt.root; /sbin/newfs_msdos /dev/fd0 As we created a disklabel before, newfs will be able to fetch disk data and construct the new - filesystem. And now, your disk is ready for use... + file system. And now, your disk is ready for use... @@ -1454,18 +1454,18 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready dump and restore. They operate on the drive as a collection of disk blocks, below the abstractions of files, links and directories that are created by - the filesystems. dump backs up an entire - filesystem on a device. It is unable to backup only part of a - filesystem or a directory tree that spans more than one - filesystem. dump does not write files and + the file systems. dump backs up an entire + file system on a device. It is unable to backup only part of a + file system or a directory tree that spans more than one + file system. dump does not write files and directories to tape, but rather writes the raw data blocks that comprise files and directories. If you use dump on your root directory, you would not back up /home, /usr or many other directories since - these are typically mount points for other filesystems or - symbolic links into those filesystems. + these are typically mount points for other file systems or + symbolic links into those file systems. dump has quirks that remain from its early days in Version 6 of AT&T Unix (circa 1975). The default @@ -1515,7 +1515,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready &man.tar.1; also dates back to Version 6 of AT&T Unix (circa 1975). tar operates in cooperation - with the filesystem; tar writes files and + with the file system; tar writes files and directories to tape. tar does not support the full range of options that are available from &man.cpio.1;, but tar does not require the unusual command @@ -1617,12 +1617,12 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready that the length of time required to backup to data directly to tape exceeds the amount of time available for the task. Amanda solves this problem. Amanda can use a holding disk to - backup several filesystems at the same time. Amanda creates + backup several file systems at the same time. Amanda creates archive sets: a group of tapes used over a period of time to - create full backups of all the filesystems listed in Amanda's + create full backups of all the file systems listed in Amanda's configuration file. The archive set also contains nightly - incremental (or differential) backups of all the filesystems. - Restoring a damaged filesystem requires the most recent full + incremental (or differential) backups of all the file systems. + Restoring a damaged file system requires the most recent full backup and the incremental backups. The configuration file provides fine control of backups and the @@ -1663,10 +1663,10 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready &man.dump.8; Period. Elizabeth D. Zwicky torture tested all the backup programs discussed here. The clear choice for preserving all your data and all the peculiarities of Unix - filesystems is dump. Elizabeth created filesystems containing + file systems is dump. Elizabeth created filesystems containing a large variety of unusual conditions (and some not so unusual ones) and tested each program by doing a backup and restore of those - filesystems. The peculiarities included: files with holes, files with + file systems. The peculiarities included: files with holes, files with holes and a block of nulls, files with funny characters in their names, unreadable and unwritable files, devices, files that change size during the backup, files that are created/deleted during the @@ -1689,7 +1689,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready First, print the disklabel from each of your disks - (e.g. disklabel da0 | lpr), your filesystem table + (e.g. disklabel da0 | lpr), your file system table (/etc/fstab) and all boot messages, two copies of each. @@ -1861,7 +1861,7 @@ cd /mnt/dev cd / # -# create minimum filesystem table +# create minimum file system table # cat > /mnt/etc/fstab < restore and the other programs that you need are located in /mnt2/stand. - Recover each filesystem separately. + Recover each file system separately. mount @@ -1933,12 +1933,12 @@ echo "The floppy has been unmounted and is now ready."]]> /mnt) the root partition of your first disk. If the disklabel was damaged, use disklabel to re-partition and label the disk to match the label that you printed and saved. Use - newfs to re-create the filesystems. Re-mount the root + newfs to re-create the file systems. Re-mount the root partition of the floppy read-write (mount -u -o rw /mnt). Use your backup program and backup tapes to - recover the data for this filesystem (e.g. restore vrf - /dev/sa0). Unmount the filesystem (e.g. umount - /mnt) Repeat for each filesystem that was + recover the data for this file system (e.g. restore vrf + /dev/sa0). Unmount the file system (e.g. umount + /mnt) Repeat for each file system that was damaged. Once your system is running, backup your data onto new tapes. @@ -1959,7 +1959,7 @@ echo "The floppy has been unmounted and is now ready."]]> - Network, Memory, and File-Based Filesystems + Network, Memory, and File-Based File Systems virtual disks disks @@ -1977,15 +1977,15 @@ echo "The floppy has been unmounted and is now ready."]]> disks memory - These include network filesystems such as the Network Filesystem and Coda, memory-based - filesystems such as md and - file-backed filesystems created by These include network file systems such as the Network File System and Coda, memory-based + file systems such as md and + file-backed file systems created by vnconfig or mdconfig. - vnconfig: File-Backed Filesystem + vnconfig: File-Backed File System disks file-backed @@ -1995,20 +1995,20 @@ echo "The floppy has been unmounted and is now ready."]]> devices. A vnode is a representation of a file, and is the focus of file activity. This means that &man.vnconfig.8; uses files to create and operate a - filesystem. One possible use is the mounting of floppy or CD + file system. One possible use is the mounting of floppy or CD images kept in files. - To mount an existing filesystem image: + To mount an existing file system image: - Using vnconfig to mount an Existing Filesystem + <title>Using vnconfig to mount an Existing File System Image &prompt.root; vnconfig vn0 diskimage &prompt.root; mount /dev/vn0c /mnt - To create a new filesystem image with vnconfig: + To create a new file system image with vnconfig: Creating a New File-Backed Disk with vnconfig @@ -2032,16 +2032,16 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - md: Memory Filesystem + md: Memory File System disks - memory filesystem + memory file system md is a simple, efficient means to create memory - filesystems. + file systems. - Simply take a filesystem you have prepared with, for + Simply take a file system you have prepared with, for example, &man.vnconfig.8;, and: @@ -2070,21 +2070,21 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - Filesystem Snapshots + File System Snapshots - Filesystem Snapshots + File System Snapshots Snapshots FreeBSD 5.0 offers a new feature in conjunction with - Soft Updates: Filesystem snapshots. + Soft Updates: File system snapshots. Snapshots allow a user to create an image of specified file systems and treat this image as a file. - Snapshot files must be created in the filesystem that the + Snapshot files must be created in the file system that the action is performed on, and a user may create no more than 20 - snapshots per filesystem. Active snapshots are recorded + snapshots per file system. Active snapshots are recorded in the superblock so they are persistent across unmount and remount operations along with system reboots. When a snapshot is no longer required, it can be removed with the standard &man.rm.1; @@ -2117,7 +2117,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on File integrity, &man.fsck.8; may be ran on the snapshot file. - Assuming that the filesystem was clean when it was mounted, you + Assuming that the file system was clean when it was mounted, you should always get a clean (and unchanging) result from running &man.fsck.8; on the snapshot. This is essentially what the background &man.fsck.8; process does. @@ -2126,7 +2126,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on Run the &man.dump.8; utility on the snapshot. A dump will be returned that is as consistent with the - filesystem as the timestamp of the snapshot. + file system as the timestamp of the snapshot. As of this writing &man.dump.8; has not yet been changed to set the dumpdates file correctly, so @@ -2135,7 +2135,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on - &man.mount.8; the snapshot as a frozen image of the filesystem. + &man.mount.8; the snapshot as a frozen image of the file system. To &man.mount.8; the snapshot /var/snapshot/snap: @@ -2146,7 +2146,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on You can now walk the hierarchy of your frozen /var - filesystem mounted at /mnt. Everything will + file system mounted at /mnt. Everything will be in the same state it was during the snapshot creation time. The only exception being that any earlier snapshots will appear as zero length files. When the use of a snapshot has delimited, @@ -2156,13 +2156,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on &prompt.root; mdconfig -d -u 4 For more information about and - filesystem snapshots, including technical papers, you can visit + file system snapshots, including technical papers, you can visit Marshall Kirk McKusick's website at http://www.mckusick.com - Filesystem Quotas + File System Quotas accounting disk space @@ -2204,10 +2204,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on For finer control over your quota startup, there is an additional configuration variable available. Normally on bootup, - the quota integrity of each filesystem is checked by the + the quota integrity of each file system is checked by the quotacheck program. The quotacheck facility insures that the data in - the quota database properly reflects the data on the filesystem. + the quota database properly reflects the data on the file system. This is a very time consuming process that will significantly affect the time your system takes to boot. If you would like to skip this step, a variable in /etc/rc.conf @@ -2222,13 +2222,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on check_quotas="YES" Finally you will need to edit /etc/fstab - to enable disk quotas on a per-filesystem basis. This is where + to enable disk quotas on a per-file system basis. This is where you can either enable user or group quotas or both for all of your - filesystems. + file systems. - To enable per-user quotas on a filesystem, add the + To enable per-user quotas on a file system, add the userquota option to the options field in the - /etc/fstab entry for the filesystem you want + /etc/fstab entry for the file system you want to enable quotas on. For example: /dev/da1s2g /home ufs rw,userquota 1 2 @@ -2241,7 +2241,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da1s2g /home ufs rw,userquota,groupquota 1 2 By default, the quota files are stored in the root directory of - the filesystem with the names quota.user and + the file system with the names quota.user and quota.group for user and group quotas respectively. See &man.fstab.5; for more information. Even though the &man.fstab.5; manual page says that @@ -2278,7 +2278,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on &prompt.root; quota -v You should see a one line summary of disk usage and current - quota limits for each filesystem that quotas are enabled + quota limits for each file system that quotas are enabled on. You are now ready to start assigning quota limits with the @@ -2295,7 +2295,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on A hard limit may not be exceeded. Once a user reaches his hard limit he may not make any further allocations on the file system in question. For example, if the user has a hard limit of - 500 blocks on a filesystem and is currently using 490 blocks, the + 500 blocks on a file system and is currently using 490 blocks, the user can only allocate an additional 10 blocks. Attempting to allocate an additional 11 blocks will fail. @@ -2324,7 +2324,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on /usr/var: blocks in use: 0, limits (soft = 50, hard = 75) inodes in use: 0, limits (soft = 50, hard = 60) - You will normally see two lines for each filesystem that has + You will normally see two lines for each file system that has quotas enabled. One line for the block limits, and one line for inode limits. Simply change the value you want updated to modify the quota limit. For example, to raise this user's block limit @@ -2369,12 +2369,12 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on is a member of. Only the super-user may view all user and group quotas. The repquota command can be used to get a summary - of all quotas and disk usage for filesystems with quotas + of all quotas and disk usage for file systems with quotas enabled. The following is some sample output from the quota -v command for a user that has quota - limits on two filesystems. + limits on two file systems. Disk quotas for user test (uid 1002): Filesystem blocks quota limit grace files quota limit grace @@ -2382,18 +2382,18 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on /usr/var 0 50 75 0 50 60 grace period - On the /usr filesystem in the above + On the /usr file system in the above example, this user is currently 15 blocks over the soft limit of 50 blocks and has 5 days of the grace period left. Note the asterisk * which indicates that the user is currently over his quota limit. - Normally filesystems that the user is not using any disk + Normally file systems that the user is not using any disk space on will not show up in the output from the quota command, even if he has a quota limit - assigned for that filesystem. The option - will display those filesystems, such as the - /usr/var filesystem in the above + assigned for that file system. The option + will display those file systems, such as the + /usr/var file system in the above example.