This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP provide
Confirmed with systemd 229-4ubuntu21.2 that dev-nbd4p1.device is only
"plugged", after client is running, and all symlinks and partitions
exist.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug noti
** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this
** Branch linked: lp:~xnox/britney/custom-kernels-cannot-pass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this b
Hello Alkis, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notificat
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
With uname -a listing 4.4.0-100-generic #123-Ubuntu I get two change
events, on the parent nbd3 device when connecting nbd export to
/dev/nbd3 with two partitions (nbd3p1 and nbd3p2).
With uname -a listing 4.4.0-98 I do not get such events.
This bug is verified on xenial, will prepate matching sy
Hello, I will retest this with the sru kernel.
The udevadm monitor appears to monitor things that it knows about
thus first one needs to load nbd module, start monitor, unload nbd
module, then proceed with the test case.
I've started validating this on wednesday, but had to travel away from a
I'm the bug reporter, and I have a problem in doing the verification.
a) The initial testcase that I reported happens in both 4.4 unpatched
and 4.10. I.e. the bug that I reported is not yet fixed.
b) Some Ubuntu developer wrote a new testcase as part of doing the SRU.
I cannot reproduce that test
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
https://launchpad.net/ubuntu/+source/linux/4.4.0-100.123
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
w
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notific
@Dimitri, yes I'll submit an SRU request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this bug go to:
https://bu
@jsalisbury that kernel is very nice, could you please cherrypick that
patch and include it in the next available/convenient src:linux SRU?
I have added the SRU template to the bug report.
** Description changed:
+ [Impact]
+ Kernel does not generate any events when ndb-client connects /dev/nbd0
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this bug go to:
https://bugs.launchpad.
I built a Xenial test kernel with a pick of commit 37091fd. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp696435/
To test the kernel, be sure to install both the linux-image and linux-
image-extra .deb packages.
--
You received this bug notification because you
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: Canonical Kernel (canonical-kernel) => Joseph Salisbury
(jsalisbury)
--
You received this bug notif
** Tags added: id-594d1970df3ec53730c0d28c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this bug go to:
https://b
I do not believe I can land the systemd change, unless 4.4 kernel picks
up the above mentioned fix. As otherwise hwe kernels will work, and GA
kernel will not.
** Changed in: systemd (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned)
Checking the issue that was referred shows it was handled and fixed in
1. Kernel
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd
230 which
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
To manage notifications about this bug go to:
https://bugs.launchp
This is still an issue in Ubuntu 16.04, now initramfs-tools
unconditionally calls `wait-for-root /dev/nbd0 10` without even using
ROOTDELAY.
I also reported this bug to https://github.com/yoe/nbd/issues/36.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nbd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-fo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696435
Titl
I think the problem is the missing ID_FS_TYPE in udev for nbd devices,
and that it's also reported more properly there:
https://bugs.freedesktop.org/show_bug.cgi?id=62565
Maybe wait-for-root could find some better workaround when ID_FS_TYPE is
unset though, e.g. checking the output of `blkid`...
Hmmm, maybe this is an easier way to reproduce something similar without
using NBD at all:
wait-for-root /dev/sr0 1
succeeds in a booted system,
but fails from the initramfs if one adds "break=bottom" in the kernel command
line.
It succeeds in both cases for e.g. /dev/sda1.
--
You received th
Yes, it's still an issue in Trusty.
Also please use "Incomplete", not "Invalid" when you need feedback from a bug
reporter.
root@ltsp241:~# blkid
/dev/nbd0: TYPE="squashfs"
/dev/nbd1: UUID="d7bfcbc8-9718-46f9-b9e3-daf9e46f596a" TYPE="swap"
/dev/sr0: LABEL="Ubuntu 10.04.3 LTS i386" TYPE="iso9660
Please reply if this is still an issue on a supported release.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: nbd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
...and yet another workaround, which doesn't hardcode "squashfs", is to
put a local-top/nbd_ltsp script with the following contents:
#!/bin/sh
# Work around LP bug #696435
if [ "$ROOT" = /dev/nbd0 ] && [ -z "$FSTYPE" ]; then
FSTYPE=$(blkid -s TYPE -o value "${ROOT}")
if [ -n "$FSTYPE" ];
Alkis, thank you for your tip. I ended up moving all the infrastructure
to a NFS root based configuration, as I had so many trouble with nbd on
our computing cluster. Since then no more issues :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Nuno: your problem seems unrelated, please file another bug report if
you didn't solve it yet.
I found a much better workaround for the problem. In an initramfs hook,
I put the following code:
# Work around LP bug #696435
mkdir -p ${DESTDIR}/lib/udev/rules.d
cat > ${DESTDIR}/lib/udev/rules.d/60-s
I ran into "nbd0: unknown partition table" with maverick 64bit client and lucid
server. The client doesn't boot:
Negotiation: ..size = 3397924KB
nbd0: unknown partition table
bs=1024, sz=3397924
and then it stops at
exec run-init /root /sbin/init ro
The client machine has two network cards if i
34 matches
Mail list logo