From owner-freebsd-hackers Mon Mar 29 11:49:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 70AB714C19 for ; Mon, 29 Mar 1999 11:49:19 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA09496; Mon, 29 Mar 1999 11:45:55 -0800 (PST) Message-Id: <199903291945.LAA09496@implode.root.com> To: Thomas David Rivers Cc: avalon@coombs.anu.edu.au, mjacob@feral.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. In-reply-to: Your message of "Mon, 29 Mar 1999 12:30:25 EST." <199903291730.MAA11166@lakes.dignus.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 29 Mar 1999 11:45:55 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> well, I've been newfs'ing the destination partitions each time, if that >> answers that question, which is where the trouble is showing up. >> > > Well - you're not going to like this, but at one time the >reproduction I had with 2.2.5 took the following steps: > > 1) Write 0xff all over the disk partition > 2) newfs the partition > 3) Do an fsck to find that 0x00 wasn't properly > written, some inodes had 0xff in them... > (that is, fsck of a newfs'd partition reported errors) > > So - if this is the same problem I had, doing a newfs doesn't >reliably clean things up. (I actually got it narrowed down to >writing a single 0xff in one spot on the disk.) > > But - I did find that fsck was able to repair things. I believe >because it did things in a different order than newfs did. > > I suppose the moral is - if you're having these kind of problems, >don't trust newfs either... :-( My recollection is that this problem was caused by large raw writes being truncated in the kernel. I also seem to remember that this only happend for floppies. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message