From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error whilst running "tune2fs -j"
Date: Fri, 4 Apr 2003 18:25:36 -0800 [thread overview]
Message-ID: <20030404182536.64e120b2.akpm@digeo.com> (raw)
In-Reply-To: <5750000.1049507953@flay>
"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> > Can you reproduce it?
>
> Not easily, I fear ... since it's a pain in the butt to remove an ext3
> journal on the root fs once mounted. I suppose I could boot from CD
> or something ... will try to recreate on a less valuable box over
> the weekend ;-)
>
> I had been having some other trouble with the fs (power cycled a couple
> of times for silly reasons), but it had just ext2 fscked. I suppose there
> *might* have been some corruption, but seems unlikely.
>
OK. Please add the below to your patchset. I've had this in -mm for *ages*,
precisely because this problem was reported a single time, maybe four months
ago.
I have not had a report of it triggering since then. I'd like to know what
block number it was.
diff -puN fs/buffer.c~buffer-debug fs/buffer.c
--- 25/fs/buffer.c~buffer-debug 2003-04-02 22:24:27.000000000 -0800
+++ 25-akpm/fs/buffer.c 2003-04-02 22:24:27.000000000 -0800
@@ -397,6 +397,9 @@ __find_get_block_slow(struct block_devic
bh = bh->b_this_page;
} while (bh != head);
buffer_error();
+ printk("block=%llu, b_blocknr=%llu\n",
+ (unsigned long long)block, (unsigned long long)bh->b_blocknr);
+ printk("b_state=0x%08lx, b_size=%u\n", bh->b_state, bh->b_size);
out_unlock:
spin_unlock(&bd_mapping->private_lock);
page_cache_release(page);
_
prev parent reply other threads:[~2003-04-05 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 23:25 Error whilst running "tune2fs -j" Martin J. Bligh
2003-04-04 23:56 ` Andrew Morton
2003-04-05 1:59 ` Martin J. Bligh
2003-04-05 2:25 ` Andrew Morton [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=20030404182536.64e120b2.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox