HOWTO : install and use the open-afs client [dapper]

[JDahl]

Openafs 1.4.2 (included in Debian Unstable) works fine with never kernels.
To build a package from Debian's source-package do the following:

1) Make a directory "openafs" and download the packages to it from:
$ mkdir openafs; cd openafs
$ wget http://ftp.debian.org/debian/pool/ma....2.orig.tar.gz
$ wget http://ftp.debian.org/debian/pool/ma....4.2-2.diff.gz

2) Unpack and patch
$ tar xzvf openafs_1.4.2.orig.tar.gz
$ zcat openafs_1.4.2-2.diff.gz | patch -p0

3) Install necessary dependencies
$ sudo apt-get build-dep openafs-client
$ sudo apt-get install build-essential fakeroot

4) Build the Debian packages (takes a long time)
$ cd openafs-1.4.2
$ chmod u+x debian/rules
$ dpkg-buildpackage -rfakeroot
Compilation may fail if you don't have all dependencies installed. Just install the missing packages and rebuild.

5) Install the packages
$ sudo dpkg -i ../openafs-modules-source_1.4.2-2_all.deb openafs-client_1.4.2-2_i386.deb

6) Build the kernel module
$ sudo apt-get install module-assistant
$ sudo module-assistant prepare openafs-modules
$ sudo module-assistant auto-build openafs-modules
$ sudo dpkg -i openafs-modules-2.6.17-10-386_1.4.2-2+2.6.17-10.33_i386.deb

7) Install the packages (and say [Y]es to overwriting /etc config scripts; there's a bug in the old ones)
$ sudo dpkg -i /usr/src/openafs-modules-2.6.17-10-386_1.4.2-2+2.6.17-10.33_i386.deb


That did if it for me, at least.

[Sethiano]

dpkg-deb: parse error, in file `debian/openafs-dbg/DEBIAN/control' near line 6 package `openafs-dbg':
 `Depends' field, reference to `openafs-fileserver': error in version: version string is empty

This is what i get when I try run the

dpkg-buildpackage -rfakeroot

command.

Any suggestions?

Thanks!

[JDahl]

I don't know where that error comes from.

This is line 6 from my version of
debian/openafs-dbg/DEBIAN/control

Depends: openafs-fileserver (= 1.4.2-2)

I don't see any reason why yours should be empty. Maybe you can just
manually insert the fileserver version number?

It probably wouldn't take the Ubuntu package maintainer long to update the
openafs package, though, which would be the preferred solution to this problem.

[Sethiano]

Openafs 1.4.2 (included in Debian Unstable) works fine with never kernels.
To build a package from Debian's source-package do the following:

1) Make a directory "openafs" and download the packages to it from:
$ mkdir openafs; cd openafs
$ wget http://ftp.debian.org/debian/pool/ma....2.orig.tar.gz
$ wget http://ftp.debian.org/debian/pool/ma....4.2-2.diff.gz

2) Unpack and patch
$ tar xzvf openafs_1.4.2.orig.tar.gz
$ zcat openafs_1.4.2-2.diff.gz | patch -p0

3) Install necessary dependencies
$ sudo apt-get build-dep openafs-client
$ sudo apt-get install build-essential fakeroot

4) Build the Debian packages (takes a long time)
$ cd openafs-1.4.2
$ chmod u+x debian/rules
$ dpkg-buildpackage -rfakeroot
Compilation may fail if you don't have all dependencies installed. Just install the missing packages and rebuild.

5) Install the packages
$ sudo dpkg -i ../openafs-modules-source_1.4.2-2_all.deb openafs-client_1.4.2-2_i386.deb

6) Build the kernel module
$ sudo apt-get install module-assistant
$ sudo module-assistant prepare openafs-modules
$ sudo module-assistant auto-build openafs-modules
$ sudo dpkg -i openafs-modules-2.6.17-10-386_1.4.2-2+2.6.17-10.33_i386.deb

7) Install the packages (and say [Y]es to overwriting /etc config scripts; there's a bug in the old ones)
$ sudo dpkg -i /usr/src/openafs-modules-2.6.17-10-386_1.4.2-2+2.6.17-10.33_i386.deb


That did if it for me, at least.

So, I did a upgrade to Edgy Eft with kernel 2.6.17-10-386 and your guide workt perfectly!

Thanks for all the help!

P.S Now that we know this, JDahl and other users should be aware that there is possible to run AFS perfectly on Edgy Eft.

[jamesotron]

I managed to get openafs-modules to build on my Edgy ppc64 (G5 iMac) machine and all seems to be working except for a stack trace in aklog:

[16:31][jnt@bingo]~$ kinit jtys003
Password for jtys003@EC.AUCKLAND.AC.NZ: 
[16:32][jnt@bingo]~$ aklog
stackcheck = 0: stack = 0 
topstack = 0xf7fcb03c: stackptr = 0xf7f9b008: stacksize = 0x30000
Wed Nov 15 16:32:04 2006 LWP: stack overflow in process IO MANAGER!
Aborted (core dumped)

If anyone has any suggestions I'd be glad to hear them.

[krugger]

The current openAFS version in the universe repositories is still 1.4.1. Why is that? Debian packages for 1.4.2 which solve the rlim problem that is happening with the 2.6.17/18 kernel has been in debian testing for about a month now. Who do I have to mail to get openAFS to 1.4.2 in universe?

And version 1.5.12 of AFS lists only Windows and Mac support.

Besides suggesting that you report the stack overflow to the AFS people, I can't help much more.

EDIT: my noobiness made me forget to check if it had been released in feisty, lets see if I a backport is possible

[bodhi.zazen]

Nice How-to

This thread has been added to the UDSF wiki.

Open-afs_client

[JMoriarty]

Backport openafs-1.4.2 from Feisty:

1. Edit /etc/apt/sources.list to add these lines:
deb http://fr.archive.ubuntu.com/ubuntu/ feisty universe multiverse
deb-src http://fr.archive.ubuntu.com/ubuntu/ feisty universe multiverse

This will add the feisty repositories.
2. Edit /etc/apt/preferences file to add:
Package: *
Pin: release a=feisty
Pin-Priority: 200

Package: openafs-modules-source
Pin: release a=feisty
Pin-Priority: 999

This will deactivate all feisty packages except the openafs-modules-sources package.

After that, proceed as usual with openafs installation.

[Luggy]

I've been following the original instructions and I'm encountering a strange problem. When I try and start afs I get the following error

paul@paul-desktop:~$ sudo /etc/init.d/openafs-client start
Password:
Starting AFS services: afsd.
afsd: All AFS daemons started.
afsd: Can't mount AFS on /afs(22)

Any ideas?

[lamnk]

I've been following the original instructions and I'm encountering a strange problem. When I try and start afs I get the following error

afsd: Can't mount AFS on /afs(22)

I think it's very obvious from the output that afsd has no write access on /afs ...