[OpenAFS] Fedora 16 and Openafs

Berthold Cogel cogel@uni-koeln.de
Wed, 29 Feb 2012 10:48:42 +0100

Am 28.02.2012 18:00, schrieb Derrick Brashear:
> On Tue, Feb 28, 2012 at 11:55 AM, Berthold Cogel <cogel@uni-koeln.de> w=
>> Hello!
>> I'm trying to get openafs to work on Fedora 16. The rpms from rpmfusio=
>> did work with older kernel versions but failed totally with recent
>> kernels. So I've build my own rpms.
>> I took the source packages for 1.6.1-0.pre2 and build an source rpm wi=
>> the makesrpm.pl. Build and install worked well with some minor fixes t=
>> the files section in the spec file.
>> System is a Dell Latitude E6520 laptop. Because of this an becaus we'r=
>> using DHCP with fixed IPs in our local net, network manager is involve=
>> After activating the client service and rebooting the system I get now=
>> [root@charon/var/log]$ systemctl status openafs-client.service
>> openafs-client.service - OpenAFS Client Service
>>          Loaded: loaded (/lib/systemd/system/openafs-client.service; e=
>>          Active: failed since Tue, 28 Feb 2012 08:07:54 +0100; 8h ago
>>         Process: 1448 ExecStart=3D/usr/vice/etc/afsd $AFSD_ARGS (code=3D=
>> status=3D1/FAILURE)
>>         Process: 1441 ExecStartPre=3D/sbin/modprobe openafs (code=3Dex=
>> status=3D0/SUCCESS)
>>         Process: 1436 ExecStartPre=3D/bin/chmod 0644 /usr/vice/etc/Cel=
>> (code=3Dexited, status=3D0/SUCCESS)
>>         Process: 1418 ExecStartPre=3D/bin/sed -n w/usr/vice/etc/CellSe=
>> /usr/vice/etc/CellServDB.local /usr/vice/etc/CellServDB.dist
>> (code=3Dexited, status=3D0/SUCCESS)
>>          CGroup: name=3Dsystemd:/system/openafs-client.service
>>                  =E2=94=94 1459 /usr/vice/etc/afsd -fakestat -afsdb -d=
>> Although failed, there are several afs processes running which can't b=
>> stopped or killed.
> as always, afsd wants to be shut down with afsd -shutdown. it will
> happily ignore your KILL signals because they're not helpful.

I did try 'systemctl stop openafs-client.service'. This should have
called the lines in openafs-client.service:

ExecStop=3D/bin/umount /afs
ExecStop=3D/usr/vice/etc/afsd -shutdown
ExecStop=3D/sbin/rmmod openafs

But this didn't work. The afsd seemed to be in a state where -shutdown
didn't work. And each restart triggered another bunch of
processes/threads which couldn't be removed.

The interesting part is that this morning the LAN interface got up some
milliseconds earlier during the boot. And so the network manager could
do his job early enough for the afsd. And now stop and start with
systemctl works as expected.

Berthold Cogel