From: Andrew Morton <akpm@osdl.org>
To: zensonic@zensonic.dk (Thomas S. Iversen)
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Help tracking down problem --- endless loop in __find_get_block_slow
Date: Wed, 23 Feb 2005 04:10:36 -0800 [thread overview]
Message-ID: <20050223041036.5f5df2ff.akpm@osdl.org> (raw)
In-Reply-To: <20050223120013.GA28169@zensonic.dk>
zensonic@zensonic.dk (Thomas S. Iversen) wrote:
>
> > > dd if=/dev/zero of=/mnt/testfile count=N, N>6
>
> It turns out N>6 is variable. But large enough and it will hang. Sugests
> some kind of race I am afraid.
>
> > > I get into an endless loop in __find_get_block_slow.
> >
> > The only way in which __find_get_block_slow() can loop is if something
> > wrecked the buffer_head ring at page->private: something caused an internal
> > loop via bh->b_this_page.
> >
> > Are you sure that's where things are hanging? That it's not stuck on a
> > spinlock?
>
> I get the same message again and again all over (this trace with
> count=100 and a BUG() and panic inserted into buffer.c)
>
> Feb 23 13:38:34 localhost kernel: __find_get_block_slow() failed.
> block=101, b_blocknr=100
> Feb 23 13:38:34 localhost kernel: b_state=0x00000010, b_size=2048
> Feb 23 13:38:34 localhost kernel: device blocksize: 2048
OK, so we're looking for the buffer_head for block 101 and the first
buffer_head which is attached to the page represents block 100. So the
next buffer_head _should_ represent block 101. Please print it out:
--- 25/fs/buffer.c~a 2005-02-23 04:06:12.000000000 -0800
+++ 25-akpm/fs/buffer.c 2005-02-23 04:06:51.000000000 -0800
@@ -459,8 +459,10 @@ __find_get_block_slow(struct block_devic
*/
if (all_mapped) {
printk("__find_get_block_slow() failed. "
- "block=%llu, b_blocknr=%llu\n",
- (unsigned long long)block, (unsigned long long)bh->b_blocknr);
+ "block=%llu, b_blocknr=%llu, next=%llu\n",
+ (unsigned long long)block,
+ (unsigned long long)bh->b_blocknr,
+ (unsigned long long)bh->b_this_page->b_blocknr);
printk("b_state=0x%08lx, b_size=%u\n", bh->b_state, bh->b_size);
printk("device blocksize: %d\n", 1 << bd_inode->i_blkbits);
}
_
> Ad inf. The output of the BUG() is show below. My questions remain:
>
> 1. Whos fault is this?
Could be UFS. But what does "transparent block encryption and sector
shuffling" mean? How is the sector shuffling implemented?
next prev parent reply other threads:[~2005-02-23 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 10:46 Thomas S. Iversen
2005-02-22 9:18 ` Andrew Morton
2005-02-22 22:46 ` Jeff Mahoney
2005-02-22 23:28 ` Andrew Morton
2005-02-26 0:03 ` Jeff Mahoney
2005-02-28 21:06 ` Jeff Mahoney
2005-02-28 21:09 ` Help tracking down problem --- endless loop in __find_get_block_slow (now with the patch) Jeff Mahoney
2005-02-23 12:00 ` Help tracking down problem --- endless loop in __find_get_block_slow Thomas S. Iversen
2005-02-23 12:10 ` Andrew Morton [this message]
2005-02-23 13:02 ` Thomas S. Iversen
2005-02-23 20:09 ` Andrew Morton
2005-02-23 22:24 ` Thomas S. Iversen
2005-02-23 23:17 ` Andrew Morton
2005-02-24 8:54 ` Thomas S. Iversen
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=20050223041036.5f5df2ff.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zensonic@zensonic.dk \
/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
Powered by JetHome