<div class="gmail_quote">2011/12/12 Christian Völker <span dir="ltr"></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><div class="im">>>>>>> Otherwise I'd expect just to grow the underlying LVM and<br>
>>>>>> then do a "drbadm resize drbd0". Will this do any harm?<br>
>>>><br>
>>>> yes, I'm afraid so.<br>
>> Is there an explanation why it's not working? Even then when<br>
>> I'll setup the upcoming secondary from scratch?<br>
><br>
> oh it *does* work, but not while your resource is up. If a downtime<br>
> is acceptable, then there's no problem.<br>
<br>
</div>Well, it doesn't. Put the device down (umount of FS done before, of<br>
course) with "drbdadm down drbd0". Did a "drbdadm resize drbd0" which<br>
ended in:<br>
drbdadm resize drbd0<br>
0: Failure: (138) Device does not have a disk-config<br></blockquote></div><br>If you extended the LV, then referring to an old post where Lars answered (that day it was for an hw raid expansion) I think it applies for you too:<br>
<br>"<br>well.<br>I guess you used internal meta data.<br>if the RAID got it right, then all the old data is still there,<br>lying at "the end" of the previous device, so somewhere at 220G.<br>drbd only looks for its meta data at the end of the device,<br>
so at offset ~400G currently.<br>there is nothing but nonsense there.<br><br>you have to create new drbd meta-data then,<br>as if you'd set it up for the first time.<br>"<br><br>Please note also in the page you referred <br>
<a href="http://www.drbd.org/users-guide/s-resizing.html" target="_blank">http://www.drbd.org/users-guide/s-resizing.html</a><br><br>the differences of caveats if resize is performed on-line or off-line.....<br><br>HIH,<br>
<br>Gianluca<br>