mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Nico Schottelius <nicos@pcsystems.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext3/reiserfs: ext3fine, reiser got OOPS!
Date: Sun, 5 Aug 2001 17:27:18 +1200	[thread overview]
Message-ID: <20010805172718.B20716@weta.f00f.org> (raw)
In-Reply-To: <3B6CAE4E.17850717@pcsystems.de>
In-Reply-To: <3B6CAE4E.17850717@pcsystems.de>

On Sun, Aug 05, 2001 at 04:24:14AM +0200, Nico Schottelius wrote:

    I 've been using ext3 and reiserfs for somedays with 2.4.7. Using
    mkreiserfs I recieved some null pointer problems and recieved a
    kernel oops.

Odd --- nobody else has reported this.  Can you plese supply more
details (ksymoops) such that these bugs may be fixed.

    While ext3 is mounted as fast as ext2, reiserfs seems is slower.

Slower to mount? Or slower to use?

    ext3, 10 GB: ~ 0.5 seconds reisferfs 10 GB: ~ 3-5 seconds

Probably journal replay, still, you might have slow disks.  A journal
reply for me of 60+ events takes about 1 second on a single spindle
(SCSI, U160).

    Generating the journal with tune2fs was again much faster than
    mkreiserfs. But I think this is because reiser creates a new fs,
    wherefore mkfs.ext2 did that before.

Yes.


Do it really matter (within reason) which fs mounts and is made
faster?  It's not something you do every other minute.



    While running there occured some problems with reiserfs.

Such as?

    I am wondering that reiserfs first got into the kernel before
    ext3!

It was ready first (mostly).





   --cw

  reply	other threads:[~2001-08-05  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-05  2:24 Nico Schottelius
2001-08-05  5:27 ` Chris Wedgwood [this message]
2001-08-05 13:16   ` Nico Schottelius
2001-08-05 14:14     ` Chris Wedgwood

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=20010805172718.B20716@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicos@pcsystems.de \
    /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®