Here are the WAM error messages that you will receive:
New mail move failed: no space left on device
This is caused by a situation where your mail spool file (the unread
mail):
/mail/userid/userid
is larger than the amount of free space available in your account.
For example, if you're using 95% of your 100MB quota (about 95MB),
which leaves you with 5% available, (about 5MB), and you have an unread
mail file of greater than 5MB, most mail clients will fail trying to read
the new (unread) mail.
When using Pine, it manifests itself with the error above. When
using other offline mail clients like Outlook or Mozilla Thunderbird, it
manifests itself by appearing that you no longer are receiving mail.
The reason for this is how most WAM and Glue accounts handle mail.
When Pine, deals with your new mail, it copies the mail spool file:
/mail/userid/userid
and appends it to the file:
/mail/userid/mbox
and then works on the mbox file. (This is to
prevent corruption to your real incoming mail file while you're reading
your mail and new mail comes in for you.) For a very short time during
this copy process, both the mail spool file and the
mbox file must exist at the same time; when the copy
is finished the mail spool file is emptied (but the file remains).
Therefore, for a brief time, the disk space usage is:
(mbox file) + (mail spool file) + (copy of mail spool file)
Once this copy process is completed, you'll only be using as much disk
space as:
(mbox file) + (mail spool file)
which will all be in your mbox file. If you don't
have enough room under your quota to handle this copy procedure, you'll
receive the (misleading) error "read only" message.
To check this, make sure that you are at the system prompt, and then type:
quota
The results of the quota command should look
similar to this:
rac1:~: quota
Volume Name Quota Used %Used Partition
user.userid 100000 95120 95%
rac1:~:
where userid is the login id of your account.
The total amount
of disk space allowed on WAM and standard Glue accounts is 100MB; the
above display shows it in Kilobytes (KB), so 100MB = 100000KB. Notice the
"Used" and "%Used" values indicate how much physical space (in KB) you are
using, and how much of a percentage of 100MB that space is. This is a
normal situation where the user apparently has plenty of space. If,
however, you use the ls command:
ls -l /mail/userid/userid
and look at the size of the mail spool file, you should see something
like this:
ls -l /mail/userid/userid
-rw------- 1 70004 root 95367021 Dec 3 10:05
/mail/userid/userid
The fifth field (in this case "95367021") is the size in bytes
(characters) of the mail spool file (in this case, ~9.5MB). If this size
is greater than the difference between the "Quota" and "Used" amounts from
the quota command above, you will encounter the error
above.
There is a program on the WAM and Glue systems to deal with this issue;
it will append your mail spool file to your "mbox" file for you (mimicking
the first step in a Pine session) without using your own file space. The
command is:
catmail
If you are under quota, you will be able to get all your mail into the
"mbox" file so that you can deal with it normally in Pine.
This is a one-time fix; you may still need to do something to get your disk
space usage down or you'll keep having the problem, unless the mail spool
file is of an unusually large size.
Checkpoint file
failure: No space left on device
Sending error 452
userid@wam.umd.edu insufficient
If either or both of these messages appears when trying to send
mail (or delete mail) from a WAM-based mail client program
such as Pine, it may be due to a filled-to-capacity status
for the /var partition on the
RAC you are logged into. To test this, use the
df command to check the size of
the rac's partitions:
rac2:/users/your-id: df
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 48727 30348 13507 70% /
/dev/dsk/c0t0d0s3 145135 79623 50999 61% /usr
/proc 0 0 0 0% /proc
/dev/dsk/c0t0d0s5 289207 21149 239138 9% /var
/dev/dsk/c0t0d0s4 1015679 806370 148369 85% /usr/vice/cache
/dev/dsk/c0t0d0s6 498271 694 447750 1% /tmp
AFS 9000000 0 9000000 0% /afs
If the capacity figure is at 99 or 100% (in the example it is
only 9%), this may be the problem. Therefore, please report
-
RAC number
-
Name of the full partition (/var, in this
case)
to the Help Desk (301.405.1400 (Students) or 301.405.1500 (Faculty / Staff))
immediately. If you don't get a direct answer, leave a message.
Getting around the problem -- Since you are
assigned a particular RAC by what is essentially a random
process when you login into WAM, you can probably escape this
problem until it is resolved by logging off and then logging
back in. If the RAC number you get this time is
different from the last, you'll have no similar problem
unless THIS machine's /var partition is also full.
Resource
temporarily unavailable writing logging article file --
throttling
This message, which may be encountered when trying to start a
news reader, may take this sort of form:
News server news.wam.umd.edu unavailable: Resource
temporarily unavailable writing article file -- throttling
Unexpected close of server socket.
This is the result of too many new, news items arriving at the
news server when it has insufficient space for them. The
volume of news is increasing rapidly, and keeping up with it
can be difficult. If the expunging of news items when their
expiration dates arrive isn't sufficient, manual intervention
on the part of the WAM news staff is necessary.
Please notify
the Help Desk when you encounter
this, leave a message if you do not receive a direct answer.
|