From: Dan Harrington (dan.harrington@overture.com)
Date: Mon May 19 2003 - 10:48:59 EDT
I did not find any references to this panic string on the HPQ Tru64 site,
and in the end I transferred the data from a backup tape to its new
home. But I did receive a potentially useful response from Jason Orendorf
of HP:
"If you're not certain the links in /etc/fdmns/{domain} are correct,
you can check an old sys_check if you have one or check ASE's
configuration by running 'asemgr -dC | more'.
If the links are correct, there may be metadata corruption which can
often be fixed by running 'verify -f {domain}' or 'fixfdmn {domain}'.
Fixfdmn usually does a better job at cleaning up corruption so is
preferred but didn't ship with 4.0G (it will likely be in the next
patch kit). However you should be able to copy the binary from a
fully patched 4.0F system without problems - or you can contact the
CSC and request a 4.0G version of the binary."
Original questions follows...
Dan
At 05:41 AM 5/16/2003 -0700, Dan Harrington wrote:
>Hello world,
>
>I'm in the midst of disassembling a 2 node cluster (V4.0G, ASE 1.6), and
>having trouble with one of our user data disks...I was unable to relocate
>the service from one host to the other (to get access to the directly
>connected DLT library). I set the service off-line, and then attempted to
>mount the device locally on one member. I ran advscan to recognize the
>domain, but any attempt to work with it (showfsets, verify, mount) result in
>a kernel panic, with the message "No xtra extents and no shadow extents".
>
>I've not found any reference to this on the list archive...and am about to
>go searching on the HPQ Tru64 site. Any pointers or suggestions would be
>welcome!
>
>Dan
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:19 EDT