From owner-freebsd-fs@freebsd.org Sun Feb 25 01:54:15 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 65AD5F34BE3 for ; Sun, 25 Feb 2018 01:54:15 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 04F9D82A9D for ; Sun, 25 Feb 2018 01:54:14 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-it0-x22e.google.com with SMTP id k79so4404979ita.2 for ; Sat, 24 Feb 2018 17:54:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=IF3iHuB/pSXrwOL8Z3Rn/e/Hh6jwcM1Pt8szY2uOyc4=; b=G3LHsnwmiWhIoibHz7nH3bvrXZidm+3rxASInm5CtY3F6XhmeISTws7HEOL0smMtBX VY2oWodcVi28HjDjYqflbRpYQhweSgFXnHiGRwKWub2eyuZMcxZo9Xu4eu0Y3NsErHNj s+841p/1UPXKlgTD2UDoMfl8zwN3cPxeXbP40Yn9B1ZdnZQyWXCzBNk04i2VKfiVAzq1 DPUfm0L9M+HKXSWWW/+kaRpFZXUYnoZgFi8d0G/xWQSLCSSRxjemFFMnysA+u+mvsUcF D4RAQXc8V1I9PSDWGOkqGkw+7x/9IrzRHntGxGBjoOWeeVtsFNRIzAPlQxAjRKohVtNb iaSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IF3iHuB/pSXrwOL8Z3Rn/e/Hh6jwcM1Pt8szY2uOyc4=; b=ge7x24FVFyNEl+shBxOAy6LGY5ulMAhdAwYpHrcc13IMpC81rSsQYRS92Imn3wdmMF s6VN/peRqZj3vikcDMBThciRv2uV07r3qTMaJaYLoPkbTPsqGB0E/nxIbMbnbB6rGFln SZGx1u97/1qAc6qaRNZWNUhkBLmtcmiN7jc2jQtW9i8aLXQ0avIDqzg05R37B+sUetB1 +rmGQdh844AdrjHY5CmDnIryjNhnNb6Kr8ZIWIi6Mm6bOSrFx3w6ZYGj9gdGPSRUmg8C cDWNzQ3I9woMlOnkN7GEBPnPovC43WStKadZEhrpsqS7S+Wou5c33XyYPBVnXt4+URsW mUAA== X-Gm-Message-State: APf1xPBbXQe+y8NRU8K+SYzfWyyvqkcvZlSSx+hoV7M/htYUvI58/9B1 ifw8Ii6F0pf9NMMpqVHdUKa78Dot1EN8TWORVLIaaw== X-Google-Smtp-Source: AG47ELtbMa/RY06q69Df/cyjHhkitiO5L8rfY/EywHsnu0vJ7hpe1X14s2rgNv9BlmdDyvTBczGd+lVpmRYdtkZh5Co= X-Received: by 10.36.44.9 with SMTP id i9mr6843476iti.95.1519523654094; Sat, 24 Feb 2018 17:54:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.155.169 with HTTP; Sat, 24 Feb 2018 17:54:12 -0800 (PST) From: Aijaz Baig Date: Sun, 25 Feb 2018 07:24:12 +0530 Message-ID: Subject: Regarding vop_vector To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2018 01:54:15 -0000 Hello I am trying to understand how the VFS layer within FreeBSD and I was rather stumped while trying to find where vop_vector was declared. Upon searching the internet, realized that an awk script is used to "generate" this like so: /sys/tools/vnode_if.awk /sys/kern/vnode_if.src -q So I was wondering if anyone could provide me a (brief would be fine as well) walk through the memory lane as to why such an 'odd looking' way was adopted (perhaps it is brilliant but my thick skull is unable to fathom it's brilliance). Keen to hear from you experts out there please! -- Best Regards, Aijaz Baig From owner-freebsd-fs@freebsd.org Sun Feb 25 10:24:49 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 E4C3DF26F20 for ; Sun, 25 Feb 2018 10:24:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 6301075480 for ; Sun, 25 Feb 2018 10:24:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w1PAObSR083634 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 25 Feb 2018 12:24:40 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w1PAObSR083634 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w1PAObix083633; Sun, 25 Feb 2018 12:24:37 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 25 Feb 2018 12:24:37 +0200 From: Konstantin Belousov To: Aijaz Baig Cc: freebsd-fs@freebsd.org Subject: Re: Regarding vop_vector Message-ID: <20180225102437.GN94212@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2018 10:24:49 -0000 On Sun, Feb 25, 2018 at 07:24:12AM +0530, Aijaz Baig wrote: > Hello > > I am trying to understand how the VFS layer within FreeBSD and I was rather > stumped while trying to find where vop_vector was declared. Upon searching > the internet, realized that an awk script is used to "generate" this like > so: > > /sys/tools/vnode_if.awk /sys/kern/vnode_if.src -q > > So I was wondering if anyone could provide me a (brief would be fine as > well) walk through the memory lane as to why such an 'odd looking' way was > adopted (perhaps it is brilliant but my thick skull is unable to fathom > it's brilliance). > > Keen to hear from you experts out there please! Google for the Ficus project from UCLA. From owner-freebsd-fs@freebsd.org Sun Feb 25 06:42:02 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 3669DF1C201 for ; Sun, 25 Feb 2018 06:42:02 +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 B6CA86ED29 for ; Sun, 25 Feb 2018 06:42:01 +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 w1P6g8Wm064509; Sat, 24 Feb 2018 22:42:08 -0800 (PST) (envelope-from mckusick@mckusick.com) Message-Id: <201802250642.w1P6g8Wm064509@chez.mckusick.com> From: Kirk McKusick To: Aijaz Baig Subject: Re: Regarding vop_vector cc: freebsd-fs@freebsd.org X-URL: http://WWW.McKusick.COM/ Reply-To: Kirk McKusick In-reply-to: Comments: In-reply-to Aijaz Baig message dated "Sun, 25 Feb 2018 07:24:12 +0530." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <64507.1519540928.1@chez.mckusick.com> Content-Transfer-Encoding: quoted-printable Date: Sat, 24 Feb 2018 22:42:08 -0800 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2018 06:42:02 -0000 > From: Aijaz Baig > Date: Sun, 25 Feb 2018 07:24:12 +0530 > Subject: Regarding vop_vector > To: freebsd-fs@freebsd.org > = > Hello > = > I am trying to understand how the VFS layer within FreeBSD and I was rat= her > stumped while trying to find where vop_vector was declared. Upon searchi= ng > the internet, realized that an awk script is used to "generate" this lik= e so: > = > /sys/tools/vnode_if.awk /sys/kern/vnode_if.src -q > = > So I was wondering if anyone could provide me a (brief would be fine as > well) walk through the memory lane as to why such an 'odd looking' way w= as > adopted (perhaps it is brilliant but my thick skull is unable to fathom > it's brilliance). > = > Keen to hear from you experts out there please! > -- = > Best Regards, > Aijaz Baig As the person that came up with this idea (in the 1980's) let me try to explain my thinking. Suppose you want to add a new VFS operation. Before I created the script, you had to create macros for it in at least four different files. Now you just need to add a concise and readable descripti= on of it in /sys/kern/vnode_if.src then run the script and all the boilerplat= e gets generated for you. Let me give you a short example. Consider the VFS operator to check to see if a vnode is locked, typically used as if (VOP_ISLOCKED(vp)) { do something with locked vp; } The description of it in /sys/kern/vnode_if.src is three lines: vop_islocked { IN struct vnode *vp; }; Here is what is generated for it in the compile directory by the awk scrip= t. In /sys/amd64/compile/GENERIC/vnode_if.c: static int vop_islocked_vp_offsets[] =3D { VOPARG_OFFSETOF(struct vop_islocked_args,a_vp), VDESC_NO_OFFSET }; SDT_PROBE_DEFINE2(vfs, vop, vop_islocked, entry, "struct vnode *", "struct= vop_islocked_args *"); SDT_PROBE_DEFINE3(vfs, vop, vop_islocked, return, "struct vnode *", "struc= t vop_islocked_args *", "int"); int VOP_ISLOCKED_AP(struct vop_islocked_args *a) { return(VOP_ISLOCKED_APV(a->a_vp->v_op, a)); } int VOP_ISLOCKED_APV(struct vop_vector *vop, struct vop_islocked_args *a) { int rc; VNASSERT(a->a_gen.a_desc =3D=3D &vop_islocked_desc, a->a_vp, ("Wrong a_desc in vop_islocked(%p, %p)", a->a_vp, a)); while(vop !=3D NULL && \ vop->vop_islocked =3D=3D NULL && vop->vop_bypass =3D=3D NULL) vop =3D vop->vop_default; VNASSERT(vop !=3D NULL, a->a_vp, ("No vop_islocked(%p, %p)", a->a_vp, a))= ; SDT_PROBE2(vfs, vop, vop_islocked, entry, a->a_vp, a); KTR_START1(KTR_VOP, "VOP", "VOP_ISLOCKED", (uintptr_t)a, "vp:0x%jX", (uintptr_t)a->a_vp); VFS_PROLOGUE(a->a_vp->v_mount); if (vop->vop_islocked !=3D NULL) rc =3D vop->vop_islocked(a); else rc =3D vop->vop_bypass(&a->a_gen); VFS_EPILOGUE(a->a_vp->v_mount); SDT_PROBE3(vfs, vop, vop_islocked, return, a->a_vp, a, rc); if (rc =3D=3D 0) { } else { } KTR_STOP1(KTR_VOP, "VOP", "VOP_ISLOCKED", (uintptr_t)a, "vp:0x%jX", (uintptr_t)a->a_vp); return (rc); } struct vnodeop_desc vop_islocked_desc =3D { "vop_islocked", 0, (vop_bypass_t *)VOP_ISLOCKED_AP, vop_islocked_vp_offsets, VDESC_NO_OFFSET, VDESC_NO_OFFSET, VDESC_NO_OFFSET, VDESC_NO_OFFSET, }; In /sys/amd64/compile/GENERIC/vnode_if.h: struct vop_islocked_args { struct vop_generic_args a_gen; struct vnode *a_vp; }; extern struct vnodeop_desc vop_islocked_desc; int VOP_ISLOCKED_AP(struct vop_islocked_args *); int VOP_ISLOCKED_APV(struct vop_vector *vop, struct vop_islocked_args *); static __inline int VOP_ISLOCKED( struct vnode *vp) { struct vop_islocked_args a; a.a_gen.a_desc =3D &vop_islocked_desc; a.a_vp =3D vp; return (VOP_ISLOCKED_APV(vp->v_op, &a)); } In /sys/amd64/compile/GENERIC/vnode_if_newproto.h, an entry in the vop_vector array: struct vop_vector { struct vop_vector *vop_default; vop_bypass_t *vop_bypass; vop_islocked_t *vop_islocked; ... }; And finally in /sys/amd64/compile/GENERIC/vnode_if_typedef.h: struct vop_islocked_args; typedef int vop_islocked_t(struct vop_islocked_args *); And absent this script, every time you wanted to make a change in the boilerplate, you would have to go through and fix it for every existing VFS operator (and trust me the boilerplate has changed a *lot* since I first did it in the 1980's :-) Kirk McKusick From owner-freebsd-fs@freebsd.org Sun Feb 25 21:00:54 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 6DC0AF286D5 for ; Sun, 25 Feb 2018 21:00:54 +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 075F37059F for ; Sun, 25 Feb 2018 21:00:54 +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 2EA9223435 for ; Sun, 25 Feb 2018 21:00:53 +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 w1PL0rJE097342 for ; Sun, 25 Feb 2018 21:00:53 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1PL0rnj097332 for freebsd-fs@FreeBSD.org; Sun, 25 Feb 2018 21:00:53 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201802252100.w1PL0rnj097332@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: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 25 Feb 2018 21:00:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2018 21:00:54 -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 | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d 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 8 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Feb 26 03:55:12 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 928AEF2659D for ; Mon, 26 Feb 2018 03:55:12 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 1D7FD80446 for ; Mon, 26 Feb 2018 03:55:11 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by mail-qt0-x236.google.com with SMTP id r16so8365441qtm.4 for ; Sun, 25 Feb 2018 19:55:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarchy-in-the-ph.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=oW5teyvFuUDUdPY69ZR4eZyxH+uN/AVv2VrBK1TZ1Ck=; b=pCxe/W3tO+RgCZQJt+m0xwRfq0o61RN1Ev2wQkJAU2K5nfzDD+ZCQTQk1a1wwah7j0 crRdjNpFixbO/s8S4Qrn3IoBlLh5DnGg1Phx1L5DmahAdGx9OEH4ttJvxSU9UV363csV p5s1AbbMrv3Gsx+txR7bXlrcUNZZzbbxK6cWrZA7Sy2O7LccdyoQxcC5P5eW8JFuVNzF A/oL+pdBukGUn1taI49s/ytnSGkU9A7wmYi672Ne6KQG6K9VUJWlf3rfhRn+XkmyaznD 55sPbaS/XMOXLbfKvTP8l39z83+E4H9fLRXKAh6OnrH7yNMDFwXxY88duNqc76g1O5GR +n5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oW5teyvFuUDUdPY69ZR4eZyxH+uN/AVv2VrBK1TZ1Ck=; b=lENzcLjNWHCOWas3UXqCXVLsP+NRN7/DVHS0gnJOMTmb4f50A950ezq6Cucqd8jhnJ E0IVPTYfuMxH9KaBkJK2skT8fk2QlXs2bPoDyn9LsYMpEX0+qG9A4xlEAU/i23iyMUCY YLqOjmjPlxzqFNuEfKH55e1siF4RtnsRUeYDNp295Ap7VKbqh5TNSKStTS6+M6njFHcI UdSImTYrQXk6hbpjy21bDY0hOTh1o6c0lzBFKODD/Y8FmRlZCjWk6zqro+HmQ97srB5q ilQX8u8HCZb4L5H8jDqyfLKTBUhrfPPWY/ZOdDll+wzcRNre3IEqoqzFpaaRKF1kGw/l a6ew== X-Gm-Message-State: APf1xPCXGEoiMD9ml8tAiGHB6D19qFw3uk+ysrZoKVayo4VVZ+YvJk2P 6fUFVLefst7g7cXZudGn/XMXHHMyNJ9CUZdl97WlQA== X-Google-Smtp-Source: AG47ELsbBGtHgLO66mONJ67oTE9S7hXnB1CaAdGb+gjRLW/4uINtT8r4ad/0l80nGxhVsJFmu8t9OzmmVao1+d6kePI= X-Received: by 10.200.28.84 with SMTP id j20mr15189734qtk.188.1519617310862; Sun, 25 Feb 2018 19:55:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.149.120 with HTTP; Sun, 25 Feb 2018 19:55:10 -0800 (PST) From: Mars G Miro Date: Mon, 26 Feb 2018 11:55:10 +0800 Message-ID: Subject: growfs only works on GPT partitioning schemes? To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2018 03:55:12 -0000 Hi It seems that growfs only works on GPT partitioned schemes ? When I first installed my FreeBSD, I unfortunately chose BSD during the FS creation. Now that I ran out of space, I wanted to increase the filesystem size. Successfully did so in Virtualbox but after rebooting, the HD doesn't see the new allocated space. It has another virtual HD, one created with GPT and I was able to increase it via growfs. This is on FreeBSD 11.1. Thanks. -- cheers mars ----- From owner-freebsd-fs@freebsd.org Mon Feb 26 14:22:24 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 14AE9F284BD for ; Mon, 26 Feb 2018 14:22:24 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4C8774AA for ; Mon, 26 Feb 2018 14:22:23 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id w1QEBRk7003711; Mon, 26 Feb 2018 14:11:27 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id w1QEBRxI002030; Mon, 26 Feb 2018 14:11:27 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id w1QEBRt1002026; Mon, 26 Feb 2018 14:11:27 GMT Date: Mon, 26 Feb 2018 14:11:27 GMT Message-Id: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> From: Martin Simmons To: Mars G Miro CC: freebsd-fs@freebsd.org In-reply-to: (message from Mars G Miro on Mon, 26 Feb 2018 11:55:10 +0800) Subject: Re: growfs only works on GPT partitioning schemes? References: X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2018 14:22:24 -0000 >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > It seems that growfs only works on GPT partitioned schemes ? > > When I first installed my FreeBSD, I unfortunately chose BSD during the > FS creation. Now that I ran out of space, I wanted to increase the > filesystem size. Successfully did so in Virtualbox but after rebooting, the > HD doesn't see the new allocated space. It has another virtual HD, one > created with GPT and I was able to increase it via growfs. For the BSD scheme, I think you also have to resize the slice (i.e. the MBR entry) and then resize the BSD partition within the slice. __Martin From owner-freebsd-fs@freebsd.org Mon Feb 26 14:30:18 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 83313F28D40 for ; Mon, 26 Feb 2018 14:30:18 +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 183887777A for ; Mon, 26 Feb 2018 14:30:17 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id o9so10972183itc.1 for ; Mon, 26 Feb 2018 06:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=RDclMnSAk7DALgOvL1DptWQ/J6qZ5zSnWjhBaAOOu8M=; b=JB0L4MPQGb05LIsL0v6VBelB9l1Dfgns/iG/SrPe+0wYOHJG02byxeTJdk2lOKkt40 yI7g9ZzRMum/cUV+Uo859tFNomcNWNL45bmQhWlylgoDf8i8Nomko0LOUpoBhoDKUrSh 48/ljhb1UPba1GlK/dkIkTIaVY1j5Pa2Qcm2XIPQDZCfAg/2CSWAFgRjBscarW4rFquQ hF2lST00OvrUIbEKvJnAvxvYO1lm7NolyEALTRKmPPEcBor4Puu6tWnCtImL5Cff5ny9 rCqZBdpRDwQyfSWImS+xwA4i6NaCOECSyULvbaBUrFKEfN1+VjDUARomTP3lm/f1aj5Q nuMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=RDclMnSAk7DALgOvL1DptWQ/J6qZ5zSnWjhBaAOOu8M=; b=QGTuT1NyVdtJnkhraDegTNIOtHqdb6QMkc/g06fPW0UmQXrkgSXO8x4tmxQMTZJBqh swELN8IT8nDrVyc0jkp3PPYJIrdI4k1P8jCEeIKNk9jjewRqsmBTxnYVcMlRFzrzWnFX nh7dMLYyAQiboaWjTUHnU/6EyITcRsZ0SKRycKJ6BJcTZpqwiwLYoQHBAF7ajTeQlgg8 30A9zbxSDPloIXZ2syonIvxoe24zNZREUQZ26QNOAd4Ly0EmZRCF481i4Niz9kCE2UQk nr1B7aHHcMHb1mFZ8zcyRPCXXPxfQ81QHouKMldx6RwrZ78n1kmRwaZ5NlyxQYAMplk4 ULig== X-Gm-Message-State: APf1xPC2YEb1bvgXKGHzyu3jsok8ipuCjfkL0n+OvQo2WcZ1+hd6PFnJ p5Mk+9pH2ZYVBb0YHPE9O5mtrGTq60n+Nn5mrn7HKA== X-Google-Smtp-Source: AG47ELvu52lujYL8nBt5eAkocfYLgpui3qffMGNY1/m90eVZHv7K9LzCYPB8TwEmuavb+Y6rv5E1h+Y+oH5cEitoSbU= X-Received: by 10.36.111.4 with SMTP id x4mr81567itb.51.1519655416989; Mon, 26 Feb 2018 06:30:16 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 26 Feb 2018 06:30:16 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> From: Warner Losh Date: Mon, 26 Feb 2018 07:30:16 -0700 X-Google-Sender-Auth: TldihnQKzQfYi-jPC0xUPGWG8Hk Message-ID: Subject: Re: growfs only works on GPT partitioning schemes? To: Martin Simmons Cc: Mars G Miro , FreeBSD FS Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2018 14:30:18 -0000 On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons wrote: > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > > > It seems that growfs only works on GPT partitioned schemes ? > > > > When I first installed my FreeBSD, I unfortunately chose BSD during > the > > FS creation. Now that I ran out of space, I wanted to increase the > > filesystem size. Successfully did so in Virtualbox but after rebooting, > the > > HD doesn't see the new allocated space. It has another virtual HD, one > > created with GPT and I was able to increase it via growfs. > > For the BSD scheme, I think you also have to resize the slice (i.e. the MBR > entry) and then resize the BSD partition within the slice. > You do. The /etc/rc.d script that does resize on boot does that automatically, but we have no other automation for the process. Warner From owner-freebsd-fs@freebsd.org Tue Feb 27 06:59:54 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 51A59F29ECB for ; Tue, 27 Feb 2018 06:59:54 +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 E528F85A70 for ; Tue, 27 Feb 2018 06:59:53 +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 115DE55C2 for ; Tue, 27 Feb 2018 06:59:53 +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 w1R6xqEk040282 for ; Tue, 27 Feb 2018 06:59:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1R6xqJm040281 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 06:59:52 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: freebsd-fs@FreeBSD.org Subject: [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps Date: Tue, 27 Feb 2018 06:59:52 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: deepak.ukey@microsemi.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 06:59:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225423 --- Comment #11 from Deepak Ukey --- (In reply to Deepak Ukey from comment #10) (In reply to Kirk McKusick from comment #9) Hi Kirk, Are you able to reproduce the issue. Is there any update on it. Thanks, Deepak --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 07:16:31 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 2D284F2AD40 for ; Tue, 27 Feb 2018 07:16:31 +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 BD99A86595 for ; Tue, 27 Feb 2018 07:16:30 +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 1B9F25885 for ; Tue, 27 Feb 2018 07:16:30 +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 w1R7GTg1090454 for ; Tue, 27 Feb 2018 07:16:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1R7GTo0090453 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 07:16:29 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: freebsd-fs@FreeBSD.org Subject: [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps Date: Tue, 27 Feb 2018 07:16:30 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 07:16:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225423 --- Comment #12 from Kirk McKusick --- Yes, I can easily reproduce it now that I know what you are doing. The filesystem has never been able to handle the removal of disks while running. Handling the removal or failure of disks is a project that we have started working on as part of ``hardening'' the filesystem. It requires an overhaul through not only the filesystem, but all the way down the I/O stack. We are= at least a year from having this component of the hardening working. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 15:21:16 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 7D473F2EA2A for ; Tue, 27 Feb 2018 15:21:16 +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 1D9487CFCB for ; Tue, 27 Feb 2018 15:21:16 +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 50E1F11C30 for ; Tue, 27 Feb 2018 15:21:15 +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 w1RFLFn5068373 for ; Tue, 27 Feb 2018 15:21:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RFLFqr068372 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 15:21:15 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: freebsd-fs@FreeBSD.org Subject: [Bug 226130] [zfs] [panic] solaris assert: zrl->zr_refcount == 0 (0x1 == 0x0) Date: Tue, 27 Feb 2018 15:21:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 15:21:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226130 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 15:21:42 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 4868DF2EAAC for ; Tue, 27 Feb 2018 15:21:42 +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 BBE247D05E for ; Tue, 27 Feb 2018 15:21:41 +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 E317A11C48 for ; Tue, 27 Feb 2018 15:21:40 +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 w1RFLeMH072302 for ; Tue, 27 Feb 2018 15:21:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RFLePI072301 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 15:21:40 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: freebsd-fs@FreeBSD.org Subject: [Bug 226141] "zpool remove" causes panic: solaris assert: zio->io_type == ZIO_TYPE_WRITE (0x3 == 0x2) Date: Tue, 27 Feb 2018 15:21:40 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 15:21:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226141 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 15:38:05 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 6D2CEF306A3 for ; Tue, 27 Feb 2018 15:38:05 +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 07CC37EB6E for ; Tue, 27 Feb 2018 15:38:05 +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 40F2211EF0 for ; Tue, 27 Feb 2018 15:38:04 +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 w1RFc4vl008179 for ; Tue, 27 Feb 2018 15:38:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RFc4cZ008178 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 15:38:04 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: freebsd-fs@FreeBSD.org Subject: [Bug 226096] [zfs] zpool add attach internal error: out of memory, pool with many vdevs, since r324255 Date: Tue, 27 Feb 2018 15:38:03 +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.1-STABLE X-Bugzilla-Keywords: patch, regression 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: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords cc 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 15:38:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226096 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org Keywords| |patch, regression CC| |avg@FreeBSD.org --- Comment #1 from Mark Linimon --- Notify committer of r324255. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 16:02:30 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 1EDCFF32AAA for ; Tue, 27 Feb 2018 16:02:30 +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 B192A8044F for ; Tue, 27 Feb 2018 16:02:29 +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 08FBC1233C for ; Tue, 27 Feb 2018 16:02:29 +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 w1RG2SgB080561 for ; Tue, 27 Feb 2018 16:02:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RG2SqA080560 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 16:02:28 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: freebsd-fs@FreeBSD.org Subject: [Bug 226096] [zfs] zpool add attach internal error: out of memory, pool with many vdevs, since r324255 Date: Tue, 27 Feb 2018 16:02:29 +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.1-STABLE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 16:02:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226096 --- Comment #2 from Andriy Gapon --- This differential request seems to be related https://reviews.freebsd.org/D13088 I participated in it, but dropped a ball. I'll try to get back to this issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 19:39:36 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 EE177F215A5 for ; Tue, 27 Feb 2018 19:39:35 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (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 639A06BB19; Tue, 27 Feb 2018 19:39:35 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id EBCD9201BF; Tue, 27 Feb 2018 20:39:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519760368; bh=i5e69zb46byA0Kg4gwIj2bq8AE63oL776leDOHZHnmY=; h=To:Cc:From:Subject:Date; b=rXqVmkLmVN940fOCWd0x3JwxNvbYWEu7rsNBI1QEmZkH9l+6FSj1L6csFqjzOvSnU rqWJPNxmMgyGxUrMNEE+aeDklzSkR9nwHZLn3dKfK766hNvPBVL+mp+wJJpxDLy1GQ kjXrAwPV3xRwtUdpG/4HZvhd1YF312laJukFjYmWAvTGgoT+v3YbG24pw7XjSf95U/ +fRRqL+L7VqGoVk3R+IsOuZOMe0FgwBw025UHAOi6KNGgZgQ3gGHByaQEe1FmvvWPm GV7S7djJOXb9gjsI4AQv6KyGkWrarz2LC72mlQIgsgUWNIwOqdUWs4bV8tIXNQvE8N P/zg7eRxZ6/CSrUKAXIaHAB8641GnOFQEtANJ4919Rd0l8seDUOU8wCdrzVpxqS2SF uygdvmXi1Y3kATZ60M1v4crH9gH0M6P1bCFl3tJ6wyfIt+C6HPmxeSDw75EOenmQuO M4PVV9jR2TWuHWVK7OXp8DlwZkJDMLWKzuZRzsD6IkzXWMcNAh556TiCI4wdcTyLSQ 327bOPAgGKbMkrwSHO/ZM7caccuiXhF/sLg8/FtJPlM6TFCXa0SwnvfVuOGIoHcBxN u93ni6Ek9UZDpHUj2EKmZMZo8M4oBJhwveisMTFFEWmn+Oefy97t8Rz7A1wWhbfiYx 8PMsIh6x+vTEl1mEaZbY+fo8= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 54968201AE; Tue, 27 Feb 2018 20:39:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519760365; bh=i5e69zb46byA0Kg4gwIj2bq8AE63oL776leDOHZHnmY=; h=To:Cc:From:Subject:Date; b=jn3qSZBZH69kVQQ12M7fjUP0zKPoly1RMDoFMMog80w9HInx3lDxb7qZgpxaa3CZb x9lAsU2iuNlD5v0C2q7daYwGKBtUn+prQjPVz1/eLzUmx8Jg3hobvR+QssueGt0B4g rqALuvwiPmlGPsFx6jWBmXFYZoDPx/q8FvCqQNUCjiuZ0xJI5nTMlXJ03VLIAw59hV 6ZgCqpdHGzkifXjDzw+frACJVu+WHv+HqP2/GueOeTv1Lb8PFhHb7rO3sjahATM0Dq bZDq1prm2RIpzJa/oqwTXK+u8eYJENFO03IqlqOQmfefuHZq3QMpbBytbo40s20EoJ EnCbRSUDvrUb/3X5p+8u1Hx5y+QU5JYMskuqE2sqhqAOw+ynJBGg9xPuusaz9I5xFw ozko33VEIvT7XLcAJzzC76fe+n5HXh/7qFz1joyE7MZZr/XXA+mrZKXctSEwiiqd0b h984VwsGhlwbO32vJO0Jz5RkWatNtZ7ZATKDV7EtR+iKnO2IldfxxNkB9zJ1myXxAq 6COd7ZmSF8s+Ic4E+aPME9LqXXglLyqKi0U9Bz0kNwaDltFFwyZ7PQDZDOE1LpCS1H 5MrvMCaFkPv/JRP7kt5+3uKJX6lBRg30atLM+67o9rN1Dq5umMzxXVZmHwzHpsTcAM lvB5evvEwGuVPSZll+nOjhxY= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.1 Received: from rubens-MacBook-Air.local (ip51ccb320.speed.planet.nl [81.204.179.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA; Tue, 27 Feb 2018 20:39:22 +0100 (CET) To: freebsd-fs@freebsd.org Cc: rmacklem@FreeBSD.org From: Ruben Subject: Linux NFSv4 clients: bad sequence-id errors. Message-ID: Date: Tue, 27 Feb 2018 20:39:21 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 19:39:36 -0000 Hi List, I'm experiencing a strange issue on a machine providing a couple of nfsv4 exports. A Linux client that generates a lot of traffic to and from the nfs server sometimes starts throwing "bad sequence-id errors": Feb 27 10:39:42 localhost kernel: [12481477.608103] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 80f7d0d0! They typically occur after a couple of months of uptime on the nfsd machine. Every couple of seconds they are thrown by the client. The situation is "remedied" by restarting the nfsd on the server. Although functionality on the specific client does not appear to be affected (much?), its a bit disturbing. I've done some digging and found : https://lists.freebsd.org/pipermail/freebsd-fs/2015-July/021707.html and the patch attached by Rick (  nfsv41exch.patch : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150729/586f776a/attachment.bin ) . Since the issue started manifesting itself I have restarted the nfs daemon (grabbed a pcap and the corresponding error lines mentioning the sequences prior to doing that in case anyone is interested). The nfs server runs FreeBSD 11.1 : freebsd-version -uk 11.1-RELEASE-p1 11.1-RELEASE-p1 but I have seen it on 10.2 and 11.0 as well. The linux client is (/has been) running a version of Debian. The export lines in /etc/exports : V4: / -network=192.168.9.0 -mask=255.255.255.0 /data/Sabnzb2015 -maproot=root: -alldirs -network=192.168.9.0 -mask=255.255.255.0 Uptime: 8:27PM  up 196 days, 22:10, 1 users, load averages: 0.21, 0.17, 0.17 Traffice since uptime (guessing NFS / non-NFS ratio of 3 to 1)           lagg0  in    400.901 KB/s        400.901 KB/s           10.425 TB                  out    32.781 KB/s         32.781 KB/s           14.132 TB I'm wondering: can the 2015 patch provided by Rick still be "safely" applied or has the nfs code changed too much since then? I've witnessed this issue a couple of times now and would very much like to test the patch provided. Kind regards, Ruben From owner-freebsd-fs@freebsd.org Tue Feb 27 22:01: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 E2652F2D413 for ; Tue, 27 Feb 2018 22:00:59 +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 811AB72B64 for ; Tue, 27 Feb 2018 22:00:59 +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 CBAB01545B for ; Tue, 27 Feb 2018 22:00:58 +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 w1RM0waj036122 for ; Tue, 27 Feb 2018 22:00:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RM0wVt036121 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 22:00:58 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: freebsd-fs@FreeBSD.org Subject: [Bug 219049] ftruncate() slow on UFS+journaled softupdates Date: Tue, 27 Feb 2018 22:00:56 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: info@murrawhip.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 22:01:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219049 --- Comment #8 from info@murrawhip.net --- I just tried to recreate the issue using the script in OP, but my times don= 't look as bad as Walter's. FreeBSD site.com 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 /dev/da0p2 on / (ufs, NFS exported, local, journaled soft-updates) 0.066318722 ftruncate(3,0x186a0) =3D 0 (0x0) 0.025288527 ftruncate(3,0x186a0) =3D 0 (0x0) 0.274295490 ftruncate(3,0x186a0) =3D 0 (0x0) 0.044457881 ftruncate(3,0x186a0) =3D 0 (0x0) 0.108361900 ftruncate(3,0x186a0) =3D 0 (0x0) 0.124630942 ftruncate(3,0x186a0) =3D 0 (0x0) 0.126537198 ftruncate(3,0x186a0) =3D 0 (0x0) 0.042581028 ftruncate(3,0x186a0) =3D 0 (0x0) 0.054237172 ftruncate(3,0x186a0) =3D 0 (0x0) 0.068103733 ftruncate(3,0x186a0) =3D 0 (0x0) 0.126835073 ftruncate(3,0x186a0) =3D 0 (0x0) gstat: L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d= =20=20=20 o/s ms/o %busy Name 0 7 0 0 0.0 7 115 15.4 0 0 0.0= =20=20=20=20 0 0.0 9.9 da0 0 5 0 0 0.0 5 69 15.5 0 0 0.0= =20=20=20=20 0 0.0 6.9 da0 0 1 0 0 0.0 1 0 8.7 0 0 0.0= =20=20=20=20 0 0.0 0.9 da0 0 4 0 0 0.0 4 67 23.4 0 0 0.0= =20=20=20=20 0 0.0 7.7 da0 0 5 0 0 0.0 5 68 16.0 0 0 0.0= =20=20=20=20 0 0.0 7.1 da0 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 22:11: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 3523DF2E312 for ; Tue, 27 Feb 2018 22:11:38 +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 C6F95738F2 for ; Tue, 27 Feb 2018 22:11:37 +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 F2781156FC for ; Tue, 27 Feb 2018 22:11:36 +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 w1RMBaTb068472 for ; Tue, 27 Feb 2018 22:11:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1RMBakX068471 for freebsd-fs@FreeBSD.org; Tue, 27 Feb 2018 22:11:36 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: freebsd-fs@FreeBSD.org Subject: [Bug 219049] ftruncate() slow on UFS+journaled softupdates Date: Tue, 27 Feb 2018 22:11:35 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 22:11:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219049 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markj@FreeBSD.org --- Comment #9 from Mark Johnston --- (In reply to Alexander Motin from comment #7) AFAIK, the journaling code issues BIO_FLUSH only when debug.softdep.flushca= che is set to 1, which it is not by default. I have not been able to reproduce = the issue with or without that sysctl set, but it would interesting to know whe= ther anyone that can reproduce this is setting that sysctl. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Feb 27 22:54:04 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 BD922F315BB for ; Tue, 27 Feb 2018 22:54:04 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670041.outbound.protection.outlook.com [40.107.67.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50C2C758BA; Tue, 27 Feb 2018 22:54:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM (52.132.66.153) by YQBPR0101MB1409.CANPRD01.PROD.OUTLOOK.COM (52.132.68.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.548.13; Tue, 27 Feb 2018 22:54:02 +0000 Received: from YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM ([fe80::3531:c817:d6f:9b93]) by YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM ([fe80::3531:c817:d6f:9b93%13]) with mapi id 15.20.0548.013; Tue, 27 Feb 2018 22:54:02 +0000 From: Rick Macklem To: Ruben , "freebsd-fs@freebsd.org" CC: "rmacklem@FreeBSD.org" Subject: Re: Linux NFSv4 clients: bad sequence-id errors. Thread-Topic: Linux NFSv4 clients: bad sequence-id errors. Thread-Index: AQHTsAK1+Ml+d7nQUEWuV8GTWVG+IqO42B0H Date: Tue, 27 Feb 2018 22:54:01 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YQBPR0101MB1409; 7:SNXGXZZ6hk2fgoGFz6e9qBeI/2AfD8z7s1BgP3P9TdaZmu4cTM+s2aREpx6m69rzednMIWJqQL4UdgoYJ+SfuZFg0v2GcydInsngi5E6pI9n/D9UPhgLHaJmfLG1kwwDxGEyDP8l4/ldCgJiqet1vcq53Q4J8arCpktrW6Rlmz6jpUZBRNWf03d2kdpsmFOtkHPH3n7aKU+QSgBR85abtpH/faPySzLlJm98K5rIqFAwuhI/5t6rQSIQ/QMiSK3D x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: bd807567-f045-4265-d97d-08d57e34fec0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989060)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:YQBPR0101MB1409; x-ms-traffictypediagnostic: YQBPR0101MB1409: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(265634631926514)(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231220)(944501161)(52105095)(6041288)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123560045)(6072148)(201708071742011); SRVR:YQBPR0101MB1409; BCL:0; PCL:0; RULEID:; SRVR:YQBPR0101MB1409; x-forefront-prvs: 05961EBAFC x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(346002)(39380400002)(39860400002)(376002)(366004)(396003)(189003)(199004)(8936002)(97736004)(2950100002)(186003)(786003)(316002)(106356001)(102836004)(3660700001)(99286004)(229853002)(7696005)(5660300001)(76176011)(6506007)(68736007)(81166006)(305945005)(110136005)(8676002)(26005)(74316002)(81156014)(2900100001)(1250700005)(6246003)(478600001)(3280700002)(2906002)(6306002)(55016002)(2501003)(5250100002)(5890100001)(14454004)(6436002)(53936002)(74482002)(9686003)(4326008)(25786009)(575784001)(86362001)(105586002)(33656002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:YQBPR0101MB1409; H:YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: H+T4qE2ygP5euoKCfs1UEJWFF0NLmlOvQHaL+c5+twera19FQUyoDt6TS00IQk/SUTkKdff2IxsuFGi319bW2V+l3AKng6RiTOkCPxXCi6l5i3jGPLGeqvYgm6za/J5I6k3RwTOL9J5Vka4jMI4WZLGTx3as4d5SVONJM6Ufmh8= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: bd807567-f045-4265-d97d-08d57e34fec0 X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2018 22:54:01.9618 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YQBPR0101MB1409 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 22:54:05 -0000 Ruben wrote: >I'm experiencing a strange issue on a machine providing a couple of >nfsv4 exports. A Linux client that generates a lot of traffic to and >from the nfs server sometimes starts throwing "bad sequence-id errors": > >Feb 27 10:39:42 localhost kernel: [12481477.608103] NFS: v4 server >returned a bad sequence-id error on an unconfirmed sequence 80f7d0d0! The handling of sequence-id in NFSv4.0 is complex and I won't even try to guess why this is happening. I am surprised that your Linux mounts are using NFSv4.0 and not NFSv4.1? (Usually Linux uses the most recent version supported by the server.) I mention this since "sessions" replaced the sequence-id stuff in NFSv4.1 and, as such, shouldn't have such an issue. >They typically occur after a couple of months of uptime on the nfsd >machine. Every couple of seconds they are thrown by the client. The >situation is "remedied" by restarting the nfsd on the server. Although >functionality on the specific client does not appear to be affected >(much?), its a bit disturbing. I've done some digging and found : The fact that this is fixed by restarting the nfsd suggests a client side problem. Why? Because restarting the nfsd does not reset any server state, so the sequenc= e-id situation would not be affected by doing this. (To get rid of server side s= tate, you must unload the nfsd.ko after killing off the nfsd daemon.) All restarting the nfsd daemon will do is force the client to establish a n= ew TCP connection. That is at a layer below the NFS state. >https://lists.freebsd.org/pipermail/freebsd-fs/2015-July/021707.html > >and the patch attached by Rick ( nfsv41exch.patch : >http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150729/586f776= a/attachment.bin >) . > >Since the issue started manifesting itself I have restarted the nfs >daemon (grabbed a pcap and the corresponding error lines mentioning the >sequences prior to doing that in case anyone is interested). If you email me the pcap as an attachment, I can take a look at it in wires= hark. >The nfs server runs FreeBSD 11.1 : I'm being lazy and not looking, but I am almost sure a 2015 patch will be i= n 11.1 and probably also in 10.2 and 11.0. >freebsd-version -uk >11.1-RELEASE-p1 >11.1-RELEASE-p1 > >but I have seen it on 10.2 and 11.0 as well. The linux client is (/has >been) running a version of Debian. > >The export lines in /etc/exports : > >V4: / -network=3D192.168.9.0 -mask=3D255.255.255.0 > >/data/Sabnzb2015 -maproot=3Droot: -alldirs -network=3D192.168.9.0 >-mask=3D255.255.255.0 > >Uptime: > >8:27PM up 196 days, 22:10, 1 users, load averages: 0.21, 0.17, 0.17 > >Traffice since uptime (guessing NFS / non-NFS ratio of 3 to 1) > > lagg0 in 400.901 KB/s 400.901 KB/s 10.425 T= B > out 32.781 KB/s 32.781 KB/s 14.132 T= B > > >I'm wondering: can the 2015 patch provided by Rick still be "safely" >applied or has the nfs code changed too much since then? I've witnessed >this issue a couple of times now and would very much like to test the >patch provided. As above, I'd be surprised if the patch isn't already in your 11.1 kernel, but you can take a look. If it isn't, let me know because that means it slipped through the cracks and I need to get it committed, etc. rick From owner-freebsd-fs@freebsd.org Wed Feb 28 11:45:43 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 9002AF40A4E for ; Wed, 28 Feb 2018 11:45:43 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (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 26EA172F7E; Wed, 28 Feb 2018 11:45:42 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id E5351201AE; Wed, 28 Feb 2018 12:45:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519818340; bh=OuB38v8otyRQ6LhwYO4+bjTa9Se+1OGvYTrg0tln6CM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=PyUQfFVbubMJ5M6F5Li3QPBq6R5yEue+tQ7dKf6GscrMZs0eXKRSi3UGGUzwwU79e GP/CpGuEJ0rUFzNv2uB9Ls0X70nML+0qz3dTXZQK+ElJdUfxCAmUedk+V7afAM6XW7 nYViu8tW1BjVJa6I49vwzwod0+dinJMqP+JeAYg0NwpqXUjaDqtPa6p6UEugkGnQxE PKLqMdgIzgRgSFTw7nq2ZWZK69WwqaQwGsVQurmw6nf4GUp4altx8B5l9+DqbS+r2H EaCUFEhOK2ZJQzJrYabSC6A/91hwYjecCICymVzHmEUorSIg/4FEPya5kDGkUOmkYU f6n4JYE/kPSieBhgGtEJ4QfOf5GNxGNuRYZ9L5vXQB4eyRye7NHuORhQ92R580Rjg/ GMgz95oc8FtemRFTHnnULETpM3/5RD48dpipYv7LxGT0og0ChnQnoPrGGUmInGUEuO CAQf50nK/u1r5qdhWZCrul6fROUWjTWihO1o5yTi+1YFgP+0wXoKHZ/jmdyPBIJy/V TNKHJiYJEe2P4t/hxtNouwvsO1blkMYsLV3OOSTBz/WfbTj+9jcoNzqK9Nx92L4vgs IZBwcZmvPfsuXNE/W/ytdj53qKMvbosDD4IAnU1bWXzEfj6b60LRf9TZ2PpwiNKmQA T2N/IvHI85drfp3NSUik/Jns= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 6858D20152; Wed, 28 Feb 2018 12:45:34 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519818338; bh=OuB38v8otyRQ6LhwYO4+bjTa9Se+1OGvYTrg0tln6CM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=LqllTgpGg3GpuWjwfVifCeCJAFcReWYhvLeR+HFDX6e5Lu3dNhMiNzp6tnaMfkdpQ EehQ54pkK1f9b7gm8/WC11UQxKI6NVHaDUk8WKK/Pkxe+4HUmPCWlpHwchgHQ9vzxC CMyYNVRHpfZhDoEH81OS0LmJUhmsr1lZuE76KuEib9lsiExC5765pQ0jsuVnsLp+Ls xUIg/nMR6zMfkujn8NSmVf4vgrw2fc+Us8Y/zOYIjgpvGC6iH5xi7V70H1LktJ68ys AJBhdu2+1S2Dh5rjae5SdKOVkHmJziNUZKlCjTmb9uXXeqMb1nDM3/3nsCPAK9JfCt Lw04oXqMEJjAmXJZS1njLpSUAfl5zOUq+pr8sEAKpainb2EzhTHMYcOH289oLTdywS XWnVRDCQpAxf/uszCwe67IILIeD+uLq2Zb1yOZKDiTZvxJHQqh6GsnkOITtO00kj4I Qd9QAUC8gNPhpB9i7MMRzuxS+eKz2Njgprx5mXbAALjfPT2ig97j+gc4ceHlRplUQE gF+lvT00P1FHMgO7Zg7yVqb4BDMFfqzLJ6zxcK3KHWreJCBGNr4rcyY7HQ+tS4ZGwm lQ1Xmtu4RjyquIq7pFNxpz3Mc9FgPtSiUJ6OE2BCl/AWsZiHmXYr3PZOWck8/DuDWC Hq4tbh1fNv8HjklbQVkOQm7M= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.1 Received: from rubens-MacBook-Air.local (engineering.quanza.net [91.208.87.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA; Wed, 28 Feb 2018 12:45:34 +0100 (CET) Subject: Re: Linux NFSv4 clients: bad sequence-id errors. To: Rick Macklem , "freebsd-fs@freebsd.org" Cc: "rmacklem@FreeBSD.org" References: From: Ruben Message-ID: <897d0abd-0770-a61c-5a1f-f267cd10e3d2@osfux.nl> Date: Wed, 28 Feb 2018 12:45:32 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 11:45:43 -0000 On 27/02/2018 23:54, Rick Macklem wrote: > Ruben wrote: >> I'm experiencing a strange issue on a machine providing a couple of >> nfsv4 exports. A Linux client that generates a lot of traffic to and > >from the nfs server sometimes starts throwing "bad sequence-id errors": >> Feb 27 10:39:42 localhost kernel: [12481477.608103] NFS: v4 server >> returned a bad sequence-id error on an unconfirmed sequence 80f7d0d0! > The handling of sequence-id in NFSv4.0 is complex and I won't even try > to guess why this is happening. > I am surprised that your Linux mounts are using NFSv4.0 and not NFSv4.1? > (Usually Linux uses the most recent version supported by the server.) > I mention this since "sessions" replaced the sequence-id stuff in NFSv4.1 > and, as such, shouldn't have such an issue. After some digging around I found out that the linux kernel on the client (raspbian running hexxeh firmware) was compiled with : CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set options regarding nfs v4 functionality. Thank you for pointing that out, Ill resolve that. > >> They typically occur after a couple of months of uptime on the nfsd >> machine. Every couple of seconds they are thrown by the client. The >> situation is "remedied" by restarting the nfsd on the server. Although >> functionality on the specific client does not appear to be affected >> (much?), its a bit disturbing. I've done some digging and found : > The fact that this is fixed by restarting the nfsd suggests a client side > problem. > Why? > Because restarting the nfsd does not reset any server state, so the sequence-id > situation would not be affected by doing this. (To get rid of server side state, > you must unload the nfsd.ko after killing off the nfsd daemon.) > > All restarting the nfsd daemon will do is force the client to establish a new > TCP connection. That is at a layer below the NFS state. Thank you for your elaboration! > >> https://lists.freebsd.org/pipermail/freebsd-fs/2015-July/021707.html >> >> and the patch attached by Rick ( nfsv41exch.patch : >> http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150729/586f776a/attachment.bin >> ) . >> >> Since the issue started manifesting itself I have restarted the nfs >> daemon (grabbed a pcap and the corresponding error lines mentioning the >> sequences prior to doing that in case anyone is interested). > If you email me the pcap as an attachment, I can take a look at it in wireshark. I've sent a download link to my troubleshooting efforts to you. Please do not look into it purely on my behalf (Im focussing on getting the client to actually run nfs v4.1 instead of v4.0)! > >> The nfs server runs FreeBSD 11.1 : > I'm being lazy and not looking, but I am almost sure a 2015 patch will be in 11.1 > and probably also in 10.2 and 11.0. >> I'm wondering: can the 2015 patch provided by Rick still be "safely" >> applied or has the nfs code changed too much since then? I've witnessed >> this issue a couple of times now and would very much like to test the >> patch provided. > As above, I'd be surprised if the patch isn't already in your 11.1 kernel, > but you can take a look. > If it isn't, let me know because that means it slipped through the cracks > and I need to get it committed, etc. I'm not at all versed in C but if I find anything ill get back to you. > rick Ruben From owner-freebsd-fs@freebsd.org Wed Feb 28 22:44: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 7CFB4F29E30 for ; Wed, 28 Feb 2018 22:44:38 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670069.outbound.protection.outlook.com [40.107.67.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A48C69FAB; Wed, 28 Feb 2018 22:44:37 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM (52.132.66.153) by YQBPR0101MB2180.CANPRD01.PROD.OUTLOOK.COM (52.132.72.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Wed, 28 Feb 2018 22:44:36 +0000 Received: from YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM ([fe80::3531:c817:d6f:9b93]) by YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM ([fe80::3531:c817:d6f:9b93%13]) with mapi id 15.20.0548.013; Wed, 28 Feb 2018 22:44:36 +0000 From: Rick Macklem To: Ruben , "freebsd-fs@freebsd.org" CC: "rmacklem@FreeBSD.org" Subject: Re: Linux NFSv4 clients: bad sequence-id errors. Thread-Topic: Linux NFSv4 clients: bad sequence-id errors. Thread-Index: AQHTsAK1+Ml+d7nQUEWuV8GTWVG+IqO42B0HgADbJACAALYMyQ== Date: Wed, 28 Feb 2018 22:44:36 +0000 Message-ID: References: , <897d0abd-0770-a61c-5a1f-f267cd10e3d2@osfux.nl> In-Reply-To: <897d0abd-0770-a61c-5a1f-f267cd10e3d2@osfux.nl> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YQBPR0101MB2180; 6:pGLpy1ed+9TpM4tVrXQNWcr/XGLN4UZrPPZvYHdfxFnfvkweFN3T1k1mGSbQgaQA7hMvQXrcbx4ngGgdC2NgJKgyQUjQ2p8Fv4MF9ZHbFYKJCs6xrxDBl4H0iOYN8a8P1ljdWrid+rS2yDNlNZT93+KqPCoCGZjBQaGPqCNoQxkgRdUjCwzjWc+5A0A/WdlsZf0oadInywOnaG0ykj1Xu2D00qMquGuE5tsN1A8OUbdon2STQpBz7YZNU2RbzdgN9lbz/fqafMTLgmfPcpSprr0CjZizL1myvqKPzc600U/raA+kSM6SMe6TAHgyYKwN1YS+evxPmfKxHxRvU3hbnIOLkFyj8qNkhWxa9LfDpQMcuLDNuzUibeQ/bJ6oNY9S; 5:9OFj8h3vlk/buqONn9N44k2M39YNwIkkZ3dhS9G+MbVDe1VleE5G85plIM+zBnP1XQ+oa97c/Gxy8NvLPlGsaWuO7zpBlSIzSto1ccm8EwsJm8HYmRIa5Fcy2+0Q9/SnrYJPr82yUGkJ/vEFCSq3cf5EoulgpAvTawVPXklaZ98=; 24:1NHRnTSJsrNcT/GlHsEcGje50DA7y4MizJQW3Raz5Je/xVOfP2uQ0Nl+IXbaqTYvwbrNOTkKC7GVk7ihPtcE3ieCNI3TilMp5FP6xYvPVJU=; 7:vf7H7KzuATNlhaLZ6tc5hWCwW7G6nzICyl0UKSC+FogHHKCXR4q1haC14WFLWxmPQlYFKarPf0gqK0ufbPXEcGvVuIAkMhF+bxPcMVa4l37mvO0TSuZeLtseKXlsnUZrGmoKRvq5yJTTMQtSluM7dOgrA+kE601qJjJTyhO3vquc0d8ap9XX7/3uTAvNsdTBbrLIdDPoVsKmLQQrod/NZcH46BnZmBMjkUql4cA9lyXE4V6XQvBlcn5CVjg80ZH2 x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 98a8f004-2a4c-4ca4-48d3-08d57efcd835 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989060)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:YQBPR0101MB2180; x-ms-traffictypediagnostic: YQBPR0101MB2180: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3231220)(944501220)(52105095)(3002001)(10201501046)(93006095)(93001095)(6041288)(20161123560045)(20161123564045)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:YQBPR0101MB2180; BCL:0; PCL:0; RULEID:; SRVR:YQBPR0101MB2180; x-forefront-prvs: 0597911EE1 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(366004)(346002)(396003)(39380400002)(189003)(199004)(5660300001)(14454004)(74482002)(68736007)(4326008)(345774005)(2950100002)(25786009)(81156014)(8676002)(5250100002)(3660700001)(105586002)(478600001)(2501003)(2900100001)(81166006)(110136005)(6246003)(786003)(316002)(76176011)(97736004)(99286004)(6436002)(305945005)(74316002)(55016002)(53936002)(1250700005)(3280700002)(9686003)(2906002)(7696005)(106356001)(102836004)(8936002)(186003)(229853002)(6506007)(86362001)(33656002)(26005)(59450400001); DIR:OUT; SFP:1101; SCL:1; SRVR:YQBPR0101MB2180; H:YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: S9s2Kro2y74pbb6KcH0rCRvxqSuJWMqhSd+W22BbxOe5606PmpQonFdvVGDMNt2V0SryXYp6Rt6afU9/FgTFOhNfHv6on2Xhg4jcztmJbHUZFqSpbeIJbLnCNl9DsTRxIw4XjFLBa2nrcngr0vl7qY0bKM+fYcMmiWlFb3WFdXQ= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 98a8f004-2a4c-4ca4-48d3-08d57efcd835 X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Feb 2018 22:44:36.6241 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YQBPR0101MB2180 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 22:44:38 -0000 Ruben wrote: [stuff snipped] >After some digging around I found out that the linux kernel on the >client (raspbian running hexxeh firmware) was compiled with : > >CONFIG_NFS_V4=3Dy ># CONFIG_NFS_V4_1 is not set > >options regarding nfs v4 functionality. > >Thank you for pointing that out, Ill resolve that. Hopefully, NFSv4.1 will work well for you. I am not, in general, a "newer version is better" guy, but NFSv4.1 fixed a lot of things poorly done in NFSv4.0 (and the minor version # change was more logistics than a reflection of how much changed). For example, the NFSv4.1 RFC (5661) is over 500pages long. (I still haven't read it all in enough detail that I am sure everything I've done is correct, but I think it's clo= se.;-) [more stuff snipped] >I've sent a download link to my troubleshooting efforts to you. Please >do not look into it purely on my behalf (Im focussing on getting the >client to actually run nfs v4.1 instead of v4.0)! Thanks. I'll take a look at it, although I'll admit I am more interested in problems w.r.t. NFSv4.1 at this point. (If you do run into issues with NFSv= 4.1, please post about them.) [more stuff snipped] rick From owner-freebsd-fs@freebsd.org Wed Feb 28 23:06:02 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 E5B88F2B5D8 for ; Wed, 28 Feb 2018 23:06:01 +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 817DF6AC9F for ; Wed, 28 Feb 2018 23:06:01 +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 99BD72274A for ; Wed, 28 Feb 2018 23:06:00 +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 w1SN60iE004897 for ; Wed, 28 Feb 2018 23:06:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1SN60Fm004896 for freebsd-fs@FreeBSD.org; Wed, 28 Feb 2018 23:06:00 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: freebsd-fs@FreeBSD.org Subject: [Bug 226096] [zfs] zpool add attach internal error: out of memory, pool with many vdevs, since r324255 Date: Wed, 28 Feb 2018 23:05:59 +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.1-STABLE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nikita@elyzion.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 23:06:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226096 Nikita Kozlov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nikita@elyzion.net --- Comment #3 from Nikita Kozlov --- I didn't had the time to propose upstream the patch from the review as aske= d by Allan, but yes it seems to be the same bug. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 1 08:08:59 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 2AE63F3BAF5 for ; Thu, 1 Mar 2018 08:08:59 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (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 B298874259 for ; Thu, 1 Mar 2018 08:08:58 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id E4AFC2014F; Thu, 1 Mar 2018 09:08:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519891730; bh=nStEpV/H67UwnwOlzkrNUvfVCT1I1j63pgfTB1uHfHI=; h=Subject:To:References:From:Date:In-Reply-To; b=Cok5HeGS+emieV+lSAHuxcYjpXpxhDiYlsKNPircYLHqSXKCw+0onfpO7qEoh+1LS YtS/XBXTsxNe42ZQ6/jItloeU3DM3UQauvOHuZISgWSEWs1dwMA+ivQ1Z0RXmHhOvU jhCOi2fQv/mI5B62Gj9SQ19tHhGyFVmx5QNJHW1PTkKKNOS274U6raUrjvmickcLiu y09DlNAwsXwsvlrUw5fCe6c4JF4swqUq5lMJAsPb/AKVZu74GhCABwb9W8ERsgGJL3 Hu9NSeyNt2TSade6HXmKU5wE64oFoV/yYsBsSAA0XyEp83qvec8JQd8QRgCZ2N2GFT aL9SxnbkpLnLNpHtLWax3Ygl8LTH/j6RRzd3T1iGaveD8V0aimFWNlimJK0fwTTKcF 89d3MFmKcx5RyjPVkkHENhXcQtzTkdHGvkPbn1+rKGsM0BlOM+Sq8PpLRGa3DNXQLL t4y7Ni0EprL4RkblowFTGCUO7BponXCCGUHIw2vXoltm4NUab7NGWTTleMy2Crj8Kg wwugDBvE+XICw9xEGMJvCH3DCnfnzrdRev+IJPqeEIL+nH4Cp8wixnIaMaU2sNyHLQ h4uVVK49rpGYBwNB9Cje6b2eCda/BYqIsnuMAJBzIGlpgtYfs0R7eV2oANXYlYlbaH dz3+cwQyOXyMmiz4dg3boPpY= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 8E2A820126; Thu, 1 Mar 2018 09:08:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519891724; bh=nStEpV/H67UwnwOlzkrNUvfVCT1I1j63pgfTB1uHfHI=; h=Subject:To:References:From:Date:In-Reply-To; b=prX7CDyqE/3GWVxSTT3kQ+0w4mrL4qRMj4WBq/hupWjjPwnzlcn+jeOQG7gh13Mb+ VHbwlAl253Y+z/LmPVxkBt5mOjMtRQ/b1UAHtqpumG8FuKs3rJyfFRsbr8xgfIfuls pWaRmtejPeMAYkfYckHM6TlJLD5jxM7703unds3fAt5TM8/Ql/nUxq7hBkfRWc6b3s 6ERBLeo1PRoiR1nPfh1o7P1QjjlTw1pK4P3GFp25P9VnWgBZJ/PCDv/M7M0EFCVzQQ h3MB9zvls1EtVGM+CGmzo2pHl6FGbn+VD4yHVRA2QV3Rh/eEgRtK4RTZl+Y9XitAyq 0MbEyvpo0h4Ksb1aoDs+helLETZPbLLY4sGaiuHbvY5B4emF4Z0Jg65ko9EkNywcUW kVvVhREsKZeUdI5+f+wNa3YEAK5oo57WxYGoaarwHdwpyZ2zMJ8Kf6+LGSNSEJkQ4k mMMeKc2JgJ3gF3E9c4d9APrezJoUtBbIvTP6u1tYKaufLy4TplilK2gKzkpfH+GZL5 k7RtoX48zxgXDSYCedBLV/H4dZHb7UzcFEu1GGRyHJkOHI80oFfA/nOMVV1Cq7rzK9 DflvIBilwMKTHOQmb2b9NN3To8uwDZh9zvekZo/tqvFFb5Zep2jWyW4YNNiXYSyotW xYOXQRUOi2Lvafzt/xH33SsY= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.1 Received: from rubens-MacBook-Air.local (ip51ccb320.speed.planet.nl [81.204.179.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA; Thu, 1 Mar 2018 09:08:33 +0100 (CET) Subject: Re: Linux NFSv4 clients: bad sequence-id errors. To: Rick Macklem , "freebsd-fs@freebsd.org" References: <897d0abd-0770-a61c-5a1f-f267cd10e3d2@osfux.nl> From: Ruben Message-ID: Date: Thu, 1 Mar 2018 09:08:32 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 08:08:59 -0000 Hi Rick, On 28/02/2018 23:44, Rick Macklem wrote: [] > Hopefully, NFSv4.1 will work well for you. I am not, in general, a > "newer version is better" guy, but NFSv4.1 fixed a lot of things poorly > done in NFSv4.0 (and the minor version # change was more logistics > than a reflection of how much changed). For example, the NFSv4.1 > RFC (5661) is over 500pages long. (I still haven't read it all in enough > detail that I am sure everything I've done is correct, but I think it's close.;-) Just glancing over it was an epic undertaking.....    > Thanks. I'll take a look at it, although I'll admit I am more interested in > problems w.r.t. NFSv4.1 at this point. (If you do run into issues with NFSv4.1, > please post about them.) Will do! Regards, Ruben From owner-freebsd-fs@freebsd.org Thu Mar 1 10:35:49 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 D0892F34FDD for ; Thu, 1 Mar 2018 10:35:49 +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 6BDA47B091 for ; Thu, 1 Mar 2018 10:35:49 +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 918D683D for ; Thu, 1 Mar 2018 10:35:48 +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 w21AZmOT074345 for ; Thu, 1 Mar 2018 10:35:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w21AZmPB074344 for freebsd-fs@FreeBSD.org; Thu, 1 Mar 2018 10:35:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223803] zio_done() panic on system with cache devices Date: Thu, 01 Mar 2018 10:35:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 10:35:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803 --- Comment #11 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Thu Mar 1 10:35:05 UTC 2018 New revision: 330237 URL: https://svnweb.freebsd.org/changeset/base/330237 Log: MFC r329314: MFV r329313: 8857 zio_remove_child() panic due to already destroyed parent zio PR: 223803 Changes: _U stable/11/ stable/11/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h stable/11/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 1 10:58:11 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 A07E4F38544 for ; Thu, 1 Mar 2018 10:58:11 +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 343477C231 for ; Thu, 1 Mar 2018 10:58:11 +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 5277AAF6 for ; Thu, 1 Mar 2018 10:58:10 +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 w21AwALm024476 for ; Thu, 1 Mar 2018 10:58:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w21AwAYn024475 for freebsd-fs@FreeBSD.org; Thu, 1 Mar 2018 10:58:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223803] zio_done() panic on system with cache devices Date: Thu, 01 Mar 2018 10:58:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 10:58:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803 --- Comment #12 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Thu Mar 1 10:57:50 UTC 2018 New revision: 330238 URL: https://svnweb.freebsd.org/changeset/base/330238 Log: MFC r329314: MFV r329313: 8857 zio_remove_child() panic due to already destroyed parent zio PR: 223803 Changes: _U stable/10/ stable/10/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h stable/10/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 1 11:13:15 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 A7C11F3A39F for ; Thu, 1 Mar 2018 11:13:15 +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 456347CC8F for ; Thu, 1 Mar 2018 11:13:15 +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 90639DC1 for ; Thu, 1 Mar 2018 11:13:14 +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 w21BDEYg074870 for ; Thu, 1 Mar 2018 11:13:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w21BDEBe074869 for freebsd-fs@FreeBSD.org; Thu, 1 Mar 2018 11:13:14 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: freebsd-fs@FreeBSD.org Subject: [Bug 223803] zio_done() panic on system with cache devices Date: Thu, 01 Mar 2018 11:13:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 11:13:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Fri Mar 2 09:07:02 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 E7345F321F7 for ; Fri, 2 Mar 2018 09:07:01 +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 83A79763B5 for ; Fri, 2 Mar 2018 09:07:01 +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 BCEF114911 for ; Fri, 2 Mar 2018 09:07:00 +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 w22970RQ071438 for ; Fri, 2 Mar 2018 09:07:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w22970RQ071426 for freebsd-fs@FreeBSD.org; Fri, 2 Mar 2018 09:07:00 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: freebsd-fs@FreeBSD.org Subject: [Bug 226096] [zfs] zpool add attach internal error: out of memory, pool with many vdevs, since r324255 Date: Fri, 02 Mar 2018 09:07:00 +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.1-STABLE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 09:07:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226096 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asomers@FreeBSD.org Status|New |Open --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Mar 2 20:25:28 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 5C88AF431EC; Fri, 2 Mar 2018 20:25:28 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 ED76D76AEF; Fri, 2 Mar 2018 20:25:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6824520E0E; Fri, 2 Mar 2018 15:25:27 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 15:25:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=1jB6Lkrayd+wLt+f2qTnvlmStt7Ra9SwdlQKMp2/sS8=; b=qWizx1+B T3E0YrYaBoHrCTHdgIdDotRHDsSCd5cyaYqTAjJHPTw59zW3yRfs9gfoRpNYhG8q hkJJd4DMxpU8SI5iJvRWNLXQJjNXmr7n3uGUbGabcyT2s5N5ecZp3P1rVX1MwrUw o4pH+PLIfKE2sjL4ND3CB5feI5EKIwm0WgzPr1SAm1HCb4Qw/5JIe46jj122eFoW Y/jCoI8VqyfjMNQ/NYber8qe7DtInFLVFJe9RNGCNR0CL96dlPxFUF/jBUJYkeMi ZzLlA8vSaR5DK2bq14C6NRJyhkaJIxKEVGAU8WP4pWS3R/iMSdQesrEjpLBIMjYK pkbaTNa30Yel4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=1jB6Lkrayd+wLt+f2qTnvlmStt7Ra 9SwdlQKMp2/sS8=; b=UHOeCEfAy60fsw5eB38co+DdBl8dj/3CKtmbWfpJcMI+J 1xKS7HBa3snt/HG6b2yU5qzAeSkVoRjOscEpyh1UDAnI6MyJZ7LEefTBT0tA1rxR trD+vJ/WHIIvZUp4lJCyIyGxbII+nSBzmZ+Xhq6wf3Jy7XgYNtLoGej1b6CdjL3f YxzKFTBt/qxXXnVVgHi5C3mnZMupjvszn9n96EVtSpNzor/yfXVnim/lXkRltr38 0HzpzUG5aFM2sp8GzlvafCTpnU7jCcKCfLVKzuPEMgJ8r/ZGIkHt8rjBNGiKq00n kvzV9LUXPL4ZWPqWDnvpT6M5eY76a7XP3uy+2ZLZA== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id D01B27E570; Fri, 2 Mar 2018 15:25:26 -0500 (EST) To: freebsd-fs@freebsd.org Cc: FreeBSD Stable From: tech-lists Subject: zfs problems after rebuilding system Message-ID: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> Date: Fri, 2 Mar 2018 20:25:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 20:25:28 -0000 Hi, Importing two zpools after a hd crash, the first pool I imported auto-loads at boot. But the second one I'm always having to zfs mount (zpool name) then mount the zfs subdirs. The system was like this: ada0 (this had the OS on. It was replaced after it crashed. Not a member of any zpool, not zfs at all, no root-on-zfs). New freebsd-11-stable-snapshot was installed to this disk. ada1 \ ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. ada3 / zpool1 - this is striped, one 4TB disk, attached via usb3 zpool1/c - this is compressed with lz4 zpool1/important - this has copies=2 enabled I ran zpool import zpool0 and then zpool import zpool1 and both imported without error. However despite setting the mountpoint for zpool1 as /zpool1, on reboot I always have to: # zfs mount zpool1 or I won't see the drive in df -h or mount or zfs mount. But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on that, I can see zpool1/c and zpool1/important as dirs but not in zfs mount or (normal) mount, nor can I see the other dirs that are not vdevs. If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in zfs mount. Confusingly, I didn't need to and don't have to do any of that for zpool0. What am I doing wrong/what am I missing? Why is zpool0 automatically loading but zpool1 is not? Before ada0 (the failed disk) was replaced, both loaded on boot. thanks, -- J. From owner-freebsd-fs@freebsd.org Fri Mar 2 20:39:06 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 6CC13F44228; Fri, 2 Mar 2018 20:39:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 B7598773AA; Fri, 2 Mar 2018 20:39:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id y19so15112444lfd.4; Fri, 02 Mar 2018 12:39:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=VXraBL3RG+g5rY5mKLCpY6LxeNtQhcLfUXjwzoQHd/I=; b=Imr2uKR9J7GxVLolt0jE0Ce5igkO96ejDzaEBsabkwR+a2SVWn4c8mM0Ub+sqKa++C Sl+R/rhocYIzGvtbTkLodcuKpT7PvhK2priRuBv4U5aPK4QGDPWIpu3Cali5P+nRolu6 S4yfEt+d9H3l2XshqeVV01Jh7+H6eDJ5OnS30NAhcy3o0wGgjZ4nm7hNW82SOdkToWWO BrU7+NtxzU6DPTlFwzI6RLsEiZTnFrsD5C5qp1JCocRxAKU2j2NJSnCdgoGx0MtVzY55 N6xJYt7fKdepCKcjrzdLkwRyBIOlOjcZydMDciRfO8Q3ppW8a4DxhZTlEDsKhxxiQ1Qa wzCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=VXraBL3RG+g5rY5mKLCpY6LxeNtQhcLfUXjwzoQHd/I=; b=fm4U75sdWKQNZGi49O+yMwiMe5jkKv77euoNgnwLiGPik+ATBxu16StLibFKmj0p55 ive4RUChRoVZrZlmTw64XJcpdMkSzefGRr3NgG6YyBUZPhhT/Disz+plvvGcjKn0oKGu u3r3xi2egsdtHx3h4JhvR5eowGJQigjkOm7RtuDB0xz/KoK7IYzFNCWleQIh5akxbZDH l2Il9NtTfMBbj2/9IiOJsE/JZ9yi18LuHyrMasR3SMutcIA770F+iL4HQDXppN1cwSJK JORzF+MHTrQI/ly/ZRPZTzcacwJjxf5U8dRQCfE3ibglZ76ae5g5pL0D8lHT4H5TsI53 X2uA== X-Gm-Message-State: APf1xPBBsSCkQOxFdiQ3x6b8TIPnvQBtmSWpwFOwt974bqFJmcE/5kRy rNHSkhAvt+VFlIMZSsvQGXA7uflrqpsJ8RhzL/GP0w== X-Google-Smtp-Source: AG47ELtw9QOPvwd8kV8g10a485EVZ6TYKjkh4h3QwqhA6K+xaUhoy5uoCVoYUyO2fLXiVHparhtVbN/Vfm2CnVpdmvg= X-Received: by 10.46.9.150 with SMTP id 144mr4892119ljj.117.1520023144139; Fri, 02 Mar 2018 12:39:04 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.2.195 with HTTP; Fri, 2 Mar 2018 12:39:03 -0800 (PST) In-Reply-To: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> From: Alan Somers Date: Fri, 2 Mar 2018 13:39:03 -0700 X-Google-Sender-Auth: kmiTTnzIJQu-r9rK3S9IXOPoM5o Message-ID: Subject: Re: zfs problems after rebuilding system To: tech-lists Cc: freebsd-fs , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 20:39:06 -0000 On Fri, Mar 2, 2018 at 1:25 PM, tech-lists wrote: > Hi, > > Importing two zpools after a hd crash, the first pool I imported > auto-loads at boot. But the second one I'm always having to zfs mount > (zpool name) then mount the zfs subdirs. The system was like this: > > ada0 (this had the OS on. It was replaced after it crashed. Not a member > of any zpool, not zfs at all, no root-on-zfs). New > freebsd-11-stable-snapshot was installed to this disk. > > ada1 \ > ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. > ada3 / > > zpool1 - this is striped, one 4TB disk, attached via usb3 > > zpool1/c - this is compressed with lz4 > zpool1/important - this has copies=2 enabled > > I ran zpool import zpool0 and then zpool import zpool1 and both imported > without error. However despite setting the mountpoint for zpool1 as > /zpool1, on reboot I always have to: > > # zfs mount zpool1 > > or I won't see the drive in df -h or mount or zfs mount. > > But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on > that, I can see zpool1/c and zpool1/important as dirs but not in zfs > mount or (normal) mount, nor can I see the other dirs that are not vdevs. > > If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk > off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have > to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in > zfs mount. > This doesn't make sense. vdevs have nothing to do with mounting. You see your vdevs by doing "zpool status". What are you expecting to see that you don't? > > Confusingly, I didn't need to and don't have to do any of that for > zpool0. What am I doing wrong/what am I missing? Why is zpool0 > automatically loading but zpool1 is not? Before ada0 (the failed disk) > was replaced, both loaded on boot. > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" and also the contents of /etc/fstab. Also, have you set "zfs_enable=YES" in /etc/rc.conf? -Alan From owner-freebsd-fs@freebsd.org Fri Mar 2 21:17: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 BB94AF46910 for ; Fri, 2 Mar 2018 21:17:57 +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 5885F79018 for ; Fri, 2 Mar 2018 21:17:57 +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 A491D1AEEE for ; Fri, 2 Mar 2018 21:17:56 +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 w22LHupa039173 for ; Fri, 2 Mar 2018 21:17:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w22LHunZ039172 for freebsd-fs@FreeBSD.org; Fri, 2 Mar 2018 21:17:56 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: freebsd-fs@FreeBSD.org Subject: [Bug 226096] [zfs] zpool add attach internal error: out of memory, pool with many vdevs, since r324255 Date: Fri, 02 Mar 2018 21:17:56 +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.1-STABLE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: asomers@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:17:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226096 Alan Somers changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |asomers@FreeBSD.org Status|Open |In Progress --- Comment #4 from Alan Somers --- I can reproduce this by creating 75 64MB files, creating a vnode-backed md(= 4) device on each of them, creating a zpool made of striped 3-mirrors on the f= irst 72, then doing "sudo zpool add foo mirror md72 md73 md74" --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Mar 2 21:26: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 9A535F47049; Fri, 2 Mar 2018 21:26:17 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 40AF779517; Fri, 2 Mar 2018 21:26:17 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5719020DDF; Fri, 2 Mar 2018 16:26:16 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 16:26:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=AhbiV2Qf0gbf9C89mMs2jl2jdaNOp q757cPUpjywZLY=; b=P4Qi82ggQOCmnuEcEi5CJaCYa+s4IwWeJNFOKzhNyGMzi OiWJ80WxLvG8/FmgdncbU/Dy6XEXNDBAUAH6oO8TpcjxPCYDiqUPfQq7FxSzFPe1 lYvr+HfIp3iVKKLEa/mn5VSXnOo8HVZ4mWgs5SeGV/xYzUmorfSslDTVa/8FQCz7 Yy+7yOXMVZpJWd+o19D+VUpTXgtJ+A39G5ud1uzboVlnQjSDpJ/8/7IbARm2PgTG u3Dl74V6AGWIcX9fEspOfdDQfPMVIWpRx2U6HY5SdhyiUWQjxWNZhHyxLai4EkFH /UGEAOpeWCgqyvv7tz08tG2pKjF3EkhItzoC6CXHA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=AhbiV2 Qf0gbf9C89mMs2jl2jdaNOpq757cPUpjywZLY=; b=lANL1kHtFteeg3A7qfUVEx mlds0JnuB3g0jgaCQciiSLMX+pjYA1en1v/GLLjPWLUVkMp0GNcio2BXmxj2mbpl skmVCe01wb75MzUuff6SMcFY8uh/vxue4/CmOWmEXLnl1Bto4R5LSR9nBLEOnvbn Ui6Qf3w2yLsWosS1ARkIpbfghWRC468KMfwVhAxFRUP1Ms2hxJPYKs797PXGw758 NsEq2mB6+X6T/CKnUyqDI57zY4uS62X/oHFxr6tdX3XL+v/QgOMW0TrTwmMakv29 tstUAFb7JQJtD4FiatNXzlnTMEkHo7aEoI8cMTPq8vVqA4zuEKFsHVHBKuCeZdtw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A76BA7E6BC; Fri, 2 Mar 2018 16:26:15 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Alan Somers Cc: freebsd-fs , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> From: tech-lists Message-ID: <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> Date: Fri, 2 Mar 2018 21:26:14 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:26:17 -0000 Hi, thanks for looking at this, On 02/03/2018 20:39, Alan Somers wrote: > This doesn't make sense. vdevs have nothing to do with mounting. You see > your vdevs by doing "zpool status". What are you expecting to see that you > don't? sorry, I was confusing terms. I was expecting to see similar to output of zfs list from both zpools instead of just zpool0. (just rebooted the system.) OK here's zpool status: # zpool status pool: zpool1 state: ONLINE scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 config: NAME STATE READ WRITE CKSUM zpool1 ONLINE 0 0 0 diskid/DISK-NA7DKXXF ONLINE 0 0 0 errors: No known data errors pool: zpool0 state: ONLINE scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 config: NAME STATE READ WRITE CKSUM zpool0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 > >> Confusingly, I didn't need to and don't have to do any of that for >> zpool0. What am I doing wrong/what am I missing? Why is zpool0 >> automatically loading but zpool1 is not? Before ada0 (the failed disk) >> was replaced, both loaded on boot. >> > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" > and also the contents of /etc/fstab. # zfs list -r -o name,mountpoint,canmount,mounted NAME MOUNTPOINT CANMOUNT MOUNTED zpool1 /zpool1 on no zpool1/compressed /zpool1/compressed on no zpool1/important /zpool1/important on no zpool0 /zpool0 on yes zpool0/home /zpool0/home on yes zpool0/usr /zpool0/usr on yes zpool0/usr/local /zpool0/usr/local on yes zpool0/usr/oldsrc /usr/oldsrc on yes zpool0/usr/ports /usr/ports on yes zpool0/usr/src /usr/src on yes zpool0/vms /zpool0/vms on yes # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0s1a / ufs rw 1 1 /dev/ada0s1b none swap sw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs /compat/linux/dev/shm tmpfs rw,mode=1777 0 0 fdescfs /dev/fd fdescfs rw,late 0 0 > Also, have you set "zfs_enable=YES" in /etc/rc.conf? yes. If I run zfs mount -a, everything zfs is mounted as expected. I'm wondering if at bootup, when zfs mount is called (I suppose it must be called from somewhere), whether it needs to specify -a. I would not know the first place to look though. thanks, -- J. From owner-freebsd-fs@freebsd.org Fri Mar 2 21:36: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 A709BF47AA2 for ; Fri, 2 Mar 2018 21:36:09 +0000 (UTC) (envelope-from anti_spam256@yahoo.ca) Received: from sonic306-22.consmr.mail.ne1.yahoo.com (sonic306-22.consmr.mail.ne1.yahoo.com [66.163.189.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44D0D7A037 for ; Fri, 2 Mar 2018 21:36:08 +0000 (UTC) (envelope-from anti_spam256@yahoo.ca) X-YMail-OSG: 3JQ84v0VM1kGXWPC.4ukhx50TmHlJUYgTOiwB_ZusF0Ig0hophJUwbP4Ja3MfYD pEpJzkirxfhOFMrUiEYeICbS0feAmi5C_L5uQGWW6mEypyaRiBMrJ2Lj4gVGoGbau1xDlwFzFaC0 b.hYvryP9Z1Hs1Sl7LMwUHrzqzy4E624IqvRMqk2iL4rppLquS2e86RSoZzrZ1EMz6fR39PPEWdu X5QW5b8JqjK_quqW1Xjzv23kU4BGdB6JDFfKOa9mnh69EV_7LhYQ3Yz5YA4SWdJ2LQL38Dt7SYEo Yhz5Vkr7rfi8K.QhUz3UqDj72QjHB96PGfJzXWDOH4I5z0ewl0e6BTwUlSNHHmrce.YCKm7cQQSy ZHmh1OQMkIdDQx_T6cz143YWaVXaKVXFHgGVFa1yMiNw0xwL9G_Uwl1JO0FMFBAAhybPN3Lexm1i Ik3p5TkFr6P6uVgUN7ArPb9FPSRGYa2UzS9_0MwSIYPvBpjOpYXzS4ivbSw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ne1.yahoo.com with HTTP; Fri, 2 Mar 2018 21:36:02 +0000 Date: Fri, 2 Mar 2018 21:25:54 +0000 (UTC) From: James Phillips Reply-To: James Phillips To: Message-ID: <104055907.2968604.1520025954207@mail.yahoo.com> Subject: Re: ZFS trashed by bad import [Update] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit References: <104055907.2968604.1520025954207.ref@mail.yahoo.com> X-Mailer: WebService/1.1.11480 YahooMailBasic Mozilla/5.0 (X11; Linux i686 (x86_64)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:36:09 -0000 As Andry Gapon suggested (in an apparently private mail), the problem was mostly user error. The import did indeed overwrite the root directory structure. While I am aware that the zpool(8) man page is already on the long side: I would suggest a more explicit hint in the import section that you may need to specify an alternate root, I had expected the command: # zpool import -f 8255478166520290766 granny to mount my foreign filesystem under /granny instead of /zroot. It did not occur to me that files would mount above the mount point in the directory hierarchy. The man page *does* talk briefly about when you would want to use an "altroot" in the "Properties" section: altroot Alternate root directory. If set, this directory is prepended to any mount points within the pool. This can be used when examining an unknown pool where the mount points cannot be trusted, or in an alternate boot environment, where the typical paths are not valid. ... I mostly trust my own filesystem that was merely degraded. I was not in an alternate boot environment (like a live DVD); I was merely trying to import my files into a new FreeBSD installation. I guess the typical work-flow for a failed disk is simply to attach a new disk in place of the old one (and wait for re-silvering). Since my disk array was was about 5GB too small to ingest all the data I wanted: I wanted to upgrade anyway. While running ddrescue proved to be unnecessary, it was able to recover about 99.9% of the data from the failed disk. A second invocation was able to recover a further 5kB (mostly a waste of time). Not sure if it was FS related, but I have absolutely been unable to boot the machine with both pools in place. The new installation (GELI) reports: "failed to read pad2 area of primary vdev" (with granny removed -- successful boot). Granny would not even run the first stage loader. What I ended up doing is the following: 1. Load up live DVD (with degraded granny + an "archive" disk) 2. # zpool import -f -R /tmp granny 3. # zpool export granny Later: 1. Same live DVD setup # ls /dev -> ada2p1 looks like my "archive" disk 1a. # mount -t extfs /dev/ada2p1 /mnt 2. # zpool import -R /rescue granny 3. # zfs snapshot -r granny@2018-02-26 3b. forgot the -r the first time. To recover (scary command): # zfs destroy granny@2018-02-26 4a: Learned that sending a zfs to itself is a valid operation (yay snapshots!) cryptic error message (out of disk space): warning cannot send '...' : signal received 4b. # zfs send -R -D -v granny@2018-02-26 > /mnt/granny.2018-02-26.zfs 5. clean up # unmount /mnt # zpool export granny Incidentally, granny was able to boot after all that, so I am reasonably sure I have all my data back. Have not tried importing it into my new installation yet. The new machine took me 2 weeks to set up, not 1, but that is off-topic here. Regards, James Phillips From owner-freebsd-fs@freebsd.org Fri Mar 2 21:38:43 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 1EC07F47CF1; Fri, 2 Mar 2018 21:38:43 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 92E997A170; Fri, 2 Mar 2018 21:38:42 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id 70so15294660lfw.2; Fri, 02 Mar 2018 13:38:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LM+ScmQrm9TjddlNzwQuussyt7YnNQZ7ayRh7ieiNAo=; b=Lq4fLwpzSoUe3GxH4s17Ny6f2GgEat92dOuZdJz4NkcNF3/uI+GbL7TnuOGgj+ba16 lIqnjJ7Md4VcqgSYXQRBDjylzogHHL7n1rP+JnvF2Th/En5TDkdsFQUTYGdOH6BbfEa3 jqVgU8D+ESEowyvPTUpyyfMb993NiDDF7HZgDPnmcl3WfCbPBS1JkDk5pfQytP1AJ6Qx ZRouwsH7Mx4N4ASWPzl2+TfAYND+G/Osy7AcUA30H3AZXRtiqiONKrNpwUNb3VaAIvRT BlaISg7UsvktdunMQIXx358jt6KzPJWT4GkRnneMN8SGdkZ8aBxgom1xY1SCg3MD8+hj /8Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LM+ScmQrm9TjddlNzwQuussyt7YnNQZ7ayRh7ieiNAo=; b=WSw7lE5XEv+OX+XS2epFXDUCdhKv5WB2agBVIW3dGzymDA8euLWB6E1n1GTF3FeIuK E3ZlR5+pEKdJiDng069RuAGaG9664mplEQ85rlMdmAUN9gafqBRhqZMMMdDiTJUnwwmw 5ezNuX6pysOfVaybdswa9qbPXq96NAit53u34kM60qtIXYACsGJ00krm3WSazvjYM9Qj v9Wgf+rxzbNEFRY8JWYTD6RcR8XxIv62gLXv3z88Glml9hB3N4Vmpr1Gdf1A6NEvJ9Kc AZHGu8Hg9y6NvZkFx/fzUAWgRqGbZkNEI0RDVYP8kIH5cHFWasxGIXAfnSG0I49TjCJ2 VKKw== X-Gm-Message-State: AElRT7GGbLaWuVyUtTFV9rB3hBJDRbWhjACiFcOSAjEuGxNDxlaFQPsg 7LIe68khc0FfWao/+RGrs930lnJJGT8Gs5gyhME= X-Google-Smtp-Source: AG47ELsLEVGJJePQN4loGs+2biVjsFUniKcZQ5IrBDybjdZxfotItgPAXsCEG6OZwviYGoBdKA02hBu6SlTTJVzkRuA= X-Received: by 10.25.157.80 with SMTP id g77mr4712467lfe.142.1520026720710; Fri, 02 Mar 2018 13:38:40 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.2.195 with HTTP; Fri, 2 Mar 2018 13:38:40 -0800 (PST) In-Reply-To: <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> From: Alan Somers Date: Fri, 2 Mar 2018 14:38:40 -0700 X-Google-Sender-Auth: bwbAbXGWsbOn5iwXj5HwjfWRpTw Message-ID: Subject: Re: zfs problems after rebuilding system To: tech-lists Cc: freebsd-fs , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:38:43 -0000 On Fri, Mar 2, 2018 at 2:26 PM, tech-lists wrote: > Hi, thanks for looking at this, > > On 02/03/2018 20:39, Alan Somers wrote: > > This doesn't make sense. vdevs have nothing to do with mounting. You > see > > your vdevs by doing "zpool status". What are you expecting to see that > you > > don't? > > sorry, I was confusing terms. I was expecting to see similar to output > of zfs list from both zpools instead of just zpool0. > > (just rebooted the system.) > > OK here's zpool status: > > # zpool status > pool: zpool1 > state: ONLINE > scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 > config: > > NAME STATE READ WRITE CKSUM > zpool1 ONLINE 0 0 0 > diskid/DISK-NA7DKXXF ONLINE 0 0 0 > > errors: No known data errors > > pool: zpool0 > state: ONLINE > scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 > config: > > NAME STATE READ WRITE CKSUM > zpool0 ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > > > >> Confusingly, I didn't need to and don't have to do any of that for > >> zpool0. What am I doing wrong/what am I missing? Why is zpool0 > >> automatically loading but zpool1 is not? Before ada0 (the failed disk) > >> was replaced, both loaded on boot. > >> > > Please post the output of "zfs list -r -o name,mountpoint,canmount, > mounted" > > and also the contents of /etc/fstab. > > # zfs list -r -o name,mountpoint,canmount,mounted > NAME MOUNTPOINT CANMOUNT MOUNTED > zpool1 /zpool1 on no > zpool1/compressed /zpool1/compressed on no > zpool1/important /zpool1/important on no > zpool0 /zpool0 on yes > zpool0/home /zpool0/home on yes > zpool0/usr /zpool0/usr on yes > zpool0/usr/local /zpool0/usr/local on yes > zpool0/usr/oldsrc /usr/oldsrc on yes > zpool0/usr/ports /usr/ports on yes > zpool0/usr/src /usr/src on yes > zpool0/vms /zpool0/vms on yes > > # cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > /dev/ada0s1a / ufs rw 1 1 > /dev/ada0s1b none swap sw 0 0 > linprocfs /compat/linux/proc linprocfs rw 0 0 > tmpfs /compat/linux/dev/shm tmpfs rw,mode=1777 0 0 > fdescfs /dev/fd fdescfs rw,late 0 0 > > > Also, have you set "zfs_enable=YES" in /etc/rc.conf? > > yes. > > If I run zfs mount -a, everything zfs is mounted as expected. I'm > wondering if at bootup, when zfs mount is called (I suppose it must be > called from somewhere), whether it needs to specify -a. I would not know > the first place to look though. > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have you checked if /etc/rc.d/zfs is printing any errors to the console during boot? -Alan From owner-freebsd-fs@freebsd.org Fri Mar 2 21:53:25 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 9E157F25444; Fri, 2 Mar 2018 21:53:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 4A13F7B140; Fri, 2 Mar 2018 21:53:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9540B20964; Fri, 2 Mar 2018 16:53:18 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 16:53:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=QkwGDfUIKnx5/PtGDH0oBp61gw/o9 SFHtL1JWFB5tlY=; b=GEVj15NUhMaODU1/QW3dwTLjVctSqaN05o0GMNadR6DCb Nd2txogDQsqQZzU/T+yZcIov6clODRixaBYY+Kv/4WjsnBPujA9ZoDVurfopqOIH gIxFn1qejB1NsxGAOPuQ8IdLGuDchL9N7C1HzyvbfXRPeDWQShxH9ffwLvz34XHv tvLKWlkOOkzeILtrskU4V0vGlUqo4AH4Oo2G0io2t3GVjnEz4nWUerQMi6cfyyp1 FcRJe/xfa/H72SQxtqjyBAU4E8YtVSHP1hyeqXIUMJB2Qk7I8e+8HJGipAY1O5H1 yHbIlYY9pmZ9VWamRvDut20mZPH1Hnel1ID8R/c1Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QkwGDf UIKnx5/PtGDH0oBp61gw/o9SFHtL1JWFB5tlY=; b=llv6/MTFk5M7R2l7HNjxvW z8Ogn/hk1t4p1Cx7ZxxnEtM52A8M38ELT6XBb/BJ+mBmpjulURMOLV3dp8vbJTUp 6qVsXd3MbRkCOD14yVwuPAyRcjAUQpohEMDzfMwF9OGt1hmDNbBnhZ8fJ4gQbgDq Zokdi9P9vkWBsI9XBUmqIB0GPllk52kpnUBUwE9p4VF3ZjG0ORSFFZgYIMPEvC06 +W4CVR7N5ZMlJeS06q7HvcoeF/JlEbq5nau1zw7YNH3RK8IlCJh2P8tf427ndo7g mR4lks4FiBkO6K1HmqZdtlKZt3ZkODzbuLougO7RAUYy4j7ySfa7bEzb8e+Lg5Yg == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 02C427E68B; Fri, 2 Mar 2018 16:53:17 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Alan Somers Cc: freebsd-fs , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> From: tech-lists Message-ID: <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> Date: Fri, 2 Mar 2018 21:53:17 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:53:25 -0000 On 02/03/2018 21:38, Alan Somers wrote: > The relevant code is in /etc/rc.d/zfs, and it already uses "-a".  Have > you checked if /etc/rc.d/zfs is printing any errors to the console > during boot? Nothing much in dmesg -a # dmesg -a | egrep -i zfs ZFS filesystem version: 5 ZFS storage pool version: features support (5000) # cat /etc/rc.conf | egrep -i zfs zfs_enable="YES" very puzzling -- J. From owner-freebsd-fs@freebsd.org Fri Mar 2 21:56:16 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 7A9C9F257E6; Fri, 2 Mar 2018 21:56:16 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 DF4DC7B313; Fri, 2 Mar 2018 21:56:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id f75so15352452lfg.6; Fri, 02 Mar 2018 13:56:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KbEX7zdEd1Gvifsj2WzUYN4Sr5yL/RwS2J2httUzZYA=; b=U7m9DtuXeHLjLMmIiF1pD7J3ka6oF7d8SWy3jhbsLoXwHDESVYjiJxJrAfx/plBe6c 8+ecAB6xr0cyRc3ggy6RcfsiefII0GKZev/XRbcvvw8mfRYFMxd1oAX3RHlo7/YhdIdK lN0Z9zOGdGLT0MbHV0dIMCsJIkHKlR6EkNgzu/kh1UU4nUoSodwmoXZGZRZGFc6fKhK/ +ypXCcfuMvKhBYUF2wFnLNQmipU/L10BIliisSa/4FGOCiTTrZe5j0QCbKF1vEigtgUo GpIX+yyBTVzuvZngutZOp0U8XlGLJo7CWSdo6ATkGQS66TA715S2lhZE/5Oh3qeqJxlX NlNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KbEX7zdEd1Gvifsj2WzUYN4Sr5yL/RwS2J2httUzZYA=; b=JLXxaCdR8mxK1ICc64hWvBNIwub3kKoNYwzREArwePPAEOS5wfVY5OOoUvqI2P8cFO ukanCEvG7cozpXtKmPSiEwllFnI0AGRSweX1azGpY1RO4UuTwMqqri2IKaoizNuLXpku oBNtDddIZ516Xr4SrcLq4DXT7npgGeLSSvbuDHKZOHjLgJxCxT7p6CgSYqQNPcNYY7eS l3x/6zbErOHlD1qKN/6ur0L9AAwywnriNpKtkWsRhfL3VULUE1AuOZa8Au0S58yNOGB5 AbDKLeSsnM0dpxlLTkKads790DMmgiXqKQJjc4wBX75Ad3BxEVPyw+rYX3EQLffEz9AJ Mb4Q== X-Gm-Message-State: AElRT7Hd1DfD2j1PuCsFUoGrFTFa1eWQz+R4AwAC383dujZaQRSmGmyq FC73LbsBMof2vWxlCY67slMnuxfvLIrGy53iXFo= X-Google-Smtp-Source: AG47ELvGVyWDzXs6D7vrs+wSQT4W9cecV26yA/rMI5u5Vdj2vIJeE68inaVaP5JLaL4Gr8NRXZa8wNaEzkl7o6rI2uw= X-Received: by 10.46.91.206 with SMTP id m75mr4765434lje.59.1520027774468; Fri, 02 Mar 2018 13:56:14 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.2.195 with HTTP; Fri, 2 Mar 2018 13:56:13 -0800 (PST) In-Reply-To: <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> From: Alan Somers Date: Fri, 2 Mar 2018 14:56:13 -0700 X-Google-Sender-Auth: FYTnb0EJVTN3ElVe07Ig3fmiEz4 Message-ID: Subject: Re: zfs problems after rebuilding system To: tech-lists Cc: freebsd-fs , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:56:16 -0000 On Fri, Mar 2, 2018 at 2:53 PM, tech-lists wrote: > On 02/03/2018 21:38, Alan Somers wrote: > > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have > > you checked if /etc/rc.d/zfs is printing any errors to the console > > during boot? > > Nothing much in dmesg -a > > # dmesg -a | egrep -i zfs > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > > # cat /etc/rc.conf | egrep -i zfs > zfs_enable="YES" > > very puzzling > -- > J. > dmesg only shows stuff that comes from the kernel, not the console. To see what's printed to the console, you'll actually have to watch it. Or enable /var/log/console.log by uncommenting the appropriate line in /etc/syslog.conf. -Alan From owner-freebsd-fs@freebsd.org Fri Mar 2 21:59:10 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 F07F0F25CC3; Fri, 2 Mar 2018 21:59:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 9AD7F7B5B2; Fri, 2 Mar 2018 21:59:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7BA2320CB0; Fri, 2 Mar 2018 16:59:08 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 16:59:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=NlV/+eBPey0+Sq3C1e+MKeJQ6wvvr V2D2fAmVo880m8=; b=i2iuR98JspWHOTdWCtjqRUaVPoWVjW8If9ZyListz1gVh kSncVkO/4X/b1VsinKAE4aLf0YuP2pbElvuYw8TjRZ6f3j2ImMjNNqNKiz8v14ov 3bkoIyhQuJTEcq+1EEvCGSxerAujC0igOmDVeUS5tW0kD04p9bvNBunwnKdUfYxR 0qBfVcJUmByLoEmMOtWXGykrouDb3LTDCA7CVBoFXEBIh4stwwHC0ZQz5u4LbZem sCphJEIoJ5jk8H9XHji6jo04aQB8Dd5YAb7Mlvb+mM8Sfa9kQlhFW3QDcVmbDGcJ 3yuxzDvCxCmWlFTvx+Fj90PW/l4kY0e517c/dzTRg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=NlV/+e BPey0+Sq3C1e+MKeJQ6wvvrV2D2fAmVo880m8=; b=VT8aAjPPEDhbzYgQ4Xu9wW DB8r0YG/VowCSGzZXL7YtShJygWPxI5hk5oMSI5+B6pQclemYbpasV0T4fanYPiN ReiBrx9Ujz6/tc4RxBFVVGgJ/tWeFYX4llGy1+x2RhZ4E+Du3bscxfXFTn1Vct/B eezT1WvS6lxHSO6fXaWVGBeeWSXfFXOGqXlcZdYACCb22eGZts4arXVfx0csdEkW 50GP26DdsK09/bJ6S8VTep514lMdj9sp2vnlIMM3Skf6rPu7NFfiCnJhuTApwNqO bAM5pelyveVDMubkM/b3W6Qmz5KGaMifNTvyU/1P8dwq+mHmelpOILsauCDiUFjw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id DC1077E745; Fri, 2 Mar 2018 16:59:07 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Alan Somers Cc: freebsd-fs , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> From: tech-lists Message-ID: Date: Fri, 2 Mar 2018 21:59:07 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 21:59:10 -0000 On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console. To see > what's printed to the console, you'll actually have to watch it. Or enable > /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok will do this asap, thanks -- J. From owner-freebsd-fs@freebsd.org Fri Mar 2 23:59:28 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 F04ADF2E517; Fri, 2 Mar 2018 23:59:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 94ADA80653; Fri, 2 Mar 2018 23:59:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E7B7820D4A; Fri, 2 Mar 2018 18:59:26 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 18:59:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=8h9Ll08UUlFhe1N9pZ1pRUX757P1p GKPyGULcsSNmJ0=; b=fZ34NpKn33bypC+xMbTf2pJ8Tydu7qnUm6tvsgKeHEL2U CtvjvmztZ0gDoDFW27sH614rwh0C3e9fzr+YPOR8kSodRX7Nesmryv/cv5N9Q3gk 2s/wPlzQ+62GiwSnb2O58T1iHP9fPls8VrZRpqLE4eHPfibpzth/UsTfCKgxDyGI 022HzZGK8iifKj6jHKQhPhtB92HMdypUNihwtbCyNyy/4SWma9uLA/WYnkWpam9B A/XKUC3843928guVRxyPeNn2t+nL1Bq0LeTrQLIV4TbVrGyXUZckcut9YghPqPjG IP4O0laryc/GjC+DIu/KdnNd2MoYmizQHPb6ZvONw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=8h9Ll0 8UUlFhe1N9pZ1pRUX757P1pGKPyGULcsSNmJ0=; b=EszWnqEYkrQ6qeF1/8vy8p 70gHbHBPVhzAq6jw6idFAQjFb7Z3WFWLp01yspZUTq2XDvw1+8mK2KXZg4JrECAf Wjbm5ZYB8xnr6NDqjo7S27gjiiEUluKZmOaqwb9DtnmD6xEaEyKWG3r3QMyvZYtp Jt8UMRL91+DcfuABcMkXX1g2MRtWSZKr8x/UH+DkZKN9q8LkSiVKplTQTBcxByji xq8eq2zun0N4xWsW+9xHPe11d6C4BJ2ptq1LQge3ADbMMpOvKwyRt9GIFw6SIFPZ phSHcMH8ByXrHQmJk9ZDBau2WkoidXN6kSmmM9oOFB4fSYRch/UbaKtTGLkUJ7MQ == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 5A57F24733; Fri, 2 Mar 2018 18:59:26 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Alan Somers Cc: freebsd-fs , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> From: tech-lists Message-ID: Date: Fri, 2 Mar 2018 23:59:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 23:59:28 -0000 On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console.  To > see what's printed to the console, you'll actually have to watch it.  Or > enable /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok did that, chmodded it to 600 then gave a kill -1 to its process id, then rebooted. # cat /var/log/console.log | grep -i zfs # lots of info if I less the file, but nothing about zfs here's output of mount: # mount /dev/ada0s1a on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) tmpfs on /compat/linux/dev/shm (tmpfs, local) zpool0 on /zpool0 (zfs, local, nfsv4acls) zpool0/home on /zpool0/home (zfs, local, nfsv4acls) zpool0/usr on /zpool0/usr (zfs, local, nfsv4acls) zpool0/usr/local on /zpool0/usr/local (zfs, local, nfsv4acls) zpool0/vms on /zpool0/vms (zfs, local, nfsv4acls) zpool0/usr/oldsrc on /usr/oldsrc (zfs, local, nfsv4acls) zpool0/usr/ports on /usr/ports (zfs, local, nfsv4acls) zpool0/usr/src on /usr/src (zfs, local, nfsv4acls) # output of zfs mount # zfs mount zpool0 /zpool0 zpool0/home /zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src now I'll do zfs mount -a and then zfs mount # zfs mount -a # zfs mount zpool0 /zpool0 zpool0/home /zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src zpool1 /zpool1 zpool1/compressed /zpool1/compressed zpool1/important /zpool1/important and everything is there as it should be, after zfs mount -a. it's as if the /etc/rc.d/zfs either isn't running or I don't know, failing to run the main section, where it uses -av rather than just -a. Is this file the only one that's called to load zfs? I mean, in that file, zfs mount is never called without a parameter. To me, it doesn't look like the file is being run at all. thanks, -- J. From owner-freebsd-fs@freebsd.org Sat Mar 3 00:09: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 C1403F2F6C9; Sat, 3 Mar 2018 00:09:37 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 39DB380F59; Sat, 3 Mar 2018 00:09:37 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id m69so15652946lfe.8; Fri, 02 Mar 2018 16:09:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wHFyJg7j71/4AfI63QITgAlgNFZQqHJ5I1dxoLUWZHU=; b=U73f1X2wWoieKbFQ/l4Nw4Vuw6XbKJnEqqvNfY9H2To8pyA5nrughOkj/6U2v+4HTF kgx7xdL4tmywsHZ/fYAE4GrE4DEbBkA3dQLEqKThIgGVjfVBJ5VaHb1A7T8XipQ/tqKN X9KceAKvmUZCVwzASfOGNGe0c8kJ2+vMVf7UOQ5KqIdjUfwXTzJJ8gr82M3ewjs2Sjy7 +0XkM2RaVDRBNt1slp2dMduyt6UQP1V2b8+4XnV4aEAKnLeosoOT5XIoiuNzcEgqrMmD Gf90PeG+ABdC2e8H/3MVw6/w/5EEs/yTtGkDsfXmZlRpBzarL0ipWVoj2VHeqNCytG6l qqmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wHFyJg7j71/4AfI63QITgAlgNFZQqHJ5I1dxoLUWZHU=; b=VIjhg4EazVFdk2N3zxJZCr/Fg9FdmSjhB57xfMw8NjYAvNdlq+MeyZpuSb31UfHdN5 Zoa7kfJ56Jm7qFut6jlF3ioMiFOeFCUTPnajy78beRLjNMcokJoyDyXw8jO1+/e9MPE7 7SwcCZfHYx5Qmi3n2OmCz9pTcylgwoyjovSHXWF3r1nyFDBLIlMAr3ahftXvfVYoqsBB TZ1F6fvGGJIYuN9y25dEP1Tio+6uDM16bKMUqweQrq26or7SHFbg/JGwfVBNnQ5W3d0J KyGv4c3QzUQwit5fsXaF3y0bpAic5HfR9WnRYo6sqeB7yBPLOyrl1xKo7OGw14NHuCoz ixrw== X-Gm-Message-State: AElRT7Em9ATOPorvFA2WsJn2Qs1E5eeFetd3bLT7Bn+h8a9gm7giYs3c ViU0KsrwAK/icQ9Xp6e3RwQ3vLvHTMPpIfdNSVOeIw== X-Google-Smtp-Source: AG47ELtbJD1taN5KQoL+A7PprQZvnV79/6wxzPxZ+Xv5jRNyIBU7y0mFt+GoEPVm4+aEv7kvsnhghwldF6hrsvdWUVE= X-Received: by 10.25.143.209 with SMTP id s78mr5306200lfk.56.1520035775738; Fri, 02 Mar 2018 16:09:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.64.216 with HTTP; Fri, 2 Mar 2018 16:09:34 -0800 (PST) Received: by 10.46.64.216 with HTTP; Fri, 2 Mar 2018 16:09:34 -0800 (PST) In-Reply-To: References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> From: Freddie Cash Date: Fri, 2 Mar 2018 16:09:34 -0800 Message-ID: Subject: Re: zfs problems after rebuilding system To: tech-lists Cc: FreeBSD Filesystems , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 00:09:38 -0000 You said it's an external USB drive, correct? Could it be a race condition during the boot process where the USB mass storage driver hasn't detected the drive yet when /etc/rc.d/zfs is run? As a test, add a "sleep 30" in that script before the "zfs mount -a" call and reboot. Cheers, Freddie Typos courtesy of my phone. From owner-freebsd-fs@freebsd.org Sat Mar 3 00:23:21 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 86D57F30B58; Sat, 3 Mar 2018 00:23:21 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20DD281E18; Sat, 3 Mar 2018 00:23:20 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 2607F1610E; Sat, 3 Mar 2018 01:23:13 +0100 (CET) From: Dimitry Andric Message-Id: <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_41898BBB-F224-4F3D-81EA-7822D32F4A99"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: zfs problems after rebuilding system Date: Sat, 3 Mar 2018 01:23:12 +0100 In-Reply-To: Cc: tech-lists , FreeBSD Filesystems , FreeBSD Stable To: Freddie Cash References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 00:23:21 -0000 --Apple-Mail=_41898BBB-F224-4F3D-81EA-7822D32F4A99 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 3 Mar 2018, at 01:09, Freddie Cash wrote: > > You said it's an external USB drive, correct? Could it be a race condition > during the boot process where the USB mass storage driver hasn't detected > the drive yet when /etc/rc.d/zfs is run? > > As a test, add a "sleep 30" in that script before the "zfs mount -a" call > and reboot. Indeed. I have had the following for a few years now, due to USB drives with ZFS pools: --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 @@ -25,6 +25,8 @@ zfs_start_main() { + echo "Sleeping for 10 seconds to let USB devices settle..." + sleep 10 zfs mount -va zfs share -a if [ ! -r /etc/zfs/exports ]; then For some reason, USB3 (xhci) controllers can take a very, very long time to correctly attach mass storage devices: I usually see many timeouts before they finally get detected. After that, the devices always work just fine, though. Whether this is due to some sort of BIOS handover trouble, or due to cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate disks!), I have no idea. I attempted to debug it at some point, but a well-placed "sleep 10" was an acceptable workaround... :) -Dimitry --Apple-Mail=_41898BBB-F224-4F3D-81EA-7822D32F4A99 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWpnq8AAKCRCwXqMKLiCW ozfDAKCIzixRre/XkhsHgqalf0xmgsyqEwCg+zQprqqW9NH26RJTbf5Esgnt2s4= =TcLW -----END PGP SIGNATURE----- --Apple-Mail=_41898BBB-F224-4F3D-81EA-7822D32F4A99-- From owner-freebsd-fs@freebsd.org Sat Mar 3 00:41:29 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 BD1EBF31C73; Sat, 3 Mar 2018 00:41:28 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 64A4E8270B; Sat, 3 Mar 2018 00:41:28 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9578520ABC; Fri, 2 Mar 2018 19:41:27 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 19:41:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Vuq1OQMMLTNSc9PC7CaXX4v5ag6Jw 3vv2JMmkGfY23Q=; b=SmKM0m+evu1JTOJEo86Qe39N9rU+eYb09Y8ZDsJpF9YR2 2G/jmX1LvWTiwXWpg1wclB3Gcdza9hK/FgSC1Vl6MECwsloLpank7K/cSavcrLJt p6ooMV93nRnMypedymH5VWdbAYyMZRSbeozb9fNKPb3bRYqMXMKVnBGChlxe/cw5 YnOVa4xI4pUwYLpgmf13Ui+avV2TUcjH6/h3wcMDFhdMCQ8OcKtrhrYgnirw0Aso ByB+B/px8Mjp78l1E83N+tvvxjdKbBmFqV1LIYO5FkfiHzxpMHR09UzM6ljP9Ejb JC+Zd3QCVMXnjek89/oC0cyNLmmj+Z64lFf0IwbaQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Vuq1OQ MMLTNSc9PC7CaXX4v5ag6Jw3vv2JMmkGfY23Q=; b=aovEVcdDlHf8MxMjtLWhyL OO0bHr3kHUf7o2YdPedA80kn7Pbdhi7AqxHMMp7t4zdt3isJ8zBGCHuiOKbU36IO bzXuZEOJsMTSVOUo6oYCPUReMZN1lFnvCDuWvSrhMBPUsmZ6p7/QsRb7BOOmSFMb Rnhk/ZO4+QmVPVhjzv9ePNoB28swxN50jH1R0bDbhDGhC8FzdSyYpL/bAFcN9qxt 5LkGlf5iMyBvnwnhPjcjowrbKIM9+1g3aXycf+z/DkLxBytx/ANCOFjbWEhm8Dpw 5t0fTonO/sejASnf2PK1s/xziJquZJ/G3VI0tIQXf1yt/fs/Hemqe03KQrz9jHTw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id F38D82482D; Fri, 2 Mar 2018 19:41:26 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Freddie Cash Cc: FreeBSD Filesystems , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> From: tech-lists Message-ID: <44037e05-f860-8a99-cbb7-abca6971b302@zyxst.net> Date: Sat, 3 Mar 2018 00:41:26 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 00:41:29 -0000 On 03/03/2018 00:09, Freddie Cash wrote: > You said it's an external USB drive, correct? Could it be a race condition > during the boot process where the USB mass storage driver hasn't detected > the drive yet when /etc/rc.d/zfs is run? > > As a test, add a "sleep 30" in that script before the "zfs mount -a" call > and reboot. Yes it's an external usb3 drive. That's interesting and I'll test that tomorrow. I recently commented out a GENERIC kernel the USB debug line because the console was filling up with usb attach messages on boot. They were appearing after the login prompt. I have a couple of usb3 hubs attached and the disk is attached through one such hub. (although it was done this way because sometimes it'd be seen as /dev/da0 and others as /dev/da4. And possibly linked to this, when it came up as /dev/da0 it was always with a usb2 speed rather than usb3). thanks everyone for your input. -- J. From owner-freebsd-fs@freebsd.org Sat Mar 3 07:13:36 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 C7F09F45E59 for ; Sat, 3 Mar 2018 07:13:36 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 6240072145 for ; Sat, 3 Mar 2018 07:13:36 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by mail-io0-x22f.google.com with SMTP id l12so12909975ioc.10 for ; Fri, 02 Mar 2018 23:13:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarchy-in-the-ph.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Zmhbj/B95oFwFdgvEn4jZD8VJxgBshR0rWNhHXux6mk=; b=dB1WD1/EdT9tI8fjU2yuWRJs31PG0AyUrFuIo1lAiBgNL30Y9FqBkv9LthvwVZl54q bcNaSyrl+VucjbL9BE+hDEce7xRtKx7TMOiFVNHg97a06RRlYxN8NwPNLgUPL5E73Qf4 ls/f83PfUjsH4YexsAB5yo5flZDA48bIeBsnLSY7dDZYKqEvjzHh+gEbIvpCJ0TZHo57 lWY6m95umfBFeEjhBtvFaIoeH6Pqt0qYg1ROgbiOJwA9Fnn9+BDzcVc69YSbnMtIdgn1 W+NykSJNCAW6ilypviQ6Xq5X4wE/p/3WH2P2t7dUXWnVf6trTjqn7k1Ru7hZCTeJSlLO Rylw== 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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Zmhbj/B95oFwFdgvEn4jZD8VJxgBshR0rWNhHXux6mk=; b=O51pnrU9u9rF3JnmwNWawShv+UVDc3lE9EHMaWCcDU/6P9dYK/XbZj/yPqUeJMXpIu q4x8IxN+zoPSXxQIy+WR1d06PfmcUGANs3LnNO88DlWI7pUx2B7rsgKvkZuEs0FAf9kf cgBqopDwHwCjZqlaHazQRwkivhlFM72aHTecA1dTCyiJh7B+8ZVVzsWh8kWVNxX5FN80 Zsza/quzOr1aVIjliuPZFEe1RA/X3EOLyxC1KVAEO099aLnE3UpsB4k5SQuVU07CwVuX ZAfozp6l9jYnZoDfaift4TPdtsKsfkgBDV73n7dx7udFL4+hJEmxOsaEXJtcQ3jL4ZUN X68Q== X-Gm-Message-State: APf1xPDBMwyWbb7n/BXrRwB8mnZhzGt3VdvC0dapSsKYoAqLrWLGSVT0 douJzpeoisXORFg89geMRheTy8f7 X-Google-Smtp-Source: AG47ELu7vbLW8RHGWNttyG/JjxiWkslL1mzVQGy89LeErAR1yVir5pWoLD6T6ZJc4dT3fuNzIMv8mw== X-Received: by 10.107.22.1 with SMTP id 1mr10040873iow.238.1520061215571; Fri, 02 Mar 2018 23:13:35 -0800 (PST) Received: from m1a1x0.krakensys.lokal ([118.200.253.91]) by smtp.googlemail.com with ESMTPSA id 80sm1732632itk.13.2018.03.02.23.13.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 23:13:35 -0800 (PST) Subject: Re: growfs only works on GPT partitioning schemes? To: Warner Losh , Martin Simmons References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> Cc: FreeBSD FS From: "Mars G. Miro" Message-ID: <5A9A4B1E.8070206@anarchy.in.the.ph> Date: Sat, 3 Mar 2018 15:13:34 +0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 07:13:37 -0000 On 02/26/18 22:30, Warner Losh wrote: > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons > wrote: > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > > > It seems that growfs only works on GPT partitioned schemes ? > > > > When I first installed my FreeBSD, I unfortunately chose BSD during the > > FS creation. Now that I ran out of space, I wanted to increase the > > filesystem size. Successfully did so in Virtualbox but after rebooting, the > > HD doesn't see the new allocated space. It has another virtual HD, one > > created with GPT and I was able to increase it via growfs. > > For the BSD scheme, I think you also have to resize the slice (i.e. > the MBR > entry) and then resize the BSD partition within the slice. > > > You do. The /etc/rc.d script that does resize on boot does that > automatically, but we have no other automation for the process. > > Warner You guys have any idea how to resize the slice ? I have 2 HDs, both have already been increased (in VirtualBox). The BSD partitioned scheme below doesn't see the newly allocated disk space, only the GPT one. camcontrol reprobe / gpart recover / etc doesn't do anything. mars@fbsd11vm1:~ % gpart show => 0 83886080 ada0 BSD (40G) 0 4194304 1 freebsd-ufs (2.0G) 4194304 16777216 2 freebsd-ufs (8.0G) 20971520 62914559 4 freebsd-ufs (30G) 83886079 1 - free - (512B) => 40 104857520 ada1 GPT (60G) [CORRUPT] 40 12582912 1 freebsd-swap (6.0G) 12582952 92274608 2 freebsd-ufs (44G) I think I might just have to dump/restore this to another GPT virtual HD then. Thanks. -- I sent a message to another time, But as the days unwind -- this I just can't believe, I sent a message to another plane, Maybe it's all a game -- but this I just can't conceive. ... I met someone who looks at lot like you, She does the things you do, but she is an IBM. She's only programmed to be very nice, But she's as cold as ice, whenever I get too near, She tells me that she likes me very much, But when I try to touch, she makes it all too clear. ... I realize that it must seem so strange, That time has rearranged, but time has the final word, She knows I think of you, she reads my mind, She tries to be unkind, she knows nothing of our world. -- ELO, "Yours Truly, 2095" From owner-freebsd-fs@freebsd.org Sat Mar 3 11:33:10 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 01BA3F3338F for ; Sat, 3 Mar 2018 11:33:10 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 6E9027CB58 for ; Sat, 3 Mar 2018 11:33:09 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id t74so7646811wme.3 for ; Sat, 03 Mar 2018 03:33:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6YLobks9zfWkmQXf8NJ3FA5Zgq9kV0xCTAzuR7aXu+o=; b=QP4GSDf1/NCIRa0AFg+io1nFvpejMJylIrdYUVIvlW7ep9OvvYy8V7LC9XL73qSTFl qLjyqAZw7reK/I/q2MiZuPttDWS2ayTWSL8GyMgYjZZ5aIoeGXW3mJbiQyx3sFTqSV98 mmF6sEWRvQBBIfjewO/ZXHsS/CgMP233DnxH7QpsFdHRZkj9/0oX4fOT0w8sq9u9F03a F2BRzuydrMHxZz4XC1naqvZKCs3nGG31op+S3aD0AOHPqKyBqRtmIv24U9ibswzo7xSI zSvT8CVRstW//7rDuJO6RUl8dqKEWy96bg7rul+YVRtpaiwP8bpHcbbE54QPAAmIbLf8 w2xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=6YLobks9zfWkmQXf8NJ3FA5Zgq9kV0xCTAzuR7aXu+o=; b=GzRiR0UUQTAObRyY1Oe2HbASlJ6xpOZwjhRjji3ptigtgKQjBN4tDizKCpog3qe1l1 F+Zqith+WKSbC4coqfwlSpMruFD+LYHZL7dNxMn6lM1BlClgpU+trBBfU8X3NRWpduUC gm5jDdavG9LPULlEG6v5xW8EWWxnTEMlI/l1Dx6IcP7xvbPTameGbU5ncGLR9s2CMQDH +UXolAKQbOS3Immkj9GRR+EGZy6YciTKgHKl4y2mtIX4isEII+ZF42C6ELacpYEvFd1C DSTx8Eo3QIZMJTMX9qdbjrcadSKkO/lE8nkr9G4QTAYreJUXcKmKyBWx1/795uMwJisq uzsQ== X-Gm-Message-State: AElRT7EebuUjurbOg9mCvj8y5jjANvuWfsqXEVGsWVK34lzIJ/DcmRzy c6RuoEwYSVKz3NpC6XVHO/I= X-Google-Smtp-Source: AG47ELuKYhVFUajxF99wlm1H6t4g/rP+Xz6W3EMc3HyNZnrO3nDKMA+MA5LjmnFiR2IZU+xCRXv11g== X-Received: by 10.28.74.199 with SMTP id n68mr3611035wmi.83.1520076788473; Sat, 03 Mar 2018 03:33:08 -0800 (PST) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id v23sm298108wmc.22.2018.03.03.03.33.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 03:33:07 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Sat, 3 Mar 2018 11:33:06 +0000 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: "Mars G. Miro" Cc: Warner Losh , Martin Simmons , FreeBSD FS Subject: Re: growfs only works on GPT partitioning schemes? Message-ID: <20180303113306.GB2029@brick> Mail-Followup-To: "Mars G. Miro" , Warner Losh , Martin Simmons , FreeBSD FS References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A9A4B1E.8070206@anarchy.in.the.ph> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 11:33:10 -0000 On 0303T1513, Mars G. Miro wrote: > On 02/26/18 22:30, Warner Losh wrote: > > > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons > > wrote: > > > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > > > > > It seems that growfs only works on GPT partitioned schemes ? > > > > > > When I first installed my FreeBSD, I unfortunately chose BSD during the > > > FS creation. Now that I ran out of space, I wanted to increase the > > > filesystem size. Successfully did so in Virtualbox but after rebooting, the > > > HD doesn't see the new allocated space. It has another virtual HD, one > > > created with GPT and I was able to increase it via growfs. > > > > For the BSD scheme, I think you also have to resize the slice (i.e. > > the MBR > > entry) and then resize the BSD partition within the slice. > > > > > > You do. The /etc/rc.d script that does resize on boot does that > > automatically, but we have no other automation for the process. > > > > Warner > > You guys have any idea how to resize the slice ? > > I have 2 HDs, both have already been increased (in VirtualBox). The BSD > partitioned scheme below doesn't see the newly allocated disk space, > only the GPT one. > > camcontrol reprobe / gpart recover / etc doesn't do anything. > > mars@fbsd11vm1:~ % gpart show > => 0 83886080 ada0 BSD (40G) > 0 4194304 1 freebsd-ufs (2.0G) > 4194304 16777216 2 freebsd-ufs (8.0G) > 20971520 62914559 4 freebsd-ufs (30G) > 83886079 1 - free - (512B) > > => 40 104857520 ada1 GPT (60G) [CORRUPT] > 40 12582912 1 freebsd-swap (6.0G) > 12582952 92274608 2 freebsd-ufs (44G) What does "geom disk list" show? From owner-freebsd-fs@freebsd.org Sat Mar 3 12:28:59 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 CF4AFF37A88; Sat, 3 Mar 2018 12:28:59 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 6869E7F053; Sat, 3 Mar 2018 12:28:59 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CF98920BE0; Sat, 3 Mar 2018 07:28:58 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 03 Mar 2018 07:28:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=DURPaCa293hbkyyfUw2BjXEpOCYmE HQAwRvUbi5wRsU=; b=hugGkg1rPH6yfz18+SgDjuO1fiH+n6NUoZtzqvO0oEq95 gRvFicMCpU73mKaf1byOX1ZfxwSwn/f28LFl7iIeg6jj1u/W+IHVDGfOY65cEvYp mnISI9HzfhCGxU6eecrvieuJernf0gpvmNpIt3fKZO91s6Px1pZu4ke3ZavsllPa y6+wl5pu4CgqPyIlOyVEhM0oA2zqtIPrs/QAl4KNCTNUSamxcb0n6jxwapuTPwWi Re6c98QkyWa0fRDp+dhvilRH+gssOUmsIHFrnIe/7iTIP00AcAwvONMEGmiuDUGx P2qSe6MFN7WrqhU6eQOBWZk/zRen9t3ZEJKt5LrZw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DURPaC a293hbkyyfUw2BjXEpOCYmEHQAwRvUbi5wRsU=; b=QpiEE6jxNydaHcMPo71MID rJUC6u4pJaoA234dapewBoKNqqLU7YP76cUwVswsXaSk+GiJsCyUOILa7grvhf4j A37j0Ob8sS4zI+0XEJCgBsTCcdDQusG3xJ+l6jqvyeEk/S/KR/cQ/sDvV4yx+4U+ R3AaQ9I3iQoxwashYeeKIULd6ptyxZKr/a5Y3ySt/YmUxK2jQ4tRMFaHF7V3VGIV hXUwmuhdjHZRtpT5VDHogtlLZ5t+qyGO5L26UiU/iKQ/QHAg7C9ur4vKH/Hwr/h0 VI7HBlTkeUYRin3IoVJMB5utifDjXPz2Vzise/lI/ZfYKSXEqrYGOnaLC5xl4gMA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 428BA243C4; Sat, 3 Mar 2018 07:28:58 -0500 (EST) Subject: Re: zfs problems after rebuilding system [SOLVED] To: Dimitry Andric Cc: FreeBSD Filesystems , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> From: tech-lists Message-ID: Date: Sat, 3 Mar 2018 12:28:57 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 12:29:00 -0000 On 03/03/2018 00:23, Dimitry Andric wrote: > Indeed. I have had the following for a few years now, due to USB drives > with ZFS pools: > > --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 > +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 > @@ -25,6 +25,8 @@ > > zfs_start_main() > { > + echo "Sleeping for 10 seconds to let USB devices settle..." > + sleep 10 > zfs mount -va > zfs share -a > if [ ! -r /etc/zfs/exports ]; then > > For some reason, USB3 (xhci) controllers can take a very, very long time > to correctly attach mass storage devices: I usually see many timeouts > before they finally get detected. After that, the devices always work > just fine, though. > > Whether this is due to some sort of BIOS handover trouble, or due to > cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate > disks!), I have no idea. I attempted to debug it at some point, but > a well-placed "sleep 10" was an acceptable workaround... :) That fixed it, thank you again :D -- J. From owner-freebsd-fs@freebsd.org Sat Mar 3 12:56:54 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 ECFFFF39BB3; Sat, 3 Mar 2018 12:56:53 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail104.syd.optusnet.com.au (mail104.syd.optusnet.com.au [211.29.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 66B088005E; Sat, 3 Mar 2018 12:56:52 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from [192.168.0.102] (c110-21-101-228.carlnfd1.nsw.optusnet.com.au [110.21.101.228]) by mail104.syd.optusnet.com.au (Postfix) with ESMTPS id 5B11442B126; Sat, 3 Mar 2018 23:56:50 +1100 (AEDT) Date: Sat, 3 Mar 2018 23:56:49 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: tech-lists cc: Dimitry Andric , FreeBSD Filesystems , FreeBSD Stable Subject: Re: zfs problems after rebuilding system [SOLVED] In-Reply-To: Message-ID: <20180303234236.M3811@besplex.bde.org> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.2 cv=VJytp5HX c=1 sm=1 tr=0 a=PalzARQSbocsUSjMRkwAPg==:117 a=PalzARQSbocsUSjMRkwAPg==:17 a=kj9zAlcOel0A:10 a=SY9sppriGsu9APizm8IA:9 a=6AGLiD1o6bKYU7sQ:21 a=jMnuJzigikWx0_6H:21 a=CjuIK1q_8ugA:10 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 12:56:54 -0000 On Sat, 3 Mar 2018, tech-lists wrote: > On 03/03/2018 00:23, Dimitry Andric wrote: >> Indeed. I have had the following for a few years now, due to USB drives >> with ZFS pools: >> >> --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 >> +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 >> @@ -25,6 +25,8 @@ >> >> zfs_start_main() >> { >> + echo "Sleeping for 10 seconds to let USB devices settle..." >> + sleep 10 >> zfs mount -va >> zfs share -a >> if [ ! -r /etc/zfs/exports ]; then >> >> For some reason, USB3 (xhci) controllers can take a very, very long time >> to correctly attach mass storage devices: I usually see many timeouts >> before they finally get detected. After that, the devices always work >> just fine, though. I have one that works for an old USB hard drive but never works for a not so old USB flash drive and a new SSD in a USB dock (just to check the SSD speed when handicapped by USB). Win7 has no problems with the xhci and USB flash drive combination, and FreeBSD has no problems with the drive on other systems. >> Whether this is due to some sort of BIOS handover trouble, or due to >> cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate >> disks!), I have no idea. I attempted to debug it at some point, but >> a well-placed "sleep 10" was an acceptable workaround... :) > > That fixed it, thank you again :D That won't work for the boot drive. When no boot drive is detected early enough, the kernel goes to the mountroot prompt. That seems to hold a Giant lock which inhibits further progress being made. Sometimes progress can be made by trying to mount unmountable partitions on other drives, but this usually goes too fast, especially if the USB drive often times out. Bruce From owner-freebsd-fs@freebsd.org Sat Mar 3 13:29:49 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 5498DF3C51E; Sat, 3 Mar 2018 13:29:49 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 F1720814C8; Sat, 3 Mar 2018 13:29:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 244AB20B5A; Sat, 3 Mar 2018 08:29:48 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 03 Mar 2018 08:29:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=9xic609pw4mxd+V4k9zm0VcPtBof+ W7BLNj39qDDn7E=; b=udMlOdFPwmQP8z7dalUSyEnxdhMhkUia7zjeXBw9NZbtr RO7potFguXFXGhfMDPhKV/wEaBBecG04xD5zO1LigL2jvYoF/AeF39Xk9QfsDMAI /KvKl+p6l8GuPRbfnc4atjxTIQdgflKYGTWoHHG96u+Mt34EljGtPFdQABlJs6aT zCihUbISL4DqcOOGrcUM1CnF6z7JugMKbcMu9y4Hr/mrhmdnFF7zYN0z+yFW45jI tpzC03no1Q1OiYABFWoN/qXwWV7K62h0+hY5e1sCtDxrQ9ZZ/V/mj+Lb76q7XCMi T9eTA+EegmmEt9oQUHldPO9TqoQi4C8a7XpOXytVQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=9xic60 9pw4mxd+V4k9zm0VcPtBof+W7BLNj39qDDn7E=; b=TSs39S97/8BjJ3sW139uj4 wiINEoDMPvMb9Imz19msuGu4BX92Y6+uYdLUHlaEbKfMxAc7g89oWysGCjTSRd0X E+w+Ncqe5T3MIfasqHILe5Z6NffVDyWDl8QJPFp48CaSt0fzXVm08EsBTXTKGu0P iXRwMuZL8U9YIePzqatrK2tYovadMii18DvJww7n6poYL/+qryw2FxSX01ABb6I/ byfXQRHNrxshBcieRDWh/hK9fL4uGcLNhAeIwAZawsbCl50biBcvInDFVO/QMLAl hepeGRBFgGJaD04u9dvHg1VvT9HhtlDmxqKt8PL+RgtOR+9o/B+s/Lk/nIogbIfA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A41C4246C8; Sat, 3 Mar 2018 08:29:47 -0500 (EST) Subject: Re: zfs problems after rebuilding system [SOLVED] To: FreeBSD Filesystems Cc: FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <20180303234236.M3811@besplex.bde.org> From: tech-lists Message-ID: Date: Sat, 3 Mar 2018 13:29:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180303234236.M3811@besplex.bde.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 13:29:49 -0000 On 03/03/2018 12:56, Bruce Evans wrote: > That won't work for the boot drive. In my case the workaround is fine because it's not a boot drive -- J. From owner-freebsd-fs@freebsd.org Sat Mar 3 14:26: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 18CE8F40926; Sat, 3 Mar 2018 14:26:57 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC0E8378A; Sat, 3 Mar 2018 14:26:56 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w23EQlkH001512 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 3 Mar 2018 15:26:48 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: brde@optusnet.com.au Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w23EQhih095788 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 3 Mar 2018 21:26:43 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: zfs problems after rebuilding system [SOLVED] To: Bruce Evans , tech-lists References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <20180303234236.M3811@besplex.bde.org> Cc: FreeBSD Filesystems , FreeBSD Stable , Dimitry Andric From: Eugene Grosbein Message-ID: <5A9AB09E.6090500@grosbein.net> Date: Sat, 3 Mar 2018 21:26:38 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20180303234236.M3811@besplex.bde.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 14:26:57 -0000 03.03.2018 19:56, Bruce Evans wrote: > On Sat, 3 Mar 2018, tech-lists wrote: > >> On 03/03/2018 00:23, Dimitry Andric wrote: >>> Indeed. I have had the following for a few years now, due to USB drives >>> with ZFS pools: >>> >>> --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 >>> +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 >>> @@ -25,6 +25,8 @@ >>> >>> zfs_start_main() >>> { >>> + echo "Sleeping for 10 seconds to let USB devices settle..." >>> + sleep 10 >>> zfs mount -va >>> zfs share -a >>> if [ ! -r /etc/zfs/exports ]; then >>> >>> For some reason, USB3 (xhci) controllers can take a very, very long time >>> to correctly attach mass storage devices: I usually see many timeouts >>> before they finally get detected. After that, the devices always work >>> just fine, though. > > I have one that works for an old USB hard drive but never works for a not > so old USB flash drive and a new SSD in a USB dock (just to check the SSD > speed when handicapped by USB). Win7 has no problems with the xhci and > USB flash drive combination, and FreeBSD has no problems with the drive > on other systems. > >>> Whether this is due to some sort of BIOS handover trouble, or due to >>> cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate >>> disks!), I have no idea. I attempted to debug it at some point, but >>> a well-placed "sleep 10" was an acceptable workaround... :) >> >> That fixed it, thank you again :D > > That won't work for the boot drive. > > When no boot drive is detected early enough, the kernel goes to the > mountroot prompt. That seems to hold a Giant lock which inhibits > further progress being made. Sometimes progress can be made by trying > to mount unmountable partitions on other drives, but this usually goes > too fast, especially if the USB drive often times out. In fact, we have enough loader.conf quirks for that: kern.cam.boot_delay "Bus registration wait time" # miliseconds vfs.mountroot.timeout "Wait for root mount" # seconds vfs.root_mount_always_wait "Wait for root mount holds even if the root device already exists" # boolean No need in extra hacks to zfs rc.d script. From owner-freebsd-fs@freebsd.org Sat Mar 3 15:29:29 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 905D3F44EF5 for ; Sat, 3 Mar 2018 15:29:29 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::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 27BF48619B for ; Sat, 3 Mar 2018 15:29:29 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by mail-qk0-x233.google.com with SMTP id d206so15651903qkb.3 for ; Sat, 03 Mar 2018 07:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarchy-in-the-ph.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=toXu38m23rMc8fH0pSXKvHTvh8sRCs0zG7844b1CED0=; b=GWy6fSh0oAkphgQ9A2SLHl8qLw75Qnl3Rrx/OokUYLUmdLPTRHm+C9hBc+dKsApwaq n7X7tjKZLDV3OAkSsNqn9KKLsaSLU0g3qWJYyVmdwPzj4eylVqnNvmw+yZjJZxIbL2qd h0hmvrVb8W2Aph18JPgQSGeXAZmRM3RNzXbF0/7ziZtgYcwbG+domfzhPeyduGT8E1C5 PAHqSqe9pAqJ4/990bXKHroyarGTVtVMh5qfsJbjv/9VTmLmTq4dK1lh1fyLYS17m22y yzgV6i9uycD/bauM2FyEZtJWQQyTcupHnpDnJEIReWFrUwlLSis19gOtbCAqTenp8FAb Huaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=toXu38m23rMc8fH0pSXKvHTvh8sRCs0zG7844b1CED0=; b=aZ+QDw3HDBA0vHNdQG704GEICNK5Ncs6j7OGm84Y+/i63fCYlST2bfAGRQMkxV8oqX 8mcYvfn1zqWlb/2/jV2zMiAEx+lafnhYob/q2Db33r7gRLkwhSBcVeDgzQEZrbxH3we9 ouh4uRMOVNqrb6voiWUuUf6BOi1sZTnxjBKnpCO2mBsofBnLvF+roYMaTuTARkSrQYcA 0fKgai4rOBvBNEaI4ooiBmr09ASQzqift61b8srr+piDf9O0fyn3m2TL7itzB/53ao12 zO+qSUL0T3oDFpJ0mlKIz/VUByAIsLeiE0IQtUL/Zgfn4kfboNbSWfOtgkizILyoee+R dwrQ== X-Gm-Message-State: AElRT7HjqtfIyp5dn4osEMzC2AfOmAahEfAQmHZnPtz5i51zN5pkRcHM dKjJG7XOsYuBL7QOpb/yCIqTOYe5kGBhbX/sb3f+HIYs X-Google-Smtp-Source: AG47ELtHkJSzt48z4ospRJb7ATcBqyyvcAAT3fGnDvn4D2SBL7vpcamqWpKFoX+e7O3dP/YvockHfh9YNEKpTuOMgiE= X-Received: by 10.233.216.68 with SMTP id u65mr13574010qkf.39.1520090968608; Sat, 03 Mar 2018 07:29:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.149.120 with HTTP; Sat, 3 Mar 2018 07:29:28 -0800 (PST) In-Reply-To: <20180303113306.GB2029@brick> References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> From: Mars G Miro Date: Sat, 3 Mar 2018 23:29:28 +0800 Message-ID: Subject: Re: growfs only works on GPT partitioning schemes? To: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Cc: Warner Losh , Martin Simmons , FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 15:29:29 -0000 On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz Napiera=C5=82a wrote: > On 0303T1513, Mars G. Miro wrote: > > On 02/26/18 22:30, Warner Losh wrote: > > > > > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons > > > wrote: > > > > > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > > > > > > > It seems that growfs only works on GPT partitioned schemes ? > > > > > > > > When I first installed my FreeBSD, I unfortunately chose BSD > during the > > > > FS creation. Now that I ran out of space, I wanted to increase > the > > > > filesystem size. Successfully did so in Virtualbox but after > rebooting, the > > > > HD doesn't see the new allocated space. It has another virtual > HD, one > > > > created with GPT and I was able to increase it via growfs. > > > > > > For the BSD scheme, I think you also have to resize the slice (i.= e. > > > the MBR > > > entry) and then resize the BSD partition within the slice. > > > > > > > > > You do. The /etc/rc.d script that does resize on boot does that > > > automatically, but we have no other automation for the process. > > > > > > Warner > > > > You guys have any idea how to resize the slice ? > > > > I have 2 HDs, both have already been increased (in VirtualBox). The BSD > > partitioned scheme below doesn't see the newly allocated disk space, > > only the GPT one. > > > > camcontrol reprobe / gpart recover / etc doesn't do anything. > > > > mars@fbsd11vm1:~ % gpart show > > =3D> 0 83886080 ada0 BSD (40G) > > 0 4194304 1 freebsd-ufs (2.0G) > > 4194304 16777216 2 freebsd-ufs (8.0G) > > 20971520 62914559 4 freebsd-ufs (30G) > > 83886079 1 - free - (512B) > > > > =3D> 40 104857520 ada1 GPT (60G) [CORRUPT] > > 40 12582912 1 freebsd-swap (6.0G) > > 12582952 92274608 2 freebsd-ufs (44G) > > What does "geom disk list" show? > > Supposedly the first drive should already have been 80Gb but: mars@fbsd11vm1:~ % geom disk list ... Geom name: ada0 Providers: 1. Name: ada0 Mediasize: 42949672960 (40G) Sectorsize: 512 Mode: r3w3e6 descr: VBOX HARDDISK ident: VB1e5e1cab-a4c47c87 rotationrate: 0 fwsectors: 63 fwheads: 16 Geom name: ada1 Providers: 1. Name: ada1 Mediasize: 64424509440 (60G) Sectorsize: 512 Mode: r2w2e3 descr: VBOX HARDDISK ident: VBef5bd266-afbdd2b4 rotationrate: 0 fwsectors: 63 fwheads: 16 Thanks! --=20 cheers mars ----- From owner-freebsd-fs@freebsd.org Sat Mar 3 19:01:36 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 11544F32664 for ; Sat, 3 Mar 2018 19:01:36 +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 9A00E70BFB for ; Sat, 3 Mar 2018 19:01:35 +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 CC524264B8 for ; Sat, 3 Mar 2018 19:01:34 +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 w23J1YEv066986 for ; Sat, 3 Mar 2018 19:01:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w23J1YMB066984 for freebsd-fs@FreeBSD.org; Sat, 3 Mar 2018 19:01:34 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: freebsd-fs@FreeBSD.org Subject: [Bug 208882] zfs root filesystem mount failure on startup in FreeBSD 10.3-RELEASE if USB hdd with zpool is attached to another port Date: Sat, 03 Mar 2018 19:01:35 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pi@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 19:01:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 --- Comment #18 from Kurt Jaeger --- See=20 https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088484.html and discussion. Seems to be a common problem. --=20 You are receiving this mail because: You are the assignee for the bug.=