From owner-freebsd-questions Thu Sep 14 12:04:05 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA18390 for questions-outgoing; Thu, 14 Sep 1995 12:04:05 -0700 Received: from main.statsci.com (main.statsci.com [198.145.127.110]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA18384 for ; Thu, 14 Sep 1995 12:04:02 -0700 Received: by main.statsci.com (Smail3.1.29.1 #3) id m0stJZj-000r3xC; Thu, 14 Sep 95 12:03 PDT Message-Id: X-Mailer: exmh version 1.6.1 5/23/95 To: Julian Elischer , questions@freebsd.org Subject: Re: Disk corruption problems in 2.0.5R (CDROM)? In-reply-to: Your message of "Wed, 13 Sep 1995 09:11:39 -0700." Reply-to: scott@statsci.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 1995 12:03:53 -0700 From: Scott Blachowicz Sender: questions-owner@freebsd.org Precedence: bulk Scott Blachowicz wrote: > Well, I'd been getting those messages from FreeBSD boot sequence from > mountmsdosfs about not being a multiple of the clustersize, so I was thinking > of using FIPS to drop the size back down to a multiple of 32K. Except that...with a BIOS C/H/S of 524/64/63 and FIPS dealing with cylinder boundaries, I probably can't get the partition to a multiple of 32K on this disc (least common multiple of 32K and that 63 = 32K * 63 = 2064384 which won't work so hot on a 1Gb disk). Or did I miss something in that reasoning process? So, it seems that I am back to this being a problem in the msdos file system code. I completely reinstalled 2.0.5 from CD again (including newfs'ing all the relevant partitions and not mounting any DOS discs). It seemed to work fine for a while. Then I mounted my C: drive (wd0s1) read-only and did a 'find' command down it... % mkdir /c % mount -r -t msdos /dev/wd0s1 /c % find /c -xdev -print The find command gave me various results when I ran it different times... find: /c/msoffice/?????????.???: No such file or directory complaining about garbage filenames. Shortly after that, I did % ls /sbin ls: /sbin: Bad file descriptor and got messages like this: ......... syslogd: /var/run/tmp: not a directory I threw a 3 finger salute at the keyboard and got this: /: bad dir ino 2 offset 0: mangled entry panic: bad dir Syncing...1 1 1 1 1 1 1 1 1 1 1 1 1 [at this point I hit the reset button, but I don't remember if the syncing stopped or not] Any clues on how to get a useable 'msdos' file system setup? Thanx, Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc. 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org