From owner-freebsd-fs@FreeBSD.ORG Fri Jul 8 08:08:36 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 4D293106566B for ; Fri, 8 Jul 2011 08:08:36 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0FD3D8FC19 for ; Fri, 8 Jul 2011 08:08:35 +0000 (UTC) Received: by iwr19 with SMTP id 19so2037338iwr.13 for ; Fri, 08 Jul 2011 01:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to; bh=U9BMyrRDzmOM41AWmQnLLLwfyyVBF+BF+QOXgMjUDs0=; b=FjNQEi+uasqArnf/NKqz77MpxZuRi/oBBSdr5xwlqvcQvr2mmYIR+7aX0ywz+Bx5yg ojURy5r9NsOIM8b8f8IFjrQvvIOs9nxRkQo+ZBhqQBYppDet4qS8MK5O+mI2dKCDR+bU we7UwXMAej0SJsMjBYFdI0zp/zQ2kpTj7x2aA= Received: by 10.42.91.139 with SMTP id p11mr1554718icm.402.1310112514158; Fri, 08 Jul 2011 01:08:34 -0700 (PDT) Received: from DataIX.net (adsl-99-181-128-71.dsl.klmzmi.sbcglobal.net [99.181.128.71]) by mx.google.com with ESMTPS id e1sm10687224icv.20.2011.07.08.01.08.31 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Jul 2011 01:08:32 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id p6888T9o050567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Jul 2011 04:08:29 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id p6888Tcj050566; Fri, 8 Jul 2011 04:08:29 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Fri, 8 Jul 2011 04:08:29 -0400 From: Jason Hellenthal To: Volodymyr Kostyrko Message-ID: <20110708080828.GA49288@DataIX.net> References: <20110707220019.GA79464@DataIX.net> <4E169107.6040109@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <4E169107.6040109@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: everlasting log device 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, 08 Jul 2011 08:08:36 -0000 On Fri, Jul 08, 2011 at 08:09:27AM +0300, Volodymyr Kostyrko wrote: > 08.07.2011 01:00, Jason Hellenthal wrote: >=20 > >> System claims that this log device has 148K data. Is this the size of > >> unwritten data? The number is still the same when booting into single > >> user mode and doesn't change at all. > >> > >> Can I remove this log device? Should I recreate the pool to get rid of > >> this behavior? > >> > > > > If you have the possibility to re-create the pool then Id definately > > suggest it. > > > > If you remove this device (physically) your pool will not be operable > > unfortunately there is still somehting missing to allow SLOGs to be > > removed from a running pool yet, what that might be is beyond me at this > > time. You might try to export the pool then boot into single user mode > > and reimport the pool and try the removal procedure but I raelly dont > > think that will help you. >=20 > Well I have already removed device physically and the pool continues to= =20 > work despite yelling about missing log device. I already tried booting=20 > from flash drive and importing/exporting pool - this doesn't work. I=20 > also tried to replace this log device with another one. Replacing works= =20 > and I can remove old device but the new one will now be unkillable. >=20 > Am I right that working without external log device is almost the same=20 > as working with disabled ZIL? >=20 What was the reason or solution for which you added the slog in the first place that you were trying to solve. I would assume it would be for speed but if that's the case and your workloads are not fsync() high amounts of data then there is absolutely no point other than debugging to make FreeBSD better! ;) I don't know what size your device was that you allotted to the slog but hope you didn't go far beyond 256MB yes that's meant to say 'MB'. There is some long discussions about slog/ZIL devices in earlier threads on these lists so you'll have to refer to them to understand what I am talking about here. Cache devices can be removed any time, and depending on the case can improve or decrease performance. ZFS is a large beast to tackle with a lot of different ways you can configure a system and a slew of options at accomplishing that. So in the least words there was a lot of documentation that was put out about it that can aid in determining how YOU should configure your pool and give you somewhat of a description of what things do and how they interact with other system processes. Besides that there is a slew of other information by some well known people on the freebsd threads that will also come in handy, check out the following. Google "site:lists.freebsd.org zfs, slog, zil, cache" Other than that it seems one layer of the system is not talking well to ZFS when its told to do something and it would be really swell if this could be found and exterminated with extreme prejudice.