All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Przybyl <lil_tux@web.de>
To: reiserfs-list@namesys.com
Subject: Re: kernel BUG at fs/reiser4/block_alloc.c:149!
Date: Tue, 20 Dec 2005 14:22:36 +0100	[thread overview]
Message-ID: <20051220142236.50e7844f@tormented-soul> (raw)
In-Reply-To: <43A7B080.3070603@namesys.com>

Hello.

what i realized yesterday, after several recompilings:

i've tested it with gcc3.3 and 2.6.14 - same problem with reiser-patch +
reiser-fix-fsync-patch. without the reiser-fix-fsync-patch, it seems to work
again, with both, gcc3.3 and gcc4.1. but this is still very strange to me,
as it worked some time ago with the same patches :/

the architecture is i368. i've forgotten to mention that in my first post
- sorry for that.


> 
> Please try
> ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.15-rc5-mm3/reiser4-for-2.6.15-rc5-mm3-1.patch.gz

fine, i will give it a try. what are the main changes in that patch?


> > are there any mount/compile options, which could produce better performance
> > with larger files (i.e. 2gb and more)?
> > 
> 
> What does your load do with large files?

normal cpu-load is not very high, the only thing i can see, is the wait-io on a
very high level (sometimes >90% for several seconds). the throughput is
therefore quite low - less than 1mbyte/sec.

the 2gb file i was talking about is a virtual machine's disk.

the host is running ide-disks with 40-50mbyte/s transfer rates. creating such a
large image on reiser4 is really fast, but working with them is not.



thx anyway.


	Heiko

      reply	other threads:[~2005-12-20 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 19:33 kernel BUG at fs/reiser4/block_alloc.c:149! Heiko Przybyl
2005-12-20  7:19 ` Vladimir V. Saveliev
2005-12-20 13:22   ` Heiko Przybyl [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=20051220142236.50e7844f@tormented-soul \
    --to=lil_tux@web.de \
    --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.