[lkml]   [2001]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectFile system Corruption with 2.4.16
    Hi there,

    i've experienced very weird behaviour with kernel 2.4.16 ( on at least 2
    different machines with different motherboards & CPUs ).
    I'm having ext2 filesystem problems on both machines now, one is totally
    unusable i need to reinstall it from scratch.
    I've noticed the problem on different points :
    - first lots of problems with symlinks ....
    unable to compile the kernel for example it bails out with "too many
    symlinks levels" ,

    /usr/src/linux/include/asm/pgtable-2level.h: Too many levels of symbolic
    In file included from /usr/src/linux/include/linux/pagemap.h:16,
    from /usr/src/linux/include/linux/locks.h:8,
    from /usr/src/linux/include/linux/devfs_fs_kernel.h:6,
    from init/main.c:16:

    and then looking in /usr/src/linux i saw this :
    /usr/src/linux/include/asm -> asm

    i tried to recreate the link :

    ln -s asm-i386 asm
    ls -l asm
    lrwxrwxrwx 1 root root 3 Dec 1 10:54 asm -> asm

    which is really weird .....
    then i did rm -f asm
    strace ln -s asm-i386 asm
    and then ends shows :
    stat64("asm", 0xbffff950) = -1 ENOENT (No such file or
    lstat64("asm", 0xbffff8e0) = -1 ENOENT (No such file or
    lstat64("asm", 0xbffff8e0) = -1 ENOENT (No such file or
    symlink("asm-i386", "asm") = 0
    _exit(0) = ?

    but ls -l asm shows again :
    lrwxrwxrwx 1 root root 3 Dec 1 10:55 asm -> asm

    - second : i had my mailserver running on one of the boxes and i stoped
    receiving mails about 2 days ago, looking a the logs i found this on all
    the incoming messages :
    fB1IY3801640: SYSERR(root): cannot rename(./tffB1IY3801640,
    ./qffB1IY3801640), uid=0: No such file or directory
    in my mailqueue dir all the tXX files where there, i renamed them to
    qXXX and sendmail was able to process them.

    I backtracked to kernel 2.4.14 and now after doing an fsck on all my
    partitions ( only one problem reported on /home ) , everything is back
    to normal.

    I've read that there was a filesystem problem in 2.4.15 that is supposed
    to be fixed in 2.4.16.
    These 2 machines did run 2.4.15 from it's birtday until 2.4.16 was born
    so maybe the problem was created in 2.4.15 but showed up in 2.4.16 ...
    If someone has an explanation to this behaviour, i would be really happy

    Charles-Edouard Ruault

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:13    [W:0.024 / U:24.624 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site