From owner-freebsd-current  Mon Feb  1 00:37:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA13937
          for freebsd-current-outgoing; Mon, 1 Feb 1999 00:37:58 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13924
          for <current@FreeBSD.ORG>; Mon, 1 Feb 1999 00:37:54 -0800 (PST)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.2/8.9.1) id AAA02272;
	Mon, 1 Feb 1999 00:37:52 -0800 (PST)
	(envelope-from dillon)
Date: Mon, 1 Feb 1999 00:37:52 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199902010837.AAA02272@apollo.backplane.com>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: current@FreeBSD.ORG
Subject: Re: vn and 4.0
References:  <36B47C1B.C509042A@newsguy.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:Is vn safe right now on -current? And does current's msdos fs
:support fat-32?
:
:--
:Daniel C. Sobral			(8-DCS)
:dcs@newsguy.com

    With that most recent patch ( which I am just committing now ) ... maybe.
    In -4.x, the alternate B_PAGING path in vn.c's vnstrategy() code is used
    for VM faults as well as swap I/O.  In -3.x that path was only used for
    swap I/O.  It is possible that there are more bugs in this section of 
    vn.c.

    I would say it is 'probably' ok, but it will take more people testing
    the vn device under -4.x to be able to say that it is safe.

    					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message