Ah yes, that helps a lot. So somehow (not sure this is because I am
using the Linux Cluster Management Console for setting up my test
environment or because timing is just in my favour) I seem to avoid this
because the drbd init script already loads the module. So by the time
the pacemaker agent ru
@Stefan, thanks for the reply. It seems my information was not that
clear. Here some more so it is more clear what my problem was.
The problem is with the pacemaker drbd agent:
/usr/lib/ocf/resource.d/linbit/drbd
Here a snippet of this agent:
-
drbd_start() {
local rc
@Jacob, sorry for the long delay. I tried to confirm your report but
could not see any problem (drbd8 version 2:8.4.3-0ubuntu0.12.04.2). Not
sure whether you refer to "eval $(drbdadm --version ...)" in
/etc/init.d/drbd. That could indeed be wrong on start. Though the values
are actually only evalua
I had the same problem and found out that there is a different behaviour
of the drbd agent between just stop and start the drbd resource or
rebooting the system. When you stop drbd, the drbd module stay loaded so
when you start drbd again, the validity check of the agent correctly
detects an 8.3 mo
Hi,
I had same problem during a regular update. The package from
http://people.canonical.com/~smb/lp1185756/ works for me in individual
DRBD config and Pacemaker/Heartbeat env. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I can confirm that solution in #97 (i.e. #71) worked for me as well
(also Pacemaker/Heartbeat).
# uname -a
Linux server 3.5.0-49-generic #74~precise1-Ubuntu SMP Fri May 2 21:32:31 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version : identical
# echo drbd8-utils "hold" | dpkg --set-sele
I was able to fix this by downgrading drbd8-utils as explained in #71,
Pacemaker/heartbeat.
CRM is again UP!
# uname -a
Linux flexfive 3.5.0-48-generic #72~precise1-Ubuntu SMP Tue Mar 11 20:09:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version
DRBD module version: 8.3.13
userland
FTR, my reported bug was triggered by the environment variable
DRBD_DONT_WARN_ON_VERSION_MISMATCH, which was set on my systems.
To work around this bug:
unset DRBD_DONT_WARN_ON_VERSION_MISMATCH
restart pacemaker
(do this before installing drbd8-utils 8.4.3-0ubuntu0.12.04.x)
See also: https://bugs
regression is tracked under bug 1314289
** Description changed:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed as the API between older and newer drbd
Right, thanks Martin. So Thilo, the mysterious question is what is
actually executed. If you manually unpack the rc4 deb:
dpkg -x drbd8-utils_8.4.3-0ubuntu0.12.04.2~rc4_amd64.deb unpack
and compare unpack/usr/lib/ocf/resource.d/linbit/drbd with what is in
/usr/lib/... they should be the same. And
Thanks, Martin, fot the clarification. The ocf::linbit::drbd agent is
(and was) configured, so that's not the source of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd
That really depends on the Pacemaker configuration. If the primitive
DRBD resource uses ocf::heartbeat::drbd, it's the resource agent from
resource-agents, /usr/lib/ocf/resource.d/heartbeat/drbd, which is
ancient and shouldn't be used.
If the primitive, however, uses ocf::linbit::drbd, it's the on
Must admit the two scripts as they are installed on my test system
differ more. Weirdly in your output there was a version check of
++ DRBDADM_VERSION_CODE=0x08030b
++ DRBDADM_VERSION=8.3.11
+ (( 0x08030b >= 0x080302 ))
and that check I cannot find in the heartbeat/drbd script. And the
linbit/d
Thilo, I looked at the debug data you sent me and somehow it seems that
using hearbeat runs a different resource agent. So drbd itself ships a
resource agent in /usr/lib/ocf/resource.d/linbit/drbd but hearbeat uses
another one (.../resource.d/heartbeat/drbd) that comes with a different
package (res
@Thilo,
this is odd. Locally I see the same adjust command but it will get
translated into a drbdadm-83 call which works. Would it be possible for
you to create '/tmp/drbd.ocf.ra.debug', set it to chmod 700 for root and
touch /tmp/drbd.ocf.ra.debug/log as root. Then "service corosync
restart" will
I can confirm that drbd8-utils 2:8.4.3-0ubuntu0.12.04.2~rc4 works fine,
at least for me.
I put one node to standby, installed drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4, did not change drbd.conf, brought node up
again and migrated all resources to that node. Everything is working as
expected:
Mast
I still have problems after upgrading to drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4.
Especially the pacemaker drbd agent does not work
(/usr/lib/ocf/resource.d/linbit/drbd). For example, there is a line
"do_drbdadm $DRBD_TO_PEER -v adjust $DRBD_RESOURCE" which translates to
"drbdadm -c /etc/drbd.con
I hope if I can get someone to sponsor the upload. Of course every
positive feedback about the last version helps me in my argument. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
d
Stefan, thank you for the fixes! Will your version find its way to the
update-repo for 12.04lts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lt
Stefan, your rc4 update seems to have nailed it! My cluster running the
3.2 kernel is now happy. The new fix you used also pleases Ganeti.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
*sigh* Final update, at least this week. With rc4 my code actually does
the right thing. Updated the kernel on one side to a 3.11 one and then
the other side to the new package (keeping the 3.2 kernel there). From
what I can tell, the cluster seems happy with that.
** Patch added: "Debdiff for rc4
Finally figured out the problem with LCMC which maybe also improves
other drbdsetup oddness. The problem is that unlike drbdadm, drbdsetup
did not use the kernel drbd module version to decide whether it should
run the legacy binary. Instead it waited for some socket connection to
fail. But that hap
Updated http://people.canonical.com/~smb/lp1185756/ with packages that
seem to fix normal corosync startup at least. Still not perfect. Migrate
through the LCMC gui might still be a problem. I need to look into that
next. Also if someone knows from the top of their head what the LCMC gui
does to de
** Patch added: "Debdiff for rc2 level."
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/4096314/+files/drbdsetup-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Well yes, there are already plenty of hints in this thread. The problem is that
while having a config option to enable those compat binaries, those do not seem
to be very well tested. I am working on it but its a bit of a mess. I think I
got the ra script in a state now where it seems to work in
I tried the fixed package in comment 60. Unfortunately, the fix did not
completely resolve the problems I had with my Corosync/Pacemaker
cluster.
I also noticed, that I had problems with the new global_common.conf parameters,
that is being installed with drbd-utils 8.4.3:
# service drbd start
*
Hmm, just to clarify: when using the drbd8-utils 8.4 package and the
kernel module 8.3, then drbdsetup execs the drbdsetup-83 compatibility
module which implements the old syntax, and will also if necessary swap
the first two arguments for "forward compatibility"
However there are some commands th
I'm not sure if anyone has mentioned it yet, but the command syntax to
the "drbdsetup" command has changed totally between drbd8-utils 8.3 and
8.4
e.g. if you are using drbd-utils 8.3 then the command is
drbdsetup /dev/drbd0 show
if you are using drbd-utils 8.4 then the command is
drbdsetup show
t quite easy to setup a
> DRBD/Pacemaker cluster.
> http://lcmc.sourceforge.net/
>
> Christoph
>
> - Ursprüngliche Mail -
> > Von: "Stefan Bader"
> > An: cmita...@thomas-krenn.com
> > Gesendet: Donnerstag, 24. April 2014 10:35:01
> > Bet
:01
> Betreff: [Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring
> kernel in 12.04
>
> @Andreas, that particular error is fixed by the test packages (see
> comment #60). There could be one in conjunction with pacemaker which
> reports an error about "
@Andreas, that particular error is fixed by the test packages (see
comment #60). There could be one in conjunction with pacemaker which
reports an error about "drbdadm syncer" not being a valid command.
Unfortunately I don't think anyone who is running a pacemaker cluster
really can afford to help
@Rocco, the problem is that there did not seem to be any sane way to do
a separate package and dependencies. You cannot depend on it in the lts
kernel package because drbd is not a required package. In don't know of
any way in Debian packaging to declare complex relationships like "if
package a get
I also had a problem starting DRBD with my Corosync/Pacemaker cluster
after upgrading drbd8-utils to 8.4.3.
This is a line from the log file where it is failing:
Apr 24 08:21:02 www6a lrmd: [1183]: info: RA output: (p_drbd_r0:0:start:stderr)
Could not connect to 'drbd' generic netlink family
Comm
~# cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 93CE421BB73A731BDC72D8E
~# uname -a
Linux zed1 3.2.0-60-generic #91-Ubuntu
@smb I mean like it states in the header:
But since the new Plans for the LTS-Enablement Stack [1] there should be a
package like drbd8-utils-lts-raring.
@Rocco, that said (and not remembering), could it be that that server
uses a kernel version >3.2.x? What does /proc/drbd say?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils
This was done because later point releases of 12.04 come with newer
kernels and the drbd module in later kernels needed the newer userspace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title
On a side note, I'm not sure why a new package where released for the
raring stack? Is there a really brilliant reason for not having two
different packages?
On 23 Apr 2014 12:06, "Stefan Bader" wrote:
> It is a bit odd. Ok, some warnings seems to be coming from pacemaker
> commands. Like the
> W
It is a bit odd. Ok, some warnings seems to be coming from pacemaker commands.
Like the
WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result (3)
for 0:0:crm-resource-3048
I guess the problem is this:
Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output:
(p_drbd_bigpool:0
got a maintainance-window today and tried
drbd8-utils_8.4.3-0ubuntu0.12.04.2~rc1_amd64.deb which doesnt help the cluster
cause.
attached a cleanup result of one of the drbd resources.
service drbd start still works.
** Attachment added: "error_cluster_drbd.log"
https://bugs.launchpad.net/ubu
@smb I'm afraid I can't. The problem with the upgrade of drbd8-utils
cause downtime on your main (production) DB-cluster today.
I can look though the logs tomorrow, but it was the drbd ocf
master/slave in pacemaker that was failing, causing drbd to get
"unconfigured" on both nodes.
--
You receiv
@Rocco, could you try whether the proposed packages from comment #59
would work? The error message only in the drbdsetup code when it fails
to find the compat binary. So I hope that you will not loose the
connection again. I know it really would suck if not but it would give
higher confidence in ge
The proposed package fixes the issue at my end too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To manage notificat
Linking the /lib/drbd/drbdsetup-8.3 to /sbin did NOT solve the problem
for me. Had to revert to to old packages then everyting worked after
cluster restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
@Stefan, your proposed fix (http://people.canonical.com/~smb/lp1185756/)
worked for me on Precise 64bit with kernel 3.2. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-ut
Proposing to fix this by adding the patch in drbdsetup, too. See attached
debdiff. Test packages can be found at
http://people.canonical.com/~smb/lp1185756/
** Patch added: "Debdiff of proposed fix."
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/4092580/+files/drbds
Anyone seeing the error message, try the proposed package on the
upgraded server. Those are for Precise (12.04) and you will need only
the one matching your installation (64bit or 32bit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also lost my slave on prod system today, pacemaker,crm cluster with
drbd.
lrmd: [1952]: info: RA output: (res_drbd_1:1:monitor:stderr) Could not
connect to 'drbd' generic netlink family
My resources are marked as Unconfigured on slave, but still Primary on
master.
Have not rebooted.
What is the
I would rather fix drbdsetup in the same way drbdadm works (so add the
libpath). That way the compat binaries are not exposed in the normal
search path. Which I believe is intentional as from the user perspective
there should be only one command. I am working on a patch and some test
binaries which
>From my (quick) reading of the source code, drbdadmin works because it adds
>/lib/drbd to the path using add_lib_drbd_to_path(), and drbdsetup seems not to.
One reason for this could be that the driver calls drbdsetup with an abolute
path and the source says "in case drbdsetup is called with an
I can confirm the problem with the netlink error.
Apr 20 11:54:59 node1 lrmd: [3636]: info: RA output:
(res_drbd_1:0:monitor:stderr) Could not connect to 'drbd' generic
netlink family
I'm using 12.04 with 3.2 kernel (3.2.0-60-generic).
The Pacemaker resource agent is also shipped in a new versio
As a workaround verified at my end, you may simply symlink the 8.3 tools
somewhere in the path, so that drbdsetup will find them:
ln -s /lib/drbd/drbdsetup-83 /sbin
Alternatively, you may revert drbd-utils to the 8.3 bersion which is still
available from the "release" repository and freeze i
thx stefan & lionel, will try your suggestions ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To manage notifica
i see no uncommon options in my configs, i built the cluster basically of
linbits dox.
i run a standard pp with no extra repos and did not upgrade to 8.4 whatsoever.
(the updated) node storage0:
root@storage1:~# ssh storage0 cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_COD
Looks very much like drbdsetup does not fall back to the 8.3 version, even
though it should according to this commit:
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=commit;h=b5ef99654f8008a7b6632261f39fc908b4e84210
Anyway, executing /lib/drbd/drbdsetup-83 instead of /sbin/drbdsetup seems to
Hm, ok. So we where only using drbdadm in testing? In theory there is
also a compat version of drbdsetup there and like for drbdadm the
fallback should be drbdsetup-83 (in /lib/drbd) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same symptoms on my kernel 3.2 cluster indeed:
"drbdsetup show all
Could not connect to 'drbd' generic netlink family"
I'm sorry I didn't notice this in my tests - I never use drbdsetup which
is supposed to be a low-level tool.
--
You received this bug notification because you are a
@Thomas, Simon, can you reveal whether there are maybe special options enabled
in the global config or for the resource configs? Both other sides are running
12.04 (Precise) and have not been upgraded, right?
The difference is that Simon did not reboot the upgraded machine but Thomas did
and see
Unfortunatly i had a maintainance-window today and upgraded the first node of
our crm/drbd based storage-cluster today.
everything done and went by the book but after reboot crm didnt have the
(slave) resources back up.
after researching and parsing logs i found this bug here which seems my exact
Yes it should work without rebooting, it's only the userspace side that
is changed.
I never met this problem, even on my kernel-3.2 hosts.
Strange.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118575
On 14-04-17 12:00 PM, Lionel Sausin - Numérigraphe wrote:
> Simon, you shouldn't have to reboot, the utils are compiled with support
> for both 8.3 and 8.4.
I did not reboot nor remove/re-inserted the drbd module. Do you still
expect the new utils to work well in that case? If yes, any idea on ho
Simon, you shouldn't have to reboot, the utils are compiled with support
for both 8.3 and 8.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts
I upgraded to the newer drbd8-utils and didn't reboot after because the
server is in prod ATM. After the upgrade, drbdsetup complains like this:
# drbdsetup show all --show-defaults
Could not connect to 'drbd' generic netlink family
Is there a way around this without reinserting the drbd module
This bug was fixed in the package drbd8 - 2:8.4.3-0ubuntu0.12.04.1
---
drbd8 (2:8.4.3-0ubuntu0.12.04.1) precise; urgency=low
* Backport version from 13.04 so that the utils will handle the
changed in-kernel drbd module from the LTS Raring kernel
(LP: #1185756).
* Activate
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
T
Verified to fix the problem on 1 node in each cluster at our end:
First cluster, Ubuntu 12.04 with Raring kernel, all packages up-to-date except
lxc 0.8.
Uninstalled drbd-8-utils and re-installed from ...-proposed, rebooted.
drbd-overview, drbdadm up|down|disconnect|connect|verify still functiona
Hello Raybuntu, or anyone else affected,
Accepted drbd8 into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/drbd8/2:8.4.3-0ubuntu0.12.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Any word on seeing this package published? This ticket hasn't seen an
update in 4 months. I can confirm that Ubuntu 12.04.3 Server out of the
box on amd64 and i386 will not work with DRDB and requires smb's fixed
debs from #17 and #18 (respectively).
--
You received this bug notification because
Sorry for delay, had another rush to work on. Fix posted in #17 works
fine in my set. Thank you.
mailtest-1:~$ uname -a
Linux mailtest-1 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
mailtest-1:~$ drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:
** Description changed:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed as the API between older and newer drbd kernel modules has changed.
[Fix]
So I did run into the problem mentioned here and installing
drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb fixed that so I validate.
(Glad to in the end be able to contribute something.)
I'm now finally watching /proc/drbd show syncing on this new drbd setup.
--
You received this bug notification
Okay, so my immediate problem was unrelated to this entirely. I didn't
have /etc/hosts setup on them so they simply couldn't find each other.
I'm sorry for cluttering this up. Thanks for indulging a drbd newb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, the problem is back again. I'm not sure why it worked briefly
after a kernel upgrade and now it is impacting my boot up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-util
@flickerfly (josiah-ritchie) : that's strange as I don't see anything in the
changelog for the kernel that might fix this. Which version of drbd8-utils are
you using please ?
Lionel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
There is a package with a proposed fix in comment #17 and #18 and we're
waiting for affected users to test it.
So please do test it and report either success or failure here.
Lionel Sausin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Sorry, I'm replying to the wrong report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To manage notifications about
Solution via kernel upgrade:
I believe I was experiencing this same problem on 12.04.3. I did a dist-
upgrade which install the current lts-raring kernel and rebooted. This
resolved my hangup.
Thank you guys for all the work put into solving this.
--
You received this bug notification because y
Generically, I think that an SRU to get it working with the HWE stack is
reasonable. It will need to be tested with both the original and HWE
stacks, so please update the test procedure to include testing both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Backports might be an option, too. Though then requiring to be aware of
the problem and manually pick the backports version when upgrading to
the LTS Raring kernel. Usability looks to be simpler with a SRU but I
would defer that decision to the SRU team.
--
You received this bug notification beca
** Description changed:
Request for SRU:
[Impact]
- DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed
+ DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
wil
I see your point.
You still have the option to ship the new version as drbd8-utils-lts-raring.
The 8.3 compatibility would still be a bonus for those who downgrade.
Otherwise, maybe you could push it to precise-backports ?
Lionel.
--
You received this bug notification because you are a member o
Thanks Lionel, I will update the SRU description and we will see.
Backporting a much newer version of anything into an older release
always is met with a lot of (justified by experience) reservations. It
probably will need more volunteers to make a case for it (at least
convincing the SRU team that
As to the problem I met on the other cluster, kern.log has no trace of a DRBD
error, so I'm pretty confident it was due to a race condition in my custom
startup plumbing.
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I just did some more testing on the second cluster and I met no problem
at all.
With your package installed, I did the drbd down/apply-al procedure and
downgraded to kernel 3.2. After fixing the config syntax, the resources came
back cleanly without a full-sync. The drbd utils just worked.
At th
Thanks for your care.
I've had a problem on the cluster with drbd 8.3 when the host where your
package was installed.
The power was lost and when it was restored, the drbd resources did not
connect. It may be related to your package or not, I'm unsure.
I reverted to the standard package and broug
Le 27/09/2013 09:34, Stefan Bader a écrit :
> So while upgrading the kernel causes no issues, trying to boot back into an
> old
> kernel will cause a failure to bring up the drbd device. It looked to be
> possible to force it back but then caused a complete re-sync.
The instructions for downgradin
I re-uploaded the Raring debdiff and packages (sorry a bit unclean and
using the same version number again). The only change to the previous
version is the legacy tools version number being bumped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/3851297/+files/drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_i386.deb"
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/3851298/+files/drbd8-utils_8.4.3-0ubuntu0.12.04.1_i386.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment removed: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/3840756/+files/drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb
** Attachment removed: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_i386.deb"
https://bugs.launc
So it seems the version displayed by the tools is coded to be that older
version. The code itself rather looks to be more recent. So I would
rather just tweak the version numbers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
> I think you might have meant to say to 8.3.10.
Yes, sorry I mixed it up.
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kerne
@Numérigraphe,
thanks for the quick testing. To answer the question from #12 first: The
version used by that package depends on the version of the kernel. So
just upgrading kernel to 3.8 (or later) and booting with that kernel
will cause the 8.4 utils part to be used. This unfortunately does some
I plan to upgrade our DRBD 8.3 cluster to 8.4 some time this autumn : should I
expect difficulties using your package, or will the 8.4 tools automatically
become available ?
Lionel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Dear Stefan Bader (smb),
I installed the 64-bits package you posted on 1 node of each cluster and it
worked mostly as expected indeed.
The first cluster has kernel 3.8.
It had tools 8.4.2 installed from the sources. I uninstalled them (make
unsintall was a bit buggy in that version but no mater)
Please note that when using kernel 3.2, the tools have actually been DOWNgraded
from 8.3.11 to 8.3.13 when the "drbd8-utils_8.4.3..." package was installed.
Lionel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Great news.
I have 2 Precise clusters, one has the Raring stack and the other has the
original Precise stack.
I'll give the package a try and let you know.
Please bear with me if that takes a little time.
Lionel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To manage notifications about this bug go to:
http
** Attachment added: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/3840756/+files/drbd8-utils_8.4.3-0ubuntu0.12.04.1_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "drbd8-utils_8.4.3-0ubuntu0.12.04.1_i386.deb"
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/3840757/+files/drbd8-utils_8.4.3-0ubuntu0.12.04.1_i386.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The newer version of the drbd8 utils offer a way to include backwards
compatible versions of drbdadm and drbdsetup. So it seemed possible to backport
that version. There were a few details to add but I think I got a version that
seems to work ok within 12.04/Precise and a 3.2 kernel and after in
1 - 100 of 108 matches
Mail list logo
