From owner-freebsd-fs@FreeBSD.ORG Wed May 19 13:32:52 2010 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 91EEC1065675 for ; Wed, 19 May 2010 13:32:52 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4D5438FC1B for ; Wed, 19 May 2010 13:32:51 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OEjOE-0007Dr-Nt for freebsd-fs@freebsd.org; Wed, 19 May 2010 15:32:50 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 May 2010 15:32:50 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 May 2010 15:32:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org connect(): No such file or directory From: Ivan Voras Date: Wed, 19 May 2010 15:32:42 +0200 Lines: 19 Message-ID: References: <4BF3A0DD.4080404@tzim.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4 In-Reply-To: <4BF3A0DD.4080404@tzim.net> X-Enigmail-Version: 1.0.1 Subject: Re: ZFS Recordsize tuning & transmission (bittorent daemon) 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: Wed, 19 May 2010 13:32:52 -0000 On 05/19/10 10:27, Arnaud Houdelette wrote: > Hi, > > I'm using the transmission bittorent client on a single drive ZFS pool > (name unsafe). Downloading is mostly OK. > But moving a downloaded file to an other zpool (zraid, name tank) takes > ages. You will generally observe the same problem with any file system you can use because torrent (and other similar p2p) downloads target random chunks of data in the files. In most other "less smart" file systems (e.g. UFS) you can preallocate the space (not by using sparse files but by really writing zeroes or random junk in the length of the total file size), which you can't in ZFS (or technically, can but you won't benefit from it). You cannot "escape" from this feature of ZFS no matter what you do (except by using expensive hardware).