<?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: Why the duplicate device file names are like &amp;quot;/dev/sddlmaa, /dev/sddlmab and /dev/sddlmac&amp;quot; in linux. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776514#M44156</link>
    <description>You definitely have HDLM.&lt;BR /&gt;&lt;BR /&gt;You should have just used native multipathing in Linux (device mapper multipath).&lt;BR /&gt;&lt;BR /&gt;Please read through Hitachi's document so the HDS disks are excluded from Linux's device mapper multipath control and be aware or you could whack/user/reuse/initialize the wrong disk.&lt;BR /&gt;&lt;BR /&gt;Please also be familiar with "blkid"&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 13 Apr 2011 17:14:47 GMT</pubDate>
    <dc:creator>Alzhy</dc:creator>
    <dc:date>2011-04-13T17:14:47Z</dc:date>
    <item>
      <title>Why the duplicate device file names are like "/dev/sddlmaa, /dev/sddlmab and /dev/sddlmac" in linux.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776512#M44154</link>
      <description>We have three LUNs in SUSE linux (SLES 9) coming fomr hitachi storage..&lt;BR /&gt;&lt;BR /&gt;So that the device files are shown like "sda, sdb and sdc"...We are using this only...&lt;BR /&gt;&lt;BR /&gt;Apart from this there are 3 more device files like "/dev/sddlmaa, /dev/sddlmab and /dev/sddlmac".&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We can find this from fdisk.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# fdisk -l&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sda: 53.6 GB, 53687091200 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 6527 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;   Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sda1               1         132     1059389   83  Linux&lt;BR /&gt;Partition 1 does not end on cylinder boundary.&lt;BR /&gt;/dev/sda2            1307        2611    10482412+  83  Linux&lt;BR /&gt;/dev/sda3            2612        4569    15727635   83  Linux&lt;BR /&gt;/dev/sda4            4570        6527    15727635   83  Linux&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sdb: 107.3 GB, 107374182400 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 13054 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;   Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sdb1               1        8355    67111506   83  Linux&lt;BR /&gt;/dev/sdb2            8356        9661    10490445   83  Linux&lt;BR /&gt;/dev/sdb3            9662       10967    10490445   83  Linux&lt;BR /&gt;/dev/sdb4           10968       13054    16763827+   5  Extended&lt;BR /&gt;/dev/sdb5           10968       12184     9775521   83  Linux&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sdc: 107.3 GB, 107374182400 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 13054 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;   Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sdc1               1        7181    57681351   83  Linux&lt;BR /&gt;/dev/sdc2            7182        8878    13631152+  83  Linux&lt;BR /&gt;/dev/sdc3            8879       12794    31455270   83  Linux&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sddlmaa: 53.6 GB, 53687091200 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 6527 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;       Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sddlmaa1               1         132     1059389   83  Linux&lt;BR /&gt;Partition 1 does not end on cylinder boundary.&lt;BR /&gt;/dev/sddlmaa2            1307        2611    10482412+  83  Linux&lt;BR /&gt;/dev/sddlmaa3            2612        4569    15727635   83  Linux&lt;BR /&gt;/dev/sddlmaa4            4570        6527    15727635   83  Linux&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sddlmab: 107.3 GB, 107374182400 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 13054 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;       Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sddlmab1               1        8355    67111506   83  Linux&lt;BR /&gt;/dev/sddlmab2            8356        9661    10490445   83  Linux&lt;BR /&gt;/dev/sddlmab3            9662       10967    10490445   83  Linux&lt;BR /&gt;/dev/sddlmab4           10968       13054    16763827+   5  Extended&lt;BR /&gt;/dev/sddlmab5           10968       12184     9775521   83  Linux&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sddlmac: 107.3 GB, 107374182400 bytes&lt;BR /&gt;255 heads, 63 sectors/track, 13054 cylinders&lt;BR /&gt;Units = cylinders of 16065 * 512 = 8225280 bytes&lt;BR /&gt;&lt;BR /&gt;       Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sddlmac1               1        7181    57681351   83  Linux&lt;BR /&gt;/dev/sddlmac2            7182        8878    13631152+  83  Linux&lt;BR /&gt;/dev/sddlmac3            8879       12794    31455270   83  Linux&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Apr 2011 11:19:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776512#M44154</guid>
      <dc:creator>senthil_kumar_1</dc:creator>
      <dc:date>2011-04-12T11:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why the duplicate device file names are like "/dev/sddlmaa, /dev/sddlmab and /dev/sddlmac" in linux.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776513#M44155</link>
      <description>&lt;!--!*#--&gt;I know nothing, but a Google search for&lt;BR /&gt;      /dev/sddlmaa&lt;BR /&gt;suggests that you might have HDLM software&lt;BR /&gt;installed.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hdsguides.com/uspv-vm/HDLM-ConceptsandPlanningGuide.html" target="_blank"&gt;http://hdsguides.com/uspv-vm/HDLM-ConceptsandPlanningGuide.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; So that the device files are shown like&lt;BR /&gt;&amp;gt; "sda, sdb and sdc"...We are using this&lt;BR /&gt;&amp;gt; only...&lt;BR /&gt;&lt;BR /&gt;Then perhaps you wasted the money you paid&lt;BR /&gt;for HDLM (if any).</description>
      <pubDate>Tue, 12 Apr 2011 11:53:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776513#M44155</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2011-04-12T11:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Why the duplicate device file names are like "/dev/sddlmaa, /dev/sddlmab and /dev/sddlmac" in linux.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776514#M44156</link>
      <description>You definitely have HDLM.&lt;BR /&gt;&lt;BR /&gt;You should have just used native multipathing in Linux (device mapper multipath).&lt;BR /&gt;&lt;BR /&gt;Please read through Hitachi's document so the HDS disks are excluded from Linux's device mapper multipath control and be aware or you could whack/user/reuse/initialize the wrong disk.&lt;BR /&gt;&lt;BR /&gt;Please also be familiar with "blkid"&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Apr 2011 17:14:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-the-duplicate-device-file-names-are-like-quot-dev-sddlmaa/m-p/4776514#M44156</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-04-13T17:14:47Z</dc:date>
    </item>
  </channel>
</rss>

