[Bug 32482] New: "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[Bug 32482] New: "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482

           Summary: "htree_dirblock_to_tree:586: inode 260099: block
                    1056737" message after every boot
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.38.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: egokillsall@gmail.com
        Regression: No


Created an attachment (id=53012)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=53012)
kernel .config

Hello!

After each system boot this message pops:

kernel: EXT4-fs (sda10): error count: 5
kernel: EXT4-fs (sda10): initial error at 1301325048:
htree_dirblock_to_tree:586: inode 260099: block 1056737
kernel: EXT4-fs (sda10): last error at 1301325083: htree_dirblock_to_tree:586:
inode 260099: block 1056737

Strange thing is that the message pops 5 minutes right after everything settle.
It is clearly visible in the attached syslog. The machine is a Fujitsu-Siemens
Lifebook C1020, the OS is Debian Testing. sda10 is the last ~7GB partition on
the 120GB disk.
This is almost a fresh install, up since a week or such and the message was
there right since with the install, with the default kernel 2.6.32.5.
Tried to boot with acpi disabled, without 'lapic' (as it needs anyway to enable
it) and removing most of the modules right after booting, tried in recovery
mode, single mode, but no luck. The message just comes after 5 mins. But what
is waiting for 5 mins then tries to tamper like from 'outside' with a mounted
file system?
The thing should be kernel (and/or Bios) related as it seems, maybe something
with the well reputed Via chipset? (Irony)
Any help would be much appreciated.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #1 from Tom <egokillsall@gmail.com>  2011-04-01 21:30:31 ---
Created an attachment (id=53022)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=53022)
dmesg

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #2 from Tom <egokillsall@gmail.com>  2011-04-01 21:31:35 ---
Created an attachment (id=53032)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=53032)
lsmod right after booting

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #3 from Tom <egokillsall@gmail.com>  2011-04-01 21:32:28 ---
Created an attachment (id=53042)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=53042)
part of syslog with the error message

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482


Tom <egokillsall@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|All                         |i386




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #4 from Tom <egokillsall@gmail.com>  2011-04-01 21:50:41 ---
Forgot to tell that Memtest86+ 4.20 passes, however i didn't leave it on for a
night to run or so. I will let it a go tonight.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482


Eric Sandeen <sandeen@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@redhat.com




--- Comment #5 from Eric Sandeen <sandeen@redhat.com>  2011-04-01 23:24:10 ---
ext4 now has the helpful feature of reminding you about errors it encountered
in the past, and doing so on a regular basis.

Isn't that a helpful message?  ;)  I think it gets truncated.

I think it came out of:
584                 if (ext4_check_dir_entry(dir, NULL, de, bh,
585                                 (block<<EXT4_BLOCK_SIZE_BITS(dir->i_sb))
586                                          + ((char *)de - bh->b_data))) {


have you tried running e2fsck -f on the filesystem?  Looks like you have a
problem in a directory.

-Eric

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #6 from Tom <egokillsall@gmail.com>  2011-04-02 07:58:08 ---
Thanks for your input Eric; yes, fsck is happy all the time (also with -fcc
flags). Find -xdev -inum 260099 shows nothing either, but in the past there was
possibly something there, so it makes sense regarding 'past stuff reminder'.
Anyway it would be *a bit more helpful* if it would tell us something about
it's *cool* behaviour, or at least some hint about some action I'd be able to
pop to clean things up.
De ja vu in the aspect of SMART, because n-2 of my n drives suffer from lovely
errors like 'uncorrectable' (because of bad cabling what got solved of course)
and 'write_dma' (right after I pulled the laptop out of the factory sealed box)
and such.
However this drive is one out of the ones without any error, and the long
self-test ran on it shows zero faults.
Memtest also passes all the time. At night.

Anything I can do to 'reset' this thing, or maybe some other recommendation I
should give a go?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

Re: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[Ted Ts'o]

This message will get reset if you use the e2fsck from e2fsprogs
1.41.13 or later.  I recommend using e2fsprogs 1.41.14.

You can translate the "initial error" and "last error" time stamps in
the kernel messages here:

kernel: EXT4-fs (sda10): error count: 5
kernel: EXT4-fs (sda10): initial error at 1301325048: htree_dirblock_to_tree:586: inode 260099: block 1056737
kernel: EXT4-fs (sda10): last error at 1301325083: htree_dirblock_to_tree:586:
inode 260099: block 1056737

via the date command:

% date --date=@1301325048
Mon Mar 28 11:10:48 EDT 2011

% date --date=@1301325083
Mon Mar 28 11:11:23 EDT 2011

(We use seconds since the epoch because we don't want to put time zone
conversion routines in the kernel.)

In any case, it's not a big deal, and you can fix this easily by
upgrading to a newer version of e2fsprogs.

							- Ted

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #7 from Tom <egokillsall@gmail.com>  2011-04-02 08:09:06 ---
Oh well, just got a SIGSEGV from aptitude.. Reboot and everything is fine
again. Something can be incompatible with something in this laptop I feel..

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482





--- Comment #8 from Theodore Tso <tytso@mit.edu>  2011-04-03 03:43:57 ---
This message will get reset if you use the e2fsck from e2fsprogs
1.41.13 or later.  I recommend using e2fsprogs 1.41.14.

You can translate the "initial error" and "last error" time stamps in
the kernel messages here:

kernel: EXT4-fs (sda10): error count: 5
kernel: EXT4-fs (sda10): initial error at 1301325048:
htree_dirblock_to_tree:586: inode 260099: block 1056737
kernel: EXT4-fs (sda10): last error at 1301325083: htree_dirblock_to_tree:586:
inode 260099: block 1056737

via the date command:

% date --date=@1301325048
Mon Mar 28 11:10:48 EDT 2011

% date --date=@1301325083
Mon Mar 28 11:11:23 EDT 2011

(We use seconds since the epoch because we don't want to put time zone
conversion routines in the kernel.)

In any case, it's not a big deal, and you can fix this easily by
upgrading to a newer version of e2fsprogs.

                            - Ted

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482


Tom <egokillsall@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |PATCH_ALREADY_AVAILABLE




--- Comment #9 from Tom <egokillsall@gmail.com>  2011-04-03 09:48:32 ---
Thanks Ted, it was purged by e2fsprogs 1.41.14-1 from Debian experimental. The
rare stuff 'just did read a file but it contains something else now' is still
up, but this is another thing, however I'm sure now it was the cause of all the
fs errors. I'll try and tweak with hdparm and module options (if any) to get to
some more compatible controlling level.
Case closed, thanx a lot!

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=32482


Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
                 CC|                            |tytso@mit.edu
         Resolution|PATCH_ALREADY_AVAILABLE     |UNREPRODUCIBLE




--- Comment #10 from Theodore Tso <tytso@mit.edu>  2011-04-04 14:14:37 ---
OK, so I'll close this bug as a hardware error.  If you can get something
reproducible that you think points this at being a file system bug, please
reopen this bug.  Thanks!!

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.