From owner-freebsd-current Mon Mar 12 0:16:43 2001 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 6DCF737B718 for ; Mon, 12 Mar 2001 00:16:37 -0800 (PST) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id DA93728E0B; Mon, 12 Mar 2001 14:16:33 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id CE4FA28DC8; Mon, 12 Mar 2001 14:16:33 +0600 (ALMT) Date: Mon, 12 Mar 2001 14:16:33 +0600 (ALMT) From: Boris Popov To: Vallo Kallaste Cc: freebsd-current@freebsd.org Subject: Re: occasional filesystem corruption In-Reply-To: <20010220091956.A68889@myhakas.matti.ee> 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 On Tue, 20 Feb 2001, Vallo Kallaste wrote: > I have experienced two filesystem corruption cases recently. Both > took place in /usr filesystem, the first was file with very big [skip] > lock order reversal > ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from /usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280 Thanks, this particular bug is fixed. Not sure if it can cause filesystem corruption (in fact it shouldn't). However, it is not advisable to use kernel modules with WITNESS enabled. P.S. setting more appropriate subject might give a faster response :) -- 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