From owner-freebsd-current Sat Oct 20 6:36:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from nala.dohd.org (a29150.upc-a.chello.nl [62.163.29.150]) by hub.freebsd.org (Postfix) with ESMTP id B737F37B407 for ; Sat, 20 Oct 2001 06:36:21 -0700 (PDT) Received: by nala.dohd.org (Postfix, from userid 1008) id 01112D993; Sat, 20 Oct 2001 15:36:16 +0200 (MET DST) Date: Sat, 20 Oct 2001 15:36:16 +0200 From: Mark Huizer To: current@freebsd.org Subject: NT filesystem panicking my current box Message-ID: <20011020153616.A76111@eeyore.local.dohd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.19i 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 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 -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message