From: Oleg Drokin <green@namesys.com>
To: Troels Walsted Hansen <troels@thule.no>
Cc: "'lkml'" <linux-kernel@vger.kernel.org>, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] [OOPS] Reiserfs corruption causing oops in VFS code? (Kernel 2.4.16)
Date: Wed, 13 Mar 2002 11:32:21 +0300 [thread overview]
Message-ID: <20020313113221.B871@namesys.com> (raw)
In-Reply-To: <001301c1ca0a$08e1bd20$0300000a@samurai>
In-Reply-To: <001301c1ca0a$08e1bd20$0300000a@samurai>
Hello!
On Tue, Mar 12, 2002 at 10:08:17PM +0100, Troels Walsted Hansen wrote:
> Mar 12 10:46:01 shogun kernel: is_leaf: item location seems wrong
> (second one): *OLD*[93946 93947 1436783232(0) DIR], item_len 3904,
> item_location 64, free_space(entry_count) 63
Have you tried to run reiserfsck on this partition?
What does it report?
> Mar 12 10:46:02 shogun kernel: Unable to handle kernel paging request at
> virtual address 43b279f0
> Mar 12 10:46:02 shogun kernel: EIP: 0010:[d_lookup+100/288] Not
> tainted
> >>EIP; c0142ca4 <d_lookup+64/120> <=====
> Trace; c013a6b0 <cached_lookup+10/50>
> Trace; c013ade8 <link_path_walk+538/790>
> Trace; c013a48e <getname+5e/a0>
d_lookup oopses are usually signs of bad memory.
Bye,
Oleg
prev parent reply other threads:[~2002-03-13 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 21:08 [OOPS] Reiserfs corruption causing oops in VFS code? (Kernel 2.4.16) Troels Walsted Hansen
2002-03-13 8:32 ` 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=20020313113221.B871@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=troels@thule.no \
/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.