Re: [OpenAFS] Crash in volserver when restoring volume from backup.

2009-10-16 Thread Anders Magnusson
Derrick Brashear wrote: looks like you already lost by the time it crashes. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x4aafd940 (LWP 30735)] 0x003c13078d60 in strlen () from /lib64/libc.so.6 (gdb) bt #0 0x003c13078d60 in strlen () from

Re: [OpenAFS] GSoC Server priorities

2009-10-16 Thread Lars Schimmer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jake Thebault-Spieker wrote: On Thu, Oct 15, 2009 at 2:19 AM, Lars Schimmer l.schim...@cgv.tugraz.atwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I've seen the code for server priorities made in a GSoC is in the private windows

Re: [OpenAFS] GSoC Server priorities

2009-10-16 Thread Jeffrey Altman
Lars Schimmer wrote: Thank you, that helped. Our point is: we got some clients in a 10.x subnet which is not routed across VPN ad therefore those clients cannot reach that fileserver. An as you tell, based on transmitted rx - with no traffic, no stats, no change for us. Lars: If you can

[OpenAFS] OpenAFS client memory usage

2009-10-16 Thread Baumann Niklaus (LOG)
Hi, I have some questions about how OpenAFS 1.5.6400 works with RAM on Windows XP (SP2/SP3): While copying data from/to AFS, the afsd_service.exe increases it's working set and fills the cachefile (at least fs getcacheparms tells). On a client with a cache file of 384MB and 3GB RAM the mem

Re: [OpenAFS] OpenAFS client memory usage

2009-10-16 Thread Jeffrey Altman
Baumann Niklaus (LOG) wrote: Hi, I have some questions about how OpenAFS 1.5.6400 works with RAM on Windows XP (SP2/SP3): While copying data from/to AFS, the afsd_service.exe increases it's working set and fills the cachefile (at least fs getcacheparms tells). On a client with a cache

[OpenAFS] Troubles with multihomed, nat'ed file server.

2009-10-16 Thread Scott Peshak
I've got a file server that is behind a nat and is also multihomed that is no longer working from outside the nat. It was working fine outside for a long while, though we're not sure when it stopped (It gets very light use externally). The server's NetInfo looks like this: 192.168.1.108