On 8/13/07, <b class="gmail_sendername">Jonathan Billings</b> <<a href="mailto:billings@negate.org">billings@negate.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there any reason why you have to have a clone of the filesystem?<br>Resizing lvm volumes is possible, as well as resizing ext3 filesystems,<br>but why go through the effort unnecessarily?<br><br>I assume that you aren't using the full capacity of the original drive,
<br>so you could always copy the data from one disk to the other, without<br>needing to clone the filesystem.<br><br>One thing you could do is this:<br>I assume you have /dev/Old/Root as /, and /dev/New/Root as the new disk,
<br>at /mnt/newroot. I'd then run:<br><br>cd /mnt/newroot;<br>/sbin/dump 0f - / | /sbin/restore rf -<br><br>That'll copy all the data from / to /mnt/newroot. Since this is LVM, I<br>suspect you'll also have to create and copy a /boot partition too, which
<br>isn't in LVM.<br><br></blockquote></div><br><br>I guess I left a few details out. :(<br><br>The new drive is actually in a second machine with identical hardware as the first.<br><br>I was tasked with putting together a server with the hardware we had at hand. I was asked
<br>to make a second box the same as the first so if it would ever die, anybody would be able to unplug<br>it and plug the backup unit in.<br><br>You are correct in that the 40gb drives are nowheres near full.<br><br>Typically I would use DD and Netcat for this. Which is how I learned my second drive is just slightly smaller
<br>than the first. Assuming the end of the drive is all zero's, is it safe to just ignore any errors I receive?<br><br>-Mike<br>