From owner-freebsd-amd64@freebsd.org Wed Aug 31 11:37:23 2016 Return-Path: Delivered-To: freebsd-amd64@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 60691BC9A08 for ; Wed, 31 Aug 2016 11:37:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5056F979 for ; Wed, 31 Aug 2016 11:37:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7VBbNYC094477 for ; Wed, 31 Aug 2016 11:37:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 212269] ZFS ARC appears to ignore vfs.zfs.arc_max Date: Wed, 31 Aug 2016 11:37:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: scratch65535@att.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: smh@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 31 Aug 2016 12:14:19 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 11:37:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212269 --- Comment #3 from MMacD --- Okay, my version is stale: r286666 It does seem to have been a regression to when "M" and "G" weren't being interpreted (I can't now find that bug again). And quotes also seem to caus= e a problem when entering the number, which doesn't seem a good idea.=20=20 But entering the value in bytes *without* quotes may have worked (zfs-stats= is a little bit unclear about that, since it still lists 30GB as target and max which is scary) Can I presume that it's fixed in 10.3 and later? --=20 You are receiving this mail because: You are on the CC list for the bug.=