Bo Hansen wrote:
Hi,
I need an advice regarding hardware for DRBD. Currently I'm looking
into using two intel servers + adaptec raid controllers to form a DRBD
setup. I'm planning to put 28 SATA disks in each server and possibly
have two DRBD volumes (maybe 10 disks/vol/server). What is recom
>
>
> You should be able to match the oops stacktrace to a source code line,
> and find out what exactly has been NULL in your case.
>
> Other than that,
> and to double check that you really have a clean and fitting build,
> no, I'm afraid not.
>
I havent modify any source ( not that advanced )
u
On Tue, Jul 06, 2010 at 07:02:08PM +0200, Raoul Bhatia [IPAX] wrote:
> i have a self rolled kernel 2.6.27.48 and tried to compile drbd 8.3.8
> (debian way using module-assistant)
>
> uppon modprobe drbd, i get:
>
> > FATAL: Error inserting drbd
> > (/lib/modules/2.6.27.48+ipax/kernel/drivers/blo
Hi,
I need an advice regarding hardware for DRBD. Currently I'm looking into
using two intel servers + adaptec raid controllers to form a DRBD setup.
I'm planning to put 28 SATA disks in each server and possibly have two
DRBD volumes (maybe 10 disks/vol/server). What is recommended for the
DR
Hello All,
I am developing a master fail-over for my perceus cluster.
from a long time I am trying to implement* DRBD in combination with
heartbeat but it's not working* as it is suppose to be.
Nothing happen in DRBD when I start heartbeat I am doing everything
manually. I am doing it as:
i have a self rolled kernel 2.6.27.48 and tried to compile drbd 8.3.8
(debian way using module-assistant)
uppon modprobe drbd, i get:
> FATAL: Error inserting drbd
> (/lib/modules/2.6.27.48+ipax/kernel/drivers/block/drbd.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
and dme
Mhmh
You did perhaps give me some new investigation ways.
drbdadm says it uses 8.0.12 (good node) and 8.0.14 (reinstalled node).
Though, I have tried so many thing that the module version might not be
the same as utils version.
Seems it loads module from the kernel 2.6.26 sources
(/lib/modules/2.6
On Tue, Jul 06, 2010 at 12:06:11PM +1200, Michael wrote:
> On Tue, Jul 6, 2010 at 8:07 AM, Lars Ellenberg
> wrote:
>
> > On Mon, Jul 05, 2010 at 08:07:26AM +1200, Michael wrote:
> > > Hi All,
> > >
> > > I've installed ( as always ) from source 8.3.8
> > > All seems to work fine but when I've tri
On Tue, Jul 06, 2010 at 07:32:25AM +0200, Eulaerts Gregory wrote:
> Hello again,
>
> The crash was due to a failure of OS files, and of course, we got no
> backup for that server :)
>
> Node01 (the one that did not fail) : Version: 8.0.12 (api:86)
> Node02 (the one that failed) : Version: 8.0.14
W dniu 06.07.2010 10:18, Ralf W. pisze:
> The use of dopd helped in our case.
> Ralf
Hi,
You are mean something like this?
ha.cf
respawn hacluster /usr/lib/heartbeat/dopd
apiauth dopd gid=haclient uid=hacluster
resource my_resource {
handlers {
outdate-peer "/usr/lib/heartbeat/drbd-peer-outdat
The use of dopd helped in our case.
Ralf
- Original Message
From: "f...@ll"
To: drbd-user@lists.linbit.com
Sent: Tue, July 6, 2010 9:52:04 AM
Subject: [DRBD-user] active/active - how to solve split-brain auto repair
Hi,
This is my net section from drbd.conf with two primary:
net {
a
Hi,
This is my net section from drbd.conf with two primary:
net {
allow-two-primaries;
cram-hmac-alg "sha1";
after-sb-0pri discard-zero-changes;
after-sb-1pri consensus;
after-sb-2pri disconnect;
sndbuf-size 0;
rcvbuf-size 0;
}
When there is a split-brain, I have to manually repair.
What would I
12 matches
Mail list logo
