[Bug 1491963] [NEW] preseeding for partman/installation_medium_mounted fails because 'seen' is forced to false
Public bug reported: partman/init.d/30parted always forces 'seen' to 'false' for partman/installation_medium_mounted. This prevents it from being preseeded, as Colin suggests in https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/344976. -- if [ "$part_warn" ]; then db_subst partman/installation_medium_mounted PARTITION "$part_warn" db_fset partman/installation_medium_mounted seen false db_capb align db_input high partman/installation_medium_mounted || true db_go || true db_capb backup align fi -- https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1355845 is the same problem, but for partman/unmount_active. ** Affects: partman-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491963 Title: preseeding for partman/installation_medium_mounted fails because 'seen' is forced to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1491963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
[1308405713.767653] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-2/target3:0:2/3:0:2:0/block/sdc
(block)
UDEV [1308405713.772146] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-3/target3:0:3/3:0:3:0/block/sdd
(block)
UDEV [1308405713.778288] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.0/host2/rport-2:0-3/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
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
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 04:04:46PM -, Martin Pitt wrote:
Accepted multipath-tools into natty-proposed, the package will build now
and be available in a few hours.
[snip]
** Changed in: ubuntu
Status: Confirmed = Invalid
** Changed in: Ubuntu Lucid
Status: Confirmed = 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_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
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
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/644489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 05:15:33PM -, Serge Hallyn wrote:
the bug was also nominated for lucid. The proposed package just hasn't
been accepted (yet) into lucid-proposed, but I've seen no indication
that it was rejected.
Cool. Does the LP bug get notified when it's accepted into -proposed, 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 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
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/644489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 04:04:46PM -, Martin Pitt wrote:
Accepted multipath-tools into natty-proposed, the package will build now
and be available in a few hours.
[snip]
** Changed in: ubuntu
Status: Confirmed = Invalid
** Changed in: Ubuntu Lucid
Status: Confirmed = 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_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/644489/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 05:15:33PM -, Serge Hallyn wrote:
the bug was also nominated for lucid. The proposed package just hasn't
been accepted (yet) into lucid-proposed, but I've seen no indication
that it was rejected.
Cool. Does the LP bug get notified when it's accepted into -proposed, 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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/644489/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote:
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp that should
not generate any more change events for you. Please post
for comparison that this new version returns the same data
as the old one.
[snip]
Once you verify that the updated prio checker no longer
generates change events, start up multipathd again and
verify that this continues to be true. Thanks!
Everything seems to be as anticipated:
[j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get install
multipath-tools=0.4.8-14ubuntu4 multipath-tools-boot=0.4.8-14ubuntu4
kpartx=0.4.8-14ubuntu4
[...]
[j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo
mpath_prio_netapp $i; done
4
1
4
1
[j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get dist-upgrade
[...]
Preparing to replace kpartx 0.4.8-14ubuntu4 (using
.../kpartx_0.4.8-14ubuntu5~lp644489_amd64.deb) ...
[...]
Preparing to replace multipath-tools 0.4.8-14ubuntu4 (using
.../multipath-tools_0.4.8-14ubuntu5~lp644489_amd64.deb) ...
[...]
Preparing to replace multipath-tools-boot 0.4.8-14ubuntu4 (using
.../multipath-tools-boot_0.4.8-14ubuntu5~lp644489_all.deb) ...
[...]
[j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo
mpath_prio_netapp $i; done
4
1
4
1
[j...@pxe-237.roch.ny:pts/0 ~ psg multi
root 30498 30498 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
root 30498 30500 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
root 30498 30514 0.0 0.0 85396 3500 ? SLl dm_wai 13:24
/sbin/multipathd
root 30498 30515 0.0 0.0 85396 3500 ? SLl hrtime 13:24
/sbin/multipathd
root 30498 30516 0.0 0.0 85396 3500 ? SLl skb_re 13:24
/sbin/multipathd
root 30498 30517 0.0 0.0 85396 3500 ? SLl poll_s 13:24
/sbin/multipathd
root 30498 30518 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
[j...@pxe-237.roch.ny:pts/0 ~ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out 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 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
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote:
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp that should
not generate any more change events for you. Please post
for comparison that this new version returns the same data
as the old one.
[snip]
Once you verify that the updated prio checker no longer
generates change events, start up multipathd again and
verify that this continues to be true. Thanks!
Everything seems to be as anticipated:
[j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get install
multipath-tools=0.4.8-14ubuntu4 multipath-tools-boot=0.4.8-14ubuntu4
kpartx=0.4.8-14ubuntu4
[...]
[j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo
mpath_prio_netapp $i; done
4
1
4
1
[j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get dist-upgrade
[...]
Preparing to replace kpartx 0.4.8-14ubuntu4 (using
.../kpartx_0.4.8-14ubuntu5~lp644489_amd64.deb) ...
[...]
Preparing to replace multipath-tools 0.4.8-14ubuntu4 (using
.../multipath-tools_0.4.8-14ubuntu5~lp644489_amd64.deb) ...
[...]
Preparing to replace multipath-tools-boot 0.4.8-14ubuntu4 (using
.../multipath-tools-boot_0.4.8-14ubuntu5~lp644489_all.deb) ...
[...]
[j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo
mpath_prio_netapp $i; done
4
1
4
1
[j...@pxe-237.roch.ny:pts/0 ~ psg multi
root 30498 30498 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
root 30498 30500 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
root 30498 30514 0.0 0.0 85396 3500 ? SLl dm_wai 13:24
/sbin/multipathd
root 30498 30515 0.0 0.0 85396 3500 ? SLl hrtime 13:24
/sbin/multipathd
root 30498 30516 0.0 0.0 85396 3500 ? SLl skb_re 13:24
/sbin/multipathd
root 30498 30517 0.0 0.0 85396 3500 ? SLl poll_s 13:24
/sbin/multipathd
root 30498 30518 0.0 0.0 85396 3500 ? SLl futex_ 13:24
/sbin/multipathd
[j...@pxe-237.roch.ny:pts/0 ~ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out 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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote:
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp
Would you provide a patch to multipath-tools instead, please? I'd be more
comfortable building a patched binary 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 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
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
[1308405713.767653] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-2/target3:0:2/3:0:2:0/block/sdc
(block)
UDEV [1308405713.772146] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-3/target3:0:3/3:0:3:0/block/sdd
(block)
UDEV [1308405713.778288] change
/devices/pci:00/:00:02.0/:07:00.3/:08:01.0/host2/rport-2:0-3/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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote:
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp
Would you provide a patch to multipath-tools instead, please? I'd be more
comfortable building a patched binary myself.
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
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
multipathing
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
Here are the udevd syslogs corresponding to the multipathd verbose logs
in #9.
I also ran udevd with --debug; the debug output is attached and the
corresponding syslogs are far below.
Apr 8 23:10:44 pxe-237 udevd-work[3952]: symlink(../../sda,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 8 23:12:39 pxe-237 udevd-work[16908]: symlink(../../sdb,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 8 23:15:44 pxe-237 udevd-work[6774]:
rename(/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273) failed: No such file or
directory
Apr 8 23:16:20 pxe-237 udevd-work[29981]:
rename(/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273) failed: No such file or
directory
Apr 8 23:16:56 pxe-237 udevd-work[11388]: symlink(../../sdd,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 8 23:16:58 pxe-237 udevd-work[8246]:
rename(/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273) failed: No such file or
directory
Apr 8 23:16:59 pxe-237 udevd-work[8246]: symlink(../../sdb,
/dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 8 23:17:00 pxe-237 udevd-work[8246]:
rename(/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273) failed: No such file or
directory
Apr 12 23:37:59 pxe-237 udevd-work[6391]:
rename(/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273) failed: No such file or
directory
Apr 12 23:37:59 pxe-237 udevd-work[6399]: symlink(../../sdc,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 12 23:37:59 pxe-237 udevd-work[6399]: symlink(../../sdc,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 12 23:37:59 pxe-237 udevd-work[6399]: symlink(../../sdc,
/dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
Apr 12 23:37:59 pxe-237 udevd-work[6395]: symlink(../../sdb,
/dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273.udev-tmp) failed: File
exists
** Attachment added: udevd-debug.gz
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+attachment/2027325/+files/udevd-debug.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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 multipathd's verbose syslogs. [j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/disk/by-id/* /dev/sd*; do echo -n $i ; sudo /sbin/mpath_prio_netapp $i; done /dev/disk/by-id/dm-name-rootvol 4 /dev/disk/by-id/dm-name-rootvol-part1 4 /dev/disk/by-id/dm-name-rootvol-part10 4 /dev/disk/by-id/dm-name-rootvol-part11 4 /dev/disk/by-id/dm-name-rootvol-part12 4 /dev/disk/by-id/dm-name-rootvol-part13 4 /dev/disk/by-id/dm-name-rootvol-part14 4 /dev/disk/by-id/dm-name-rootvol-part15 4 /dev/disk/by-id/dm-name-rootvol-part2 4 /dev/disk/by-id/dm-name-rootvol-part5 4 /dev/disk/by-id/dm-name-rootvol-part6 4 /dev/disk/by-id/dm-name-rootvol-part7 4 /dev/disk/by-id/dm-name-rootvol-part8 4 /dev/disk/by-id/dm-name-rootvol-part9 4 /dev/disk/by-id/dm-uuid-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part1-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part10-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part11-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part12-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part13-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part14-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part15-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part2-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part5-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part6-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part7-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part8-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part9-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part9 4 /dev/disk/by-id/scsi-rootvol 4 /dev/disk/by-id/scsi-rootvol-part1 4 /dev/disk/by-id/scsi-rootvol-part10 4 /dev/disk/by-id/scsi-rootvol-part11 4 /dev/disk/by-id/scsi-rootvol-part12 4 /dev/disk/by-id/scsi-rootvol-part13 4 /dev/disk/by-id/scsi-rootvol-part14 4 /dev/disk/by-id/scsi-rootvol-part15 4 /dev/disk/by-id/scsi-rootvol-part2 4 /dev/disk/by-id/scsi-rootvol-part5 4 /dev/disk/by-id/scsi-rootvol-part6 4 /dev/disk/by-id/scsi-rootvol-part7 4 /dev/disk/by-id/scsi-rootvol-part8 4 /dev/disk/by-id/scsi-rootvol-part9 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part9 4 /dev/sda 4 /dev/sda1 4 /dev/sda10 4 /dev/sda11 4 /dev/sda12 4 /dev/sda13 4 /dev/sda14 4 /dev/sda15 4 /dev/sda2 4 /dev/sda5 4 /dev/sda6 4 /dev/sda7 4 /dev/sda8 4 /dev/sda9 4 /dev/sdb 1 /dev/sdb1 1 /dev/sdb10 1 /dev/sdb11 1 /dev/sdb12 1 /dev/sdb13 1 /dev/sdb14 1 /dev/sdb15 1 /dev/sdb2 1 /dev/sdb5 1 /dev/sdb6 1 /dev/sdb7 1 /dev/sdb8 1 /dev/sdb9 1 /dev/sdc 4 /dev/sdc1 4 /dev/sdc10 4 /dev/sdc11 4 /dev/sdc12 4 /dev/sdc13 4 /dev/sdc14 4 /dev/sdc15 4 /dev/sdc2 4 /dev/sdc5 4 /dev/sdc6 4 /dev/sdc7 4 /dev/sdc8 4 /dev/sdc9 4 /dev/sdd 1 /dev/sdd1 1 /dev/sdd10 1 /dev/sdd11 1 /dev/sdd12 1 /dev/sdd13 1 /dev/sdd14 1 /dev/sdd15 1 /dev/sdd2 1 /dev/sdd5 1 /dev/sdd6 1 /dev/sdd7 1 /dev/sdd8 1 /dev/sdd9 1 **
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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 multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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 multipathd's verbose syslogs. [j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/disk/by-id/* /dev/sd*; do echo -n $i ; sudo /sbin/mpath_prio_netapp $i; done /dev/disk/by-id/dm-name-rootvol 4 /dev/disk/by-id/dm-name-rootvol-part1 4 /dev/disk/by-id/dm-name-rootvol-part10 4 /dev/disk/by-id/dm-name-rootvol-part11 4 /dev/disk/by-id/dm-name-rootvol-part12 4 /dev/disk/by-id/dm-name-rootvol-part13 4 /dev/disk/by-id/dm-name-rootvol-part14 4 /dev/disk/by-id/dm-name-rootvol-part15 4 /dev/disk/by-id/dm-name-rootvol-part2 4 /dev/disk/by-id/dm-name-rootvol-part5 4 /dev/disk/by-id/dm-name-rootvol-part6 4 /dev/disk/by-id/dm-name-rootvol-part7 4 /dev/disk/by-id/dm-name-rootvol-part8 4 /dev/disk/by-id/dm-name-rootvol-part9 4 /dev/disk/by-id/dm-uuid-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part1-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part10-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part11-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part12-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part13-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part14-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part15-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part2-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part5-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part6-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part7-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part8-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part9-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part9 4 /dev/disk/by-id/scsi-rootvol 4 /dev/disk/by-id/scsi-rootvol-part1 4 /dev/disk/by-id/scsi-rootvol-part10 4 /dev/disk/by-id/scsi-rootvol-part11 4 /dev/disk/by-id/scsi-rootvol-part12 4 /dev/disk/by-id/scsi-rootvol-part13 4 /dev/disk/by-id/scsi-rootvol-part14 4 /dev/disk/by-id/scsi-rootvol-part15 4 /dev/disk/by-id/scsi-rootvol-part2 4 /dev/disk/by-id/scsi-rootvol-part5 4 /dev/disk/by-id/scsi-rootvol-part6 4 /dev/disk/by-id/scsi-rootvol-part7 4 /dev/disk/by-id/scsi-rootvol-part8 4 /dev/disk/by-id/scsi-rootvol-part9 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part9 4 /dev/sda 4 /dev/sda1 4 /dev/sda10 4 /dev/sda11 4 /dev/sda12 4 /dev/sda13 4 /dev/sda14 4 /dev/sda15 4 /dev/sda2 4 /dev/sda5 4 /dev/sda6 4 /dev/sda7 4 /dev/sda8 4 /dev/sda9 4 /dev/sdb 1 /dev/sdb1 1 /dev/sdb10 1 /dev/sdb11 1 /dev/sdb12 1 /dev/sdb13 1 /dev/sdb14 1 /dev/sdb15 1 /dev/sdb2 1 /dev/sdb5 1 /dev/sdb6 1 /dev/sdb7 1 /dev/sdb8 1 /dev/sdb9 1 /dev/sdc 4 /dev/sdc1 4 /dev/sdc10 4 /dev/sdc11 4 /dev/sdc12 4 /dev/sdc13 4 /dev/sdc14 4 /dev/sdc15 4 /dev/sdc2 4 /dev/sdc5 4 /dev/sdc6 4 /dev/sdc7 4 /dev/sdc8 4 /dev/sdc9 4 /dev/sdd 1 /dev/sdd1 1 /dev/sdd10 1 /dev/sdd11 1 /dev/sdd12 1 /dev/sdd13 1 /dev/sdd14 1 /dev/sdd15 1 /dev/sdd2 1 /dev/sdd5 1 /dev/sdd6 1 /dev/sdd7 1 /dev/sdd8 1 /dev/sdd9 1 **
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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
multipathing
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
What additional information do you need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644489
Title:
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with
multipathing
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Fri, Mar 18, 2011 at 05:13:55PM -, Lars Hansson wrote: The problem with the upstart solution is that it doesn't work since Upstart will kill the virsh instances that you spawn in shutdown_guests. That's only the case if you don't follow the instructions to patch sendsigs to avoid 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 executed during the course of the job script. 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 is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Fri, Mar 18, 2011 at 05:13:55PM -, Lars Hansson wrote: The problem with the upstart solution is that it doesn't work since Upstart will kill the virsh instances that you spawn in shutdown_guests. That's only the case if you don't follow the instructions to patch sendsigs to avoid 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 executed during the course of the job script. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680248] Re: Random VLAN subinterfacess fail to come up
I should have mentioned that this is with lucid's upstart 0.6.5-7. The Upstart changelogs for 0.6.6 and 0.6.7 and the Ubuntu changelogs for more recent versions (up to 0.6.7-3 in natty) don't contain any obvious fixes for this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680248 Title: Random VLAN subinterfacess fail to come up -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
Removed my PPA (lp546091-lucid-stable) since packaging with this fix has been released. -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680248] [NEW] Random VLAN subinterfacess fail to come up
Public bug reported: Binary package hint: upstart On machines with a fairly large number of VLAN subinterfaces (most of our machines have ~20), a random subset of the configured subinterfaces sometimes fail to come up on boot. Sometimes all interfaces come up correctly, sometimes one or a few subint(s) doesn't come up. Whether any subints fail to come up, how many subints fail, and which subints appears completely random. Verbose output from init(8) is attached. In this example, five subints, bond0.47 through bond0.51, failed to come UP/RUNNING despite upstart declaring that they entered the 'running' state: network-interface (bond0.47) state changed from post-start to running status(8) shows the interface in start/running, but ifconfig(8) shows the subint isn't UP and RUNNING. For example: [...@virt03.ekgv.ca:pts/0 ~ ifconfig bond0.47 bond0.47 Link encap:Ethernet HWaddr e4:1f:13:7b:fa:92 BROADCAST MASTER MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) [...@virt03.ekgv.ca:pts/0 ~ sudo status network-interface INTERFACE=bond0.47 network-interface (bond0.47) start/running Subints that fail to come up are still listed in /var/run/network/ifstate: [...@virt03.ekgv.ca:pts/0 ~ fgrep bond0.47 /var/run/network/ifstate bond0.47=bond0.47 Representative sections of /etc/network/interfaces: auto bond0 iface bond0 inet manual bond-slaves none auto eth0 iface eth0 inet manual bond-master bond0 bond-primary eth0 eth1 auto eth1 iface eth1 inet manual bond-master bond0 bond-primary eth0 eth1 auto bond0.47 iface bond0.47 inet manual auto br10 iface br10 inet manual bridge_ports bond0.47 bridge_maxwait 0 [more subints and bridge interfaces...] Finally, I'm not sure it's relevant to this behavior, but I thought I'd mention it: these VLAN subinterfaces are part of bridge interfaces. All of our bridge interfaces contain only a single interface (the VLAN subint) at boot; KVM VMs are eventually added to these bridge groups. When a VLAN subint fails to come up, so does the corresponding bridge interface: [...@virt03.ekgv.ca:pts/0 ~ sudo status network-interface INTERFACE=br10 status: Unknown instance: br10 [...@virt03.ekgv.ca:pts/0 ~ ifconfig br10 br10: error fetching interface information: Device not found [...@virt03.ekgv.ca:pts/0 ~ fgrep br10 /var/run/network/ifstate br10=br10 ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- Random VLAN subinterfacess fail to come up https://bugs.launchpad.net/bugs/680248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680248] Re: Random VLAN subinterfacess fail to come up
** Attachment added: upstart-verbose-output.txt https://bugs.launchpad.net/bugs/680248/+attachment/1741993/+files/upstart-verbose-output.txt -- Random VLAN subinterfacess fail to come up https://bugs.launchpad.net/bugs/680248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
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 don't work with syslinux 3.86, but I'm not sure what the underlying problem is. Like I said, I looked through the upstream syslinux changelogs and didn't notice any obvious changes that would have fixed this. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
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 don't work with syslinux 3.86, but I'm not sure what the underlying problem is. Like I said, I looked through the upstream syslinux changelogs and didn't notice any obvious changes that would have fixed this. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Thu, Nov 04, 2010 at 11:43:10AM -, Valentijn Sessink wrote: The proposals in this report (mine, John Morrissey's) all have a pre- stop shutdown of virtual machines in their Upstart conf-file. When you update libvirt-bin, dpkg will stop libvirt-bin before upgrading. As a result — if you have implemented the pre-stop shutdown — your virtual machines will all stop. Sorry, that's incorrect. The libvirt-bin upstart job I wrote will only shut down VMs if the physical machine is entering runlevels 0 or 6 (i.e., shutdown or reboot): -- pre-stop script if [ -z $RUNLEVEL ]; 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/__(_)/_(_)/\___(_) /_(_)__ -- 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 kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Thu, Nov 04, 2010 at 11:43:10AM -, Valentijn Sessink wrote: The proposals in this report (mine, John Morrissey's) all have a pre- stop shutdown of virtual machines in their Upstart conf-file. When you update libvirt-bin, dpkg will stop libvirt-bin before upgrading. As a result — if you have implemented the pre-stop shutdown — your virtual machines will all stop. Sorry, that's incorrect. The libvirt-bin upstart job I wrote will only shut down VMs if the physical machine is entering runlevels 0 or 6 (i.e., shutdown or reboot): -- pre-stop script if [ -z $RUNLEVEL ]; 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/__(_)/_(_)/\___(_) /_(_)__ -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
Looks good to me. [...@virt11.roch.ny:pts/0 ~ lspci | grep -i lsi 01:00.0 RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS 9260 (rev 03) [...@virt11.roch.ny:pts/0 ~ uname -a Linux virt11.roch.ny.frontiernet.net 2.6.32-26-server #46-Ubuntu SMP Tue Oct 26 18:03:15 UTC 2010 x86_64 GNU/Linux [...@virt11.roch.ny:pts/0 ~ dpkg -l | fgrep linux-image-2.6.32-26-server ii linux-image-2.6.32-26-server2.6.32-26.46 Linux kernel image for version 2.6.32 on x86 -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
On Tue, Nov 02, 2010 at 09:20:55PM -, Martin Pitt wrote: Does the controller actually work? lspci says nothing about whether there's a driver for it. It's the only thing in the system with storage attached to it, so by virtue of booting... :-) john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Sat, Oct 02, 2010 at 02:54:47AM -, Nathan Crawford wrote: FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the libvirt packaging. I think it already is? (dpkg --status libvirt-bin says it is... but I've been changing things all over the place so I might have confused it) Yes, my fault. debhelper probably adds it as a conffile automatically. Also, are these changes based on Lucid packages? The Lucid machine I'm using for testing has a kernel panic on shutdown with the packages from my PPA installed. Yes, I'm running these changes on a number of lucid 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/__(_)/_(_)/\___(_) /_(_)__ -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Sat, Oct 02, 2010 at 02:54:47AM -, Nathan Crawford wrote: FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the libvirt packaging. I think it already is? (dpkg --status libvirt-bin says it is... but I've been changing things all over the place so I might have confused it) Yes, my fault. debhelper probably adds it as a conffile automatically. Also, are these changes based on Lucid packages? The Lucid machine I'm using for testing has a kernel panic on shutdown with the packages from my PPA installed. Yes, I'm running these changes on a number of lucid 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/__(_)/_(_)/\___(_) /_(_)__ -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639940] Re: sendsigs can kill upstart scripts' child processes prematurely on system shutdown
** Summary changed: - sendsigs can kill upstart scripts' child processes + sendsigs can kill upstart scripts' child processes prematurely on system shutdown -- sendsigs can kill upstart scripts' child processes prematurely on system shutdown https://bugs.launchpad.net/bugs/639940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
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.
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the
libvirt packaging. Also, it might make more sense to package
omit-kvm-vm-pids as part of libvirt instead of a separate package; makes it
harder to forget to install it.
One question on omit-kvm-vm-pids from #51, what does the '##*/' mean
toward the end of line 26?
It's a shell construct that removes text at the beginning of a parameter. In
this case, the net effect is to remove the leading pathname, so all that's
left is the filename ('##' is longest match, and the pattern is '*/'). Since
it's a shell builtin, it's faster than calling basename(1), although speed
is arguably important here. :-)
Looking at it again, that for loop should probably have a guard so it
gracefully handles the case where no QEMU VMs are running:
for pidfile in /var/run/libvirt/qemu/*.pid; do
if [ $pidfile = '/var/run/libvirt/qemu/*.pid' ]; then
break
fi
if ! cp -f $pidfile
/lib/init/rw/sendsigs.omit.d/libvirt-bin-${pidfile##*/}; then
status=1
fi
done
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
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
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
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.
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the
libvirt packaging. Also, it might make more sense to package
omit-kvm-vm-pids as part of libvirt instead of a separate package; makes it
harder to forget to install it.
One question on omit-kvm-vm-pids from #51, what does the '##*/' mean
toward the end of line 26?
It's a shell construct that removes text at the beginning of a parameter. In
this case, the net effect is to remove the leading pathname, so all that's
left is the filename ('##' is longest match, and the pattern is '*/'). Since
it's a shell builtin, it's faster than calling basename(1), although speed
is arguably important here. :-)
Looking at it again, that for loop should probably have a guard so it
gracefully handles the case where no QEMU VMs are running:
for pidfile in /var/run/libvirt/qemu/*.pid; do
if [ $pidfile = '/var/run/libvirt/qemu/*.pid' ]; then
break
fi
if ! cp -f $pidfile
/lib/init/rw/sendsigs.omit.d/libvirt-bin-${pidfile##*/}; then
status=1
fi
done
john
--
John Morrissey _o/\ __o
j...@horde.net_- \_ / \ \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Wed, Sep 22, 2010 at 09:47:47AM -, Valentijn Sessink wrote: - if the shutdown script searches for the word running (like mine does, - but John Morrissey's script is affected, too), it must set LANG=C at the - top, otherwise virsh will run in the local language. Good catch. I've updated 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 https://bugs.launchpad.net/bugs/350936/+attachment/1622533/+files/libvirt-bin.conf ** Attachment added: omit-kvm-vm-pids https://bugs.launchpad.net/bugs/350936/+attachment/1622534/+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 of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Wed, Sep 22, 2010 at 09:47:47AM -, Valentijn Sessink wrote: - if the shutdown script searches for the word running (like mine does, - but John Morrissey's script is affected, too), it must set LANG=C at the - top, otherwise virsh will run in the local language. Good catch. I've updated 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 https://bugs.launchpad.net/bugs/350936/+attachment/1622533/+files/libvirt-bin.conf ** Attachment added: omit-kvm-vm-pids https://bugs.launchpad.net/bugs/350936/+attachment/1622534/+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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 639940] Re: sendsigs can kill upstart scripts' child processes
On Wed, Sep 22, 2010 at 09:23:51AM -, Valentijn Sessink wrote: I might have overlooked it, but I could not find the PID of the sendsigs-revised.sh script itself as an omit PID inside the script. I.e. isn't there a possibility the script kills itself now? Or did I miss something? sendsigs is executed via the upstart 'rc' job, so it will be omitted because of the exception for child processes of upstart jobs. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- sendsigs can kill upstart scripts' child processes https://bugs.launchpad.net/bugs/639940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
Looks good to me. Thanks, Brad. [...@virt11.roch.ny:pts/0 ~ uname -a Linux virt11.roch.ny.frontiernet.net 2.6.32-26-server #45 SMP Wed Sep 22 21:18:52 UTC 2010 x86_64 GNU/Linux [...@virt11.roch.ny:pts/0 ~ lspci | grep -i lsi 01:00.0 RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS 9260 (rev 03) -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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
infinite event loop.
** Package changed: udev (Ubuntu) = multipath-tools (Ubuntu)
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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.
multipath-tools (0.4.8-11) unstable; urgency=low
[...]
* [4f8a5d1] Call multipath via udev on block device add/change events This
helps slow devices when either /etc/init.d/multipath-tools-boot or the
initramfs script are being run although the devices are not ready yet.
(Closes: #489850) - many thanks to Janusz Dziemidowicz for his suggestions
and testing
[...]
-- Guido Guenther a...@sigxcpu.org Wed, 30 Jul 2008 17:59:03 -0400
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644481] Re: 95-kpartx.rules uses invalid -Q argument to modprobe(8)
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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
If anyone else is using the PPA for this bug, I've had to move to: https://launchpad.net/~jwm/+archive/lp546091-lucid-stable since USN-988-1 inserted a package version before the current (unreleased) 2.6.32-25.44 that I had in the PPA. It was just easier/better to switch to a new PPA and track only released kernel packaging. -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644481] [NEW] 95-kpartx.rules uses invalid -Q argument to modprobe(8)
Public bug reported: Binary package hint: multipath-tools 95-kpartx.rules calls modprobe(8) with the invalid -Q argument. I'm guessing it wants -q, for quiet? -- # Always attempt to load dm-multipath. This way we can get rid of the # init script. ACTION==add|change, SUBSYSTEM==block, \ RUN+=/sbin/modprobe -Qba dm-multipath -- udevd debug output: 1285084979.983300 [15293] udev_rules_apply_to_event: RUN '/sbin/modprobe -Qba dm-multipath' /lib/udev/rules.d/95-kpartx.rul es:10 1285084979.984021 [15293] util_run_program: '/sbin/modprobe -Qba dm-multipath' started 1285084979.984499 [15293] util_run_program: '/sbin/modprobe' (stderr) '/sbin/modprobe: invalid option -- 'Q'' 1285084979.984516 [15293] util_run_program: '/sbin/modprobe' (stderr) 'Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d dirname ] [-n] [-i] [-q] [-b] [-o modname] [ --dump-modversions ] modname [parameters...]' 1285084979.984522 [15293] util_run_program: '/sbin/modprobe' (stderr) '/sbin/modprobe -r [-n] [-i] [-v] modulename ...' 1285084979.984524 [15293] util_run_program: '/sbin/modprobe' (stderr) '/sbin/modprobe -l -t dirname [ -a modulename ...]' 1285084979.984578 [15293] util_run_program: '/sbin/modprobe -Qba dm-multipath' returned with exitcode 1 ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] [NEW] constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
Public bug reported:
Binary package hint: udev
udevd constantly changes LUN device node symlinks (devices/LUNs, not the
partition nodes) in /dev/disk/by-id. udevd uses ~15% of CPU and system
time is using ~50-60%.
For example:
[...@syslog01.roch.ny:pts/0 /dev/disk/by-id ls -l
wwn-0x60a98000486e5339576f596675735354 wwn-0x60a98000486e5339576f596675744c36
scsi-360a98000486e5339576f596675735354 scsi-360a98000486e5339576f596675744c36;
sleep 1; echo '=='; ls -l wwn-0x60a98000486e5339576f596675735354
wwn-0x60a98000486e5339576f596675744c36 scsi-360a98000486e5339576f596675735354
scsi-360a98000486e5339576f596675744c36
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
scsi-360a98000486e5339576f596675735354 - ../../sde
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
scsi-360a98000486e5339576f596675744c36 - ../../sdf
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
wwn-0x60a98000486e5339576f596675735354 - ../../sde
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
wwn-0x60a98000486e5339576f596675744c36 - ../../sdf
==
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
scsi-360a98000486e5339576f596675735354 - ../../sdg
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
scsi-360a98000486e5339576f596675744c36 - ../../sdh
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
wwn-0x60a98000486e5339576f596675735354 - ../../sdg
lrwxrwxrwx 1 root root 9 2010-09-21 16:12
wwn-0x60a98000486e5339576f596675744c36 - ../../sdh
All other device nodes stay the same, such as the device nodes for the
partitions:
[...@syslog01.roch.ny:pts/0 /dev/disk/by-id ls -l
scsi-360a98000486e5339576f596675735354-part1; sleep 1; echo '=='; ls -l
scsi-360a98000486e5339576f596675735354-part1
lrwxrwxrwx 1 root root 10 2010-09-21 15:47
scsi-360a98000486e5339576f596675735354-part1 - ../../sdg1
==
lrwxrwxrwx 1 root root 10 2010-09-21 15:47
scsi-360a98000486e5339576f596675735354-part1 - ../../sdg1
I'm not entirely sure whether this is udev's problem or something related to
multipathing. Our most recent experience with multipathing is the last LTS
release (hardy), which doesn't exhibit this behavior given similar
configurations.
[...@syslog01.roch.ny:pts/0 ~ sudo multipath -ll
rootvol (360a98000486e5339576f596675735354) dm-1 NETAPP ,LUN
[size=36G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=8][active]
\_ 2:0:2:0 sda 8:0 [active][ready]
\_ 3:0:2:0 sde 8:64 [active][ready]
\_ round-robin 0 [prio=2][enabled]
\_ 3:0:3:0 sdg 8:96 [active][ready]
\_ 2:0:3:0 sdc 8:32 [active][ready]
syslog-data (360a98000486e5339576f596675744c36) dm-0 NETAPP ,LUN
[size=1.0T][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=8][active]
\_ 2:0:2:1 sdb 8:16 [active][ready]
\_ 3:0:2:1 sdf 8:80 [active][ready]
\_ round-robin 0 [prio=2][enabled]
\_ 3:0:3:1 sdh 8:112 [active][ready]
\_ 2:0:3:1 sdd 8:48 [active][ready]
[...@syslog01.roch.ny:pts/0 ~ cat /etc/multipath.conf
multipaths {
multipath {
wwid360a98000486e5339576f596675735354
alias rootvol
}
multipath {
wwid360a98000486e5339576f596675744c36
alias syslog-data
}
}
devices {
device {
vendor NETAPP
product LUN
path_checkertur
path_grouping_policygroup_by_prio
prio_callout/sbin/mpath_prio_netapp /dev/%n
failbackimmediate
rr_min_io 128
no_path_retry queue
}
}
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
** Attachment added: udev debug output
https://bugs.launchpad.net/bugs/644489/+attachment/1618717/+files/udev-out
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
I should mention that this is with fully up-to-date lucid.
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
It looks like udev is responding to legitimate received events, based on
'udevadm monitor -e'. Commenting out the add|change action in
95-multipath.rules stops the spurious events and returns CPU consumption
to expected levels.
** Attachment added: udevadm monitor -e
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/644489/+attachment/1618827/+files/udevadm-monitor-events
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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
infinite event loop.
** Package changed: udev (Ubuntu) = multipath-tools (Ubuntu)
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
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.
multipath-tools (0.4.8-11) unstable; urgency=low
[...]
* [4f8a5d1] Call multipath via udev on block device add/change events This
helps slow devices when either /etc/init.d/multipath-tools-boot or the
initramfs script are being run although the devices are not ready yet.
(Closes: #489850) - many thanks to Janusz Dziemidowicz for his suggestions
and testing
[...]
-- Guido Guenther a...@sigxcpu.org Wed, 30 Jul 2008 17:59:03 -0400
--
constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing
https://bugs.launchpad.net/bugs/644489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644481] Re: 95-kpartx.rules uses invalid -Q argument to modprobe(8)
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
I can confirm that 879111224d0784eab623fe8130a1f4481e0e1966 and 7bebf5c79cb62766c76c6c1b9c77b86496fd363e (from stable/linux-2.6.32.y.git) are enough to add the necessary support for the SAS2. I pushed my local git repo to http://github.com/jwm/ubuntu-lucid/ if it's useful. -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
On Fri, Sep 17, 2010 at 07:45:02PM -, Steve Conklin wrote: which upstream commit(s) did you cherry pick? Do you have a public git tree with these visible? I cherry picked to bring megaraid_sas up to 00.00.04.17.1-rc1; the commit list is below. I had an IBM x3550 on eval that I wanted to get up quickly, so not all of them are necessary. The big one is 879111224d0784eab623fe8130a1f4481e0e1966, which adds support for the SAS2. I'm not familiar with the SRU requirements, but you could get more selective pretty easily if you have to. I don't have an easy way of making the git repo public right now, but if it's helpful, I can make that happen, just let me know. john 63bad45db1d4e8aafe0633c5741c9720641f336a c978684254d11e3768c5a0b2780302fb0cada29c bdc6fb8d69fab7b4b7f70823e3932bd8e4cfd7db 780a3762fb9208748baac5aa9c63a4d4c9287753 aeab3fd7b865bc4086a80a83cfdd67dded3b41a0 a0b7736828f7615823a7dec680632656d9a9edde 7218df69e3609d1fcf4d83cf8f3fc89dbfbf82a8 0c79e681eef10810a5ed41a2eb1dce244ab1c37d f4c9a1317d32bb0af7546ef0c1dcc3be52dc8d0a 7bebf5c79cb62766c76c6c1b9c77b86496fd363e 044833b572b96afe91506a0edec42efd84ba4939 81e403ce3c6a34cd705bf54d4cdeefdeb7068a8d 879111224d0784eab623fe8130a1f4481e0e1966 72c4fd36dc7f755a5245ef2495fe27d5084d776d c35188377f12e5e0a74f18c3dfdd67baf88db514 8d56825321339f0ef7ad08eb58332e1836881e3b -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
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 omit-kvm-vm-pids init script (attachment forthcoming), which copies the KVM pidfiles to /lib/init/rw/sendsigs.omit.d, preventing /etc/init.d/sendsigs from killing KVM VM processes before the updated libvirt-bin upstart job shuts them down. 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 executed during the course of the job script. With all of these changes, VMs shut down gracefully with the physical host. I would have implemented suspend-on-shutdown (a la the rc script from libvirt 0.8.2), but lucid has an older libvirt that doesn't support 'virsh managedsave'. Shutting down domains gets us *a lot* of the way there, anyway. In fact, I run some largeish KVM hosts, and saving 30-60GB of memory images to disk before shutdown strikes me as less useful than shutting the domains down. sudo service stop libvirt-bin sudo cp libvirt-bin.conf /etc/init/ sudo kill -HUP 1 sudo service start libvirt-bin sudo cp omit-kvm-vm-pids /etc/init.d/ sudo update-rc.d omit-kvm-vm-pids defaults sudo cp -f sendsigs /etc/init.d/ # get fixed sendsigs from LP#639940 ** Attachment added: Stop libvirt VMs gracefully on system shutdown https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599109/+files/libvirt-bin.conf -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
** 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 of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
@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. -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
@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. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
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 omit-kvm-vm-pids init script (attachment forthcoming), which copies the KVM pidfiles to /lib/init/rw/sendsigs.omit.d, preventing /etc/init.d/sendsigs from killing KVM VM processes before the updated libvirt-bin upstart job shuts them down. 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 executed during the course of the job script. With all of these changes, VMs shut down gracefully with the physical host. I would have implemented suspend-on-shutdown (a la the rc script from libvirt 0.8.2), but lucid has an older libvirt that doesn't support 'virsh managedsave'. Shutting down domains gets us *a lot* of the way there, anyway. In fact, I run some largeish KVM hosts, and saving 30-60GB of memory images to disk before shutdown strikes me as less useful than shutting the domains down. sudo service stop libvirt-bin sudo cp libvirt-bin.conf /etc/init/ sudo kill -HUP 1 sudo service start libvirt-bin sudo cp omit-kvm-vm-pids /etc/init.d/ sudo update-rc.d omit-kvm-vm-pids defaults sudo cp -f sendsigs /etc/init.d/ # get fixed sendsigs from LP#639940 ** Attachment added: Stop libvirt VMs gracefully on system shutdown https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599109/+files/libvirt-bin.conf -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
** 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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639940] [NEW] sendsigs can kill upstart scripts' child processes
Public bug reported: Binary package hint: sysvinit sendsigs can kill child processes executed as part of upstart pre/post- stop scripts. It successfully omits upstart processes (daemons and the script processes themselves), but if you use anything other than shell builtins in an upstart job script, those shell-spawned processes don't wind up in OMITPIDS and killall5 kills them. For example, 143 (15/SIGTERM) ends up in /tmp/foo with a script like this. pre-stop script sleep 30 || echo $? /tmp/foo end script Also, the post-SIGTERM loop ends prematurely because killall5 supports a maximum of 16 omitted processes (LP#634460). In my case, the ssh (LP#603363), portmap, statd, and (obviously) rc upstart jobs are still running. Each iteration of the post-SIGTERM loop duplicates these processes in OMITPIDS. On the fifth iteration, the list overflows and killall5 terminates with exitstatus 1. The loop terminates prematurely, since it interprets killall5 failure as an indicator that all SIGTERMed processes have terminated. The attached sendsigs fixes both problems. It won't kill processes that are children of upstart processes. In doing so, it avoids the use of killall5(1), allowing SIGTERMed processes the full ten seconds to shut down gracefully before SIGKILL. If killall5 had parent process checking, using that would be faster, but the fixed omitpid list size would still be a problem. Doing it by hand in the shell is reasonably fast, since there shouldn't be many processes still running. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- sendsigs can kill upstart scripts' child processes https://bugs.launchpad.net/bugs/639940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639940] Re: sendsigs can kill upstart scripts' child processes
** Attachment added: sendsigs-revised.sh https://bugs.launchpad.net/bugs/639940/+attachment/1590506/+files/sendsigs-revised.sh -- sendsigs can kill upstart scripts' child processes https://bugs.launchpad.net/bugs/639940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546091] Re: 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers
The megaraid_sas driver in the current linux-2.6 (stable) git tree has support for this adapter, the LSI SAS2 SKINNY. I've cherrypicked the updated driver into the latest Lucid kernel and uploaded to this PPA: https://launchpad.net/~jwm/+archive/lp546091 (Note that the built kernel is based on the next Lucid kernel update, 2.6.32-24.42. Currently, the only difference between .42 and .41 are some fixes in the i915 graphics driver.) I'll try to keep the PPA kernel up-to-date, but I can't make any guarantees. Also, I'm netbooting to install, so I'm adding the newer scsi-modules udeb to the initrd like so: [...@boost:pts/1 ~ wget -q http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz [...@boost:pts/1 ~ wget -q http://ppa.launchpad.net/jwm/lp546091/ubuntu/pool/main/l/linux/scsi-modules-2.6.32-24-generic-di_2.6.32-24.42+lp546091_amd64.udeb [...@boost:pts/1 ~ mkdir lucid-initrd [...@boost:pts/1 ~ cd lucid-initrd/ [...@boost:pts/1 ~/lucid-initrd gzip -dc ../initrd.gz | sudo cpio -i --make-directories 51151 blocks [...@boost:pts/1 ~/lucid-initrd sudo mv ../scsi-modules-2.6.32-24-generic-di_2.6.32-24.42+lp546091_amd64.udeb . [...@boost:pts/1 ~/lucid-initrd sudo chroot . udpkg -i scsi-modules-2.6.32-24-generic-di_2.6.32-24.42+lp546091_amd64.udeb (Reading database...) (Updating database...) [...@boost:pts/1 ~/lucid-initrd sudo rm scsi-modules-2.6.32-24-generic-di_2.6.32-24.42+lp546091_amd64.udeb [...@boost:pts/1 ~/lucid-initrd sudo find . | sudo cpio -H newc -o | gzip ../initrd.gz-new 63149 blocks -- 10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers https://bugs.launchpad.net/bugs/546091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591739] [NEW] upstart job tries to start rsyslogd when the package is removed but not purged
Public bug reported: Binary package hint: rsyslog rsyslog's upstart job tries to start rsyslogd when the package is removed but not purged (and therefore /usr/sbin/rsyslogd doesn't exist), yielding this error message at boot: init: Failed to spawn rsyslog main process: unable to execute: No such file or directory [...@virt07.roch.ny:pts/0 /var/log dpkg -l rsyslog Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- rc rsyslog4.2.0-2ubuntu8 enhanced multi-threaded syslogd ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: rsyslog - rsyslog's upstart job tries to start rsyslogd even if the package is - purged (and therefore /usr/sbin/rsyslogd doesn't exist), yielding this - error message at boot: + rsyslog's upstart job tries to start rsyslogd when the package is + removed but not purged (and therefore /usr/sbin/rsyslogd doesn't exist), + yielding this error message at boot: init: Failed to spawn rsyslog main process: unable to execute: No such file or directory [...@virt07.roch.ny:pts/0 /var/log dpkg -l rsyslog Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- rc rsyslog4.2.0-2ubuntu8 enhanced multi-threaded syslogd -- upstart job tries to start rsyslogd when the package is removed but not purged https://bugs.launchpad.net/bugs/591739 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
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 Copyright (C) 1994-2010 H. Peter Anvin et al I looked over the syslinux Debian and upstream changelogs, but nothing jumps out at me. Our other hosts run KVM 85 or qemu-kvm 0.11.1+dfsg-1. They had been fine with pxelinux 3.63 or 3.71 (we PXE boot nearly all our new VMs for OS installation). FWIW, they also seem to be fine with 3.86. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
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 Copyright (C) 1994-2010 H. Peter Anvin et al I looked over the syslinux Debian and upstream changelogs, but nothing jumps out at me. Our other hosts run KVM 85 or qemu-kvm 0.11.1+dfsg-1. They had been fine with pxelinux 3.63 or 3.71 (we PXE boot nearly all our new VMs for OS installation). FWIW, they also seem to be fine with 3.86. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
** 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 during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579596] Re: VNC console doesn't accept keyboard input during PXE boot
** 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 during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579596] [NEW] VNC console doesn't accept keyboard input during PXE boot
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 boot: prompt. No matter what keystrokes I hit, nothing happens on the VNC console. Input on PXELinux's *serial* console works fine. I can boot a target and keyboard input on the VNC console works fine when the target boots. What I type on the PXELinux serial console appears in the PXELinux VNC console. Interestingly, if I request a nonexistent boot target on the serial console, the VNC console starts accepting keyboard input. For example: r...@pxe-244:~# virsh console foo Connected to domain foo Escape character is ^] PXELINUX 3.63 Debian-2008-07-15 Copyright (C) 1994-2008 H. Peter Anvin boot: a Could not find kernel image: a boot: The VNC console now accepts keyboard input. I have kvm-pxe installed (obviously, since the VM *does* successfully load PXELinux). I'm not sure how to troubleshoot this further, or even if this is a bug in qemu-kvm proper; this is a strange failure mode. The libvirt domain XML for the VM I'm booting is below. It was created by a local tool, but using virt-manager(1) to create and PXE boot a VM exhibits the same behavior. domain type='kvm' namefoo/name uuidc80f27f4-cf2d-2125-9dd5-ca35855bdf42/uuid memory2097152/memory currentMemory2097152/currentMemory vcpu1/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='network'/ /os features acpi/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' source file='/var/lib/libvirt/images/foo.raw'/ target dev='vda' bus='virtio'/ /disk interface type='bridge' mac address='02:00:00:3d:7c:a5'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target port='0'/ /console input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'/ video model type='cirrus' vram='9216' heads='1'/ /video /devices /domain ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579596] [NEW] VNC console doesn't accept keyboard input during PXE boot
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 boot: prompt. No matter what keystrokes I hit, nothing happens on the VNC console. Input on PXELinux's *serial* console works fine. I can boot a target and keyboard input on the VNC console works fine when the target boots. What I type on the PXELinux serial console appears in the PXELinux VNC console. Interestingly, if I request a nonexistent boot target on the serial console, the VNC console starts accepting keyboard input. For example: r...@pxe-244:~# virsh console foo Connected to domain foo Escape character is ^] PXELINUX 3.63 Debian-2008-07-15 Copyright (C) 1994-2008 H. Peter Anvin boot: a Could not find kernel image: a boot: The VNC console now accepts keyboard input. I have kvm-pxe installed (obviously, since the VM *does* successfully load PXELinux). I'm not sure how to troubleshoot this further, or even if this is a bug in qemu-kvm proper; this is a strange failure mode. The libvirt domain XML for the VM I'm booting is below. It was created by a local tool, but using virt-manager(1) to create and PXE boot a VM exhibits the same behavior. domain type='kvm' namefoo/name uuidc80f27f4-cf2d-2125-9dd5-ca35855bdf42/uuid memory2097152/memory currentMemory2097152/currentMemory vcpu1/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='network'/ /os features acpi/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' source file='/var/lib/libvirt/images/foo.raw'/ target dev='vda' bus='virtio'/ /disk interface type='bridge' mac address='02:00:00:3d:7c:a5'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target port='0'/ /console input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'/ video model type='cirrus' vram='9216' heads='1'/ /video /devices /domain ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315597] [NEW] openoffice.org-hyphenation-en-us postinst depends on update-openoffice-dicts, but the latter may not exist
Public bug reported: The postinst for openoffice.org-hyphenation-en-us invokes update- openoffice-dicts, which is provided by dictionaries-common. Since there is no dependency on openoffice.org-hyphenation-en-us for dictionaries- common, the postinst fails when the latter package is not installed. ** Affects: hyphen (Ubuntu) Importance: Undecided Status: New -- openoffice.org-hyphenation-en-us postinst depends on update-openoffice-dicts, but the latter may not exist https://bugs.launchpad.net/bugs/315597 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] Re: MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
Right, we already happened upon pci=nomsi and have been using that since we first experienced the lockups. Unfortunately, nearly all the nodes we experienced this with were put into production (with pci=nomsi) and we don't have 5T of storage to spare any more. I was able to find one node with 3T of storage and spent some time yesterday trying to reproduce this with the kernel we were running at the time (linux-image-2.6.24-19-server-2.6.24-19.36) and couldn't reproduce the lockups. I'm not sure what to say; we definitely experienced the lockups and pci=nomsi definitely put a stop to them, so I'm puzzled that I wasn't able to reproduce given a couple of hours. Close this if you need to, but I just don't have the time now to pursue further. -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] Re: MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
This was with Ubuntu 8.04 and its stock -server kernel (2.6.24-19-server). As far as we remember, there wasn't anything syslogged. The problem appeared to present as the machines ceasing to service interrupts. Network activity ground to a halt, Ethernet and FC link dropped, all disk I/O blocked. These machines have all of their local filesystems mounted via fibre channel, so there wasn't a chance at that point for them to log much of anything to their syslogs. As far as we remember, there wasn't anything useful in the kernel syslogs and the only log output on the console was the qla driver complaining about the fc link dropping and associated noise. Let me know if there's anything more we can provide. -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] Re: MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
Sorry Leann, I should have been clearer. I was just citing the header on the RHEL5 patch, which I pasted. Here's a copy of their patch, from the latest RHEL5 kernel source RPM. ** Attachment added: linux-2.6-scsi-qla2xxx-msi-x-hardware-issues-on-platforms.patch http://launchpadlibrarian.net/17517070/linux-2.6-scsi-qla2xxx-msi-x-hardware-issues-on-platforms.patch -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] Re: MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
Sigh, I should read the patch before I attach it; correct one coming in a minute... -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] Re: MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
Correct patch (linux-2.6-scsi-qla2xxx-disable-msi-x-by-default.patch). ** Attachment added: linux-2.6-scsi-qla2xxx-disable-msi-x-by-default.patch http://launchpadlibrarian.net/17517188/linux-2.6-scsi-qla2xxx-disable-msi-x-by-default.patch -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268242] [NEW] MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load
Public bug reported: MSI-X support in the qla2xxx driver causes reproducible hangs under moderate I/O load on our BladeCenter HS21 blades with QLogic ISP2422 fibre channel adapters. product: IBM eServer BladeCenter HS21 -[8853GLU]- 08:01.0 Fibre Channel: QLogic Corp. ISP2422-based 4Gb Fibre Channel to PCI-X HBA (rev 02) We first experienced this behavior while mkfs(8)ing a large (5TB) ext3 filesystem on an otherwise unloaded system. The system apparently stops handling interrupts and locks up tight, generally before 50% completion (the exact percentage varies, but it happens every time). Disabling MSI on the kernel command line with 'pci=nomsi' stops the lockups even under much heavier I/O load. FWIW, Red Hat has disabled MSI-X in (at least) RHEL5's kernel. Unfortunately, the Red Hat bug cited in their kernel patch (252410) is not publicly accessible. From kernel-2.6.18-92.1.10.el5.src.rpm's linux-2.6-scsi-qla2xxx-disable- msi-x-by-default.patch: From: Marcus Barrow [EMAIL PROTECTED] Subject: [Bug 252410][QLOGIC 5.1 bug] qla2xxx MSI-X hardware issues on some platforms Date: Wed, 15 Aug 2007 20:22:09 -0400 Bugzilla: 252410 Message-Id: [EMAIL PROTECTED] Changelog: [scsi] qla2xxx: disable MSI-X by default Testing and upstream have found problems handling MSI-X by some chipsets. These include major servers. Enabling MSI-X support has caused a major regression on some machines. This attached patch disable the MSI-X feature by default, but allows enabling with a module parameter ql2x_enable_msix. It basically ammounts to one line, plus 5 lines to declare the module parameter. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- MSI-X support in qla2xxx causes reproducible hangs under moderate I/O load https://bugs.launchpad.net/bugs/268242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105539] Re: can't preseed dash/sh to false
In the meantime, you should (I haven't tested this yet) be able to work around this with a late_command. Something like: d-i preseed/late_command string in-target /var/lib/dpkg/info/dash.postinst Yup, this is basically what we're doing. Our late_command calls a more involved local script, and one of the things it does is 'dpkg- reconfigure dash', which causes the /bin/sh symlink to be set appropriately. -- can't preseed dash/sh to false https://bugs.launchpad.net/bugs/105539 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261274] [NEW] clustat(8) truncates columnar output when stdout is not a TTY
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 is
not a TTY. As a result, it is impossible to obtain untruncated service names
when calling clustat(8) from a script or any situation where its output is
being parsed programmatically.
Version-Release number of selected component (if applicable):
Latest available in RHEL5. The cluster3 master branch at:
http://sources.redhat.com/cluster/wiki/
also exhibits this behavior.
How reproducible:
Always.
From rgmanager/src/utils/clustat.c:
34 int dimx = 80, dimy = 24, stdout_is_tty = 0;
[...]
1103 if (isatty(STDOUT_FILENO)) {
1104 stdout_is_tty = 1;
1105 setupterm((char *) 0, STDOUT_FILENO, (int *) 0);
1106 dimx = tigetnum(cols);
1107 dimy = tigetnum(lines);
1108 }
dimx is initialized to 80 columns. No code other than the above modifies dimx.
Therefore, when the environment variable COLUMNS is set, its value is never
honored when stdout is not going to a TTY. This causes the Service Name column
to be truncated as though the output was being emitted on an 80-column
terminal:
Service Name Owner (Last) State
--- - -- -
service:cl01-svc01.roch.ny.exa (cl01-host01) disabled
service:cl01-svc02.roch.ny.exa (cl01-host02) disabled
service:cl01-svc03.roch.ny.exa cl01-host03started
service:cl01-svc04.roch.ny.exa cl01-host04started
Ideally, columnar data would *never* be truncated when output is not going to a
TTY, so programmatic callers do not have to worry about setting COLUMNS.
** Affects: redhat-cluster-suite (Ubuntu)
Importance: Undecided
Status: New
--
clustat(8) truncates columnar output when stdout is not a TTY
https://bugs.launchpad.net/bugs/261274
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to redhat-cluster-suite in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 261274] [NEW] clustat(8) truncates columnar output when stdout is not a TTY
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 is
not a TTY. As a result, it is impossible to obtain untruncated service names
when calling clustat(8) from a script or any situation where its output is
being parsed programmatically.
Version-Release number of selected component (if applicable):
Latest available in RHEL5. The cluster3 master branch at:
http://sources.redhat.com/cluster/wiki/
also exhibits this behavior.
How reproducible:
Always.
From rgmanager/src/utils/clustat.c:
34 int dimx = 80, dimy = 24, stdout_is_tty = 0;
[...]
1103 if (isatty(STDOUT_FILENO)) {
1104 stdout_is_tty = 1;
1105 setupterm((char *) 0, STDOUT_FILENO, (int *) 0);
1106 dimx = tigetnum(cols);
1107 dimy = tigetnum(lines);
1108 }
dimx is initialized to 80 columns. No code other than the above modifies dimx.
Therefore, when the environment variable COLUMNS is set, its value is never
honored when stdout is not going to a TTY. This causes the Service Name column
to be truncated as though the output was being emitted on an 80-column
terminal:
Service Name Owner (Last) State
--- - -- -
service:cl01-svc01.roch.ny.exa (cl01-host01) disabled
service:cl01-svc02.roch.ny.exa (cl01-host02) disabled
service:cl01-svc03.roch.ny.exa cl01-host03started
service:cl01-svc04.roch.ny.exa cl01-host04started
Ideally, columnar data would *never* be truncated when output is not going to a
TTY, so programmatic callers do not have to worry about setting COLUMNS.
** Affects: redhat-cluster-suite (Ubuntu)
Importance: Undecided
Status: New
--
clustat(8) truncates columnar output when stdout is not a TTY
https://bugs.launchpad.net/bugs/261274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105539] Re: can't preseed dash/sh to false
This also affects hardy (8.04 LTS). -- can't preseed dash/sh to false https://bugs.launchpad.net/bugs/105539 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109788] vpnc-script assumes /sbin/ is in its path
Public bug reported: Binary package hint: vpnc vpnc(8) assumes /sbin/ is in its path. When it's not, calls to ifconfig(8) fail and the tunnel does not come up, although vpnc continues to run. This patch fixes this: --- vpnc-script.orig2007-04-24 19:21:40.0 -0400 +++ vpnc-script 2007-04-24 19:21:29.0 -0400 @@ -39,6 +39,8 @@ mkdir -p /var/run/vpnc fi +export PATH=$PATH:/sbin + # stupid SunOS: no blubber in /usr/local/bin ... (on stdout) IPROUTE=`which ip | grep '^/' 2 /dev/null` ** Affects: vpnc (Ubuntu) Importance: Undecided Status: Unconfirmed -- vpnc-script assumes /sbin/ is in its path https://bugs.launchpad.net/bugs/109788 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105539] can't preseed dash/sh to false
Public bug reported: Binary package hint: dash It seems impossible to preseed dash/sh to false. I'm doing a netboot install with a preseed file fetched from an HTTP server. In the preseed, I have: dash dash/sh boolean false I'm not sure what difference it makes, but I've also tried: d-i dash/sh boolean false as well as preseeding dash/sh on the kernel command line. The installer (outside of the /target chroot) seems to pick up on the preseeded value right away; from VC 2 as soon as the installer has started up: ~ # debconf-get dash/sh false However, the target installation has the value 'true' during the debootstrap(8) phase: ~ # chroot /target/ # debconf-show dash dash/sh: true /target/var/cache/debconf/config.dat during debootstrapping says: Name: dash/sh Template: dash/sh Value: true Owners: dash After the target installation has been bootstrapped, the debconf configuration finally contains the preseeded value: Name: dash/sh Template: dash/sh Value: false Owners: dash Flags: seen However, dash has already been unpacked and configured during the debootstrap: Apr 10 14:40:44 debootstrap: Selecting previously deselected package dash. Apr 10 14:40:44 debootstrap: Unpacking dash (from .../dash_0.5.3-5ubuntu2_i386.deb) ... [...] Apr 10 14:41:13 debootstrap: Setting up dash (0.5.3-5ubuntu2) ... Apr 10 14:41:13 debootstrap: Adding `diversion of /bin/sh to /bin/sh.distrib by dash' Apr 10 14:41:13 debootstrap: Adding `diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' and therefore can't pick up on this preseeded value. Given this behavior, it seems like it isn't possible to preseed debconf settings for packages installed during the bootstrap (Priority: required)? ** Affects: dash (Ubuntu) Importance: Undecided Status: Unconfirmed -- can't preseed dash/sh to false https://bugs.launchpad.net/bugs/105539 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94126] preseed docs incorrectly state devfs support
Public bug reported: The installation guide at: https://help.ubuntu.com/6.10/ubuntu/installation-guide/example- preseed.txt incorrectly (AFAICT) states devfs paths are supported: # Alternatively, you can specify a disk to partition. The device name can # be given in either devfs or traditional non-devfs format. It seems the NoMoreDevfs spec: https://blueprints.launchpad.net/ubuntu/+spec/no-more-devfs https://wiki.ubuntu.com/NoMoreDevfs was implemented before edgy's release. In fact, I tried preseeding an edgy installation with a devfs path, which failed. ** Affects: installation-guide (Ubuntu) Importance: Undecided Status: Unconfirmed -- preseed docs incorrectly state devfs support https://launchpad.net/bugs/94126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
