From owner-freebsd-bugs@freebsd.org Tue Jan 17 12:32:28 2017 Return-Path: Delivered-To: freebsd-bugs@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 39FBCCB2687 for ; Tue, 17 Jan 2017 12:32:28 +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 1D5961E67 for ; Tue, 17 Jan 2017 12:32:28 +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 v0HCWR1O008403 for ; Tue, 17 Jan 2017 12:32:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 216178] ZFS ARC and L2ARC are unrealistically large, maybe after r307265 Date: Tue, 17 Jan 2017 12:32:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: lev@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 12:32:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216178 Bug ID: 216178 Summary: ZFS ARC and L2ARC are unrealistically large, maybe after r307265 Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: lev@FreeBSD.org I have two ZFS pools: one with single device (zroot) and one raidz with 5 devices (zstor). zstor has L2ARC of 185GB. % zpool list -v NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH=20 ALTROOT zroot 39.9G 13.7G 26.2G - 50% 34% 1.00x ONLINE - gpt/root 39.9G 13.7G 26.2G - 50% 34% zstor 13.6T 8.55T 5.08T - 22% 62% 1.00x ONLINE - raidz1 13.6T 8.55T 5.08T - 22% 62% ada1 - - - - - - ada2 - - - - - - ada3 - - - - - - ada4 - - - - - - ada5 - - - - - - cache - - - - - - gpt/l2arc 185G 185G 148M - 0% 99% % Both pools has compression enabled (lz4), but compression ratio on zstor is negligible (it contains mostly media files, like music, films and RAW digit= al photos). zroot has compression rate about 1.4: % zfs get compressratio zroot zstor NAME PROPERTY VALUE SOURCE zroot compressratio 1.43x - zstor compressratio 1.00x - % My system has 16GB of physical memory. After upgrade to post-r307266 system (10-STABLE) different system tools sta= rts to show unrealistically large ARC. Upgrade to 11-STABLE (after r307265) doe= n't help either. It looks like this: (1) top output: Mem: 195M Active, 4678M Inact, 9656M Wired, 1373M Free ARC: 75G Total, 247M MFU, 6135M MRU, 1190K Anon, 77M Header, 556M Other Swap: 8192M Total, 8192M Free (2) zfs-stats -A output: ARC Size: 515.61% 74.92 GiB Target Size: (Adaptive) 100.00% 14.53 GiB Min Size (Hard Limit): 12.50% 1.82 GiB Max Size (High Water): 8:1 14.53 GiB This starts after some uptime with disc activity (like buildworld & backup)= and could be reset to "normal" state with reboot only. Sometimes, L2ARC starts to grow up to 400% of its size, too. L2ARC shows a = lot of checksum errors as it grow larger than physical size. --=20 You are receiving this mail because: You are the assignee for the bug.=