From owner-freebsd-bugs Sun Sep 12 16: 0:50 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id C3E5114DCE for ; Sun, 12 Sep 1999 16:00:48 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id RAA12972; Sun, 12 Sep 1999 17:00:58 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909122300.RAA12972@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ted Mittelstaedt" Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/11226: Invalid files on disk after fsync In-reply-to: Your message of "Sun, 12 Sep 1999 00:20:02 PDT." <199909120720.AAA78735@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Sep 1999 17:00:58 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The only one time that I have ever seen anything in the message log > regarding this is a rather cryptic log entry: > > Aug 11 06:12:59 herald /kernel: biodone: buffer already done This bug is believed to be fixed in the CAM version of the aic7xxx driver and/or in the CAM SCSI layer. I never pinned down just which of the bugs it was (my hunch being a bug in the SCSI layer), but Tor confirmed that CAM fixed it for him. If you are able to upgrade to a 3.2R or 3.3-stable system, the problem should go away. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message