Re: panic(cpu 1 caller ...): vnode_put(...): iocount < 1
Re: panic(cpu 1 caller ...): vnode_put(...): iocount < 1
- Subject: Re: panic(cpu 1 caller ...): vnode_put(...): iocount < 1
- From: James Reynolds <email@hidden>
- Date: Fri, 7 Oct 2005 11:27:46 -0600
Thanks for the info! It is totally what I needed. Autopsy
conclusions are below.
You will probably want to switch to the frame number from the bt for
the vnode_put_locked frame, and do a:
frame 3 (or whatever the frame number is from the bt)
print *vp
as well; this will narrow down the issue for your bug report.
If the mount point isn't dead:
p vp->v_mount
p dead_vnodeop_p
and v_mount is not 0 or the same value as dead_vnodeop_p, then also do this:
p *vp->v_mount
If you are just interested in avoiding the problem, or want to avoid
it until there's a fixed release (it may already be fixed by the
next update), the showallstacks will report the process name of all
the processes, and you will see the panic in one of them;
It is mds, spotlight, which is what I thought.
the print *vp will give a v_name field, which will be the name of
the file (probably a symbolic link).
Nope. "Icon\r"
You can look at the vp pointed to by the v_parent, and print it's
v_name, and so on, to assemble the path to the vp.
Specifically:
.../Library/Preferences/Painter 7 Prefs/Brushes/Ver 6/Cloners/Icon\r
This is a home folder for a student. I normally delete these folders
at logout. But I've noticed on some machines that the rm -rf process
will fail trying to delete the Cloners folder. I had no idea why.
And kill -9 <pid of rm> failed. ls -l /path/to/Cloners failed as
well (and couldn't be killed either).
We have also been running DiskWarrior and it has been reporting
"Repaired: Custom Icon Flag" for that file and many many more on the
systems. I didn't think it was an issue, but wow, I guess it can
cause a kernel panic and hangs (I didn't know the icons were the
reason the rm -rf was failing, just something in that folder).
Anyway, I am still thinking this might be a Radmind problem. We
distributed these files with Radmind. Radmind may be messing them
up. I'll take this up with them.
I'll still file it with Apple though.
If it's dead because of a forced unmount, the value of v_mount
will be 0; it might also be that the vp->v_op has the same address
in it as the symbol dead_vnodeop_p; you could check both of those.
I really would recommend filing a bug, though, including all the
above information:
<http://bugreporter.apple.com>
PS: Say "hi" to North Physics for me... I started my college career
at the UofU majoring in high energy physics and applied math. 8-).
Yay! Go UTES!
--
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