Date: Wed, 18 Mar 1998 21:27:57 -0600 From: Karl Denninger <karl@mcs.net> To: dannyman <dannyman@sasquatch.dannyland.org> Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current ** READ THIS ** Message-ID: <19980318212757.30801@mcs.net> In-Reply-To: <19980318211402.23977@arh0300.urh.uiuc.edu>; from dannyman on Wed, Mar 18, 1998 at 09:14:02PM -0600 References: <199803190257.VAA06394@dyson.iquest.net> <199803190307.WAA23964@dyson.iquest.net> <19980318211402.23977@arh0300.urh.uiuc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 18, 1998 at 09:14:02PM -0600, dannyman wrote: > On Wed, Mar 18, 1998 at 10:07:57PM -0500, John S. Dyson wrote: > > John S. Dyson said: > > > > > > If -current works for you, I am still concerned. I would be misleading you > > > and others if I stated otherwise!!! I really do care about people getting > > > messed up filesystems!!! > > > Following up on my own posting: Maybe I am not being strong enough in > > my suggestion: Please do not use the -current kernel unless you know > > that the consequences will be that you will likely loose filesystem(s). > > > > Karl is trying to help with testing and advice, and unless you want to > > participate in trying to narrow down the problem, please don't use > > -current until we figure out what is going on. > > John: > > I am aware of the consequences, but to be honest, I don't know how to "revert" > or anything. Some cvsup option that'll reverse the code on my system? > > I've backed a few things up, I'll back some more up. I'm happy to "ride out > the storm" as it were, especially since things have been fine so far. I am > happy to share system information if it will help any. cd /usr/src/sys cvs update -D'03/12/1998' . ..... Kernels built from 3/12 <appear> to not contain the bug. At least, so far they appear not to contain the bug. Give me until tomorrow morning and I'll know for sure - I'm running a full regression test on the 3/12 extract right now, and will post something here if/when it either fails or runs to completion. If you're not aware that you're seeing the problem, then you probably are in one of two camps: 1) You're slowly having your data destroyed and don't know it, and by the time you DO know it you'll be completely screwed and need to essentially reformat the disk :-) 2) You are not tripping the condition that is causing the destruction. This *IS* possible; I have two machines in particular uses which do NOT cause the problem, but I don't know why. HOWEVER, be aware that even in case (2), the problematic kernel has problems with lock-ups and other bad behavior (like unsolicited resets without core dump or even a panic message, along with hard wedges which don't respond to anything short of a RESET switch) which may be related. I can readily reproduce the wedge problem on a busy webserver (which has a boot disk that never gets written to, and thus is "safe" to use the bad kernel on otherwise). If you're either unable or unwilling to actually help find this and take the concurrent risk that comes with doing so, you're best off reverting as above so you don't become a victim. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980318212757.30801>