From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0BF261381F3 for ; Thu, 3 Oct 2013 12:49:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 47839E0A97; Thu, 3 Oct 2013 12:49:09 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 34F82E0A02 for ; Thu, 3 Oct 2013 12:49:08 +0000 (UTC) Received: from mail-ve0-f176.google.com ([209.85.128.176]:49157) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VRiL7-000gl1-Nf for gentoo-user@lists.gentoo.org; Thu, 03 Oct 2013 19:49:09 +0700 Received: by mail-ve0-f176.google.com with SMTP id jx11so1637234veb.7 for ; Thu, 03 Oct 2013 05:49:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ChwgLIpvWnw8NikPrnYqL3Iza54tBzgGp70fDwhgRmQ=; b=Q4oT4eibl+P3fKMYRgQVnQ1bi5SPwrqtSKZ2WaqYp2Zekfi7SD0kMbrSUfbu227M2i C6YysEzw0gfeyRjeC2/Oc8zdrYkP1ASnAYGB4VP4ouf2kBGUPZk3qfaL6ct3JYAMRKjt gR7xT+kKvfgP8QLCfHFubaIWTW2oQGesC7bqhqxFKsQ4uk6pdEmSgdirKdiR9BGccXRS sqDpsW191ZUNO3YE8u06SOWbv6YPfOSdkTZPZHX22snX0APICCdUGI+ZUrNpihZ0NqFt p+uZzyPY0imUJTR55wcTqSrGV6MYQlJws4xoKKsuIA6AKcB+4crBSnOYG8wKZl3gDOUl CjeQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.58.179.104 with SMTP id df8mr681722vec.26.1380804546571; Thu, 03 Oct 2013 05:49:06 -0700 (PDT) Received: by 10.220.163.69 with HTTP; Thu, 3 Oct 2013 05:49:06 -0700 (PDT) In-Reply-To: <524D3F00.9090901@fastmail.co.uk> References: <5239A20E.7090102@ramses-pyramidenbau.de> <4083700.7YOtJyrB1G@wstn> <5239C231.9080702@gmail.com> <524D3F00.9090901@fastmail.co.uk> Date: Thu, 3 Oct 2013 19:49:06 +0700 Message-ID: Subject: Re: [gentoo-user] which filesystem is more suitable for /var/tmp/portage? From: Pandu Poluan To: gentoo-user Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Get-Message-Sender-Via: svr-us4.tirtonadi.com: authenticated_id: rileyer+pandu.poluan.info/only user confirmed/virtual account not confirmed X-Archives-Salt: 3ac2781a-5ef2-404b-9c3e-bab926e332af X-Archives-Hash: ac962082ad70d18af38681f410c36097 On Thu, Oct 3, 2013 at 4:55 PM, Kerin Millar wro= te: > On 18/09/2013 16:09, Alan McKinnon wrote: >> >> On 18/09/2013 16:05, Peter Humphrey wrote: >>> >>> On Wednesday 18 Sep 2013 14:52:30 Ralf Ramsauer wrote: >>> >>>> In my opinion, reiser is a bit outdated ... >>> >>> >>> What is the significance of its date? I use reiserfs on my Atom box for >>> /var, >>> /var/cache/squid and /usr/portage, and on my workstation for /usr/porta= ge >>> and >>> /home/prh/.VirtualBox. It's never given me any trouble at all. >> >> >> >> Sooner or later, reiser is going to bitrot. The ReiserFS code itself >> will not change, but everything around it and what it plugs into will >> change. When that happens (not if - when), there is no-one to fix the >> bug and you will find yourself up the creek sans paddle >> >> An FS is not like a widget set, you can't really live with and >> workaround any defects that develop. When an FS needs patching, it needs >> patching, no ifs and buts. Reiser may nominally have a maintainer but in >> real terms there is effectively no-one >> >> Circumstances have caused ReiserFS to become a high-risk scenario and >> even though it might perform faultlessly right now, continued use should >> be evaluated in terms of that very real risk. > > > Another problem with ReiserFS is its intrinsic dependency on the BKL (big > kernel lock). Aside from hampering scalability, it necessitated compromis= e > when the time came to eliminate the BKL: > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?i= d=3D8ebc423 > > Note the performance loss introduced by the patch; whether that was > addressed I do not know. > > In my view, ReiserFS is only useful for saving space through tail packing= . > Unfortunately, tail packing makes it slower still (an issue that was > supposed to be resolved for good in Reiser4). > > In general, I would recommend ext4 or xfs as the go-to filesystems these > days. > > --Kerin > XFS is honestly looking mighty good if your host has 8 cores or more: http://lwn.net/Articles/476263/ If data corruption is *totally* not acceptable, and if you have more than one disks of similar sizes, ZFS might even be more suitable. Rgds, --=20 FdS Pandu E Poluan ~ IT Optimizer ~ =E2=80=A2 LOPSA Member #15248 =E2=80=A2 Blog : http://pepoluan.tumblr.com =E2=80=A2 Linked-In : http://id.linkedin.com/in/pepoluan