From: Matteo Croce Subject: Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted Date: Fri, 22 May 2009 15:25:32 +0200 Message-ID: <40101cc30905220625o987a66eo57b1a52b169d05df@mail.gmail.com> References: <40101cc30905201635t6af2586bne1acbc77216628ee@mail.gmail.com> <4A14AC12.4000108@redhat.com> <40101cc30905220131t48d3de40y89beafb15d9e2201@mail.gmail.com> <4A169C96.1050808@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-ext4@vger.kernel.org To: Eric Sandeen Return-path: Received: from mail-ew0-f176.google.com ([209.85.219.176]:54009 "EHLO mail-ew0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751655AbZEVNZy convert rfc822-to-8bit (ORCPT ); Fri, 22 May 2009 09:25:54 -0400 Received: by ewy24 with SMTP id 24so1831335ewy.37 for ; Fri, 22 May 2009 06:25:54 -0700 (PDT) In-Reply-To: <4A169C96.1050808@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: I haven't the syslog now, but it was normal messages, not ATA related o= r errors On Fri, May 22, 2009 at 2:37 PM, Eric Sandeen wrot= e: > Matteo Croce wrote: >> the HD seems to reset soon. >> can it be an hardware problem? > > It can be, it'd be easier for me to tell you if you could provide any > messages prior to the remount messages, as I'd requested. > > If you see things like ATA errors or resets, then yes, it's likely a > hardware problem. > > But without actual information, I just have to guess.... > > -Eric > >> On Thu, May 21, 2009 at 3:19 AM, Eric Sandeen w= rote: >>> Matteo Croce wrote: >>>> When launching a web browser in normal desktop usage, I get this a= nd >>>> the disk mounted read only: >>>> >>>> [ 1101.535101] EXT4-fs error (device sda1) in >>>> ext4_reserve_inode_write: Journal has aborted >>> Anything before that? =A0I'd think you'd get a message when the jou= rnal >>> aborts. >>> >>>> [ 1101.535114] Remounting filesystem read-only >>>> [ 1101.535622] EXT4-fs error (device sda1) in >>>> ext4_reserve_inode_write: Journal has aborted >>>> [ 1101.535637] EXT4-fs error (device sda1) in ext4_dirty_inode: >>>> Journal has aborted >>>> [ 1101.535669] mpage_da_map_blocks block allocation failed for ino= de >>>> 1867 at logical offset 0 with max blocks 1 with error -30 >>>> [ 1101.535681] This should not happen.!! Data will be lost >>> Hm this is probably a bad followon to the filesystem shutting down,= and >>> delalloc data having nowhere to go... >>> >>> -Eric >>> >>>> [ 1101.535703] ext4_da_writepages: jbd2_start: 1024 pages, ino 186= 7; err -30 >>>> [ 1101.535716] Pid: 26, comm: pdflush Not tainted 2.6.29.1 #12 >>>> [ 1101.535724] Call Trace: >>>> [ 1101.535744] =A0[] ? printk+0x18/0x1c >>>> [ 1101.535862] =A0[] ext4_da_writepages+0x409/0x430 >>>> [ 1101.535879] =A0[] ? ext4_da_get_block_write+0x0/0x210 >>>> [ 1101.535893] =A0[] ? ext4_da_writepages+0x0/0x430 >>>> [ 1101.535907] =A0[] do_writepages+0x2e/0x50 >>>> [ 1101.535921] =A0[] __writeback_single_inode+0x88/0x500 >>>> [ 1101.535936] =A0[] ? set_next_entity+0x97/0x180 >>>> [ 1101.535950] =A0[] generic_sync_sb_inodes+0x283/0x410 >>>> [ 1101.535963] =A0[] writeback_inodes+0x47/0xd0 >>>> [ 1101.535975] =A0[] wb_kupdate+0xb2/0x120 >>>> [ 1101.535988] =A0[] pdflush+0x112/0x1d0 >>>> [ 1101.536000] =A0[] ? wb_kupdate+0x0/0x120 >>>> [ 1101.536160] =A0[] ? pdflush+0x0/0x1d0 >>>> [ 1101.536173] =A0[] kthread+0x3c/0x70 >>>> [ 1101.536184] =A0[] ? kthread+0x0/0x70 >>>> [ 1101.536198] =A0[] kernel_thread_helper+0x7/0x1c >>>> [ 1101.536417] journal commit I/O error >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-ex= t4" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at =A0http://vger.kernel.org/majordomo-info.ht= ml >>> > > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html