From owner-freebsd-bugs@freebsd.org  Wed Nov 18 19:24:31 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 39670A32ADC
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 18 Nov 2015 19:24:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1CD2B1A05
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Nov 2015 19:24:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAIJOU6Z064798
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Nov 2015 19:24:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 204661] Either zdb doesn't correctly report block size of zfs
 root files, or ZFS isn't applying recordsize to files in the zfs root
Date: Wed, 18 Nov 2015 19:24:31 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: chris@acsi.ca
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-204661-8-gJiLeQZXJ7@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204661-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-204661-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 19:24:31 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204661

--- Comment #2 from Christopher Forgeron <chris@acsi.ca> ---
Ah yes, I tried 'zdb -d $pool/ $N' when my first attempt didn't work, so it
does seem a natural way to find the info.

I would suggest the most error-free way would be to follow Solaris' lead on
this, as my command syntax shouldn't be different when I'm in the root dataset
or not.

Of course this is probably a non-trivial update. 

Any recommendations for an alternate way to watch IO size for a file? a dtrace
script that targets an inode perhaps?

-- 
You are receiving this mail because:
You are the assignee for the bug.