From owner-freebsd-bugs@freebsd.org Sun Oct 6 12:37:09 2019 Return-Path: Delivered-To: freebsd-bugs@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 068B114796C for ; Sun, 6 Oct 2019 12:37:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46mNR86QtSz4FXK for ; Sun, 6 Oct 2019 12:37:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DAEB8147964; Sun, 6 Oct 2019 12:37:08 +0000 (UTC) Delivered-To: bugs@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 DAB17147963 for ; Sun, 6 Oct 2019 12:37:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46mNR85LHpz4FXJ for ; Sun, 6 Oct 2019 12:37:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9AD312644D for ; Sun, 6 Oct 2019 12:37:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x96Cb8jS028203 for ; Sun, 6 Oct 2019 12:37:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x96Cb8Ip028199 for bugs@FreeBSD.org; Sun, 6 Oct 2019 12:37:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241097] freebsd-update(8) archives NFS mounts (and maybe other stuff) Date: Sun, 06 Oct 2019 12:37:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kjift14@posteo.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2019 12:37:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241097 Bug ID: 241097 Summary: freebsd-update(8) archives NFS mounts (and maybe other stuff) Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: kjift14@posteo.at FreeBSD 12.0-RELEASE with UFS root here (with /boot on the / volume), but I have witnessed this behaviour before on older releases as well. I have an NFS mount at the (FreeBSD non-standard) location /opt/XYZ When running `freebsd-update install`, the kernel backup copies the file sy= stem into /boot/kernel.old , and also wants to copy contents of NFS mounts there. This alone is wrong (and dangerous, think about full disks), as far as I understand what the kernel backup should do and what it should not. But even this copy fails with seemingly infinite errors of the form: cp: ///boot/kernel.old/./opt/XYZ/svn/[=E2=80=A6]/.svn/pristine/[=E2=80=A6]:= Cross-device link Probably many (all?) files on NFS are affected; the SVN internals were just= the ones for which I could see this. As a short-term mitigation, I interrupted the update, unmounted the NFS sha= res, deleted /boot/kernel.old (which took remarkably long for a SSD), and reissu= ed `freebsd-update install`. I don't think it is intentional that the kernel backup black-/whitelists ca= n be confused so easily. --=20 You are receiving this mail because: You are the assignee for the bug.=