test

[hcoop/zz_old/ikiwiki] / TroubleshootingAFS.mdwn

diff --git a/TroubleshootingAFS.mdwn b/TroubleshootingAFS.mdwn
new file mode 100755 (executable)
index 0000000..d4468c5
--- /dev/null
+++ b/TroubleshootingAFS.mdwn
@@ -0,0 +1,13 @@
+= AFS on Debian/Ubuntu =\r
+\r
+The instructions on http://research.cs.berkeley.edu/doc/afs/debian.html page, linked elsewhere in the wiki, were enough to get me started.  I use a non-stock kernel in Ubuntu Feisty, and had no problem building and loading the OpenAFS modules.  Even with that, I've stumbled on 2 problems.\r
+\r
+== ReiserFS ==\r
+\r
+First, if you are using ReiserFS, the AFS daemon will simply refuse to work because it cannot use that filesystem for its cache.  If the daemon doesn't run, you'll get a puzzling error message that might make you think you have a firewall problem.  I lost some time over that.  I discovered it wasn't the case by Googling a bit.\r
+\r
+To get the daemon to work, I had to edit the `/etc/openafs/afs.conf` to make it use the memory cache.  It is said to be less stable than the hard disk cache.  I have not had obvious problems with it yet.  The README.Debian file also suggests creating a loopback ext2 filesystem for the cache.  If I ever need to use this technique, I'll try to remember to document it here.\r
+\r
+== Konqueror ==\r
+\r
+Konqueror simply hung up when I tried to browse /afs with the default CellServerDB.  I suspect it is because it is trying to access AFS volumes it doesn't have access to or that are not accessible, and hangs indefinitely.  There is a lot of cells pre-configured in the Debian package, and probably some of them are not valid or not accessible.  Once I erased the content of /etc/openafs/CellServerDB but left just the hcoop.net entry, I managed to browse /afs with Konqueror\r