[OpenAFS] Re: AFS Perl module and threaded Perl

2004-12-01 Thread Norbert Gruener
Hi Russ, On Wed, Dec 01 2004, Russ Allbery wrote: I'd really like to use the AFS Perl module in a few more places than I'm using it now, including on Debian systems where we're using the Debian Perl. The problem is that Debian Perl is built with threading support, which the AFS Perl module

Re: [OpenAFS] OpenAFS 1.2.13 and fsck problems on Solaris 9

2004-12-01 Thread Douglas E. Engert
Andy Malato wrote: I have seen similar postings on this topic in the mail archives, however, I don't know if this issue has been completly resolved. I am running OpenAFS 1.2.13 on Solaris 9 with kernel patch 117171-07. According to what I have read in the archive postings it appears that Sun has

Re: [OpenAFS] OpenAFS 1.2.13 and fsck problems on Solaris 9

2004-12-01 Thread Andy Malato
! Date: Wed, 01 Dec 2004 08:06:05 -0600 ! From: Douglas E. Engert [EMAIL PROTECTED] ! To: Andy Malato [EMAIL PROTECTED] ! Cc: [EMAIL PROTECTED] ! Subject: Re: [OpenAFS] OpenAFS 1.2.13 and fsck problems on Solaris 9 ! ! ! ! ! ! Andy Malato wrote: ! ! I have seen similar postings on this topic in

[CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: On Fri, 29 Oct 2004, David Thompson wrote: The ACLs on the directory give this user read acess but no write. Like I said, the openafs code is the same on both boxes. Has anyone seen anything like this? Is this a kernel change? Perchance does one support 64 bit

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
Ew, a widereply. Perchance does one support 64 bit locks (F_GETLK64) and the other doesn't? Box 2 (flock doesn't work per the man page): open(/s/db-apps/lib/GradApp/lib/GradApp.pbk, O_RDONLY|O_LARGEFILE) = 4 ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfffae08) = -1 EINVAL (Invalid argumen t)

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: fine, so i'll guess this function calls one of our ops (getattr?) and somehow loses, because EACCES shouldn't be coming from afs_lockctl (at least not directly) Can you fstrace both cases? Here's the sample C program I'm using: #include sys/file.h #include

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
On Wed, 1 Dec 2004, David Thompson wrote: time 962.599815, pid 21833: Open 0x422de2c4 flags 0x0 time 962.599815, pid 21833: Open 0x422de2c4 flags 0xf423f time 962.599815, pid 21833: Analyze RPC op 13 conn 0x2128b4c0 code 0xd user 0x417529fa time 962.599815, pid 21833: Returning code 13 from 1 time

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread David Thompson
Derrick J Brashear wrote: On Wed, 1 Dec 2004, David Thompson wrote: time 962.599815, pid 21833: Open 0x422de2c4 flags 0x0 time 962.599815, pid 21833: Open 0x422de2c4 flags 0xf423f time 962.599815, pid 21833: Analyze RPC op 13 conn 0x2128b4c0 code 0xd user 0x417529fa time 962.599815, pid

Re: [CSL #248914] [OpenAFS] flock() behavior openafs-1.2.11

2004-12-01 Thread Derrick J Brashear
On Wed, 1 Dec 2004, David Thompson wrote: The command I used on the clients was: tcpdump -vv -s 1500 port 7001 Hope that's right... Doesn't matter. the traffic will all be from port 7001 to port 7000, and back. Box 2 (failure): 14:57:52.434114

Re: [OpenAFS] 1.3.74 on AMD64

2004-12-01 Thread Jeffrey Hutzelman
On Friday, November 26, 2004 20:57:26 +0100 Andrej Filipcic [EMAIL PROTECTED] wrote: On Friday 26 November 2004 18:46, Derrick J Brashear wrote: On Fri, 26 Nov 2004, Todd Harris wrote: has anyone been able to get this working on dual AMD Opteron 64's. I've been able to compile the source

RE: [OpenAFS] unable to start afs client

2004-12-01 Thread EC
-Message d'origine- De : Horst Birthelmer [mailto:[EMAIL PROTECTED] Envoyé : mardi 30 novembre 2004 16:39 À : EC Cc : 'OpenAFS-info mailing list' Objet : Re: [OpenAFS] unable to start afs client On Nov 30, 2004, at 4:32 PM, EC wrote: Hi, unfortunately I have exactly the same problem on

[OpenAFS] memcache or diskcache on ramdisk

2004-12-01 Thread EC
Hi, Do using memory cache for AFSD 'better' (faster, more stable, etc..) than disk cache over RAMDISK or TMPFS ? EC. ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] memcache or diskcache on ramdisk

2004-12-01 Thread Derek Atkins
EC [EMAIL PROTECTED] writes: Hi, Do using memory cache for AFSD 'better' (faster, more stable, etc..) than disk cache over RAMDISK or TMPFS ? Well, you can't use TMPFS. So your choice is memcache or ramdisk + ext2/3. I think most people would say you're better off with the ramdisk + ext2/3

Re: [OpenAFS] memcache or diskcache on ramdisk

2004-12-01 Thread Kris Van Hees
On Thu, Dec 02, 2004 at 12:24:25AM +0100, EC wrote: Do using memory cache for AFSD 'better' (faster, more stable, etc..) than disk cache over RAMDISK or TMPFS ? I haven't particularly attempted to use a disk cache on ramdisk or tmpfs, but my guess would be that in those circumstances you are

[OpenAFS] client hangs through ipsec

2004-12-01 Thread Wes Chow
I have two fileservers (both Debian Sarge, OpenAFS 1.2.11), and several clients (also Sarge, however OpenAFS 1.2.13). The local clients work fine. Remote clients that are connected through IPsec (OpenSwan 2.2.0) hang. I've heard of ssh/scp of large files through OpenSwan sometimes hanging, but

Re: [OpenAFS] Panic under MacOS 10.3.6 with OpenAFS-1.2.13

2004-12-01 Thread Garance A Drosihn
At 9:08 PM -0500 11/18/04, Derrick J Brashear wrote: On Thu, 18 Nov 2004, Garance A Drosihn wrote: I am not certain which version of OpenAFS I had been running, but I believe it was 1.2.11. So, I figured I might as well upgrade my Mac to 1.2.13. Now, I seem to get panics when I save a file which