From owner-freebsd-questions@freebsd.org Sun Oct 11 14:09:45 2020 Return-Path: Delivered-To: freebsd-questions@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 1CDE73F541F for ; Sun, 11 Oct 2020 14:09:45 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (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 4C8Nwm3knBz4GSw for ; Sun, 11 Oct 2020 14:09:44 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm1-x341.google.com with SMTP id b127so1946398wmb.3 for ; Sun, 11 Oct 2020 07:09:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=HJdanCPY72ulIZvE01XJd6YLP7aw6/MhVcwSRH8Svo0=; b=WtUcnOf8VEclfokNowvwy7sors/hPPhD+hRA1VEAyo9lW7xAP9sHImHVkDfmNn6g1l lalGYwy1sb3eDriyZFyvYa6caiod3oW02qB5BibNVlBPzmeKDDM5jbKzBTtb6sIpPepB XCYab8qD/F4LbU1uqXLFPAeRvkPwWrhs91Dn+hzG/9C4o1fZ91sC/AJ8CqPBpoU6amkk PGh8AeSufuiHu2OmFPFDi+xLfqr62u33kO+v+yZHE9/iQohWH43B0PVpfwOPR9THzhrs uypC3XDEVCj4p4+qzqVmt2X/GTd9n4Xm0w7lEvdII3zMMY55Dha9AY78LsVlJhcMpcTW tq3A== X-Gm-Message-State: AOAM530UrWBWh1GO0xOpLdTti4hyGoxoKsWGhVVdjGC3hMGBv6/Tvngn FWxfw64/tjuwRJKT13DoxSJ/CdUlvst2Yg== X-Google-Smtp-Source: ABdhPJx1hnH7TUCLvDUgJZbvJy2qDSJPFq/oPEWg6R4UkpEmHZqDTCPIMAQOO/P5Myf5g9sDazXIJg== X-Received: by 2002:a1c:9d90:: with SMTP id g138mr6847516wme.5.1602425382889; Sun, 11 Oct 2020 07:09:42 -0700 (PDT) Received: from gumby.homeunix.com ([90.195.199.9]) by smtp.gmail.com with ESMTPSA id r1sm20514565wro.18.2020.10.11.07.09.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 11 Oct 2020 07:09:42 -0700 (PDT) Date: Sun, 11 Oct 2020 15:09:40 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: errors happening with /usr/libexec/save-entropy on 12.1-p10 Message-ID: <20201011150940.6d0f5547@gumby.homeunix.com> In-Reply-To: <20201011030537.GA30207@rpi4.gilescoppice.lan> References: <20201011030537.GA30207@rpi4.gilescoppice.lan> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd12.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4C8Nwm3knBz4GSw X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.51 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-0.61)[-0.607]; RECEIVED_SPAMHAUS_PBL(0.00)[90.195.199.9:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.971]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.93)[-0.927]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::341:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2020 14:09:45 -0000 On Sun, 11 Oct 2020 04:05:37 +0100 tech-lists wrote: > Hi, > > I've noticed recently in the daily security email that *sometimes* > when this is run out of /etc/crontab on a 12.1-p10 system: > > # Save some entropy so that /dev/random can re-seed on boot. > */11 * * * * operator > /usr/libexec/save-entropy > > that it'll generate an error visible in the security email like this: > > [redacted] kernel log messages: +pid 12995 (dd), uid 2 inumber 2086730 > on /: filesystem full > > (the filesystem has plenty of inodes spare and plenty of space) > > It's the only one I've seen so far (12.1-p10) with this issue. > 12-stable doesn't have this problem, but the If it fails on 12.1 but not on 12-stable that would imply that it's a long standing problem and something was fixed in stable. There's no sign that anything like that happened. I think it's unlikely that this is caused by save-entropy. All it does is dd the output of /dev/random to a file and rotate the files. When you say that there's plenty of space, are you allowing for the fact that the operator user can't write to space reserved for root.