/target2:0:3/2:0:3:0/block/sdb
(block)
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you are a member of Ubuntu
= Invalid
So this won't be SRU'd for lucid? Unfortunately, I don't have any affected
machines running natty, and can't upgrade the affected lucid machine(s) to
that release in order to provide feedback.
john
--
John Morrissey _o/\ __o
j...@horde.net
, or
should I check for it in -proposed periodically?
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you
after rule processing
KERNEL - the kernel uevent
[no events generated]
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification
myself.
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
On Wed, Apr 13, 2011 at 03:59:58PM -, Serge Hallyn wrote:
Does fixing the rule to use '-q' fix this bug for you?
Doesn't seem to. Changing the one instance of -Q in
/lib/udev/rules.d/95-kpartx.rules to -q doesn't change the behavior
described in this bug.
john
--
John Morrissey _o
Wasn't sure which /dev paths you were interested in specifically, so
here's ~everything that might be relevant.
We don't run the stock syslog configuration, so I filtered out
multipathd verbose output from our syslogs and attached it; let me know
if you were looking for something more than
I should also note that the errant behavior has changed a little since
we first observed it; events used to be generated constantly, but now
there are large bursts every ~20s.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
What additional information do you need?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
that bug:
#44: John Morrissey wrote on 2010-09-17:
Finally, this modified upstart job requires the fix for
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/639940. Otherwise,
the libvirt-bin pre-stop script isn't guaranteed to finish successfully,
since sendsigs races the child processes
I imagine this is still a problem, since the only update (to the qemu-
kvm or syslinux packages in lucid) since I reported this bug was to fix
an iovec memory leak in qemu-kvm.
I'm not sure if the problem lies in qemu-kvm or in syslinux. What it
boils down to is that newer versions of qemu-kvm
]; then
exit 0
fi
if [ $RUNLEVEL -ne 0 ] [ $RUNLEVEL -ne 6 ]; then
exit 0
fi
--
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net
machines. Maybe the
changed behavior triggers something in the kernel that's causing a panic?
I can't really say without seeing the full panic output.
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net
On Fri, Oct 01, 2010 at 03:47:07AM -, Nathan Crawford wrote:
@John Morrissey - Nice work on getting this working! I hope you don't
mind, I've taken the liberty of packaging all your changes and putting
them in a PPA for easier testing.
Thanks, and packaging the changes is no problem at all
libvirt-bin.conf; let's see if LP accepts
attachments via e-mail.
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
** Attachment added: libvirt-bin.conf
For example, running 'multipath -v0 /dev/sda' while watching 'udevadm
monitor -e' shows one event generated for each path, each time the
multipath command is run. Each even would generate another multipath(8)
invocation.
Looks like the multipath(8) action in 95-multipath.rules is causing an
Looks like this call to multipath(8) in the udev rules was added quite a
while ago. I'm not sure where to go from here; our hardy machines don't
exhibit this behavior, and I'm not sure what's generating the events or
how to break the loop short of commenting out the udev rule action.
0.4.8-14ubuntu4. Sorry, I forgot to mention that.
--
95-kpartx.rules uses invalid -Q argument to modprobe(8)
https://bugs.launchpad.net/bugs/644481
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
--
The attached file updates libvirt-bin's upstart job to gracefully shut
down VMs when the system shuts down. You can alter the shutdown timeout
(SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use
(URIS, default: qemu:///system) in /etc/default/libvirt-bin.
You'll also need the
** Attachment added: omit-kvm-vm-pids
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599117/+files/omit-kvm-vm-pids
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member
@francesco, #46
The packaging is cleaner and easier with the rc script running before sendsigs
(which is also an rc script). That way, the initscripts package/sendsigs
doesn't need to carry around special behavior for libvirt-bin and any other
packages that don't need this type of fix.
--
Er, s/don't need/need/
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Upgrading to a new version of pxelinux fixes this. We had been running
these:
# lenny
PXELINUX 3.71 Debian-2008-09-06 Copyright (C) 1994-2008 H. Peter Anvin
# Ubuntu lucid
PXELINUX 3.63 Debian-2008-07-15
3.86, from Debian squeeze/sid seems to have fixed this.
PXELINUX 3.86 debian-20100418
** Bug watch added: Debian Bug tracker #582434
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582434
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582434
Importance: Unknown
Status: Unknown
--
VNC console doesn't accept keyboard input
Public bug reported:
Binary package hint: qemu-kvm
On lucid, I'm PXE booting a VM.
Keyboard input on the VNC console works fine until PXELinux loads, so I
can answer N to:
Boot from (N)etwork or (Q)uit? N
just fine, but once PXELinux loads, the VNC console ignores all keyboard
input at the
Public bug reported:
Binary package hint: redhat-cluster-suite
I originally discovered this bug in Ubuntu 8.04 LTS. I've also submitted
this as:
https://bugzilla.redhat.com/show_bug.cgi?id=460060
Description of problem:
clustat(8) offers no way of obtaining untruncated columns when its stdout
26 matches
Mail list logo
