lkml.org 
[lkml]   [2013]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ext4_block_to_path block > max warning.
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



\
 
 \ /
  Last update: 2013-03-19 16:01    [W:0.308 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site