From owner-freebsd-fs@FreeBSD.ORG Fri Jun 17 12:41:17 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE1A7106564A for ; Fri, 17 Jun 2011 12:41:17 +0000 (UTC) (envelope-from cmdlnkid@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 695888FC16 for ; Fri, 17 Jun 2011 12:41:17 +0000 (UTC) Received: by iyj12 with SMTP id 12so2813331iyj.13 for ; Fri, 17 Jun 2011 05:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to; bh=qwh54qo9cS1phfKfhuDUy4jmDctstfA+bBIIlraVXLI=; b=QxgXaTQ9s30NdZ0dok5ps9pCHwcncpdbUUA0QWHVMckGIbjbwTAvCp8NLbdlh2Oepd CIgcX2o2XhiNbD3ef8JUinH6FsUJT51mYpGgPTuBGsV3YjNB6p4X7twrmwYOQ5uqgHhl ISg2xBhs5YrCSRzADz2m7PWnj8UKNDaUr6pHw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=g8eW+Zt9AVg6yInija3FvPAdEOEzi9ryljYQVEv1y4U5bNuMg/aygZOxU41d7sNnGy xCfdiyDWr5TZSo+r4+qL9DOOUWlOrDTWSHXgsjnKG0GXgb7eEvwdS8fKOwgMskUeHPTj YZdCXWQ1gjDzaHTjZakavPtFdvAqhnxh8G1XE= Received: by 10.42.131.71 with SMTP id y7mr2143409ics.315.1308314476561; Fri, 17 Jun 2011 05:41:16 -0700 (PDT) Received: from DataIX.net ([108.73.113.243]) by mx.google.com with ESMTPS id s2sm2545916icw.17.2011.06.17.05.41.14 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Jun 2011 05:41:15 -0700 (PDT) Sender: The Command Line Kid Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p5HCfCDd012857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2011 08:41:12 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p5HCfBgw012856; Fri, 17 Jun 2011 08:41:11 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Fri, 17 Jun 2011 08:41:11 -0400 From: jhell To: krad Message-ID: <20110617124111.GA12660@DataIX.net> References: <20110613094803.GA10290@icarus.home.lan> <4E09C82B45BA46019281930B2EB13AC1@multiplay.co.uk> <20110613193529.GA21103@DataIX.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-fs@freebsd.org Subject: Re: Impossible compression ratio on ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2011 12:41:17 -0000 On Fri, Jun 17, 2011 at 10:10:26AM +0100, krad wrote: > On 13 June 2011 23:50, Steven Hartland wrote: > > > > > ----- Original Message ----- From: "jhell" > > To: "Steven Hartland" > > Cc: "Jeremy Chadwick" ; > > Sent: Monday, June 13, 2011 8:35 PM > > > > Subject: Re: Impossible compression ratio on ZFS > > > >> > >> > > Hi Steve, > >> > >> Knowing that there were patches out for v28 on 8.X can you confirm that > >> in fact you are using v15 ZFS ? I would assume you are because of the > >> release but I don't want to do that. > >> > > > > Confirmed this is a pure 8.2 release build machine no additional patches > > except for compiling libz without assembly optimisations as thats known > > to cause crashes. > > > > Specifically the following as directed by Xin LI:- > > cd /usr/src/lib/libz > > make cleandir > > make cleandir (yes, do it the second time) > > make MACHINE_ARCH=x86_64 obj depend all > > make MACHINE_ARCH=x86_64 install > > > > > > > > If not, then seeing you have compression turned on... did you just dump > >> that whole table into the database ? its quite possible that the > >> compression was still happening in ARC before it was finally written out > >> and this would also explain why that happened. > >> > > > > The table was just rebuilt due to changing an index, so in effect yes > > the data would have been copied from the old table into a fresh new copy > > and then renamed. > > > > > > Also what level of compression are you using ? > >> > > > > Standard lzjb, which is achieving 1.9 overall and 2.45 on this table file. > > > > Does indeed sound like this data was still being processed in some way but > > surprised it took quite so long to show something other than the initial > > file > > creation size. > > > > Its not a big issue in this case, but does raise concerns that if it wasn't > > showing the "correct" file size that the data may not have been commited to > > disk, hence could have been unsafe for this quite extended period. > > > > Setting that may be relavent in the case within mysql are:- > > innodb_log_file_size = 1024M > > innodb_log_buffer_size = 8M > > innodb_flush_method = O_DIRECT > > innodb_use_native_aio = 1 > > > > So its possible that the table was in the innodb log, but I've never > > witnessed that before tbh but its also only very recently we have moved > > our db server from ufs to zfs, hence the questions. > > > > > > Regards > > Steve > > > > > > > > ==============================**================== > > This e.mail is private and confidential between Multiplay (UK) Ltd. and the > > person or entity to whom it is addressed. In the event of misdirection, the > > recipient is prohibited from using, copying, printing or otherwise > > disseminating it or any information contained in it. > > In the event of misdirection, illegible or incomplete transmission please > > telephone +44 845 868 1337 > > or return the E.mail to postmaster@multiplay.co.uk. > > > > ______________________________**_________________ > > 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 > > " > > > > is that cvs'd to release or stable though? If stable when? zfs v28 was > commited to stable a week or so ago. Do a 'zpool upgrade' to check I think its safe to say that by Steve's reply if youve been following that it is v15.