drbd not working after kernel upgrade 5.0.x -> 5.3.x
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
drbd-utils (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Rafael David Tinoco |
Bug Description
[Impact]
* One can't manage drbd resources through drbdadm command after kernel has been upgraded to 5.3 (latest HWE kernel).
[Test Case]
$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
$ sudo losetup --find --show /.loop
/dev/loop0
$ cat /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
}
net {
}
on drbdfix {
}
on drbdnon {
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* Very minor in this case as it adds a single flag to nla_put() attribute argument.
* Based in upstream patch fixing the issue, test case is fixed.
* [racb] Older kernels still supported in affected Ubuntu releases may not understand the new flag, causing unexpected failure or other unexpected behaviour. #ifndef doesn't mitigate this since the new flag constant would be available at build time (we only build one src:drbd-utils for all kernels and don't ship a different set of binary packages per kernel).
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://<email address hidden>
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSign
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-
libstdc++6 8.3.0-6ubuntu1~
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
Related branches
- Rafael David Tinoco (community): Approve
- Christian Ehrhardt (community): Needs Fixing
-
Diff: 87 lines (+53/-1)4 files modifieddebian/changelog (+7/-0)
debian/control (+2/-1)
debian/patches/lp1866458-add-NLA_F_NESTED-flag.patch (+43/-0)
debian/patches/series (+1/-0)
Changed in drbd-utils (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
tags: | added: server-next |
description: | updated |
Changed in drbd-utils (Ubuntu): | |
status: | Confirmed → In Progress |
status: | In Progress → Fix Released |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
importance: | Medium → Undecided |
Changed in drbd-utils (Ubuntu Bionic): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
description: | updated |
description: | updated |
drbd-utils_ 9.5.0-1_ amd64.deb does not work either..