X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C894E0.2F50B098@onstor-exch02.onstor.net>; Wed, 2 Apr 2008 09:39:56 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: rootfs
Date: Wed, 2 Apr 2008 09:39:56 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09321B3E@onstor-exch02.onstor.net>
In-Reply-To: <47F3B602.2080306@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: rootfs
Thread-Index: AciU37yWSHom/cyvQoyYxdhJctYg2gAAB4TA
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9513@onstor-exch02.onstor.net>	<BB375AF679D4A34E9CA8DFA650E2B04E056C9515@onstor-exch02.onstor.net> <20080401181310.63e656bb@ripper.onstor.net> <47F3B602.2080306@onstor.com>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

Don't see why you can not fix the problem instead of forcing everybody
to apply workarounds.  You can detect that we are running from NFS and
skip the dhcp thing.=20

>-----Original Message-----
>From: Sripal Surendiran (HCL)
>Sent: Wednesday, April 02, 2008 9:36 AM
>To: Andy Sharp
>Cc: Larry Scheer; Maxim Kozlovsky; dl-Cougar; dl-QA
>Subject: Re: rootfs
>
>Those who have NFS root will face the problem. NFS root becomes invalid
>as soon as filer tries to contact DHCP server. DHCP client brings down
>the interface IP to 0 to enable the network card before contacting the
>DHCP server. So the filer will hang, since it doesn't have the file
system.
>
>But NFS root has been used only for internal purpose. Updating the
>network configurations manually to skip DHCP will be the workaround.
>This will also suppress the FTI.
>
>Can we update the wiki  about the work around for NFS root?
>
>-Sripal
>
>Andrew Sharp wrote:
>> This is a bug with trying to use the dev branch now that the FTI
>> stuff has been integrated when running your filer with NFS root and
>> dhcp IP address.  When running NFS root, I always set IP address
>> statically, but that's just me.
>>
>> The FTI code sets eth0 up to be set by dhcp, which causes the root
file
>> system to disappear when dhcp daemon sets the IP address to 0.
>>
>> This is a bug, but I'm not sure where the fix should go.  I'll leave
>> that up to Larry and Sripal.
>>
>>
>> People who need to run NFS root in the meantime can just hack
>> their /etc/network/interfaces file and comment out the
>>
>> auto eth?
>> iface
>>
>> lines.  You should be able to boot after that at least.
>>
>>
>> On Tue, 1 Apr 2008 17:52:25 -0700 "Larry Scheer"
>> <larry.scheer@onstor.com> wrote:
>>
>>
>>> Max,
>>>   I hit the same problem as you. This will delay creating submittal
16
>>> until I get to the bottom of this. It doesn't appear to have been a
>>> problem with the initial configuration of the root filesystem but
>>> something I have yet to identify.
>>>
>>> Larry
>>>
>>> _____________________________________________
>>> From: Larry Scheer
>>> Sent: Tuesday, April 01, 2008 4:58 PM
>>> To: Maxim Kozlovsky
>>> Subject: RE: rootfs
>>>
>>> It is supposed to work. It must work. But the FTI code was just
merged
>>> into the dev branch today and I am just getting around to building
the
>>> rootfs from scratch. It build ok for me the last time I did one
which
>>> was on 3/19. I will know in a 30 minutes or so if I hit the same
>>> problem as you.
>>>
>>> Larry
>>>
>>> _____________________________________________
>>> From: Maxim Kozlovsky
>>> Sent: Tuesday, April 01, 2008 4:24 PM
>>> To: Larry Scheer
>>> Subject: rootfs
>>>
>>> Hi Larry,
>>>
>>> I have tried to configure the root fs from scratch on my filer as is
>>> described on the wiki, and it hangs during the boot:
>>>
>>> Mounting local filesystems...done.
>>> Activating swapfile swap...done.
>>> Starting ONStor initial configuration utility:.
>>> Setting up networking....
>>> Configuring network interfaces...Internet Systems Consortium DHCP
>>> Client V3.0.4
>>> Copyright 2004-2006 Internet Systems Consortium.
>>> All rights reserved.
>>> For info, please visit http://www.isc.org/sw/dhcp/
>>>
>>> bp0: unknown hardware address type 65535
>>>
>>> Is this supposed to work at all?
>>>
>>> Max
>>>

