Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760725AbWLIKyi (ORCPT ); Sat, 9 Dec 2006 05:54:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759156AbWLIKyi (ORCPT ); Sat, 9 Dec 2006 05:54:38 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:47353 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760725AbWLIKyh (ORCPT ); Sat, 9 Dec 2006 05:54:37 -0500 Date: Sat, 9 Dec 2006 11:54:36 +0100 From: Jan Kara To: Jim van Wel Cc: linux-kernel@vger.kernel.org Subject: Re: Ext3 Errors... Message-ID: <20061209105436.GB10261@atrey.karlin.mff.cuni.cz> References: <13634.62.194.65.8.1165659510.squirrel@webmail.coolzero.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13634.62.194.65.8.1165659510.squirrel@webmail.coolzero.info> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2466 Lines: 56 Hi, > I have something really strange while running kernel 2.6.19. > > See the following lines: > > Dec 5 23:50:49 kernel: do_get_write_access: OOM for frozen_buffer > Dec 5 23:50:49 kernel: ext3_free_blocks_sb: aborting transaction: Out of > memory in __ext3_journal_get_undo_access > Dec 5 23:50:49 kernel: EXT3-fs error (device md1) in ext3_free_blocks_sb: > Out of memory > Dec 5 23:50:49 kernel: EXT3-fs error (device md1) in > ext3_reserve_inode_write: Readonly filesystem > Dec 5 23:50:50 kernel: EXT3-fs error (device md1) in ext3_truncate: Out > of memory > Dec 5 23:50:51 kernel: EXT3-fs error (device md1) in > ext3_reserve_inode_write: Readonly filesystem > Dec 5 23:50:51 kernel: EXT3-fs error (device md1) in ext3_orphan_del: > Readonly filesystem > Dec 5 23:50:51 kernel: EXT3-fs error (device md1) in > ext3_reserve_inode_write: Readonly filesystem > Dec 5 23:50:51 kernel: EXT3-fs error (device md1) in ext3_delete_inode: > Out of memory > > And three days later the same: > > Dec 8 08:24:29 kernel: do_get_write_access: OOM for frozen_buffer > Dec 8 08:24:29 kernel: ext3_reserve_inode_write: aborting transaction: > Out of memory in __ext3_journal_get_write_access > Dec 8 08:24:29 kernel: EXT3-fs error (device md1) in > ext3_reserve_inode_write: Out of memory > Dec 8 08:24:32 kernel: EXT3-fs error (device md1) in ext3_dirty_inode: > Out of memory > Dec 8 08:24:32 kernel: EXT3-fs error (device md1) in ext3_new_blocks: > Readonly filesystem > Dec 8 08:24:32 kernel: EXT3-fs error (device md1) in > ext3_reserve_inode_write: Readonly filesystem > Dec 8 08:24:32 kernel: EXT3-fs error (device md1) in ext3_dirty_inode: > Out of memory > Dec 8 08:24:32 kernel: EXT3-fs error (device md1) in ext3_prepare_write: > Out of memory > > Now the funny thing is, with kernel 2.6.18.3 I did not had these errors. > Could it be my memory that is just going nuts, or something else? I have > seen some other topics about the EXT3 corruption problems. Maybe this is > also the same thing? Probably some error on the kernel's side. Maybe somebody (e.g. my new code in jbd commit) forgets to release some buffers? What does your /proc/slabinfo look like? Thanks for report. Honza - 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/