From owner-freebsd-questions@FreeBSD.ORG Sat Apr 2 15:40:02 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 676A11065675 for ; Sat, 2 Apr 2011 15:40:02 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 21D7F8FC14 for ; Sat, 2 Apr 2011 15:40:01 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p32Fe1G0008645; Sat, 2 Apr 2011 09:40:01 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p32Fe1p0008642; Sat, 2 Apr 2011 09:40:01 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 2 Apr 2011 09:40:01 -0600 (MDT) From: Warren Block To: Chris Rees In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-196401946-1301758801=:5156" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Sat, 02 Apr 2011 09:40:01 -0600 (MDT) Cc: questions@freebsd.org Subject: Re: mount a dumpfile X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 15:40:02 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-196401946-1301758801=:5156 Content-Type: TEXT/PLAIN; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Sat, 2 Apr 2011, Chris Rees wrote: > On 2 Apr 2011 00:08, "Warren Block" wrote: > > > > Is it possible to mount a dump(8) dumpfile?  restore(8) obviously knows everything about the file structure, and restore -i is nearly a read-only mount_dump already. > > Restore -i isn't really anything like a mount; it works on a stream (which is why it works on tapes and stdin) where the first but is the file list, telling restore how far to skip to > get the file. This is why ls is fast on it, but when you tell it to restore it then takes a little time. Sorry, I didn't explain very well. Use mdconfig to create a device backed by a dumpfile. Then factor out the code from restore to treat that layout as a filesystem. Conceptually, it'd be similar to mount_cd9660. Which is another way to ask the question: does anything besides restore(8) understand the dumpfile format? libarchive does not, unfortunately. > If you want proper interactive backups, I'd respectfully suggest you > start using rsync incremental backup, for which I have a script sy > home I'd you're interested. It's malus versus citrus, but it's always interesting to see alternate approaches. ---902635197-196401946-1301758801=:5156--