Your message dated Fri, 16 Jan 2009 19:12:56 +0000
with message-id <[email protected]>
and subject line Re: Bug#512041: linux-image-2.6.26-1-powerpc64: Multiple
bonding devices aren't configured
has caused the Debian Bug report #512041,
regarding linux-image-2.6.26-1-powerpc64: Multiple bonding devices aren't
configured
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
512041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512041
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: linux-image-2.6.26-1-powerpc64: Multiple bonding devices aren't
configured
Package: linux-image-2.6.26-1-powerpc64
Version: 2.6.26-13
Severity: normal
*** Please type your report below this line ***
Hello,
with the following configuration (resolution from BugID: 439007) only
the first ethernet bonding device (bond0) of several gets configured:
# cat /etc/modprobe.d/aliases
[...]
alias bond0 bonding
options bond0 mode=active-backup miimon=100 downdelay=200 updelay=200
max_bonds=4
alias bond1 bonding
options bond1 mode=active-backup miimon=100 downdelay=200 updelay=200
alias bond2 bonding
options bond2 mode=active-backup miimon=100 downdelay=200 updelay=200
alias bond3 bonding
options bond3 mode=active-backup miimon=100 downdelay=200 updelay=200
# lsmod | grep bond
bonding 123512 0
All other devices (bond1, bond2, bond3) are ignored. If manually configured
with:
# modprobe -o bond1 bonding mode=active-backup miimon=100 downdelay=200
updelay=200
# modprobe -o bond2 bonding mode=active-backup miimon=100 downdelay=200
updelay=200
# modprobe -o bond3 bonding mode=active-backup miimon=100 downdelay=200
updelay=200
# lsmod | grep bond
bonding 123512 0
bond1 123512 0
bond2 123512 0
bond3 123512 0
the additional bonding interfaces work fine. So i guess the problem is
with parsing the config files or passing the options (e.g. "-o") to the
init-tools.
If not the above, what would be the correct way to configure multiple
bonding interfaces?
Regards,
Frank
-- Package-specific info:
** Version:
Linux version 2.6.26-1-powerpc64 (Debian 2.6.26-13) ([email protected]) (gcc
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10
14:42:07 CET 2009
** Command line:
root=/dev/mapper/mpath0-part2 ro
** Not tainted
** Kernel log:
[ 1.307486] io scheduler deadline registered
[ 1.307538] io scheduler cfq registered (default)
[ 1.315074] vio_register_driver: driver hvc_console registering
[ 1.315964] HVSI: registered 0 devices
[ 1.315973] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
[ 1.316640] pmac_zilog: 0.6 (Benjamin Herrenschmidt
<[email protected]>)
[ 1.320235] brd: module loaded
[ 1.320498] input: Macintosh mouse button emulation as /class/input/input0
[ 1.320632] Uniform Multi-Platform E-IDE driver
[ 1.320642] ide: Assuming 50MHz system bus speed for PIO modes; override
with idebus=xx
[ 1.321079] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI)
Driver
[ 1.345095] mice: PS/2 mouse device common for all mice
[ 1.345407] platform ppc-rtc.0: rtc core: registered ppc_md as rtc0
[ 1.346272] TCP cubic registered
[ 1.346282] NET: Registered protocol family 17
[ 1.346614] registered taskstats version 1
[ 1.346760] platform ppc-rtc.0: setting system clock to 2009-01-16 14:57:19
UTC (1232117839)
[ 1.346846] Freeing unused kernel memory: 296k freed
[ 1.978123] SCSI subsystem initialized
[ 2.014627] vio_register_driver: driver ibmvscsi registering
[ 2.014737] ibmvscsi 30000002: SRP_VERSION: 16.a
[ 2.014859] scsi0 : IBM POWER Virtual SCSI Adapter 1.5.8
[ 2.015099] ibmvscsi 30000002: partner initialization complete
[ 2.015116] ibmvscsi 30000002: sent SRP login
[ 2.015189] ibmvscsi 30000002: SRP_LOGIN succeeded
[ 2.015242] ibmvscsi 30000002: host srp version: 16.a, host partition 01 -
s6521 - VIOS1 (1), OS 3, max io 262144
[ 2.033414] ibmvscsi 30000003: SRP_VERSION: 16.a
[ 2.033537] scsi1 : IBM POWER Virtual SCSI Adapter 1.5.8
[ 2.033696] ibmvscsi 30000003: partner initialization complete
[ 2.033707] ibmvscsi 30000003: sent SRP login
[ 2.033783] ibmvscsi 30000003: SRP_LOGIN succeeded
[ 2.033839] ibmvscsi 30000003: host srp version: 16.a, host partition 02 -
s6522 - VIOS2 (2), OS 3, max io 262144
[ 2.034584] scsi 0:0:2:0: Direct-Access AIX VDASD 0001
PQ: 0 ANSI: 3
[ 2.034808] scsi 0:0:3:0: CD-ROM AIX VOPTA
PQ: 0 ANSI: 4
[ 2.050417] scsi 1:0:1:0: Direct-Access AIX VDASD 0001
PQ: 0 ANSI: 3
[ 2.123896] Driver 'sd' needs updating - please use bus_type methods
[ 2.124145] sd 0:0:2:0: [sda] 75497472 512-byte hardware sectors (38655 MB)
[ 2.124230] sd 0:0:2:0: [sda] Write Protect is off
[ 2.124239] sd 0:0:2:0: [sda] Mode Sense: 2f 00 00 08
[ 2.124318] sd 0:0:2:0: [sda] Cache data unavailable
[ 2.124328] sd 0:0:2:0: [sda] Assuming drive cache: write through
[ 2.124488] sd 0:0:2:0: [sda] 75497472 512-byte hardware sectors (38655 MB)
[ 2.124543] sd 0:0:2:0: [sda] Write Protect is off
[ 2.124553] sd 0:0:2:0: [sda] Mode Sense: 2f 00 00 08
[ 2.124604] sd 0:0:2:0: [sda] Cache data unavailable
[ 2.124614] sd 0:0:2:0: [sda] Assuming drive cache: write through
[ 2.124625] sda: sda1 sda2 sda3
[ 2.125104] sd 0:0:2:0: [sda] Attached SCSI disk
[ 2.125298] sd 1:0:1:0: [sdb] 75497472 512-byte hardware sectors (38655 MB)
[ 2.125366] sd 1:0:1:0: [sdb] Write Protect is off
[ 2.125376] sd 1:0:1:0: [sdb] Mode Sense: 2f 00 00 08
[ 2.125435] sd 1:0:1:0: [sdb] Cache data unavailable
[ 2.125445] sd 1:0:1:0: [sdb] Assuming drive cache: write through
[ 2.125605] sd 1:0:1:0: [sdb] 75497472 512-byte hardware sectors (38655 MB)
[ 2.125670] sd 1:0:1:0: [sdb] Write Protect is off
[ 2.125681] sd 1:0:1:0: [sdb] Mode Sense: 2f 00 00 08
[ 2.125742] sd 1:0:1:0: [sdb] Cache data unavailable
[ 2.125752] sd 1:0:1:0: [sdb] Assuming drive cache: write through
[ 2.125761] sdb: sdb1 sdb2 sdb3
[ 2.126371] sd 1:0:1:0: [sdb] Attached SCSI disk
[ 2.163465] Driver 'sr' needs updating - please use bus_type methods
[ 2.163629] sr0: scsi-1 drive
[ 2.163638] Uniform CD-ROM driver Revision: 3.20
[ 2.163747] sr 0:0:3:0: Attached scsi CD-ROM sr0
[ 2.190383] sd 0:0:2:0: Attached scsi generic sg0 type 0
[ 2.190437] sr 0:0:3:0: Attached scsi generic sg1 type 5
[ 2.190485] sd 1:0:1:0: Attached scsi generic sg2 type 0
[ 2.318294] device-mapper: uevent: version 1.0.3
[ 2.318433] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised:
[email protected]
[ 2.320975] device-mapper: multipath: version 1.0.5 loaded
[ 2.328330] device-mapper: multipath emc: version 0.0.3 loaded
[ 2.349172] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 2.962360] PM: Starting manual resume from disk
[ 2.988184] kjournald starting. Commit interval 5 seconds
[ 2.988216] EXT3-fs: mounted filesystem with ordered data mode.
[ 8.637703] udevd version 125 started
[ 9.453490] drivers/net/ibmveth.c: ibmveth: IBM i/pSeries Virtual Ethernet
Driver 1.03
[ 9.453509] vio_register_driver: driver ibmveth registering
[ 13.582353] EXT3 FS on dm-2, internal journal
[ 14.654187] loop: module loaded
[ 14.722173] Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008)
[ 14.722190] bonding: Warning: either miimon or arp_interval and
arp_ip_target module parameters must be specified, otherwise bonding will not
detect link failures! see bonding.txt for details.
[ 23.372917] kjournald starting. Commit interval 5 seconds
[ 23.373378] EXT3 FS on dm-6, internal journal
[ 23.373390] EXT3-fs: mounted filesystem with ordered data mode.
[ 23.375666] kjournald starting. Commit interval 5 seconds
[ 23.376075] EXT3 FS on dm-9, internal journal
[ 23.376086] EXT3-fs: mounted filesystem with ordered data mode.
[ 23.377523] kjournald starting. Commit interval 5 seconds
[ 23.377917] EXT3 FS on dm-5, internal journal
[ 23.377928] EXT3-fs: mounted filesystem with ordered data mode.
[ 23.379399] kjournald starting. Commit interval 5 seconds
[ 23.379761] EXT3 FS on dm-8, internal journal
[ 23.379771] EXT3-fs: mounted filesystem with ordered data mode.
[ 23.381611] kjournald starting. Commit interval 5 seconds
[ 23.382131] EXT3 FS on dm-7, internal journal
[ 23.382141] EXT3-fs: mounted filesystem with ordered data mode.
[ 24.075804] Adding 499704k swap on /dev/mapper/vg00-swap_1. Priority:-1
extents:1 across:499704k
[ 24.996062] bonding: bond0: enslaving eth0 as an active interface with an up
link.
[ 25.007952] bonding: bond0: enslaving eth1 as an active interface with an up
link.
** Loaded modules:
Module Size Used by
bonding 123512 0
loop 28412 0
atkbd 29352 0
serio 27336 1 atkbd
libps2 13992 1 atkbd
ibmveth 31008 0
evdev 20864 0
ext3 187856 6
jbd 79760 1 ext3
mbcache 17012 1 ext3
dm_mirror 29880 0
dm_log 20372 1 dm_mirror
dm_snapshot 31024 0
dm_round_robin 9176 1
dm_emc 11648 0
dm_multipath 31816 3 dm_round_robin,dm_emc
dm_mod 95016 25 dm_mirror,dm_log,dm_snapshot,dm_multipath
sg 52592 0
sr_mod 28588 0
cdrom 50440 1 sr_mod
sd_mod 39016 2
ibmvscsic 38168 4
scsi_transport_srp 14864 1 ibmvscsic
scsi_tgt 25216 1 scsi_transport_srp
scsi_mod 227432 6
sg,sr_mod,sd_mod,ibmvscsic,scsi_transport_srp,scsi_tgt
windfarm_pid 8304 0
windfarm_smu_sat 12856 0 [permanent]
windfarm_max6690_sensor 10160 0
windfarm_lm75_sensor 10840 0
windfarm_cpufreq_clamp 8352 0
windfarm_core 21224 4
windfarm_smu_sat,windfarm_max6690_sensor,windfarm_lm75_sensor,windfarm_cpufreq_clamp
i2c_powermac 10896 0
** PCI devices:
** Sound cards:
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc64)
Kernel: Linux 2.6.26-1-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-powerpc64 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-1-powerpc64 recommends no packages.
Versions of packages linux-image-2.6.26-1-powerpc64 suggests:
pn linux-doc-2.6.26 <none> (no description available)
pn mkvmlinuz <none> (no description available)
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-1-powerpc64/preinst/overwriting-modules-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/preinst/lilo-has-ramdisk:
linux-image-2.6.26-1-powerpc64/postinst/bootloader-test-error-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/postinst/depmod-error-2.6.26-1-powerpc64: false
linux-image-2.6.26-1-powerpc64/preinst/initrd-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/preinst/lilo-initrd-2.6.26-1-powerpc64: true
linux-image-2.6.26-1-powerpc64/preinst/abort-overwrite-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/postinst/old-system-map-link-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/preinst/failed-to-move-modules-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/postinst/kimage-is-a-directory:
linux-image-2.6.26-1-powerpc64/preinst/abort-install-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/postinst/old-initrd-link-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/prerm/removing-running-kernel-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/preinst/bootloader-initrd-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/postinst/create-kimage-link-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/postinst/depmod-error-initrd-2.6.26-1-powerpc64:
false
linux-image-2.6.26-1-powerpc64/preinst/elilo-initrd-2.6.26-1-powerpc64: true
linux-image-2.6.26-1-powerpc64/postinst/bootloader-error-2.6.26-1-powerpc64:
linux-image-2.6.26-1-powerpc64/postinst/old-dir-initrd-link-2.6.26-1-powerpc64:
true
linux-image-2.6.26-1-powerpc64/prerm/would-invalidate-boot-loader-2.6.26-1-powerpc64:
true
--
Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a
--- End Message ---
--- Begin Message ---
On Fri, Jan 16, 2009 at 06:21:53PM +0100, Frank Fegert wrote:
[...]
> If not the above, what would be the correct way to configure multiple
> bonding interfaces?
See section 3.4 of the bonding HOWTO
<http://www.kernel.org/doc/Documentation/networking/bonding.txt>
Ben.
--
Ben Hutchings
I say we take off; nuke the site from orbit. It's the only way to be sure.
--- End Message ---
