From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ext4 - grow_buffers: requested out-of-range block <BLOCKID>
Date: Mon, 12 Dec 2011 14:55:30 -0600 [thread overview]
Message-ID: <CAEH5T2Mpi2r015zUVaCEjOObOeps2V6tRq4ydeV2kfO8cEuB2Q@mail.gmail.com> (raw)
In-Reply-To: <CA+hid6G=-JzMojgVu6a7b2hQNo8_Wboih=m7uc=PYGmzzn-OLA@mail.gmail.com>
On Mon, Dec 12, 2011 at 2:33 PM, James Broadhead
<jamesbroadhead@gmail.com> wrote:
> 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"?
Does it happen to be a >2TB USB drive? I remember reading about
problems with some of those. It works in Windows with the factory
partition/FAT tables because of tricks they do to the addressing that
works in Windows, but once you reformat it you can't access the >2TB
areas. Something like that... As far as I recall, you could
repartition to create a 2TB or smaller partition and that would work,
but then the rest of the drive was inaccessible.
next prev parent reply other threads:[~2011-12-12 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 20:33 [gentoo-user] Re: ext4 - grow_buffers: requested out-of-range block <BLOCKID> James Broadhead
2011-12-12 20:55 ` Paul Hartman [this message]
2011-12-13 0:03 ` James Broadhead
2011-12-13 0:23 ` Paul Hartman
2011-12-13 9:52 ` James Broadhead
2011-12-13 3:04 ` Walter Dnes
2011-12-13 10:01 ` James Broadhead
2011-12-12 21:52 ` Florian Philipp
2011-12-12 22:44 ` Adam Carter
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=CAEH5T2Mpi2r015zUVaCEjOObOeps2V6tRq4ydeV2kfO8cEuB2Q@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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