Date: Sun, 1 Dec 1996 21:02:04 -0500 (EST) From: Brian Tao <taob@io.org> To: Robert Nordier <rnordier@iafrica.com> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, hackers@FreeBSD.org Subject: Re: A simple way to crash your system. Message-ID: <Pine.BSF.3.95.961201205627.4096C-100000@nap.io.org> In-Reply-To: <199611261049.MAA02308@eac.iafrica.com>
index | next in thread | previous in thread | raw e-mail
On Tue, 26 Nov 1996, Robert Nordier wrote:
>
> *All* problems occurred with the DOS FS on a 64/63 IDE drive. FIPS
> was not necessarily used. In one case, the corrupted UFS fs was
> actually on another drive.
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.
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Senior Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961201205627.4096C-100000>