<?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: failed pvmove clvm rh4 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972566#M27615</link>
    <description>This is a new LV without FS so it's not possible that someone lock it.</description>
    <pubDate>Thu, 05 Apr 2007 03:32:23 GMT</pubDate>
    <dc:creator>SV Linux</dc:creator>
    <dc:date>2007-04-05T03:32:23Z</dc:date>
    <item>
      <title>failed pvmove clvm rh4</title>
      <link>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972564#M27613</link>
      <description>I'm not able to pvmove a LV from PV to other PV on same VG; the environment is a Linux cluster RH4U4 with clvm. VG is composed by three PV;&lt;BR /&gt;pvmove -n /dev/myvg/pippone /dev/sdy2 /dev/sdx2&lt;BR /&gt;  Error locking on node pinco.pluto.it: Resource temporarily unavailable&lt;BR /&gt;  Failed to activate pippone&lt;BR /&gt;&lt;BR /&gt;Chris&lt;BR /&gt;</description>
      <pubDate>Fri, 30 Mar 2007 02:42:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972564#M27613</guid>
      <dc:creator>SV Linux</dc:creator>
      <dc:date>2007-03-30T02:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: failed pvmove clvm rh4</title>
      <link>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972565#M27614</link>
      <description>Shalom, &lt;BR /&gt;&lt;BR /&gt;It would appear that someone or some process is using the physical volume you wish to move. Perhaps try it again in single user mode.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 30 Mar 2007 08:13:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972565#M27614</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-03-30T08:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: failed pvmove clvm rh4</title>
      <link>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972566#M27615</link>
      <description>This is a new LV without FS so it's not possible that someone lock it.</description>
      <pubDate>Thu, 05 Apr 2007 03:32:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972566#M27615</guid>
      <dc:creator>SV Linux</dc:creator>
      <dc:date>2007-04-05T03:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: failed pvmove clvm rh4</title>
      <link>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972567#M27616</link>
      <description>Thanks for the update.&lt;BR /&gt;&lt;BR /&gt;I therefore suggest, since its new.&lt;BR /&gt;&lt;BR /&gt;lvremove&lt;BR /&gt;&lt;BR /&gt;lvcreate in new location.&lt;BR /&gt;&lt;BR /&gt;This assumes there is no data on it.&lt;BR /&gt;&lt;BR /&gt;Note that clvm daemon will not work unless ccsd and cman are already running on a valid cluster configuration.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 05 Apr 2007 03:58:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/failed-pvmove-clvm-rh4/m-p/3972567#M27616</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-04-05T03:58:21Z</dc:date>
    </item>
  </channel>
</rss>

