lkml.org 
[lkml]   [2001]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRAID, 2.4.2 and Buslogic

    Leonard,

    My story is somewhat similar to what Dick Johnson has encountered except
    this is with 2.4.2 running on a pentium 200.

    I encountered an oops last night while untarring a file. Upon reboot, it
    appears that the partition labels disappeared along with the superblock.
    Unfortunately, I was not able to recover and had to redo the setup from
    scratch.


    Here is the lspci output

    deepthought%jauderho% lspci
    00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
    00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01)
    00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
    00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
    00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01)
    00:09.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
    (rev 02)
    00:0b.0 VGA compatible controller: ATI Technologies Inc 210888GX [Mach64
    GX] (rev 01)
    00:0d.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
    (rev 10)
    00:0f.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10] (rev 08)



    Unfortunately, the System.map was deleted during a compile but attached is
    the dmesg output.

    EXT2-fs error (device md(9,0)): ext2_add_entry: bad entry in directory
    #343396:
    inode out of bounds - offset=0, inode=343396, rec_len=12, name_len=1
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 12
    EXT2-fs error (device md(9,0)): free_inode: reserved inode or nonexistent
    inode
    kernel BUG at inode.c:885!
    invalid operand: 0000
    CPU: 0
    EIP: 0010:[<c01425ba>]
    EFLAGS: 00010292
    eax: 0000001b ebx: c2af8ba0 ecx: c373c000 edx: 00000001
    esi: c023b9e0 edi: c38bd017 ebp: c3c285e0 esp: c1877f24
    ds: 0018 es: 0018 ss: 0018
    Process tar (pid: 5383, stackpage=c1877000)
    Stack: c01fd7e5 c01fd865 00000375 c2af8ba0 c13b8f40 c014fa07 c2af8ba0
    ffffffff
    000001fd c3c285e0 c3c28650 c13b8f40 00000007 c3932560 c0138ef7
    fffffffe
    c013a773 c3c285e0 c13b8ee0 000001fd c13b8ee0 c1877fa4 c13b8ee0
    c1e5c000
    Call Trace: [<c014fa07>] [<c0138ef7>] [<c013a773>] [<c013a816>]
    [<c0108de3>]

    Code: 0f 0b 83 c4 0c eb 6f 39 1b 74 3b f6 83 ec 00 00 00 07 75 26
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 474218
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 474219
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 474216

    ...

    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number:
    1062908
    EXT2-fs error (device md(9,0)): ext2_readdir: bad entry in directory
    #310689: in
    ode out of bounds - offset=0, inode=310689, rec_len=12, name_len=1
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 228935
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212584
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212583
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212586
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212588
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212589
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212587
    EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 212585
    EXT2-fs error (device md(9,0)): ext2_find_entry: bad entry in directory
    #883010:
    inode out of bounds - offset=60, inode=245344, rec_len=4036, name_len=16



    --Jauder







    PS. Is there a minimum processor speed requirement to do RAID? I know the
    pentium 200 is pretty wimpy but if this is the failure mode it was
    certainly unexpected.



    -
    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: 2005-03-22 13:29    [W:0.026 / U:118.188 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site