<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Generating Core Dump in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008905#M605722</link>
    <description>First of all, you are running fstyp on a LVOL that does not contain a filesystem. I suppose that it is possible that a swap area (especially if that swap area once housed a filesystem) contains enough data to get fstyp in a confused state (ie, it could read part of  what was a superblock and then do more tests that would trigger a segmentation violation). I suppose the first thing to do would be to look for and install the latest fstyp cumulative patch. Since you didn't bother to identify your OS version, I have no idea what that patch might be.&lt;BR /&gt;&lt;BR /&gt;What in the Wide World of Sports is vg00 doing with 25 (or more) LVOL's? That is a recipe for an extremely poorly organized system.</description>
    <pubDate>Tue, 29 May 2007 10:45:50 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2007-05-29T10:45:50Z</dc:date>
    <item>
      <title>Generating Core Dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008903#M605720</link>
      <description>When I exected the command &lt;BR /&gt;#fstyp /dev/vg00/lvol25   &lt;BR /&gt;&lt;BR /&gt;It terminated with a coredump&lt;BR /&gt;&lt;BR /&gt;/dev/vg00/lvol25   is a addon swap &lt;BR /&gt;&lt;BR /&gt;fstab entry follows&lt;BR /&gt;/dev/vg00/lvol25 ....swap pri=1 0 0 &lt;BR /&gt;&lt;BR /&gt;In swapinfo -t command it saying that 16% of that particular swap getting used.&lt;BR /&gt;&lt;BR /&gt;Can anybody suggest what is wrong with the server ???&lt;BR /&gt;</description>
      <pubDate>Tue, 29 May 2007 07:27:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008903#M605720</guid>
      <dc:creator>vinayan</dc:creator>
      <dc:date>2007-05-29T07:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Generating Core Dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008904#M605721</link>
      <description>How many swap devices have you configured in the system? and can you post the output of the following here:&lt;BR /&gt;&lt;BR /&gt;# swapinfo -mat</description>
      <pubDate>Tue, 29 May 2007 08:53:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008904#M605721</guid>
      <dc:creator>Sandman!</dc:creator>
      <dc:date>2007-05-29T08:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: Generating Core Dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008905#M605722</link>
      <description>First of all, you are running fstyp on a LVOL that does not contain a filesystem. I suppose that it is possible that a swap area (especially if that swap area once housed a filesystem) contains enough data to get fstyp in a confused state (ie, it could read part of  what was a superblock and then do more tests that would trigger a segmentation violation). I suppose the first thing to do would be to look for and install the latest fstyp cumulative patch. Since you didn't bother to identify your OS version, I have no idea what that patch might be.&lt;BR /&gt;&lt;BR /&gt;What in the Wide World of Sports is vg00 doing with 25 (or more) LVOL's? That is a recipe for an extremely poorly organized system.</description>
      <pubDate>Tue, 29 May 2007 10:45:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008905#M605722</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-05-29T10:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Generating Core Dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008906#M605723</link>
      <description>Hi Vinayan,&lt;BR /&gt;              you need to install below patches on your system&lt;BR /&gt;patch hp-ux_patches/s700_800/11.X/PHCO_35524 7384864&lt;BR /&gt;patch hp-ux_patches/s700_800/11.X/PHKL_31500 103143254&lt;BR /&gt;patch hp-ux_patches/s700_800/11.X/PHKL_35889 3308237&lt;BR /&gt;patch hp-ux_patches/s700_800/11.X/PHKL_36244 1999576&lt;BR /&gt;patch superseded_patches/hp-ux_patches/s700_800/11.X/PHCO_33522 68030&lt;BR /&gt;patch superseded_patches/hp-ux_patches/s700_800/11.X/PHCO_34273 6389503&lt;BR /&gt;&lt;BR /&gt;Hopefully it will resolve error :)</description>
      <pubDate>Fri, 13 Jul 2007 07:48:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/generating-core-dump/m-p/4008906#M605723</guid>
      <dc:creator>$t!$-</dc:creator>
      <dc:date>2007-07-13T07:48:59Z</dc:date>
    </item>
  </channel>
</rss>

