<?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: Subject: Performance Issue under RedHat in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693985#M62287</link>
    <description>&lt;P&gt;&amp;gt;I have used only /dev/null as the output file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oops, sorry, I assumed the input (if=) was first.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Jun 2012 06:55:17 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2012-06-19T06:55:17Z</dc:date>
    <item>
      <title>Subject: Performance Issue under RedHat</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693507#M62283</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have our storage LUN's coming from an EVA4400 and presented over fiber to DL380's running RHEL 5.6. The LUN is about 450GB of student files, and formatted to GFS. We were noticing that the HP Data Protector was taking a really long time to do the initial scan and the backup. It took about 12 hours to do the full backup, when it use to take about 4 hours under HP-UX. Therefore, we compared the difference between EXT3 and GFS on the RedHat machines, and it was significant.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore, we setup a 2-node cluster running RHEL 6.2 and formatted the 2 test LUN’s to EXT4 and GFS2. We did a simple “time&amp;nbsp; tar -cvf /dev/null “ of each of the filesystems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EXT4: 28 minutes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GFS2: 305 minutes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RedHat Support had us try a “dd of=/dev/null if=/dev/mapper/mpathc bs=4096” on both filesystems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GFS2: 45 minutes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GFS2 with lock_nolock: 41 minutes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EXT4: 38 minutes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore, I am assuming that the issue is with RedHat, and am looking for thoughts. RedHat Support has not been very good in getting this resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Emil&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jun 2012 18:37:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693507#M62283</guid>
      <dc:creator>Emil Henry</dc:creator>
      <dc:date>2012-06-18T18:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: Subject: Performance Issue under RedHat</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693825#M62284</link>
      <description>&lt;P&gt;&amp;gt;RedHat Support had us try a “dd of=/dev/null if=/dev/mapper/mpathc bs=4096”&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you sure it wasn't /dev/zero?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2012 05:57:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693825#M62284</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2012-06-19T05:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Subject: Performance Issue under RedHat</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693869#M62286</link>
      <description>&lt;P&gt;Hi Dennis!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have used only /dev/null as the output file. Never tried /dev/zero. We were trying to read existing data from the file system and writing to a null device, instead of writing to the tape library.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Emil&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2012 06:13:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693869#M62286</guid>
      <dc:creator>Emil Henry</dc:creator>
      <dc:date>2012-06-19T06:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Subject: Performance Issue under RedHat</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693985#M62287</link>
      <description>&lt;P&gt;&amp;gt;I have used only /dev/null as the output file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oops, sorry, I assumed the input (if=) was first.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2012 06:55:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/subject-performance-issue-under-redhat/m-p/5693985#M62287</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2012-06-19T06:55:17Z</dc:date>
    </item>
  </channel>
</rss>

