<br><br><div class="gmail_quote">On Fri, Apr 24, 2009 at 10:39 PM, Tom Brown <span dir="ltr"><<a href="mailto:tbrown@baremetal.com">tbrown@baremetal.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, 24 Apr 2009, Kristinn Soffanias Runarsson wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yeah I could do pvmove, that is what I will be using on machines that are<br>
using LVM. But most of them are just using plain devices. And LVM doesn't<br>
support non-destructive import of a device into LVM (but Solaris SVM does :)<br>
and I've had good results with that :)<br>
<br>
so drbd out of the question? :)<br>
</blockquote>
<br></div>
I have no idea. I don't know how you're consuming the storage, whether you can tolerate a reboot or two, whether this is the root filesystem of a device that is literally booting off it (as compared to a virtual machine using it for /).<br>
<br>
MD _might_ be able to help. You can build a mirror of an existing device, but you need to be able to tell your storage "consumer" to switch from using /dev/sda1 to /dev/md0 ... same as you would for drbd. The only real difference between using drbd and md is that drbd wants to sync to a remote server. MD wants to sync two local devices... but one or both of those could be network attached storage. lookup mdadm (the build option) if that seems interesting.<br>
<br>
That said, I've neither done this, nor do I have time to test it.<br><font color="#888888">
<br>
-Tom<br>
</font></blockquote></div><br>Yeah I can survive a few reboots, but not lengthy outages. As far as MD is concerned.. it cannot consume a device that already contains data without destroying it.<br><br>soffi<br>