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 <[EMAIL PROTECTED]> > SuSE CR Labs > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
