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
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
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 it
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
Linbit's Lars Ellenberg confirmed on the ML that adding /lib/drbd to the
path won't fix drbdsetup in all cases: drbdsetup-83 has to be in the
same directory as the drbdsetup, and it also applies to drbdadmin.
On Tue, Apr 22, 2014 at 01:56:16PM +0200, Lionel Sausin wrote:
(...)
Is the correct
The proposed package fixes the issue at my end too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To
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
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not
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
Server Team, which is subscribed to drbd8 in Ubuntu.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring
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
Sorry, I'm replying to the wrong report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To manage
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
Server Team, which is
*** This bug is a duplicate of bug 1185756 ***
https://bugs.launchpad.net/bugs/1185756
This is a duplicate bug, you won't get any help here.
The issue is being resolved here :
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756
There is a proposed fix in comment #17 #18, please
@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
Server Team, which is subscribed to
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
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
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
Server Team, which is subscribed to drbd8
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
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 downgrading
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
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with
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
Server
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
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
Server Team, which is subscribed to drbd8 in Ubuntu.
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
Server Team, which is subscribed to
** Changed in: drbd8 (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring
*** This bug is a duplicate of bug 1185756 ***
https://bugs.launchpad.net/bugs/1185756
** This bug has been marked a duplicate of bug 1185756
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
--
You received this bug notification because you are a member of Ubuntu
Server
** 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
+ [Test Case]
+ Install the Raring kernel in Precise, install/configure DRBD:
Would someone from the Bug Control Team please consider this as a
request for SRU?
If this cannot be fixed as an SRU, at least it should be documented in
the Release Notes for 12.04.3 server, and affected users should be
advised to downgrade to the Quantal stack.
Lionel Sausin.
--
You received
Public bug reported:
Ubuntu 12.04.3 is due in august and, as part of the LTS Enablement Stack
program, it will ship with Raring's kernel 3.8
This new kernel includes DRBD v8.4.2, but the DRBD utils shipped in Precise are
version 8.3.11. They will not work with the new kernel: please check Bug
** Description changed:
+ [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
+ [Test Case] install the Raring kernel in Precise, install/configure DRBD: you
get No response from
Would someone from the Ubuntu Bug Control Team please consider this bug as an
SRU request for Ubuntu 12.04.3LTS ?
Lionel Sausin.
** Summary changed:
- Please package drbd tools v8.4 for use with Precice LTS Enablement Stacks
+ Please package drbd tools v8.4 for use with Raring LTS Enablement
Dear Robie Basak,
I made a quick test and it just worked on a fresh install of raring
with drbd8-tools 2:8.4.3-0ubuntu1~ppa2 from your PPA.
Thanks,
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
Thanks for your care. I'll give the packages a try.
I guess any 8.4.x version would be OK.
However I don't expect the DRBD module to be upgraded in Raring because they
are in the mainline kernel now. Linux 3.8 has DRBD 8.4.2, so you might as well
ship the same drbdadm version.
Lionel
--
You
Dear Robie Basak,
I made but a quick test, but the tools provided by your PPA's package worked
fine.
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1132302
Title:
Public bug reported:
Ubuntu Raring is going to ship with kernel 3.8, which contains DRBD v8.4.2
Unfortunately, the userland tools in drbd8-utils are still v8.3.13, which is 1
major version behind: they are not compatible with the kernel module.
From my testing (both in a vmware environment and
What you lack is the DRBD feature to auto-promote one node at startup :
http://www.drbd.org/users-guide-9.0/s-recent-changes-auto-promote.html
This is a new feature in the current beta DRBD.
Ubuntu shouldn't bother at least until DRBD 9.0 hits the mainline kernel.
--
You received this bug
Sorry, I meant OK to use drbdadm 8.3.11 with module 8.3.13 of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1103656
Title:
Update Precise drbd8-utils to 8.3.13 for the
As discussed in Debian[1], it's OK to use drbdadm 8.3.11 with module
3.8.13, and This warning can be silenced if you set the following
environment variable: DRBD_DONT_WARN_ON_VERSION_MISMATCH
The only downside I know of is you won't have access to the newest
command-line options. Reading the
By bad, this is fixed in Precise too thanks to the backported kernel.
Lionel.
** Changed in: drbd8 (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
This will be fixed in raring, because kernel 3.8 includes DRBD v8.4.2.
It's still a problem for Precise LTS though.
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/912254
Title:
Sorry to get back with this again, but a flaw was found that may cause data
loss and was fixed only in 8.3.13.
http://lists.linbit.com/pipermail/drbd-announce/2012-May/000169.html
Of course, the problem is in the kernel module, not the userspace tools, so I
guess it's the kernel package that
DRBD was upgraded to 8.3.13 in Quantal, and from your latest comment I gather
that a SRU is not something we can consider.
So maybe this bug should be marked won't fix ?
Lionel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in
Isn't this a duplicate of #483410 ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/858644
Title:
DRBD Linux Headers Required
To manage notifications about this bug go to:
Public bug reported:
DRBD 8.3.12 was published recently and makes DRBD more robust in the face of a
network or storage failure.
Furthermore, DRBD 8.3.12 will probably be the last 8.3.x revision, because 8.4
is out.
I think that makes it a good candidate for inclusion in the upcoming LTS, so
Public bug reported:
The script /usr/lib/drbd/snapshot-resync-target-lvm.sh shipped with drbd
v8.3.7 in Lucid fails to read its command line options and falls into an
infinite loop.
This bug is not in present in natty, but I humbly request an SRU to
Lucid.
This script can be called by DRBD to
Public bug reported:
Binary package hint: tgt
Th init job currently packaged for natty does not let tgtd be respawned
whenever it fails or is killed.
I humbly suggest you add a respawn stanza to /etc/init/tgt.conf
Lionel Sausin
** Affects: tgt (Ubuntu)
Importance: Undecided
For your information, a similar bug was introduced in the Lucid cycle and then
fixed again in Maverick.
In Lucid thhe default-start and default-sop are empty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in ubuntu.
Dear SRU team, please would you care to push the fix to Lucid? Being an
LTS, I think it's worth it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in ubuntu.
https://bugs.launchpad.net/bugs/282876
Title:
drbd doesn't start on
48 matches
Mail list logo
