Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jul 2005 14:53:57 -0500
From:      Karl Denninger <karl@denninger.net>
To:        freebsd-stable@freebsd.org
Subject:   Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!]
Message-ID:  <20050722195357.GB95692@FS.denninger.net>
In-Reply-To: <20050722194009.GA95692@FS.denninger.net>
References:  <20050721194500.W9208@fledge.watson.org> <20050721192613.GA61902@FS.denninger.net> <6.2.1.2.0.20050721153750.0851fab0@64.7.153.2> <20050721202234.GA62615@FS.denninger.net> <20050722004340.H16902@fledge.watson.org> <20050722001253.GA70277@FS.denninger.net> <20050722013605.U16902@fledge.watson.org> <20050722010611.GA72234@FS.denninger.net> <42E0F93E.7000108@commit.it> <20050722194009.GA95692@FS.denninger.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 22, 2005 at 02:40:09PM -0500, Karl Denninger wrote:
> It is definitely NOT fixed in 6.0-BETA1
> 
> Within SECONDS of starting a buildworld after the provider rebuild
> completed, I got this...
> 
> GEOM_MIRROR: Device boot: provider ad4s1 detected.
> GEOM_MIRROR: Device boot: rebuilding provider ad4s1.
> GEOM_MIRROR: Device boot: provider ad6s1 detected.
> GEOM_MIRROR: Device boot: rebuilding provider ad6s1.
> GEOM_MIRROR: Device boot: rebuilding provider ad4s1 finished.
> GEOM_MIRROR: Device boot: provider ad4s1 activated.
> GEOM_MIRROR: Device boot: rebuilding provider ad6s1 finished.
> GEOM_MIRROR: Device boot: provider ad6s1 activated.
> subdisk4: detached
> ad4: detached
> unknown: FAILURE - SETFEATURES SET TRANSFER MODE timed out
> unknown: timeout waiting to issue command
> unknown: error issueing SETFEATURES SET TRANSFER MODE command
> GEOM_MIRROR: Device boot: provider ad4s1 disconnected.
> GEOM_MIRROR: Request failed (error=6). ad4s1[READ(offset=35096543232,
> length=10240)]

Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE
DISK DETACHED!

At least with the 5.x problems you'd SEE an error before it went BOOM.

This time around, nope - just death.

What's worse, the complaints continue even through a shutdown, making any
attempt to shutdown and reboot the machine futile.  After waiting over 10
minutes for a shutdown to complete I had to resort to the use of the power
switch.

This is NOT good, because if you get hosed by this kind of thing you have
no way out of it remotely.

Thus, my contention is that 6.0-BETA1 is far <WORSE> than 5.x is in this
regard.

Be careful out there....

--
-- 
Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist
http://www.denninger.net	My home on the net - links to everything I do!
http://scubaforum.org		Your UNCENSORED place to talk about DIVING!
http://homecuda.com		Emerald Coast: Buy / sell homes, cars, boats!
http://genesis3.blogspot.com	Musings Of A Sentient Mind





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050722195357.GB95692>