All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: Pierre Etchemaite <petchema@concept-micro.com>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.6.8.1-mm4 oops
Date: Sat, 28 Aug 2004 22:27:32 +0400	[thread overview]
Message-ID: <20040828182731.GH5108@backtop.namesys.com> (raw)
In-Reply-To: <20040828170721.23774956@rayanne>

On Sat, Aug 28, 2004 at 05:07:21PM +0200, Pierre Etchemaite wrote:
> 
> 	Hi all,
> 
> Just gave kernel 2.6.8.1-mm4's Reiserfs4 support a try on my home box :)
> 
> As a test, I tried to import Linux kernel 2.6.0 source tree into a brand new
> Subversion repository (Just in case you don't
> know about Subversion yet, try http://subversion.tigris.org/, it's a
> very nice revision control system).
> 
> Importing was much slower than expected, so I straced svn. The problem was
> easy to understand: being based on BerkeleyDB4 transactions, it was doing
> fsync() all around, and I remember reading in this list that Reiserfs4's
> fsync()s [well, was it sync() ?] was currently exiting synchronously, which
> is not the traditional behavior of this call.
> 
> Ok, nevermind if this was a bad speed test ;) I ^C'ed strace (during a
> fsync() I think, since most of svn's time was spent there), and all
> the sudden OOPses started scrolling in logs' window. After a few seconds, I
> had to reset the system.

did you enable reiser4 debugging options?

> 
> Too bad I couldn't find anything in the logs after reboot, but the problem
> occured on first try, so I suspect it will be easy to reproduce.
> 
> Good luck!
> Pierre.

thanks for the report.


-- 
Alex.

      reply	other threads:[~2004-08-28 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28 15:07 2.6.8.1-mm4 oops Pierre Etchemaite
2004-08-28 18:27 ` Alex Zarochentsev [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=20040828182731.GH5108@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=petchema@concept-micro.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.