kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #123349
[Bug 1462530] Re: multipath errors on vivid and wily kernel?
So, just to catch this bug up with where Oleg and I are.
a.) curtin installs multipath-tools-boot into the target with /dev, /proc and /sys mounted. However, it has disabled services from starting through ChrootableTarget's allow_services=False [1]. That uses disable_services_in_root [2].
b.) the way /etc/multipath/bindings is normally created is through the multipath daemon running
So, since we've blocked 'b', we dont get the file created and it doesn't
get collected into the initramfs.
To solve this, we'll need to run a blocking command with no other side effects in the chroot that creates /etc/multipath/bindings. Oleg found that that can be accomplished with /multipath -r'.
sudo sh -c 'rm -Rf /etc/multipath && multipath -r >/dev/null && ls -l /etc/multipath/bindings'
Last thing, a minor point, there is a race condition in the normal
install path that could lead to initramfs not collecting
/etc/multipath/bindings. This is because the daemon is started in the
background, and is not guaranteed to create /etc/multipath/bindings
before update-initramfs is run by the trigger.
--
[1] http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L289
[2] http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L257
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1462530
Title:
multipath errors on vivid and wily kernel?
Status in linux package in Ubuntu:
Confirmed
Bug description:
Oleg and I got changes into curtin to fix bug 1371634.
So that now we can boot into multipath iscsi devices on power.
It seems to go well enough with trusty+hwe-u, but when trying vivid, I am seeing errors.
Boot was failing in one case
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jun 8 16:05 seq
crw-rw---- 1 root audio 116, 33 Jun 8 16:05 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.3-0ubuntu4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.10
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: root=UUID=962acf9e-cd1c-49b0-9264-801271cd510f ro console=hvc0
ProcLoadAvg: 0.08 0.12 0.10 1/1126 3818
ProcLocks:
1: FLOCK ADVISORY WRITE 2951 00:12:14557 0 EOF
2: POSIX ADVISORY WRITE 2952 00:12:43306 0 EOF
3: POSIX ADVISORY WRITE 2905 00:12:22701 0 EOF
4: POSIX ADVISORY WRITE 2965 00:12:18505 0 EOF
ProcSwaps:
Filename Type Size Used Priority
/swap.img file 8388544 0 -1
ProcVersion: Linux version 3.19.0-20-generic (buildd@fisher03) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #20-Ubuntu SMP Fri May 29 10:03:56 UTC 2015
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
RelatedPackageVersions:
linux-restricted-modules-3.19.0-20-generic N/A
linux-backports-modules-3.19.0-20-generic N/A
linux-firmware 1.144
RfKill: Error: [Errno 2] No such file or directory
Tags: wily uec-images
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-20-generic ppc64le
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_dscr: DSCR is 0
cpu_freq:
min: 3.693 GHz (cpu 72)
max: 3.695 GHz (cpu 87)
avg: 3.694 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No firmware implementation of function
cpu_smt: SMT=8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions
References