<?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: EXTENT-BASED MIRRORED STRIPES in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/extent-based-mirrored-stripes/m-p/3807810#M616754</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Seems like your plan will work.&lt;BR /&gt;&lt;BR /&gt;Would it not be easier to handle this on the hardware level? What kind of storage is this?&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 19 Jun 2006 06:47:52 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-06-19T06:47:52Z</dc:date>
    <item>
      <title>EXTENT-BASED MIRRORED STRIPES</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/extent-based-mirrored-stripes/m-p/3807809#M616753</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;Our volume group /dev/vgtest has two physical volume groups: PVG1, PVG2.&lt;BR /&gt;The mirror exists between two different PVGs, so data in PVG1 gets mirrored to PVG2.&lt;BR /&gt;Each physical volume group has 5 physical volumes.&lt;BR /&gt;I need to implement Distributed Allocation Policy on a shared VG (/dev/vgtest) in a two node ServiceGuard claster.&lt;BR /&gt;&lt;BR /&gt;Could I implement this change interactively without affecting the state of the database?&lt;BR /&gt;&lt;BR /&gt;I have outlined the steps that I think I need to take below.&lt;BR /&gt;&lt;BR /&gt;1) lvreduce -m 0 &lt;LVOL1&gt; &lt;DISKS_IN_PVG2&gt;&lt;BR /&gt;2) lvchange -D f &lt;LVOL1&gt;&lt;BR /&gt;3) lvextend -m 1 &lt;LVOL1&gt; &lt;PVG2&gt;&lt;BR /&gt;4) lvreduce -m 0 &lt;LVOL1&gt; &lt;DISKS_IN_PVG1&gt;&lt;BR /&gt;3) lvextend -m 1 &lt;LVOL1&gt; &lt;PVG1&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Have I missing anything?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/PVG1&gt;&lt;/LVOL1&gt;&lt;/DISKS_IN_PVG1&gt;&lt;/LVOL1&gt;&lt;/PVG2&gt;&lt;/LVOL1&gt;&lt;/LVOL1&gt;&lt;/DISKS_IN_PVG2&gt;&lt;/LVOL1&gt;</description>
      <pubDate>Mon, 19 Jun 2006 06:03:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/extent-based-mirrored-stripes/m-p/3807809#M616753</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2006-06-19T06:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: EXTENT-BASED MIRRORED STRIPES</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/extent-based-mirrored-stripes/m-p/3807810#M616754</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Seems like your plan will work.&lt;BR /&gt;&lt;BR /&gt;Would it not be easier to handle this on the hardware level? What kind of storage is this?&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 19 Jun 2006 06:47:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/extent-based-mirrored-stripes/m-p/3807810#M616754</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-06-19T06:47:52Z</dc:date>
    </item>
  </channel>
</rss>

