From owner-freebsd-fs@freebsd.org Mon Aug 10 09:56:13 2015 Return-Path: Delivered-To: freebsd-fs@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 F1CFF998348 for ; Mon, 10 Aug 2015 09:56:12 +0000 (UTC) (envelope-from email.ahmedkamal@googlemail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (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 8CE1CE0D for ; Mon, 10 Aug 2015 09:56:12 +0000 (UTC) (envelope-from email.ahmedkamal@googlemail.com) Received: by wijp15 with SMTP id p15so128632021wij.0 for ; Mon, 10 Aug 2015 02:56:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7HocLFOqrdR+KTzW1WrHLXlwmXZhBnMjcUiputaC85E=; b=Cb5wvuQs7osI8Hp6cYFSj6x4RWVSfuV7ZyMazmIZNkddU+DbQ6aX0yD83dZfGXZG69 uN8ooEc6G9V9LMpCP3DH5uVMB/C9GZHWjupU8SUpseL1gApaLBhwEhWIEEl82XjWjhr7 Z09Gbhtc2AFNzYCss0ywfvSF9eMLLGgXfMpYzO9WXtO2XnIMp6qJFYIM/38cCJ2t4vSa FINRrA1ryRD5IJR3SKlG4pfmxCEU8tvCgjd4bG1CSRRt8/xxzNLjuQsXvZeE9Sj3VKVT LfF7XVRzCL0PcHKKIWOe5PpbFw1GOLjQfHdE9X5lRnze2yTp7RpEcORmjqx/gL/UoQ6i OGew== X-Received: by 10.180.21.244 with SMTP id y20mr22920099wie.65.1439200571020; Mon, 10 Aug 2015 02:56:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.6.143 with HTTP; Mon, 10 Aug 2015 02:55:51 -0700 (PDT) In-Reply-To: <55C872FD.1060608@herveybayaustralia.com.au> References: <55C82BCD.2050404@herveybayaustralia.com.au> <55C863DE.3000200@digiware.nl> <55C872FD.1060608@herveybayaustralia.com.au> From: Ahmed Kamal Date: Mon, 10 Aug 2015 11:55:51 +0200 Message-ID: Subject: Re: Urgently need some help solving lost space due to snapshots during receive op To: Da Rock Cc: Willem Jan Withagen , Ahmed Kamal via freebsd-fs Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2015 09:56:13 -0000 Try setting compression=lz4 on the target pool .. that might shave off some space especially if the source wasn't compressed On Mon, Aug 10, 2015 at 11:46 AM, Da Rock < freebsd-fs@herveybayaustralia.com.au> wrote: > On 10/08/2015 18:42, Willem Jan Withagen wrote: > >> On 10-8-2015 06:42, Da Rock wrote: >> >>> I'm trying to move a pool from one system to another - exact same hdd >>> and config, different in other areas. Both register same space >>> available, and so should be no issue. The old system is quite full - >>> still at least 5% free though. >>> >> Hi, >> >> Are the versions of your FreeBSD also equal? >> > No. 9.1 to 10.1. > >> >> Because in newer version, the free space reservation is significantly >> bigger. So if disks are equal size, then with newer FreeBSDs you have >> less usable space available. >> Don't know the exact SVN commit where it happened. But there are more >> question on this topic in the list, and they all boil down to the same >> thing: ZFS needs more reserved space to be able to do certain things >> without freezing the system. >> >> I've not read any suggestions that you can circumvent this setting. >> > Crap. So I guess my best will be to compress as best I can for the moment > or something like that. > >> >> As a second note I think is is more or less general understanding that a >> ZFS systeem needs a lot more space left free than 5% to actual be able >> to perform. >> Last number I remember as sensible maximum fill level is around 70%. >> If you go over it, your system is going to be busy with ZFS bookkeeping >> instead of data storage. >> > Yeah, I noticed that. Something I'm working on... backlog of sorting > activities really :) Once I'm done it'll drop to well below 50% I'd say. > >> (One of the things I remember from the ZFS lecture by Kirk McKusik, >> which I no longer can find on YouTube :( ) >> >> --WjW >> > Thanks for the info - I owe you a beer! At least I know why now and eases > my growing headache from banging my head on the brick wall. > > >> I have done a recursive snapshot on the system and a send/receive over >>> ssh. Near the end, it final croaks and says no space left. The snapshot >>> it is sending is nowhere to be found on the receiving system. >>> >>> Ok, checked free space - should be enough - so I try a simple cp op on >>> the last dataset, but then it again croaks no space near the end, but at >>> least I have some data. >>> >>> Checking space again, it says free space of an expected value, but still >>> won't allow further data. >>> >>> I can't seem to figure out why this is not working, I'm currently trying >>> using compression on the dataset to see if it can't squeeze it on there, >>> but I still have a couple of no space messages so far. >>> >>> Where has my space gone?! >>> >>> TIA >>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >>> >> > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >