From: Edward Shishkin <edward.shishkin@gmail.com>
To: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Cc: "'reiserfs-devel@vger.kernel.org'" <reiserfs-devel@vger.kernel.org>
Subject: Re: Status of Reiser4?
Date: Thu, 30 Aug 2012 22:31:32 +0200 [thread overview]
Message-ID: <503FCDA4.9060203@gmail.com> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C620EB58@ex-mb1.corp.adtran.com>
Hello.
On 08/30/2012 09:42 PM, ANDY KENNEDY wrote:
> All,
>
> Google didn't help me much in my search for information, though I admit
> to not being the greatest at searching the net. I'm a long-term user of
> ReiserFS but after moving to a multi-core processor, I'm experience less
> than desirable performance. BTW, quick shout-out: Been using ReiserFS
> 3.4 for ~12 years and I have only ever had ONE problem with it (and it
> wasn't the FS's fault -- a disk pack failed repeatedly during a reboot
> caused by a RAID drive failure -- I was able to recover 100% of the
> data, though it took a LONG TIME ;) ).
>
> In my search on the web, I have seen that there is still life in Reiser4
> but being adopted into the main-line kernel has stalled/met opposition.
> Is Reiser4 ready for a production machine?
Make sure that you have the latest stuff (reiser4-for-2.6.39) and
tail packing is turned off (format your partition with the option
-o "formatting=extents"). In this configuration it should work.
Once everything gets stable, we'll turn it on via mount option. If
something goes wrong, then let us know..
Reiser4 doesn't have scalability problems inherent to ReiserFS (v3)
because of using progressive algorithms.
Thanks,
Edward.
prev parent reply other threads:[~2012-08-30 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 19:42 Status of Reiser4? ANDY KENNEDY
2012-08-30 20:31 ` Edward Shishkin [this message]
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=503FCDA4.9060203@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=ANDY.KENNEDY@adtran.com \
--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;
as well as URLs for NNTP newsgroup(s).