[lkml]   [2010]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Regular ext4 error warning with HD in USB dock
    On Tue, Dec 28, 2010 at 09:53:45AM +1100, Con Kolivas wrote:
    > Since I moved my internal HD into a USB dock externally and mount the ext4
    > filesystem on it, I regularly get the following errors after it has been
    > mounted for a while (see timecode). It doesn't seem to matter which recent
    > kernel I use.
    > [1048401.773270] EXT4-fs (sde8): mounted filesystem with writeback data mode.
    > Opts: (null)
    > [1048702.736011] EXT4-fs (sde8): error count: 3
    > [1048702.736016] EXT4-fs (sde8): initial error at 1289053677:
    > ext4_journal_start_sb:251
    > [1048702.736018] EXT4-fs (sde8): last error at 1289080948: ext4_put_super:719

    That's actually not an error. It's a report which is generated every
    24 hours, indicating that there has been 3 errors since the last time
    the error count has been cleared, with the first error taking place at
    Sat Nov 6 10:27:57 2010 (US/Eastern) in the function
    ext4_journal_start_sb(), at line 251, and the most recent error taking
    place at Sat Nov 6 18:02:28 2010 (US/Eastern), in the function
    ext4_put_super() at line 719. This is a new feature which was added
    in 2.6.36.

    This information (which is stored in the ext4 superblock) gets cleared
    by e2fsck version 1.41.13 or newer (1.41.14 is the most recently
    released version). If you are using an older version of e2fsck, this
    information won't get cleared, which is not a disaster, although it
    could potentially get annoying. The solution is to simply to upgrade
    to the newest version of e2fsprogs if you are using the 2.6.36 or
    newer kernel.

    The idea behind this feature is to make sure that if there was a file
    system corruption detected, it wouldn't be lost due to log files
    getting overflowed. It's also helpful when users report problems to
    distribution support lines, since it makes it more likely support
    personnel will be able to determine that there has been some file
    system corrutpion issues, perhaps caused by hardware problems, or some
    other cause, including kernel bugs.

    Hope this helps explain what you're seeing!

    - Ted

     \ /
      Last update: 2010-12-28 03:57    [W:0.024 / U:3.020 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site