From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264546AbUBIBre (ORCPT ); Sun, 8 Feb 2004 20:47:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264547AbUBIBre (ORCPT ); Sun, 8 Feb 2004 20:47:34 -0500 Received: from stout.hampshire.edu ([192.33.12.80]:55998 "EHLO stout.hampshire.edu") by vger.kernel.org with ESMTP id S264546AbUBIBr3 (ORCPT ); Sun, 8 Feb 2004 20:47:29 -0500 Date: Sun, 8 Feb 2004 20:47:22 -0500 From: Heriberto A Tejeda To: linux-kernel@vger.kernel.org Subject: Re: could someone plz explain those ext3/hard disk errors Message-ID: <20040209014722.GA22683@stout.hampshire.edu> References: <20040208175346.767881A96E1@23.cms.ac> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040208175346.767881A96E1@23.cms.ac> User-Agent: Mutt/1.3.28i X-message-flag: Please do NOT send HTML e-mail or MS Word attachments - use plain text instead Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I have had the same exact errors.. and i have RMA'ed two disks... already. i just thought it was bad luck.. i power down properly and i dont think its power surges, since i am in school and it only happens to me. i would expect my neighbors to have problems too. -eddie On Sun, Feb 08, 2004 at 06:53:34PM +0100, JG wrote: > hi, > > i'm getting many many disk errors and there already died 4 hard disks (IDE, different vendors) within two months (even the newer ones). i was able to save most of the data, but now even my spare disks are full and since 1 hour the next 2 disks are showing problems. > i don't know if the mainboard, the raid controller or all disks are dying, everything else works fine but it seems very strange that 6 disks die that fast. > > could someone please explain those errors? i know they are many, but i'm completely lost. > > hdi = 200gb maxtor > hdj = 200gb maxtor > hdk = 120gb seagate > mainboard = elitegroup k7s5a > raidcontroller = highpoint rocketraid 404, hpt374 > kernel 2.6.2 > > recently died 3 160gb maxtor and 1 120gb hitachi/ibm > ------------ > init_special_inode: bogus i_mode (76557) > init_special_inode: bogus i_mode (74557) > init_special_inode: bogus i_mode (74557) > EXT3-fs error (device hdf1): ext3_readdir: bad entry in directory #15941633: directory entry across blocks - offset=0, inode=410738721, rec_len=4124, name_len=25 > Aborting journal on device hdf1. > > hdi: task_out_intr: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } > hdi: task_out_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=280923064991615, high=16744319, low=8355711, sector=199145949 > ide4: reset: success > > hdi: drive not ready for command > ide4: reset: master: error (0x7f?) > blk: queue e7ca1800, I/O limit 4095Mb (mask 0xffffffff) > end_request: I/O error, dev hdi, sector 199145948 > Buffer I/O error on device hdi2, logical block 526 > lost page write due to I/O error on hdi2 > end_request: I/O error, dev hdi, sector 57151695 > end_request: I/O error, dev hdi, sector 199141740 > Buffer I/O error on device hdi2, logical block 0 > lost page write due to I/O error on hdi2 > hdk: dma_timer_expiry: dma status == 0x00 > hdk: DMA timeout retry > hdk: timeout waiting for DMA > hdk: status error: status=0x58 { DriveReady SeekComplete DataRequest } > > hdk: drive not ready for command > end_request: I/O error, dev hdi, sector 57151695 > end_request: I/O error, dev hdi, sector 57151695 > EXT3-fs error (device hdi1): ext3_readdir: directory #3571715 contains a hole at offset 0 > Aborting journal on device hdi1. > end_request: I/O error, dev hdi, sector 4271 > Buffer I/O error on device hdi1, logical block 526 > lost page write due to I/O error on hdi1 > end_request: I/O error, dev hdi, sector 63 > Buffer I/O error on device hdi1, logical block 0 > lost page write due to I/O error on hdi1 > ext3_abort called. > EXT3-fs abort (device hdi1): ext3_journal_start: Detected aborted journal > Remounting filesystem read-only > end_request: I/O error, dev hdi, sector 57151695 > EXT3-fs error (device hdi1): ext3_readdir: directory #3571715 contains a hole at offset 0 > end_request: I/O error, dev hdi, sector 57151695 > end_request: I/O error, dev hdi, sector 57151695 > > EXT3-fs error (device hdi2): ext3_readdir: directory #32769 contains a hole at offset 0 > buffer layer error at fs/buffer.c:1262 > Call Trace: > [] mark_buffer_dirty+0x54/0x60 > [] ext3_commit_super+0x51/0x90 > [] ext3_handle_error+0x75/0xb0 > [] ext3_error+0x55/0x60 > [] ext3_readdir+0x4cd/0x500 > [] capable+0x23/0x50 > [] do_brk+0x15d/0x230 > [] vfs_readdir+0x9c/0xa0 > [] filldir64+0x0/0x150 > [] sys_getdents64+0x7b/0xc1 > [] filldir64+0x0/0x150 > [] syscall_call+0x7/0xb > > buffer layer error at fs/buffer.c:2666 > Call Trace: > [] submit_bh+0x1a0/0x200 > [] __set_page_dirty_nobuffers+0x7b/0x90 > [] sync_dirty_buffer+0x5c/0xc0 > [] ext3_handle_error+0x75/0xb0 > [] ext3_error+0x55/0x60 > [] ext3_readdir+0x4cd/0x500 > [] capable+0x23/0x50 > [] do_brk+0x15d/0x230 > [] vfs_readdir+0x9c/0xa0 > [] filldir64+0x0/0x150 > [] sys_getdents64+0x7b/0xc1 > [] filldir64+0x0/0x150 > [] syscall_call+0x7/0xb > > end_request: I/O error, dev hdi, sector 199141740 > Buffer I/O error on device hdi2, logical block 0 > lost page write due to I/O error on hdi2 > ext3_abort called. > EXT3-fs abort (device hdi2): ext3_journal_start: Detected aborted journal > Remounting filesystem read-only > > buffer layer error at fs/buffer.c:1262 > Call Trace: > [] mark_buffer_dirty+0x54/0x60 > [] journal_update_superblock+0x50/0xb0 > [] destroy_inode+0x43/0x70 > [] journal_destroy+0xa9/0x190 > [] ext3_xattr_put_super+0x1e/0x30 > [] ext3_put_super+0x29/0x190 > [] generic_shutdown_super+0xf6/0x110 > [] kill_block_super+0x1d/0x50 > [] deactivate_super+0x48/0x80 > [] sys_umount+0x3f/0x90 > [] sys_oldumount+0x17/0x20 > [] syscall_call+0x7/0xb > > buffer layer error at fs/buffer.c:2666 > Call Trace: > [] submit_bh+0x1a0/0x200 > [] sync_dirty_buffer+0x5c/0xc0 > [] mark_buffer_dirty+0x3b/0x60 > [] journal_update_superblock+0x64/0xb0 > [] destroy_inode+0x43/0x70 > [] journal_destroy+0xa9/0x190 > [] ext3_xattr_put_super+0x1e/0x30 > [] ext3_put_super+0x29/0x190 > [] generic_shutdown_super+0xf6/0x110 > [] kill_block_super+0x1d/0x50 > [] deactivate_super+0x48/0x80 > [] sys_umount+0x3f/0x90 > [] sys_oldumount+0x17/0x20 > [] syscall_call+0x7/0xb > > ------- > hdj: task_out_intr: status=0x51 { DriveReady SeekComplete Error } > hdj: task_out_intr: error=0x04 { DriveStatusError } > hdj: task_out_intr: status=0x58 { DriveReady SeekComplete DataRequest } > hdj: task_out_intr: status=0x51 { DriveReady SeekComplete Error } > hdj: task_out_intr: error=0x51 { UncorrectableError SectorIdNotFound AddrMarkNotFound }, LBAsect=141 > 284313497587, high=8421201, low=5341171, sector=4326 > end_request: I/O error, dev hdj, sector 4319 > Buffer I/O error on device hdj1, logical block 532 > lost page write due to I/O error on hdj1 > hdj: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } > hdj: status error: error=0x51 { UncorrectableError SectorIdNotFound AddrMarkNotFound }, LBAsect=1412 > 84313497471, high=8421201, low=5341055, sector=63 > end_request: I/O error, dev hdj, sector 63 > Buffer I/O error on device hdj1, logical block 0 > lost page write due to I/O error on hdj1 > hdj: no DRQ after issuing WRITE_EXT > > [...] > > thx! > JG > -- eddie tejeda