From owner-freebsd-fs@FreeBSD.ORG Tue Oct 12 11:12:33 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFCA4106566C for ; Tue, 12 Oct 2010 11:12:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0DBD68FC16 for ; Tue, 12 Oct 2010 11:12:32 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA16326; Tue, 12 Oct 2010 14:12:29 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1P5cmT-000OOg-8C; Tue, 12 Oct 2010 14:12:29 +0300 Message-ID: <4CB4429C.9040109@icyb.net.ua> Date: Tue, 12 Oct 2010 14:12:28 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <39F05641-4E46-4BE0-81CA-4DEB175A5FBE@free.de> <20101009111241.GA58948@icarus.home.lan> <4CB17983.3020907@icyb.net.ua> <20101011151508.GA10917@icarus.home.lan> <4CB32C75.2060000@icyb.net.ua> <20101011183707.GA13925@icarus.home.lan> <4CB3870F.7070107@icyb.net.ua> <20101012100709.GA29861@icarus.home.lan> In-Reply-To: <20101012100709.GA29861@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Locked up processes after upgrade to ZFS v15 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 11:12:33 -0000 on 12/10/2010 13:07 Jeremy Chadwick said the following: > I've been trying to reproduce this problem on my testbed box without > much luck so far. The box differs severely -- the biggest differences > being the testbed runs i386 (due to CPU), only has 1GB RAM, and is > single-core. I don't have an amd64 testbed system on hand right now. > > I've been trying to reproduce it by enabling Sendfile and MMAP in Apache > on the system, putting up some very large files on an Apache-accessible > ZFS filesystem, and using something like "wget -r" to download > everything. I've been watching "netstat -m" to monitor the number of > sendfile requests. > > There have been a couple cases where I've seen processes go into "zfs" > state, but I have yet to see any lock up. > > Is there something amd64-specific to the problem at hand, or maybe some > VM feature which isn't getting triggered on i386? Or do you know of a > reliable way to reproduce the issue at this point? I don't have an easy way to reproduce it. The theory is that you should sendfile a file with size which is not multiple of page size (4K) and then you should mmap and read the same file; the last step should lock up. Perhaps, tools/regression/sockets/sendfile/sendfile.c with the following patch would reproduce it? http://people.freebsd.org/~avg/sendfile.diff -- Andriy Gapon