Date: Fri, 13 Nov 2020 10:36:45 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-current@freebsd.org Subject: Re: remove df(1) support for mounting filesystems Message-ID: <1704143613.1.1605260205588@localhost> In-Reply-To: <20201112185139.GA8558@raichu> References: <20201112185139.GA8558@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
haha, this is the weirdest functionality I have seen in times. So long for the 'programs that do one thing and do it well' philosophy. :-) axe it! cheers, Ronald. PS: sorry for the twitter-style reply. Van: Mark Johnston <markj@freebsd.org> Datum: donderdag, 12 november 2020 19:51 Aan: freebsd-current@freebsd.org Onderwerp: remove df(1) support for mounting filesystems > > Hi, > > df(1) has the ability to mount character devices in order to collect > usage information. This functionality has been deprecated for the past > couple of years, since r329092, and is buggy per PR 237368. I propose > removing it in 13.0: https://reviews.freebsd.org/D27197 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > From owner-freebsd-current@freebsd.org Fri Nov 13 10:35:57 2020 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@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 9CE8B2D64E4 for <freebsd-current@mailman.nyi.freebsd.org>; Fri, 13 Nov 2020 10:35:57 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 4CXZcr5ZCCz3krs for <freebsd-current@freebsd.org>; Fri, 13 Nov 2020 10:35:56 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-ej1-x636.google.com with SMTP id dk16so12621229ejb.12 for <freebsd-current@freebsd.org>; Fri, 13 Nov 2020 02:35:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=/BI0eqrDgzP42lrNsovqrVz+v4YsbEwlxwGxgKV3UAQ=; b=Ox0RiRhEOQef5BWHpJSTcO1CigPqou5UPa/Qn1yLk99WO3pBJP7k4Nzi/m7t33uEQX umDL8xipSfM0aeTlf5AJN6PNBFuGWQpm+vzs0WC04LPp9SHp8NgGvEGKkLSVoXj8Hz+w EK3s2vFxFvfQsiaxKF9EaalrG0bNt9Pc4uqZ2laHDA9C2ypWGwoJmu/lxJBhRUQddA4E yGXVPtj/H3QvMt5YOtqnQR9FJM4+GGsWyAhuk3fAKV6B155kP5EJMB0+hvSLx4ILCL6/ ZmTiWJeG390aA7MJe+LDPs0rLb1QCIBJ7YYInHD3qXGuI/lNsxtG4bugj8qfvCXruS3Z iL2A== X-Gm-Message-State: AOAM533Oev5hxLRSKsdZjGSs+h9bcvq3rrIzKoocnk09FkLgEswcVV+M ksMv+5jWj1e5Xgfuz4JExZ1yrv3RaRY= X-Google-Smtp-Source: ABdhPJwlgrQe85WzbSBhKIeli0IZPLOQfvQgHy4Tiqm4lETOB6NPiG+X0J/ZALX8sHOULpAJDIL8kw== X-Received: by 2002:a17:906:a155:: with SMTP id bu21mr1227570ejb.378.1605263754419; Fri, 13 Nov 2020 02:35:54 -0800 (PST) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id j9sm3218604ejf.105.2020.11.13.02.35.53 for <freebsd-current@freebsd.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Nov 2020 02:35:53 -0800 (PST) To: freebsd-current@freebsd.org From: Johan Hendriks <joh.hendriks@gmail.com> Subject: Shutdown errors and timeout Message-ID: <65b1ff51-a946-61d0-79d9-104c1e053554@gmail.com> Date: Fri, 13 Nov 2020 11:35:53 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4CXZcr5ZCCz3krs X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::636:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::636:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::636:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 13 Nov 2020 10:35:57 -0000 Hello all, i have two FreeBSD 13 machines, one is a bare metal and one is virtualbox machine which i both update about once a week. The vritual machine seems to fail stopping something and gives a timeout after 90 sec. The console ends with Writing entropy file: . Writing early boot entropy file: . 90 second watchdog timeout expired. Shutdown terminated. Fri Nov13 11:20:40 CEST 2020 Nov 13 11:20:40 test-head init[1]: /etc/rc.shutdown terminated abnormally, going to single user mode ... On the bare metal machine i see the following. Writing entropy file: . Writing early boot entropy file: . cannot unmount '/var/run': umount failed cannot unmount '/var/log': umount failed cannot unmount '/var': umount failed cannot unmount '/usr/home': umount failed cannot unmount '/usr': umount failed cannot unmount '/': umount failed The virtual machine has the following mount points set. zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs) fdescfs on /dev/fd (fdescfs) zroot/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) zroot/jails on /jails (zfs, local, noatime, nfsv4acls) zroot/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot/var/audit on /var/audit (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot on /zroot (zfs, local, noatime, nfsv4acls) zroot/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls) zroot/var/mail on /var/mail (zfs, local, nfsv4acls) The barematal one zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs) fdescfs on /dev/fd (fdescfs) zroot/usr on /usr (zfs, local, noatime, nfsv4acls) zroot/var on /var (zfs, local, noatime, nfsv4acls) zroot/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) zroot/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/run on /var/run (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/mail on /var/mail (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/db on /var/db (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/empty on /var/empty (zfs, local, noatime, noexec, nosuid, read-only, nfsv4acls) zroot/usr/src on /usr/src (zfs, NFS exported, local, noatime, noexec, nosuid, nfsv4acls) zroot/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls) zroot/usr/obj on /usr/obj (zfs, NFS exported, local, noatime, nfsv4acls) zroot/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot/usr/ports/distfiles on /usr/ports/distfiles (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/usr/ports/packages on /usr/ports/packages (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/db/pkg on /var/db/pkg (zfs, local, noatime, nosuid, nfsv4acls) The pools have not been upgraded after the latest openzfs import, maybe that is related? FreeBSD test-freebsd-head 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r367585: First thing i noticed is about a week ago.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1704143613.1.1605260205588>