From owner-freebsd-fs@freebsd.org Sun Jul 22 10:08:53 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F60D1046992 for ; Sun, 22 Jul 2018 10:08:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DAED88F813 for ; Sun, 22 Jul 2018 10:08:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 94686104698F; Sun, 22 Jul 2018 10:08:52 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81765104698E for ; Sun, 22 Jul 2018 10:08:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 145678F80B for ; Sun, 22 Jul 2018 10:08:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6F14C1C151 for ; Sun, 22 Jul 2018 10:08:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6MA8pH6050852 for ; Sun, 22 Jul 2018 10:08:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6MA8pRY050851 for fs@FreeBSD.org; Sun, 22 Jul 2018 10:08:51 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: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Date: Sun, 22 Jul 2018 10:08:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: andreas.sommer87@googlemail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 10:08:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #9 from Andreas Sommer --- Saw this again just now, after having reinstalled the whole instance on July 10th (12 days "incubation time" :P). Again, I could see the steady CPU usage (spinlock) in AWS CloudWatch monitoring graphs. Doing `procstat -kk` on the buildbot master process gave `procstat: sysctl: kern.proc.kstack: 67301: De= vice busy`, while `procstat -kka` made the system unavailable and rebooted. Thus= , no further info collected apart from the knowledge that this also happens for ashift=3D12 (originally I had an ashift=3D9 pool on the old instance which = had this problem every few days). Anything more we can do to debug/resolve this? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jul 22 18:14:19 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 479D9105217C for ; Sun, 22 Jul 2018 18:14:19 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B65377F08E for ; Sun, 22 Jul 2018 18:14:15 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id w6MIE59s009120 for ; Sun, 22 Jul 2018 21:14:05 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 22 Jul 2018 21:14:05 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-fs@FreeBSD.org Subject: ZFS backup Q: send/recv and mountpoint property Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Sun, 22 Jul 2018 21:14:06 +0300 (MSK) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 18:14:19 -0000 Colleagues, still stuck in compiling stable procedure. Prerequisites: - some servers, all on ZFS, with layout such as machine -> unique pool name, usually 2-letters, say, hm and im - zfs layouts like hm/R/${fs}, like hm/R hm/R/usr hm/R/usr/local hm/R/var hm/R/home etc, where hm/R has property mountpoint=/ and others just inherit it - on servers, zfs allows for non-root user to make snapshots, hold, etc, like Local+Descendent permissions: group operator hold,send,snapshot - zfs send -R [-i pool@prev-snap] pool@now-snap | \ ssh backupserver 'zfs recv tgpool/B/zfs/srvname' Problem: 0. on backup (zfs recv) server, I could not - overwrite mountpoint property (and I'd better avoid it) - add canmount=off, especially for child filesets, as it's not inherited (which could be preferred behaviour) 1. after backup server reboot, if special manual tweaks did not have place, filesets from backup images overwrite backup filesets, render it unuseable Any hints? Or did I missed something trivial? Thanks, as usual, in advance! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-fs@freebsd.org Sun Jul 22 19:25:07 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77B811053716 for ; Sun, 22 Jul 2018 19:25:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0C78A80FA5 for ; Sun, 22 Jul 2018 19:25:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C49D21053714; Sun, 22 Jul 2018 19:25:06 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0BA91053713 for ; Sun, 22 Jul 2018 19:25:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49CA780FA2 for ; Sun, 22 Jul 2018 19:25:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 749E720ECF for ; Sun, 22 Jul 2018 19:25:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6MJP5me002787 for ; Sun, 22 Jul 2018 19:25:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6MJP5We002786 for fs@FreeBSD.org; Sun, 22 Jul 2018 19:25:05 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: fs@FreeBSD.org Subject: [Bug 229958] ctld / zfs deadlock with 'zfs rename ...' Date: Sun, 22 Jul 2018 19:25:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: 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-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 19:25:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229958 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jul 22 21:01:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3A57102AEF6 for ; Sun, 22 Jul 2018 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED318490B for ; Sun, 22 Jul 2018 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 132A4102AEDA; Sun, 22 Jul 2018 21:01:09 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7FA3102AED4 for ; Sun, 22 Jul 2018 21:01:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 860BF84901 for ; Sun, 22 Jul 2018 21:01:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id ADDB921D01 for ; Sun, 22 Jul 2018 21:01:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6ML17n0034197 for ; Sun, 22 Jul 2018 21:01:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6ML178u034188 for fs@FreeBSD.org; Sun, 22 Jul 2018 21:01:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807222101.w6ML178u034188@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 22 Jul 2018 21:01:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 21:01:10 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Tue Jul 24 01:29:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADDF1102F4DB for ; Tue, 24 Jul 2018 01:29:09 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 32A1B76F36 for ; Tue, 24 Jul 2018 01:29:09 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6O1RkLD094784 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 23 Jul 2018 18:27:46 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6O1RkVg094783 for freebsd-fs@freebsd.org; Mon, 23 Jul 2018 18:27:46 -0700 (PDT) (envelope-from warlock) Date: Mon, 23 Jul 2018 18:27:45 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: CRC32Mounting from zfs:zroot/ROOT/default failed with error 2 Message-ID: <20180724012745.GB75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 01:29:09 -0000 I'm trying to get my RPI3B+ to boot up with a ZFS root. I've seeded the OS with FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180719-r336479.img (and it's predecessors 20180709-r336134 and 20180618-r335317). I've more or less copied the EFI/U-Boot partition over as-is, and that part seems fine. The EFI loader iterates through my partitions, finds the ZFS root (zfs:zroot/ROOT/default), clearly reads the /boot/defaults/loader.conf and downloads the kernel, umodem.ko and zfs.ko so it's obviously able get the data off of there. [/boot/loader.conf] hw.usb.template=3 umodem_load="YES" zfs_load="YES" The kernel boots. That parts looks relatively normal except for this message during the boot: ... Instruction Set Attributes 0 = : unknown file system. ... (It's possible that the error is landing in the middle of the rest of the info dump that after the CPU 0 processor feature dump.) It eventually fails and gives me a mountroot> prompt. It prints out a good- looking vfs.root.mountfrom (=zfs:zroot/ROOT/default) variable. Trying devices like zfs:zoort (wrong) and zfs:zroot/ROOT/default (should be Ok) results in this, much like the kernel startup error: Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file system At the mountroot prompt, I don't see the ZFS partition directly (but mmcsd0s2a is shown). At the loader prompt, lsdev lists zfs:zroot as a zfs device, and "lszfs zroot" shows ROOT (+$MOS, $FREE & $ORIGIN), "lszfs zroot/ROOT" shows default, but I can't get below that. "ls" and "ls /boot" show what you'd expect to see off of the root filetree from zroot/ROOT/default. I literally made the image by creating a UFS version to build the ZFS version, same kernel, so you'd think there wouldn't be any incompatibilities. Any suggestions? From owner-freebsd-fs@freebsd.org Tue Jul 24 08:33:52 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C153D1044E25 for ; Tue, 24 Jul 2018 08:33:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 40D89853FD for ; Tue, 24 Jul 2018 08:33:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wm0-f42.google.com with SMTP id y2-v6so1029302wma.1 for ; Tue, 24 Jul 2018 01:33:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=crdp/XoHPp2qWCN4dSfG6Xz5rRfPSasLUwvRbQ1YqnY=; b=qsWtQz9PGw6UT5T2N/6asrpTabUmoSqaMzE51lSL7JeqkC8JTrpsNpV93t3GLUXV4T 5IplADtmX788Xli/YtuoC9V0zOG9qaVWicp/eza2GnuPOsmsogXxtmaeOnjEO8gocyaj SnMyqpN9iZgMCws73Fty9PfnaP489tblmeQ4Bp+hv1y7dr/ZcX6lyHYcsnjrLQLNVCU8 8IaXpRDWDyX14gRiYy6mie95i4U06+BR17MCB1wmmWE3mVu12wh8yLNzUZFvphj1kaZO 51EuG78IwkdGWPr7CsGMc+z/gJKT7l5bsywHcow8kOpIspZcP+Bi/5PEb/X/1bnMJrUk zzfQ== X-Gm-Message-State: AOUpUlHejxaOQqqWNEI5ID3ZGdKTC1CpbAq29SWO6cdBhUuP67QeOZS+ PHms22C5jgQxOzIjegzDBFgZKwTi X-Google-Smtp-Source: AAOMgpfUoZZBRPSn3CW0EAuwosXTEM4UiFY5oA4EyGmLsCr2li2QjAXwHm4ia9jvzrWKksiSMgLHog== X-Received: by 2002:a7b:c016:: with SMTP id c22-v6mr1472316wmb.160.1532421230532; Tue, 24 Jul 2018 01:33:50 -0700 (PDT) Received: from [192.168.1.36] (broadband-82-140-206-85.atc.tvcom.ru. [82.140.206.85]) by smtp.googlemail.com with ESMTPSA id s124-v6sm1402320wmf.47.2018.07.24.01.33.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Jul 2018 01:33:49 -0700 (PDT) Subject: Re: CRC32Mounting from zfs:zroot/ROOT/default failed with error 2 To: John Kennedy , freebsd-fs@freebsd.org References: <20180724012745.GB75644@phouka1.phouka.net> From: Andriy Gapon Message-ID: <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> Date: Tue, 24 Jul 2018 11:33:52 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180724012745.GB75644@phouka1.phouka.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 08:33:53 -0000 On 24/07/2018 04:27, John Kennedy wrote: > I'm trying to get my RPI3B+ to boot up with a ZFS root. I've seeded the OS > with FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180719-r336479.img (and it's > predecessors 20180709-r336134 and 20180618-r335317). > > I've more or less copied the EFI/U-Boot partition over as-is, and that part > seems fine. The EFI loader iterates through my partitions, finds the ZFS root > (zfs:zroot/ROOT/default), clearly reads the /boot/defaults/loader.conf and > downloads the kernel, umodem.ko and zfs.ko so it's obviously able get the data > off of there. > > [/boot/loader.conf] > hw.usb.template=3 > umodem_load="YES" > > zfs_load="YES" > > The kernel boots. That parts looks relatively normal except for this message > during the boot: > > ... Instruction Set Attributes 0 = CRC32Mounting from zfs:zroot/ROOT/default failed with error 2> > : unknown file system. > ... > > (It's possible that the error is landing in the middle of the rest of the info > dump that after the CPU 0 processor feature dump.) > > It eventually fails and gives me a mountroot> prompt. It prints out a good- > looking vfs.root.mountfrom (=zfs:zroot/ROOT/default) variable. > > Trying devices like zfs:zoort (wrong) and zfs:zroot/ROOT/default (should be Ok) > results in this, much like the kernel startup error: > > Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file system This seems like possibly the same problem as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229972 That bug report also describes getting error 2 (ENOENT). Your report adds an additional detail, "unknown file system". That means that vfs_byname() cannot find "zfs" filesystem type. As-if zfs module was not loaded. I wonder if there can be any conflict / confusion between the module declared via VFS_SET(zfs_vfsops, zfs, VFCF_JAIL | VFCF_DELEGADMIN); in zfs_vfsops.c and the module declared via DECLARE_MODULE(zfsctrl, zfs_mod, SI_SUB_VFS, SI_ORDER_ANY); in zfs_ioctl.c. Both define an object named 'zfs_mod' but the objects are static so should not conflict. But there can be quirks in the toolchain (linker) or in the kernel loader. Also, there have been some relatively recent changes related to VFS_SET and DECLARE_MODULE. But the problem is very strange. > At the mountroot prompt, I don't see the ZFS partition directly (but mmcsd0s2a > is shown). At the loader prompt, lsdev lists zfs:zroot as a zfs device, and > "lszfs zroot" shows ROOT (+$MOS, $FREE & $ORIGIN), "lszfs zroot/ROOT" shows > default, but I can't get below that. "ls" and "ls /boot" show what you'd > expect to see off of the root filetree from zroot/ROOT/default. > > I literally made the image by creating a UFS version to build the ZFS version, > same kernel, so you'd think there wouldn't be any incompatibilities. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Wed Jul 25 01:38:38 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B2BB1035CD3 for ; Wed, 25 Jul 2018 01:38:38 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E5A60898CF for ; Wed, 25 Jul 2018 01:38:37 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: by mailman.ysv.freebsd.org (Postfix) id A748D1035CD1; Wed, 25 Jul 2018 01:38:37 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A01F1035CD0; Wed, 25 Jul 2018 01:38:37 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from natasha.teterin.net (symbion.zaytman.com [64.112.176.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "symbion", Issuer "Narawntapu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 080AE898CE; Wed, 25 Jul 2018 01:38:33 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from narawntapu.narawntapu (pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28]) by natasha.teterin.net (8.15.2/8.15.2) with ESMTPS id w6P1cWGr009103 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 24 Jul 2018 21:38:32 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) X-Authentication-Warning: natasha.teterin.net: Host pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28] claimed to be narawntapu.narawntapu Received: from [127.0.0.1] (localhost [127.0.0.1]) by narawntapu.narawntapu (8.15.2/8.15.2) with ESMTP id w6P1cQf9050508; Tue, 24 Jul 2018 21:38:26 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) X-Authentication-Warning: narawntapu.narawntapu: Host localhost [127.0.0.1] claimed to be [127.0.0.1] To: stable@freebsd.org, fs@freebsd.org From: "Mikhail T." Subject: core dumps onto ZFS Message-ID: Date: Tue, 24 Jul 2018 21:38:26 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Language: en-US X-DCC-dmv.com-Metrics: narawntapu 1095; Body=2 Fuz1=2 Fuz2=2 X-Spam-Status: No, score=-2.9 required=7.5 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on narawntapu.narawntapu Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 01:38:38 -0000 Hello! Last night I was trying to get KDE5 to start up on my new machine, and a couple of KDE's processes kept crashing, dumping cores like the one below: -rw-------  1 mi    wheel  45780992 Jul 23 22:28 ksplashqml.core After, maybe, 10 such rounds -- each generating two core-dump -- ZFS hung... The machine was otherwise responsive, but any attempts to access the ZFS filesystems would hang as NFS would, when the remote server stops responding... Pressing Ctrl-T would show the process in the state named "zfs". According to "systat -vm", all four disks involved in the raidz1 were writing in excess of 100MB/s, so I let it be for a few minutes, but nothing improved -- and the writes continued... I pressed Ctrl-Alt-Del, which initiated a shutdown, but the shutdown hung as well ("some processes would not die") and I had to do a power cycle... The sole zpool consists of 4 3TB drives and a 16GB log (on an SSD) thus:         NAME        STATE     READ WRITE CKSUM         aldan       ONLINE       0     0     0           raidz1-0  ONLINE       0     0     0             da0     ONLINE       0     0     0             ada1    ONLINE       0     0     0             da2     ONLINE       0     0     0             da1     ONLINE       0     0     0         logs           ada0e     ONLINE       0     0     0 It reports no data-errors after reboot. There are multiple filesystems on it, among them /home. The box is running a very recent FreeBSD-11/amd64 (r336626). It has 4 Xeon cores and 128GB of RAM. The pool was created under FreeBSD-10 -- after this incident I upgraded it. What happened? Thanks! Yours, -mi From owner-freebsd-fs@freebsd.org Wed Jul 25 12:03:57 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86F5910494AA for ; Wed, 25 Jul 2018 12:03:57 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C28C7B345 for ; Wed, 25 Jul 2018 12:03:56 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.bultmann.eu (unknown [IPv6:2a00:c380:c0d5:1:2971:e363:baad:4e05]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 0C63F17860 for ; Wed, 25 Jul 2018 12:03:48 +0000 (UTC) Subject: Re: ZFS backup Q: send/recv and mountpoint property To: freebsd-fs@freebsd.org References: From: Jan Bramkamp Message-ID: <7631a2af-8041-4666-3cef-ebbeed31eabf@rlwinm.de> Date: Wed, 25 Jul 2018 14:03:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 12:03:57 -0000 On 22.07.18 20:14, Dmitry Morozovsky wrote: > Colleagues, > > still stuck in compiling stable procedure. > > Prerequisites: > > - some servers, all on ZFS, with layout such as > machine -> unique pool name, usually 2-letters, say, hm and im > > - zfs layouts like > > hm/R/${fs}, like > hm/R > hm/R/usr > hm/R/usr/local > hm/R/var > hm/R/home > etc, where hm/R has property mountpoint=/ and others just inherit it > > > - on servers, zfs allows for non-root user to make snapshots, hold, etc, like > > Local+Descendent permissions: > group operator hold,send,snapshot > > - zfs send -R [-i pool@prev-snap] pool@now-snap | \ > ssh backupserver 'zfs recv tgpool/B/zfs/srvname' > > Problem: > > 0. on backup (zfs recv) server, I could not > - overwrite mountpoint property (and I'd better avoid it) > - add canmount=off, especially for child filesets, as it's not inherited (which > could be preferred behaviour) > > 1. after backup server reboot, if special manual tweaks did not have place, > filesets from backup images overwrite backup filesets, render it unuseable > > Any hints? > > Or did I missed something trivial? You missed the normal non-replication streams. Those contain only the dataset and not its properties. You can use those to backup the dataset and a wrapper script to deal with the dataset's properties. The zxfer script does all that for you. From owner-freebsd-fs@freebsd.org Wed Jul 25 22:55:33 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF62D10560AA for ; Wed, 25 Jul 2018 22:55:33 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4A90671686 for ; Wed, 25 Jul 2018 22:55:33 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0C6D410560A9; Wed, 25 Jul 2018 22:55:33 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED82510560A8 for ; Wed, 25 Jul 2018 22:55:32 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6678B71685 for ; Wed, 25 Jul 2018 22:55:32 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost [IPv6:::1]) by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id w6PMxhDt055842; Wed, 25 Jul 2018 15:59:43 -0700 (PDT) (envelope-from mckusick@mckusick.com) Message-Id: <201807252259.w6PMxhDt055842@chez.mckusick.com> From: Kirk McKusick To: "Mikhail T." Subject: Re: core dumps onto ZFS cc: fs@freebsd.org X-URL: http://WWW.McKusick.COM/ Reply-To: Kirk McKusick In-reply-to: Comments: In-reply-to "Mikhail T." message dated "Tue, 24 Jul 2018 21:38:26 -0400." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <55840.1532559583.1@chez.mckusick.com> Date: Wed, 25 Jul 2018 15:59:43 -0700 X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chez.mckusick.com X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 22:55:33 -0000 Is there any chance that your filesystem was more than 90% full? Once ZFS gets past 90% full its performance drops precipitously. As it approaches completely full it locks up for minutes per write doing huge numbers of writes to its pool in an attempt to consolodate what little free space it has left into something big enough for it to use (which it sounds like is happening to you). Kirk McKusick From owner-freebsd-fs@freebsd.org Thu Jul 26 02:32:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8016F105B48A for ; Thu, 26 Jul 2018 02:32:09 +0000 (UTC) (envelope-from mi+m@aldan.algebra.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 12EBF77812 for ; Thu, 26 Jul 2018 02:32:09 +0000 (UTC) (envelope-from mi+m@aldan.algebra.com) Received: by mailman.ysv.freebsd.org (Postfix) id CBCFD105B482; Thu, 26 Jul 2018 02:32:08 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA849105B481 for ; Thu, 26 Jul 2018 02:32:08 +0000 (UTC) (envelope-from mi+m@aldan.algebra.com) Received: from natasha.teterin.net (symbion.zaytman.com [64.112.176.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "symbion", Issuer "Narawntapu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 30B147780C for ; Thu, 26 Jul 2018 02:32:07 +0000 (UTC) (envelope-from mi+m@aldan.algebra.com) Received: from [100.106.130.79] (32.sub-174-202-27.myvzw.com [174.202.27.32]) (authenticated bits=0) by natasha.teterin.net (8.15.2/8.15.2) with ESMTPSA id w6Q2Vrg1012609 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jul 2018 22:31:54 -0400 (EDT) (envelope-from mi+m@aldan.algebra.com) X-Authentication-Warning: natasha.teterin.net: Host 32.sub-174-202-27.myvzw.com [174.202.27.32] claimed to be [100.106.130.79] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: core dumps onto ZFS From: "Mikhail T." X-Mailer: iPhone Mail (15F79) In-Reply-To: <201807252259.w6PMxhDt055842@chez.mckusick.com> Date: Wed, 25 Jul 2018 22:31:48 -0400 Cc: "Mikhail T." , fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2EEED9B8-A743-4901-8539-9A8C2E42ED21@aldan.algebra.com> References: <201807252259.w6PMxhDt055842@chez.mckusick.com> To: Kirk McKusick X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 02:32:09 -0000 No, most certainly not. In fact, it is hardly used at all... Only about 15% o= f the 9TB... Maybe, the log-device filled up - not sure. Could core-dumping be bypassing something, thus triggering what normal writi= ng would not? --=20 Sent from mobile device, please, pardon shorthand. 25 =D0=BB=D0=B8=D0=BF. 2018 =D1=80. =D0=BE 18:59 Kirk McKusick =D0=BF=D0=B8=D1=88=D0=B5: > Is there any chance that your filesystem was more than 90% full? >=20 > Once ZFS gets past 90% full its performance drops precipitously. > As it approaches completely full it locks up for minutes per write > doing huge numbers of writes to its pool in an attempt to consolodate > what little free space it has left into something big enough for > it to use (which it sounds like is happening to you). >=20 > Kirk McKusick From owner-freebsd-fs@freebsd.org Thu Jul 26 04:41:00 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A119103C9DA for ; Thu, 26 Jul 2018 04:41:00 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 06F977CA5C; Thu, 26 Jul 2018 04:40:59 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6Q4dbeM050336 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jul 2018 21:39:37 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6Q4dbFg050335; Wed, 25 Jul 2018 21:39:37 -0700 (PDT) (envelope-from warlock) Date: Wed, 25 Jul 2018 21:39:37 -0700 From: John Kennedy To: Andriy Gapon Cc: freebsd-fs@freebsd.org Subject: Re: CRC32Mounting from zfs:zroot/ROOT/default failed with error 2 Message-ID: <20180726043937.GC75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 04:41:00 -0000 On Tue, Jul 24, 2018 at 11:33:52AM +0300, Andriy Gapon wrote: > This seems like possibly the same problem as > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229972 > That bug report also describes getting error 2 (ENOENT). > Your report adds an additional detail, "unknown file system". > That means that vfs_byname() cannot find "zfs" filesystem type. > As-if zfs module was not loaded. Before I try to make this a bug report, lets sanity-check this. My partitions: => 63 124735425 da0 MBR (59G) 63 1985 - free - (993K) 2048 104448 1 fat32lba [active] (51M) 106496 124624896 2 freebsd (59G) 124731392 4096 - free - (2.0M) => 0 124624896 da0s2 BSD (59G) 0 92274688 1 freebsd-zfs (44G) 92274688 16777216 2 freebsd-ufs (8.0G) 109051904 15572992 4 freebsd-swap (7.4G) I took the dump when I was creating it, now da0s1 -> mmcsd0s1. That part works since it'll boot into the kernel, and when that fails to boot into the -zfs partition, I can boot into the -ufs partition at the mountroot> prompt. I created the ZFS pool like this: zpool create -f -m none -o altroot=/mnt/dst zroot ${DISK}s2a zfs set compression=lz4 atime=off zroot zfs create -o mountpoint=none zroot/ROOT zfs create zroot/ROOT/default zfs set mountpoint=/ canmount=noauto zroot/ROOT/default zpool set bootfs=zroot/ROOT/default zroot I've added zfs_load="YES" to /boot/loader.conf, and zfs_enable="YES" into the /etc/rc.conf file. I don't have a / mountpoint specified in /etc/fstab like I do with the UFS root, but I don't have that on my amd64 ZFS system. No errors detected during scrub: # zpool status -v pool: zroot state: ONLINE scan: scrub repaired 0 in 0 days 00:00:47 with 0 errors on Wed Jul 25 21:21:28 2018 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mmcsd0s2a ONLINE 0 0 0 errors: No known data errors Things look good to me: # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zroot 43.5G 809M 42.7G - - 1% 1% 1.00x ONLINE - # zfs list -tall NAME USED AVAIL REFER MOUNTPOINT zroot 809M 41.4G 23K /zroot zroot/ROOT 809M 41.4G 23K none zroot/ROOT/default 809M 41.4G 809M / I only added zfs_load="YES" to /boot/loader.conf (which is all I did for amd64) but I've noticed in some old recipes that opensolaris is also added, and I see it now, as a dependency I'm guessing: # kldstat Id Refs Address Size Name 1 25 0xffff000000000000 13eba80 kernel 3 1 0xffff000054400000 2c2000 zfs.ko 4 1 0xffff0000546c2000 47000 opensolaris.ko 5 1 0xffff000054709000 41000 tmpfs.ko 6 1 0xffff00005474a000 41000 if_muge.ko 7 1 0xffff00005478b000 41000 ums.ko 8 1 0xffff000054a00000 41000 uhid.ko From owner-freebsd-fs@freebsd.org Thu Jul 26 05:23:34 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6EE8103FBC1 for ; Thu, 26 Jul 2018 05:23:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 57D0E7E4BF for ; Thu, 26 Jul 2018 05:23:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1BFA3103FBC0; Thu, 26 Jul 2018 05:23:34 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE251103FBBF for ; Thu, 26 Jul 2018 05:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 780027E4BE for ; Thu, 26 Jul 2018 05:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id w16-v6so1149639ita.0 for ; Wed, 25 Jul 2018 22:23:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5ZbuzWFb05kcCtlP0k1Tn6UvFIbchDgGdXuKBUi7hyI=; b=o8rUa5YFxLD+0aj2P4oBe9GBNWMyYBo3lwxqizv1tGcfhegCTF+uBNLBq0vXaWi9z1 Mc/op+2C9qAY2N7ZbHpTEoqLT4B5EVKmoWycMhzPVURUX7y+/1lM844vGuEUHLulDdzd YRDMCk7ycQTwjkdI3HU3RU3Vg5s8eUmX78BoykzXzBBJj0jJUPKLbRV9Gd/P1keJHbPl m6KK7+m3qCRY42DKhwItZu8ndnZe/VGGCTkeZMpXN9lAmCdmR2OcFqnsb7TZoiBzZGOu zQ4rjdcByUEGcYF3Ohg2gT8ywRpJd3vE+PHkph0LFY5gCbI2qGK6QF0FkZQRgtMEBsHV cUnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5ZbuzWFb05kcCtlP0k1Tn6UvFIbchDgGdXuKBUi7hyI=; b=jYjxGFFcBJPGB6Pb1D0s332i0KBV2NAp0FEF0n6cgnzUbPBPv18iDNpDgOLuKjYGku bU+HvNdyGwABx0uP3JGBHVcNLDP/QHc+/kP2wQXFgn0gUkGaJmAbV+++J7Be8aZT7FtV nbfufZhkAP4bfgcC3omTXl02T4jEuIqr48JXt45Lj8c5K6wxPfVNus6S6r1DPZ84HMQa ltX2LNr7z3CJYvjBtoU/YWyA6LeFXgxNDbvXhfGOyH3ydRSdkDV7pz1QG4gL5f9SHLbv CoSBuiXP+ro4CxJO9eqnohiye2TMoWla67Kqso3djB38fUV55t4fEAvmsmQ8z/tTBt+W EfZw== X-Gm-Message-State: AOUpUlFuCw1njJmX1s+01eZJ2yQ+sVQIgp4uWxmGlE1UUwBmTw6IXt13 bzgoTUxHw3qUcZ+N7qqXblsgn1jeZc17bz5rKl5OL2/5ikg= X-Google-Smtp-Source: AAOMgpdj0KjpL8O1OcyWQUGuKKb2OJmIOQm7HIV5M+aWRelaSlbVHMLtTISalzb4DGQ1BwYDjq603UrCCIdS3kq4lVM= X-Received: by 2002:a02:a701:: with SMTP id k1-v6mr452575jam.140.1532582612438; Wed, 25 Jul 2018 22:23:32 -0700 (PDT) MIME-Version: 1.0 References: <201807252259.w6PMxhDt055842@chez.mckusick.com> In-Reply-To: <201807252259.w6PMxhDt055842@chez.mckusick.com> From: Warner Losh Date: Wed, 25 Jul 2018 23:23:21 -0600 Message-ID: Subject: Re: core dumps onto ZFS To: Kirk McKusick Cc: "Mikhail T." , fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 05:23:35 -0000 On Jul 25, 2018 4:56 PM, "Kirk McKusick" wrote: Is there any chance that your filesystem was more than 90% full? Once ZFS gets past 90% full its performance drops precipitously. As it approaches completely full it locks up for minutes per write doing huge numbers of writes to its pool in an attempt to consolodate what little free space it has left into something big enough for it to use (which it sounds like is happening to you). Write amplification (the amount of extra writing described here) approaches 1 / free-space as free-space goes to zero... so 1% empty is 10x slower than 10% empty, but that is only 2x slower than 80% full. I say tends because the more free space you have, the greater the odds you have ready space to write without GC. Warner Kirk McKusick _______________________________________________ freebsd-fs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Fri Jul 27 03:20:17 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D140105F22A for ; Fri, 27 Jul 2018 03:20:17 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E561D81E18 for ; Fri, 27 Jul 2018 03:20:16 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6R3J0kO054322 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 26 Jul 2018 20:19:00 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6R3IxOJ054321 for freebsd-fs@freebsd.org; Thu, 26 Jul 2018 20:18:59 -0700 (PDT) (envelope-from warlock) Date: Thu, 26 Jul 2018 20:18:59 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: Re: Mounting from zfs:zroot/ROOT/default failed with error 2 (and 6) Message-ID: <20180727031859.GD75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> <20180726043937.GC75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180726043937.GC75644@phouka1.phouka.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 03:20:17 -0000 First off, subject change. I've become convinced that what I'm seeing is two error messages being mashed together: [Normal RPI3B+ kernel output ... CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Instruction Set Attributes 0 = Instruction Set Attributes 1 = <0> ... ... and the messages + error: Trying to mount root from zfs:zrasp/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 2 Digging out that error gets a lot more hits, although typically years old. As I said, if I comment out zfs_enable="YES" and zfs_load="YES" and boot into My UFS partition, I can see that the extra modules that get loaded using ZFS are zfs.ko and opensolaris.ko, even though there are other dependencies: [strings -a < opensolaris.ko | grep _depend_on_] _opensolaris_depend_on_kernel [strings -a < zfs.ko | grep _depend_on_] _zfsctrl_depend_on_acl_nfs4 _zfsctrl_depend_on_kernel _zfsctrl_depend_on_krpc _zfsctrl_depend_on_opensolaris _zfs_depend_on_kernel _zfs_zvol_depend_on_kernel _zfs_vdev_depend_on_kernel If I add opensolaris, sort of progress. Root mount waiting for: usbus0 Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 3 more seconds Mounting from zfs:zroot/ROOT/default failed with error 6 Not only that, it looks like it gets me in a non-writing mode: ZFS WARNING: Unable to open diskid/DISK-73180AA8s2 for writing (error=1). Adding in these two didn't seem to make any difference at all (didn't see a load *.ko message): acl_nfs4_load="YES" krpc_load="YES" For what it's worth: [usbconfig list] ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (98mA) -> Standard Microsystems Corp. USB 2.0 Hub? That's presumably my entire BSD space, including UFS which hangs booting (well, I waited over 10 minutes stayed at "Tryint to mount root" message). If I power cycle, interrupt the loader, unload everything and just load the kernel I can get into the UFS partition just fine from the mountroot> prompt. If I start up with "boot -v", I see some new messages: GEOM_PART: partition 1 on (mmcsd0, MBR) is not aligned to 4194304 bytes GEOM_PART: partition 1 on (diskid/DISK-73180AAB, MBR) is not aligned to 4194304 bytes Those alternate about 5 times inbetween the second-by-second "error 6" countdown. I'm going to rebuild it with that partition aligned and see what happens. From owner-freebsd-fs@freebsd.org Fri Jul 27 06:08:08 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BA1B1061E66 for ; Fri, 27 Jul 2018 06:08:08 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EA8B386BDE for ; Fri, 27 Jul 2018 06:08:07 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6R66jSn054687 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 26 Jul 2018 23:06:45 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6R66jdn054686 for freebsd-fs@freebsd.org; Thu, 26 Jul 2018 23:06:45 -0700 (PDT) (envelope-from warlock) Date: Thu, 26 Jul 2018 23:06:44 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: Re: Mounting from zfs:zroot/ROOT/default failed with error 6 Message-ID: <20180727060644.GE75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> <20180726043937.GC75644@phouka1.phouka.net> <20180727031859.GD75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180727031859.GD75644@phouka1.phouka.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 06:08:08 -0000 On Thu, Jul 26, 2018 at 08:18:59PM -0700, John Kennedy wrote: > ... If I add opensolaris, sort of progress: > > Root mount waiting for: usbus0 > Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 3 more seconds > Mounting from zfs:zroot/ROOT/default failed with error 6 > > Not only that, it looks like it gets me in a non-writing mode: > > ZFS WARNING: Unable to open diskid/DISK-73180AA8s2 for writing (error=1). > > ... If I start up with "boot -v", I see some new messages: > > GEOM_PART: partition 1 on (mmcsd0, MBR) is not aligned to 4194304 bytes > GEOM_PART: partition 1 on (diskid/DISK-73180AAB, MBR) is not aligned to 4194304 bytes > > Those alternate about 5 times inbetween the second-by-second "error 6" countdown. > > I'm going to rebuild it with that partition aligned and see what happens. Fixing the partition alignment gets rid of that message, but doesn't get the system to boot. I grabbed FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180726-r336739.img and then rebuilt with that. That has issues: devfs didn't enumerate things like /dev/msdosfs ethernet (ue0) isn't showing up as a device (just lo0) (kldload ums fixed that) umodem.ko didn't find depedency (ucom.ko) On a plus, it didn't hang. Even though it was exported and destroyed, a previous incarnation of zroot is cursing me. So, have to wipe the card and reburn tomorrow. An edited /var/log/messages after boot: ... FreeBSD 12.0-CURRENT #0 r336739: Thu Jul 26 18:05:26 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 ... Preloaded elf kernel "/boot/kernel/kernel" at 0xffff000001786000. Preloaded elf module "/boot/kernel/umodem.ko" at 0xffff00000178f068. Preloaded elf module "/boot/kernel/opensolaris.ko" at 0xffff00000178f880. Preloaded elf module "/boot/kernel/zfs.ko" at 0xffff00000178ffa0. KLD file umodem.ko is missing dependencies ... bcm283x_dwcotg0: mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 43,44 on simplebus0 usbus0 on bcm283x_dwcotg0 ... usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 64GB at mmc0 50.0MHz/4bit/65535-block GEOM: new disk mmcsd0 Root mount waiting for: usbus0 ugen0.2: at usbus0 uhub1: on usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 uhub2: on usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 ukbd0: on usbus0 ... Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 3 more seconds Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 2 more seconds Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 1 more second Mounting from zfs:zroot/ROOT/default failed with error 6. Loader variables: vfs.root.mountfrom=zfs:zroot/ROOT/default Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> Trying to mount root from ufs:/dev/ufs/uroot []... Warning: no time-of-day clock registered, system time will not be set accurately start_init: trying /sbin/init ZFS WARNING: Unable to open diskid/DISK-73180AABs2 for writing (error=1). ... From owner-freebsd-fs@freebsd.org Fri Jul 27 13:08:34 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17FC4104A1D0 for ; Fri, 27 Jul 2018 13:08:34 +0000 (UTC) (envelope-from fuz@fuz.su) Received: from fuz.su (fuz.su [IPv6:2001:41d0:8:e508::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A0FB473AAE for ; Fri, 27 Jul 2018 13:08:33 +0000 (UTC) (envelope-from fuz@fuz.su) Received: from fuz.su (localhost [127.0.0.1]) by fuz.su (8.15.2/8.15.2) with ESMTPS id w6RD7h22046647 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 27 Jul 2018 15:07:43 +0200 (CEST) (envelope-from fuz@fuz.su) Received: (from fuz@localhost) by fuz.su (8.15.2/8.15.2/Submit) id w6RD7h5K046646 for freebsd-fs@freebsd.org; Fri, 27 Jul 2018 15:07:43 +0200 (CEST) (envelope-from fuz) Date: Fri, 27 Jul 2018 15:07:43 +0200 From: Robert Clausecker To: freebsd-fs@freebsd.org Subject: badsect(8) is gone -- what now? Message-ID: <20180727130743.GB45967@fuz.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 13:08:34 -0000 Good evening, I recently tried to use badsect(8) to salvage a slightly broken disk with some janky sectors which the drive doesn't remap but still likes to complain about, just to find out that kernel support for badsect(8) is no longer available in FreeBSD 11.2. This is an annoying situation as I have no way to stop these sectors from being used otherwise. Is there any way the kernel interface for badsect(8) or a utilitiy fulfilling a similar purpose is going to come back? I understand that kernel support was removed due to possible misuse of mknod(S_IFMT) leading to crashes [1], but there really ought to be some way to mark a sector as bad if the disk doesn't want to do it for you. Yours, Robert Clausecker [1]: https://www.mail-archive.com/svn-src-all@freebsd.org/msg151790.html -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments From owner-freebsd-fs@freebsd.org Fri Jul 27 13:46:00 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 470AE104B39C for ; Fri, 27 Jul 2018 13:46:00 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D47C975147 for ; Fri, 27 Jul 2018 13:45:59 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6RDigfo056044 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 27 Jul 2018 06:44:42 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6RDigVM056043 for freebsd-fs@freebsd.org; Fri, 27 Jul 2018 06:44:42 -0700 (PDT) (envelope-from warlock) Date: Fri, 27 Jul 2018 06:44:42 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: Re: Mounting from zfs:zroot/ROOT/default failed with error 6 Message-ID: <20180727134442.GF75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> <20180726043937.GC75644@phouka1.phouka.net> <20180727031859.GD75644@phouka1.phouka.net> <20180727060644.GE75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180727060644.GE75644@phouka1.phouka.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 13:46:00 -0000 On Thu, Jul 26, 2018 at 11:06:44PM -0700, John Kennedy wrote: > I grabbed FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180726-r336739.img and then > rebuilt with that. That has issues: > > devfs didn't enumerate things like /dev/msdosfs > ethernet (ue0) isn't showing up as a device (just lo0) > (kldload ums fixed that) > umodem.ko didn't find depedency (ucom.ko) > > On a plus, it didn't hang. > > Even though it was exported and destroyed, a previous incarnation of zroot > is cursing me. So, have to wipe the card and reburn tomorrow. So I've had this issue before. Writing the SDCARD out for RPI takes so long that I destroy partitions and have to be very careful about destroying the zpool otherwise it ends up lingering. Sometimes, it manages to survive anyway and the boot process can latch onto and resurrect that now horribly corrupted space. Long story short, after wiping and rebuilding again, some ZFS success! [df -h] Filesystem Size Used Avail Capacity Mounted on zrasp/ROOT/default 38G 814M 37G 2% / devfs 1.0K 1.0K 0B 100% /dev tmpfs 50M 4.0K 50M 0% /tmp I didn't have a problem with umodem.ko or ums.ko this time. The devfs still has some weirdness going on though. I don't see /dev/msdos, /dev/ufs, or /dev/mmcsd0s2* [zpool status -v] pool: zrasp state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zrasp ONLINE 0 0 0 diskid/DISK-3C748841s2a ONLINE 0 0 0 errors: No known data errors [gpart show] => 63 124735425 diskid/DISK-3C748841 MBR (59G) 63 8129 - free - (4.0M) 8192 98304 1 fat32lba [active] (48M) 106496 124624896 2 freebsd (59G) 124731392 4096 - free - (2.0M) => 0 124624896 diskid/DISK-3C748841s2 BSD (59G) 0 83886080 1 freebsd-zfs (40G) 83886080 25165824 2 freebsd-ufs (12G) 109051904 15572992 4 freebsd-swap (7.4G) [ls -las /dev/mmcsd0*] 0 crw-r----- 1 root operator 0x47 Jul 27 06:15 /dev/mmcsd0 [ls -las /dev/diskid] total 1 1 dr-xr-xr-x 2 root wheel 512 Jul 27 06:15 . 1 dr-xr-xr-x 11 root wheel 512 Jul 27 06:15 .. 0 crw-r----- 1 root operator 0x4f Jul 27 06:15 DISK-3C748841 0 crw-r----- 1 root operator 0x54 Jul 27 06:15 DISK-3C748841s1 0 crw-r----- 1 root operator 0x55 Jul 27 06:15 DISK-3C748841s2 0 crw-r----- 1 root operator 0x58 Jul 27 06:15 DISK-3C748841s2a 0 crw-r----- 1 root operator 0x59 Jul 27 06:15 DISK-3C748841s2b 0 crw-r----- 1 root operator 0x5a Jul 27 06:15 DISK-3C748841s2d From owner-freebsd-fs@freebsd.org Fri Jul 27 23:20:53 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A746105A059 for ; Fri, 27 Jul 2018 23:20:53 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E34A58E6E8 for ; Fri, 27 Jul 2018 23:20:52 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6RNJYBW057280 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 27 Jul 2018 16:19:35 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6RNJYEV057279 for freebsd-fs@freebsd.org; Fri, 27 Jul 2018 16:19:34 -0700 (PDT) (envelope-from warlock) Date: Fri, 27 Jul 2018 16:19:34 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: arm64 devfs: /dev/diskid/* Message-ID: <20180727231934.GG75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> <20180726043937.GC75644@phouka1.phouka.net> <20180727031859.GD75644@phouka1.phouka.net> <20180727060644.GE75644@phouka1.phouka.net> <20180727134442.GF75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180727134442.GF75644@phouka1.phouka.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 23:20:53 -0000 If you're following this thread, you know that I'm trying to get ZFS boot (but have a UFS backup) RPI3B+ setup. TL/DR: Initially had issues, mucked about, issues seemed to have stopped, why? I can't say that I've seen that happen everywhere else, and I think I'd have noticed since my swap space would have issues. Looking at the web, it looks like I might get that under ZFS when it latches onto the diskid. I "mucked" with it by booting into my UFS partition, mounting the ZFS partition and put some previous kernels into the ZFS /boot. Maybe that seeded it with the more current name? It was initially created hanging off the system as an adapter-connected da0* but was then inserted back into the SDCARD slot and should then be mmcsd0*. * * * * * Yesterday, a new version came out: FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180726-r336739.img.xz FreeBSD rpi3.phouka.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r336739: Thu Jul 26 18:05:26 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 When I boot into ZFS, My disk devices seem to have moved into /dev/diskid [UFS gpart show] => 63 124735425 mmcsd0 MBR (59G) 63 8129 - free - (4.0M) 8192 98304 1 fat32lba [active] (48M) 106496 124624896 2 freebsd (59G) 124731392 4096 - free - (2.0M) => 0 124624896 mmcsd0s2 BSD (59G) 0 83886080 1 freebsd-zfs (40G) 83886080 25165824 2 freebsd-ufs (12G) 109051904 15572992 4 freebsd-swap (7.4G) [ZFS gpart show] => 63 124735425 diskid/DISK-3C748841 MBR (59G) 63 8129 - free - (4.0M) 8192 98304 1 fat32lba [active] (48M) 106496 124624896 2 freebsd (59G) 124731392 4096 - free - (2.0M) => 0 124624896 diskid/DISK-3C748841s2 BSD (59G) 0 83886080 1 freebsd-zfs (40G) 83886080 25165824 2 freebsd-ufs (12G) 109051904 15572992 4 freebsd-swap (7.4G) Booting UFS, I see my fstype-mapped names. Booting ZFS, I don't: [ls -las /dev/msdosfs/* /dev/ufs/*] 0 crw-r----- 1 root operator 0x4f Jul 27 21:19 /dev/msdosfs/UBOOT 0 crw-r----- 1 root operator 0x56 Jul 27 13:06 /dev/ufs/uroot Booting ZFS, /dev/mmcsd0* isn't populated, but /dev/diskid is: [ls -las /dev/mmcsd0*] 0 crw-r----- 1 root operator 0x47 Jul 27 06:15 /dev/mmcsd0 [ls -las /dev/diskid] total 1 1 dr-xr-xr-x 2 root wheel 512 Jul 27 06:15 . 1 dr-xr-xr-x 11 root wheel 512 Jul 27 06:15 .. 0 crw-r----- 1 root operator 0x4f Jul 27 06:15 DISK-3C748841 0 crw-r----- 1 root operator 0x54 Jul 27 06:15 DISK-3C748841s1 0 crw-r----- 1 root operator 0x55 Jul 27 06:15 DISK-3C748841s2 0 crw-r----- 1 root operator 0x58 Jul 27 06:15 DISK-3C748841s2a 0 crw-r----- 1 root operator 0x59 Jul 27 06:15 DISK-3C748841s2b 0 crw-r----- 1 root operator 0x5a Jul 27 06:15 DISK-3C748841s2d Booting UFS, the SDCARD devices are where I've come to expect them: [ls -las /dev/mmcsd0*] 0 crw-r----- 1 root operator 0x46 Jul 27 21:19 /dev/mmcsd0 0 crw-r----- 1 root operator 0x4c Jul 27 21:19 /dev/mmcsd0s1 0 crw-r----- 1 root operator 0x4d Jul 27 21:19 /dev/mmcsd0s2 0 crw-r----- 1 root operator 0x50 Jul 27 21:19 /dev/mmcsd0s2a 0 crw-r----- 1 root operator 0x51 Jul 27 21:19 /dev/mmcsd0s2b 0 crw-r----- 1 root operator 0x52 Jul 27 21:19 /dev/mmcsd0s2d I tried to boot up into a previous kernel (from rpi3-20180719-r336479) once, didn't get it right, but when I rebooted back with the normal kernel it worked. I haven't messed with kern.geom.label.*: [sysctl kern.geom.label] kern.geom.label.disk_ident.enable: 1 kern.geom.label.gptid.enable: 1 kern.geom.label.gpt.enable: 1 kern.geom.label.ufs.enable: 1 kern.geom.label.ufsid.enable: 1 kern.geom.label.reiserfs.enable: 1 kern.geom.label.ntfs.enable: 1 kern.geom.label.msdosfs.enable: 1 kern.geom.label.iso9660.enable: 1 kern.geom.label.ext2fs.enable: 1 kern.geom.label.debug: 0