From: Benjamin Vander Jagt <benjamin@winchesterpc.com>
To: reiserfs-list@namesys.com
Subject: Re: [nikita-3002]: assertion failed: carry_level_invariant(doing, CARRY_DOING)
Date: Wed, 16 Aug 2006 06:32:42 -0700 (PDT) [thread overview]
Message-ID: <5832497.post@talk.nabble.com> (raw)
In-Reply-To: <200608111315.17116.vs@namesys.com>
Vladimir V. Saveliev wrote:
>
> Hello
>
> What kernel do you use? Recently we had few fixes of such problem.
>
>
I am having the exact same problems but with one difference. After a while,
the drive starts thrashing, and the system becomes totally unresponsive. I
have no way of knowing what it's doing, and I've tried leaving it alone for
as much as 24 hours, and it just doesn't stop. So far I don't see any data
loss. I am running 2.6.17 vanilla + reiser4 patch "2.6.17-3". There are no
signs of hardware errors, but I'll run a full hard drive test next just to
be sure.
Here's what dmesg says right now:
reiser4[find(26470)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
reiser4[find(26470)]: key_warning
(fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]:
WARNING: Error for inode 876827 (-2)
reiser4[syslog-ng(2407)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
reiser4[syslog-ng(2407)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
reiser4[udevd(883)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
reiser4[udevd(883)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
reiser4[udevd(883)]: parse_node40
(fs/reiser4/plugin/node/node40.c:673)[nikita-494]:
WARNING: Wrong level found in node: 2 != 1
Then it says this message about 50 times:
reiser4[find(26470)]: key_warning
(fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]:
WARNING: Error for inode 876827 (-2)
Then it says this:
reiser4[find(26470)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
Andrew, may I ask for the contents of your /proc/meminfo file? I noticed
now that I have made a typo in my fstab and have never had swap space on
this computer. I also found a lot of OOM errors earlier in dmesg. I'll be
putting swap back in now and see if it fixes anything.
-Benjamin Vander Jagt
-Vander Jagt Computers
--
View this message in context: http://www.nabble.com/-nikita-3002-%3A-assertion-failed%3A-carry_level_invariant%28doing%2C-CARRY_DOING%29-tf2042550.html#a5832497
Sent from the ReiserFS - General forum at Nabble.com.
next prev parent reply other threads:[~2006-08-16 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 21:49 [nikita-3002]: assertion failed: carry_level_invariant(doing, CARRY_DOING) Andrew James Wade
2006-08-03 12:51 ` Andrew James Wade
2006-08-03 15:28 ` Alexander Zarochentsev
2006-08-04 0:53 ` Andrew James Wade
2006-08-07 2:24 ` Andrew James Wade
2006-08-10 17:55 ` Andrew James Wade
2006-08-11 9:15 ` Vladimir V. Saveliev
2006-08-11 18:37 ` Andrew James Wade
2006-08-16 13:32 ` Benjamin Vander Jagt [this message]
2006-08-17 20:34 ` Andrew James Wade
2006-08-19 1:39 ` Benjamin Vander Jagt
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=5832497.post@talk.nabble.com \
--to=benjamin@winchesterpc.com \
--cc=reiserfs-list@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.