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.
Greeti
Hi there,
Well, after I was getting the error again, I now switched back to kernel
2.6.18.1, and going to check if I am getting the same errors. I'll keep
you posted about the progress. If a week have passed and no errors has
shown, I'll e-mail this again.
Thanks!
Jim.
> Hi,
>
>> Well, that's
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)
n
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
Hi there,
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?
Or
Hi,
> Here is the output of /proc/slabinfo
>
> slabinfo - version: 2.1
> # name
> : tunables: slabdata
>
> jbd_4k 5 10 409611 : tunables 24 128
> : slabdata 5 10 0
> ext3_inode_cache 22447 2269696841 : tun
Hi there,
Here is the output of /proc/slabinfo
slabinfo - version: 2.1
# name
: tunables: slabdata
ip_conntrack_expect 0 0136 281 : tunables 120 60
8 : slabdata 0 0 0
ip_conntrack 641 1040304 131 : tunables 54
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
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 kern
On Tue, Aug 23, 2005 at 09:05:27AM -0400, Jess Balint wrote:
> Problem:
> I get massive ext3 errors once every few days. See "errors on console"
> section below. Almost all commands return I/O error. I have to power
> cycle the machine to get it running again. Upon reboot,
Problem:
I get massive ext3 errors once every few days. See "errors on console"
section below. Almost all commands return I/O error. I have to power
cycle the machine to get it running again. Upon reboot, there are
usually 3 orphan inodes deleted and everything is fine. See "mes
11 matches
Mail list logo
