On Mon, Jan 07, 2008 at 05:06:32PM +0100, Andre Timmermann wrote:
> I am using a Debian-based nfs-root as a rescue-system in our datacenter.
> I am running into some problems with the initial ramdisks and nfsroot.
>
> In 90% everythiong is OK, but 10% of our servers have a second nic. In
> these cases the server will not boot, as he knows not how to mount the
> nfs-root.
>

there was one important nfsroot fix that got missed for the lenny
release afair.

you could checkout initramfs-tools togethere with newer klibc from Lenny
and see if you can still reproduce with those your trouble?

--
maks


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

Hi,

thank you for your reply. I discovered, that there is no easy way to
solve the problem just by adding some configuration. I had to hack the
nfs-script to get the work done.

Here is the result of my work, just to let you know that there is no
direct problem with the package

Am Montag, den 07.01.2008, 18:28 +0100 schrieb maximilian attems:

> you could checkout initramfs-tools togethere with newer klibc from Lenny
> and see if you can still reproduce with those your trouble?

Thank you for pointing me to klibc, there is one of the problems in this
case.

When u use the parameter ip=::::::dhcp on the commandline, the following
command will be executed by the
nfs-script /usr/share/initramfs-tools/scripts/nfs:

ipconfig -d ::::::dhcp

This loops forever because one interface will not come up due to a
missing network-cable.

Adding "-t 10" kills ipconfig after 10 tries.
ipconfig -t 10 -d ::::::dhcp

I dont't know if the loop is a desired behaviour or if it is a bug, I
think there are good reasons for both possibilities.

After that sourceing /tmp/net-${DEVICE}.conf will overwrite the nfs
setting from the kernel-commandline with the setting gathered from the
dhcp-server. And again, this could be desired or not
Our DHCP-Server does not know anything about the nfs-root because it is
needed exclusively by the rescuesystem.

In addition ${DEVICE} seemes to be hardcoded in the initramfs.conf. If
initramfs.conf says eth0 and the interface is eth1 it will not be
sourced.

I have put it like this:

for i in `ls /tmp/net-*.conf`; do . $i; done

as I know that there is only one nic which will be configured.

--
Mit freundlichen Gruessen

Andre Timmermann
Nine Internet Solutions AG, nine.ch, Letzigraben 77, CH-8003 Zuerich
Tel +41 44 637 40 00 | Direkt +41 44 637 40 06 | Fax +41 44 481 16 43


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

On Thu, 10 Jan 2008, Andre Timmermann wrote:

> When u use the parameter ip=::::::dhcp on the commandline, the following
> command will be executed by the
> nfs-script /usr/share/initramfs-tools/scripts/nfs:
>
> ipconfig -d ::::::dhcp
>
> This loops forever because one interface will not come up due to a
> missing network-cable.

fixed in unstable ipconfig klibc 1.5.9-1,
please try it out

> Adding "-t 10" kills ipconfig after 10 tries.
> ipconfig -t 10 -d ::::::dhcp

couldn't reproduce that would continue to loop for me.

> After that sourceing /tmp/net-${DEVICE}.conf will overwrite the nfs
> setting from the kernel-commandline with the setting gathered from the
> dhcp-server. And again, this could be desired or not
> Our DHCP-Server does not know anything about the nfs-root because it is
> needed exclusively by the rescuesystem.

hmmm that depends on your nfs boot params, can you please post yours,
where you were seeing this?

> In addition ${DEVICE} seemes to be hardcoded in the initramfs.conf. If
> initramfs.conf says eth0 and the interface is eth1 it will not be
> sourced.
>
> I have put it like this:
>
> for i in `ls /tmp/net-*.conf`; do . $i; done
>
> as I know that there is only one nic which will be configured.

this should be possbile to pass as boot param afair.


thanks for your feedback and patience.

best regards

--
maks


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