translated by Google

Machine-translated page for increased accessibility for English questioners.

In our network, you will encounter disk quotas for UN * OS and Windows OS machines.


On UN * X machines, each user has a quota of:

  • on the volume /home/ xlogin with the home directory currently located on and exported using NFS and SMB
  • on the machine on the volume /var/mail with mail (does not apply to employee mailboxes on anxur)
  • on machines and on volumes /tmp and /var/tmp for temporary files

Quota limits the amount of disk space and the number of files stored. The limitation of each of these sources is given by the soft quota, hard quota and time limit, the meaning of which is as follows. Once the soft quota has been exceeded, the user has set a time limit for the normal operation. However, the system notifies him of an overrun quota - an alert message is sent and the alert is also displayed in the statement statement quota (see below). Once the timeout has elapsed, the user is restricted access to an over quota quota (it is not possible to create new files and increase the size of existing files), the user must delete enough data and / or files to recover the access. Hard limit system does not allow to exceed. If any operation causes a hard limit to be exceeded, it will not finish and end with an error.

Quota status detection

You can find all the volume limits you set in Faculty administration under My Account - Overview. You will find the current occupancy values ​​and the limits for the place and number of files on a particular machine by entering the command quota -v or also quota -vs for a more comprehensive listing of numeric values. Example:

aisa$ quota -v
Disk quotas for user xlogin (uid 5555):
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
                    820  2000000 4000000             194   50000   80000
                      4  150000  180000               1      50     100
                     72  2000000 4000000               9   50000   80000
                1912792  2000000  3000000            8717   80000  100000

nymfeXY$ quota -v
Disk quotas for user xlogin (uid 5555):
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
                2100500* 2000000 3000000   6days     8718   80000  100000
                      4  150000  180000               1      50     100

As an example, we see a quotation on the aisa and nymph machine. The first three columns are in kilobytes and the last three determine the number of files. U aisy you can see quotas for bundles /tmp (/dev/mapper/vg0-tmp) , /var/mail (/dev/mapper/vg0-mail) , /var/tmp (/dev/mapper/vg0-vartmp) and then for .

The last row above is usually the most important, as it displays quota information in the home directory, even if someone else's xblabla's login is displayed. This is due to the fact that one physical home machine is using the program automounter as separate volumes, the home directories of other logged in users and the command are also attached quota by default, quotes the quota only for the first found connection point on one physical device. This is, in spite of the slightly misleading description, relevant and actually gives the quota for the home directory of the current user.

In the second example, we also see a quota first in the home directory (with another login for the same reasons as described above) and the quota on the mailbox directory. This example also shows how the command quota informs about quota overrun. Behind the number is an asterisk, and the time bar is displayed in the Grace column.

If the quota is exceeded

If the quota is exceeded, we automatically send the message to the faculty address. After the quota is exceeded on the volume aisa:/var/mail the mailbox is moved to the home directory and the user is also informed by the message. If the quota is exceeded on the home directory, logging into the system using the graphical interfaces can be mysterious.

How do I find out which files occupy the most space?

Log in to your account (for example, using ssh) and start the command line at the command prompt:
$ du -kax | sort -n | tail -n 10
323316  ./.cpanm/work/1329993381.18167
340828  ./mail/misclass
350480  ./.Spotlight-V100/Store-V1
350488  ./.Spotlight-V100
367740  ./.cpanm/work
367820  ./.cpanm
414276  ./prog
627336  ./.ccache
2420912 ./mail
7762344 .

This command lists the used space in kB in all directories and files (even hidden) in the home directory, organizes them by size, and lists the top 10. In this case, we could delete some unnecessary files:

$ rm -rf .ccache .cpanm/work

The above command du it may not always reveal the cause of the quota. The listing only displays the files used in the home directory, but the quota counts over the entire directory /home and the owner of the file is decisive. If the data from the statement statement quota and du significantly different, it may mean that some files owned by the current user are located in the home directory of another user (or vice versa). In this case, you need to remember where they can be located and, if necessary, ask the user for access to / remove files. If you've tried the options listed here and still do not know the advice, you can contact the administrator at last .