From owner-freebsd-hackers Mon Dec 2 09:40:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02270 for hackers-outgoing; Mon, 2 Dec 1996 09:40:12 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA02265 for ; Mon, 2 Dec 1996 09:40:10 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id RAA21851 for ; Mon, 2 Dec 1996 17:40:02 GMT Message-Id: <199612021740.RAA21851@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-156.va.us.ibm.net(166.72.229.156) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaak8DM2; Mon Dec 2 17:37:07 1996 Reply-To: From: "Steve Sims" To: Subject: Re: A simple way to crash your system. Date: Mon, 2 Dec 1996 09:44:32 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao pens: [File Corruption vis-a-vis UFS & MSDOSFS ] > 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. ==== I had a similar experience with UFS corruption (ld.so complaints) but without the happy ending you cite: An fsck *didn't* fix it - the entire lib tree was hosed -- to the point of a system rebuild to sort things out. Since that, I've religiously avoided MSDOS file systems. That's why FTP was invented, I guess ;-). While I endorse the movement to disable (or make it harder to mount) DOS file systems as a *real*-short-term fix, the real goal _is_ to fix MSDOSFS. How can I help in testing same? ...sjs...