From owner-freebsd-fs@freebsd.org Fri Feb 19 12:29:40 2016 Return-Path: Delivered-To: freebsd-fs@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 08891AADFD7 for ; Fri, 19 Feb 2016 12:29:40 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9616719F6 for ; Fri, 19 Feb 2016 12:29:39 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22e.google.com with SMTP id a4so68490060wme.1 for ; Fri, 19 Feb 2016 04:29:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=3a7490QJPajESWeUTEMOF93kQJdP+NobdJRolpjUdeI=; b=g+9dB2ujhVvfJY1dDCYpepcKylWCc2URgmre/7ckvXe+jmt+6wRhJaat2ryquZwlHf Y5xrD/3NdQ/BXPSNoXekrkWrYVW7tcXY8PvgTuBE3cWUlAo7YpWhnpcCrX7x8oI90SkY rucJR2qrqLBGyW0P8KijVhVK6keTgaxK8rN82Vi3aewTwWDJf97tNUVMheAeUpfD2VMY bARQjZKnIZ4et7V5K/eTLG/ZxQo6kLkmQgDjQrNkf3jnSZgJyNcuclx1+0PLfs9e8xb/ Ncdtl1xr3/YugZUJBw0hlez4Le1lRnp+Y6D6qfNLp7MvgAuSIdtKeWmrSYk2mN2bPxuE aE+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=3a7490QJPajESWeUTEMOF93kQJdP+NobdJRolpjUdeI=; b=jKSrebUFfiwqscftu21fC2sjhE75v2ca0w1+++hkz1KeejEis6seMar40LSHvA8RTK 2hmvggfw2ElrFC4tNfFziJzA22CDPgLy/tW6B0H5xQiNN6Z37j9m3ggqDColW+W7pKpl etCUsFV0z5KhZxsNyL9Kqn+fPv4EEQjDP7so7RsKDpgmWXYGFz4KNrFkkAob/yeNwhry MQY4jKLwMCXxr0HFoHgFmnr5IPsa20vd6gHkdeiFo6nsZPWau+NFnj/MvnTvA7o8lgiv 5htgSMjmYLlUxLM2gxYH69MObOEhMdxc0HaIEQLFVo75+sHdxfguxmVqrAFZXqQqHeGx yG9A== X-Gm-Message-State: AG10YOS3DHeuCmrtkEkG5oBnQHaTsJ0fzHOtd2CR6lBBMuqLx0p5E3mPvjll+1SL5Yz31kqz X-Received: by 10.28.129.10 with SMTP id c10mr8625229wmd.35.1455884978161; Fri, 19 Feb 2016 04:29:38 -0800 (PST) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id s2sm11023038wjs.39.2016.02.19.04.29.36 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 19 Feb 2016 04:29:36 -0800 (PST) Subject: Re: Zfs heavy io writing | zfskern txg_thread_enter To: freebsd-fs@freebsd.org References: <56C70365.1050800@sorbs.net> From: Steven Hartland Message-ID: <56C70AB0.6050400@multiplay.co.uk> Date: Fri, 19 Feb 2016 12:29:36 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56C70365.1050800@sorbs.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 12:29:40 -0000 On 19/02/2016 11:58, Michelle Sullivan wrote: > Niccolò Corvini wrote: >> Hi, first time here! >> We are having a problem with a server running FreeBsd 9.1 with ZFS on a >> > You should upgrade to a supported version first... 9.3 would probably > be the best (rather than 10.x) as it's still supported and uses the same > ABI (ie you should need to reinstall all your ports/packages - though > you should because it sometimes breaks things - at least check for > broken things :) .) > > If you're not familiar "freebsd-update -r 9.3-RELEASE upgrade" will help > you do it without too many problems. 9.3 is still ancient, and while "supported" its not in active development, and to be blunt no one will be interested in helping to diagnose any actual issue on something so old. 10.x has a totally different ZFS IO scheduler for example, so its differently for most workloads. > >> single sata drive. Since a few days ago, in the morning the system becomes >> really slow due of a really heavy io writing. We investigated and we think >> it might start at night, maybe correlated to to crondaily (standard) but we >> are not sure. After a few hours the situation returns to normal. >> > Yeah this sounds like something I am quite familiar with... It's the > security check cronjob that runs every day... its looking for any > setuid/setgid files, new/modified files...etc... across all file systems This is quite likely, so while updating to 10 may not fix the issue running on 9.x. Be aware that 10.3-BETA2 has a known issue related to vnode memory usage which can be triggered by such workloads so trying BETA3 when released, which should address this would be a good idea. Regards Steve