From owner-freebsd-current@freebsd.org Wed Jul 6 06:20:59 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 2D71AB71D35 for ; Wed, 6 Jul 2016 06:20:59 +0000 (UTC) (envelope-from nathan.bosley@gmail.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 DC14917CC; Wed, 6 Jul 2016 06:20:58 +0000 (UTC) (envelope-from nathan.bosley@gmail.com) Received: by mail-yw0-x22a.google.com with SMTP id i12so79465692ywa.1; Tue, 05 Jul 2016 23:20:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=51GdmyS+WRko926CMB6yyhovroZYM+bKOA/BwF4pUus=; b=MbelQ6uvlXCKAtIg+waiqfz+OrLEUr9ISGyzErkiRZeYtYfbCEvDctkiGVnu23QaVx 7Rw7IliIV2zuqm4vdoRt1MpiBJapgjMk8v7nhAYoLY2ncjojAqtiCE3Pl4c1Fm273Qtm F6shOzR46jjnI7XJOpM4mII4iWwwTngcPI2bM12fr/AR6Y/QQf57s+8nlIXp0Ukjb9Id ZQ+c3imBRsELvc3mBBNv/qSonTxUoGUnswPgXfIFSmgByMRaLyGxhXCQI997d5jKjLVf uPoqEapH8NGdr2+32s7kzOgQwYiWqjQV1OqBRYEQOdFb9Vh2x4/bWfJMdPIPiuDO3lnd me0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=51GdmyS+WRko926CMB6yyhovroZYM+bKOA/BwF4pUus=; b=htnGYGskQEOIFMEBWYbW3ASr7svLRrKSVsMlH+KtsviEwoO6w6/xPJD0w1476wIxu9 FygQvlbPH3iA4Pb/rTMKnBIB85ACZ2cC4abVsHtqBGx6vTOHMT0P1hG3bqxOKJax8YMb eM/GQooUo+iyeAvYTq9Ltry6KjRHMfmcMLzxwqYpJThdsgeQ2NB+y3yeZaxyj8VpelEu WUk6a98niszzSjJqZbm/nWmeTUCAn+GNOvtsmgrpVjMhmBv00F1jVrWKERupLGeLn9Nn CAdfqfNQz8Hu+ytmwwcBmOdGDOfujZoMCkO8+qK3Q90okdNqDfnZbYxbacaWl5wqBPcz hXQQ== X-Gm-Message-State: ALyK8tIE3xVSxGAO2Xw/OKGCH4ftBdKxce9L/PErMFADfq/ZZsjf9pz1IbgzwWf0C0JNCA9/bfLJUgRhBwTamA== X-Received: by 10.13.196.131 with SMTP id g125mr1443028ywd.183.1467786057787; Tue, 05 Jul 2016 23:20:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.97.8 with HTTP; Tue, 5 Jul 2016 23:20:57 -0700 (PDT) In-Reply-To: References: <975e5ae2-2090-94cd-49c0-eee9866ff02b@freebsd.org> <145180d1-43c9-d894-9221-b210d641955d@freebsd.org> <7255f240-8cf0-0a62-89be-2a0970b67063@freebsd.org> From: Nathan Bosley Date: Wed, 6 Jul 2016 02:20:57 -0400 Message-ID: Subject: Re: Setting sysctl vfs.zfs.arc_max failed: 22 To: Allan Jude Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 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 06:20:59 -0000 Maybe I misunderstood after all. I took this: "You can work around it temporarily by setting a lower arc_min first." To mean that I could do something like: vfs.zfs.arc_min="1073741824" vfs.zfs.arc_max="8589934592" in loader.conf, which would circumvent the problem. But with the above, in that order, I still get: Setting sysctl vfs.zfs.arc_max failed: 22 Setting sysctl vfs.zfs.arc_min failed: 22 As an FYI, WITHOUT any tunables set, my defaults are: vfs.zfs.arc_meta_limit: 3903459328 vfs.zfs.arc_min: 1951729664 vfs.zfs.arc_max: 15613837312 So even if I only specified: vfs.zfs.arc_max="8589934592" in loader.conf, that's still not below my default min. However, if I make the changes with 'sysctl' after boot, it works fine: root@athlonbsd:~ # sysctl vfs.zfs.arc_min="1073741824" vfs.zfs.arc_min: 1951729664 -> 1073741824 root@athlonbsd:~ # sysctl vfs.zfs.arc_max="8589934592" vfs.zfs.arc_max: 15613837312 -> 8589934592 They also work fine sysctl.conf. Sorry if this is a silly question: I should still be able to set these max/min values in loader.conf, right--not just in sysctl.conf? Thanks. On Tue, Jul 5, 2016 at 10:16 PM, Nathan Bosley wrote: > OK, I follow you now. > Thanks for the explanation. > I will try that later tonight or tomorrow. > > On Tue, Jul 5, 2016 at 9:45 PM, Allan Jude wrote: > >> On 2016-07-05 21:32, Nathan Bosley wrote: >> > I think in about 4 - 5 hours I can show what values I'm using in >> > loader.conf under, say, r302264 and r302265 for comparison. I'm not 100% >> > sure that the problem arose for me in r302265; I merely suspect it. >> > >> > On Tue, Jul 5, 2016 at 9:25 PM, 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 >> > >> >> > >> >> > >> _______________________________________________ >> > >> freebsd-current@freebsd.org >> > >> > > > > >> > >> mailing list >> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > >> To unsubscribe, send any mail to >> > >> "freebsd-current-unsubscribe@freebsd.org >> > >> > >> > > >" >> > >> >> > >> >> > > >> > > _______________________________________________ >> > > freebsd-current@freebsd.org >> > mailing list >> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > > To unsubscribe, send any mail to " >> freebsd-current-unsubscribe@freebsd.org >> > " >> > >> > >> > 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. >> > >> > -- >> > Allan Jude >> > >> > >> >> The problem is related to Steven's commit, which makes it so you can >> adjust arc_max and arc_min at runtime. Part of this change put in a >> requirement that the new arc_max you are trying to set, must be less >> than the current arc_min. When you first boot, i think the default is >> arc_max = all ram save 1GB, and arc_min = 1/8 of that. >> >> So if you try to set your arc_max to 1/8th or less, it will fail with >> that error 22 (this should be fixed). >> >> You can work around it temporarily by setting a lower arc_min first. >> >> >> -- >> Allan Jude >> >> >