[OpenAFS] 1.4.0 on Solaris 10 x86/amd64

[Kris Kasner]

I'm not sure if I'm missing something, but all I can find from the link you 
provided is the initial bug report..

The patch you're referring to is in 1.4.0, and it deals with user level 
commands "svcs -p" and "ctrun -v" causing a system panic because of an orphaned 
kernel thread.. The patch causes the kernel thread to be associated with 
"sched" instead of orphaned.. which causes some weirdness in svcs -p (sched 
shows up looking like it "belongs" to afs), but it doesn't crash!

That happens on 32bit, 64bit, amd64, SPARC, etc.. It's a function of how Solaris 
10 kernel deals with tracking processes and threads associated with the 
"contract" model.

That patch does Not resolve the "No such device" on any afs volume in Solaris 
10 x86/64 booted in 64bit mode, which is the bug this email was about, and the 
bug you posted was about..

I hope that helps clarify things.. If I'm missing where the resolution is shown 
on the URL you sent, please let me know.. I'd love to try it out if there is a 
different patch to address this.


--Kris

Today at 12:45, Derrick J Brashear <shadow@dementia.org> wrote:

> On Mon, 7 Nov 2005, Loic Tortay wrote:
>
>> I have the same problem.
>> 
>> I submitted a bug report for this about 3 weeks ago but the ticket was
>> silently closed (<http://rt.central.org/rt/index.html?q=22320>).
>
> You have a strange definition of silence. However, the referred-to issue is 
> then not the same one you were seeing? (namely the patch dealing with afsd 
> and waitpid from chas williams)
>
> Derrick
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

-- 

Thomas Kris Kasner                  Qualcomm Inc.
UNIX Infrastructure Architecture    5775 Morehouse Drive
UNIX Systems Administration 	    San Diego, CA 92121
 				    (858)658-4932


Don't burn the day...
 					-- Dave Matthews "Pig"