Hi,
On 07/24/2011 10:28 PM, Christian Völker wrote:
As both are backed by LVM I added the use-bmbv in disk {} section on
both drbd.conf files. To update config I started a drbdadm adjust
drbd0 on node 1. On node2 this command refused as it was still syncing.
node2 got rebooted again.
Now
Hi Felix,
this reminds me of something I've seen during a drbdadm adjust.
The adjusting Primary would re-initialize its DRBD and then (apparently)
sync back its hot AL extents from the peer. Seeing as the peer was
Inconsistent in your case (it was still syncing), this can't work, and
the
On 07/25/2011 01:31 PM, Christian Völker wrote:
Hi Felix,
this reminds me of something I've seen during a drbdadm adjust.
The adjusting Primary would re-initialize its DRBD and then (apparently)
sync back its hot AL extents from the peer. Seeing as the peer was
Inconsistent in your case (it
Hi Felix,
What? Do you say the primary updates its data from the secondary during
an adjust command?
Generally? No. In your case? Yes :-)
And why this?
OK, that's ancient? So that's what was shipping with RHEL5? Hmm. You may
want to
a) step away from your distributor's packaged DRBD or
b)
Hi again,
On 07/25/2011 02:22 PM, Christian Völker wrote:
What? Do you say the primary updates its data from the secondary during
an adjust command?
Generally? No. In your case? Yes :-)
And why this?
your changed some metadata config detail. So DRBD hat to detach your
backing device, do
Hi,
I'm having a two node setup here and serious issues.
node1 was running all the time without any issues.
node2 was rebooted and syncing.
As both are backed by LVM I added the use-bmbv in disk {} section on
both drbd.conf files. To update config I started a drbdadm adjust
drbd0 on node 1. On
Ok, I solved it on my own. Still don't know why this happened
I re-created the metadata with drbdadm create-md drbd0 while the
secondary on WFConnection and then forced the primary to be primary with
drbdsetup primary -force drbd0.
Now it's syncing and I can access my data. All good :)
On Tue, Oct 13, 2009 at 11:54:54AM +0200, maurizio oggiano wrote:
Hi all,
I have a problem with a cluster degraded with a node inconsistent state.
Is there a way to recovery a consistent state even if the sync source is dead?
Maybe by means a snapshot, but I don't know how to do that.
Can you
This is my initial sync. There is no data yet on there. And yes, it is
connected to a switch. This server only has 1 ethernet port... so
maybe that's the problem.
-marc
On Oct 13, 2009, at 4:21 PM, Lars Ellenberg wrote:
Can you elaborte on the situation?
Is this just a what iff
On Tue, Oct 13, 2009 at 04:42:09PM -0400, Marc Pope wrote:
This is my initial sync. There is no data yet on there. And yes, it is
connected to a switch. This server only has 1 ethernet port... so maybe
that's the problem.
I don't see the problem yet, then.
Care to show /proc/drbd, and maybe
On Tue, Oct 13, 2009 at 10:52:25PM +0200, Lars Ellenberg wrote:
On Tue, Oct 13, 2009 at 04:42:09PM -0400, Marc Pope wrote:
This is my initial sync. There is no data yet on there. And yes, it is
connected to a switch. This server only has 1 ethernet port... so maybe
that's the problem.
11 matches
Mail list logo
