reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew <jackdachef@gmail.com>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Bartosz Szreder <cfiend@talent.edu.pl>,
	Matthew <jackdachef@gmail.com>,
	Dushan Tcholich <dusanc@gmail.com>,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: Current status of Reiser4
Date: Thu, 31 Jan 2008 22:43:23 +0100	[thread overview]
Message-ID: <e85b9d30801311343w587c08cdjd63bc3d7af41e93@mail.gmail.com> (raw)
In-Reply-To: <47A0F68C.2040805@gmail.com>

That's perfect timing,
thanks a lot, Edward,
I just wanted to ask, what the current status for reiser4 is :)

The mentioned hanging with bash-scripts is gone with
2.6.24-vanilla/gentoo-sources + 2.6.24-rc8-mm1-based reiser4-patch +
your additional patch, it should be the same with official / your
2.6.24-patch

However, I still run into them from time to time with zen-sources:
http://repo.or.cz/w/linux-2.6/zen-sources.git ,
perhaps due to it's aggressive / tweaked nature,

that's the only little "problem" right now, reiser4 is perfectly
stable & pretty fast: it e.g. cuts down compile time for
openoffice-2.3.1 by about 15-20 minutes with cypcompress + lzo1
(noatime,nodiratime) compared to reiserfs
(noatime,nodiratime,data=writeback,commit=120)

reiserfs: around 2 hours
reiser4 + cryptcompress w. lzo1: 1 hour 40 minutes

kde4 is simply a pleasure with it :)

i've attached the test-scripts (usually intended for some tweaking /
power-saving tests), perhaps you're able to reproduce the "hang":
- when executing full.sh & no problems, it should exit (vanilla-kernel behavior)
- when executing & the mentioned behavior it should sit there &
executing the file & not exiting, finishing it;
everytime it seems to halt / hang at another position

Regards,
Mat

      reply	other threads:[~2008-01-31 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 22:13 Current status of Reiser4 Edward Shishkin
2008-01-31 21:43 ` Matthew [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=e85b9d30801311343w587c08cdjd63bc3d7af41e93@mail.gmail.com \
    --to=jackdachef@gmail.com \
    --cc=cfiend@talent.edu.pl \
    --cc=dusanc@gmail.com \
    --cc=edward.shishkin@gmail.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).