osdir.com
mailing list archive

Subject: SUMMARY:CORE ANALYSIS - msg#00138

List: os.solaris.managers.summaries

Date: Prev Next Index Thread: Prev Next Index
The summary from the question below is: - Sun has a course on this,
docs.sun.com has a book on the modular debugger
- SolarisCAT
http://wwws.sun.com/software/download/products/3e3af5aa.html
- book PANIC! Unix System Crash Dump Analysis ISBN 0-13-149386-8 - run this for
starters: #strings vmcore.# |head against the core
files.

Thanks to: Harold Reinstein, Alan Pae, Sun Systems Admin (Bill), John England,,
Michael Peters and Jason Shatzkamer. Regards. Hi Gurus, I know this is a pretty
broad question, but I would like to know if there is any document to analyse
cores in Sun Machines. I can run adb commands or get the iscda output, but to
be honest the output is not of big help to me, especially in "Bad traps" type
of cores.I've been surfing Internet and Sun web but nothing good Ive found. Of
course I am sure that with a document it won't analyse all the cases but I
would like to have unless the most typical hints to get focused with an iscda
output or russing adb commands. Ive also checked the book "Panic!..." but it's
not too practical to me... Any help is welcome! Thanks in advance and regards.


---------------------------------
Yahoo! Messenger
Nueva versión: Super Webcam, voz, caritas animadas, y más
#161;Gratis!


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

NON-SUMMARY: Mismatch between physical geometry and disk label contents

Hi Gurus, Unfortunately, I did not get any solution. I had suggestions to just "Label" the disk, but my problem is not fixing a disk with an incorrect label, but rather finding such disks (LUNs) across many systems because these disks are currently "in use" and as a result, some portions of the disk is not available. Richard Hobbs mentioned having seen the same thing in the past when moving disks from one system to another. Using "format" to label a disk with an existing label does not re-read the disk geometry from the physical disk, it reads it from the existing label. The only way to really re-label a disk is by first corrupting the label, eg using the following procedure: First, corrupt the first sector on the disk c#t#d# dd if=/path/to/any/file of=/dev/rdsk/c#t#d#s2 count=1 bs=512 Next, use format to write a new label to the disk format select disk label? YES quit Then finally, encapsulate the disk, or partition and start using it as per normal. My Original question: > > Hi gurus, > > > > I was happily scripting a couple of weeks ago and came across something > > that produced a message similar to this (off the top of my head) > > > > Warning: The label contents does not match the geometry reported by the > > physical device. > > > > Now I can not remember the command I ran, but I want to use it in another > > script. I was busy writing a script to report on raw disk sizes as seen > by > > Solaris (not Veritas), and I was playing with commands like > > > > format, prtvtoc, fmthard > > > > I've been searching the web and sunsolve, but I can't find out what it is > I > > did. Makes me want to "script" to record everything I do... ! > > > > The situation I have is that sometimes when the storage administrators > > allocate a whole bunch of LUNs I do not check each individually, and > > sometimes I don't realise I am not seeing the full LUN (eg if the first > > sector of an expanded LUN was previously the first sector of a smaller > > LUN). I am trying to write a script which will tell me where I may be > > using LUNs without getting access to the whole full size of the LUN. > > > > > > > > moreover, I have tried to write something to compare the output of fdisk > -g > > with that of fdisk -G, but I always get the following message: > > > > # fdisk -g /dev/rdsk/c3t11d4s2 > > * Label geometry for device /dev/rdsk/c3t11d4s2 > > * PCYL NCYL ACYL BCYL NHEAD NSECT SECSIZ > > 39516 39516 2 0 15 96 512 > > # fdisk -G /dev/rdsk/c3t11d4s2 > > /dev/rdsk/c3t11d4s2: Cannot get physical disk geometry. > > > > > > > > devinfo appears totally useless, and on Solaris 2.6 I get for -g and -G > > both: > > > > Disk does not support fixed disk partition table > > > > > > Any ideas/suggestions ? > > > > Thanx, > > _Johan |---------+---------------------------> | | "Hobbs, Richard"| | | <hobbs | | | @mongeese.co.uk>| | | | | | 17/04/2003 04:14| | | PM | | | | |---------+---------------------------> >-----------------------------------------------------------------------------------------------------------------| | | | To: Johan Hartzenberg/GIS/CSC@CSC | | cc: | | Subject: Re: Mismatch between physical geometry and disk label contents | >-----------------------------------------------------------------------------------------------------------------| Hello, How do you know the disk label is valid though?? What told you that it was valid? To produce the error, i took the 2GB disk out of my Ultra 1, and then took two 9GB disks out of an old veritas-managed disk array. I then put the two 9GB disks into my Ultra 1, and tried to install Solaris 9 onto them. These two disks were going to stay in my Ultra 1 permanently from now on. At some point in the install (fairly early on), i got the error you had... about the wrong physical geometry. I checked several things: - Whether that type of disk would actually work in my machine at all. - Whether the disk type was compatible with the bus i had plugged them onto. - Whether the disks were actually dead (by putting them in a working array). - Whether there were any master/slave jumpers on the disks. - Whether a "probe-scsi-all" command at the ok prompt could pick up the disks. - Whether a boot into single user-mode, followed by a 'format' would help. - ...and finally, i tried labelling them, and that worked! I don't know too much about it technically, i'm afraid, but there's my story. Hope it helps!! Try posting on my forum!! http://unixforum.co.uk Thanks, Richard. Quoting Johan Hartzenberg <jhartzen@xxxxxxx>: > > > Hi, > > Thanx for your reply. The veritas stuff is not the problem, the problem is > that the disk label was valid, but the geometry was "wrong". > > What did you have to do to actually get the system to produce this message? > > So far I only got your reply, plus one from someone who didn't properly > read my question! > > Thanx, > _Johan > > > > > > |---------+---------------------------> > | | "Hobbs, Richard"| > | | <hobbs | > | | @mongeese.co.uk>| > | | | > | | 17/04/2003 03:45| > | | PM | > | | | > |---------+---------------------------> > > > -----------------------------------------------------------------------------------------------------------------| > | > | > | To: Johan Hartzenberg <jhartzen@xxxxxxx> > | > | cc: > | > | Subject: Re: Mismatch between physical geometry and disk label > contents | > > > -----------------------------------------------------------------------------------------------------------------| > > > > > Hello, > > I had that problem when i put two disks from a veritas-managed array into > an > Ultra 1. It said the disk was reporting geometry that didn't match the > physical > disk. > > I simply had to label it i think. Veritas doesn't label disks the same way > Solaris does, so this could be the problem. > > I'd be very interested to see the summary when yo figure it out though! > > Thanks, > Richard. > > > > _______________________________________________ > > sunmanagers mailing list > > sunmanagers@xxxxxxxxxxxxxxx > > http://www.sunmanagers.org/mailman/listinfo/sunmanagers > > > > > -- > Richard Hobbs > hobbs@xxxxxxxxxxxxxx > http://mongeese.co.uk | http://unixforum.co.uk > > "There's only one way of life, and that's your own" - The Levellers > > _____________________________________________________ > Send all your jokes to jokes@xxxxxxxxxxxxxxxx !! > To subscribe, email: jokes-subscribe@xxxxxxxxxxxxxxxx > > > > > -- Richard Hobbs hobbs@xxxxxxxxxxxxxx http://mongeese.co.uk | http://unixforum.co.uk "There's only one way of life, and that's your own" - The Levellers _____________________________________________________ Send all your jokes to jokes@xxxxxxxxxxxxxxxx !! To subscribe, email: jokes-subscribe@xxxxxxxxxxxxxxxx

Next Message by Date: click to view message preview

SUMMARY: limiting the size of emails

Thanks for all the replies, Consensus is that I should uncomment the O MaxMessageSize=nnnn line in sendmail.cf, setting nnnn to the size in bytes that we require the limit to be, and restart sendmail. Also, in response to: will MaxMessageSize work for outgoing emails? Yes, basically as far as sendmail is concerned it treats all emails as incoming when it receives them, whether from the local host for a remote host, or from a remote host for the local host or for relaying, and therefore runs its rules. The SIZE keyword was a bit more difficult, most said that if it wasnt specified or was 0 it would be infinity, so we're going to wait & see what happens. Thanks again, Jo -----Original Message----- From: Jo Ashmore [mailto:Jo.Ashmore@xxxxxxxxxxxxxxxxxxx] Sent: 22 April 2003 16:28 To: 'sunmanagers@xxxxxxxxxxxxxxx' Subject: limiting the size of emails Hi all, I have been asked to limit the size of both incoming and outgoing emails - we are currently running a very basic vanilla sendmail on Solaris 8. Any ideas please? Jo Ashmore Unix Systems & Support Manager Securicor Information Systems Direct Dial 01249 665191 Mobile 07974 732668 ********************************************************************** The information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of Securicor Information Systems Limited. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please immediately notify the sender by using the e-mail reply facility. ********************************************************************** _____________________________________________________________________ This message has been checked for all known viruses on behalf of Securicor Information Systems by the MessageLabs. For further information visit http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxxxxxxxx _______________________________________________ sunmanagers mailing list sunmanagers@xxxxxxxxxxxxxxx http://www.sunmanagers.org/mailman/listinfo/sunmanagers ********************************************************************** The information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of Securicor Information Systems Limited. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please immediately notify the sender by using the e-mail reply facility. ********************************************************************** _____________________________________________________________________ This message has been checked for all known viruses on behalf of Securicor Information Systems by the MessageLabs. For further information visit http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxxxxxxxx

Previous Message by Thread: click to view message preview

NON-SUMMARY: Mismatch between physical geometry and disk label contents

Hi Gurus, Unfortunately, I did not get any solution. I had suggestions to just "Label" the disk, but my problem is not fixing a disk with an incorrect label, but rather finding such disks (LUNs) across many systems because these disks are currently "in use" and as a result, some portions of the disk is not available. Richard Hobbs mentioned having seen the same thing in the past when moving disks from one system to another. Using "format" to label a disk with an existing label does not re-read the disk geometry from the physical disk, it reads it from the existing label. The only way to really re-label a disk is by first corrupting the label, eg using the following procedure: First, corrupt the first sector on the disk c#t#d# dd if=/path/to/any/file of=/dev/rdsk/c#t#d#s2 count=1 bs=512 Next, use format to write a new label to the disk format select disk label? YES quit Then finally, encapsulate the disk, or partition and start using it as per normal. My Original question: > > Hi gurus, > > > > I was happily scripting a couple of weeks ago and came across something > > that produced a message similar to this (off the top of my head) > > > > Warning: The label contents does not match the geometry reported by the > > physical device. > > > > Now I can not remember the command I ran, but I want to use it in another > > script. I was busy writing a script to report on raw disk sizes as seen > by > > Solaris (not Veritas), and I was playing with commands like > > > > format, prtvtoc, fmthard > > > > I've been searching the web and sunsolve, but I can't find out what it is > I > > did. Makes me want to "script" to record everything I do... ! > > > > The situation I have is that sometimes when the storage administrators > > allocate a whole bunch of LUNs I do not check each individually, and > > sometimes I don't realise I am not seeing the full LUN (eg if the first > > sector of an expanded LUN was previously the first sector of a smaller > > LUN). I am trying to write a script which will tell me where I may be > > using LUNs without getting access to the whole full size of the LUN. > > > > > > > > moreover, I have tried to write something to compare the output of fdisk > -g > > with that of fdisk -G, but I always get the following message: > > > > # fdisk -g /dev/rdsk/c3t11d4s2 > > * Label geometry for device /dev/rdsk/c3t11d4s2 > > * PCYL NCYL ACYL BCYL NHEAD NSECT SECSIZ > > 39516 39516 2 0 15 96 512 > > # fdisk -G /dev/rdsk/c3t11d4s2 > > /dev/rdsk/c3t11d4s2: Cannot get physical disk geometry. > > > > > > > > devinfo appears totally useless, and on Solaris 2.6 I get for -g and -G > > both: > > > > Disk does not support fixed disk partition table > > > > > > Any ideas/suggestions ? > > > > Thanx, > > _Johan |---------+---------------------------> | | "Hobbs, Richard"| | | <hobbs | | | @mongeese.co.uk>| | | | | | 17/04/2003 04:14| | | PM | | | | |---------+---------------------------> >-----------------------------------------------------------------------------------------------------------------| | | | To: Johan Hartzenberg/GIS/CSC@CSC | | cc: | | Subject: Re: Mismatch between physical geometry and disk label contents | >-----------------------------------------------------------------------------------------------------------------| Hello, How do you know the disk label is valid though?? What told you that it was valid? To produce the error, i took the 2GB disk out of my Ultra 1, and then took two 9GB disks out of an old veritas-managed disk array. I then put the two 9GB disks into my Ultra 1, and tried to install Solaris 9 onto them. These two disks were going to stay in my Ultra 1 permanently from now on. At some point in the install (fairly early on), i got the error you had... about the wrong physical geometry. I checked several things: - Whether that type of disk would actually work in my machine at all. - Whether the disk type was compatible with the bus i had plugged them onto. - Whether the disks were actually dead (by putting them in a working array). - Whether there were any master/slave jumpers on the disks. - Whether a "probe-scsi-all" command at the ok prompt could pick up the disks. - Whether a boot into single user-mode, followed by a 'format' would help. - ...and finally, i tried labelling them, and that worked! I don't know too much about it technically, i'm afraid, but there's my story. Hope it helps!! Try posting on my forum!! http://unixforum.co.uk Thanks, Richard. Quoting Johan Hartzenberg <jhartzen@xxxxxxx>: > > > Hi, > > Thanx for your reply. The veritas stuff is not the problem, the problem is > that the disk label was valid, but the geometry was "wrong". > > What did you have to do to actually get the system to produce this message? > > So far I only got your reply, plus one from someone who didn't properly > read my question! > > Thanx, > _Johan > > > > > > |---------+---------------------------> > | | "Hobbs, Richard"| > | | <hobbs | > | | @mongeese.co.uk>| > | | | > | | 17/04/2003 03:45| > | | PM | > | | | > |---------+---------------------------> > > > -----------------------------------------------------------------------------------------------------------------| > | > | > | To: Johan Hartzenberg <jhartzen@xxxxxxx> > | > | cc: > | > | Subject: Re: Mismatch between physical geometry and disk label > contents | > > > -----------------------------------------------------------------------------------------------------------------| > > > > > Hello, > > I had that problem when i put two disks from a veritas-managed array into > an > Ultra 1. It said the disk was reporting geometry that didn't match the > physical > disk. > > I simply had to label it i think. Veritas doesn't label disks the same way > Solaris does, so this could be the problem. > > I'd be very interested to see the summary when yo figure it out though! > > Thanks, > Richard. > > > > _______________________________________________ > > sunmanagers mailing list > > sunmanagers@xxxxxxxxxxxxxxx > > http://www.sunmanagers.org/mailman/listinfo/sunmanagers > > > > > -- > Richard Hobbs > hobbs@xxxxxxxxxxxxxx > http://mongeese.co.uk | http://unixforum.co.uk > > "There's only one way of life, and that's your own" - The Levellers > > _____________________________________________________ > Send all your jokes to jokes@xxxxxxxxxxxxxxxx !! > To subscribe, email: jokes-subscribe@xxxxxxxxxxxxxxxx > > > > > -- Richard Hobbs hobbs@xxxxxxxxxxxxxx http://mongeese.co.uk | http://unixforum.co.uk "There's only one way of life, and that's your own" - The Levellers _____________________________________________________ Send all your jokes to jokes@xxxxxxxxxxxxxxxx !! To subscribe, email: jokes-subscribe@xxxxxxxxxxxxxxxx

Next Message by Thread: click to view message preview

SUMMARY: limiting the size of emails

Thanks for all the replies, Consensus is that I should uncomment the O MaxMessageSize=nnnn line in sendmail.cf, setting nnnn to the size in bytes that we require the limit to be, and restart sendmail. Also, in response to: will MaxMessageSize work for outgoing emails? Yes, basically as far as sendmail is concerned it treats all emails as incoming when it receives them, whether from the local host for a remote host, or from a remote host for the local host or for relaying, and therefore runs its rules. The SIZE keyword was a bit more difficult, most said that if it wasnt specified or was 0 it would be infinity, so we're going to wait & see what happens. Thanks again, Jo -----Original Message----- From: Jo Ashmore [mailto:Jo.Ashmore@xxxxxxxxxxxxxxxxxxx] Sent: 22 April 2003 16:28 To: 'sunmanagers@xxxxxxxxxxxxxxx' Subject: limiting the size of emails Hi all, I have been asked to limit the size of both incoming and outgoing emails - we are currently running a very basic vanilla sendmail on Solaris 8. Any ideas please? Jo Ashmore Unix Systems & Support Manager Securicor Information Systems Direct Dial 01249 665191 Mobile 07974 732668 ********************************************************************** The information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of Securicor Information Systems Limited. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please immediately notify the sender by using the e-mail reply facility. ********************************************************************** _____________________________________________________________________ This message has been checked for all known viruses on behalf of Securicor Information Systems by the MessageLabs. For further information visit http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxxxxxxxx _______________________________________________ sunmanagers mailing list sunmanagers@xxxxxxxxxxxxxxx http://www.sunmanagers.org/mailman/listinfo/sunmanagers ********************************************************************** The information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of Securicor Information Systems Limited. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please immediately notify the sender by using the e-mail reply facility. ********************************************************************** _____________________________________________________________________ This message has been checked for all known viruses on behalf of Securicor Information Systems by the MessageLabs. For further information visit http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxxxxxxxx
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by