Thank you, that was the issue. And is gentoo related also, with a little
bit of mistake from my side for not reading all bug lists when upgrading a
software. See end of posts in this bug thread
http://bugs.gentoo.org/275684";>http://bugs.gentoo.org/275684,
useless change of init script from my poin
You did not provide all the relevant info required, but I think that
you issue is as below
>
> 1_mail ~ # nano /data/chroot/dns/etc/bind/pri/adomain-static.eu.zone
> #
OK, this is where you access the file.
[...]
> 2_mail ~ # diff /data/chroot/dns/etc/bind/pri/adomain-static.eu.zone
>
So I tried to dig further...
I requested a full resync of the secondary by issuing drdbadm invalidate r0
on it.
Verified that cat /proc/drbd is showing the resync, waited until finished.
I repeated the above procedure this time by just stopping heartbeat.
Went to the new primary and have a bigger
On Tue, Mar 09, 2010 at 08:35:27AM -0800, avn wrote:
>
> I was not trying to squeeze myself into getting free payed support :).
> Everything shows that the system works fine, but the facts are that is not
> working.
> There is no reason drbd to say that both disks are up-to-date, when they are
> n
I was not trying to squeeze myself into getting free payed support :).
Everything shows that the system works fine, but the facts are that is not
working.
There is no reason drbd to say that both disks are up-to-date, when they are
not.
So i suppose either:
1. There is something broken with drbd o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
I'm just scratching my head about following scenario, and I didn't find
similar setups around the interweb (all the setups out there mention
'the whole stack' from block device/DRBD up to the FS used):
I want to virtualize some machines usin
On Tue, Mar 09, 2010 at 02:47:29AM -0800, avn wrote:
>
> OK,
> You may have a point here.
>
>
> On Tue, Mar 09, 2010 at 01:53:20AM -0800, avn wrote:
> > >> after-sb-0pri discard-younger-primary;
>
> This should be the line with potential danger to new data.
> > >> after-sb-1pri violen
On Tue, Mar 09, 2010 at 07:32:06AM -0800, avn wrote:
>
> Lars,
> I think that we have to separate the issues (or maybe here is my mistake).
> All the configuration issues pointed by you are from my understanding
> related only to what happen only after a split brain is detected/occured.
> And spli
On Tue, Mar 09, 2010 at 11:39:34AM +0100, Olivier LAMBERT wrote:
> Hmmm. I like riddles, so I'm going to google this. Is there any simple
> solutions, in example force drbd to deal with that ?
You need to "force" your application stuff (and, yes, in this context
lvm is an application) do deal with
Lars,
I think that we have to separate the issues (or maybe here is my mistake).
All the configuration issues pointed by you are from my understanding
related only to what happen only after a split brain is detected/occured.
And split brain could occur due to a lot of facts. Yes, since the servers
OK,
You may have a point here.
On Tue, Mar 09, 2010 at 01:53:20AM -0800, avn wrote:
> >> after-sb-0pri discard-younger-primary;
This should be the line with potential danger to new data.
> >> after-sb-1pri violently-as0p;
But I think my situation has nothing to do with it. The primary
Hmmm. I like riddles, so I'm going to google this. Is there any simple
solutions, in example force drbd to deal with that ?
Regards,
Olivier
XO Project
http://xen-orchestra.com
On Tue, Mar 9, 2010 at 11:22 AM, Lars Ellenberg
wrote:
> On Tue, Mar 09, 2010 at 10:59:54AM +0100, Olivier LAMBERT wr
> It just replicates whatever you write to it, no more, no less.
That's why I don't understand why it works fine when LVM clients are
connected on the same DRBD server, and it doesn't work when each
client is on separate DRBD server (despite replication is working).
Can you explain this behaviour
On Tue, Mar 09, 2010 at 01:53:20AM -0800, avn wrote:
> >> after-sb-0pri discard-younger-primary;
> >> after-sb-1pri violently-as0p;
> >> after-sb-2pri violently-as0p;
> >> rr-conflict call-pri-lost;
You configure automatic data loss.
Don't do that, unless you mean it.
--
: La
Hi,
Thanks for reply.
Here is the cat /proc/drbd from both servers in set 1 ( I think that if we
solve one, I will manage to do the second set by myself):
1_mail-Master
version: 8.3.7 (api:88/proto:86-91)
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by r...@1_mail,
2010-03-04 01:20:0
On Tue, Mar 09, 2010 at 10:59:54AM +0100, Olivier LAMBERT wrote:
> I've got your point. I know my first message is long and maybe
> complicated. It seems you "jump" some lines. It's not "nested" LVM as
> described in the doc (because I RTFM before try to ask help).
>
> My problem is not located on
I've got your point. I know my first message is long and maybe
complicated. It seems you "jump" some lines. It's not "nested" LVM as
described in the doc (because I RTFM before try to ask help).
My problem is not located on DRBD hosts. I've run some test, and I can
really simplify the example. Ple
Hey and thanks for reading,
At this moment i have a drbd setup that syncs 2 ssd disks in my server. But
when i unplug a network cable and put it back in the state is unknown of the
second drbd disk. I think i just configured something wrong.. What i want is
this:
When the power or the network die
On Mon, 2010-03-08 at 09:22 -0800, avn wrote:
> Hello,
> I tried to find a solution to my problem, but cannot find one either in the
> forum or google.
> I have 2 sets of 2 boxes each set in HA setup. One set is heartbeat 2.14
> with drbd 8.2.7, the other heartbeat 3.0.2-rc2, pacemaker 1.0.7 and dr
19 matches
Mail list logo
