From owner-freebsd-current@FreeBSD.ORG Mon Jan 19 12:21:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E23516A4CE for ; Mon, 19 Jan 2004 12:21:46 -0800 (PST) Received: from mail.tradex.sk (tradex.sk [81.0.229.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D987743D2D for ; Mon, 19 Jan 2004 12:21:44 -0800 (PST) (envelope-from martin@tradex.sk) Received: from localhost (tradex.sk [81.0.229.33]) by mail.tradex.sk (Postfix) with ESMTP id 5B618AD34 for ; Mon, 19 Jan 2004 21:21:44 +0100 (CET) Received: from tradex.sk (unknown [217.23.250.82]) by mail.tradex.sk (Postfix) with ESMTP id 48CFFAD2F for ; Mon, 19 Jan 2004 21:21:25 +0100 (CET) Message-ID: <400C3D1C.80500@tradex.sk> Date: Mon, 19 Jan 2004 21:25:00 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; cs-CZ; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 0.82.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at tradex.sk X-Mailman-Approved-At: Tue, 20 Jan 2004 05:20:25 -0800 Subject: vnode-backed md stops responding on copying files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 20:21:46 -0000 I am using FreeBSD-Current (post 5.2-RELEASE) and have created a vnode backed vn using these commands: mdconfig -a -t vnode -s 8G -f somebackingfile -u 0 (I tried 4G and 2G, too) bsdlabel -w md0 auto newfs md0c mount /dev/md0c /mnt Then I started copying files or doing a make installworld DESTDIR=/mnt from /usr/src and md hangs after some time copying. The md device and all processes accessing it cannot be accessed, only a hardware reset is possible to survive, reboot command doesn't work, too. I was able to reproduce this system on various system configurations (all i386, with up to 2GB memory with AMD K6-3, Athlon or Intel P4 processors), so it doesnt seem to be caused by my system configuration. I am using a clean FreeBSD install. It does not depend on mdconfig flags or if system is mounted asynchronously/synchronously, too, tried to turn off clustering, make mount synchronous, no help. This problem does not occur with FreeBSD 4 (using vn driver).