Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Monday 12 December 2011 12:23:06 Felix Frank wrote: > On 12/12/2011 11:14 AM, Christian Völker wrote: > >>> >> Otherwise I'd expect just to grow the underlying LVM and then do > >>> >> a "drbadm resize drbd0". Will this do any harm? > >> > yes, I'm afraid so. > > Is there an explanation why it's not working? Even then when I'll > > setup the upcoming secondary from scratch? > oh it *does* work, but not while your resource is up. If a downtime is > acceptable, then there's no problem. When the drbd is active with only one node, resizing shouldn't be a problem. The second node, once its set up, should have a underlying device of equal size though. But assuming you start drbd in a single-node first, grow that once you realize there is not enough space, then set up the second node and sync to that, there shouldn't be a problem. In fact I did the exact same but without the resize, saving network transfer by only syncing a populated and 50% filled filesystem instead of syncing random numbers before mkfs. Have fun, Arnold -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20111212/486fc513/attachment.pgp>