From: Oleg Drokin <green@namesys.com>
To: Sebastian Kanthak <sebastian.kanthak@muehlheim.de>
Cc: reiserfs-list@namesys.com, vs@namesys.com
Subject: Re: vs-3050: wait_buffer_until_released
Date: Wed, 19 Feb 2003 11:22:33 +0300 [thread overview]
Message-ID: <20030219112233.A10215@namesys.com> (raw)
In-Reply-To: <200302181840.47996.sebastian.kanthak@muehlheim.de>
Hello!
On Tue, Feb 18, 2003 at 06:40:47PM +0100, Sebastian Kanthak wrote:
> I'm using a vanilla 2.4.20 kernel with reiserfs on lvm. I can reproducably
> crash the system by accessing the reiserfs-partition via samba. If I do this,
> the following message appears in the kernel log and repeats every 5 or 10
> seconds.
> Feb 18 11:11:10 manticore kernel: vs-3050: wait_buffer_until_released: nobody
> releases buffer (dev 3a:01, size 4096, blocknr 128036, count 2, list 0, state
> 0x10019, page c1108284, (UPTODATE, CLEAN, UNLOCKED)). Still waiting
> (60000000) JDIRTY !JWAIT
> I've dumped the mentioned block via debugreiserfs and attached it to this
> email.
Aha. More info for you.
If you mean the above message as the "crash", then there is different scenario,
that might be taking place.
There is a in-tree block that is marked as free in the bitmap (how did it get in
that state is still unclear). Now you use that block during tree traversals.
Then you want to allocate one more block. Bitmap allocator chooses the block
that is marked free and by accident it is the same block sthat is in fact used
already. We start to wait for buffer with the block to be released, but that's we
who hold the buffer in this case, so buffer is indeed never released.
You can fix this problem with reiserfsck --fix-fixable, just as it recommended.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-19 8:22 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 [this message]
2003-02-19 13:26 ` Sebastian Kanthak
2003-02-19 13:49 ` Oleg Drokin
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=20030219112233.A10215@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sebastian.kanthak@muehlheim.de \
--cc=vs@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.