From: Dave Jones <davej@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: ext4_block_to_path block > max warning.
Date: Tue, 19 Mar 2013 10:21:05 -0400 [thread overview]
Message-ID: <20130319142105.GA1465@redhat.com> (raw)
In-Reply-To: <20130319122244.GA32310@thunk.org>
On Tue, Mar 19, 2013 at 08:22:44AM -0400, Theodore Ts'o wrote:
> On Mon, Mar 18, 2013 at 11:35:55PM -0400, Dave Jones wrote:
> > Not sure what I did to trigger this, but it's happened a few times while fuzzing syscalls.
> > Rebooted and fscked, didn't find anything wrong.
> >
> > [ 5084.436288] EXT4-fs warning (device sda1): ext4_block_to_path:105: block 1874853625 > max in inode 34
> > [ 5167.723925] EXT4-fs warning (device sda1): ext4_block_to_path:105: block 2507988634 > max in inode 34
>
> Yes, this wouldn't be a problem that would be be reflected in an fsck
> problem. What warning indicates is that there was an attempt to write
> to file offset which is larger than what is supported by using
> indirect blocks. (Presumably this was probably a ext3 file system
> mounted using ext4?)
Yeah, think so. That was my /boot partition it wandered into.
Dave
prev parent reply other threads:[~2013-03-19 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 3:35 ext4_block_to_path block > max warning Dave Jones
2013-03-19 12:22 ` Theodore Ts'o
2013-03-19 14:21 ` Dave Jones [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=20130319142105.GA1465@redhat.com \
--to=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).