From owner-freebsd-hackers Fri Sep 17 16:15:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id 9DF3C15A72 for ; Fri, 17 Sep 1999 16:15:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com ([209.157.86.2]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04461 for ; Fri, 17 Sep 1999 16:12:40 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA25887; Mon, 13 Sep 1999 14:11:17 -0700 (PDT) (envelope-from dillon) Date: Mon, 13 Sep 1999 14:11:17 -0700 (PDT) From: Matthew Dillon Message-Id: <199909132111.OAA25887@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates panic in 3.3-RC References: <199909131727.NAA67883@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Our ftp server crashed early this morning with what appears to be a softupdates :error: : :> Sep 13 09:56:19 stumble /kernel: pid 41477 (perl), uid 0 on /exports/share3/ftp/.2: file system full :> :> panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 15597568 :> syncing disks... panic: softdep_lock: locking against myself : :'perl' would have been the nightly mirror(1) run to sync up our ftp site. : :What additional details would be usefull? We didn't have crashdumps enabled :on this machine, so a backtrace is not fully possible, although it would seem :the contextual evidence for what went wrong is strong. : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd :Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Softupdates has known bugs relating to filesystem full conditions which I believe Kirk is working on. There isn't much you can do until then other then either disable softupdates or work to avoid the disk-full condition. The panic does not occur very frequently so working to avoid the disk-full condition is what I would recommend. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message