<?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: RedHat 4.0 / udev / SAN disks in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973732#M47067</link>
    <description>Shalom TJ,&lt;BR /&gt;&lt;BR /&gt;This is probably the reporting utility being broken.&lt;BR /&gt;&lt;BR /&gt;Is the storage available to the RH 4 system?&lt;BR /&gt;&lt;BR /&gt;If not, its perhaps a more serious RH 4 bug.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Sat, 15 Apr 2006 14:21:59 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-04-15T14:21:59Z</dc:date>
    <item>
      <title>RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973731#M47066</link>
      <description>working with RedHat 4.0, I have noticed a few differences with the way SAN storage reporting works compared to RH 3.0.  We use the EMC tool inq and the HP supplied lssd from the fibreutils rpm to do some reporting on SAN storage.  I have noticed, that after rebooting, the makedev's we run to allow inq/lssd to see and report on the SAN storage does not work.  I believe it is just a udev issue, but being unfamiliar with udev, I am at a loss as to how to proceed.  Any info on how to make udev devices for SAN storage?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Fri, 14 Apr 2006 09:25:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973731#M47066</guid>
      <dc:creator>TJ Toedebusch</dc:creator>
      <dc:date>2006-04-14T09:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973732#M47067</link>
      <description>Shalom TJ,&lt;BR /&gt;&lt;BR /&gt;This is probably the reporting utility being broken.&lt;BR /&gt;&lt;BR /&gt;Is the storage available to the RH 4 system?&lt;BR /&gt;&lt;BR /&gt;If not, its perhaps a more serious RH 4 bug.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sat, 15 Apr 2006 14:21:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973732#M47067</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-04-15T14:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973733#M47068</link>
      <description>Hi TJ,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00306808/c00306808.pdf?jumpid=reg_R1002_USEN" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00306808/c00306808.pdf?jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hope this helps !!!</description>
      <pubDate>Wed, 03 May 2006 17:42:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973733#M47068</guid>
      <dc:creator>Bharath_Pingali</dc:creator>
      <dc:date>2006-05-03T17:42:41Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973734#M47069</link>
      <description>I think I found the issue.  the inq utility requires the /dev/sgXX links be made and this is normally done by running MAKEDEV sg against the /dev directory...  but with udev, the /dev directory get rebuilt after reboot.  I think if I just make those links and mknodes under /etc/udev/devices, I will be OK.  Haven't tried yet, but this the path I am going down.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Fri, 05 May 2006 07:07:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973734#M47069</guid>
      <dc:creator>TJ Toedebusch</dc:creator>
      <dc:date>2006-05-05T07:07:09Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973735#M47070</link>
      <description>We had a small linux workshop with HP a few weeks ago. I couldn't test any of what we were showed (powerpoint, not a real workshop, actually), but from what I recall they were very aware of that issue, and I think there ought to be a configuration mechanism in udev that will automatically create the symlinks for You.&lt;BR /&gt;&lt;BR /&gt;In general, if You have a devfs/devmapper/udev controller /dev filesystem, don't manually edit in there.&lt;BR /&gt;&lt;BR /&gt;(rant: this is where enterprise distributions get us. 'supported' is outdated and doesn't work, making it work is unsupported, horray!)</description>
      <pubDate>Fri, 05 May 2006 12:48:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973735#M47070</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2006-05-05T12:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat 4.0 / udev / SAN disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973736#M47071</link>
      <description>Figured out how to dynamically populate the /dev dir after reboots using udev.</description>
      <pubDate>Mon, 15 May 2006 12:33:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-4-0-udev-san-disks/m-p/4973736#M47071</guid>
      <dc:creator>TJ Toedebusch</dc:creator>
      <dc:date>2006-05-15T12:33:23Z</dc:date>
    </item>
  </channel>
</rss>

