From owner-freebsd-fs@FreeBSD.ORG Thu Apr 9 21:39:10 2015 Return-Path: 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 C8B62889 for ; Thu, 9 Apr 2015 21:39:10 +0000 (UTC) Received: from smtp101-5.vfemail.net (eightfive.vfemail.net [96.30.253.185]) (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 94309F14 for ; Thu, 9 Apr 2015 21:39:09 +0000 (UTC) Received: (qmail 15432 invoked by uid 89); 9 Apr 2015 21:39:00 -0000 Received: by simscan 1.4.0 ppid: 15420, pid: 15428, t: 0.0735s scanners:none Received: from unknown (HELO d3d3MTEwQDE0Mjg2MTU1NDA=) (cmlja0BoYXZva21vbi5jb21AMTQyODYxNTU0MA==@MTcyLjE2LjEwMC45MkAxNDI4NjE1NTQw) by 172.16.100.61 with ESMTPA; 9 Apr 2015 21:39:00 -0000 Date: Thu, 09 Apr 2015 16:39:00 -0500 Message-ID: <20150409163900.Horde.ZLVwr91i2UaonmJT1bC-Pw1@www.vfemail.net> From: Rick Romero To: freebsd-fs Subject: ZFS 10.1 send single snapshot - space 'used' irregularity User-Agent: Internet Messaging Program (IMP) H5 (6.2.2) X-VFEmail-Originating-IP: MTA4Ljc2LjE3NS4xMw== X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include VFEmail headers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes Content-Transfer-Encoding: 8bit Content-Disposition: inline Content-Description: Plaintext Message 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 21:39:10 -0000 I have 3 servers, A, B, C.  I'm building C to replace A, and replicating the data to C from backup B.  A is offsite in relation to B and C. All servers are FreeBSD 10.1, except A - which is 9.2. I'm confused on disk usage. Not so much a GB here or there, but 250GB is 'unaccounted for' on C.  C and A should be a pretty close match. A - looks correct sysvolssd2/home  used                  495G                   - sysvolssd2/home  usedbysnapshots       37.9G                  - sysvolssd2/home  usedbydataset         456G                   - sysvolssd2/home  usedbychildren        669M                   - sysvolssd2/home  usedbyrefreservation  0                      - sysvolssd2/home  logicalused           585G                   - NAME         SIZE     ALLOC   FREE    CAP    DEDUP    HEALTH  ALTROOT sysvolssd2  1.39T   744G   680G       52%      1.00x     ONLINE  - B - looks correct (backup of A, holds more snapshots and other crap than A) sysvol/primessd_home  used                  777G                   - sysvol/primessd_home  usedbysnapshots       240G                   - sysvol/primessd_home  usedbydataset         537G                   - sysvol/primessd_home  usedbychildren        0                      - sysvol/primessd_home  usedbyrefreservation  0                      - sysvol/primessd_home  logicalused           754G                   - NAME         SIZE  ALLOC   FREE   FRAG  EXPANDSZ    CAP  DEDUP  HEALTH  ALTROOT sysvol          4.53T  2.43T  2.10T    20%         -                 53%  1.00x  ONLINE  -  C - missing what appears to be the multiple snapshot data.  Only the latest snapshot was sent, not the entire dataset.  So 531GB is close enough to the 537G of B's dataset. sysvol_enc/home  used                  758G                   - sysvol_enc/home  usedbysnapshots       3.00M                  - sysvol_enc/home  usedbydataset         752G                   - sysvol_enc/home  usedbychildren        5.84G                  - sysvol_enc/home  usedbyrefreservation  0                      - sysvol_enc/home  logicalused           531G                   - NAME         SIZE  ALLOC   FREE   FRAG  EXPANDSZ    CAP  DEDUP  HEALTH  ALTROOT sysvol_enc  1.39T  1.12T   277G    49%         -                   80%  1.00x  ONLINE  - C is geli encrypted and B is not. Unfortunately when I check another server that's geli encrypted, it looks fine: E - nlsysvol/home  used                  13.8G                  - nlsysvol/home  usedbysnapshots       5.58G                  - nlsysvol/home  usedbydataset         7.78G                  - nlsysvol/home  usedbychildren        483M                   - nlsysvol/home  usedbyrefreservation  0                      - nlsysvol/home  logicalused           12.0G                  - NAME       SIZE  ALLOC   FREE   FRAG  EXPANDSZ    CAP  DEDUP  HEALTH  ALTROOT nlsysvol   115G  42.8G    72.2G      -         -                    37%  1.00x    ONLINE  - So the difference shouldn't be related to the encryption.  It's almost as if the send from B to C included all the incremental snapshots, but didn't actually account for them.  Am I reading this wrong, or is something else not right ? Should I delete that dataset, re-send the entire original dataset, then delete the incremental snapshots? It makes me a little concerned that deleting a snapshot might delete the data which was written at that time, even though it was not deleted in followup snapshots... And I assume FRAG is fragmentation.  50% is a bit strange for a brand new receive, isn't it? help.  :) Rick