Hi, > 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?
Well, that's the most funny thing. It doesn't remount RO, it's still mounted as RW. Like here: /dev/md1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/md0 on /boot type ext3 (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /proc on /var/named/chroot/proc type none (rw,bind) So it doesn't mount it to RO. And yes the system is just up and running. It's a server. So it's on for 24/7. It now only happened for two times when running the kernel 2.6.19. So it even looks like these messages are false, because in all logs, I don't see Segfaults anywhere. And there should be some if the error is really true what is said. Anyway, I cannot trace back this easily as you can see. So what can I do to help with these strange messages? Thanks! 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/
