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" <email address hidden> wrote:

> 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:start:stderr) drbdadm: Unknown command 'syncer'
> Apr 22 21:55:43 storage0 drbd[3079]: ERROR: bigpool: Called drbdadm -c
> /etc/drbd.conf syncer bigpool
>
> This would mean that drbdadm did not pass control on drbdadm-83. And
> that would only happen if the current version did not seem to be 8.3.
> That version number looks to be read from /proc/drbd and would reflect
> the version of the kernel module.  At least as long as reading from
> /proc/drbd is not failing. Then it would fall back to a version number
> defined in the command (which would be wrong). Would have been
> interesting to find out whether calling "drbdadm syncer bigpool"
> manually would fail the same way but that would need another maintenance
> window. Maybe try to see what /proc/drbd is showing.
>
> I probably would suggest that we open a new bug report for the cluster
> case, so this one can be closed with the fix to drbdsetup. Then at least
> the direct usage seems to work.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1185756
>
> Title:
>   drbd8-utils not compatible with linux-lts-raring kernel in 12.04
>
> Status in “drbd8” package in Ubuntu:
>   Invalid
> Status in “drbd8” source package in Precise:
>   Fix Released
>
> Bug description:
>   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]
>   The current version of drbd8 utils in Saucy/Raring can be compiled with
> legacy utils enabled (basically drbdadm and drbdsetup) and automatically
> switches to use the legacy version when an older kernel module is found.
> Comparing the code of those two legacy tools showed them to be mostly the
> same (except some things that actually look like bug fixes).
>   I only found two small issues, one was the init.d script which was
> changed to use a new command of drbdadm to activate resources. This would
> fail if drbdadm fell back to the legacy version. So I picked the shell
> function that the current util uses and verified that this still works with
> the new binary.
>   The other problem was the default config file which contained a new open
> which would cause the legacy util to fail. It does not seem to be a
> required one in the new tools to commenting it out by default seems to work
> in both cases, too.
>   Lastly (this did not seem to be a real issue) the legacy tools claimed
> to be a version 3.8.10 while the the code really looked like the 3.8.11
> version we have in Precise. Since that also matches the version number of
> the drbd module in Precise I modified the legacy tools version to be 3.8.11.
>
>   [Test Case]
>   For testing compatibility with the Precise 3.2 based kernels, either
> just install the prepared package and verify everything still works as
> before (before installing any HWE kernel). Or if already having installed a
> HWE kernel and experiencing the issue, boot into the 3.2 kernel before
> installing the proposed package (or follow the downgrade instructions
> before booting back).
>
>   To test functionality with HWE kernels, install the Raring kernel in
>   Precise, install/configure DRBD: you get "No response from the DRBD
>   driver! Is the module loaded?". With the proposed backport the mirror
>   continues to work. Only for switching back to an older kernel a
>   special procedure must be followed (see comment #21):
>
>   http://www.drbd.org/users-guide/s-downgrading-drbd84.html
>
>   ---
>
>   I've just installed linux-generic-lts-raring on 12.04.2 and my drbd
> device stoped working.
>   Seems like drbd8-utils is not compatible with DRBD 8.4 in Kernel 3.8.
>   I see that we can't upgrade the package since this would break
> compatibility with the older Kernels in Precise.
>
>   But since the new Plans for the LTS-Enablement Stack [1] there should
>   be a package like drbd8-utils-lts-raring. And the dependancies should
>   be resolved automatically with apt.
>
>   kind regards
>
>   [1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: linux-image-3.8.0-22-generic 3.8.0-22.33~precise1
>   ProcVersionSignature: Ubuntu 3.8.0-22.33~precise1-generic 3.8.11
>   Uname: Linux 3.8.0-22-generic x86_64
>   ApportVersion: 2.0.1-0ubuntu17.2
>   Architecture: amd64
>   Date: Thu May 30 11:53:13 2013
>   InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" -
> Release amd64 (20120817.3)
>   MarkForUpload: True
>   SourcePackage: linux-lts-raring
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions
>