From owner-freebsd-current Tue Jul 21 00:38:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00800 for freebsd-current-outgoing; Tue, 21 Jul 1998 00:38:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00794 for ; Tue, 21 Jul 1998 00:38:25 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id IAA22264; Tue, 21 Jul 1998 08:39:08 +0100 (BST) Date: Tue, 21 Jul 1998 08:39:08 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <27156.900992019@time.cdrom.com> 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 Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > > hrm, not really there was some traffic on the lists a few weeks/months > > back about it being broken, but that's all i know. > > Erm, wonderful. Can we have some commentary from someone who's > actually proven this either way now? Like I said, my own usage of the > vn driver has not shown any such instability. If someone who's > _actually used it_ can now comment on its instability, we'll get a lot > further. I was using it on 2.2.5 recently and managed to cause a reboot a couple of times copying large numbers of files into a ufs mounted from a vn device. I kind of assumed that it was a 2.2.x problem and ignored it. I'm afraid I don't even know what the panic message was since the console was in a different room. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message