All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat Double <pat@patdouble.com>
To: reiserfs-list@namesys.com
Cc: David Masover <ninja@slaphack.com>
Subject: Re: reiser4 performance
Date: Tue, 9 Aug 2005 21:19:13 -0500	[thread overview]
Message-ID: <200508092119.13103.pat@patdouble.com> (raw)
In-Reply-To: <42F96238.1000502@slaphack.com>

Actually I did make it public, hit the wrong command on my mail client ;)

I did not try the -mm kernel (latest patches is for -mm5 IIRC), I use software 
suspend 2 and it does not apply to the 2.6.12.x-mm series. Except for this 
problem reiser4 has worked great for me. Since I use a single partition and 
'/' does not get modified much I copied all my data over, rebuilt the 
filesystem, and then started using it. I have not discovered any problems, 
and the filesystem is quite fast.

On Tuesday 09 August 2005 09:11 pm, David Masover wrote:
> Pat Double wrote:
> > Forgive me for moving to private, but I've posted this on the list before
> > without comment.
>
> Make it public again if you like.
>
> > The 2.6.12.x patches and 2.6.12.x applied from -mm have incorrect
> > behavior when modifying the root directory. If you add or remove files in
> > the root, the filesystem check fails. You can try this on a ram disk or
> > loop file system. I'd be interested to see if you'd try it and let me
> > know if you get a failed filesystem check. I am able to repair without
> > data loss.
>
> I'll have to try it sometime, but not now.  Does this happen on that -mm
> kernel if you apply *all* the patches, not just reiser4-specific?
> (Doing this would eliminate the need for my patch, obviously.)
>
> Incidentally, if you've been watching the list, I recently recovered
> some ungodly amount of data that I'd effectively "rm -rf"ed.  The kernel
> used both to create that catastrophy and to recover from it was a
> 2.6.12.2 kernel, patched just as I described, using fsck.reiser4 1.0.4.
>
> > On Tuesday 09 August 2005 08:34 pm, David Masover wrote:
> >>Gregory Maxwell wrote:
> >>>On 8/8/05, David Masover <ninja@slaphack.com> wrote:
> >>
> >>[...]
> >>
> >>>My ability to use it is severely hampered only being able to use it on
> >>>boxes running test-kernel of the day.. which are laden with other
> >>>issues unrelated to reiser4 that I don't have time to deal with.
> >>
> >>How recent a Reiser4 do you need?  There are some patches against the
> >>vanilla kernel at
> >>
> >>http://namesys.com/pub/reiser4-for-2.6/
> >>
> >>But those seem out of date and don't work for me.  But, the patches from
> >>the mm-kernel have been rock-solid for me.  I'm taking the vanilla
> >>2.6.12.3 kernel and patching it with the Reiser4 patches from
> >>2.6.12-mm2.  Unpack this:
> >>
> >>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-
> >>mm 2/2.6.12-mm2-broken-out.tar.bz2
> >>
> >>to /usr/src/ and run this:
> >>
> >>#!/bin/sh
> >># hack to bring mm reiser4 back to vanilla
> >>cd /usr/src/linux
> >>for i in `grep reiser4 ../broken-out/series`; do
> >>	patch -p1 < ../broken-out/$i;
> >>done
> >>
> >>I've attached one patch of my own that makes it compile properly --
> >>apply after you run the script above.

-- 
Pat Double, pat@patdouble.com
"In the beginning God created the heaven and the earth."

  reply	other threads:[~2005-08-10  2:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 10:32 reiser4 performance Hemiplegic Menehune
2005-08-08 10:51 ` PFC
2005-08-08 11:09 ` Raymond A. Meijer
2005-08-08 13:38   ` Ingo Bormuth
2005-08-08 16:44     ` PFC
2005-08-08 19:53       ` David Masover
2005-08-08 20:30         ` michael chang
2005-08-08 20:34           ` michael chang
2005-08-08 20:40             ` Bedros Hanounik
2005-08-08 20:58               ` michael chang
2005-08-08 21:41                 ` Ingo Bormuth
2005-08-08 20:51         ` Funding [Was:reiser4 performance] Pysiak Satriani
2005-08-08 19:56   ` reiser4 performance David Masover
2005-08-08 22:06     ` Hans Reiser
2005-08-09  0:02       ` David Masover
2005-08-09  0:16         ` michael chang
2005-08-09  1:02           ` David Masover
2005-08-09 17:52             ` michael chang
2005-08-09 20:19               ` Valdis.Kletnieks
2005-08-10  1:23               ` David Masover
2005-08-10 21:33         ` Hans Reiser
2005-08-08 18:09 ` Hans Reiser
2005-08-08 18:10 ` Hans Reiser
2005-08-08 23:13   ` Gregory Maxwell
2005-08-08 23:30     ` Hans Reiser
2005-08-09  0:20     ` David Masover
2005-08-09  0:58       ` Gregory Maxwell
2005-08-09  1:33         ` David Masover
2005-08-09  1:55           ` Gregory Maxwell
2005-08-11 18:49             ` Hans Reiser
2005-08-11 19:00               ` PFC
2005-08-11 21:29                 ` Gregory Maxwell
2005-08-09  2:03           ` Gregory Maxwell
2005-08-10  1:34             ` David Masover
2005-08-10  1:51               ` Pat Double
2005-08-10  2:11                 ` David Masover
2005-08-10  2:19                   ` Pat Double [this message]
2005-08-10  2:32                     ` David Masover
2005-08-10  2:49                       ` Pat Double
2005-08-09  7:41         ` PFC
  -- strict thread matches above, loose matches on Subject: below --
2005-08-08 20:57 Pysiak Satriani
2005-08-08 22:42 ` Hans Reiser

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=200508092119.13103.pat@patdouble.com \
    --to=pat@patdouble.com \
    --cc=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.