From owner-freebsd-fs@FreeBSD.ORG  Sun Nov 23 22:00:20 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 82BBB9BE
 for <freebsd-fs@freebsd.org>; Sun, 23 Nov 2014 22:00:20 +0000 (UTC)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com
 [IPv6:2607:f8b0:4003:c01::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 47E4BC94
 for <freebsd-fs@freebsd.org>; Sun, 23 Nov 2014 22:00:20 +0000 (UTC)
Received: by mail-ob0-f172.google.com with SMTP id wn1so6385086obc.3
 for <freebsd-fs@freebsd.org>; Sun, 23 Nov 2014 14:00:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=G1FdaQ+InsLv8wnsCFNMgylvsHHNQKlNdmRZsYf34FQ=;
 b=CCXQvrEADnRQIhXg1vzdGtfWlwtbpQ/O+h94hclJHfE6gokshvYlNFENueEUWLm2L7
 Ri2B4zf5u3WuPZd5fekQmYq5iUCJVbSwBsXrVoR5UdLKhISHBVS42TruQvkZvXws3FmO
 oRkQCIPXIoR1cuLPdjVX74HGWMdEQ/Ok4HE0rYA8qd+Su+wHTAwTBXckjmBoQynxKFQ/
 gMb3Nbrr/yG/D0FdClaMu1ReVMSAdyqLWgBXcaj34bm9TvMAJU/QzgGMpA6st/L8nuZB
 NfRrnUNe6eWaPdaCC/GMGgs377kzo5Mc9bAVThrfFV3+MwSGSV9JYzckw8UkbZxL8jg+
 1D6Q==
MIME-Version: 1.0
X-Received: by 10.182.65.105 with SMTP id w9mr9430376obs.60.1416780019633;
 Sun, 23 Nov 2014 14:00:19 -0800 (PST)
Received: by 10.76.0.138 with HTTP; Sun, 23 Nov 2014 14:00:19 -0800 (PST)
Date: Sun, 23 Nov 2014 17:00:19 -0500
Message-ID: <CACpH0MdJLi1CCd6eLsNrsxHMbM5u594x=p3BbxaoqPyqMbCg1Q@mail.gmail.com>
Subject: Making sense of some ZDB output...?
From: Zaphod Beeblebrox <zbeeble@gmail.com>
To: freebsd-fs <freebsd-fs@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Nov 2014 22:00:20 -0000

In my quest to recover files, I've come across something I don't understand.

          100000   L0 1:720cfa33400:24c00 20000L/20000P F=1
B=11756828567/11756828567
          120000   L0 0:94048dc9000:24000 20000L/20000P F=1
B=11756828567/11756828567

So far, files I've recovered have been on vdev '0' ... which has 9
devices... I therefore makes sense to me that 24000 (hex) bytes is composed
of 20000 bytes of data and 4000 bytes of parity.  But this object I'm
trying to fetch has some data on vdev '1' ... which has 8 devices.  24c000
/ 8 is 4980 ... which isn't a very even number.  Am I looking at this
wrongly?  Does the size include the parity or not?