All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Any progress in fixing "block_alloc.c:151"?
Date: Mon, 15 Aug 2011 18:21:29 +0200	[thread overview]
Message-ID: <4E494789.7040001@gmail.com> (raw)
In-Reply-To: <4E492FB9.3040501@gmail.com>

On 08/15/2011 04:39 PM, Ivan Shapovalov wrote:
> Hello,

Hello.

>
> is there any progress in fixing "kernel BUG at
> fs/reiser4/block_alloc.c:151" problem?
>
> I use reiser4 on my /home partition with cryptocompress regular file
> plugin.
> As of kernel 2.6.38, the bug still happens in data-intensive
> applications (amarok, firefox, nepomuk, etc).
> The 'estimate_dirty_cluster' patch didn't work for me, only delaying the
> appearance of problem.
>
> I guess it's somehow related to frequent fsync() calls in databases used
> by these applications..


I am trying to narrow down the problem. Debugging messages show problems
in the code, which performs compression on commit. TBH this code is
unclear and should be rewritten. Unfortunately I do have only weekends
for this, so it all long..

Thanks,
Edward.


>
> Thanks in advance,
> Ivan Shapovalov.
> --
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2011-08-15 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 14:39 Any progress in fixing "block_alloc.c:151"? Ivan Shapovalov
2011-08-15 16:21 ` Edward Shishkin [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=4E494789.7040001@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=intelfx100@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 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.