[releng_4 tinderbox] failure on i386/i386

2004-04-19 Thread FreeBSD Tinderbox
TB --- 2004-04-19 23:21:06 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2004-04-19 23:21:06 - starting RELENG_4 tinderbox run for i386/i386
TB --- 2004-04-19 23:21:06 - checking out the source tree
TB --- 2004-04-19 23:21:06 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386
TB --- 2004-04-19 23:21:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 
src
TB --- 2004-04-19 23:32:01 - building world (CFLAGS=-O -pipe)
TB --- 2004-04-19 23:32:01 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-19 23:32:01 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1: bootstrap tools
>>> stage 2: cleaning up the object tree
>>> stage 2: rebuilding the object tree
>>> stage 2: build tools
>>> stage 3: cross tools
>>> stage 4: populating 
>>> /home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/include
>>> stage 4: building libraries
>>> stage 4: make dependencies
>>> stage 4: building everything..
TB --- 2004-04-20 06:22:29 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2004-04-20 06:22:29 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-20 06:22:29 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Tue Apr 20 06:22:31 GMT 2004
>>> Kernel build for GENERIC completed on Tue Apr 20 06:57:15 GMT 2004
TB --- 2004-04-20 06:57:15 - building LINT kernel (COPTFLAGS=-O -pipe)
TB --- 2004-04-20 06:57:15 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-20 06:57:15 - /usr/bin/make buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Tue Apr 20 06:57:16 GMT 2004
--
===> LINT
mkdir -p 
/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/sys
cd /other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf;  
PATH=/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/sbin:/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/bin:/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d 
/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/sys/LINT
  /other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf/LINT
/other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf/LINT:957: unknown option 
"DA_OLD_QUIRKS"
*** Error code 1

Stop in /other/tinderbox/RELENG_4/i386/i386/src.
*** Error code 1

Stop in /other/tinderbox/RELENG_4/i386/i386/src.
TB --- 2004-04-20 06:57:17 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2004-04-20 06:57:17 - ERROR: failed to build lint kernel
TB --- 2004-04-20 06:57:17 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Should I merge fix for PR#64091 (NFS data corruption)?

2004-04-19 Thread Stephen McKay
On Monday, 19th April 2004, Stephen McKay wrote:

>On Sunday, 18th April 2004, Eugene Grosbein wrote:
>
>>Should one patch (and reboot in case of NFS compiled in a kernel)
>>both of a client and a server?
>
>It is a client-side patch.  The server could be anything, though I've
>only tested with FreeBSD.

By the way, Eugen, how do I get on your whitelist?  Your "challenge
response" spam protection forgot to do the "challenge" bit!

Stephen.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Any plans to update CVS beyond v1.11.5?

2004-04-19 Thread Doug Lee
Well hallelujah!  I couldn't ask for much better than that.  I look
forward to v1.11.15's arrival in STABLE.

On Mon, Apr 19, 2004 at 09:05:55PM +0100, Colin Percival wrote:
> At 20:59 19/04/2004, Doug Lee wrote:
> >CVS is being updated but FreeBSD still uses v1.11.5.  ...
> >Any plans to update CVS in the base system?
> 
>   CVS 1.11.15 was imported into -current four days ago.  I
> would assume that it will be merged onto -stable at some
> point after 4.10-RELEASE.
> 
> Colin Percival
> 

-- 
Doug Lee   [EMAIL PROTECTED]http://www.dlee.org
Bartimaeus Group   [EMAIL PROTECTED]   http://www.bartsite.com
"I before E, except after C, or when sounded like A, as in neighbor
and weigh, except for when weird foreign concierges seize neither
leisure nor science from the height of society."
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Any plans to update CVS beyond v1.11.5?

2004-04-19 Thread Colin Percival
At 20:59 19/04/2004, Doug Lee wrote:
>CVS is being updated but FreeBSD still uses v1.11.5.  ...
>Any plans to update CVS in the base system?

  CVS 1.11.15 was imported into -current four days ago.  I
would assume that it will be merged onto -stable at some
point after 4.10-RELEASE.

Colin Percival


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Any plans to update CVS beyond v1.11.5?

2004-04-19 Thread Julien Gabel
> CVS is being updated but FreeBSD still uses v1.11.5.  I'm trying to
> use a FreeBSD box as a server for both FreeBSD and Windows CVS
> clients, and I'm finding a few problems which, I believe, are fixed in
> CVS versions after 1.11.5.  Unless I missed something major, there's
> not a port for keeping up with CVS either.
>
> Any plans to update CVS in the base system?

It seems that Peter Wemm has updated CVS to version 1.11.15:
 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1758503+0+/usr/local/www/db/\
 text/2004/cvs-all/20040418.cvs-all

-- 
-jpeg.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Any plans to update CVS beyond v1.11.5?

2004-04-19 Thread Doug Lee
CVS is being updated but FreeBSD still uses v1.11.5.  I'm trying to
use a FreeBSD box as a server for both FreeBSD and Windows CVS
clients, and I'm finding a few problems which, I believe, are fixed in
CVS versions after 1.11.5.  Unless I missed something major, there's
not a port for keeping up with CVS either.

Any plans to update CVS in the base system?

This is not a complaint, btw; it's just an attempted optimization of
local resources. 

Please Cc me on replies.  Thanks much.


-- 
Doug Lee   [EMAIL PROTECTED]http://www.dlee.org
Bartimaeus Group   [EMAIL PROTECTED]   http://www.bartsite.com
"Innovation is hard to schedule." -- Dan Fylstra
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[releng_4 tinderbox] failure on i386/i386

2004-04-19 Thread FreeBSD Tinderbox
TB --- 2004-04-19 12:02:04 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2004-04-19 12:02:04 - starting RELENG_4 tinderbox run for i386/i386
TB --- 2004-04-19 12:02:04 - checking out the source tree
TB --- 2004-04-19 12:02:04 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386
TB --- 2004-04-19 12:02:04 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 
src
TB --- 2004-04-19 12:12:16 - building world (CFLAGS=-O -pipe)
TB --- 2004-04-19 12:12:16 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-19 12:12:16 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1: bootstrap tools
>>> stage 2: cleaning up the object tree
>>> stage 2: rebuilding the object tree
>>> stage 2: build tools
>>> stage 3: cross tools
>>> stage 4: populating 
>>> /home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/include
>>> stage 4: building libraries
>>> stage 4: make dependencies
>>> stage 4: building everything..
TB --- 2004-04-19 18:15:21 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2004-04-19 18:15:21 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-19 18:15:21 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Mon Apr 19 18:15:26 GMT 2004
>>> Kernel build for GENERIC completed on Mon Apr 19 18:47:30 GMT 2004
TB --- 2004-04-19 18:47:30 - building LINT kernel (COPTFLAGS=-O -pipe)
TB --- 2004-04-19 18:47:30 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-04-19 18:47:30 - /usr/bin/make buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Mon Apr 19 18:47:31 GMT 2004
--
===> LINT
mkdir -p 
/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/sys
cd /other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf;  
PATH=/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/sbin:/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/bin:/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d 
/home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/sys/LINT
  /other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf/LINT
/other/tinderbox/RELENG_4/i386/i386/src/sys/i386/conf/LINT:957: unknown option 
"DA_OLD_QUIRKS"
*** Error code 1

Stop in /other/tinderbox/RELENG_4/i386/i386/src.
*** Error code 1

Stop in /other/tinderbox/RELENG_4/i386/i386/src.
TB --- 2004-04-19 18:47:32 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2004-04-19 18:47:32 - ERROR: failed to build lint kernel
TB --- 2004-04-19 18:47:32 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: filesystem corruption with 1TB filesystem, 4.9-STABLE, twe

2004-04-19 Thread Vinod Kashyap

Please check the customer advisory at
http://www.3ware.com/support/index.asp
and make sure you don't have a known problem configuration.

Also, I would recommend using the "FreeBSD 4.8 Beta Driver"
on the 3ware website, or still better, use the driver at the
tip of RELENG_4 at:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twe/?only_with_tag=RELENG_4

If you need any help with the 3ware product, please contact
[EMAIL PROTECTED]


Thanks,

Vinod.


> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Ollie Cook
> Sent: Monday, April 19, 2004 10:06 AM
> To: Matthew Seaman; [EMAIL PROTECTED]
> Subject: Re: filesystem corruption with 1TB filesystem, 
> 4.9-STABLE, twe
> 
> 
> On Mon, Apr 19, 2004 at 04:51:16PM +0100, Matthew Seaman wrote:
> > Can you rule out hardware problems by substituting in a different
> > known good 3-ware card?  Last time I saw anything like this 
> was an IO
> > controller chip going marginal through overheating under heavy load
> > and flipping occasional bits on disk block addresses.
> 
> Hi,
> 
> This is the first time we've tried the 3ware ATA RAID cards 
> so I don't have
> another 'known good' one. Usually we use SCSI RAID cards. If 
> I were to replace
> it I still wouldn't be able to guarantee that is was 'known 
> good'. I may be
> able to arrange a part replacement, just to test that theory, 
> in any case.
> 
> Are you aware of any utilities which would be able to 
> diagnose what you
> describe? I guess what I'm asking is how did you determine 
> that that was what
> happened last time you saw these symtoms?
> 
> Thanks,
> 
> Ollie
> 
> -- 
> Oliver CookSystems Administrator, Claranet UK
> [EMAIL PROTECTED]   +44 20 7903 3065
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: filesystem corruption with 1TB filesystem, 4.9-STABLE, twe

2004-04-19 Thread Matthew Seaman
On Mon, Apr 19, 2004 at 06:05:33PM +0100, Ollie Cook wrote:

> This is the first time we've tried the 3ware ATA RAID cards so I don't have
> another 'known good' one. Usually we use SCSI RAID cards. If I were to replace
> it I still wouldn't be able to guarantee that is was 'known good'. I may be
> able to arrange a part replacement, just to test that theory, in any case.

Suppliers are usually glad to accomodate you with spare kit when the
sale depends upon it.
 
> Are you aware of any utilities which would be able to diagnose what you
> describe? I guess what I'm asking is how did you determine that that was what
> happened last time you saw these symtoms?

Hard to say.  We had around a hundred machines and this only happened
to some of them.  It took some time, and quite a lot of false starts
but eventually we pinned it down to overheating, and fixed the problem
by applying a larger heatsink and uprated fans.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature


Re: filesystem corruption with 1TB filesystem, 4.9-STABLE, twe

2004-04-19 Thread Ollie Cook
On Mon, Apr 19, 2004 at 04:51:16PM +0100, Matthew Seaman wrote:
> Can you rule out hardware problems by substituting in a different
> known good 3-ware card?  Last time I saw anything like this was an IO
> controller chip going marginal through overheating under heavy load
> and flipping occasional bits on disk block addresses.

Hi,

This is the first time we've tried the 3ware ATA RAID cards so I don't have
another 'known good' one. Usually we use SCSI RAID cards. If I were to replace
it I still wouldn't be able to guarantee that is was 'known good'. I may be
able to arrange a part replacement, just to test that theory, in any case.

Are you aware of any utilities which would be able to diagnose what you
describe? I guess what I'm asking is how did you determine that that was what
happened last time you saw these symtoms?

Thanks,

Ollie

-- 
Oliver CookSystems Administrator, Claranet UK
[EMAIL PROTECTED]   +44 20 7903 3065
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"