[lkml]   [2000]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: corruption

    In article <>,
    Andrew Morton <> writes:
    AM> In thread "File corruption part deux", Lawrence Walton wrote:
    >> my system has been acting slightly odd on all the pre 12 kernels
    >> with the fs going read only with out any messages until now.
    >> no opps or anything like that, but I did get this just now.
    >> EXT2-fs error (device sd(8,2)): ext2_readdir:
    >> bad entry in directory #458430: directory entry
    >> across blocks - offset=152, inode=3393794200,
    >> rec_len=12440, name_len=73
    AM> 3393794200 == 0xca493098. A kernel address. And 152 is 0x98,
    AM> which is equal to N * 0x20 + 0x18. Read on...

    Don't know what these do for your analysis, observed on
    2.4.0test12pre2, compiling mozilla.

    EXT2-fs error (device ide0(3,11)):
    ext2_readdir: bad entry in directory #409870: directory entry across blocks
    - offset=88, inode=3284439128, rec_len=36952, name_len=196

    EXT2-fs error (device ide0(3,11)):
    ext2_add_entry: bad entry in directory #344273: rec_len % 4 != 0 - offset=0,
    inode=1769234798, rec_len=28271, name_len=85

    Recompiling it with 2.4.0test12pre3 last night did not cause any fs
    problems, at least that I've noticed.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 12:49    [W:7.222 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site