Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] DRBD-8: recent regression causing corruption andcrashes
Date: Fri, 11 Aug 2006 21:57:16 +0200	[thread overview]
Message-ID: <20060811195716.GI7373@soda.linbit> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767103624F87@EXNA.corp.stratus.com>

/ 2006-08-11 15:11:38 -0400
\ Graham, Simon:
> > / 2006-08-11 12:01:23 -0400
> > \ Graham, Simon:
> > > Quick update:
> > >
> > 
> > How exactly do you "test"?
> > Kernel and hardware?
> > (sorry, if you posted that earlier, just point me to it)
> 
> In this case, this happens only when I install a pair of systems from
> scratch and it is doing initial synchronization of one specific DRBD
> partition which is also being written to by our applications at the same
> time. I did post the sequence at the end of a previous message, but it's
> basically:
> 
> 1. on both systems use drbdmeta to wipe the meta data with no network
> connection established
> 2. on one system, mount the drbd disk, make a file system and untar some
> stuff on to it (still with no network connection)
> 3. reboot both systems - when they come up, resync starts. On one
> system, mount the file system (which causes reads/writes
>    at the same time as the resync)
> 
> Once I'm in this state (and have had the crash which happens everytime),
> I'm not able to manually resync the disks -- I suspect I don't
> understand enough about this yet, but it always says there is a
> split-brain and it's not able to fix it even if I set the after-sb-xpri
> options.
> 
> The hardware is a pair of Dell servers, software is 2.6.16.13 with Xen
> 3.0.2 patches; this all worked fine until about 1 week ago when I
> upgraded to the latest trunk version of drbd 8.

ok...
so there is badness somewhere in our recent commits?
you remember (look it up in the kernel logs) which
revision did work last?

did you change the file system?

> Simon
> 
> BTW: I have also checked carefully that I'm running the latest trunk
> version (as of last night).

Also, I'm up to some serious bug in the alloc_ee function:
we do not handle bio_add_page "errors" yet, but they _do_ occur.
may or may not be related to those strange WriteAck sector == 0.

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :

  reply	other threads:[~2006-08-11 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 19:11 [Drbd-dev] DRBD-8: recent regression causing corruption andcrashes Graham, Simon
2006-08-11 19:57 ` Lars Ellenberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 21:55 Graham, Simon
2006-08-11 22:31 Graham, Simon
2006-08-14  6:53 ` Philipp Reisner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060811195716.GI7373@soda.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox