From owner-freebsd-hackers@freebsd.org Sun Sep 6 12:15:21 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C9E39CC3F6 for ; Sun, 6 Sep 2015 12:15:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB04A1CDB for ; Sun, 6 Sep 2015 12:15:20 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t86CFIdR024242 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 6 Sep 2015 06:15:18 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t86CFIah024239; Sun, 6 Sep 2015 06:15:18 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 6 Sep 2015 06:15:18 -0600 (MDT) From: Warren Block To: Don whY cc: FreeBSD-Hackers Mailing List Subject: Re: Mount NetBSD partition/slice In-Reply-To: <55EBF5C1.2050906@gmx.com> Message-ID: References: <55EBF5C1.2050906@gmx.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 06 Sep 2015 06:15:18 -0600 (MDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2015 12:15:21 -0000 On Sun, 6 Sep 2015, Don whY wrote: > Hi, > > I've pulled the media from my NetBSD systems (6.x?) before moving to > FreeBSD (9.2). The goal was to set up FreeBSD-based appliances and > maintain them from FreeBSD *systems*. > > However, I've been having a tough time getting FreeBSD to play nice > with the NetBSD media. A bit of research indicates that there is > no support for these incompatible volume formats. It's not clear whether you mean filesystems or a partitioning system or maybe some kind of RAID-type "volume". > So, I can either rebuild one of more NetBSD systems and pull all > the data across a network connection. This could be tedious as > there are 10-12 slices of significant size on each volume. (I had > hoped to just install the drives in the FreeBSD boxen and cp(1) the > contents of the volume at bus speeds.) > > Or, just rebuild the NetBSD systems and make NetBSD-based appliances > (i.e., abandon FreeBSD). > > [I'm not an OS zealot; I'm just looking for something that *works* > with the least amount of wasted effort/time] > > Have I missed some "trick" to coax NetBSD into *reading* these > volumes? It depends on the answer to the question above. If FreeBSD can read the NetBSD version of UFS but there is some header/partitioning data in the way, there is an example of skipping over that in mdconfig(8). If NetBSD can read and write FreeBSD UFS, then add another drive with FreeBSD UFS to the NetBSD system and copy it there. If it is something only NetBSD can read, a NetBSD VM on a FreeBSD host could deal with it. scp/rsync/cpdup could be used. That will go through the VM-to-host network. In theory, that would be faster than a physical network. In practice, it might not be any faster.