Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hmm. We didn't try any active/active stuff and since we also ran centos
5.2/8.2.6 I would guess that therein lies the difference and possibly
issue.
> -----Original Message-----
> From: nathan at robotics.net [mailto:nathan at robotics.net]
> Sent: 14 July 2008 19:59
> To: Lee Christie
> Cc: drbd-user at lists.linbit.com
> Subject: RE: [DRBD-user] Greater then 4TB
>
> On Mon, 14 Jul 2008, Lee Christie wrote:
>
> > During testing we knocked up a pair of servers with 5TB.
> Seemed to work
> > just fine, taken at face value. However we didn't put much
> data on the
> > volume so it is possible that it doesn't work with >4TB and
> we were just
> > lucky.
>
> Centos 5.2 kernel 2.6.18-92.1.6.el5xen running DRBD 8.2.6
>
> Box with valid data comes up fine with:
>
> /sbin/service cman start
> /sbin/service drbd start
> /sbin/service clvmd start
> /bin/mount -t gfs /dev/mirror/share /share
>
> I try to bring up 2nd primary, shortly after drbd start comes
> up I get a
> kernel panic, unfortunately, I am not able to get the full
> crash on my
> screen and nothing shows up in any logs. Below is what I was
> able to make
> out on the screen, it is typed in by hand so...
>
> Call Trace:
> [<ffffffff885efa11>] :drbd:w_make_resync_request+0x191/0x3f7
> [<ffffffff885ef731>] :drbd:drbd_worker+0x2a3/0x3f2
> [<ffffffff8028773e>] __wake_up_common+0x33/0x68
> [<ffffffff8860532a>] :drbd:drbd_thread_setup_0xa2/0x18b
> [<ffffffff80260b24>] child_rip+0xa/0x12
> [<ffffffff88605288>] :drbd:drbd_thread_setup_0x0/0x18b
> [<ffffffff80260b1a>] child_rip+0x0/0x12
>
> Code: 44 0f a3 20 19 d2 32 db 85 d2 0f 95 c3 eb 20 75 05 83 cb ff
> RIP [<ffffffff885ece4e>] :drbd:drbd_bm_test_bit+0x8b/0xd1
>
> drbd.conf:
> resource r0 {
> protocol C;
> handlers {
> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
> }
>
> startup {
> degr-wfc-timeout 120; # 2 minutes.
> become-primary-on both;
> }
>
> disk {
> on-io-error detach;
> max-bio-bvecs 1;
> }
>
> net {
> allow-two-primaries;
> after-sb-0pri discard-least-changes;
> after-sb-1pri discard-secondary;
> after-sb-2pri call-pri-lost-after-sb;
> rr-conflict call-pri-lost;
> }
>
> syncer {
> rate 100M;
> }
>
> on xen0.nyc.blinkmind.net {
> device /dev/drbd0;
> disk /dev/sdb;
> address 172.16.0.220:7789;
> flexible-meta-disk internal;
> }
>
> on xen1.nyc.blinkmind.net {
> device /dev/drbd0;
> disk /dev/sdb;
> address 172.16.0.221:7789;
> meta-disk internal;
> }
> }
>
-------------------------------------------------------------------------------
This email may contain legally privileged and/or confidential information. It is solely for and is confidential for use by the addressee. Unauthorised recipients must preserve, observe and respect this confidentiality. If you have received it in error please notify us and delete it from your computer. Do not discuss, distribute or otherwise copy it.
Unless expressly stated to the contrary this e-mail is not intended to, and shall not, have any contractually binding effect on the Company and its clients. We accept no liability for any reliance placed on this e-mail other than to the intended recipient. If the content is not about the business of this Company or its clients then the message is neither from nor sanctioned by the Company.
We accept no liability or responsibility for any changes made to this e-mail after it was sent or any viruses transmitted through this e-mail or any attachment. It is your responsibility to satisfy yourself that this e-mail or any attachment is free from viruses and can be opened without harm to your systems.