Re: [OpenAFS] klog really slow (Fedora Core Linux, kernel-2.6.14-1.1656_FC4)

2006-01-20 Thread zeroguy
On Fri, 20 Jan 2006 22:41:02 +0100 Sergio Gelato <[EMAIL PROTECTED]> wrote: > * Paul Johnson [2006-01-19 23:21:01 -0600]: > > Starting AFS cache scan...<6>tg3: eth0: Link is up at 10 Mbps, half duplex. > > That's a slow network link by today's standards, and half duplex can > lead to a higher rat

Re: [OpenAFS] Questions about OpenAFS "reality"

2006-01-20 Thread Jan Johansson
You received many good answers and I would just like to add some small details. Leroy Tennison <[EMAIL PROTECTED]> wrote: > How does AFS compare in administrative burden compared to the > common PC NOSes (NetWare and AD)? It has been quite long since I saw NetWare but keeping file history so user

Re: [OpenAFS] klog really slow (Fedora Core Linux, kernel-2.6.14-1.1656_FC4)

2006-01-20 Thread Sergio Gelato
* Paul Johnson [2006-01-19 23:21:01 -0600]: > When I type > > $ klog pauljohn > > the system waits for between 40 and 50 seconds. THere are no errors, > and eventually the klog is approved. The connection is good and I can > move files in and out of /afs/ku.edu, our cell. [...] > How to debug?

Re: [OpenAFS] can't unount afs on macos 10.4 with 1.4.1-rc4

2006-01-20 Thread Derrick J Brashear
On Fri, 20 Jan 2006, Dan Pritts wrote: the installation notes when installing openafs 1.4.1-rc4 suggest that you unmount /afs manually before shutdown, or else the system will hang. I can confirm the hanging problem. I can't, however, figure out how to successfully unmount. vfr800:~ root# um

[OpenAFS] can't unount afs on macos 10.4 with 1.4.1-rc4

2006-01-20 Thread Dan Pritts
the installation notes when installing openafs 1.4.1-rc4 suggest that you unmount /afs manually before shutdown, or else the system will hang. I can confirm the hanging problem. I can't, however, figure out how to successfully unmount. vfr800:~ root# umount /afs umount: unmount(/afs): Resour

Re: [OpenAFS] klog very slow in Fedora Core Linux (kernel-2.6.14-1.1656_FC4)

2006-01-20 Thread Derek Atkins
Um, it did make it to the list just fine the first time. Perhaps you have yourself set to "don't receive own posts"? Anyways, are you sure that the contents of /usr/vice/etc/CellServDB for the local cell are correct? Also, can you reach each of the IPs that you get from a DNS lookup for the ser

[OpenAFS] klog very slow in Fedora Core Linux (kernel-2.6.14-1.1656_FC4)

2006-01-20 Thread Paul Johnson
Hello, openafs list: I sent this last night, but it did not appear yet, sorry if you get two copies. Our Sysadmin built an openafs server with very much storage and he says Windows clients access it without delay. On my Linux systems, however, I observe some very strange/sluggish behavior. And

Re: [OpenAFS] slab error in kmem_cache_destroy

2006-01-20 Thread Derrick J Brashear
On Fri, 20 Jan 2006, Hendrik Hoeth wrote: Thus spake Derrick J Brashear ([EMAIL PROTECTED]): What's the reason for this behaviour? What has changed between before and after the first attempt to start the client? Just the kernel error I pasted in my previous mail or is there something else forci

Re: [OpenAFS] slab error in kmem_cache_destroy

2006-01-20 Thread Hendrik Hoeth
Thus spake Derrick J Brashear ([EMAIL PROTECTED]): > >What's the reason for this behaviour? What has changed between before > >and after the first attempt to start the client? Just the kernel > >error I pasted in my previous mail or is there something else forcing > >me to reboot? > > no, the kern

Re: [OpenAFS] slab error in kmem_cache_destroy

2006-01-20 Thread Derrick J Brashear
On Fri, 20 Jan 2006, Hendrik Hoeth wrote: Hi, Thus spake Derrick J Brashear ([EMAIL PROTECTED]): you'll need to reboot. otherwise, it won't work. Thanks! What's the reason for this behaviour? What has changed between before and after the first attempt to start the client? Just the kernel er

Re: [OpenAFS] slab error in kmem_cache_destroy

2006-01-20 Thread Hendrik Hoeth
Hi, Thus spake Derrick J Brashear ([EMAIL PROTECTED]): > you'll need to reboot. otherwise, it won't work. Thanks! What's the reason for this behaviour? What has changed between before and after the first attempt to start the client? Just the kernel error I pasted in my previous mail or is there