From owner-freebsd-fs@FreeBSD.ORG Mon Nov 28 02:21:26 2011 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 A94B31065670; Mon, 28 Nov 2011 02:21:26 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5E23E8FC12; Mon, 28 Nov 2011 02:21:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Message-Id:References:In-Reply-To:Subject:To:From:Date:Content-Type:Mime-Version; bh=nu5wCuFJB2x6UzTAvYyJpklGSW8NmseEG6Dk1u/zq+g=; b=YiLnjfIhRY3zod1avQDQ1gYGDef4XaNfrbRCuslWIOiRauxp911nqpYiqWnYHHeXLzIWClDOeOaVoJgzOYHDN+95SMDztj9QT78rpsxjzMgEL6/C3EeHmZj99DThLP0+; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RUqqS-00086j-Ch; Sun, 27 Nov 2011 20:21:25 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1322446878-1863-1862/5/4; Mon, 28 Nov 2011 02:21:18 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Date: Sun, 27 Nov 2011 20:21:18 -0600 From: Mark Felder To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <881f876f-6f27-49fd-b6c7-edbe6493ec75@email.android.com> References: <95d00c1b714837aa32e7da72bc4afd03@feld.me> <20111126104840.GA8794@garage.freebsd.pl> <881f876f-6f27-49fd-b6c7-edbe6493ec75@email.android.com> Message-Id: <820791346f600ea50ff9ebd68e30c059@feld.me> X-Sender: feld@feld.me User-Agent: Roundcube Webmail/0.6 X-SA-Score: -1.0 Cc: Subject: Re: zfs i/o hangs on 9-PRERELEASE 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: Mon, 28 Nov 2011 02:21:26 -0000 After many hours of testing, reproducing, and testing again I've finally been able to narrow down what the real issue is and it's not ZFS as I suspected. After completely turning off all NFS functionality and serving my files over Samba I haven't had a single issue. It seems there is something going on with the new NFS code (I serve out over v4, but reproduced it last week with v3) and my media player box, a Popcorn Hour A-200 which is running Linux. If I can cobble some hardware together and place it between so I can do some tcpdumps I will provide that data so perhaps someone can understand what's going on. If this is due to a badly behaving client this is potentially a DoS on the server. Regards, Mark