From owner-freebsd-stable@FreeBSD.ORG Mon Jul 16 13:24:09 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1CFA1065672 for ; Mon, 16 Jul 2012 13:24:09 +0000 (UTC) (envelope-from gmx@ross.cx) Received: from www81.your-server.de (www81.your-server.de [213.133.104.81]) by mx1.freebsd.org (Postfix) with ESMTP id 7F95B8FC08 for ; Mon, 16 Jul 2012 13:24:09 +0000 (UTC) Received: from [92.76.69.32] (helo=michael-think) by www81.your-server.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.74) (envelope-from ) id 1SqlHO-000869-JR for freebsd-stable@freebsd.org; Mon, 16 Jul 2012 15:24:02 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Mon, 16 Jul 2012 15:23:57 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Michael Ross" Message-ID: User-Agent: Opera Mail/12.00 (Win32) X-Authenticated-Sender: gmx@ross.cx X-Virus-Scanned: Clear (ClamAV 0.97.3/15138/Mon Jul 16 00:46:06 2012) Subject: 8.2 ->8.3 regression on disk writes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 13:24:09 -0000 Hello, using 8.2 the machine runs fine, using 8.3 or higher, not so much. In laymans terms, if I do "too many" writes/time just once, the machine can't do any disk access for a couple of hours. As in: What's already running stays running, no crashes or anything, but as soon as I need to read from disk (login, start program not cached in memory from previous run), I'm all out of luck. I killed the testing ftp-transfer about 15 seconds after the transfer speed dropped, now I'm waiting for 10+ minutes for ``top'' to start. I can install ports and kernels and world fine, but "ezjail-admin install" or transferring a few GB of files from another machine sends it to limbo. The next step would likely be to go through the kernel changes between 8.2 and 8.3 to narrow it down, I'd appreciate pointers as to what kernel changes to look out for, or other suggestions on what to do. Verbose dmesg: http://gurder.ross.cx/misc/dmesg.txt TIA, Michael Postscript: That's the same problem I wrote about in "Trouble with gmirror and device ada", turns out using gmirror just makes the problem appear much faster as opposed to eventually.