Date: Tue, 4 Dec 2012 16:32:28 +0100 From: CeDeROM <cederom@tlen.pl> To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: misc/174060: Ext2FS system crashes (buffer overflow?) Message-ID: <CAFYkXj=Bih1XJm_B8VAJAcpJM5Scszp2yCUHkmjj8nZo=k=PcQ@mail.gmail.com> In-Reply-To: <201212021830.qB2IU0ZZ069787@freefall.freebsd.org> References: <201212021820.qB2IKvRU052643@red.freebsd.org> <201212021830.qB2IU0ZZ069787@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It got worse, now the system crash on single file save :-( Maybe this is not the reason but the address/location number is printed as negative value... Is there any way to see why this happens? Maybe some backtrace from kernel dump? I noticed some time ago that the filesystem was too big to handle so many files, some sort of inodes exhaustion, so I have removed lots of unnecessary files and it was fine for some time. Should I increase bytes-per-inode and/or number of inodes? Any hints are welcome :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXj=Bih1XJm_B8VAJAcpJM5Scszp2yCUHkmjj8nZo=k=PcQ>