mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jim van Wel" <jim@coolzero.info>
To: "Jan Kara" <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ext3 Errors...
Date: Sun, 17 Dec 2006 16:23:25 +0100 (CET)	[thread overview]
Message-ID: <22316.62.194.74.53.1166369005.squirrel@webmail.coolzero.info> (raw)
In-Reply-To: <20061209114930.GE10261@atrey.karlin.mff.cuni.cz>

Hi all,

As promised, I should notify if no problems would happen. Well, no
problems happened. So when I was running kernel version 2.6.19 the
problems of my previous e-mails did happen, with kernel 2.6.18.1 running
right now, just none of the errors are comming up, and is running
smoothly.

Greetings,

Jim.

>   Hi,
>
>> Well, that's kind of difficult because it looks a little random when he
>> does it, and a interval of three days, but also is maybe random.
>>
>> And the most difficult part is it's only for three seconds, and than
>> it's
>> gone, so making a crontab script every minute might not even notice it?
>   Oh, so the machine does not crash or go totally out of memory when this
> happens? At least it seems the filesystem is remounted RO?
>
> <snip>
>> >> >> 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
>  <snip>
>
> 								Honza
> --
> Jan Kara <jack@suse.cz>
> SuSE CR Labs
>


  parent reply	other threads:[~2006-12-17 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 10:18 Jim van Wel
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 [this message]
  -- 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=22316.62.194.74.53.1166369005.squirrel@webmail.coolzero.info \
    --to=jim@coolzero.info \
    --cc=jack@suse.cz \
    --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®