From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 21:15:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 121FD106564A for ; Tue, 2 Dec 2008 21:15:00 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id DD2C68FC24 for ; Tue, 2 Dec 2008 21:14:59 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 095101A000B24 for ; Tue, 2 Dec 2008 12:54:26 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id X-TPa-tmd0bM for ; Tue, 2 Dec 2008 12:54:21 -0800 (PST) Received: from coal.localnet (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 90E3B1A000B23 for ; Tue, 2 Dec 2008 12:54:21 -0800 (PST) From: Freddie Cash To: freebsd-current@freebsd.org Date: Tue, 2 Dec 2008 12:54:21 -0800 User-Agent: KMail/1.10.3 (Linux/2.6.26-1-686; KDE/4.1.3; i686; ; ) References: <20081117205526.GC1733@garage.freebsd.pl> <20081202203308.GA13818@hyperion.scode.org> In-Reply-To: <20081202203308.GA13818@hyperion.scode.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812021254.21242.fjwcash@gmail.com> Subject: Re: HEADS UP: New ZFS in the tree. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 21:15:00 -0000 On December 2, 2008 12:33 pm Peter Schuller wrote: > I just upgraded my workstation to CURRENT for the purpose of testing > ZFS. I wanted to report one anomoly that I have seen so far, that I > never saw before and that I do not recognize from other posts. > > I had ktorrent seemingly hang. The process is in state TL, and does > not respond to SIGKILL. SIGCONT also has no effect; neither has > SIGSTOP followed by SIGCONT. > > Though I do not know how ktorrent works internally, the typical > behavior, and behavior that I saw just prior to this hang, is one of > periodically flushing out a lot of (bittorrent, not file system) > blocks. This happens to the point that the pool is more or less > saturated for the duration of these bursts (when downloading quickly; > around 10 MB/sec in this case). So possibly the triggering factor is > quick writing of a lot of randomly located blocks in a handful of > files. Hrm, I wonder if this is what I'm running into with 7.1-PRERELEASE (Nov 17). I'm running a P4 3.0 GHz system w/2 GB RAM, and 3x 200 GB SATA drives in raidz1 config (/ is on USB flash drive, everything else is on ZFS). I'm also running ktorrent. I've noticed the past couple of days, when using the server (not very often), every now and then, the GUI (KDE 4.1) will "hang" for up to 5 minutes (no mouse movement, no keyboard events), while the drives work like crazy. The drives will quiet, and everything will go back to working all nice and snappy. Most noticeable when new torrents start to download (pre- allocate space for new torrents is disabled), or when combined download rate goes above 100 KBps, or combined up/down rate goes above 200 KBps. Unfortunately, when this happens, I can't swith terminals or apps to see what's happening with gstat, zpool stats, vmstat, top, etc. During this "hang" period, network throughput also drops to nil, most noticeable when watching video over Samba/NFS via the laptop in the living room. Movie pauses for up to 2 minutes, then either continues, or the player aborts and starts the next one in the queue. Gets really annoying when it pauses multiple times in a 60-minute video. I figured this was a networking issue, as it only ever affected streaming movies off the server, and have been playing with Samba setting, NFS settings, TCP/IP sysctls, and NIC options on the server and laptop. Never thought to look at ZFS, as it's only been in the last couple days that I noticed the drives working like crazy in burst. Unfortunately, by the time I go from the living room downstairs to the computer room upstairs, things have generally resolved themselves, so I can't say for sure that the pausing video stream is happening at the same time as the drives are working like crazy. loader.conf sets kmem_max to 1 GB, zfs_arc_max to 0.5 GB, and disables ZFS prefetching. All ZFS filesystems have recordsize set to 64 KB; /usr/src and /usr/ports have lzjb compression enabled; all the other filesystems have compression disabled. TCP send and receive buffers are also set to 64 KB. Not sure what to look for, or how to go about debugging this one. Just been living with it. So any and all suggestions, comments, threats, and flames welcomed. :) -- Freddie fjwcash@gmail.com