lkml.org 
[lkml]   [2006]   [Feb]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: fsck: i_blocks is xxx should be yyy on ext3
    From
    Date
    On Wed, 2006-02-08 at 22:53 -0800, Andrew Morton wrote:
    > Helge Hafting <helge.hafting@aitel.hist.no> wrote:
    > >
    > > Today I rebooted into 2.6.16-rc2-mm1. Fsck checked a "clean" ext3 fs,
    > > because it was many mounts since the last time.
    > >
    > > I have seen that many times, but this time I got a lot of
    > > "i_blocks is xxx, should be yyy fix?"
    > >
    > > In all cases, the blocks were fixed to a lower number.
    >
    > Yes, thanks. It's due to the ext3_getblocks() patches in -mm. I can't
    > think of any actual harm which it'll cause.
    >
    > To reproduce:
    >
    > mkfs
    > mount
    > dbench 32
    > <wait 20 seconds>
    > killall dbench
    > umount
    > fsck
    > -

    Sorry about the late response. I failed to reproduce the problem with
    above instructions. I am running 2.6.16-rc2-mm1 kernel, played dbench
    32 ,64 and 128, and tried both 8 cpu and 1 cpu, still no luck at last. I
    am using e2fsck version 1.35 though. What versions you are using?


    Thanks!

    Mingming


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-02-16 01:47    [W:0.022 / U:30.460 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site