<?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: VXVM : Read error on large VxFS filesystem in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186681#M9701</link>
    <description>Sounds like someone pulled a disk on the disk array.&lt;BR /&gt;&lt;BR /&gt;That absolutely should not cause any issues like you are receiving.&lt;BR /&gt;&lt;BR /&gt;I would fear a major problem. I would call HP support for a critical issue and be ready to shut that database down and back it up.&lt;BR /&gt;&lt;BR /&gt;For OLTP Oracle does not reccomend your setup, they actually recommend Raid 1 or Raid 10. I assume you did not do that due to space concerns or the database doesn't run at a high load factor.&lt;BR /&gt;&lt;BR /&gt;If this is production, get some kind of a backup fast.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 09 Feb 2004 15:13:58 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2004-02-09T15:13:58Z</dc:date>
    <item>
      <title>VXVM : Read error on large VxFS filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186679#M9699</link>
      <description>The following vxvm filesystem (lvol1, striped to 9 luns, on 9 different Fiber chan cards on Xp512 array) is setup for oracle dumps like this -&amp;gt;&lt;BR /&gt;&lt;BR /&gt;dg rootdg       4            default  0        985293812.1025&lt;BR /&gt;                                                                       &lt;BR /&gt;dm disk01       c45t1d3      simple   1024     14225328 NOHOTUSE       &lt;BR /&gt;dm disk02       c31t9d4      simple   1024     14225328 NOHOTUSE       &lt;BR /&gt;dm disk03       c47t1d5      simple   1024     14225328 NOHOTUSE       &lt;BR /&gt;dm disk04       c47t9d5      simple   1024     14225328 NOHOTUSE       &lt;BR /&gt;dm disk05       c43t9d3      simple   1024     14225328 NOHOTUSE       &lt;BR /&gt;dm disk10       c41t9d2      simple   1024     14225328 -              &lt;BR /&gt;dm disk11       c37t9d1      simple   1024     14225328 -              &lt;BR /&gt;dm disk12       c39t1d2      simple   1024     14225328 -              &lt;BR /&gt;dm disk13       c35t1d1      simple   1024     14225328 -           &lt;BR /&gt;&lt;BR /&gt;Some of the disks in rootdg are not "nohotuse" and some are..Does it make any difference in the "vxvm" functioning ? ( The rootdg has no root file systems)&lt;BR /&gt;&lt;BR /&gt;Oracle suggests that the problem may be a "logical read issue" between the&lt;BR /&gt;disks and the server.  &lt;BR /&gt;&lt;BR /&gt;The file system is mounted at /XYZ with -&amp;gt;&lt;BR /&gt;&lt;BR /&gt;/dev/vx/dsk/rootdg/lvol1 /XYZ vxfs delaylog,nodatainlog,mincache=direct,convos&lt;BR /&gt;ync=direct 0 2                                                &lt;BR /&gt;                   &lt;BR /&gt;-TIA &lt;BR /&gt;&lt;BR /&gt;Q&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Feb 2004 14:38:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186679#M9699</guid>
      <dc:creator>Q4you</dc:creator>
      <dc:date>2004-02-09T14:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: VXVM : Read error on large VxFS filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186680#M9700</link>
      <description>Well "read error" is extremely vague.  Can you be specific?&lt;BR /&gt;&lt;BR /&gt;And "NOHOTUSE" shouldn't matter.  That flag defines whether or not the disk is used in hot relocation.&lt;BR /&gt;&lt;BR /&gt;First, middle, last:&lt;BR /&gt;&lt;BR /&gt;Call Veritas' tech support.  They will walk you through this.  You do have phone support with Veritas, right?  Don't mess around with this.  Especially if this is a production machine.&lt;BR /&gt;&lt;BR /&gt;If you don't have paid tech support with Veritas and can't call them (and your menagement doesn't approve T&amp;amp;M) then please describe your problem in more detail.  Folks on this list ought to be able to get you close to a solution.&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Feb 2004 14:55:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186680#M9700</guid>
      <dc:creator>Mark Travis</dc:creator>
      <dc:date>2004-02-09T14:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: VXVM : Read error on large VxFS filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186681#M9701</link>
      <description>Sounds like someone pulled a disk on the disk array.&lt;BR /&gt;&lt;BR /&gt;That absolutely should not cause any issues like you are receiving.&lt;BR /&gt;&lt;BR /&gt;I would fear a major problem. I would call HP support for a critical issue and be ready to shut that database down and back it up.&lt;BR /&gt;&lt;BR /&gt;For OLTP Oracle does not reccomend your setup, they actually recommend Raid 1 or Raid 10. I assume you did not do that due to space concerns or the database doesn't run at a high load factor.&lt;BR /&gt;&lt;BR /&gt;If this is production, get some kind of a backup fast.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 09 Feb 2004 15:13:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-read-error-on-large-vxfs-filesystem/m-p/3186681#M9701</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-09T15:13:58Z</dc:date>
    </item>
  </channel>
</rss>

