From owner-freebsd-hackers Sun Dec 1 22:25:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA04825 for hackers-outgoing; Sun, 1 Dec 1996 22:25:34 -0800 (PST) Received: from eac.iafrica.com (196-7-192-126.iafrica.com [196.7.192.126]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA04818 for ; Sun, 1 Dec 1996 22:25:27 -0800 (PST) Received: (from rnordier@localhost) by eac.iafrica.com (8.7.6/8.6.12) id IAA02020; Mon, 2 Dec 1996 08:22:17 +0200 (SAT) From: Robert Nordier Message-Id: <199612020622.IAA02020@eac.iafrica.com> Subject: Re: A simple way to crash your system. In-Reply-To: from Brian Tao at "Dec 1, 96 09:02:04 pm" To: taob@io.org (Brian Tao) Date: Mon, 2 Dec 1996 08:22:16 +0200 (SAT) Cc: rnordier@iafrica.com, jkh@time.cdrom.com, hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao wrote: > Twice I've had ufs corruption with 2.2-ALPHA: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0a 98479 15436 75165 17% / > /dev/sd0s2e 73855 56996 10951 84% /usr > /dev/sd0s2f 19487 5549 12380 31% /var > /dev/sd0s2g 297423 226040 47590 83% /usr/local > /dev/sd0s2h 285087 67507 194774 26% /usr/X11R6 > /dev/sd0s1 102166 17800 84366 17% /c: > /dev/sd1s1 1052064 604832 447232 57% /d: > > Both times I was copying files to /d:, which you will note is a > DOS filesystem over 1G, on a separate drive. I think that's about the > only piece of hard evidence we have in common. My /usr filesystem > (and probably others) was hosed. I've had problems before (prior to > 2.2-ALPHA) writing to smaller DOS filesystems on the same drive as UFS > filesystems, but I can't remember the details of those incidents. > > On another occasion, ld.so complained it couldn't find needed > libraries, and an 'ls -l' in /usr/lib showed corrupted directory > entries (strange filenames, huge file sizes, etc.) I immediately > rebooted and after the fsck, nothing appeared to be lost. Thanks for the info. I believe that John Dyson's vfs changes over this past weekend should put an end to the ufs corruption problem. I'm not sure if or when they, or some other fix, are going into 2.2, though. -- Robert Nordier