Package: initramfs-tools
Version: 0.85i
Severity: important


On a server with three e1000-based cards, I have configured eth0 and
then bond0 which uses eth1 and eth2.

I have an NFS share that requires mounting on boot and uses the network
attached to the bonded interface.

If eth0 is listed first in the /etc/network/interfaces file, the system
tries to mount the share before bond0 is brought up and times out as a
result (although the timeout appears to be 7 minutes, not 180 seconds).

If I place the "auto bond0" statement as the first statement in the
file, the system works without issue.

This issue can be replicated using SAMBA in place of NFS and is present
after a base install with only a few more packages (such as ifenslave)
installed.

I realise that this may not be an initramfs issue, however I am unable
to track it down any further. Please feel free to move to a more
appropriate package if you think it may be required.

Matt


-- Package-specific info:
-- /proc/cmdline
root=/dev/md0 ro

-- /proc/filesystems
cramfs
ext3

-- lsmod
Module Size Used by
button 6672 0
ac 5188 0
battery 9636 0
ipv6 226272 30
nls_iso8859_1 4256 1
cifs 190684 1
dm_snapshot 15552 0
dm_mirror 19152 0
dm_mod 50232 2 dm_snapshot,dm_mirror
loop 15048 0
i2c_i801 7468 0
i2c_core 19680 1 i2c_i801
parport_pc 32132 0
parport 33256 1 parport_pc
psmouse 35016 0
serio_raw 6660 0
evdev 9088 0
floppy 53156 0
pcspkr 3072 0
rtc 12372 0
ext3 119240 4
jbd 52456 1 ext3
mbcache 8356 1 ext3
raid1 21056 5
md_mod 70388 6 raid1
ide_generic 1408 0 [permanent]
sd_mod 19040 12
ata_piix 13896 10
libata 89396 1 ata_piix
scsi_mod 124168 2 sd_mod,libata
generic 4868 0 [permanent]
ide_core 110504 2 ide_generic,generic
ehci_hcd 28136 0
uhci_hcd 21164 0
e1000 108832 0
usbcore 112644 3 ehci_hcd,uhci_hcd
thermal 13608 0
processor 28840 1 thermal
fan 4804 0
bonding 71528 0

-- kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook = update-grub


-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages initramfs-tools depends on:
ii busybox 1:1.1.3-4 Tiny utilities for small and embed
ii cpio 2.6-18.1+etch1 GNU cpio -- a program to manage ar
ii klibc-utils 1.4.34-2 small statically-linked utilities
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii udev 0.105-4 /dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, Aug 21, 2008 at 03:16:06PM +0100, Matthew Macdonald-Wallace wrote:
> Package: initramfs-tools
> Version: 0.85i
> Severity: important
>
>
> On a server with three e1000-based cards, I have configured eth0 and
> then bond0 which uses eth1 and eth2.
>
> I have an NFS share that requires mounting on boot and uses the network
> attached to the bonded interface.
>
> If eth0 is listed first in the /etc/network/interfaces file, the system
> tries to mount the share before bond0 is brought up and times out as a
> result (although the timeout appears to be 7 minutes, not 180 seconds).
>
> If I place the "auto bond0" statement as the first statement in the
> file, the system works without issue.
>
> This issue can be replicated using SAMBA in place of NFS and is present
> after a base install with only a few more packages (such as ifenslave)
> installed.
>
> I realise that this may not be an initramfs issue, however I am unable
> to track it down any further. Please feel free to move to a more
> appropriate package if you think it may be required.
>
> Matt

please file relevant info, like
cat /etc/network/interfaces
cat /etc/udev/rules.d/70-persistent-net.rules

and relevant nfs setup.

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, 21 Aug 2008 16:44:53 +0200
maximilian attems <max@stro.at> wrote:
> please file relevant info, like
> cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 172.16.24.102
netmask 255.255.255.0
network 172.16.24.0
broadcast 172.16.24.255
gateway 172.16.24.1

auto bond0
iface bond0 inet static
address 10.27.1.202
netmask 255.255.255.0
network 10.27.1.0
broadcast 10.27.1.255
hwaddress ether 00:30:48:67:2A:3E
post-up ifenslave bond0 eth1 eth2
post-up /usr/local/bin/routing-setup.sh

> cat /etc/udev/rules.d/70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules
file. #
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# PCI device 0x8086:0x108c (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:30:48:67:2a:3e",
NAME="eth1"

# PCI device 0x8086:0x109a (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:30:48:67:2a:3f",
NAME="eth2"

# PCI device 0x8086:0x10b9 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:21:1c:f8:32",
NAME="eth0"


> and relevant nfs setup.

fstab on NFS client (reformatted to fit on single lines):

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/md0 / ext3 defaults,errors=remount-ro 0 1
/dev/md4 /home ext3 defaults 0 2
/dev/md2 /tmp ext3 defaults 0 2
/dev/md3 /var ext3 defaults 0 2
/dev/md1 none swap sw 0 0
10.27.1.254:/data/weblogs /data/weblogs nfs defaults 0 0

/etc/exports on NFS server:


# /etc/exports: the access control list for filesystems which may be
exported # to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)

/data/weblogs 10.27.1.0/24(rw,sync,subtree_check,no_root_squash)

/etc/netwrok/interfaces on NFS server:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 172.16.24.13
netmask 255.255.255.0
network 172.16.24.0
broadcast 172.16.24.255
gateway 172.16.24.1
# dns-* options are implemented by the resolvconf package, if
installed dns-nameservers 217.72.162.2 217.72.162.3
dns-search webonhigh.net

auto bond0
iface bond0 inet static
address 10.27.1.101
netmask 255.255.255.0
network 10.27.1.0
broadcast 10.27.1.255
hwaddress ether 00:30:48:67:25:44
post-up ifenslave bond0 eth1 eth2


10.27.1.254 (the address that the client connects to) is provided by
Heartbeat and is a virtual IP split across bond0 on the NFS server and
another interface on another NFS server.

Please let me know if you require any further information, thanks for
the help.

M.
--
|Matthew Macdonald-Wallace
|Tiger Computing Ltd
|"The Linux Specialists"
|
|Tel: 0330 088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org