From owner-freebsd-bugs@freebsd.org Sat Sep 12 14:57:13 2020 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 5CF993DA16D for ; Sat, 12 Sep 2020 14:57:13 +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 4BpbLx1rx1z44N0 for ; Sat, 12 Sep 2020 14:57:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 3F6AF3DA16C; Sat, 12 Sep 2020 14:57:13 +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 3F3533DA16B for ; Sat, 12 Sep 2020 14:57:13 +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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4BpbLx0yjkz44f8 for ; Sat, 12 Sep 2020 14:57:13 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 00E1616E96 for ; Sat, 12 Sep 2020 14:57:13 +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 08CEvCIE002652 for ; Sat, 12 Sep 2020 14:57:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 08CEvC85002651 for bugs@FreeBSD.org; Sat, 12 Sep 2020 14:57:12 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 249280] Issues migrating from 12-STABLE to 13-CURRENT regarding filesystem layout changes Date: Sat, 12 Sep 2020 14:57:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctorwhoguy@gmail.com 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.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2020 14:57:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249280 Bug ID: 249280 Summary: Issues migrating from 12-STABLE to 13-CURRENT regarding filesystem layout changes Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: doctorwhoguy@gmail.com I recently decided to make the jump from 12-STABLE to 13-CURRENT on my home server. For the most part, the upgrade went smoothly. However, I did run in= to a couple of issues so far that seem to be due to a change in the filesystem layout and possibly adding certain directories as ZFS datasets. The first issue I ran into was with /usr/src. Since I had sources for 12.1-RELEASE, 12-STABLE, and HEAD in /usr, I used a symlink pointing in /usr pointing from src -> head-src during the upgrade. After each reboot during = the upgrade process, my source code in /usr/src seemingly disappeared, and I ha= d to fetch the source again. I was baffled until I realized that /usr/src was no= w a ZFS dataset. I unmounted the dataset, and my data was still there. I was subsequently able to move my data to a temporary directory, remount the dataset, and put the data into /usr/src where it belongs. That was yesterday. Today I realized that /home is now a symlink to /usr/ho= me which is a ZFS dataset, and all the data I had in my home directory has seemingly disappeared. I'm sure that my data is still there, but I can't unmount this dataset on a running system because I get a "device busy" error when trying to unmount it. So there seems to be two separate issues that need to be addressed. 1) The problem of "disappearing data" where the contents of a directory see= m to be gone when a ZFS dataset is mounted at the same location as a preexisting directory. 2) There needs to be a clear way to upgrade a system to this new filesystem layout which can avoid the above issue. I didn't see anything in UPDATING w= hich addresses this problem. --=20 You are receiving this mail because: You are the assignee for the bug.=