panic(cpu 1 caller ...): vnode_put(...): iocount < 1
panic(cpu 1 caller ...): vnode_put(...): iocount < 1
- Subject: panic(cpu 1 caller ...): vnode_put(...): iocount < 1
- From: James Reynolds <email@hidden>
- Date: Mon, 3 Oct 2005 16:50:28 -0600
I manage a lab of about 300 Macs. Since I've upgraded them to Tiger,
I've had various problems I've been chasing without success. The
latest version of the problem is that about 120 of my Macs (nearly
all of my dual 2.0 G5's) kernel panic daily with: panic(cpu 1 caller
...): vnode_put(...): iocount < 1
The only place I have seen anything on vnode_put is this list... thus
I post my question here.
I think this is related to my previous problems because my old
problems were also file system problems, which consisted of fsck
failing at startup (resulting in /etc/rc calling halt--which I had to
change to reboot to keep my machines up--and they worked relatively
fine after a reboot, until the kernel panics started).
I'm trying to do the closest I can come to a clean install of my OS,
but I have hundreds of other apps that are layered on top of the OS
and I can't rebuild them all quickly, especially since I'm not even
sure that will fix it, and since the new school term is roaring at
full speed. And I'm not sure the clean install will actually fix the
error. So I would like to figure out what exactly is going on while
I prep my new OS.
Also, these errors don't occur on my non-dual 2.0 G5's (G5 iMacs & G4
iMacs and towers). And the file systems of all machines are pretty
much clones, and are maintained with radmind (www.radmind.org).
In fact, I'm wondering if radmind could be causing these problems.
But because of the hardware uniqueness, I'm also wondering if Tiger
is just more picky than Panther was to my dual G5 hardware. But
because this all seems to have something to do with file system
problems... I'm not sure what direction I should be looking.
Anyway, I'm assuming the kernel panic below means something like a
vnode is missing its file.
My question is, is there any way I can figure out what file this is
dying on (or is there any other way to figure out what is going on):
panic(cpu 1 caller 0x000E6D70): vnode_put(191e084): iocount < 1
Latest stack backtrace for cpu 1:
Backtrace:
0x00095544 0x00095A5C 0x0002683C 0x000E6D70 0x000E6D1C
0x000ED6D0 0x000EDA50 0x000EDAF0
0x002A7A94 0x000ABCB0 0x797A6F46
Proceeding back via exception chain:
Exception state (sv=0x2A74BC80)
PC=0x9002218C; MSR=0x0000D030; DAR=0x12D89000;
DSISR=0x42000000; LR=0x9003FDD0; R1=0xF02023B0; XCP=0x00000030 (0xC00
- System call)
Kernel version:
Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005;
root:xnu-792.2.4.obj~3/RELEASE_PPC
--
Thanks,
James Reynolds
University of Utah
Student Computing Labs
email@hidden
801-585-9811
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden