<?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: disk thrashing diagnosis - part 2 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434307#M4328</link>
    <description>&lt;BR /&gt;Your using one of the slowest disk subsystems known to man - an Autoraid!! Do you know that internally the Autoraid is single-ended - ie. 5 MB/s ! If youre using a serious application then ditch the autoraid. Even using HASS/Jamacias would be tons faster and probably cheaper. And to boot the Autoraid is using so called 'intelligence' to move data around from Raid 0/1 to Raid 5 behind the scenes - as if you had any bandwith to spare! Theres plenty of previous post on how to get the best out of an autoraid but IMHO its like trying to get the best out of a Skoda. Replace it.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 02 Aug 2000 15:52:52 GMT</pubDate>
    <dc:creator>Stefan Farrelly</dc:creator>
    <dc:date>2000-08-02T15:52:52Z</dc:date>
    <item>
      <title>disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434306#M4327</link>
      <description>(see my first post for background)&lt;BR /&gt;&lt;BR /&gt;All of the data are on an HP Raid. I know nothing about this RAID except that it's rack mounted with the 570, and there are no docs of any kind, and a physical inspection is not practical (distance).&lt;BR /&gt;&lt;BR /&gt;How do HP's RAID's work? Is the cache (host) controller based, or in the RAID cabinet? How can I find out about this environment (e.g. product name/#, parameters, esp. cache). This is setup RAID 5 with hot spares (I'm told), and I'm concerned about the amont of cache ... this seems like my only avenue to mitigate (not resolve) disk problems. (again, see first post - during mid and peak processing, I get 100% disk utilization overall, as reported by Glance. I'm breaking this down with sar now.)&lt;BR /&gt;&lt;BR /&gt;Other ideas/suggestions?</description>
      <pubDate>Wed, 02 Aug 2000 15:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434306#M4327</guid>
      <dc:creator>Phil Corchary</dc:creator>
      <dc:date>2000-08-02T15:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434307#M4328</link>
      <description>&lt;BR /&gt;Your using one of the slowest disk subsystems known to man - an Autoraid!! Do you know that internally the Autoraid is single-ended - ie. 5 MB/s ! If youre using a serious application then ditch the autoraid. Even using HASS/Jamacias would be tons faster and probably cheaper. And to boot the Autoraid is using so called 'intelligence' to move data around from Raid 0/1 to Raid 5 behind the scenes - as if you had any bandwith to spare! Theres plenty of previous post on how to get the best out of an autoraid but IMHO its like trying to get the best out of a Skoda. Replace it.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 02 Aug 2000 15:52:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434307#M4328</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2000-08-02T15:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434308#M4329</link>
      <description>I am completely ignorant of AutoRAID ... is this hardware or software ... any details or pointers?&lt;BR /&gt;&lt;BR /&gt;There is NO money that can be spent in the next 12 months.&lt;BR /&gt;&lt;BR /&gt;What can I do with that constraint?</description>
      <pubDate>Wed, 02 Aug 2000 15:59:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434308#M4329</guid>
      <dc:creator>Phil Corchary</dc:creator>
      <dc:date>2000-08-02T15:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434309#M4330</link>
      <description>Full AutoRAID documentation can be found at the following URL:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hp.com/essd/model12H_alldocs.html" target="_blank"&gt;http://www.hp.com/essd/model12H_alldocs.html&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Brian &lt;BR /&gt;&amp;lt;*(((&amp;gt;&amp;lt; er</description>
      <pubDate>Wed, 02 Aug 2000 16:17:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434309#M4330</guid>
      <dc:creator>Brian M. Fisher</dc:creator>
      <dc:date>2000-08-02T16:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434310#M4331</link>
      <description>If you have NO money, then little can be done with the disk or it's cache.  I'm assuming that it is fully utilized.  The best short term thing to do would be to somehow  move as much batch activity off to non peak periods.  Batch stuff is a big time disk killer.  If this is not an alternative, my only suggestion would be to dust off your resume. &lt;G&gt;  If your organization is that stapped on that they can't afford minimal disk improvements, I'm quite sure that your next pay raise will be generous.  If it's some sort of government agency, let the politicians take the heat; it's as much their problem for not having the resources.&lt;/G&gt;</description>
      <pubDate>Wed, 02 Aug 2000 16:33:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434310#M4331</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2000-08-02T16:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: disk thrashing diagnosis - part 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434311#M4332</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;to obtain information about the AutoRAID use the arraydsp command:&lt;BR /&gt;arraydsp -R&lt;BR /&gt;scans for AutoRAID devices&lt;BR /&gt;you get the ID&lt;BR /&gt;Then do&lt;BR /&gt;arraydsp -a &lt;ID&gt;&lt;BR /&gt;this will give you much information for your AutoRAID&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Andrew&lt;/ID&gt;</description>
      <pubDate>Wed, 02 Aug 2000 19:09:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-thrashing-diagnosis-part-2/m-p/2434311#M4332</guid>
      <dc:creator>Andreas Voss</dc:creator>
      <dc:date>2000-08-02T19:09:17Z</dc:date>
    </item>
  </channel>
</rss>

