[OpenAFS] Re: OpenAFS 1.4.1 RC1 Cache on OS X 10.4.2
Derrick Brashear asked: > And also... SMP only or uniprocessor also? Only on my dual-processor machine. I'm the heaviest user of AFS by far in my department, for various reasons. The various problems I see invariably result in a kernel panic on shutdown, which I've described in bug 21046. Cheers, Sam ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] Re: OpenAFS 1.4.1 RC1 Cache on OS X 10.4.2
[EMAIL PROTECTED] wrote: Date: Mon, 24 Oct 2005 11:06:10 -0700 From: Mike Bydalek <[EMAIL PROTECTED]> To: Derrick J Brashear <[EMAIL PROTECTED]> Cc: OpenAFS-info@openafs.org Subject: Re: [OpenAFS] OpenAFS 1.4.1 RC1 Cache on OS X 10.4.2 Derrick J Brashear wrote: I doubt it's an AFS cache problem as opposed to an issue where permission denied is being misinterpreted and the result cache in either internal AFS or MacOS kernel filesystem code I should note that on MacOS 10.3.9, I've had this problem, reliably, after extended use (e.g., several days of reads/writes). For me, it's tended to cooccur with random crap at the beginning of files (e.g., the name of the AFS volume overwriting the corresponding initial characters of the file). I've confirmed that these problems only appear in the AFS volume as viewed on the Mac, not as viewed from other platforms. Cheers, Sam Bayer [EMAIL PROTECTED] ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Reproducible kernel panic on MacOS x 10.3.9 with 1.3.81
From: Derrick J Brashear <[EMAIL PROTECTED]> To: openafs-info@openafs.org Subject: Re: [OpenAFS] Reproducible kernel panic on MacOS x 10.3.9 with 1.3.81 On Tue, 23 Aug 2005, Samuel L. Bayer wrote: The kernel panic is clearly in the afs extension, according to the PC counter in the panic log and the kextstat command. The kernel panic I get is panic(cpu 0): unmount: dangling vnode This one's known but I'd been unable to figure out what was going on. I assume this happens when you're otherwise rebooting? Rebooting or shutting down. Before 1.3.81, I would occasionally get kernel panics at runtime, but no longer; on the other hand, I don't leave my machine up long enough to necessarily reach that point. I reboot because AFS starts behaving strangely; I'll get contents of files that are incorrect, etc. I've used afs flushvolume at least once to fix that, but I don't know whether it's a consistent fix. In some cases, I've know that AFS had confused my machine because I'd get a bus error running gcc; I wish I recalled whether it happened only when compiling from source files in AFS space, or whether it was any invocation of gcc. That part isn't particularly reproducible, and I haven't until recently gotten fed up enough to commit myself to really tracking this problem down. Sam Bayer ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] Reproducible kernel panic on MacOS x 10.3.9 with 1.3.81
Hi all - I've submitted this to the bug tracker (#21046), but I thought I'd run it past you all to see if anyone has any ideas. We have OpenAFS installed on a number of machines, all of them dual processor G5s. My machine seem to be the heaviest user of our AFS space among those machines, and it reliable generates a kernel panic on shutdown. This would merely be an annoyance, except the AFS performance tends to get flakier and flakier the longer the machine is up: strange file contents, etc. My standard solution is to boot the machine, but if I happen not to be on site, and I get a kernel panic on shutdown, somebody has to intervene physically in order for the machine to reboot properly, to the best of my knowledge. The kernel panic is clearly in the afs extension, according to the PC counter in the panic log and the kextstat command. The kernel panic I get is panic(cpu 0): unmount: dangling vnode Latest stack backtrace for cpu 0: Backtrace: 0x00083498 0x0008397C 0x0001EDA4 0x000C60B4 0x000C39DC 0x00218030 0x00220BA4 0x00246D84 0x000941C0 0x01D099E0 Proceeding back via exception chain: Exception state (sv=0x2D566280) PC=0x9005F5CC; MSR=0xD030; DAR=0x0030E300; DSISR=0x4000; LR=0x27A4; R1=0xBEB0; XCP=0x0030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Sometimes it's the other CPU, but it's always the same first several items of the backtrace, PC, etc. If I haven't done anything in AFS space, I don't get the kernel panic; but it doesn't seem like I have to do much to trigger it. None of the other machines seem to be having this problem, but I can't exactly tell whether it's because of their relatively light AFS use or because of possibly conflicting kernel extensions. Any ideas? I've looked at ticket 18358, and it looks like it might be related, but I can't really tell. Thanks for any advice you can provide. Cheers, Sam Bayer [EMAIL PROTECTED] ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] Re: home directories in AFS
Hi all - I thought I'd share a little experience with using OpenAFS for my home directory on MacOS X 10.2.6. I'm also subscribing to our Solaris NIS server for password authentication. In general, the configuration is *reasonably* reliable. However, it's not quite ready for prime time, for the following reasons: (1) There doesn't really appear to be support for PAM authentication in MacOS X yet, and that means that there's a point where I'm logged in, but have no write permissions. This can be a problem if any login items try to write to any files. It's also annoying having to open the Terminal to klog every time I log in. (2) I occasionally have a problem where my System Preferences Screen Effects pane will hang, and at the same time, Logout or Restar from the Apple menu will simply fail to do anything. I can't find any indication of a problem in the system logs, and if I force a logout by killing the loginwindow process and log in as admin, there's no problem. I'm convinced that this has something to do with the AFS/NIS configuration, but the only evidence I have is that the AFS-mounted user has the problem (intermittently) and the non-AFS-mounted user never does. Other than these problems, I'm extremely happy with the configuration. Sam Bayer ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
