[OpenAFS-devel] 1.2.8 on HP-UX 11.00

[Derrick J Brashear]

So it gets in the archive, the answer to this is "don't use VxFS for
cache, use (I think it's) hfs. (The vendor's standard ufs filesystem)

This probably belongs in some documentation we don't have yet.,

On Thu, 17 Apr 2003, Liakakis Kostas wrote:


> report_trap_or_int_and_panic+0x4c
> trap+0xeb0
> $call_trap+0x38
> in_get+0x7c
> iget+0x14
> getinode+0x8c
> igetinode+0x54
> osi_UFSOpen+0x1f4
> afs_InitCacheInfo+0x248
> afs_syscall_call+0x1918
> Afs_syscall+0x84
> coerce_scall_args+0x9c
> syscall+0x6e8
> $syscallrtn+0x0
> q4>
>
> Q4 has many utilities... Analyze.pl AMPU gave me a huge output
> (~5.5MB) providing information of every process running. It included
> a more detailed kernel stack dump, register values, processes stack.
>
> WhatHappened.pl gave me what appears to be a summury of the above and
> which I am attaching here. Appended is all info that was available for the
> afsd process.
>
> Thanks again,
>
> -Kostas
>
>
> On Wed, 16 Apr 2003, Derrick J Brashear wrote:
> > On Wed, 16 Apr 2003, Liakakis Kostas wrote:
> > > Please tell me if you need anything in addition.
> >
> > Are you familiar with the HP kernel debugger? (I am not, so I can't give
> > you good instructions easily)
> >
> > What would be useful, if you can do it, would be a translation of the
> > stack trace provided to a backtrace.
>
>