<?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 Emulex 1105e HP in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/emulex-1105e-hp/m-p/4630864#M40800</link>
    <description>We have installed 2007-lpfc drivers in ours two RHEL5.3 server's. Our 4100 EVA, has presented 1 LUN 10GB, in tow server's.&lt;BR /&gt;&lt;BR /&gt;The server's can view perfectly this LUN, but when we try to writte fron one sever, you can writte, but the other server can't view the same data.&lt;BR /&gt;If you restart the server that can't view the LUN data, you can view the same information, but only read access.&lt;BR /&gt;&lt;BR /&gt;How we can change this situation? We've tried the last drivers 2009-lpfc, and didn't work, compilation error.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
    <pubDate>Mon, 10 May 2010 09:31:28 GMT</pubDate>
    <dc:creator>Xavier Almenar</dc:creator>
    <dc:date>2010-05-10T09:31:28Z</dc:date>
    <item>
      <title>Emulex 1105e HP</title>
      <link>https://community.hpe.com/t5/operating-system-linux/emulex-1105e-hp/m-p/4630864#M40800</link>
      <description>We have installed 2007-lpfc drivers in ours two RHEL5.3 server's. Our 4100 EVA, has presented 1 LUN 10GB, in tow server's.&lt;BR /&gt;&lt;BR /&gt;The server's can view perfectly this LUN, but when we try to writte fron one sever, you can writte, but the other server can't view the same data.&lt;BR /&gt;If you restart the server that can't view the LUN data, you can view the same information, but only read access.&lt;BR /&gt;&lt;BR /&gt;How we can change this situation? We've tried the last drivers 2009-lpfc, and didn't work, compilation error.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Mon, 10 May 2010 09:31:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/emulex-1105e-hp/m-p/4630864#M40800</guid>
      <dc:creator>Xavier Almenar</dc:creator>
      <dc:date>2010-05-10T09:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Emulex 1105e HP</title>
      <link>https://community.hpe.com/t5/operating-system-linux/emulex-1105e-hp/m-p/4630865#M40801</link>
      <description>What's the filesystem type you're using? Regular ext3 or a cluster filesystem like GFS or OCFS?&lt;BR /&gt;&lt;BR /&gt;A regular filesystem like ext3 has a built-in assumption that the filesystem will be mounted by one server at a time only. This allows extensive caching to improve filesystem performance.&lt;BR /&gt; &lt;BR /&gt;When server B changes data on the disk, the server A may have an old version of the same data in its cache. Because a regular filesystem does not expect the data to change on the disk, server A will happily give the old version of the data from the cache to any application that asks for it. Sooner or later an application on server A will want something was not cached, so the server A will load more data from the disk. As a result, server A will have a corrupt mixture of old and updated data in its cache. The situation is symmetrical: the same may happen on server B too.&lt;BR /&gt;&lt;BR /&gt;If only one server is allowed to write to the disk, the problem is still there: the server with the read-only access still cannot know when the data it recently read from the disk is being modified by the other server. The server with the read-only access will again get corrupted data, unless all disk caching is prevented on that filesystem (which would hurt performance very much).&lt;BR /&gt;&lt;BR /&gt;So, you cannot simply present a regular filesystem to 2 or more servers simultaneously and have it work. You need a cluster filesystem: it will communicate between the servers, so that all the servers are aware what blocks each server is writing and can throw away old data in their read caches as necessary. A cluster filesystem will also implement some sort of cluster-wide file and/or block locking, to prevent any attempts to read any disk block that is being written to at the same time.&lt;BR /&gt;&lt;BR /&gt;RHEL 5 includes GFS cluster filesystem, but setting it up requires that you first configure the basic elements of a RedHat Cluster, to implement the cluster-wide locking infrastructure that is required by GFS.&lt;BR /&gt;&lt;BR /&gt;Note: to use RedHat Cluster and GFS, you will need the Advanced Platform version of the RHEL 5 license.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 11 May 2010 16:52:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/emulex-1105e-hp/m-p/4630865#M40801</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-05-11T16:52:35Z</dc:date>
    </item>
  </channel>
</rss>

