X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C894E3.C9F6F3E8@onstor-exch02.onstor.net>; Wed, 2 Apr 2008 10:05:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C894E3.C9F6F3E8"
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9513@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E056C9515@onstor-exch02.onstor.net> <20080401181310.63e656bb@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09321B66@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: rootfs
Date: Wed, 2 Apr 2008 10:05:44 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F013C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: rootfs
Thread-Index: AciUXrd4qtOXKPv3RvGBRlI1EV8hGAAgY+UAAACGyrA=
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C894E3.C9F6F3E8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Max,
   I commented out the eth[01] sections in my network/interfaces file =
and I was able to boot. However, I did not go any further than that. I =
did not try to manually configure my filer the rest of the way. I needed =
to shift it back to booting to CF for submittal 16.=20

I don't find it acceptable to say it is ok to break NFS boots because it =
is just used internally. Having a workaround is fine if it works for all =
people in all cases. The cougar team has spent a lot of time and effort =
to make sure this feature works and continues to work because it is a =
valuable asset to rapid development. My opinion is it needs to be given =
a priority to get it working again. Do you agree?

Larry


-----Original Message-----
From: Maxim Kozlovsky
Sent: Wed 4/2/2008 9:54 AM
To: Andy Sharp; Larry Scheer
Cc: Sripal Surendiran (HCL); dl-Cougar; dl-QA
Subject: RE: rootfs
=20
Ok I fixed the interfaces file and it helped somewhat. Now the system is =
in reboot loop because of the watchdog timeout during the startup.

>-----Original Message-----
>From: Andy Sharp
>Sent: Tuesday, April 01, 2008 6:13 PM
>To: Larry Scheer
>Cc: Sripal Surendiran (HCL); Maxim Kozlovsky; dl-Cougar; dl-QA
>Subject: Re: rootfs
>
>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


------_=_NextPart_001_01C894E3.C9F6F3E8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: rootfs</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Max,<BR>
&nbsp;&nbsp; I commented out the eth[01] sections in my =
network/interfaces file and I was able to boot. However, I did not go =
any further than that. I did not try to manually configure my filer the =
rest of the way. I needed to shift it back to booting to CF for =
submittal 16.<BR>
<BR>
I don't find it acceptable to say it is ok to break NFS boots because it =
is just used internally. Having a workaround is fine if it works for all =
people in all cases. The cougar team has spent a lot of time and effort =
to make sure this feature works and continues to work because it is a =
valuable asset to rapid development. My opinion is it needs to be given =
a priority to get it working again. Do you agree?<BR>
<BR>
Larry<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Maxim Kozlovsky<BR>
Sent: Wed 4/2/2008 9:54 AM<BR>
To: Andy Sharp; Larry Scheer<BR>
Cc: Sripal Surendiran (HCL); dl-Cougar; dl-QA<BR>
Subject: RE: rootfs<BR>
<BR>
Ok I fixed the interfaces file and it helped somewhat. Now the system is =
in reboot loop because of the watchdog timeout during the startup.<BR>
<BR>
&gt;-----Original Message-----<BR>
&gt;From: Andy Sharp<BR>
&gt;Sent: Tuesday, April 01, 2008 6:13 PM<BR>
&gt;To: Larry Scheer<BR>
&gt;Cc: Sripal Surendiran (HCL); Maxim Kozlovsky; dl-Cougar; dl-QA<BR>
&gt;Subject: Re: rootfs<BR>
&gt;<BR>
&gt;This is a bug with trying to use the dev branch now that the FTI<BR>
&gt;stuff has been integrated when running your filer with NFS root =
and<BR>
&gt;dhcp IP address.&nbsp; When running NFS root, I always set IP =
address<BR>
&gt;statically, but that's just me.<BR>
&gt;<BR>
&gt;The FTI code sets eth0 up to be set by dhcp, which causes the root =
file<BR>
&gt;system to disappear when dhcp daemon sets the IP address to 0.<BR>
&gt;<BR>
&gt;This is a bug, but I'm not sure where the fix should go.&nbsp; I'll =
leave<BR>
&gt;that up to Larry and Sripal.<BR>
&gt;<BR>
&gt;<BR>
&gt;People who need to run NFS root in the meantime can just hack<BR>
&gt;their /etc/network/interfaces file and comment out the<BR>
&gt;<BR>
&gt;auto eth?<BR>
&gt;iface<BR>
&gt;<BR>
&gt;lines.&nbsp; You should be able to boot after that at least.<BR>
&gt;<BR>
&gt;<BR>
&gt;On Tue, 1 Apr 2008 17:52:25 -0700 &quot;Larry Scheer&quot;<BR>
&gt;&lt;larry.scheer@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt;&gt; Max,<BR>
&gt;&gt;&nbsp;&nbsp; I hit the same problem as you. This will delay =
creating submittal 16<BR>
&gt;&gt; until I get to the bottom of this. It doesn't appear to have =
been a<BR>
&gt;&gt; problem with the initial configuration of the root filesystem =
but<BR>
&gt;&gt; something I have yet to identify.<BR>
&gt;&gt;<BR>
&gt;&gt; Larry<BR>
&gt;&gt;<BR>
&gt;&gt; _____________________________________________<BR>
&gt;&gt; From: Larry Scheer<BR>
&gt;&gt; Sent: Tuesday, April 01, 2008 4:58 PM<BR>
&gt;&gt; To: Maxim Kozlovsky<BR>
&gt;&gt; Subject: RE: rootfs<BR>
&gt;&gt;<BR>
&gt;&gt; It is supposed to work. It must work. But the FTI code was just =
merged<BR>
&gt;&gt; into the dev branch today and I am just getting around to =
building the<BR>
&gt;&gt; rootfs from scratch. It build ok for me the last time I did one =
which<BR>
&gt;&gt; was on 3/19. I will know in a 30 minutes or so if I hit the =
same<BR>
&gt;&gt; problem as you.<BR>
&gt;&gt;<BR>
&gt;&gt; Larry<BR>
&gt;&gt;<BR>
&gt;&gt; _____________________________________________<BR>
&gt;&gt; From: Maxim Kozlovsky<BR>
&gt;&gt; Sent: Tuesday, April 01, 2008 4:24 PM<BR>
&gt;&gt; To: Larry Scheer<BR>
&gt;&gt; Subject: rootfs<BR>
&gt;&gt;<BR>
&gt;&gt; Hi Larry,<BR>
&gt;&gt;<BR>
&gt;&gt; I have tried to configure the root fs from scratch on my filer =
as is<BR>
&gt;&gt; described on the wiki, and it hangs during the boot:<BR>
&gt;&gt;<BR>
&gt;&gt; Mounting local filesystems...done.<BR>
&gt;&gt; Activating swapfile swap...done.<BR>
&gt;&gt; Starting ONStor initial configuration utility:.<BR>
&gt;&gt; Setting up networking....<BR>
&gt;&gt; Configuring network interfaces...Internet Systems Consortium =
DHCP<BR>
&gt;&gt; Client V3.0.4<BR>
&gt;&gt; Copyright 2004-2006 Internet Systems Consortium.<BR>
&gt;&gt; All rights reserved.<BR>
&gt;&gt; For info, please visit <A =
HREF=3D"http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</A><BR>
&gt;&gt;<BR>
&gt;&gt; bp0: unknown hardware address type 65535<BR>
&gt;&gt;<BR>
&gt;&gt; Is this supposed to work at all?<BR>
&gt;&gt;<BR>
&gt;&gt; Max<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C894E3.C9F6F3E8--
