From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Tobias Bengtsson <tobbe@tobbe.nu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
JFS Discussion <jfs-discussion@www-124.southbury.usf.ibm.com>
Subject: Re: BUG in jfscode
Date: Thu, 05 Feb 2004 15:22:13 -0600 [thread overview]
Message-ID: <1076016133.25034.95.camel@shaggy.austin.ibm.com> (raw)
In-Reply-To: <20040203123709.GB23130@debian.as>
On Tue, 2004-02-03 at 06:37, Tobias Bengtsson wrote:
> Hi!
Hi, Sorry it's taken me so long to respond.
> kernel BUG at fs/jfs/jfs_dmap.c:2686!
I've seen a similar bug reported before, but it occurs only rarely. I'm
not sure what the cause is. My initial thought was the the block map
got corrupted, but after digging through the code I don't know if it's
that simple.
I would be interested if you can recreate the problem. If so, I may be
able to put in some debug code to help determine where JFS is getting
confused. Also, if it is block map corruption, running fsck -f against
the volume should fix that.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2004-02-05 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 12:37 Tobias Bengtsson
2004-02-05 21:22 ` Dave Kleikamp [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=1076016133.25034.95.camel@shaggy.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tobbe@tobbe.nu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®