From nobody Sun Jan 8 20:36:11 2023 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Nqpkg4kZvz2r4rZ for ; Sun, 8 Jan 2023 20:36:11 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Nqpkg2V8lz3DKX for ; Sun, 8 Jan 2023 20:36:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1673210171; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Is/cfvb6SsJMB5Tbbky/01cAgOfO5/8NUwUI/bJgN7I=; b=fK0TXXVR+AUY1tmXKmMNkJswTG30VWBirRmOmfUXaYVPX0qgQmAogQ+M45u9qD1QKRSVim u7YwXJZ752Ad5DVHGkbMQCNpEdnmOVQ9EjPjyeImQqScF4wjYfp/A2FBy6YWL3qY2pNhJ0 pnM/o92AsO3aQ823arhVGFYKkakk7IbCyGjrJyCSEeyk+QQUVyNKkop5XihO4/+9mMswcC yjRIjuXTR91lsyF8tO19Tr6Q8KOGXUGIPojNrucwh8thcGorjNfuAIHNvqsVvogEJeD6gs Cv2BNRqvFuKh189LdIJCWgku+nhMdMXWbq1cuYct9YEqjf4rXKKM0/1JL7cz6Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1673210171; a=rsa-sha256; cv=none; b=aQgpBbaL5QWU+M3Jj1vqLE2rFMqccAI3UrRq9ihciBia0zZMcF45PdE09LgYwMqP1D8RyJ 4S4r0Z4i7zCPuUH3PALAwPjosPPgw7NA4Lv9wZkx6pHVJBszOi78zPrnua4B846Sw8+HR/ fmmHaKCgaQp5vWzd2MJe/cBnlyIzMshMkv7ndrQdFHjGAVnURkoY8GD4+KeuhmphfIskcD tH/ox2kBLB2875tbRRq+i9iB+m8vG+YYSj9LRVGbro+TT32A8ni2c1sA0kruEWXABDOpYd d+EalOiZuokG3LEJ1u5EAVK4IiZX3x/HANdHvcsyneHJMQ9xBrLUnw0x9ULlLw== 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 4Nqpkg1ShBz12sg for ; Sun, 8 Jan 2023 20:36:11 +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 308KaBYE059328 for ; Sun, 8 Jan 2023 20:36:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 308KaBe9059327 for bugs@FreeBSD.org; Sun, 8 Jan 2023 20:36:11 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 268830] After 12.3 to 13.1 upgrade, failed to mount zfs filesystems Date: Sun, 08 Jan 2023 20:36:11 +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: 13.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: leif@ofWilsonCreek.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 List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268830 Bug ID: 268830 Summary: After 12.3 to 13.1 upgrade, failed to mount zfs filesystems Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: leif@ofWilsonCreek.com 13.1 (and possibly 13.0) appears unable to mount a filesystem by the name of "tank/.". My pattern has been to set mountpoint=3D/ and canmount=3Doff for = tank. Then I create a descendent filesystem called "tank/." and let it inherit the mountpoint. Why? Using "tank" for / is troublesome because it cannot be renamed, and any special properties get inherited by all others (which some would argue is appropriate but I find necessitates override settings on all other filesystems). Having the mountpoint inherit instead of explicitly set= ting it to / allows such a rename to be performed without a "tripping hazard" of forgetting to update the mountpoint property. I totally understand if there's a new reason this can't be supported. I can endure losing my clever trick. However, I believe there at least needs to b= e a path to recovery, short of using 12.3 boot media; that is, `zfs rename` nee= ds to work. Everything I could think of post-upgrade has failed. Here are details of what happened. After upgrading from 12.3 to 13.1, the kernel successfully mounted the root filesystem and booted, but rc failed to mount any other ZFS filesystems, su= ch as tank/home. # mount tank/. on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs) fdescfs on /dev/fd (fdescfs) procfs on /proc (procfs, local) Baffled as to what was going on, I wondered if the other filesystems were intact: # zfs list internal error: cannot iterate filesystems: Invalid argument Abort trap (core dumped) I was able to mount them explicitly: # zfs mount tank/home=20 # ls /home [correct output, redacted] Wondering if something in the upgrade failed, I tried rollback: # zfs rollback -r tank/.@2023-01-07.12.3-RELEASE-p5 cannot open 'tank/.': self reference, '.' is found in name This thankfully told me the problem with a correct error message, so I figu= red I needed to rename from my clever name of `tank/.` to something else, but I couldn't: # zfs rename -u tank/. tank/_ cannot open 'tank/.': self reference, '.' is found in name # zfs set mountpoint=3D/ tank/. cannot open 'tank/.': self reference, '.' is found in name My only recourse appears to be booting 12.3 media and renaming the filesyst= em. Happily I was able to rename it using 12.3 and set the explicit mountpoint without rollback or other hassle. --=20 You are receiving this mail because: You are the assignee for the bug.=