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

* Minor sentence revisions for consistency

Browse source 
* Changed some comma usage
 * Made use of the <quota> tag over a literal "word"
This commit is contained in:
Chern Lee 2001-09-07 00:13:40 +00:00
parent 2e0731b31b
commit c5f66c8cec
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10609
1 changed files with 27 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.57 2001/08/28 12:36:43 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.58 2001/09/05 00:57:22 chern Exp $
-->
<chapter id="disks">
@ -84,18 +84,19 @@
Adventures:</title>
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
for Fred. Bill installs a single SCSI drive as SCSI unit zero, and
for Fred. Bill installs a single SCSI drive as SCSI unit zero and
installs FreeBSD on it.</para>
<para>Fred begins using the system, but after several days notices that
the older SCSI drive is reporting numerous soft errors, and reports
the older SCSI drive is reporting numerous soft errors and reports
this fact to Bill.</para>
<para>After several more days, Bill decides it is time to address the
situation, so he grabs an identical SCSI drive from the disk drive
"archive" in the back room. An initial surface scan indicates that
<quote>archive</quote> in the back room. An initial surface scan
indicates that
this drive is functioning well, so Bill installs this drive as SCSI
unit four, and makes an image copy from drive zero to drive four. Now
unit four and makes an image copy from drive zero to drive four. Now
that the new drive is installed and functioning nicely, Bill decides
that it is a good idea to start using it, so he uses features in the
SCSI BIOS to re-order the disk drives so that the system boots from
@ -104,8 +105,8 @@
<para>Fred continues his work for several days, and soon Bill and Fred
decide that it is time for a new adventure -- time to upgrade to a
newer version of FreeBSD. Bill removes SCSI unit zero because it was
a bit flaky, and replaces it with another identical disk drive from
the "archive." Bill then installs the new version of FreeBSD onto the
a bit flaky and replaces it with another identical disk drive from
the <quote>archive.</quote> Bill then installs the new version of FreeBSD onto the
new SCSI unit zero using Fred's magic Internet FTP floppies. The
installation goes well.</para>
@ -119,7 +120,8 @@
<para>Where did the data go?</para>
<para>When Bill made an image copy of the original SCSI unit zero onto
SCSI unit four, unit four became the "new clone," When Bill
SCSI unit four, unit four became the <quote>new clone,</quote>
When Bill
re-ordered the SCSI BIOS so that he could boot from SCSI unit four, he
was only fooling himself. FreeBSD was still running on SCSI unit zero.
Making this kind of BIOS change will cause some or all of the Boot and
@ -299,8 +301,8 @@
<para>During the <link linkend="boot">boot process</link>,
filesystems listed in <filename>/etc/fstab</filename> are
automatically mounted (unless they are listed with
<option>noauto</option>).</para>
automatically mounted (unless they are listed with the
<option>noauto</option> option).</para>
<para>The <filename>/etc/fstab</filename> file contains a list
of lines of the following format:</para>
@ -312,7 +314,7 @@
<term><literal>device</literal></term>
<listitem>
<para>A device name (which should exist), as explained in
the <link linkend="disks-naming">Disk naming
<link linkend="disks-naming">Disk naming
conventions</link> above.</para>
</listitem>
</varlistentry>
@ -839,16 +841,16 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>Quotas are an optional feature of the operating system that
allow you to limit the amount of disk space and/or the number of
files a user, or members of a group, may allocate on a per-file
files a user or members of a group may allocate on a per-file
system basis. This is used most often on timesharing systems where
it is desirable to limit the amount of resources any one user or
group of users may allocate. This will prevent one user from
consuming all of the available disk space.</para>
group of users may allocate. This will prevent one user or group
of users from consuming all of the available disk space.</para>
<sect2>
<title>Configuring Your System to Enable Disk Quotas</title>
<para>Before attempting to use disk quotas it is necessary to make
<para>Before attempting to use disk quotas, it is necessary to make
sure that quotas are configured in your kernel. This is done by
adding the following line to your kernel configuration
file:</para>
@ -902,13 +904,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<programlisting>/dev/da1s2g /home ufs rw,userquota 1 2</programlisting>
<para>Similarly, to enable group quotas, use the
<literal>groupquota</literal> option instead of the
<literal>userquota</literal> keyword. To enable both user and
<literal>groupquota</literal> option instead of
<literal>userquota</literal>. To enable both user and
group quotas, change the entry as follows:</para>
<programlisting>/dev/da1s2g /home ufs rw,userquota,groupquota 1 2</programlisting>
<para>By default the quota files are stored in the root directory of
<para>By default, the quota files are stored in the root directory of
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
@ -957,7 +959,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
files they may create. You may limit allocations based on disk
space (block quotas) or number of files (inode quotas) or a
combination of both. Each of these limits are further broken down
into two categories; hard and soft limits.</para>
into two categories: hard and soft limits.</para>
<indexterm><primary>hard limit</primary></indexterm>
<para>A hard limit may not be exceeded. Once a user reaches his
@ -995,7 +997,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<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 users block limit
the quota limit. For example, to raise this user's block limit
from a soft limit of 50 and a hard limit of 75 to a soft limit of
500 and a hard limit of 600, change:</para>
@ -1032,9 +1034,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>You can use either the <command>quota</command> or the
<command>repquota</command> commands to check quota limits and
disk usage. The <command>quota</command> command can be used to
check individual user and group quotas and disk usage. Only the
super-user may examine quotas and usage for other users, or for
groups that they are not a member of. The
check individual user or group quotas and disk usage. A user
may only examine his own quota, and the quota of a group he
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 file systems with quotas
enabled.</para>
@ -1050,7 +1053,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<indexterm><primary>grace period</primary></indexterm>
<para>On the <filename>/usr</filename> file system in the above
example this user is currently 15 blocks over the soft limit of
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>