From owner-freebsd-current Tue Oct 10 21:11:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AAD8C37B502 for ; Tue, 10 Oct 2000 21:11:39 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 14ACE28732; Wed, 11 Oct 2000 11:11:29 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 01DAA2865C for ; Wed, 11 Oct 2000 11:11:28 +0700 (ALMST) Date: Wed, 11 Oct 2000 11:11:28 +0700 (ALMST) From: Boris Popov To: freebsd-current@freebsd.org Subject: 'dup alloc' panic - more details needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Call to all who experienced this panic - please provide mount(8) output for filesystem in question, so one can gather statistic about mount/ffs options. It seems that the one of the recent commits just disclosed a very old bug somewhere in ffs and/or VFS. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message