Re: [gentoo-user] Re: ext4 - grow_buffers: requested out-of-range block <BLOCKID>

[Florian Philipp <lists@binarywings.net>]

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Am 12.12.2011 21:33, schrieb James Broadhead:
> On 12 December 2011 14:14, James Broadhead <jamesbroadhead@gmail.com> wrote:
>> ext4: "fill_buffer on unknown block <BLOCKID> out of range"
> 
> Apologies; the correct message is:
> grow_buffers: requested out-of-range block 18446744072382021139 for device sdb1
> 
> This appears 42 times immediately following mount.
> 
> Running picasa today, it informed me that one of the files I was
> working with was corrupted (but put the message in a box too small to
> read the full path).
> 
> This makes me think that perhaps the disk is bad.  Any advice, aside
> from the usual "get your data off asap"?
> 

I've looked at the kernel code that causes the error message. It
verifies that this is most likely a dead disk:

<quote>

commit e5657933863f43cc6bb76a54d659303dafaa9e58
Author: Andrew Morton <akpm@osdl.org>
Date:   Wed Oct 11 01:21:46 2006 -0700

[PATCH] grow_buffers() infinite loop fix

If grow_buffers() is for some reason passed a block number which wants
to lie outside the maximum-addressable pagecache range (PAGE_SIZE * 4G
bytes) then it will accidentally truncate `index' and will then
instnatiate[sic] a page at the wrong pagecache offset.  This causes
__getblk_slow() to go into an infinite loop.

This can happen with corrupted disks, or with software errors elsewhere.

Detect that, and handle it.

</quote>

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]