Bug#495946: initramfs-tools: potential race condition between nfsmounts in fstab and network interfaces
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
Reply to: