You could always just use openafs client.
Yes, it works.
Working on a howto, for configuring the client.
-bash-3.00# modstat
Type Id Off Loadaddr Size Info Rev Module Name
VFS 0 0 e36e4000 0077 e374f748 2 afs
-bash-3.00# ps |grep afsd
9011 p4 I+ 0:00.00 grep afsd
28154 C0- DKL 0:00.00 (afsd)
4188 C0- IKL 0:00.00 (afsd)
21217 C0- DKL 0:00.92 (afsd)
30134 C0- DKL 0:00.00 (afsd)
14611 C0- DKL 0:00.00 (afsd)
19159 C0- DKL 0:00.00 (afsd)
30863 C0- DKL 0:00.00 (afsd)
23582 C0- DKL 0:00.00 (afsd)
17813 C0- DKL 0:01.02 (afsd)
13379 C0- DKL 0:00.10 (afsd)
21462 C0- DKL 0:00.04 (afsd)
4849 C0- DKL 0:00.00 (afsd)
-bash-3.00# df
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/wd0a 38384476 16628716 19836540 46% /
AFS 144000000 0 144000000 0% /afs
-bash-3.00# uname -a
OpenBSD bench.linbsd.org 3.7 BULLSEYE#1 i386
-bash-3.00#
-Ober
On Tue, 4 Oct 2005, scorch wrote:
Jan Johansson said the following on 2005-09-29 11:44:
Hello.
I am having problems with arla. 2 of 3 reboots the afsd will be running but
$ cd /afs
ksh: cd: /afs - Not a directory
I did not see this problem on 3.7. I did start to see it on my home pc but
took
it as a fluke because of the amount of problems I have with that machine.
Today
I installed
OpenBSD 3.8-current (GENERIC) #159: Tue Sep 27 22:21:33 MDT 2005
on my laptop (that have been rock solid with 3.7) and see the problem
imediatly.
hi Jan,
I can't speak from experience, I'm not running -current on OpenBSD with
OpenAFS yet.
my only issues in several months of reasonably heavy arla usage has been with
physical disk IO errors, and then needing to flush the cache afterwards.
try rm -rf /var/spool/afs before restarting arla next time, and also using
these arla flags in your rc.* somewhere.
afs=YES
afsd_flags="--log=/var/log/arlad.log --recover"
maybe this will help get more info, & also ensure a clean startup.
can you determine if you always have the issue accessing a file from cache,
or not? fs flush* may help here as well.
cheers, scorch
--
out of the frying pan and into the fire
