From owner-freebsd-bugs@FreeBSD.ORG Tue Dec 4 15:32:31 2012 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 303FE89F; Tue, 4 Dec 2012 15:32:31 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 70CFC8FC0C; Tue, 4 Dec 2012 15:32:30 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so4292227lah.13 for ; Tue, 04 Dec 2012 07:32:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=xoOtaq3uJ/w2oPVtdCegaUPGKLf6elti4i18JQPTesM=; b=WYaM3wiiU1+usTtKS2mw21j68PvCvbd5VzDZ4gdIq2Y3SymQXsqnRljfOzbwF19pl2 07pL5Y1NDI4OsUES/ARgWeD8HKsKLBhjNWludeuegJPM9diFO3FBfbxPHjKIUg4mAyAL bRGllo2Q+SAw6inV0gGXvXtIjCdv5bxhiMW75uvrvLXUe9uhnKwMtZUOasQ60/QeivOa oisfY153uc7H4+sJsa+pcObtnzOGt3qrJblJ5+xZ0SEsNuacOjv7ZsO8kCaL55Ia3+a2 US/mAE1vn1y2Kmi6Jfpx+NiQYmeuQHmk6/WEjC4wRJ/hCbCJUuw9oRUSJYMUlayBC773 o0FA== MIME-Version: 1.0 Received: by 10.112.83.133 with SMTP id q5mr6063227lby.40.1354635148847; Tue, 04 Dec 2012 07:32:28 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.114.12.226 with HTTP; Tue, 4 Dec 2012 07:32:28 -0800 (PST) In-Reply-To: <201212021830.qB2IU0ZZ069787@freefall.freebsd.org> References: <201212021820.qB2IKvRU052643@red.freebsd.org> <201212021830.qB2IU0ZZ069787@freefall.freebsd.org> Date: Tue, 4 Dec 2012 16:32:28 +0100 X-Google-Sender-Auth: E9URRGQEpW1ZD8zHAL7OzbGdhuw Message-ID: Subject: Re: misc/174060: Ext2FS system crashes (buffer overflow?) From: CeDeROM To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 15:32:31 -0000 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