This page briefly describes the uses, sizes, access methods,
and policies for each of the
major user disk areas on the pangea network server.
|
Disk Area
|
Uses and Size
|
Access and Policies
|
|
/home
|
Base of the home directory tree.
Separate disks for each department or group map to subdirectories
/home/ges,
/home/gp,
/home/pete, and
/home/other.
Dean's Office, Earth Systems, and guest users share the
/home/other
disk area.
Total storage capacity: 114,000 Megabytes
|
Permanent storage of user files. Each user only has write permission
to his own home directory.
Files in
/home
are regularly backed up to magnetic tape and
can be recovered
if accidentally erased.
Informal guidelines limit storage to 200 Megabytes per regular user and 30
Megabytes per guest user. Do
not
use your pangea home directory for "temporary" storage of large files
that you are transferring between computers. Use the
/play or /scr1 directory
for that purpose.
|
|
/var/spool/mail
|
Location of email "inboxes".
Total storage capacity: 37,000 Megabytes
|
There is a separate file to store new mail for each account.
Files in
/var/spool/mail
are regularly backed up to magnetic tape and
can be recovered
if accidentally erased.
Informal guidelines limit storage of old or unread email
to 200 Megabytes per regular user and 30 Megabytes per guest user.
Do not configure your email program to "leave mail on server"
indefinitely. Include a reasonable time limit for old, already
downloaded email to persist - for example, seven days.
|
|
/play
|
Directory tree for "medium term" temporary storage of user files.
Subdirectory structure that parallels the
/home
directories.
Total storage capacity: about 18,400 Megabytes
|
Files regularly backed up to magnetic tape and
can be recovered
if accidentally erased.
Files put in
/play
are
automatically erased after twelve weeks with no warning.
No limits on amount of disk space one account can use.
|
|
/scr1
|
Short-term temporary scratch space for user files
The symbolic link
/scr
also points to
/scr1.
Total storage capacity: about 18,400 Megabytes
|
Files are
not
backed up to magnetic tape.
Files put in
/scr1
are
automatically erased after fifteen days with no warning.
All users have permission to create files here. Please make a subdirectory
with your account name to store your files.
No limits on amount of disk space one account can use.
|
|
/aufs
|
Base of the personal "Classic" Macintosh volume directory tree.
Mac OS X users access their entire home directory as a
network file share.
Subdirectory structure parallels that in
/home.
For example, if your home directory is
/home/gp/joe,
then there is also an
/aufs/gp/joe
directory for you to use.
Total storage capacity: 9,000 Megabytes
|
This disk area can only be accessed as a
Macintosh volume for storage of Macintosh files and programs via the
pangea Aufs
AppleShare server in the
ES-Ethernet
AppleTalk network zone.
This zone is only visible in the
Chooser
when connected to the Earth Sciences network.
Otherwise, it is accessible via AppleShare/IP from anywhere
on campus under then name
pangea.stanford.edu.
This disk area is maintained for historical use by "classic"
Macintosh OS 8 and 9 and will eventually be phased out.
MacOS X users can and should use their home directories for
Macintosh file storage.
When connected to the server, you will see the volume name
Pangea-username-Mac-files,
where your account name substitutes for
username.
Files regularly backed up to magnetic tape and
can be recovered
if accidentally erased.
Informal guidelines limit storage to 30 Megabytes per regular user
and 5 Megabytes per guest.
|
|
/ftp
|
Files served to the entire Internet via anonymous ftp.
Total storage capacity: about 5,600 Megabytes for temporary files
and 9,200 Megabytes for permanent distribution.
|
For sharing files with colleagues who do not have pangea accounts.
See the
How to use anonymous ftp on pangea
web page for instructions.
Files in temporary disk area
/ftp/pub/share
are automatically erased after 7 days.
Files in other subdirectories of
/ftp/pub
may stay indefinitely, but are
not
backed up.
No specific disk quotas.
|
|
/WWW
|
"Home directory" of the pangea
World Wide Web server.
Contains system, department, and research group web files.
Personal web files
go into the
WWW
subdirectory of your home directory.
|
Files are regularly backed up to magnetic tape and
can be recovered
if accidentally erased.
Contact the
web manager
to get access to update particular department or research group files.
|
|
/afs
|
Entry point to a world-wide distributed file system called AFS.
Directories and files from other computers around the world are visible under
this directory tree as if they were on local disk.
Each remote site has a main subdirectory usually named the same as its network
domain, for example, "ir.stanford.edu" is the AFS domain for Stanford
University.
|
Pangea access to this file system is read-only for system files.
From pangea, you can get read/write access to your leland home directory,
which is located in a subdirectory of
/afs/ir.stanford.edu/users,
if you have the proper AFS kerberos credential.
ssh command line logins
and
scp or sftp file transfer logins
to pangea will automatically get the correct AFS kerberos credentials
if your pangea account name matches your SUNet ID name, and you
login with your SUNet ID password instead of your
pangea local password.
If you login via another method, you must first run the
klog
command on pangea to get your AFS kerberos credentials; in this case,
your SUNet ID account name must match your pangea account name and you
must supply your SUNet ID password when prompted.
|
|
Other network attached file systems
|
Places to attach file systems from other computers via the NFS network
software.
These remote file systems remain on the remote computer disk but appear as
if they were locally connected. For example, directories from a computer
named
myserver
would be accessed via
/myserver.
|
System managers of
pangea
and the remote computer must cooperate to establish this access.
Pangea users have the same permissions to modify or add files in these
remote directories as if they were logged into the remote system (which
also means you have
no
access if you do not have an account on the remote system).
Some remote file systems may be connected in "read-only" mode.
|
