> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Bill Sommerfeld
>
> > But simply creating the snapshot on the sending side should be no
> problem.
>
> By default, zvols have reservations equal to their size (so that writes
> don't fail due
On Sun, Sep 16, 2012 at 7:43 PM, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris)
wrote:
> There's another lesson to be learned here.
>
> As mentioned by Matthew, you can tweak your reservation (or refreservation)
> on the zvol, but you do so at your own risk, possibly putting yourself in
On Sep 15, 2012, at 6:03 PM, Bob Friesenhahn
wrote:
> On Sat, 15 Sep 2012, Dave Pooser wrote:
>
>> The problem: so far the send/recv appears to have copied 6.25TB of
>> 5.34TB.
>> That... doesn't look right. (Comparing zfs list -t snapshot and looking at
>> the 5.34 ref for the snapshot v
On 9/16/12 10:40 AM, "Richard Elling" wrote:
>With a zvol of 8K blocksize, 4K sector disks, and raidz you will get 12K
>(data
>plus parity) written for every block, regardless of how many disks are in
>the set.
>There will also be some metadata overhead, but I don't know of a metadata
>sizing for
