From owner-freebsd-questions@FreeBSD.ORG  Tue Apr 14 16:17:27 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B3FCE10656DF
	for <freebsd-questions@freebsd.org>;
	Tue, 14 Apr 2009 16:17:27 +0000 (UTC)
	(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 57AFF8FC23
	for <freebsd-questions@freebsd.org>;
	Tue, 14 Apr 2009 16:17:27 +0000 (UTC)
	(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
	by fw.farid-hajji.net (Postfix) with ESMTP id 1D7F73454D;
	Tue, 14 Apr 2009 18:17:24 +0200 (CEST)
Date: Tue, 14 Apr 2009 18:17:24 +0200
From: cpghost <cpghost@cordula.ws>
To: freebsd-questions@freebsd.org
Message-ID: <20090414161724.GA3721@phenom.cordula.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.19 (2009-01-05)
Subject: Block device to regular file?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 16:17:28 -0000

I'm trying to recover some deleted files from a UFS2 file
system with the sleuthkit. Unfortunatly, most sleuthkit
utilities expect regular image files and won't operate
on block devices:

  phenom# fls /dev/ad4s1e
  Sector offset supplied is larger than disk image (maximum: 0)

Of course, I could always dd(1) the block device into another
file system, and analyze that:

  phenom# dd if=/dev/ad4s1e of=/mnt/ad4s1e.dd
  phenom# fls /mnt/ad4s1e.dd | more
  <regular-output-of-fls>

but unfortunatly, the file system I'm trying to analyze
is VERY large and I don't have enough disk space elsewhere
to take an image.

Now, is there an easy way to turn a block device into
something that would behave like a regular file?
Something like "mdconfig -t vnode", but in reverse?

Thanks,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/