From owner-freebsd-threads@freebsd.org Sat Mar 5 12:29:50 2016 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F3AA9DB2EA for ; Sat, 5 Mar 2016 12:29:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 504A6697 for ; Sat, 5 Mar 2016 12:29:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u25CTnSe088052 for ; Sat, 5 Mar 2016 12:29:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Sat, 05 Mar 2016 12:29:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2016 12:29:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #59 from Robert Blayzor --- Thinking about this a little, going out on a limb. The only thing that diff= ers on these servers compared to other diskless boot servers we have. (that use= the same read only NFS root) is they have a larger memory disks for "/var" when created from /etc/rc.initdiskless. /dev/md0 8.8M 3.8M 4.3M 47% /etc /dev/md1 457M 516K 420M 0% /var Because these are mail servers, /var may be a bit busier than on say DNS and web servers. (as /var/tmp is there, etc, temporary file writes from files b= eing scanned by viruses). I've never seen any "out of memory" errors or that mou= nt ever close to being anywhere near full; but I'm sure there are a lot of read/write going on. I know it's a stretch but it's the only thing I can think of that differs f= rom the other diskless servers that are setup the exact same way. This appears to be happening on only our mail servers, which consequently happen to be our busiest. --=20 You are receiving this mail because: You are the assignee for the bug.=