os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

s/filesystem/file system/ it's in part a revert of a previous commit to

Browse source 
respect our official wordlist.
This commit is contained in:
Marc Fonvieille 2002-09-01 20:28:50 +00:00
parent 52ce212a52
commit 3b5ef6601b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14139
1 changed files with 98 additions and 98 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

196
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -20,11 +20,11 @@
<listitem><para>The terminology FreeBSD uses to describe the
organization of data on a physical disk (partitions and slices).</para>
</listitem>
<listitem><para>How to mount and unmount filesystems.</para>
<listitem><para>How to mount and unmount file systems.</para>
</listitem>
<listitem><para>How to add additional hard disks to your system.</para>
</listitem>
<listitem><para>How to setup virtual filesystems, such as memory
<listitem><para>How to setup virtual file systems, such as memory
disks.</para></listitem>
<listitem>
<para>How to use quotas to limit disk space usage.</para>
@ -233,9 +233,9 @@
<para><application>sysinstall</application>'s Label editor
favors the <literal>e</literal>
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
<userinput>C</userinput>. When prompted if this will be a FS
(filesystem) or swap, choose <literal>FS</literal> and type in a
(file system) or swap, choose <literal>FS</literal> and type in a
mount point (e.g, <filename>/mnt</filename>). When adding a
disk in post-install mode, <application>sysinstall</application>
will not create entries
@ -243,7 +243,7 @@
you specify is not important.</para>
<para>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
<userinput>W</userinput>. Ignore any errors from
<application>sysinstall</application> 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.</para>
<para>To sum it up, I need something that will give me the most
@ -397,7 +397,7 @@ ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlist
true slave/master configuration.</para>
<para>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;
(<xref linkend="vinum-vinum">) 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 &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlist
<para><application>CCD</application> 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
<application>ccd</application>, I need a kernel with
<application>ccd</application> support built into it. I
added this line to my kernel configuration file and rebuilt
@ -463,7 +463,7 @@ disklabel -e ad3</programlisting>
</sect4>
<sect4 id="ccd-buildingfs">
<title>Building the Filesystem</title>
<title>Building the File System</title>
<para>Now that I have all of the disks labeled, I needed to
build the <application>ccd</application>. To do that, I
@ -478,7 +478,7 @@ disklabel -e ad3</programlisting>
sh MAKEDEV ccd0</programlisting>
<para>The next argument <command>ccdconfig</command> 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</programlisting>
<programlisting>ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e</programlisting>
<para>This configures the <application>ccd</application>.
I can now &man.newfs.8; the filesystem.</para>
I can now &man.newfs.8; the file system.</para>
<programlisting>newfs /dev/ccd0c</programlisting>
@ -609,11 +609,11 @@ sh MAKEDEV ccd0</programlisting>
<indexterm><primary>ISO 9660</primary></indexterm>
<indexterm>
<primary>filesystems</primary>
<primary>file systems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>The ISO 9660 filesystem was designed to deal with these
differences. It unfortunately codifies filesystem limits that were
<para>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.</para>
@ -647,42 +647,42 @@ sh MAKEDEV ccd0</programlisting>
<sect2 id="mkisofs">
<title>mkisofs</title>
<para><filename role="package">sysutils/mkisofs</filename> produces an ISO 9660 filesystem
that is an image of a directory tree in the Unix filesystem name
<para><filename role="package">sysutils/mkisofs</filename> 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:</para>
<screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
<indexterm>
<primary>filesystems</primary>
<primary>file systems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>This command will create an <replaceable>imagefile</replaceable>
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
<replaceable>/path/to/tree</replaceable>. 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.</para>
standard ISO 9660 file system, and will exclude files that have
names uncharacteristic of ISO file systems.</para>
<indexterm>
<primary>filesystems</primary>
<primary>file systems</primary>
<secondary>HFS</secondary>
</indexterm>
<indexterm>
<primary>filesystems</primary>
<primary>file systems</primary>
<secondary>Joliet</secondary>
</indexterm>
<para>A number of options are available to overcome those
restrictions. In particular, <option>-R</option> enables the
Rock Ridge extensions common to Unix systems, <option>-J</option>
enables Joliet extensions used by Microsoft systems, and
<option>-hfs</option> can be used to create HFS filesystems used
<option>-hfs</option> can be used to create HFS file systems used
by MacOS.</para>
<para>For CDs that are going to be used only on FreeBSD systems,
<option>-U</option> can be used to disable all filename
restrictions. When used with <option>-R</option>, 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.</para>
@ -698,13 +698,13 @@ sh MAKEDEV ccd0</programlisting>
<filename>/tmp/myboot</filename> holds a bootable FreeBSD system
with the boot image in
<filename>/tmp/myboot/boot/cdboot</filename>, you could produce the
image of an ISO 9660 filesystem in
image of an ISO 9660 file system in
<filename>/tmp/bootable.iso</filename> like so:</para>
<screen>&prompt.root; <userinput>mkisofs -U -R -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
<para>Having done that, if you have <devicename>vn</devicename>
configured in your kernel, you can mount the filesystem with:</para>
configured in your kernel, you can mount the file system with:</para>
<screen>&prompt.root; <userinput>vnconfig -e vn0c /tmp/bootable.iso</userinput>
&prompt.root; <userinput>mount -t cd9660 /dev/vn0c /mnt</userinput></screen>
@ -891,16 +891,16 @@ scsibus1:
<para>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
<literal>ufs</literal>. If you try something like:</para>
<screen>&prompt.root; <userinput>mount /dev/cd0c /mnt</userinput></screen>
<para>you will get a complaint about <errorname>Incorrect super
block</errorname>, and no mount. The CDROM is not a
<literal>UFS</literal> filesystem, so attempts to mount it
<literal>UFS</literal> 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 <literal>ISO9660</literal>, and
the file system is of type <literal>ISO9660</literal>, and
everything will work. You do this by specifying the
<option>-t cd9660</option> option &man.mount.8;. For
example, if you want to mount the CDROM device,
@ -952,7 +952,7 @@ scsibus1:
<title>Burning Raw Data CDs</title>
<para>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:</para>
@ -1077,25 +1077,25 @@ scsibus1:
</sect2>
<sect2>
<title>The filesystem</title>
<title>The file system</title>
<para>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.</para>
<para>You can choose now which filesystem to use on your floppy.
<para>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.</para>
<para>To put a new filesystem on the floppy do this:</para>
<para>To put a new file system on the floppy do this:</para>
<screen>&prompt.root; <userinput>/sbin/newfs_msdos /dev/fd0</userinput></screen>
<para>As we created a disklabel before, <application>newfs</application>
will be able to fetch disk data and construct the new
filesystem. And now, your disk is ready for use...</para>
file system. And now, your disk is ready for use...</para>
</sect2>
<sect2>
@ -1454,18 +1454,18 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<command>dump</command> and <command>restore</command>. 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. <command>dump</command> 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. <command>dump</command> does not write files and
the file systems. <command>dump</command> 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. <command>dump</command> does not write files and
directories to tape, but rather writes the raw data blocks that
comprise files and directories.</para>
<note><para>If you use <command>dump</command> on your root directory, you
would not back up <filename>/home</filename>,
<filename>/usr</filename> or many other directories since
these are typically mount points for other filesystems or
symbolic links into those filesystems.</para></note>
these are typically mount points for other file systems or
symbolic links into those file systems.</para></note>
<para><command>dump</command> has quirks that remain from its early days in
Version 6 of AT&amp;T Unix (circa 1975). The default
@ -1515,7 +1515,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>&man.tar.1; also dates back to Version 6 of AT&amp;T Unix
(circa 1975). <command>tar</command> operates in cooperation
with the filesystem; <command>tar</command> writes files and
with the file system; <command>tar</command> writes files and
directories to tape. <command>tar</command> does not support the
full range of options that are available from &man.cpio.1;, but
<command>tar</command> does not require the unusual command
@ -1617,12 +1617,12 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
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 <quote>holding disk</quote> to
backup several filesystems at the same time. Amanda creates
backup several file systems at the same time. Amanda creates
<quote>archive sets</quote>: 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 <quote>archive set</quote> 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.</para>
<para>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</screen>
<para>&man.dump.8; <emphasis>Period.</emphasis> 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 <command>dump</command>. Elizabeth created filesystems containing
file systems is <command>dump</command>. 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</screen>
</indexterm>
<para>First, print the disklabel from each of your disks
(<command>e.g. disklabel da0 | lpr</command>), your filesystem table
(<command>e.g. disklabel da0 | lpr</command>), your file system table
(<filename>/etc/fstab</filename>) and all boot messages,
two copies of
each.</para>
@ -1861,7 +1861,7 @@ cd /mnt/dev
cd /
#
# create minimum filesystem table
# create minimum file system table
#
cat > /mnt/etc/fstab <<EOM
/dev/fd0a / ufs rw 1 1
@ -1917,7 +1917,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<command>restore</command> and the other programs that you need are
located in <filename>/mnt2/stand</filename>.</para>
<para>Recover each filesystem separately.</para>
<para>Recover each file system separately.</para>
<indexterm>
<primary><command>mount</command></primary>
@ -1933,12 +1933,12 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use <command>disklabel</command> to re-partition and
label the disk to match the label that you printed and saved. Use
<command>newfs</command> to re-create the filesystems. Re-mount the root
<command>newfs</command> to re-create the file systems. Re-mount the root
partition of the floppy read-write (<command>mount -u -o rw
/mnt</command>). Use your backup program and backup tapes to
recover the data for this filesystem (e.g. <command>restore vrf
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
/mnt</command>) Repeat for each filesystem that was
recover the data for this file system (e.g. <command>restore vrf
/dev/sa0</command>). Unmount the file system (e.g. <command>umount
/mnt</command>) Repeat for each file system that was
damaged.</para>
<para>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."]]></programlisting>
</sect1>
<sect1 id="disks-virtual">
<title>Network, Memory, and File-Based Filesystems</title>
<title>Network, Memory, and File-Based File Systems</title>
<indexterm><primary>virtual disks</primary></indexterm>
<indexterm>
<primary>disks</primary>
@ -1977,15 +1977,15 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<primary>disks</primary>
<secondary>memory</secondary>
</indexterm>
<para>These include network filesystems such as the <link
linkend="nfs">Network Filesystem</link> and Coda, memory-based
filesystems such as <link linkend="disks-md">md</link> and
file-backed filesystems created by <link
<para>These include network file systems such as the <link
linkend="nfs">Network File System</link> and Coda, memory-based
file systems such as <link linkend="disks-md">md</link> and
file-backed file systems created by <link
linkend="disks-vnconfig">vnconfig</link> or
<command>mdconfig</command>.</para>
<sect2 id="disks-vnconfig">
<title>vnconfig: File-Backed Filesystem</title>
<title>vnconfig: File-Backed File System</title>
<indexterm>
<primary>disks</primary>
<secondary>file-backed</secondary>
@ -1995,20 +1995,20 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
devices. A <firstterm>vnode</firstterm> 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.</para>
<para>To mount an existing filesystem image:</para>
<para>To mount an existing file system image:</para>
<example>
<title>Using vnconfig to mount an Existing Filesystem
<title>Using vnconfig to mount an Existing File System
Image</title>
<screen>&prompt.root; <userinput>vnconfig vn<replaceable>0</replaceable> <replaceable>diskimage</replaceable></userinput>
&prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput></screen>
</example>
<para>To create a new filesystem image with vnconfig:</para>
<para>To create a new file system image with vnconfig:</para>
<example>
<title>Creating a New File-Backed Disk with vnconfig</title>
@ -2032,16 +2032,16 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
</sect2>
<sect2 id="disks-md">
<title>md: Memory Filesystem</title>
<title>md: Memory File System</title>
<indexterm>
<primary>disks</primary>
<secondary>memory filesystem</secondary>
<secondary>memory file system</secondary>
</indexterm>
<para><devicename>md</devicename> is a simple, efficient means to create memory
filesystems.</para>
file systems.</para>
<para>Simply take a filesystem you have prepared with, for
<para>Simply take a file system you have prepared with, for
example, &man.vnconfig.8;, and:</para>
<example>
@ -2070,21 +2070,21 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<!-- 15 JUL 2002 -->
</sect1info>
<title>Filesystem Snapshots</title>
<title>File System Snapshots</title>
<indexterm>
<primary>Filesystem Snapshots</primary>
<primary>File System Snapshots</primary>
<secondary>Snapshots</secondary>
</indexterm>
<para>FreeBSD 5.0 offers a new feature in conjunction with
<link linkend="soft-updates">Soft Updates</link>: Filesystem snapshots.</para>
<link linkend="soft-updates">Soft Updates</link>: File system snapshots.</para>
<para>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
<listitem>
<para>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.</para>
@ -2126,7 +2126,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<listitem>
<para>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.</para>
file system as the timestamp of the snapshot.</para>
<warning><para>As of this writing &man.dump.8; has not yet
been changed to set the <filename>dumpdates</filename> file correctly, so
@ -2135,7 +2135,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
</listitem>
<listitem>
<para>&man.mount.8; the snapshot as a frozen image of the filesystem.
<para>&man.mount.8; the snapshot as a frozen image of the file system.
To &man.mount.8; the snapshot
<filename>/var/snapshot/snap</filename>:</para>
@ -2146,7 +2146,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
</itemizedlist>
<para>You can now walk the hierarchy of your frozen <filename>/var</filename>
filesystem mounted at <filename>/mnt</filename>. Everything will
file system mounted at <filename>/mnt</filename>. 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
<screen>&prompt.root; <userinput>mdconfig -d -u 4</userinput></screen>
<para>For more information about <option>softupdates</option> and
filesystem snapshots, including technical papers, you can visit
file system snapshots, including technical papers, you can visit
Marshall Kirk McKusick's website at
<ulink url="http://www.mckusick.com/">http://www.mckusick.com</ulink></para>
</sect1>
<sect1 id="quotas">
<title>Filesystem Quotas</title>
<title>File System Quotas</title>
<indexterm>
<primary>accounting</primary>
<secondary>disk space</secondary>
@ -2204,10 +2204,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
</indexterm>
<para>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
<command>quotacheck</command> program. The
<command>quotacheck</command> 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 <filename>/etc/rc.conf</filename>
@ -2222,13 +2222,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<programlisting>check_quotas="YES"</programlisting>
<para>Finally you will need to edit <filename>/etc/fstab</filename>
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.</para>
file systems.</para>
<para>To enable per-user quotas on a filesystem, add the
<para>To enable per-user quotas on a file system, add the
<literal>userquota</literal> option to the options field in the
<filename>/etc/fstab</filename> entry for the filesystem you want
<filename>/etc/fstab</filename> entry for the file system you want
to enable quotas on. For example:</para>
<programlisting>/dev/da1s2g /home ufs rw,userquota 1 2</programlisting>
@ -2241,7 +2241,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<programlisting>/dev/da1s2g /home ufs rw,userquota,groupquota 1 2</programlisting>
<para>By default, the quota files are stored in the root directory of
the filesystem with the names <filename>quota.user</filename> and
the file system with the names <filename>quota.user</filename> and
<filename>quota.group</filename> 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
<screen>&prompt.root; <userinput>quota -v</userinput></screen>
<para>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.</para>
<para>You are now ready to start assigning quota limits with the
@ -2295,7 +2295,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>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.</para>
@ -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)</programlisting>
<para>You will normally see two lines for each filesystem that has
<para>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
<command>repquota</command> 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.</para>
<para>The following is some sample output from the
<command>quota -v</command> command for a user that has quota
limits on two filesystems.</para>
limits on two file systems.</para>
<programlisting>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</programlisting>
<indexterm><primary>grace period</primary></indexterm>
<para>On the <filename>/usr</filename> filesystem in the above
<para>On the <filename>/usr</filename> 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 <literal>*</literal> which indicates that the user is
currently over his quota limit.</para>
<para>Normally filesystems that the user is not using any disk
<para>Normally file systems that the user is not using any disk
space on will not show up in the output from the
<command>quota</command> command, even if he has a quota limit
assigned for that filesystem. The <option>-v</option> option
will display those filesystems, such as the
<filename>/usr/var</filename> filesystem in the above
assigned for that file system. The <option>-v</option> option
will display those file systems, such as the
<filename>/usr/var</filename> file system in the above
example.</para>
</sect2>