<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 10pt; color: #000000'>Hi,<br><br>DRBD is running directly on md0. /dev/drbd1 is then exported via iSCSI.<br><br>The logs show:<br><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.332010] drbd: initialized. Version: 8.3.7 (api:88/proto:86-91)</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.332012] drbd: GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root@filer-1, 2011-03-05 08:29:38</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.332014] drbd: registered as block device major 147</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.332015] drbd: minor_table @ 0xffff88021dbaf300</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.334144] block drbd1: Starting worker thread (from cqueue [1489])</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif; background-color: rgb(248, 250, 51);">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.334177] block drbd1: ==> truncating very big lower level device to currently maximum possible 8587575296 sectors <==</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif; background-color: rgb(248, 250, 51);"><span style="font-family: courier new,courier,monaco,monospace,sans-serif; background-color: rgb(248, 250, 51);">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.334179] block drbd1: ==>> using internal or flexible meta data may help <<==</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif; background-color: rgb(248, 250, 51);"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.334188] block drbd1: disk( Diskless -> Attaching ) </span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.353306] Loading iSCSI transport class v2.0-870.</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.360582] skge eth0: disabling interface</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 iscsid: iSCSI logger with pid=1515 started!</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 kernel: [ 7.381956] iscsi: registered transport (iser)</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 init: ssh main process (1162) terminated with status 255</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:53 iscsi-filer-1 postfix/master[1411]: reload -- version 2.7.0, configuration /etc/postfix</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584678] block drbd1: Found 57 transactions (3507 active extents) in activity log. </span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584684] block drbd1: Method to ensure write ordering: barrier</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584691] block drbd1: Backing device's merge_bvec_fn() = ffffffffa00c0100</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584694] block drbd1: max_segment_size ( = BIO size ) = 4096</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584698] block drbd1: Adjusting my ra_pages to backing device's (32 -> 96) </span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.584704] block drbd1: drbd_bm_resize called with capacity == 8587575296</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.603470] block drbd1: resync bitmap: bits=1073446912 words=16772608</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Oct 21 15:34:54 iscsi-filer-1 kernel: [ 7.603474] block drbd1: size = 4095 GB (4293787648 KB)</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><br><span style="font-family: times new roman,new york,times,serif;">The lines in yellow bug me. I don't recall see them before.<br><br>I had a 4 disk RAID-6 md0 (4x2TB = 4 TB RAID-6). I added a single drive (5x2TB = 6 TB array).<br><br>Any ideas?<br><br>Gerald<br><br></span><br><hr id="zwchr"><br><blockquote> From: "Andreas Kurz" <andreas@hastexo.com><br> To: drbd-user@lists.linbit.com<br> Sent: Friday, October 21, 2011 2:55:06 PM<br> Subject: Re: [DRBD-user] Increasing a DRBD array<br> <br> On 10/21/2011 09:30 PM, Gerald Brandt wrote:<br> > Hi,<br> > <br> > I've successfully resize the lower level RAID-6 array, and grown<br> > it. I'm now attempting to resize drbd, and nothing seems to<br> > happen.<br> > <br> > /dev/md0 is definitely bigger.<br> > <br> > What should I see during a drbd resize?<br> <br> You should see a DRBD resync of the newly added space.<br> <br> What is the lower level device of your DRBD resource? The whole md0,<br> a<br> partition on md0, a lv on a vg on a pv on md0?<br> <br> ... so if the lower level device has been resized on both nodes, DRBD<br> should definitely grow on a "drbdadm resize".<br> <br> Did I mention that on starting DRBD it is resized automatically if a<br> bigger lower level device is detected? ... have a look at the kernel<br> logs...<br> <br> Regards,<br> Andreas<br> <br> --<br> Need help with DRBD?<br> http://www.hastexo.com/now<br> <br> > <br> > Gerald<br> > <br> > <br> > ----- Original Message -----<br> >> From: "Gerald Brandt" <gbr@majentis.com><br> >> To: drbd-user@lists.linbit.com<br> >> Sent: Tuesday, October 18, 2011 7:08:55 AM<br> >> Subject: Re: [DRBD-user] Increasing a DRBD array<br> >><br> >> Hi,<br> >><br> >> Okay, this is my list of what to do, and in what order:<br> >><br> >> 1. remove the primary from DRBD<br> >> 2. add the physical disk to the primary<br> >> 3. add the primary back to DRBD and allow resync.<br> >> 4. remove the secondary from DRBD<br> >> 5. add the physical disk to the secondary<br> >> 6. add the secondary back to DRBD and allow resync.<br> >> 7. fdisk and add the disk to the RAID array on primary and<br> >> secondary<br> >> 8. grow the RAID array on the primary and secondary (while mounted<br> >> or<br> >> not mounted?)<br> >> 9. drbdadm resize on the primary (can this be done while drbd is<br> >> in<br> >> use?)<br> >> 10. expand the file system on the primary only (via Citrix<br> >> XenServer<br> >> (iSCSI))<br> >><br> >> That sounds about right. As long as I don't lose data. (yeah,<br> >> backups. That's left up to my client, but becomes my problem if<br> >> they failed.)<br> >><br> >> Gerald<br> >><br> >><br> >><br> >> ----- Original Message -----<br> >>> From: "Florian Haas" <florian@hastexo.com><br> >>> To: drbd-user@lists.linbit.com<br> >>> Sent: Tuesday, October 18, 2011 3:53:11 AM<br> >>> Subject: Re: [DRBD-user] Increasing a DRBD array<br> >>><br> >>> On 2011-10-17 22:19, Matt Graham wrote:<br> >>>>>> Your DRBD uses the MD RAID as its backing device, doesn't it?<br> >>>>>> That means you'll have add the drive and resize your RAID<br> >>>>>> first,<br> >>>>>> then<br> >>>>>> you can resize your DRBD, and then expand the file system.<br> >>>>> Definitely built on top of the RAID. I'm a bit confused by<br> >>>>> your<br> >>>>> answer though. Step 8 grows the RAID array, and I don't have a<br> >>>>> step<br> >>>>> to grow DRBD. Does that mean I'm missing something?<br> >>>><br> >>>> 8. mdadm --grow /dev/md0 (other mdadm options)<br> >>>> Do that on both machines.<br> >>>> 8.1 (on secondary) drbdsetup /dev/drbd0 resize<br> >>>> 8.2 (on primary) drbdsetup /dev/drbd0 resize<br> >>><br> >>> There's a "resize" subcommand for drbdadm too; no need to use<br> >>> drbdsetup.<br> >>> And it needs to be done on one node only. Just do "drbdadm resize<br> >>> <resourcename>" on the primary while the two nodes are connected,<br> >>> and<br> >>> you're good to go.<br> >>><br> >>>> The softRAID is below the DRBD device. Once the softRAID is<br> >>>> larger, the DRBD device needs to be informed of this fact.<br> >>>> When making arrays/devices larger, you go bottom-up; you make<br> >>>> the hardware changes first, then softRAID changes, then DRBD<br> >>>> changes, then filesystem changes.<br> >>>> 9. (on primary) resize2fs /dev/drbd0<br> >>><br> >>> If it's ext3 and if it supports on-line resizing, of course. But<br> >>> that<br> >>> should be obvious.<br> >>><br> >>> Cheers,<br> >>> Florian<br> >>><br> >>> --<br> >>> Need help with DRBD?<br> >>> http://www.hastexo.com/knowledge/drbd<br> >>> _______________________________________________<br> >>> drbd-user mailing list<br> >>> drbd-user@lists.linbit.com<br> >>> http://lists.linbit.com/mailman/listinfo/drbd-user<br> >>><br> >> _______________________________________________<br> >> drbd-user mailing list<br> >> drbd-user@lists.linbit.com<br> >> http://lists.linbit.com/mailman/listinfo/drbd-user<br> >><br> > _______________________________________________<br> > drbd-user mailing list<br> > drbd-user@lists.linbit.com<br> > http://lists.linbit.com/mailman/listinfo/drbd-user<br> <br> <br> <br> <br> <br> _______________________________________________<br> drbd-user mailing list<br> drbd-user@lists.linbit.com<br> http://lists.linbit.com/mailman/listinfo/drbd-user<br> <br><br></blockquote></div></body></html>