Select Page

SEASnet Account Quotas

Introduction

Your SEASnet account can have up to three separate quotas. The first is your email quota. This quota is for your incoming mail and webmail folders only. All other email read on SEASnet systems is saved to your allocated disk space on the SEASnet servers, which is the second place your account has been granted disk space. The final quota you are allocated only applies if you use either the SEASnet labs or the terminal server. This disk space is related to your “lab profile” on the SEASnet lab machines.

SEASnet assigns disk quotas to ensure that all users on our systems receive sufficient space. When disks become full this adversely affects all users, leaving them unable to save their work. SEASnet will notify you via email to your SEASnet account if either your email or your allocated disk space on the SEASnet servers has been exceeded. If you have exceeded your lab profile quota on the SEASnet lab machines, you will not be allowed to logout until you have resolved the issue.

 

Email Quotas

There is currently no way for users to check the amount of disk space in use for incoming mail and/or webmail. System messages are generated when users exceed 10MB and an email is automatically sent to the user requesting the user reduce the size of their mailbox. If your email quota exceeds 250MB, SEASnet automatically tars all messages, places the tar file in your account, and blocks the account from receiving any future emails. This is only done if the user is unresponsive to repeated requests from SEASnet.

A good rule of thumb is to check your email every few days and save any email that requires your action or that you wish to keep in another mail folder. Mail should never be stored in your inbox. In addition, please keep in mind that webmail is not designed to be your standard mail reader. It has been designed as a temporary way to access your email.

 

Allocated Disk Quota

This is the space you use when you log in to ugrad.seas.ucla.edu and grad.seas.ucla.edu and when you log in to the SEASnet lab machines. Each student is allocated a specific amount of disk space (Currently 1.5GB).  Email is sent to your SEASnet account email (if GRAD) or your email on file (if UGRAD) if your disk space has been increased/decreased due to a request by your TA or instructor.

To check your allocated disk quota at any time, you can:

  • Log in to the SEASnet servers (SSH ugrad or SSH grad icons on the lab machines deskops)
  • Type in the command “showdq”. This will give you your assigned space and the amount of space being used. This figure is given in KB instead of MB so remember 1000KB = 1MB. You cannot get an accurate reading of the amount of disk space you are using on the Windows systems by checking your Z: drive as this does not include all of the Windows files that get copied back over to your account when you logout.
  • When prompted, type in “y” to view your highest 5 directories

You can also use the command du -k | more in the server environment (| is the pipe found about your enter key).  This will give you a page by page display (use spacebar to advance each page or enter to advance line by line) of your actual disk space used.  This view will show you each individual file with subtotals for each directory.  This easily identifies what files are in your profile that are taking up the most space.

You should note that the following folders located in your Windows lab profile actually reside in your account on the SEASnet servers.

  • Application Data
  • Desktop
  • My Documents
  • Start Menu

The recycle bin also “travels” around with you, so make sure you empty it.

SEASnet has also noticed profiles growing extremely large when the user uses Netscape in the SEASnet labs. The Netscape cache directory is set to 50MB by default. Additionally, the file XUL.mfl can grow quite large. This file contains precompiled chrome and JavaScript and is used for fast loading. It is not neccessary for normal browser functunality and can be deleted without causing any problems.

Users can lower the Netscape default cache size to limit its growth. We recommend 5MB or lower. To set Netscape’s cache size:

  • Edit -> Preferences -> Advanced -> Cache (input new cache size and apply)

There is no way to limit the size of XUL.mfl. However, we can delete the file and create a directory named XUL.mfl. This will trick the brower into thinking that the file has already been created. Since it’s not a file it will not grow large in size. This workaround is appropriate since this file is not neccessary for browser functionality.

SEASnet has also created these additional tips to assist users with their allocated disk space.

 

SEASnet Lab Roaming Profile Quota

All other files and folders (those folders mentioned above are excluded from this quota) located in the users account on the Windows machines in C:Documents and Settings are subject to a 10MB size limit. If you exceed this limit then you will not be allowed to log out until you reduce it. You can click on the profile quota icon on the bottom right of the menu bar to see what is using the disk space. You may need to change your Windows Explorer view to show hidden files and folders.

PrivacIE / Index.dat

This error is the most typical profile quota you’ll see.  In order to correct this, you’ll need to do the following:

  • Open My Computer
  • Click on TOOLS / Folder Options / VIEW tab
  • Click on SHOW HIDDEN FILES AND FOLDERS (to set bullet)
  • Click on HIDE PROTECTED OPERATING SYSTEM FILES (to remove bullet)
  • Click on OK and close all windows
  • OPEN up My Computer / C Drive / user / Your USERNAME folder / PrivacIE / and delete the index.dat
  • Your error will now clear
  • You can get assistance from the 2nd floor front desk LC’s
  • If your file is NOT the index.dat which is causing the problem, browse to the directories listed and delete the file in question

If you are getting an error which is NOT the PrivacIE/Index.dat, look for the icon in the lower right hand corner and open it. This should give you the path to the file / program which is causing the error. Once you have the path, follow the instructions above to go to that location to delete the temp files in question.

 

Note: Profiles do not roam from the lab machines to the terminal server.