From: Oleg Drokin <green@namesys.com>
To: Sebastian Kanthak <sebastian.kanthak@muehlheim.de>
Cc: reiserfs-list@namesys.com
Subject: Re: vs-3050: wait_buffer_until_released
Date: Wed, 19 Feb 2003 16:49:37 +0300 [thread overview]
Message-ID: <20030219164937.A13769@namesys.com> (raw)
In-Reply-To: <200302191426.22177.sebastian.kanthak@muehlheim.de>
Hello!
On Wed, Feb 19, 2003 at 02:26:22PM +0100, Sebastian Kanthak wrote:
> I haven't fixed the bitmap inconsistency yet, because I thought, you might
> want some other info. In the meantime, the filesystem was not used very much
> (only some simple cron-jobs or so), but I got new errors in my kernel log.
> Output from dmesg is:
> vs-4080: reiserfs_free_block: free_block (3a01:482474)[dev:blocknr]: bit
> already cleared
> vs-4080: reiserfs_free_block: free_block (3a01:482473)[dev:blocknr]: bit
> already cleared
> vs-4080: reiserfs_free_block: free_block (3a01:482472)[dev:blocknr]: bit
> already cleared
> vs-4080: reiserfs_free_block: free_block (3a01:482471)[dev:blocknr]: bit
> already cleared
> vs-4080: reiserfs_free_block: free_block (3a01:322183)[dev:blocknr]: bit
> already cleared
> vs-4080: reiserfs_free_block: free_block (3a01:322180)[dev:blocknr]: bit
Yes, these might happen too, if you have inconsistent bitmaps.
> and a lot of similar lines. If I do a reiserfsck now, I get more errors than
> the first time:
And these are kind of expected, too.
> Now, I'm wondering where these new errors came from. Are they a result of the
Used blocks that are marked free gets allocated again.
So noow you have same space used twice.
> problems with reiserfsck, but I'm afraid it will happen again, as I'm using
The interesting question is hod you got bitmap out of sync with reality.
> the problems. Do you have an idea, where my problems come from? I know now,
Have you already ruled out bad hardware?
> cause for this inconsistency? What's going on here? Can I provide you with
> additional (useful) data somehow?
Hm. If you can reproduce initial bitmap corruption somehow, this is would be very interesting.
> As reiserfs certainly does not contain so many bugs I'm starting to suspect my
> hardware (I've read your FAQ about reiserfs running hotter). Memory seems to
> be ok, though. Do you know a good tool to stress test the hard-disk and
> report errors? I'll certainly need a way to reproduce the error in order to
> locate it...
Hm. There was some.
E.g. Robin Miller´s Data Test Program
http://www.bit-net.com/~rmiller/dt.html
Bye,
Oleg
prev parent reply other threads:[~2003-02-19 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 17:40 vs-3050: wait_buffer_until_released Sebastian Kanthak
2003-02-19 6:41 ` Oleg Drokin
2003-02-19 8:22 ` Oleg Drokin
2003-02-19 13:26 ` Sebastian Kanthak
2003-02-19 13:49 ` Oleg Drokin [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=20030219164937.A13769@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sebastian.kanthak@muehlheim.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 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.