![Lead Image © Luis Louro, 123RF.com Lead Image © Luis Louro, 123RF.com](/var/ezflow_site/storage/images/archive/2014/23/zfs-on-linux-helps-if-the-zfs-fuse-service-refuses-to-work/123rf_4095333_pakt-teufel_luis-louro_resized.png/104802-1-eng-US/123rf_4095333_pakt-teufel_Luis-Louro_resized.png_medium.png)
Lead Image © Luis Louro, 123RF.com
ZFS on Linux helps if the ZFS FUSE service refuses to work
Dancing with the Devil
The differences between Linux and BSD start with everyday tools, such as ifconfig
and fdisk
. When it comes to the popular and powerful ZFS filesystem [1], the incompatibilities extend to hard disk images. The new FreeBSD 10 in particular can cause Linux admins problems when reconstructing data from ZFS pools.
As a case in point, an expert in a recent court case was tasked with evaluating a disk image: The injured party created a dd
image of his server and saved the image to a hard disk connected to a FreeNAS [2] system, which is based on BSD. The idea was for experts to analyze the server image directly from the data disk on a Linux forensics station. Windows was ruled out from the start because it cannot handle the ZFS system.
Missing Info
Surprisingly, the data disk had no partition information in the form of a master boot record (MBR) or a GUID partition table (GPT) [3]. The tricks the expert used to revive RAID systems (Figure 1) did not help: Neither fdisk
nor mmls
– the forensic counterpart from The Sleuth Kit – were willing to cooperate.
Because the victim had stored the image on a FreeNAS system, the standard file format should have provided UFS information. However, the filesystem information was unavailable. Was this disk using ZFS?
The recently released FreeBSD 10 [4] uses ZFS, which will boost the number of ZFS installations. That means more admins will be confronted with this scenario in the future.
Solution
If you remove a ZFS drive and try to mount it on a Linux system, you are likely to face the same
...Buy this article as PDF
(incl. VAT)