<?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: Move data to a new LUN in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610566#M40349</link>
    <description>It should work sort of like in HP-UX, i.e.&lt;BR /&gt;&lt;BR /&gt;lvconvert -m0 /dev/vg01/lvol1 &lt;OLD_PV&gt;&lt;BR /&gt;&lt;BR /&gt;would unmirror the LV, making the &lt;OLD_PV&gt; free and keeping the data on the new one.&lt;BR /&gt;&lt;BR /&gt;An alternative would be to just brutally un-present the old LUN at the SAN level, or tell the SCSI subsystem to delete the old device: &lt;BR /&gt;echo 1 &amp;gt; /sys/block/&lt;OLD_LUN&gt;/device/delete&lt;BR /&gt;&lt;BR /&gt;When one-half of the LVM-mirrored LV becomes inaccessible or fails in any other way, LVM should automatically convert the remaining half of the mirror back to a regular non-mirrored LV. &lt;BR /&gt;&lt;BR /&gt;At the time of our last SAN migration, we used LVM mirror to migrate some RHEL 4 systems. Back then, the LVM mirror did the job, but somehow left me the impression of "fragility" - not quite ready for production use. But that was more than two years ago - perhaps it has improved, at least in RHEL 5.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/OLD_LUN&gt;&lt;/OLD_PV&gt;&lt;/OLD_PV&gt;</description>
    <pubDate>Wed, 31 Mar 2010 16:28:42 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2010-03-31T16:28:42Z</dc:date>
    <item>
      <title>Move data to a new LUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610565#M40348</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We are moving off of one SAN onto another.  Now in the HP-UX world, I would extend the VG with the new LUN and lvextend -m 1 each LV to the new LUN, then break the mirror lvreduce -m 0 and get rid of the old LUN, then remove the old LUN from the VG.&lt;BR /&gt;&lt;BR /&gt;In RHEL we are trying to do this and I did an lvconvert -m1 vg01/lvol1 and it was all successfully mirrored.  How do I now, break the mirror?  I know I can lsconvert -m0 but how do I tell it to unload the old lun and keep the data on the new one?  Or is this even possible?  I am wondering if this is not possible with Linux and you can either mirror or not mirror but can't use it to move data.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Sally</description>
      <pubDate>Wed, 31 Mar 2010 15:49:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610565#M40348</guid>
      <dc:creator>dev44</dc:creator>
      <dc:date>2010-03-31T15:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: Move data to a new LUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610566#M40349</link>
      <description>It should work sort of like in HP-UX, i.e.&lt;BR /&gt;&lt;BR /&gt;lvconvert -m0 /dev/vg01/lvol1 &lt;OLD_PV&gt;&lt;BR /&gt;&lt;BR /&gt;would unmirror the LV, making the &lt;OLD_PV&gt; free and keeping the data on the new one.&lt;BR /&gt;&lt;BR /&gt;An alternative would be to just brutally un-present the old LUN at the SAN level, or tell the SCSI subsystem to delete the old device: &lt;BR /&gt;echo 1 &amp;gt; /sys/block/&lt;OLD_LUN&gt;/device/delete&lt;BR /&gt;&lt;BR /&gt;When one-half of the LVM-mirrored LV becomes inaccessible or fails in any other way, LVM should automatically convert the remaining half of the mirror back to a regular non-mirrored LV. &lt;BR /&gt;&lt;BR /&gt;At the time of our last SAN migration, we used LVM mirror to migrate some RHEL 4 systems. Back then, the LVM mirror did the job, but somehow left me the impression of "fragility" - not quite ready for production use. But that was more than two years ago - perhaps it has improved, at least in RHEL 5.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/OLD_LUN&gt;&lt;/OLD_PV&gt;&lt;/OLD_PV&gt;</description>
      <pubDate>Wed, 31 Mar 2010 16:28:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610566#M40349</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-03-31T16:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: Move data to a new LUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610567#M40350</link>
      <description>pvmove might also be a simpler option..&lt;BR /&gt;&lt;BR /&gt;it creates the mirror and then removes it for you...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;man pvmove &lt;BR /&gt;</description>
      <pubDate>Wed, 31 Mar 2010 16:52:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/move-data-to-a-new-lun/m-p/4610567#M40350</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2010-03-31T16:52:07Z</dc:date>
    </item>
  </channel>
</rss>

