From owner-freebsd-stable@freebsd.org Fri Jun 26 10:55:07 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 85F123546E0 for ; Fri, 26 Jun 2020 10:55:07 +0000 (UTC) (envelope-from dwilde1@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49tYgZ3TZxz4S0b for ; Fri, 26 Jun 2020 10:55:06 +0000 (UTC) (envelope-from dwilde1@gmail.com) Received: by mail-lj1-x22f.google.com with SMTP id h22so2691427lji.9 for ; Fri, 26 Jun 2020 03:55:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=8mZ8HI2blpR4gQDNjD9Q8Cr4BcL6/WwSYs6pb6i+7iQ=; b=nO4JiLNA1V+YE80zymzP4zDnYBdMebndLi/JVJyRM/pgPVxK2Q0iZrQEsmQQXL5WsR eVXN7sBRF/DK/x97u1rNlkMacWzB7oEzBkBWtuz35zUnPIInKQIpRLarByoRhTcKJ0aE n69zLQMmUvSSg1L4tol7aFsV56ILYwI7ayipLFEie2iPAw0lH1VYC4QtmsXnU8tkC4xz pvgdYCaMqcM1QLburIN8rvDneysZ5eH2X7jRvx9pWYL01lIY/fS7V2MFefwS9zdWfVaj QglbQhPKC+/63kATmLKpYbj6FtiKOUJd/Do5k0RBhWcRrU53gNUylzrPwjVAkyIOeWj3 j2xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=8mZ8HI2blpR4gQDNjD9Q8Cr4BcL6/WwSYs6pb6i+7iQ=; b=QXDgQ4FNcOcPkcNtY/DKTqtGcJA1VMoH14Z69y/cXc0/WsO2EB56sGAImIZMtn3AUZ k1MAyvh/AxCE+8jGT+j05aMRrK+O/cyAmsIr7VAAE3evSH8QoaVvXuJZ3gJJIHF+6mhi 0Nd0/kcl0V5onxCxuo8TEWiUGxALSOdeI0+ZdklSxaHSgZMDhFCkIBxRhG7cnQiDEECk H7kCZteDdKe50N4E8MqsBKQRLB6wHzsf0lPP0zs9gNAMI3cJ8N9yWZpYmJjscdSO7/l7 lI8Hh7RHjYc7xC7rOgGOKXr7Fq6o8A1htGBty25NruQOT7EkwIMJJDmmJWRA+Ox5DPJ8 K1hA== X-Gm-Message-State: AOAM533k4N0wGzPgjBocgXEICmF0D0gbYk+h0+YZUVqLcks6pjoLNHBy N2zX3OIHHUR+YrZ/NA6Gen7EEuxgCk1cR6ReN0osA+gB X-Google-Smtp-Source: ABdhPJxXZrJNn8bnPvHBV+cXuXcQjS55XjKHul+DOvNo2ksPNZHqqpKZS4h0WxzXxSKSbKmxZi2JeMZ/KwlE395K+Xs= X-Received: by 2002:a2e:959a:: with SMTP id w26mr1091677ljh.74.1593168904588; Fri, 26 Jun 2020 03:55:04 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab3:4703:0:0:0:0:0 with HTTP; Fri, 26 Jun 2020 03:55:04 -0700 (PDT) Reply-To: dwilde1@gmail.com In-Reply-To: <20200626102331.GA6406@server.rulingia.com> References: <20200625000410.GA10210@eureka.lemis.com> <20200625025248.GB10210@eureka.lemis.com> <20200626102331.GA6406@server.rulingia.com> From: Donald Wilde Date: Fri, 26 Jun 2020 03:55:04 -0700 Message-ID: Subject: Re: swap space issues To: Peter Jeremy Cc: freebsd-stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49tYgZ3TZxz4S0b X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=nO4JiLNA; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of dwilde1@gmail.com designates 2a00:1450:4864:20::22f as permitted sender) smtp.mailfrom=dwilde1@gmail.com X-Spamd-Result: default: False [-3.47 / 15.00]; HAS_REPLYTO(0.00)[dwilde1@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.38)[-0.377]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.04)[-1.043]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.05)[-1.045]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::22f:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 10:55:07 -0000 On 6/26/20, Peter Jeremy wrote: > On 2020-Jun-25 11:30:31 -0700, Donald Wilde wrote: >>Here's 'pstat -s' on the i3 (which registers as cpu HAMMER): >> >>Device 1K-blocks Used Avail Capacity >>/dev/ada0s1b 33554432 0 33554432 0% >>/dev/ada0s1d 33554432 0 33554432 0% >>Total 67108864 0 67108864 0% > > I strongly suggest you don't have more than one swap device on spinning > rust - the VM system will stripe I/O across the available devices and > that will give particularly poor results when it has to seek between the > partitions. My intent is to make this machine function -- getting the bear dancing. How deftly she dances is less important than that she dances at all. My for-real boxen will have real HP and real cores and RAM. > > Also, you can't actually use 64GB swap with 4GB RAM. If you look back > through your boot messages, I expect you'll find messages like: > warning: total configured swap (524288 pages) exceeds maximum recommended > amount (498848 pages). > warning: increase kern.maxswzone or reduce amount of swap. Yes, as I posted, those were part of the failure stream from the synth program. When I had kern.maxswzone increased, it got through boot without complaining. > or maybe: > WARNING: reducing swap size to maximum of xxxxMB per unit The warnings were there, in the as-it-failed complaints. > The absolute limit on swap space is vm.swap_maxpages pages but the > realistic > limit is about half that. By default the realistic limit is about 4=C3= =97RAM > (on > 64-bit architectures), but this can be adjusted via kern.maxswzone (which > defines the #bytes of RAM to allocate to swzone structures - the actual > space allocated is vm.swzone). > > As a further piece of arcana, vm.pageout_oom_seq is a count that controls > the number of passes before the pageout daemon gives up and starts killin= g > processes when it can't free up enough RAM. "out of swap space" messages > generally mean that this number is too low, rather than there being a > shortage of swap - particularly if your swap device is rather slow. > Thanks, Peter! --=20 Don Wilde **************************************************** * What is the Internet of Things but a system * * of systems including humans? * ****************************************************