From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 1 10:17:22 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EB8816A4CE for ; Fri, 1 Oct 2004 10:17:22 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6F6F43D2D for ; Fri, 1 Oct 2004 10:17:21 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id i91AGcff010680 for ; Fri, 1 Oct 2004 12:16:39 +0200 (CEST) (envelope-from ivoras@fer.hr) Message-ID: <415D2E86.5060007@fer.hr> Date: Fri, 01 Oct 2004 12:16:38 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <415BDFC2.1020304@fer.hr> <415C9967.3090309@jonny.eng.br> In-Reply-To: <415C9967.3090309@jonny.eng.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: GEOM (ggate) compression consumer +problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2004 10:17:22 -0000 João Carlos Mendes Luís wrote: > Instead of block compression, wouldn't it be better (and maybe easier) > to use file compresion, in a VFS layer (and a threaded daemon)? Better, yes. Easier very much not, since I know something about GEOM (actually, ggate), and nothing about VFS and kernel internals. Also, as others mentioned, even files would need to be compressed in blocks, to allow for random seeking... > This is what I would like to see in a compressed file system. I agree :) But, I still can't solve the wdrain problem. I've tried it on a recent BETA6 kernel and it still remains. Writes get slower and slower (actually, the frequency of writes), and then something locks up (with no CPU usage...). Sometimes, *any* writes to any filesystem lock up. Should I take it to geom@ list? It doesn't seem to be developer-oriented.