mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jim van Wel" <jim@coolzero.info>
To: linux-kernel@vger.kernel.org
Subject: Ext3 Errors...
Date: Sat, 9 Dec 2006 11:18:30 +0100 (CET)	[thread overview]
Message-ID: <13634.62.194.65.8.1165659510.squirrel@webmail.coolzero.info> (raw)

Hi all,

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?

Thanks for reading.

             reply	other threads:[~2006-12-09 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 10:18 Jim van Wel [this message]
2006-12-09 10:54 ` Jan Kara
2006-12-09 10:57   ` Jim van Wel
2006-12-09 11:34     ` Jan Kara
2006-12-09 11:44       ` Jim van Wel
2006-12-09 11:49         ` Jan Kara
2006-12-09 16:13           ` Jim van Wel
2006-12-11 14:55           ` Jim van Wel
2006-12-17 15:23           ` Jim van Wel
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  0:19 ext3 errors Ferenc Engard
2002-07-01 19:24 EXT3 errors Bongani
2002-07-01 21:38 ` Andrew Morton
2002-07-02  4:15   ` Bongani
2002-07-02 11:35     ` Liakakis Kostas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13634.62.194.65.8.1165659510.squirrel@webmail.coolzero.info \
    --to=jim@coolzero.info \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®