Hi,
I have a problem between DRBD and iscsi disk mapping.
The problem is the following:
When I restart my Debian 9 server my DRBD service don't start, I believe
because the iscsi doesn't ready.
This is my log messages in /var//log/syslog:
Feb 21 12:03:25 bkp kernel: [ 10.459216] scsi
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] DRBD an ISCSI
That's easily accomplished with Pacemaker cluster manager,
there are many guides on how to do it all over the internet.
Simply said, Pacemaker controls both DRBD and ISCSI targets
and if the slave node detects master's failure
I have researched some about mixing DRBD an ISCSI. An what I am finding is
opinions about as vast as what people like on pizza.
So I figure I would ask it here...
Can I take 2 servers, setup DRBD between them, then configure ISCSI on both
servers but only connect to 1 of the ISCSI targets.
That's easily accomplished with Pacemaker cluster manager,
there are many guides on how to do it all over the internet.
Simply said, Pacemaker controls both DRBD and ISCSI targets
and if the slave node detects master's failure - it promotes
DRBD to primary, brings up shared ip address and starts
Anybody have an idea whats happened (see below)? The iSCSI and NFS load are
both KVM images (iSCSI is LVM based).
Gerald
- Original Message -
From: Gerald Brandt g...@majentis.com
To: drbd-user@lists.linbit.com
Sent: Saturday, November 30, 2013 11:00:20 AM
Subject: [DRBD-user
, 2013 11:00:20 AM
Subject: [DRBD-user] DRBD with iSCSI vs NFS issue
Hi,
I've been running DRBD on my servers for quite some time on some
servers at a clients (a little over a year with this client, I
believe). I've been exporting drbd0 as iSCSI for the entire time.
Write tests over GigE (1B
, 2013 11:00:20 AM
Subject: [DRBD-user] DRBD with iSCSI vs NFS issue
Hi,
I've been running DRBD on my servers for quite some time on some
servers at a clients (a little over a year with this client, I
believe). I've been exporting drbd0 as iSCSI for the entire time.
Write tests over GigE (1B
Hi,
I've been running DRBD on my servers for quite some time on some servers at a
clients (a little over a year with this client, I believe). I've been
exporting drbd0 as iSCSI for the entire time. Write tests over GigE (1B block
size, sequential write) gives me an everage of 118MB/s. Very
Hello,
On Fri, Jul 27, 2012 at 4:32 AM, Christian Balzer ch...@gol.com wrote:
Hello,
I'm pondering a HA iSCSI (really iSER or SRP, Infiniband backend) storage
cluster based on DRBD and Pacemaker. So something that has been documented
and implemented numerous times.
However setting up
On Jul 26, 2012, at 10:32 PM, Christian Balzer wrote:
1. Which bloody iSCSI stack?
I've been satisfied with LIO, though I can't say I've tested the others as
extensively. I'm using the Debian kernel from sequeeze-backports. I'm using an
Ethernet backend, so I can't comment on anything more
Hello,
I'm pondering a HA iSCSI (really iSER or SRP, Infiniband backend) storage
cluster based on DRBD and Pacemaker. So something that has been documented
and implemented numerous times.
However setting up things on one of my test clusters it became clear to me
that this is probably not
on this aspect of such a
cluster.
-Morey
-Original Message-
From: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of Mark Watts
Sent: Wednesday, September 08, 2010 9:03 AM
To: Jiri Vitek; drbd-user@lists.linbit.com
Subject: Re: [DRBD-user
On Thu, 9 Sep 2010 14:57:55 +0200
Bart Coninckx bart.conin...@telenet.be wrote:
Maybe I might throw in a warning: I use a active/passive iSCSI server based
on
Heartbeat and DRBD as well and it serves both blockdevices for Xen guests as
storage for a Novell NSS file system. After
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know you can export DRBD block devices as iSCSI LUNs, but what happens
to active iSCSI connections when a fail-over occurs?
Do they get reconnected automatically or is it something more involved?
(Last time I looked at iSCSI I'm sure you had to
On Wed, Sep 08, 2010 at 01:59:13PM +0100, Mark Watts wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know you can export DRBD block devices as iSCSI LUNs, but what happens
to active iSCSI connections when a fail-over occurs?
Do they get reconnected automatically or is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/08/2010 03:57 PM, Jiri Vitek wrote:
you need properly configured heartbeat with ietd which will provide
failover to ietd and ip on which ietd listen. With this setup initiator
will detect connection error and wait with data for failover
Watts
Sent: Wednesday, September 08, 2010 9:03 AM
To: Jiri Vitek; drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] DRBD and iSCSI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/08/2010 03:57 PM, Jiri Vitek wrote:
you need properly configured heartbeat with ietd which will provide
failover
-Original Message-
From: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of Mark Watts
Sent: Wednesday, September 08, 2010 9:03 AM
To: Jiri Vitek; drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] DRBD and iSCSI
On 09/08/2010 03:57 PM
18 matches
Mail list logo
