From: Edward Shishkin <edward.shishkin@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: R4 2.6.33 inconsistent keys
Date: Fri, 19 Mar 2010 17:49:58 +0100 [thread overview]
Message-ID: <4BA3AB36.8030106@gmail.com> (raw)
In-Reply-To: <4BA3A66B.5000508@gmail.com>
Edward Shishkin wrote:
> Luciano wrote:
>> First, thanks for this great filesystem. Been using it for years
>> without probs, so I hope it gets integrated into the mainline soon.
>>
>> However, I'm having some problems after upgrading from kernel 2.6.31.6
>> to 2.6.33. This is a 64 bit gentoo-patched kernel (just patches for
>> stability, I believe - no new features), with the reiser4 patches from
>> Edward's site. It's happened to me twice now that my X session locks
>> up and I see the following in my logs:
>>
>> Mar 19 15:05:23 [kernel] WARNING: Keys are inconsistent. Fsck?
>> Mar 19 15:05:23 [kernel] reiser4[gconfd-2(6033)]: cbk_level_lookup
>> (fs/reiser4/search.c:963)[vs-3533]:
>>
>
> Yup, I know about this problem. I think this is an old bug which was
> sleeping and has woken up after mainline upgrade to 2.6.31.X
>
> I remember that VS pursued this bug with partial success right
> before leaving 2.5 years ago.
>
> This is reproducible for me and I am trying to narrow down the
> problem.
This is a situation when trying to insert a key
{el = {22136708, 20075163819723075, 1384069, 131072}, pad = 22136708}
Insert position in the node is correct, but its right neighbor
has wrong value of ld_key:
node->left:----------------------------------------------------------
{el = {22136708, 18386395447120969, 1383892, 131124}, pad = 22136708}
(ld_key)
{el = {22136708, 18386395447120969, 1383892, 131124}, pad = 22136708}
{el = {22136708, 18386395447120969, 1383892, 196608}, pad = 22136708}
...
{el = {22136708, 20075163819723075, 1383894, 196608}, pad = 22136708}
{el = {22136708, 20075163819723075, 1383894, 196657}, pad = 22136708}
(rd_key)
node:----------------------------------------------------------------
{el = {22136708, 20075163819723075, 1383894, 196657}, pad = 22136708}
(ld_key)
{el = {22136708, 20075163819723075, 1383894, 196657}, pad = 22136708}
{el = {22136708, 20075163819723075, 1384069, 0}, pad = 22136708}
{el = {22136708, 20075163819723075, 1384069, 65536}, pad = 22136708}
{el = {22136708, 20075163819723075, 1384069, 131072}, pad = 22136708}
<<< insert
{el = {22136708, 21745356274552664, 1383939, 0}, pad = 22136708}
{el = {22136708, 21745356274552664, 1383939, 65536}, pad = 22136708}
{el = {22136708, 21745356274552664, 1383939, 131072}, pad = 22136708}
{el = {22136708, 21745356274552664, 1383939, 196608}, pad = 22136708}
{el = {22136708, 23442993670401603, 1384065, 0}, pad = 22136708}
...
{el = {22136708, 23720044866262066, 1383988, 131072}, pad = 22136708}
{el = {22136708, 23720044866262066, 1383988, 131118}, pad = 22136708}
(rd_key)
node->right:---------------------------------------------------------
{el = {22136708, 21745356274552664, 1383939, 0}, pad = 22136708}
(ld_ley) <<<< WRONG!
{el = {22136708, 23720044866262066, 1383988, 131118}, pad = 22136708}
{el = {22136708, 23720044866262066, 1383988, 196608}, pad = 22136708}
prev parent reply other threads:[~2010-03-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 15:52 R4 2.6.33 inconsistent keys Luciano
2010-03-19 16:29 ` Edward Shishkin
2010-03-19 16:49 ` 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=4BA3AB36.8030106@gmail.com \
--to=edward.shishkin@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.