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 7499C1381F3 for ; Thu, 3 Oct 2013 09:55:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 63AE2E0AED; Thu, 3 Oct 2013 09:55:25 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 37AE6E0A88 for ; Thu, 3 Oct 2013 09:55:24 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D130520C5C for ; Thu, 3 Oct 2013 05:55:23 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 03 Oct 2013 05:55:23 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.co.uk; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=hZ0RavZVAUTdSdiQbcNLobNp4KA=; b=j53n9CRy6X8pAopQIs21B+qusuT/ 7YWnYxMhNQc6N8RHzuXQj3W/YL9rTzi9EzZOVo5BKrVkIq82nn+l/Uh5/6Kj3/0L TDJiXJASR5SCVR5HLELWtLsY9QDwasDF62o2SJMYe2VKIrKiSKw4kJ/kfdaPE65X oUcNv3TdM376KOo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=hZ0RavZVAUTdSdiQbcNLob Np4KA=; b=C3ZUC+goezN+DE3DX2Z7NKAw57JqE2cosKMWDIX00VEdJxVFyjrId1 OzR/NWl8DtgLmM/7pqVOq2K0whYhw+db1K7iGlfNG+9PjpwuogXP4ge7Cn7sxD8F +eSHyIZtlG+5E9aLCap0T5qv2cdqzf5v3ig+VzQmPQSb19PM75ZE8= X-Sasl-enc: jkchV1dLhGlnxVpRz/yrbF3Rx2VtY9OYyHl1ml1TkDrk 1380794123 Received: from [192.168.1.100] (unknown [94.170.82.148]) by mail.messagingengine.com (Postfix) with ESMTPA id 6BDB3C00E81 for ; Thu, 3 Oct 2013 05:55:23 -0400 (EDT) Message-ID: <524D3F00.9090901@fastmail.co.uk> Date: Thu, 03 Oct 2013 10:55:12 +0100 From: Kerin Millar User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] which filesystem is more suitable for /var/tmp/portage? References: <5239A20E.7090102@ramses-pyramidenbau.de> <4083700.7YOtJyrB1G@wstn> <5239C231.9080702@gmail.com> In-Reply-To: <5239C231.9080702@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 5c747c42-0c49-46d6-9259-6d24c8aa0ffe X-Archives-Hash: 0b08212c999107062bb3d8fa514a3afb 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/portage 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 compromise when the time came to eliminate the BKL: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8ebc423 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