From owner-freebsd-stable@freebsd.org Mon Feb 15 14:55:42 2016 Return-Path: Delivered-To: freebsd-stable@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 87CFAAA8F7E for ; Mon, 15 Feb 2016 14:55:42 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 4C8791A4C for ; Mon, 15 Feb 2016 14:55:42 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-yw0-x22c.google.com with SMTP id h129so116323522ywb.1 for ; Mon, 15 Feb 2016 06:55:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eIUD/uHokuj4elGJonRN+esIBKNmEbpRVHwKDNrlVKA=; b=vHlYd358yu8qvs3c9GI/gi3iDbDYiG4evYFI7cYYPm0Wg5HFm0rzBzfcb4WXvN8pEc q6pZT+oXoIfo3GCB+yYsC/5yNNuL5J63JQ0qRknKxfJQSp5fBinpWu04N/fM+XqLcd9n qq2clIyn2Ja1GDFBKUA6bpt/f+eK/1Y61vns3lip/JbJM4rjOu7LaVmy1hLMoe3w7BMX jd9nAZDhRAa2ZTmIViG7ItvhQj9A+lRHEm94+UzMvuFYKZXdiZub8rJTe1w7RyV2Qysh BP4yaaoOAyV/o+1W/BOV3cpU1SW2uBA4b0DDBRZQQ0WEqgc9+Fionei+ghPtYHhC3XrF QNfQ== 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:date :message-id:subject:from:to:cc:content-type; bh=eIUD/uHokuj4elGJonRN+esIBKNmEbpRVHwKDNrlVKA=; b=NA0ryNWSa6J3Pk6piKf1T+5W55sbyACZe060Q2IoJ+wG3gNEFZU0flLbuFBlZdmxr1 60C2IXyaYQLcx4Z8P4kXf6z5hg2uZzG5pRtmhEPJgldOiau9hWxhfJm1O1JcalI5mhgB BlRpH4PLH0MBGMui28Yz9MxFeHLKWvmrmit+zfDwvfx9WThAg96O57EkIh5jedyNHPgT s2s+yGbrVEHJcYn/jYtlV38Pb3lCKp37i38PLlL7kK9OmR9VMrOZmWutiST1n8C5CCmH +hB91h7DGE40khWuk01J9rU8jy0aRXH8AYUwrh3OawhAcgO7cxl5Ghasb4gIA56ahOMn 7YyQ== X-Gm-Message-State: AG10YORIQV24SlITA7dsResFqaStt0VAMHnGZI2T8a935S+WSqx45y3YnK6mjyUAoqVdR8Pg7mj/nBsNdWujbA== MIME-Version: 1.0 X-Received: by 10.129.148.133 with SMTP id l127mr9266403ywg.272.1455548141331; Mon, 15 Feb 2016 06:55:41 -0800 (PST) Received: by 10.13.214.74 with HTTP; Mon, 15 Feb 2016 06:55:41 -0800 (PST) X-Originating-IP: [67.81.241.220] In-Reply-To: <56C1E0B4.5080201@FreeBSD.org> References: <56C1E0B4.5080201@FreeBSD.org> Date: Mon, 15 Feb 2016 09:55:41 -0500 Message-ID: Subject: Re: ZFS ARC vs Inactive memory on 10-STABLE: is it Ok? From: Mark Saad To: lev@freebsd.org Cc: freebsd-fs@freebsd.org, FreeBSD-Stable ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Feb 2016 14:55:42 -0000 On Mon, Feb 15, 2016 at 9:29 AM, Lev Serebryakov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > I have mostly-storage server with 8GB of physical RAM and 9TB (5x2TB > HDD) raidz ZFS pool (so, about 6.5TB usable space). > > ARC is limited to 3GB by vfs.zfs.arc_max. > > This server runs Samba (of course), CrashPlan backup client (Linux > Java!), and torrent client (transmission-daemon). > > Wow someone else as crazy as I was. :) > And I'm noticing this regularly ("screenshot" of top(1)): > > Mem: 1712M Active, 3965M Inact, 2066M Wired, 137M Cache, 822M Buf, > 4688K Free > ARC: 421M Total, 132M MFU, 54M MRU, 1040K Anon, 7900K Header, 227M Other > Swap: 4096M Total, 248M Used, 3848M Free, 6% Inuse > > As you can see, here are almost 4G of Inactive memory and only 412M > of ARC! > > Is it Ok? Why Inactive memory (non-dirty buffers?) are pressed ARC > out of memory? > > Lev so I ran a similar setup on 10.1-RELEASE with 40TB in a raid 1+0 like zpool . My top looked similar but its been a while and i had 24G of ram. With a 12G Arc max. I always wondered what was going on here but I suspected it was due to a interaction of java and arc eviction. The crash plan app is terrible and would "start doing something new" up and look hung. Disk io went to hell etc . Then things would settle down and start chugging away. Keep in mind crash plan would take like a month to back up 2TB of changes on this thing. I eventually convinced management to move to a automated tape library and a normal backup client ( netbackup ) for the backups. Also I abandoned this project about 18 months ago too . - -- > // Lev Serebryakov > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQJ8BAEBCgBmBQJWweC0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF > QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePRTYP/RHajhE+EuvX3fCppShb/BSg > vpJZ8F1jeInIOVXe/XLw07jht04uquTXHsMvw6F0J+WIIqsCld53q1bfj4CWAnl6 > 4TjULTZYUWANv3wK6KxItEN5eMmDEPOW6Eqls57OSCFcZA/32hyf/Y15Nec0L6JD > sd8wpqUvQs0zb//frbUpjIRcfoVSMO2ip4doGPDtBv9IcE/kDz78IcmU9By2deXU > IJE8Xlg2hDY+f/NhTR2sCuwtCSvpL9/mBztffYqsKQsAm8oIn0Sz9mNdjVzUR+rN > lF4GoxcWf6c3HEM/LF4+dgOdb058YwO4amyUI7GoBSFBQq3OlJzvomGeOi2vPAvC > BkWxOWOcWsmEwfk1b22k00yNAjvaXQsCx6r2L/6vyrAtoQ0moXF4Rks8+MLFRUTu > FFke93UUPRQPXBdrBtlnFpXX6jpmlEm7g9pazarGc4hteYOKpvHajFvNvAB7RswI > NQL70+QfLBgtaA5683scCuURNptStf/RfvhwjW/o5DPNLv+NHnT+nPk64MTDuaZD > 4z9Kcj088KjB++xt9c6BXuCS4zlkyUhas5cNGG+SxupZajtIuaCBTeUv0QwjnDH5 > Pnu44Xe4MCvpDSt9odICdzytxO6yzwL7mLj70o2SsPs2ijN1w/fOlNqS46bekmJ/ > MtvVwObCRnoDg3aMRUL0 > =In6V > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- mark saad | nonesuch@longcount.org