Hello
As one of the admins bedie us told me, there needs something special to
be taken care of while updating 1.4.12 Debian OpenAFS fileserver to 1.6,
I just want to ask here.
On webpage and in release note I did not seen anything about to take of,
neither do I remember.
But did I miss
As one of the admins bedie us told me, there needs something special to be
taken care of while updating 1.4.12 Debian OpenAFS fileserver to 1.6, I just
want to ask here.
On webpage and in release note I did not seen anything about to take of,
neither do I remember.
But did I miss
in our cell enea.it we had the same problem long ago and we were able to
repair the situation in the way that was described at the Openafs
Best Practices Workshop 2005:
http://workshop.openafs.org/afsbpw05/talks/VirtualAFScell_Bracco_Pittsburgh2005.pdf
No idea at that time (nor now!) of how
Something is broken or not returning particularly useful error messages:
hozer@six:~$ /usr/sbin/afsd.fuse /tmp/afs
fuse: bad mount point `': No such file or directory
hozer@six:~$ /usr/sbin/afsd.fuse -- /tmp/afs
fuse: bad mount point `--': No such file or directory
hozer@six:~$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 19.09.2011 16:39, schrieb Andrew Deason:
Yes, sorry, I read 'below' as 'above'. In this case, perhaps the
client still had old vldb information, which did not contain the RO
site? The 'vos examine' info for the RO said:
CreationSat Sep
I have not set up fuse on this machine for regular user access, but I get the
same behavior
on another machine that is configured.
hozer@six:~/cray/msgq$ sudo /usr/sbin/afsd.fuse -mountdir /tmp/afs/ -cachedir
/tmp/vcache/ -d
[sudo] password for hozer:
Sorry, try again.
[sudo] password for
Hi,
Dunno. My fuse ukernel is pretty old, and worked. From the src, afs_root() is
failing. Might be an issue with the supplied dirs? I would at this point
build with full debugging and trace into it.
Matt
- Troy Benjegerdes ho...@hozed.org wrote:
I have not set up fuse on this
