Date: Mon, 29 Mar 1999 11:45:55 -0800 From: David Greenman <dg@root.com> To: Thomas David Rivers <rivers@dignus.com> Cc: avalon@coombs.anu.edu.au, mjacob@feral.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. Message-ID: <199903291945.LAA09496@implode.root.com> In-Reply-To: Your message of "Mon, 29 Mar 1999 12:30:25 EST." <199903291730.MAA11166@lakes.dignus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903291945.LAA09496>