<?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: MSA 1000 and Linux AS 3 Update 5. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/msa-1000-and-linux-as-3-update-5/m-p/3836309#M66567</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If you can, boot the machine and remove the device files with the MSA not connected.&lt;BR /&gt;&lt;BR /&gt;rmsf is the command that will probably do the job.&lt;BR /&gt;&lt;BR /&gt;Then shut the system down, reconnect the system to the MSA and see what the results are.&lt;BR /&gt;&lt;BR /&gt;The device names are a function of how the LUNS are configured on the MSA device.&lt;BR /&gt;&lt;BR /&gt;Of course you could do a fresh OS install but thats a lot of work to solve this issue.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Thu, 03 Aug 2006 01:50:23 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-08-03T01:50:23Z</dc:date>
    <item>
      <title>MSA 1000 and Linux AS 3 Update 5.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/msa-1000-and-linux-as-3-update-5/m-p/3836308#M66566</link>
      <description>All,&lt;BR /&gt;&lt;BR /&gt;I have a Linux machine where a database is running and filesystems are created on LUNs from an MSA 1000 attached to this machine.&lt;BR /&gt;&lt;BR /&gt;I need to recreate the LUNs so that i can create 3 volumes groups using different LUNs.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Here is a snapshot of the /proc/partitions&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  65     0   10485600 sdq 119 97 912 510 11020 256441 556258 1118990 0 5620 1119520&lt;BR /&gt;   8     0    3145680 sda 27321 127730 1238770 150240 21557323 23310080 358940200 1922080 0 1517530 2071800&lt;BR /&gt;   8    16    5242800 sdb 224 327 3682 10580 14878660 25267871 321172248 750440 0 563600 760690&lt;BR /&gt;   8    32    3145680 sdc 121215 2125 985994 1112750 4177989 3718291 63170232 1218230 0 1886400 2330050&lt;BR /&gt;   8    48    3145680 sdd 121193 110 969698 510750 4168664 3727587 63170008 1201440 0 1208290 1711750&lt;BR /&gt;   8    64    3145680 sde 206 1738 14826 6750 19150049 15891793 280334712 447590 0 328430 454120&lt;BR /&gt;   8    80   39845280 sdf 185 122 1706 3570 170053 3264343 27504792 2337655 0 436400 2421605&lt;BR /&gt;   8    96   39845280 sdg 142 122 1362 3050 85854 1774617 14892816 27440224 0 236450 27459544&lt;BR /&gt;   8   112   39845280 sdh 1626 128 13282 6750 182116 4040742 33809256 6731602 0 532130 6795842&lt;BR /&gt;   8   128   39845280 sdi 178 119 1626 3590 173318 2998192 25401928 29710898 0 403800 29813608&lt;BR /&gt;   8   144   39845280 sdj 140 114 1282 3370 107628 2014561 16993616 9066981 0 278640 9112681&lt;BR /&gt;   8   160   17825520 sdk 381 132 3378 2150 55718 1017434 8589336 18899527 0 135870 18909987&lt;BR /&gt;   8   176   17825520 sdl 444 129 3858 2730 112275 2535988 21195648 34404261 0 333230 34426411&lt;BR /&gt;   8   192   17825520 sdm 115 115 1114 1310 29445 255399 2281376 15050630 0 35740 15057360&lt;BR /&gt;   8   208   17825520 sdn 114 115 1106 650 26679 258423 2281344 13551090 0 33320 13553420&lt;BR /&gt;   8   224   17825520 sdo 158 174 1930 2420 45921 342557 3108712 15179340 0 42740 15188170&lt;BR /&gt;   8   240  314573823 sdp 452 434 4322 840 24417 125664 1200648 11650 0 5120 12490&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see i have now /dev/sda to /dev/sdq.&lt;BR /&gt;&lt;BR /&gt;Once i destory the luns and recreate with different sixes, will the luns will have the same device files.&lt;BR /&gt;&lt;BR /&gt;eg: the first lun will be /dev/sda itself.&lt;BR /&gt;&lt;BR /&gt;If that is not the case, what should i do to make the new devices to start using in the order /dev/sda, /dev/sdb ...etc.&lt;BR /&gt;&lt;BR /&gt;Any help is appreciated ?</description>
      <pubDate>Wed, 02 Aug 2006 17:31:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/msa-1000-and-linux-as-3-update-5/m-p/3836308#M66566</guid>
      <dc:creator>Silver_1</dc:creator>
      <dc:date>2006-08-02T17:31:21Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 1000 and Linux AS 3 Update 5.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/msa-1000-and-linux-as-3-update-5/m-p/3836309#M66567</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If you can, boot the machine and remove the device files with the MSA not connected.&lt;BR /&gt;&lt;BR /&gt;rmsf is the command that will probably do the job.&lt;BR /&gt;&lt;BR /&gt;Then shut the system down, reconnect the system to the MSA and see what the results are.&lt;BR /&gt;&lt;BR /&gt;The device names are a function of how the LUNS are configured on the MSA device.&lt;BR /&gt;&lt;BR /&gt;Of course you could do a fresh OS install but thats a lot of work to solve this issue.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 03 Aug 2006 01:50:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/msa-1000-and-linux-as-3-update-5/m-p/3836309#M66567</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-03T01:50:23Z</dc:date>
    </item>
  </channel>
</rss>

