Look for compare #605957 and #529876...<br><br>:start<br><br>At first time pvmove create /dev/mapper/mir1a-pvmove0, change metadata. <br>move data, and not remove /dev/mapper/mir1a-pvmove0.<br><br>At second time pvmove -- fail, change metadata. but not move realdata<br>
and remove /dev/mapper/mir1a-pvmove0...<br><br>GOTO start<br><br><div class="gmail_quote">2010/12/5 Andrew Shirrayev <span dir="ltr"><<a href="mailto:andrews239@gmail.com">andrews239@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At first time i move 300Gb mail storage to new disk, and lost all data. :-(<br>Transfer complite at 300Gb/sec speed... <br><br>Kernel logs:<br><br>omega:~# ls -l /dev/mapper/ | grep move<br>
omega:~# dmesg | tail -2<br>[11762.790363] drbd5: peer( Secondary -> Primary )<br>[11764.552933] drbd2: peer( Secondary -> Primary )<br>omega:~# pvmove -n tmptmp1 /dev/sda2 /dev/sdb1<br> /dev/sda2: Moved: 48.0%<br>
/dev/sda2: Moved: 83.6%<div class="im"><br> /dev/sda2: Moved: 100.0%<br></div>omega:~# ls -l /dev/mapper/ | grep move<br>brw-rw---- 1 root disk 254, 17 2010-12-05 17:28 mir1a-pvmove0<br>omega:~# dmesg | tail -2<br>[11762.790363] drbd5: peer( Secondary -> Primary ) <br>
[11764.552933] drbd2: peer( Secondary -> Primary ) <br><div class="im">omega:~# pvmove -n tmptmp1 /dev/sdb1 /dev/sda2<br> device-mapper: create ioctl failed: Device or resource busy<br> device-mapper: reload ioctl failed: Invalid argument<br>
</div><div class="im">
WARNING: dev_open(/dev/sdb1) called while suspended<br> WARNING: dev_open(/dev/sda2) called while suspended<br> WARNING: dev_open(/dev/sdb1) called while suspended<br> WARNING: dev_open(/dev/sda2) called while suspended<br>
WARNING: dev_open(/dev/sdb1) called while suspended<br> WARNING: dev_open(/dev/sda2) called while suspended<br> /dev/sdb1: Moved: 100.0%<br></div><div class="im"> device-mapper: create ioctl failed: Device or resource busy<br>
</div><div class="im"> Unable to reactivate logical volume "pvmove0"<br></div>
omega:~# ls -l /dev/mapper/ | grep move<br>omega:~# dmesg | tail -4<br>[11762.790363] drbd5: peer( Secondary -> Primary ) <br>[11764.552933] drbd2: peer( Secondary -> Primary ) <br>[35829.622520] device-mapper: table: 254:16: linear: dm-linear: Device lookup failed<br>
[35829.622520] device-mapper: ioctl: error adding target to table<br><br><br><div class="gmail_quote">2010/12/5 Bastian Blank <span dir="ltr"><<a href="mailto:waldi@debian.org" target="_blank">waldi@debian.org</a>></span><div>
<div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
severity 605957 important<br>
thanks<br>
<div><br>
On Sun, Dec 05, 2010 at 05:11:19AM +0300, Andrew Shirayev wrote:<br>
> Justification: causes serious data loss<br>
<br>
</div>The log does not show any indication that there is actually some data<br>
lost.<br>
<br>
> ====== Short description<br>
<br>
I miss a description.<br>
<div><br>
> omega:~# pvmove -n tmptmp1 /dev/sdb1 /dev/sda2<br>
> device-mapper: create ioctl failed: Device or resource busy<br>
> device-mapper: reload ioctl failed: Invalid argument<br>
<br>
</div>The kernel log will shows the reason. No need to speculate here.<br>
<br>
Bastian<br>
<font color="#888888"><br>
--<br>
History tends to exaggerate.<br>
-- Col. Green, "The Savage Curtain", stardate 5906.4<br>
</font></blockquote></div></div></div><br>
</blockquote></div><br>