mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org, "Michał Dec" <moog621@gmail.com>,
	reiserfs-devel@vger.kernel.org, "Jan Kara" <jack@suse.cz>
Subject: Re: Alternatives after removal of ReiserFS
Date: Thu, 19 May 2022 12:16:52 +0200	[thread overview]
Message-ID: <20220519101652.iu5jbol2cjwr4y5c@quack3.lan> (raw)
In-Reply-To: <2631780.mvXUDI8C0e@natalenko.name>

On Thu 19-05-22 11:20:24, Oleksandr Natalenko wrote:
> Hello.
> 
> On středa 18. května 2022 14:10:25 CEST Michał Dec wrote:
> > Does the Linux kernel actually offer any alternatives to users whose use 
> > cases are satisfied by ReiserFS? These users will probably be stuck with 
> > a much older kernel once ReiserFS is completely removed. I'm one of 
> > those users and I use ReiserFS to keep around large quantities of small 
> > files and quite ironically these are copies of the Linux kernel. I keep 
> > around 2, maybe 3 separate kernel trees to make sure the kernels I have 
> > on my devices can be rebuilt at any time.
> 
> I think the advantage of using reiserfs for small files faded away over
> time and became an old tale that is being passed from one generation to
> another without any modern adequate testing.
> 
> XFS should serve you well.

Yes, so the space savings of tail packing e.g. for the kernel tree are
likely still noticeable (my tree here has around half of the files with
size below 4k). But given how cheap the storage is these days, people don't
care as much. If space efficiency is important, it could be improved by using
1k blocksize for xfs or ext4. Also btrfs does packing of small files so
for lots of small files it may be more space-efficient. And btrfs also
supports transparent compression so that can reduce space usage for larger
files even further.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2022-05-19 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 12:10 Michał Dec
2022-05-19  9:20 ` Oleksandr Natalenko
2022-05-19 10:16   ` Jan Kara [this message]
2022-05-19 15:43     ` Michał Dec

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=20220519101652.iu5jbol2cjwr4y5c@quack3.lan \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moog621@gmail.com \
    --cc=oleksandr@natalenko.name \
    --cc=reiserfs-devel@vger.kernel.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

all inboxes | Powered by JetHome®