|
Size: 4554
Comment:
|
Size: 4862
Comment: spam
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma section-numbers off This page explains some nuances of the Andrew File System (AFS), which we use to serve home directories. <<TableOfContents>> |
|
| Line 41: | Line 47: |
| a keytab, such as `kadmin -p domtool/deleuze -k -t /etc/keytabs/domtool.deleuze` . | a keytab, such as `kadmin -p domtool -k -t /etc/keytabs/domtool` . |
| Line 78: | Line 84: |
= Listing and setting quotas = To list volume quota, run{{{ fs lq DIR }}} To set volume quota in 1-kilobyte blocks, run{{{ fs sq DIR -max SIZE }}} |
This page explains some nuances of the Andrew File System (AFS), which we use to serve home directories.
Basic Architecture
Using the shared filesystem involves a combination of Kerberos and OpenAFS.
File conventions
The /afs tree contains shared filesystems. /afs/hcoop.net (symlinked from /afs/hcoop as well) is our piece of the AFS-o-sphere. Subdirectories include:
/afs/hcoop.net/user, the home of home directories
/afs/hcoop.net/user/U/US/$USERNAME, $USERNAME's home directory
/afs/hcoop.net/common/etc, the home of non-platform-specific fun stuff like DomTool
Connecting to AFS from an HCoop server
I found this handy summary of the commands that must be run:
On our servers, it seems sufficient to run: