From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] which filesystem is more suitable for /var/tmp/portage?
Date: Thu, 3 Oct 2013 19:49:06 +0700 [thread overview]
Message-ID: <CAA2qdGVmRdL9bi3z_30OJX3M6jfVPRs7tXUf1=mji4Av6ZJg4A@mail.gmail.com> (raw)
In-Reply-To: <524D3F00.9090901@fastmail.co.uk>
On Thu, Oct 3, 2013 at 4:55 PM, Kerin Millar <kerframil@fastmail.co.uk> wrote:
> 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
>
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,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
next prev parent reply other threads:[~2013-10-03 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 12:34 [gentoo-user] which filesystem is more suitable for /var/tmp/portage? 东方巽雷
2013-09-18 12:52 ` Ralf Ramsauer
2013-09-18 14:05 ` Peter Humphrey
2013-09-18 14:13 ` Ralf Ramsauer
2013-09-18 15:09 ` Alan McKinnon
2013-09-18 18:12 ` Peter Humphrey
2013-10-03 9:55 ` Kerin Millar
2013-10-03 12:08 ` Volker Armin Hemmann
2013-10-03 16:32 ` Kerin Millar
2013-10-03 18:50 ` Volker Armin Hemmann
2013-10-03 12:15 ` Peter Humphrey
2013-10-03 12:49 ` Pandu Poluan [this message]
2013-09-18 12:55 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2qdGVmRdL9bi3z_30OJX3M6jfVPRs7tXUf1=mji4Av6ZJg4A@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox