<?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: pvmove? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010921#M605210</link>
    <description>&lt;!--!*#--&gt;Coolmar,&lt;BR /&gt;&lt;BR /&gt;From pvmove(1M):&lt;BR /&gt;      The pvmove command moves allocated physical extents and the data they&lt;BR /&gt;      contain from a source physical volume, source_pv_path, to one or more&lt;BR /&gt;      other physical volumes in the same volume group.&lt;BR /&gt;&lt;BR /&gt;So, yes, 'pvmove' is like 'mv' in the sense that source data are discarded after the operation completes.&lt;BR /&gt;&lt;BR /&gt;PCS&lt;BR /&gt;</description>
    <pubDate>Thu, 31 May 2007 12:54:00 GMT</pubDate>
    <dc:creator>spex</dc:creator>
    <dc:date>2007-05-31T12:54:00Z</dc:date>
    <item>
      <title>pvmove?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010919#M605208</link>
      <description>Is pmove like the "mv" command where it will move all the data from one lun to another rather than *copy* it.  So LUN1 becomes empty and LUN2 has all the data after a pvmove?</description>
      <pubDate>Thu, 31 May 2007 12:47:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010919#M605208</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2007-05-31T12:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010920#M605209</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;Yes.  See the manpages for 'pvmove(1M)' for some options.&lt;BR /&gt;&lt;BR /&gt;Whatever you do, if/when you use 'pvmove' do not interrupt (kill) it.  You can leave your volume in a "corrupt" state.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 31 May 2007 12:52:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010920#M605209</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-05-31T12:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010921#M605210</link>
      <description>&lt;!--!*#--&gt;Coolmar,&lt;BR /&gt;&lt;BR /&gt;From pvmove(1M):&lt;BR /&gt;      The pvmove command moves allocated physical extents and the data they&lt;BR /&gt;      contain from a source physical volume, source_pv_path, to one or more&lt;BR /&gt;      other physical volumes in the same volume group.&lt;BR /&gt;&lt;BR /&gt;So, yes, 'pvmove' is like 'mv' in the sense that source data are discarded after the operation completes.&lt;BR /&gt;&lt;BR /&gt;PCS&lt;BR /&gt;</description>
      <pubDate>Thu, 31 May 2007 12:54:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/4010921#M605210</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2007-05-31T12:54:00Z</dc:date>
    </item>
  </channel>
</rss>

