From owner-freebsd-questions@freebsd.org Tue Jan 2 18:40:28 2018 Return-Path: Delivered-To: freebsd-questions@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 4F2B9EB2E34 for ; Tue, 2 Jan 2018 18:40:28 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2EFE16CBA8 for ; Tue, 2 Jan 2018 18:40:28 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2DE2FEB2E32; Tue, 2 Jan 2018 18:40:28 +0000 (UTC) Delivered-To: questions@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 2D75AEB2E31 for ; Tue, 2 Jan 2018 18:40:28 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9B8C6CBA6 for ; Tue, 2 Jan 2018 18:40:27 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id w196so38615886lff.5 for ; Tue, 02 Jan 2018 10:40:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=wSHOAs4rmlgSMuVeFx2N+SYqIfjsa3sLVC0qb2Q2HIo=; b=GM3bPTOBamOuYNLLufYdV6Q4q66WDJxHo2oEDdsgCobT7QC7d0h4YYgJYNsixgEyDj BN4jIhFyaz+O8gfSXWK38Apvn0OH0GydbJbiYe4aVOXFDZXJzIPezhGJ+1g4hcLbWxl3 R4ufc2uMsENX3CTA387TUwr0KxVFGH0WR6DcgV/6xaVKNIJJ1RgYaPapAaVcxKgW07ox c/eIxD7ffqOvrsjb2NwTnndGYq0n1GPT9zJbTYb2+84H+rQurWkGRrPVTG8pnCBgB9PB qZDeKBsrE+bib1hC6VwhkQD9l+0qPGoWmpxFUda/9Cq9TPj8TaREPwp4RMCLInMT1Si4 93+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wSHOAs4rmlgSMuVeFx2N+SYqIfjsa3sLVC0qb2Q2HIo=; b=k0zOI50T2bBOStA7M6yGI3KlgquxCsP7IZE7ezf5ZnMQjfNnmUl22lpVA6T1Wy61zK g8l4/0VxUwp8ngCCUerkv3+RUhKTLcPFmK3yd5fmrEt4JlxeXuoReOXL+ED0p6P7kiDJ JUQwC2/UYGYSQiUU2nKOLuCjj7N1HOMqM/zMacneahaR0jA3UoD+5PVi6lUD5n85/PKF v+FgvsBK4qGtQj9NvI+wmbKLhyPj1xNRQEisprsdoFf3g6X+fm9NKZbTDEcecUncvXBH vn7yVRDyF9l/s0a+1ZvRRi/zR4jMkzgMeNd7il1IashQf8EiOyH/bINnXOE89GrJWHvU 5B1w== X-Gm-Message-State: AKGB3mKg7ni4BiyD6J/OKVhYoxozUVrcU+4mFWhQ4DlB7Ed4JfqS6XF2 x7Bll7LAhELIGB/T7H4toSr0fKHP54tMviHZdqOALp5A X-Google-Smtp-Source: ACJfBouMhruwd2otgqXzW9N3ergCQqLKch/fvYCgx4OJ4DUYeSVMcnewmgE/Y4FL//Cp+4r+aMTllUkAO+QWchU5KLE= X-Received: by 10.25.23.80 with SMTP id n77mr19679986lfi.84.1514918425448; Tue, 02 Jan 2018 10:40:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.228.149 with HTTP; Tue, 2 Jan 2018 10:40:24 -0800 (PST) From: pete wright Date: Tue, 2 Jan 2018 10:40:24 -0800 Message-ID: Subject: zpool fragmentation To: freebsd-questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2018 18:40:28 -0000 Hi there, I was wondering how others here on the list deal with zpool fragmentation. My general purpose laptop uses zroot, and I've noticed over time fragmentation of my pool has grown to %42: $ zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zroot 230G 87.3G 143G - 42% 37% 1.00x ONLINE - $ I guess I have two questions: 1) is fragmentation generally bad, or just a fact of life for a system with lots of churn? 2) if it is bad, are there any coping mechanisms people use to reduce fragmentation? Cheers! -pete -- pete wright www.nycbug.org @nomadlogicLA