From owner-freebsd-current Sat Oct 20 20:18:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3EE0F37B401 for ; Sat, 20 Oct 2001 20:18:44 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9L3IZq56810; Sat, 20 Oct 2001 20:18:35 -0700 (PDT) (envelope-from dillon) Date: Sat, 20 Oct 2001 20:18:35 -0700 (PDT) From: Matthew Dillon Message-Id: <200110210318.f9L3IZq56810@apollo.backplane.com> To: Mark Huizer Cc: current@FreeBSD.ORG Subject: Re: NT filesystem panicking my current box References: <20011020153616.A76111@eeyore.local.dohd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Try turning off vmiodirenable: sysctl -w vfs.vmiodirenable=0 And see if that makes a difference. -Matt :On one of my current boxes I run amanda, which some 2 weeks ago (after an :upgrade to that current) started dying reliable when the backup started. : :the ntfs FS is mounted on /nt : :2 seconds of testing showed that 'tar -czf /dev/null /nt' was enough for :a kernel panick within 2 seconds. : :A few upgrades later the problem still exists. : :Before I go through the trouble of collecting the backtraces and make :kernel dumps and all: do other people have this problem as well? Or is :this part of the NTFS module not really updated after the KSE happening? :(I have now disabled all local filesystems from the backup, since only :excluding the NTFS backup didn't solve the problem, still a crash, that :one I haven't looked at later on) : :Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message