From: Ivan Shapovalov <intelfx100@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Any progress in fixing "block_alloc.c:151"?
Date: Mon, 15 Aug 2011 18:39:53 +0400 [thread overview]
Message-ID: <4E492FB9.3040501@gmail.com> (raw)
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..
Thanks in advance,
Ivan Shapovalov.
next reply other threads:[~2011-08-15 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 14:39 Ivan Shapovalov [this message]
2011-08-15 16:21 ` Any progress in fixing "block_alloc.c:151"? Edward Shishkin
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=4E492FB9.3040501@gmail.com \
--to=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.