Most users have disk quotas applied to them which limit the total size of the files they can own on the system. This section describes how quotas work and the current quota policy.
You can discover your quota with the showquota command. For example:
%showquotaUsed 2.1M; Quota 256.0M
This says that your (actually joe's)
current usage is 2.1M. (An “M” is a megabyte: about
a million
bytes, or characters, of disk space.)
Your quota is 256.0M (256 megabytes).
The system will not allow you to create or add to your files so that your current usage would exceed your quota. Depending on the programs you're running, you may (or may not) get error messages (of varying wording) notifying you of quota problems.
Users who need additional disk space for short-term storage of large files
should usually use the “scratch” directory /var/tmp available on each
system. Files in the scratch directory do not count against user quota.
However, as the `tmp' name implies, any files you put in the scratch areas
should be strictly tmporary. The area is not backed up to tape, and an
automatic program cleans old files out periodically. For more information on
the scratch directory,
see Section 8.4, “Temporary Files Policy”.
Generally, you'll want to stay comfortably under quota; exceeding your quota can put your saved data at risk.
However, if you do ever find yourself flirting with quota-disaster, if you're careful and cool-headed, you can often pull yourself out of potentially bad situations.
For example, if you are in an editor when you get a quota-exceeded
message, you may be unable to save your edited file in your own area.
All is not lost, however: you should (a) tell the editor to write your
file in the /var/tmp
directory, (b) delete or compress files in your
area to get below quota; (c) log out; (d) log back in again; and,
finally (e) copy the file from /var/tmp
back into your own
directory.
For example, the vi command to write a file named
poli.c
in the /var/tmp directory would be
:w /var/tmp/poli.c
Then, after you've gone under quota, logged out, and logged back in, you can then bring the file back by typing the Unix command:
%cp /var/tmp/poli.c poli.c
(Of course, you want to be very sure you log back into the same
machine. The /var/tmp
directories on different
machines are on different disks.)
Most users have a “base” quota of 256 megabytes, which we hope is adequate to accommodate the vast majority of normal everyday disk storage. (For reference purposes, the text version of the King James Bible is about four megabytes.)
Users will (usually) receive warnings via e-mail if their quota is about to be reduced below their current disk usage.
Requests for increased quota (for some reason nobody ever requests a
decreased quota) should be made via e-mail to
<sysman@cisunix.unh.edu>.
This is called an “override request” because it replaces our default
quota-calculation algorithm.
Guidelines:
Quota overrides are (almost without exception) not “free”. The current charge is $50 per year per additional 100 Megabytes. Waiver of this fee must be approved by the CIS Director.
Your override request should include:
the additional quota you're asking for, typically some multiple of 100 Megabytes;
the proposed purpose of your additional disk space usage;
billing information (your BSC contact person, typically).
Quota overrides normally last for one year, and they may be renewed at the current rate.
Quota overrides for students must be "sponsored" by a faculty member, and the faculty member must make the request on behalf of the student.
The /tmp and
/var/tmp
directories are for temporary storage of files.
Many system programs expect to be able to create files in these
directories, and fail miserably if they are full. This can be
inconvenient to all users of the system.
The system runs a tmp-cleaning program daily to automatically enforce the following rules:
Files at the top level of the tmp directories will be removed after ten days.
Files in subdirectories within the tmp directories will be removed after thirty days.
Empty subdirectories within the tmp directories will be removed immediately.
Extremely large files or directories may be removed at any time if
/tmp or /var/tmp become over 90% full.
Technical note: The age of a file or directory will be determined by the time its contents were last accessed. (For unix geeks: atime.)