> 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 vs zfs list on the new system and looking at
> space used.)
>
> Is this a problem? Should I be panicking yet?
W
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 vs zfs list on the new system and looking at
space used.)
Is this a p
On Fri, Sep 14, 2012 at 11:07 PM, Bill Sommerfeld wrote:
> On 09/14/12 22:39, Edward Ned Harvey
> (**opensolarisisdeadlongliveopens**olaris)
> wrote:
>
>> From:
>> zfs-discuss-bounces@**opensolaris.org[mailto:
>>> zfs-discuss-
>>> boun...@opensolaris.org] On Behalf Of Dave Pooser
>>>
>>> Unfortu
On Sat, Sep 15, 2012 at 2:07 PM, 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 vs zfs list on the new system and looking at
> space used.)
On Thu, Aug 30, 2012 at 1:11 PM, Timothy Coalson wrote:
> Is there a way to get the total amount of data referenced by a snapshot
> that isn't referenced by a specified snapshot/filesystem? I think this is
> what is really desired in order to locate snapshots with offending space
> usage.
Try
