<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">Thank you
Felix. My concern from the documentation sources from the
criteria at the top of the page:<br>
<br>
"1. The affected resource’s backing device must be one managed
by a logical volume management subsystem, such as LVM."<br>
<br>
The backing device is not LVM, it is is software RAID10. I'm
presuming this "criteria" is only stated because it isn't normal
to grow/shrink software RAID10, but I'm guessing that by syncing
drbd to a larger device, disconnecting the drbd peers, then
doing "drbd resize" and "pvresize /dev/drbd0" on the larger
system, it will react just fine?<br>
</font></font><br>
On 07/21/2011 01:21 AM, Felix Frank wrote:
<blockquote cite="mid:4E27D35E.2040607@mpexnet.de" type="cite">
<pre wrap="">On 07/21/2011 01:19 AM, Pete Ashdown wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have one host that has a StandAlone 1.5TB lvm running on top of drbd
(pv is /dev/drbd0) and a software raid10. I connected a second peer to
this with a 2TB software raid10. The drbd started to sync as expected,
but of course retained the 1.5TB sizing. If I disconnect the drbd peers
from each other, is it possible to safely grow the drbd & lvm to the
full 2TB?
</pre>
</blockquote>
<pre wrap="">
Well, <a class="moz-txt-link-freetext" href="http://www.drbd.org/users-guide/s-resizing.html#s-growing-offline">http://www.drbd.org/users-guide/s-resizing.html#s-growing-offline</a>
But why do it offline? You probably want to replace the original 1.5TB
node with another 2TB one, no? So why wouldn't you
1. fail over
2. disconnect
3. replace
4. connect + sync up
5. resize online?
HTH,
Felix
</pre>
</blockquote>
</body>
</html>