From owner-freebsd-current@freebsd.org Wed Jul 6 08:08:56 2016 Return-Path: Delivered-To: freebsd-current@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 411A5B73969 for ; Wed, 6 Jul 2016 08:08:56 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 CA6AA1782 for ; Wed, 6 Jul 2016 08:08:55 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x233.google.com with SMTP id r201so181911928wme.1 for ; Wed, 06 Jul 2016 01:08:55 -0700 (PDT) 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; bh=pJkswIuK8LfxXPs2QycHXVQfY24utcRhdz2GpCXthTs=; b=IrR77NyaRAXiJkgOZYj90FS8+HPYromX4KeHWGZOya8g0tTG5MeTavDA4UJIvRgYQA 8CudkSUdXbmJfOIhK21J2SGWKA5bIoi131dDAbDn54IpkT/qKYt8NjOM5irvc0jevsNr UcGi3Z5qncs5eKPUuMnj0QFbO4lihiknGqsq8B6kfrMDMli0Ju9j60wzzTAiwqW8+mSn fsjnLrr2r9As+gk6s9ItGZOQz8j5iqCYtKBysRx2oJlkoeEi10+hoI+4mMwt/blnrSg8 KUzJz6FyEwG7F9Zs/VzaWAkxtwc6drjpUkP+K5szyUZCF+M10qyuk7i7sdcgc6t/yVRV tT4Q== 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; bh=pJkswIuK8LfxXPs2QycHXVQfY24utcRhdz2GpCXthTs=; b=eM5nJV2biKLpiGKT0eM8jrHp+Sru5iHBbnkIYMVvuVw3civYCJS8I8uRYEquvOuqrl FdyoOc+kPHG3wTgJNtjCfRSaxUE1PMub2mMgpgUEtQ/fh8FuIh9bkJ0KcU8uOlYKfYDa HuSritKTHejc5a7u1G+6L5a81lsKR1ZI/5HMZJ7jHkK2Exs7AOijjxzTb+s1WnQfrqZ1 opWz8SMSYyH61nItA6uZ5IlAuN/qXjiz/krJzfunamHDLFgcA5QotkpNWuPoKDEFJAwY UGRYKr2uwehcqHojQ5b+XOgVECNrDH1rpg3zTMZoJe5EMqBczA4qVsARum9T9HK9nQSM 2lGw== X-Gm-Message-State: ALyK8tI8HQWePDm3804J2Kk6YZzzj2n3hvsmni63+qVDH8HxRLQTTf54WLowKreSkkJI84Y6 X-Received: by 10.28.54.134 with SMTP id y6mr18958785wmh.96.1467792533536; Wed, 06 Jul 2016 01:08:53 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id e69sm4777401wma.2.2016.07.06.01.08.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jul 2016 01:08:52 -0700 (PDT) Subject: Re: Setting sysctl vfs.zfs.arc_max failed: 22 To: freebsd-current@freebsd.org References: <975e5ae2-2090-94cd-49c0-eee9866ff02b@freebsd.org> <145180d1-43c9-d894-9221-b210d641955d@freebsd.org> From: Steven Hartland Message-ID: Date: Wed, 6 Jul 2016 09:08:58 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <145180d1-43c9-d894-9221-b210d641955d@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Wed, 06 Jul 2016 08:08:56 -0000 On 06/07/2016 02:25, Allan Jude wrote: > On 2016-07-05 20:27, Steven Hartland wrote: >> Ahh right, let me check that. >> >> On 06/07/2016 00:51, Nathan Bosley wrote: >>> I actually have this same problem. >>> I'll send more details when I get home later. >>> >>> I think the problem started for me after r302265. >>> Before that, I can set vfs.zfs.arc_max and vfs.zfs.arc_min in >>> loader.conf. >>> After r302265, setting either vfs.zfs.arc_max or vfs.zfs.arc_min in >>> loader.conf results in the EINVAL errors in 'dmesg': >>> >>> Setting sysctl vfs.zfs.arc_max failed: 22 >>> Setting sysctl vfs.zfs.arc_min failed: 22 >>> >>> But setting vfs.zfs.arc_meta_limit in loader.conf works fine. >>> >>> But I did notice that using 'sysct' or sysctl.conf for vfs.zfs.arc_max >>> and vfs.zfs.arc_min works. >>> I only have problems with setting them now in loader.conf. >>> >>> Like I said, I'll try to send output from my setup later. >>> >>> Thanks. >>> >>> On Tue, Jul 5, 2016 at 6:10 PM, Steven Hartland >>> > wrote: >>> >>> What is it currently? >>> >>> Just had a quick play here: >>> sysctl vfs.zfs.arc_max >>> vfs.zfs.arc_max: 32283127808 >>> sysctl vfs.zfs.arc_max=32283127807 >>> vfs.zfs.arc_max: 32283127808 -> 32283127807 >>> sysctl vfs.zfs.arc_max=32283127808 >>> vfs.zfs.arc_max: 32283127807 -> 32283127808 >>> >>> Error 22 = EINVAL so I suspect you're requesting a value which one >>> of the following: >>> * < arc_abs_min >>> * > kmem_size >>> * < arc_c_min >>> * < zfs_arc_meta_limit >>> >>> Regards >>> Steve >>> >>> On 05/07/2016 22:56, Eric van Gyzen wrote: >>> >>> Steven and -current: >>> >>> I just updated to r302350 with a GENERIC kernel config. I see >>> this in >>> dmesg: >>> >>> VT(efifb): resolution 1024x768 >>> Setting sysctl vfs.zfs.arc_max failed: 22 >>> CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz >>> (3491.98-MHz K8-class >>> CPU) >>> >>> The relevant parts of /boot/loader.conf are: >>> >>> zfs_load="YES" >>> vfs.zfs.arc_max="6442450944" >>> >>> Let me know what other information you need. >>> >>> Cheers, >>> >>> Eric >>> > > I think the issue might be that the default value of arc_min is higher > than when the user is trying to set arc_max to. In that case we might > want sysctl to lower arc_min instead of giving an error? > > It would definitely be a POLA violation to have to set arc_min lower to > be able to have existing lines that set arc_max in loader.conf work > correctly. > I'm actually thinking its because the initial calculation hasn't occurred yet. This is not apparent on 10 because the tunable and the sysctl are separate. I'm waiting for my head box to rebuild ATM and will check when that's done. Regard Steve