<?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 Single LUN mirroring within a VG in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140229#M31576</link>
    <description>I have a VG which consists of 5 x 1.35TB Clariion LUNS. I was informed by the Storage team that one of these luns was experiencing parity errors for a while and the only way to correct is to relocate data elsewhere(maybe tape) and recreate the VG. This is not practicle due to the size invovled and the criticality of data.&lt;BR /&gt;&lt;BR /&gt;Is it possible,that if they were to provide me with another 1.35 TB LUN, that i could mirror the problematic LUN on this and detach the bad lun? &lt;BR /&gt;&lt;BR /&gt;The current probematic lun looks like this:&lt;BR /&gt;pvdisplay  --- Physical volume ---&lt;BR /&gt;pvdisplay  PV Name               /dev/sdd1&lt;BR /&gt;pvdisplay  VG Name               vg1&lt;BR /&gt;pvdisplay  PV Size               1.35 TB / not usable 0&lt;BR /&gt;pvdisplay  Allocatable           yes (but full)&lt;BR /&gt;pvdisplay  PE Size (KByte)       4096&lt;BR /&gt;pvdisplay  Total PE              354814&lt;BR /&gt;pvdisplay  Free PE               0&lt;BR /&gt;pvdisplay  Allocated PE          354814&lt;BR /&gt;pvdisplay  PV UUID               PvrSu9-NTgI-iZnZ-Xwi1-a6y1-12It-6wwKpT&lt;BR /&gt;</description>
    <pubDate>Mon, 04 Feb 2008 22:04:03 GMT</pubDate>
    <dc:creator>MonitKapoor</dc:creator>
    <dc:date>2008-02-04T22:04:03Z</dc:date>
    <item>
      <title>Single LUN mirroring within a VG</title>
      <link>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140229#M31576</link>
      <description>I have a VG which consists of 5 x 1.35TB Clariion LUNS. I was informed by the Storage team that one of these luns was experiencing parity errors for a while and the only way to correct is to relocate data elsewhere(maybe tape) and recreate the VG. This is not practicle due to the size invovled and the criticality of data.&lt;BR /&gt;&lt;BR /&gt;Is it possible,that if they were to provide me with another 1.35 TB LUN, that i could mirror the problematic LUN on this and detach the bad lun? &lt;BR /&gt;&lt;BR /&gt;The current probematic lun looks like this:&lt;BR /&gt;pvdisplay  --- Physical volume ---&lt;BR /&gt;pvdisplay  PV Name               /dev/sdd1&lt;BR /&gt;pvdisplay  VG Name               vg1&lt;BR /&gt;pvdisplay  PV Size               1.35 TB / not usable 0&lt;BR /&gt;pvdisplay  Allocatable           yes (but full)&lt;BR /&gt;pvdisplay  PE Size (KByte)       4096&lt;BR /&gt;pvdisplay  Total PE              354814&lt;BR /&gt;pvdisplay  Free PE               0&lt;BR /&gt;pvdisplay  Allocated PE          354814&lt;BR /&gt;pvdisplay  PV UUID               PvrSu9-NTgI-iZnZ-Xwi1-a6y1-12It-6wwKpT&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2008 22:04:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140229#M31576</guid>
      <dc:creator>MonitKapoor</dc:creator>
      <dc:date>2008-02-04T22:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: Single LUN mirroring within a VG</title>
      <link>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140230#M31577</link>
      <description>Mirror? Well, not really; but you can migrate the data off the LUN onto the newly added space.&lt;BR /&gt;&lt;BR /&gt;'pvmove' is your friend.  'vgextend' your volume group to include the new LUn, then 'pvmove' the data, followed by 'vgreduce' to remove the old LUN.&lt;BR /&gt;&lt;BR /&gt;See &lt;A href="http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html" target="_blank"&gt;http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html&lt;/A&gt; for exact details, in particular 13.5.2.</description>
      <pubDate>Mon, 04 Feb 2008 22:52:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140230#M31577</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2008-02-04T22:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: Single LUN mirroring within a VG</title>
      <link>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140231#M31578</link>
      <description>We do vgextend &amp;amp; lvextend(-m 1) and once the mirror synced do the lvreduce (-m 0) and do vgreduce.. similar procedure works well with HP-UX.. Not really done on Linux.&lt;BR /&gt;&lt;BR /&gt;lvextend/lvreduce are aplicable to all the lvol where the defective device is in use.</description>
      <pubDate>Mon, 04 Feb 2008 23:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/single-lun-mirroring-within-a-vg/m-p/4140231#M31578</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-02-04T23:44:05Z</dc:date>
    </item>
  </channel>
</rss>

