From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kara Subject: Re: 2.6.33-rc4-mmotm0113 - ext3 throws warning.. Date: Tue, 19 Jan 2010 00:33:52 +0100 Message-ID: <20100118233352.GA6352@atrey.karlin.mff.cuni.cz> References: <20914.1263776885@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Andreas Dilger , Theodore Ts'o , linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org To: Valdis.Kletnieks@vt.edu Return-path: Content-Disposition: inline In-Reply-To: <20914.1263776885@localhost> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Hi, > Took a power hit earlier in the day, laptop rode it out, external 500G SUB > drive didn't. Several hours later I finally do something that references > the filesystem on the external drive, and I get: > > [312252.610201] EXT3-fs error (device sdb2): ext3_get_inode_loc: unable to read inode block - inode=5964029, block=23855121 > [312252.610740] ------------[ cut here ]------------ > [312252.610759] WARNING: at fs/buffer.c:1181 mark_buffer_dirty+0x65/0xdd() > [312252.610768] Hardware name: Latitude E6500 > [312252.610776] Modules linked in: ppp_async sunrpc usb_storage [last unloaded: microcode] > [312252.610808] Pid: 2256, comm: ls Not tainted 2.6.33-rc4-mmotm0113 #1 > [312252.610816] Call Trace: > [312252.610836] [] warn_slowpath_common+0x77/0x8f > [312252.610849] [] warn_slowpath_null+0xf/0x11 > [312252.610862] [] mark_buffer_dirty+0x65/0xdd > [312252.610875] [] ext3_commit_super.clone.0+0x54/0x64 > [312252.610889] [] ext3_handle_error+0x90/0xb7 > [312252.610902] [] ext3_error+0x76/0x81 > [312252.610918] [] __ext3_get_inode_loc+0x261/0x287 > [312252.610932] [] ext3_get_inode_loc+0x1a/0x1c > [312252.610945] [] ext3_reserve_inode_write+0x28/0x82 > [312252.610958] [] ext3_mark_inode_dirty+0x38/0x55 > [312252.610971] [] ext3_dirty_inode+0x6a/0x81 > [312252.610986] [] __mark_inode_dirty+0x2f/0x14c > [312252.610999] [] touch_atime+0x102/0x125 > [312252.611014] [] ? filldir+0x0/0xcb > [312252.611027] [] vfs_readdir+0x8a/0xb1 > [312252.611040] [] sys_getdents+0xa6/0xf8 > [312252.611057] [] system_call_fastpath+0x16/0x1b > [312252.611067] ---[ end trace e506d3eb52cbaab0 ]--- > [312252.611138] EXT3-fs (sdb2): error in ext3_reserve_inode_write: IO failure > [312257.701924] journal_bmap: journal block not found at offset 84 on sdb2 > [312257.701937] Aborting journal on device sdb2. > > It was totally in its rights to abort the journal. The WARNING, not so much? Yeah, this is a known problem that buffer_uptodate flag gets cleared on IO error and so if we ever try to mark that buffer dirty again, we get this warning... It's harmless but annoying I agree. Honza -- Jan Kara SuSE CR Labs