Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 105 to 105 | ||||||||
A practical example of automount | ||||||||
Changed: | ||||||||
< < | My home directory is /a/home/tanya/seligman . Thanks to NIS![]() | |||||||
> > | My home directory is /nevis/tanya/home/seligman . Thanks to NIS![]() | |||||||
this is my home directory no matter which Linux box I'm logged
into. All of my various configuration files and scripts are available
in my ~seligman directory; for example, ~/.zshrc is | ||||||||
Line: 114 to 114 | ||||||||
When I get a chance to do physics, I might simulate![]() | ||||||||
Changed: | ||||||||
< < | /a/home/tanya/seligman/geant4 (or ~seligman/geant4 , | |||||||
> > | /nevis/tanya/home/seligman/geant4 (or ~seligman/geant4 , | |||||||
or simply ~/geant4 for me).
The ATLAS workgroup server is kolya, so I store my compiled
binary files and libraries in | ||||||||
Changed: | ||||||||
< < | /a/home/kolya/seligman/g4work . That way, when my programs | |||||||
> > | /nevis/kolya/home/seligman/g4work . That way, when my programs | |||||||
execute, their physical location is on the same computer that's running the programs. I prefer to compile and execute my programs on the server kolya, which is much faster than my desktop | ||||||||
Line: 129 to 129 | ||||||||
ssh kolya "at -f ~/geant4/calo/LArHits-0.5/cmd/electron.cmd now" When I generate big ROOT Tree files or any other form of output, I can | ||||||||
Changed: | ||||||||
< < | store them in /a/data/kolya/seligman/LArHits , which has a lot of | |||||||
> > | store them in /nevis/kolya/data/seligman/LArHits , which has a lot of | |||||||
available disk space.
Note that these directory names are the same on every system in the Linux cluster: my own desktop tanya, the server kolya, the student desktop workstation eeyore, etc. You have access to all of my work through the same directory names.
Obviously, I don't type in all these long names every time I want to change directories. If you look at ~seligman/.myprofile , you'll see aliases that I've defined for these directory names. For example:
| ||||||||
Changed: | ||||||||
< < | setenv G4WORKDIR /a/home/kolya/seligman/g4work setenv LArDataDir /a/data/kolya/seligman/LArHits | |||||||
> > | setenv G4WORKDIR /nevis/kolya/home/seligman/g4work setenv LArDataDir /nevis/kolya/data/seligman/LArHits | |||||||
However, all this fails if tanya goes down. Then | ||||||||
Changed: | ||||||||
< < | the /a/home/tanya directory would be inaccessible, and I'd | |||||||
> > | the /nevis/tanya/home directory would be inaccessible, and I'd | |||||||
have problems logging onto other machines in the Linux cluster. As an alternative, I could keep my home directory on the server (i.e., | ||||||||
Changed: | ||||||||
< < | /a/home/kolya/seligman ), since if the ATLAS server goes down | |||||||
> > | //nevis/kolya/home/seligman ), since if the ATLAS server goes down | |||||||
I couldn't do any analysis work anyway.
Caveat |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 8 to 8 | ||||||||
The naming scheme for automount directories | ||||||||
Changed: | ||||||||
< < | This section is first because I assume most users at Nevis know what
"mounting a disk" means and have a vague sense what "automount" means.
This section tells you what you really want to know: how to access
files on other Nevis machines just by visiting a directory. The
special directory names are:
This maps to the | |||||||
> > | This section is first because I assume most users at Nevis know what "mounting a disk" means and have a vague sense what "automount" means. This section tells you what you really want to know: how to access files on other Nevis machines just by visiting a directory. The special directory names are: | |||||||
Changed: | ||||||||
< < | | |||||||
> > |
This is perhaps the simpler way of accessing files on another machine. For example, if you want to access the | |||||||
This maps to a Nevis application directory (e.g., /usr/nevis on the applications server. This is soft-linked to /usr/nevis on your computer, so the contents of this directory always come from the applications server.
What does it mean to mount a disk? | ||||||||
Changed: | ||||||||
< < | Suppose you're on one computer system. You want to see files located
on another computer system. You can copy files from the other system
using sftp![]() ![]() ![]() ![]() {computer-name}:{remote-directory} . So if you wanted access
to the /home disk on my computer tanya, you'd want to mount
tanya:/home .
After you've mounted my disk on your computer, you need some way to
refer to it. You probably don't want to call it /home ,
because then you wouldn't be able to refer to a /home
directory that already exists on your computer. Typically you have to
mount a remote directory under some other name. In this example,
let's pick a "local" name for tanya:/home of
/tanya/home . So the mount command would be: | |||||||
> > | Suppose you're on one computer system. You want to see files located on another computer system. You can copy files from the other system
using sftp![]() ![]() ![]() ![]() {computer-name}:{remote-directory} . So if you wanted access to the /home disk on my computer tanya, you'd want to mount tanya:/home .
After you've mounted my disk on your computer, you need some way to refer to it. You probably don't want to call it /home ,
because then you wouldn't be able to refer to a /home directory that already exists on your computer. Typically you have to
mount a remote directory under some other name. In this example, let's pick a "local" name for tanya:/home of /tanya/home . So the mount command would be: | |||||||
mount tanya:/home /tanya/homeIf you could execute this command, then you could cd /tanya/home and see the files in /home on tanya. | ||||||||
Changed: | ||||||||
< < | But if you tried to execute the above command, you probably got an
error message because you're not running an account with
administrative privileges. Even if you were, you have to make sure to
create the directory /tanya/home on your machine before you
execute the mount command. Once you were through accessing
the directory, you'd have to remember to unmount it. And if you had
to access many directories on many computers (which is common in a
cluster), you'd have to remember all these details for each directory | |||||||
> > | But if you tried to execute the above command, you probably got an error message because you're not running an account with
administrative privileges. Even if you were, you have to make sure to create the directory /tanya/home on your machine before you
execute the mount command. Once you were through accessing the directory, you'd have to remember to unmount it. And if you had
to access many directories on many computers (which is common in a cluster), you'd have to remember all these details for each directory | |||||||
you mounted. | ||||||||
Changed: | ||||||||
< < | As you've already guessed, automount takes care of all these
details for you. | |||||||
> > | As you've already guessed, automount takes care of all these details for you. | |||||||
What does automount do? | ||||||||
Line: 123 to 89 | ||||||||
benjamin:/mail/inbox 4.1G 3.1G 1.0G 76% /a/mail/inbox library:/usr/nevis 17G 11G 5.0G 69% /a/apps/local | ||||||||
Changed: | ||||||||
< < | The first three filesystems are partitions on my system. The
last two are directories on remote computer systems that have been
mounted on tanya by automount : | |||||||
> > | The first three filesystems are partitions on my system. The last two are directories on remote computer systems that have been mounted on tanya by automount : | |||||||
| ||||||||
Line: 137 to 101 | ||||||||
Changed: | ||||||||
< < | When you do your work, you can ignore all these links. Just access a
directory using the automount naming
scheme and let the system take care of the links for you. | |||||||
> > | When you do your work, you can ignore all these links. Just access a directory using the automount naming scheme and let the system take care of the links for you. | |||||||
A practical example of automount | ||||||||
Line: 170 to 132 | ||||||||
store them in /a/data/kolya/seligman/LArHits , which has a lot of
available disk space. | ||||||||
Changed: | ||||||||
< < | Note that these directory names are the same on every system in the
Linux cluster: my own desktop tanya, the server kolya,
Mikhail Leltchouk's desktop client anna, etc. Mikhail has
access to all of my work through the same directory names.
Obviously, I don't type in all these long names every time I want to
change directories. If you look at ~seligman/.myprofile ,
you'll see aliases that I've defined for these directory names. For
example: | |||||||
> > | Note that these directory names are the same on every system in the Linux cluster: my own desktop tanya, the server kolya, the student desktop workstation eeyore, etc. You have access to all of my work through the same directory names.
Obviously, I don't type in all these long names every time I want to change directories. If you look at ~seligman/.myprofile , you'll see aliases that I've defined for these directory names. For example: | |||||||
setenv G4WORKDIR /a/home/kolya/seligman/g4work setenv LArDataDir /a/data/kolya/seligman/LArHits | ||||||||
Line: 190 to 146 | ||||||||
alternative, I could keep my home directory on the server (i.e.,
/a/home/kolya/seligman ), since if the ATLAS server goes down
I couldn't do any analysis work anyway. | ||||||||
Added: | ||||||||
> > |
CaveatFor you to access a given partition or disk on a remote computer, that computer has to export![]() /nevis/tanya/etc , because the system tanya does not export that directory for mounting by other computers. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 6 to 6 | ||||||||
Deleted: | ||||||||
< < | IMPORTANTIf you refer to any path that begins with the text/.automount , you are automatically doing something wrong. If you write to a systems administrator![]() /a not /.automount ; use of the latter guarantees that your task will fail. | |||||||
The naming scheme for automount directoriesThis section is first because I assume most users at Nevis know what | ||||||||
Line: 124 to 120 | ||||||||
/dev/hda5 486M 190M 271M 41% / /dev/hda6 2.7G 1014M 1.6G 38% /home /dev/hda7 972M 849M 72M 92% /usr | ||||||||
Changed: | ||||||||
< < | franklin:/mail/inbox 4.1G 3.1G 1.0G 76% /.automount/a/franklin/mail/inbox karthur:/usr/local 17G 11G 5.0G 69% /.automount/a/karthur/usr/nevis | |||||||
> > | benjamin:/mail/inbox 4.1G 3.1G 1.0G 76% /a/mail/inbox library:/usr/nevis 17G 11G 5.0G 69% /a/apps/local | |||||||
The first three filesystems are partitions on my system. The
last two are directories on remote computer systems that have been
mounted on tanya by automount : | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
# ls -ld ${NevisAppBase} | ||||||||
Line: 141 to 137 | ||||||||
Deleted: | ||||||||
< < | You'll notice that the directory under which the remote system is
mounted is /.automount . This is an
automount convention; you should leave this directory alone (see the warning above).
If you list the name of a directory that automount monitors,
you can see the link:
# ls -ld /a/mail/inbox lrwxrwxrwx 1 root root 34 Jul 12 11:35 /a/mail/inbox -> /.automount/a/franklin/mail/inbox | |||||||
When you do your work, you can ignore all these links. Just access a
directory using the automount naming
scheme and let the system take care of the links for you. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 24 to 24 | ||||||||
computer, you will see the contents of /home/seligman on
tanya. | ||||||||
Added: | ||||||||
> > |
This maps to the | |||||||
This maps to the | ||||||||
Line: 32 to 38 | ||||||||
Not every computer has a /data partition. If you try to access
/a/data/hypatia , you'll get an error message. | ||||||||
Changed: | ||||||||
< < |
This maps to the | |||||||
> > |
This maps to the | |||||||
This maps to the | ||||||||
Line: 47 to 51 | ||||||||
/a/file/d0disk/d0/steinbru from my computer, I will see the
contents of /file/d0disk/d0/steinbru on archive. | ||||||||
Changed: | ||||||||
< < | This is meant to be a way for long-time users to access files that were
formerly on nevis1, a central Nevis server that no longer exists![]() | |||||||
> > | This is meant to be a way for long-time users to access files that were formerly on nevis1, a central Nevis server that no longer exists![]() | |||||||
This maps to the |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 38 to 38 | ||||||||
usually this is an additional disk that was added to the server. As
of May 2010, no servers export any /work partitions. | ||||||||
Changed: | ||||||||
< < |
This maps to the | |||||||
> > |
This maps to the | |||||||
This maps to the | ||||||||
Line: 58 to 58 | ||||||||
server. See the mail-related files page for more information.
| ||||||||
Changed: | ||||||||
< < | This maps to a Nevis application directory (e.g., /usr/nevis on the applications server. This is soft-linked to the directory defined in ${NevisAppBase} on your computer, so the contents of this directory always come from the applications server. | |||||||
> > | This maps to a Nevis application directory (e.g., /usr/nevis on the applications server. This is soft-linked to /usr/nevis on your computer, so the contents of this directory always come from the applications server. | |||||||
What does it mean to mount a disk? |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nevis Linux Cluster - Automount | ||||||||
Line: 43 to 43 | ||||||||
of May 2010, only xenia has a /teir3 partition.
| ||||||||
Changed: | ||||||||
< < | This maps to the /file directory on the archive file server![]() | |||||||
> > | This maps to the /file directory on the archive file server. For example, if I access | |||||||
/a/file/d0disk/d0/steinbru from my computer, I will see the
contents of /file/d0disk/d0/steinbru on archive. | ||||||||
Line: 58 to 58 | ||||||||
server. See the mail-related files page for more information.
| ||||||||
Changed: | ||||||||
< < | This maps to a Nevis application directory (e.g., /usr/nevis on the applications server![]() ${NevisAppBase} on your computer, so the contents of this directory always come from the applications server. | |||||||
> > | This maps to a Nevis application directory (e.g., /usr/nevis on the applications server. This is soft-linked to the directory defined in ${NevisAppBase} on your computer, so the contents of this directory always come from the applications server. | |||||||
What does it mean to mount a disk? |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Nevis Linux Cluster - AutomountThis page describes how automount![]() IMPORTANTIf you refer to any path that begins with the text/.automount , you are automatically doing something wrong. If you write to a systems administrator![]() /a not /.automount ; use of the latter guarantees that your task will fail.
The naming scheme for automount directoriesThis section is first because I assume most users at Nevis know what "mounting a disk" means and have a vague sense what "automount" means. This section tells you what you really want to know: how to access files on other Nevis machines just by visiting a directory. The special directory names are:
This maps to the |