Date: Tue, 17 Mar 1998 15:16:20 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Karl Denninger <karl@mcs.net> Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected Message-ID: <Pine.SV4.3.95.980317151432.8814E-100000@parkplace.cet.co.jp> In-Reply-To: <19980317000929.36464@mcs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Did you newfs /usr/obj? On Tue, 17 Mar 1998, Karl Denninger wrote: > No. I removed the entire source tree and re-extracted it. If that was the > problem then there would be errors in the source files - there aren't. > > -- > -- > 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 > > On Tue, Mar 17, 1998 at 02:55:42PM +0900, Michael Hancock wrote: > > Is it possible that the previous kernel quietly trashed your disks and it > > didn't manifest itself until after the last vm fix commit? > > > > Regards, > > > > Mike Hancock > > > > On Mon, 16 Mar 1998, Karl Denninger wrote: > > > > > ************ URGENT ************** > > > > > > I strongly advise that you *DO NOT* use -CURRENT as it sits at the > > > present time. > > > > > > The kernel you build may do SEVERE damage to your filesystems. > > > > > > I am working on finding the commit which is causing this and will post to > > > the list as soon as I have identified it. > > > > > > This is not a trivial matter. It is a very good thing indeed that I use a > > > scratch disk for my /usr/obj area, or I would be really rather upset. :-) > > > > > > The symptoms are random core dumps and other problems - but the underlying > > > reason is that the filesystem has been trashed beyond belief! > > > > > > I unmounted the disk in question CLEANLY and found both partially truncated > > > and duplicate inodes all over it, along with severe internal file damage. > > > > > > I suspect the commit today in kern/vfs_cluster.c, as that's the only > > > filesystem or VM related commit that my first-level examination has found. > > > I am backing that out locally right now and will advise if it makes the > > > problem go away. > > > > > > Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > > > the problem. > > > > > > -- > > > -- > > > 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 > > > > > > > -- > > michaelh@cet.co.jp http://www.cet.co.jp > > CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, > > Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 > > > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 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?Pine.SV4.3.95.980317151432.8814E-100000>