From owner-freebsd-current@freebsd.org Sun Apr 7 22:17:59 2019 Return-Path: Delivered-To: freebsd-current@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 435E6156CF23 for ; Sun, 7 Apr 2019 22:17:59 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-ed1-f68.google.com (mail-ed1-f68.google.com [209.85.208.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EBCA474ED1; Sun, 7 Apr 2019 22:17:57 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: by mail-ed1-f68.google.com with SMTP id s39so9954261edb.2; Sun, 07 Apr 2019 15:17:57 -0700 (PDT) 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=dR+a6yOLTouon7od/5WYYGuOXG+33gkXITKvurYSTug=; b=BOkBSgzYHB2WHC8IU1Ei9bCVq3qm161ciVbaTj4gOxTsRBw16ERsQulqPlUe+Ex+wp BbELSyDPLK5xZTpsfphhSoLA7fJIufv5Xds4Fqp4uyLM0mW5uggGjAd8TTH48rbzdNYC GU62DZ55gbdK/7g3zttyu7GCNNk74OLOClNvVTdNYT3tr+BYK8ctia78rk7Cr1PgPGp7 nAY+yo5YYSy6uHuCjK8cWNzbzg0WRx60drLXLLpWhNVzMvCKiEwRqplNGI1wZ0GMNxS8 2Wty+yr8A1P3tNqc4gU9wjIQNmbGw+wM1OUKkdHv/lm9WYpYyFZUownX2IPf4A4C5Ly+ 708g== X-Gm-Message-State: APjAAAWsohDquy0t3qdYwzY8Gv57D/joXohKBfIjAE2zwDFr/q0HvjoB 0wBKD3Wyh6UXcBRDMICwnoRu9/wipuhqjN/B8I1Qng== X-Google-Smtp-Source: APXvYqxb7I9jscMFbAEANbkC8tdhdSCqB+UE08w/7luzOnlPHnam9pYoDh4Mu2DqlJi9yOuAwR+LiDSMX7ProKH7p/Q= X-Received: by 2002:a50:b582:: with SMTP id a2mr16860226ede.268.1554675034871; Sun, 07 Apr 2019 15:10:34 -0700 (PDT) MIME-Version: 1.0 From: Antoine Brodin Date: Mon, 8 Apr 2019 00:10:23 +0200 Message-ID: Subject: Kernel regression in head, now unusable for package building To: FreeBSD Current , Konstantin Belousov Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: EBCA474ED1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of antoinebrodinfreebsd@gmail.com designates 209.85.208.68 as permitted sender) smtp.mailfrom=antoinebrodinfreebsd@gmail.com X-Spamd-Result: default: False [-4.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.18), country: US(-0.06)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.208.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.87)[-0.872,0]; FORGED_SENDER(0.30)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2019 22:17:59 -0000 Hi, There seems to be a kernel regression in head, that happened somewhere between r343921 and r345991. When launching "poudriere bulk -a", the ssh session is terminated when poudriere attempts to clone/start builders (tmpfs mounts, file copying...), the jails don't start and the consequence is that we can't build any package. Cheers, Antoine (with hat: portmgr) From owner-freebsd-current@freebsd.org Mon Apr 8 08:25:38 2019 Return-Path: Delivered-To: freebsd-current@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 A1F8E1578F8E for ; Mon, 8 Apr 2019 08:25:38 +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 D8F548E004; Mon, 8 Apr 2019 08:25:37 +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 x388PTX3015508 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Apr 2019 11:25:32 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x388PTX3015508 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x388PTt1015507; Mon, 8 Apr 2019 11:25:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 8 Apr 2019 11:25:29 +0300 From: Konstantin Belousov To: Antoine Brodin Cc: FreeBSD Current Subject: Re: Kernel regression in head, now unusable for package building Message-ID: <20190408082529.GN1923@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.11.4 (2019-03-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Apr 2019 08:25:38 -0000 On Mon, Apr 08, 2019 at 12:10:23AM +0200, Antoine Brodin wrote: > Hi, > > There seems to be a kernel regression in head, that happened > somewhere between r343921 and r345991. Can you bisect ? I looked over the stated range and I do not see a revision that would be an obvious candidate for the regression. I could think about r345955, r345980, and r345982/r345983 as something that might be most interesting to try. > When launching "poudriere bulk -a", the ssh session is terminated > when poudriere attempts to clone/start builders (tmpfs mounts, file > copying...), the jails don't start and the consequence is that we > can't build any package. Are there any more details about the issue ? It is not clear, does the machine survives the event, i.e. did kernel paniced, what are the console messages, any more details that you can provide. Long time ago there was a similarly sound bug where mountd(8) signalled wrong process, which caused ssh sessions termination. > > Cheers, > > Antoine (with hat: portmgr) From owner-freebsd-current@freebsd.org Mon Apr 8 18:36:18 2019 Return-Path: Delivered-To: freebsd-current@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 447D71564A9F for ; Mon, 8 Apr 2019 18:36:18 +0000 (UTC) (envelope-from ml+freebsd@vishwin.info) Received: from varun.vishwin.info (varun.vishwin.info [46.101.93.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "varun.vishwin.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8874D85EA8; Mon, 8 Apr 2019 18:36:17 +0000 (UTC) (envelope-from ml+freebsd@vishwin.info) Received: from varun.vishwin.info (fd35:9eae:7575::2 [IPv6:fd35:9eae:7575::2]) by varun.vishwin.info (OpenSMTPD) with ESMTP id afaeb580; Mon, 8 Apr 2019 14:36:13 -0400 (EDT) Received: from [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d] (2001:470:8:6ca:cad7:19ff:fec0:a06d [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d]) by varun.vishwin.info (OpenSMTPD) with ESMTPSA id ad3fd87e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 8 Apr 2019 14:36:12 -0400 (EDT) Subject: Re: Kernel regression in head, now unusable for package building To: Konstantin Belousov , Antoine Brodin Cc: FreeBSD Current References: <20190408082529.GN1923@kib.kiev.ua> From: Charlie Li Openpgp: preference=signencrypt Autocrypt: addr=ml+freebsd@vishwin.info; keydata= mQINBFt7iHUBEADCorTixbMGuHd9WYSKCELlv/TFcRtvpHUw/n9LtXzKixUUwl7iuMFMYTz3 QXePX0Twq4jCQYySfcxWbPkLsSYlPOkaGQ+XytfmIHoqG5ba4i1fp+F41is0oCtLt1+oL84j NKUd13em/JWd+PJeQbSTVnHbT2yaAi7vqWw5WKVaMExjfPGU5TArV46wSRU6Zuy1ZX66q0q5 dPzeBdeKYWJE8aGtyi3pYUpKUOX4gxiNetf6leDFZ4OsexWaRdU0n8fId5d1qwjAE3lOwV5z 0Ilt8t4iXtX3JL3DAQyLZIeXHIg9O3rrpPMXQWSp2/5g39PohNk7farbhcpIKxuDN+L5N6U9 OxNHBSCv9FGDO4R/mw3YwJCovDzsF7RSyXQDIY36yjdh2uTLZ0uD5Ci/DPmJUySFLRvpqWnQ M7V5cYhdqDfcElGpRbi8JZQVYRJjvI5Jj0byG98KeaD0YFxKqmmm+Oh+xWXE7xt/DsBoZeZJ BFP84LvFbwQqprvI+sg+1z2+JIgNbYwl8VaYzfyGnqTEXTOsQYEKTdKA9MODSAsN31MlQICe CIHZV+OwOqH1KQ/mZp59AnpXAmj4T94bnahE9yJtVW/qglX/nTeFNUdu5MyEgkeB0x7mx+t0 3hE20yp/NbyvG1T/o53NHwHiURC/8Fxd1NWPZ6n4X8npQn6iyQARAQABtC5DaGFybGllIExp IChGcmVlQlNEKSA8bWwrZnJlZWJzZEB2aXNod2luLmluZm8+iQJOBBMBCAA4FiEE/3/Cqr5a +41PbEb+jnB43vIDq2wFAlt7iwoCGyMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQjnB4 3vIDq2zlBQ/7Boe3K9i4pxvIlBWlFDmDuclLiju/LTsc81mO607TIwUMx5p3BfnhqTwqpcuT Gilj2JKSlIw0NioJ3HnPiPyIpMmOmdeLBwvBn8iBmjs14DdDMgKusE8gKc0KRFbTM397rB7K oXj2/R8VF3Uuo8i3vlWyah6p+Osz1dAad/7COqPeM9OBMKaYAOrdKvxMC96l5k+Wc1JKOLeA BP7BtgmQB7HydHUm+dzqUB1rgMP2djIXd5Ngc749kzNQIFvC9ZXbaABw5M4JqKRbVFm08Wgw IUyhkNEtMpkBxMPwqXsk3t1KVptYQSAfW/+8mWDP2sgUOyz9O2IBfb1acCPk04/jf8SsXRaT HzJr64NseWlZUHAMYl9EC09gdE6UDCIHR68+IzutMtgT17Djuu1HRYly+RWAGkyTOeR7Sv/V 2B89Nsq5OfHYs3F2vD57/aRj5TmZJDQWxH/rDYbj8Pk6UjXcaY6QWUtNFidvCMFlBpXuncXU ZWgTsJEyZLHP5SJ7S9sRSHU5+CVUkjsbEFNuHkkGHAkSnpP+HosnH8/q9Rykn9FTamLbiQRQ UxJ6+IlqvOUtRRrMGMBF7ZIFGHcl8tcKynsPTeaHjpqPhCrZx8PmCKKoJHwW4Ua7+cdZkBJq R20qvXuLIrInjkIpA1CbacMckS5a7el6pi/nU0NG1S1K4Zu5Ag0EW3uIdQEQANdl7YHG8JOy HbEYv+7ExSrO96qBRavg1FsDG0riDmlsOSfZ2fqL6/YJF5WsfsX99+YSdIiLQfC4QOw/cA+M I65pgY4cCu42L7YIW/AR+jB1hFg+Q/cbeOwjuKPFYtZvxeDpSsaA6iIR+p+t4DXkjWl86g6W aFLC+til/rCilFHY/1/6M918F1gm/6xCIADDFu0BXLkASc5B4LuvaFEiJIuI9ZoQDIgWxnsX 0tXXE36SwK/XrowzRzsOa+2iOHAPKu7rPGHwy28vO4T5Uq7UynMZG2sK3RTbOijaxL4IJF4W MRqpuGdBSJ4sWmr5aIpgX9au5L1TNAAILJpHXnkv+k825+9VgbhFtFYBHEkgUtXb+w34JnkH okpr9A78dpWb+T+jOEP6ZUgM+4VVy+hCCpbcCVI2PEXu8w2z3+4yZWxIFmy8UYZRoeTMKzV2 zLeisoA0XA8jj548YNPiAl20Mjyoqu42WNv0P8fD9PMTcfLFCj2PlxOhuUFaIUH3ty0/bNeS jPtVK+L9x4W37R7U1tYk+tB5MlPakQiSQtdToB+8K34rnBt/3kCoAYL7Hygw9+qyZrEKZDtP 5JKekfgsy28t1z66xWCUwq9PHuUFiij3cjbwIbskI9uy2+xITcXt4ZqVfpZcdGmjfbdTPkGf PH2pjDoCJaezYdbha/3OVhmVABEBAAGJAjYEGAEIACAWIQT/f8Kqvlr7jU9sRv6OcHje8gOr bAUCW3uIdQIbDAAKCRCOcHje8gOrbExnD/9qwSL4HiorJmUEJ+5CTh8IJql4PzeQK8Dx93gi Zs5jWVlCJTmcpQNirWIZM2eRt67C/wTJjLmEVGzySVLpGiUqhXqdROgFmDwvEnmpIbtWWyvG sgSOCmZj/tz0GEtLSsjJcV/kLffkv7XEKkt9ZjIJnFYVYSovDK1o2PoO6Rfi5AWHHB7jYhjS HJvJjDx0yClO9gEYhtw7R60YOLH+cKoDou9tu+4wR3QwRsNGO6wrzLGhptxuBrDMI+HuOx+j wBTliuzuvZrry6OdKDDdq5D4vvQCj4vFnK4p7LZXhBshCMoLkWoA0I2T+YF/V5Ob5EuvsTIC re/pO/g941ipVkehvVNAsiplSaHjasB1HS6BQ95csI8E/b6PnKm+IECp2bANbLP1jrxKeBGj UkeyRxTmOV/ADUIIj8S4a2yOxTxlysN2O5wqXCJcxaYelC/Y4TUcL6ENxn2dLBdCYKQEna0u DdxZp7fS+pXN6qyK8Qz6Q42MHAxFAZdLKf6a44d4HQt6rPcWdETVlnVKnJr0b9kg5K1Q8N4k PVoTGVrkGAZhmjFYsqWulq445VU46mX7WcqsrZx8LqNTwP6i3Bf71FJ9EBxTyA8fP8k0qosP 8U8D7jhcc5x4yVW8RBBtB+a5q3odWdFnjMLEm4wtxBH/mSN/UKRcFSBvKQ8FxTgpX4Yxcw== Organization: FreeBSD Message-ID: <5e53428e-f557-9d7d-03f0-e07a5fbbed57@vishwin.info> Date: Mon, 8 Apr 2019 14:36:05 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190408082529.GN1923@kib.kiev.ua> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qdudqLExNYFMRgXTjPvdUEMw4vW3seuf0" X-Rspamd-Queue-Id: 8874D85EA8 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; TAGGED_FROM(0.00)[freebsd] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Apr 2019 18:36:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qdudqLExNYFMRgXTjPvdUEMw4vW3seuf0 Content-Type: multipart/mixed; boundary="dAW4nJEYf06va0g6RZDofQ7lvDH5bYpMS"; protected-headers="v1" From: Charlie Li To: Konstantin Belousov , Antoine Brodin Cc: FreeBSD Current Message-ID: <5e53428e-f557-9d7d-03f0-e07a5fbbed57@vishwin.info> Subject: Re: Kernel regression in head, now unusable for package building References: <20190408082529.GN1923@kib.kiev.ua> In-Reply-To: <20190408082529.GN1923@kib.kiev.ua> --dAW4nJEYf06va0g6RZDofQ7lvDH5bYpMS Content-Type: text/plain; charset=utf-8 Content-Language: en-GB-large Content-Transfer-Encoding: quoted-printable Konstantin Belousov wrote: > On Mon, Apr 08, 2019 at 12:10:23AM +0200, Antoine Brodin wrote: >> There seems to be a kernel regression in head, that happened >> somewhere between r343921 and r345991. >> When launching "poudriere bulk -a", the ssh session is terminated >> when poudriere attempts to clone/start builders (tmpfs mounts, file >> copying...), the jails don't start and the consequence is that we >> can't build any package. > Are there any more details about the issue ? It is not clear, does the= > machine survives the event, i.e. did kernel paniced, what are the conso= le > messages, any more details that you can provide. >=20 I just ran into this both on a remote machine and the laptop I'm typing on right now. At least the reference jail does start and run, as any subsequent poudriere-bulk(8) invocations detect it. The entire login session is killed in the process, and the only clue of anything I can find (at least in the syslog) is that ntpd exits with Hangup: Apr 8 14:12:27 ardmore ntpd[74109]: ntpd exiting on signal 1 (Hangup) This seems to happen randomly, but still quite often. Restarting ntpd can help, though ntpd can still exit and kill the login again. Without ntpd running, running poudriere-bulk(8) is guaranteed to kill the login. --=20 Charlie Li =E2=80=A6nope, still don't have an exit line. (This email address is for mailing list use; replace local-part with vishwin for off-list communication if possible) --dAW4nJEYf06va0g6RZDofQ7lvDH5bYpMS-- --qdudqLExNYFMRgXTjPvdUEMw4vW3seuf0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE/3/Cqr5a+41PbEb+jnB43vIDq2wFAlyrlJsACgkQjnB43vID q2zktw/7BJmUSt1ZzLk27XoPKtV+hKweIquAQrYLKKtl9DCJ2XrPRisnljMy1ZnV T6IjmtxCvhizWzyR0wgfR74RqJF8PEO8bINvXG+t2OX/uBxzXSKj8DyCa7iBalP1 CtSYdwQ+jJs944u4SaKu+6E1MloMzEW6lrdKPToM+Fyh/5bPrtNxKXX0evrdpPyA j3ZH42q9bARMgP4jsSN1Rsan1umIpv9ufsbukUOLG79s6hoc+fSclckXfqM3Eerr TwYJ3uUxoccOylxcnr4iIOWhSQNNySzKO8oNywBzWXljTs7cuxNQ2O3GKktVVZZ4 p/H1BsAn+wVjpcDlpFjshIGOws5Ca8II06UwrtH5M+HBnzskVsP4/0goZxwMbj78 rN9DC+F4bf4yMjavdN1GbNdRLbfrV8JNCmF/AAYCbHniP3fjhbKAAeBpaS28PSJ5 gM2LE7PdwV+JORqTlg9T3fmuIOzs0qza49CDdFCKp5vf5eGeDD9UmJIk3nZQg8Xl Z7QKqTSJaXHd9rInqo0cXKuQErJTUSHDgewTlgVohpmeUzQ57/CZnO7Il3ikHldg nPTsVn7GEmVDqDwOiyeGYPpnZIrPlY2s9NY6XROfMyrT1WLlzBdnWuxeGl4+sUKg BDGJ5abUNATnJxGcY67SFfFs1sRRgNbFpPlIocNKn6EqxKsgcsI= =7yAp -----END PGP SIGNATURE----- --qdudqLExNYFMRgXTjPvdUEMw4vW3seuf0-- From owner-freebsd-current@freebsd.org Mon Apr 8 17:59:02 2019 Return-Path: Delivered-To: freebsd-current@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 713451563610 for ; Mon, 8 Apr 2019 17:59:02 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C8C783F13 for ; Mon, 8 Apr 2019 17:59:00 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554746339; bh=m3XED45b2XXxju0HuOdM7juu+PQNDZtoUqf88zvwegE=; h=X-UI-Sender-Class:Date:From:To:Subject; b=dJIPJ6ZkQIGbpjVewxCauo6daOSRIxd/VuV7Ylmt8bDZPsknaJ+jdFVVidFBaGqba YsLSq0N7w/PGH3O8BsOtqbe418u5EAAlXODj6dlh6+qUOClMJu4LqhbJG8/eELWYOP lonqbsZCBgu3X2Ie/1NDf1gdI3EUHAdoL7ltfMSI= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from thor.intern.walstatt.dynvpn.de ([77.11.81.119]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MLfLH-1hCjCK0rsR-000u74 for ; Mon, 08 Apr 2019 19:58:59 +0200 Date: Mon, 8 Apr 2019 19:58:23 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: r346025: ZFS filesystems do not mount anymore Message-ID: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:YAchi0rd+G51QdVLG4BzGIxMR3UVpm8ANVZ/yP1ejMmn0+g2Fqb FsevqRxTn2l8LkqaMqcg60/D0ewMa28wLLFAGZWUeMXseOgBVHfCxIPT0Tu/p00MCj+LDsi zCv85HvhvGWPGNl3yX1Pad5OGHrWyiNuUv5pF8i91/JedtXoXs2XkSkOwR8L1WJgJQvroLV 1QcNYXkMLzHg+MbzuLimw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:lhi/Sn6pJMw=:MvbAKvIzNkWxpewp7UcB0v /t3uJcmZAT8zDxJY/tGQtXV+xLnnYY7EtxXWw404gBtyYvgd/V+QqZzWdDEGr5+zNHKnR0BI9 /lSTxPTl8RZo7VI3Uqk3CWM0CfIL1nVVedMt6gvtveWx9wWRO/zK8aTO1QWipfsVC1SRO/nLh sPv7KT8XlyIoc+Jh3HVx6hZ51aeHXXZG8xCTzutKkT+kpP8m6UVq9cobwxxIGLNfK7hkJ3Hsm IzrDGSN+TXhyEJjsXeNx7O6CABP5n/8ib+nV4TrVjtgTKYsjqimDLQbLlw1MD7U+Fug78jyUn ZogEsErVp2JaZAPlNMAE8DvH8M+wkDU5p4hs96XCVyXJ7/iuUqns/yid102o1qL+ggaB98l3a SOSlem5VdROc4nF4it0xcoH2gJ0q82oTqduRtN+kRo1qzJzCgVALZOOGteFA5kZM1tfGPY7aM FVapLYH0HWlJIVu2m2GQCdy7hehsEO2uw5ge2duJnWEqsgrO2hkjNFvkOq9QAIp4AqLOvGpHQ Nph5K1cpEaMVkCZux3vvptiVzYipwb6UOdbxamj3me78QZUqMgCDgPWRiz7Arqumq2IXZktHU scBJBYwww6FAKUljlIKepI91f9sW37dP9ux1P0DoqP/X7P6QVGtdkHGphlay93nh9v+EOac3Z eNI3/cAB8JGjwlh9HB2U4oNIgY8fWyWDgEqBj+SzQlYTy3uPjcPNWhT5wqbsp+dH6xU16roK5 pXzx87FDg1RawKfRWb1m77x5sc/R0w28klwDu5NMmYOPPiR4V9qFS7VfpIM6t1QU4TWHPRUT8 qa64FzmLd6mOoWlzj+MnePzBlbGgoZll8VkEp7VASaqsqBPuF2BhlHF+pIvZfrMyZq4d1qqZk nuqtWVPXdMWI+FOYZycdW0ZCENXQoLSkWcbeiiC5V1yqD6HZo+oaML6KXzdi5gjuOXzPFtRCD XT8BhxOvlHw== X-Rspamd-Queue-Id: 2C8C783F13 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.net header.s=badeba3b8450 header.b=dJIPJ6Zk X-Spamd-Result: default: False [-4.41 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmx.net:+]; MIME_BASE64_TEXT(0.10)[]; MX_GOOD(-0.01)[mx00.gmx.net,mx01.gmx.net]; NEURAL_HAM_SHORT(-0.78)[-0.777,0]; RCVD_IN_DNSWL_LOW(-0.10)[18.15.227.212.list.dnswl.org : 127.0.3.1]; RECEIVED_SPAMHAUS_PBL(0.00)[119.81.11.77.zen.spamhaus.org : 127.0.0.11]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; IP_SCORE(-1.32)[ip: (-6.76), ipnet: 212.227.0.0/16(-1.38), asn: 8560(1.54), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmx.net:s=badeba3b8450]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt.org]; RCPT_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Mailman-Approved-At: Mon, 08 Apr 2019 18:39:09 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Apr 2019 17:59:02 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMjU2DQoNCkhlbGxv LA0KDQphZnRlciBhIGJ1bmNoIG9mIHVwZGF0ZXMgdGhpcyB3ZWVrZW5kLCBtb3VudGluZyBaRlMg ZmlsZXN5c3RlbXMgb24gQ1VSUkVOVCByMzQ2MDI1IGRvZXNuJ3QNCndvcmsgYW55bW9yZSBhdCBi b290IHRpbWUgd2hlbiBaRlMgaXMgYnVpbHQtaW4ta2VybmVsLiB6ZnNfZW5hYmxlPSJZRVMiIGlz IHNldCBpbiAvZXRjL3JjLmNvbmYuDQoNCkFmdGVyIHRoZSBzeXN0ZW0gaGFzIGJvb3RlZCwgbW91 bnRpbmcgYWxsIFpGUyBmaWxlc3lzdGVtcyB2aWEgInpmcyBtb3VudCAtYSIgb3BlcmF0ZXMgYXMN CmV4cGVjdGVkIGFuZCBhbGwgZmlsZXN5c3RlbXMgYXJlIGF2YWlsYWJsZSBhcyB1c3VhbC4NCg0K S2luZCByZWdhcmRzLA0KDQpvaA0KDQoNCi0gLS0gDQpPLiBIYXJ0bWFubg0KDQpJY2ggd2lkZXJz cHJlY2hlIGRlciBOdXR6dW5nIG9kZXIgw5xiZXJtaXR0bHVuZyBtZWluZXIgRGF0ZW4gZsO8cg0K V2VyYmV6d2Vja2Ugb2RlciBmw7xyIGRpZSBNYXJrdC0gb2RlciBNZWludW5nc2ZvcnNjaHVuZyAo wqcgMjggQWJzLiA0IEJEU0cpLg0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCg0KaUhV RUFSWUlBQjBXSVFTeThJQnhBUERrcVZCYVRKNDROMVpaUGJhNVJ3VUNYS3VMMmdBS0NSQTROMVpa UGJhNQ0KUjF4ckFQOXN1N0oycVNRSWdOaVFsTUZzc3kwVml3ZUxCNElialAwNUZBTzNBenlWNVFF QXkrY2RxQ0YwTFZxUQ0KUGRNZGZPS0ZwK1U4RnFBVW4ydE9PRHBXcVRobVhBbz0NCj1kZkdjDQot LS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg== From owner-freebsd-current@freebsd.org Mon Apr 8 19:14:26 2019 Return-Path: Delivered-To: freebsd-current@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 A5B9A1565E88 for ; Mon, 8 Apr 2019 19:14:26 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-ed1-f68.google.com (mail-ed1-f68.google.com [209.85.208.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3B0187FBD for ; Mon, 8 Apr 2019 19:14:25 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: by mail-ed1-f68.google.com with SMTP id w3so3533290edu.10 for ; Mon, 08 Apr 2019 12:14:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HVGh0HjfQnIm6OKitmZVOoZOQJwYiqyr48UXY4tf30A=; b=G62ZnLkvUIpWrRJNJtB07VtOUY/QtzeyHCMJ2wUrWdhLLBFIxKka++aCYPFUTJg9sb m8ayz/cA924e7ZXZ3GGEgVt/HhpHyDHNxPecQTKfNHUGOYxI48a+KAqWKxjF5tlCObz7 04Y3lJaPSgqwjRWZ5JjYOwWdWEnyglO3/DY6jeVtZHrVkL5UvWQnZYyGw6aIGsQnd25I AcETRavDUsP21nJiJrX6xDnOCx77r8BmlCvbQxQ5Szw0fUGKt+w/omd6s5r81i76e6/I /sY20pAUBzhywTtHvGrGaivBHkYcQzrUREO3evdrSXwitSzbbn/S1KfhKaGa/Atfkioi UJLA== X-Gm-Message-State: APjAAAWr5g8L2aAp39aMjTUwNzoDRiq6ba/e7xEqO912G4ije8j1oAbf 149HhQKhhD+K31xgkyMgt4CQoDkCnz89XoEJ1kE= X-Google-Smtp-Source: APXvYqz0h61iAVFy/e4Oifg87fqaYIiEBDwuZcCR/bKwIYkNWtH73Sz2OTN6t5SqGIZcNVlodbg51qtmw5aE1q/gPzM= X-Received: by 2002:aa7:d6cb:: with SMTP id x11mr19322825edr.85.1554750365468; Mon, 08 Apr 2019 12:06:05 -0700 (PDT) MIME-Version: 1.0 References: <20190408082529.GN1923@kib.kiev.ua> <5e53428e-f557-9d7d-03f0-e07a5fbbed57@vishwin.info> In-Reply-To: <5e53428e-f557-9d7d-03f0-e07a5fbbed57@vishwin.info> From: Antoine Brodin Date: Mon, 8 Apr 2019 21:05:53 +0200 Message-ID: Subject: Re: Kernel regression in head, now unusable for package building To: Charlie Li Cc: Konstantin Belousov , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: A3B0187FBD X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of antoinebrodinfreebsd@gmail.com designates 209.85.208.68 as permitted sender) smtp.mailfrom=antoinebrodinfreebsd@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.76)[-0.765,0]; FORGED_SENDER(0.30)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.18), country: US(-0.06)]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_NEQ_ENVFROM(0.00)[antoine@freebsd.org,antoinebrodinfreebsd@gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[68.208.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_CC(0.00)[gmail.com] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Apr 2019 19:14:26 -0000 On Mon, Apr 8, 2019 at 8:36 PM Charlie Li wrote: > Konstantin Belousov wrote: > > On Mon, Apr 08, 2019 at 12:10:23AM +0200, Antoine Brodin wrote: > >> There seems to be a kernel regression in head, that happened > >> somewhere between r343921 and r345991. > >> When launching "poudriere bulk -a", the ssh session is terminated > >> when poudriere attempts to clone/start builders (tmpfs mounts, file > >> copying...), the jails don't start and the consequence is that we > >> can't build any package. > > Are there any more details about the issue ? It is not clear, does the > > machine survives the event, i.e. did kernel paniced, what are the console > > messages, any more details that you can provide. > > > I just ran into this both on a remote machine and the laptop I'm typing > on right now. At least the reference jail does start and run, as any > subsequent poudriere-bulk(8) invocations detect it. The entire login > session is killed in the process, and the only clue of anything I can > find (at least in the syslog) is that ntpd exits with Hangup: > > Apr 8 14:12:27 ardmore ntpd[74109]: ntpd exiting on signal 1 (Hangup) > > This seems to happen randomly, but still quite often. Restarting ntpd > can help, though ntpd can still exit and kill the login again. Without > ntpd running, running poudriere-bulk(8) is guaranteed to kill the login. It should be fixed in https://svnweb.freebsd.org/changeset/base/346029 Antoine From owner-freebsd-current@freebsd.org Tue Apr 9 08:06:20 2019 Return-Path: Delivered-To: freebsd-current@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 022191578841 for ; Tue, 9 Apr 2019 08:06:20 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 657FF81563 for ; Tue, 9 Apr 2019 08:06:19 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTP id x3986C1k050540 for ; Tue, 9 Apr 2019 10:06:12 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id x3986CHD050537 for ; Tue, 9 Apr 2019 10:06:12 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 9 Apr 2019 10:06:12 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore In-Reply-To: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> Message-ID: References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 08:06:20 -0000 On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello, > > after a bunch of updates this weekend, mounting ZFS filesystems on CURRENT r346025 doesn't > work anymore at boot time when ZFS is built-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. > > After the system has booted, mounting all ZFS filesystems via "zfs mount -a" operates as > expected and all filesystems are available as usual. I blame r346017: Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. Setting hostid: 0xf9071336. interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs Starting file system checks: Mounting local filesystems:. interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs ELF ldconfig path: /lib /usr/lib /usr/lib/compat 32-bit compatibility ldconfig path: /usr/lib32 [...] Creating and/or trimming log files. Starting syslogd. Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/security: No such file or directory Setting date via ntp. 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset -0.992370 sec No core dumps found. Clearing /tmp (X related). Updating motd:. Mounting late filesystems:mount: /usr/compat/linux: No such file or directory mount: /usr/compat/linux: No such file or directory mount: /usr/compat/linux: No such file or directory mount: /usr/compat/linux: No such file or directory . Mounting /etc/fstab filesystems failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Enter full pathname of shell or RETURN for /bin/sh: root@freebsd-head-zfs:/ # zfs mount -av root@freebsd-head-zfs:/ # mount -al root@freebsd-head-zfs:/ # exit Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. Setting hostid: 0xf9071336. interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs Fast boot: skipping disk checks. Mounting local filesystems:. interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs interface zfsctrl.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/zfs.ko - unsupported file type kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. /etc/rc: WARNING: Unable to load kernel module zfs ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE 32-bit compatibility ldconfig path: /usr/lib32 [...] Once I manually mount the remaining filesystems, multiuser boot proceeds as expected. My kernel has options ZFS, and the boot scripts doesn't account for this scenario. -- Trond. From owner-freebsd-current@freebsd.org Tue Apr 9 08:42:51 2019 Return-Path: Delivered-To: freebsd-current@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 B2B0C1579EC8 for ; Tue, 9 Apr 2019 08:42:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1ADEE833C7 for ; Tue, 9 Apr 2019 08:42:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTP id x398glIk050737 for ; Tue, 9 Apr 2019 10:42:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id x398glUo050734 for ; Tue, 9 Apr 2019 10:42:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 9 Apr 2019 10:42:47 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore In-Reply-To: Message-ID: References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 08:42:51 -0000 On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote: > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > Hello, > > > > after a bunch of updates this weekend, mounting ZFS filesystems on CURRENT r346025 doesn't > > work anymore at boot time when ZFS is built-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. > > > > After the system has booted, mounting all ZFS filesystems via "zfs mount -a" operates as > > expected and all filesystems are available as usual. > > I blame r346017: > > Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > Setting hostid: 0xf9071336. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > Starting file system checks: > Mounting local filesystems:. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > ELF ldconfig path: /lib /usr/lib /usr/lib/compat > 32-bit compatibility ldconfig path: /usr/lib32 > > [...] > > Creating and/or trimming log files. > Starting syslogd. > Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/security: No such file or directory > Setting date via ntp. > 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset -0.992370 sec > No core dumps found. > Clearing /tmp (X related). > Updating motd:. > Mounting late filesystems:mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > . > Mounting /etc/fstab filesystems failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Enter full pathname of shell or RETURN for /bin/sh: > root@freebsd-head-zfs:/ # zfs mount -av > root@freebsd-head-zfs:/ # mount -al > root@freebsd-head-zfs:/ # exit > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > Setting hostid: 0xf9071336. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > Fast boot: skipping disk checks. > Mounting local filesystems:. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE > 32-bit compatibility ldconfig path: /usr/lib32 > > [...] At a later point, this happens: Starting syslogd. usage: protect [-i] command protect [-cdi] -g pgrp | -p pid Setting date via ntp. It looks like syslogd is no longer protected against the OOM killer. > Once I manually mount the remaining filesystems, multiuser boot > proceeds as expected. My kernel has options ZFS, and the boot scripts > doesn't account for this scenario. -- Trond. From owner-freebsd-current@freebsd.org Tue Apr 9 13:31:38 2019 Return-Path: Delivered-To: freebsd-current@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 2F4001581329 for ; Tue, 9 Apr 2019 13:31:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3668D693 for ; Tue, 9 Apr 2019 13:31:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554816620; bh=UntC4PAh1wgBVc+Z3L7kx/8qbrgHIt41UHi6X7qTpRo=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References; b=dYQJ5r7CZc0ugEHtQaDJ19KOzjDCSeEPEgVNvCak0artKDbjb+OnQx2CJP63enAy1 yOv1hvjevqjrB8S8Vr/UDBXDQIk4lKqhtHhIFZglQtDEiXlMdZL8YM0B44jSlmCy3W r4rKsdA/2uVBUKduBBom1otq7Iis2zX8xmtq042A= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from freyja ([46.88.91.252]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LaFmY-1gSzD80nGA-00m6FW; Tue, 09 Apr 2019 15:30:20 +0200 Date: Tue, 9 Apr 2019 15:30:18 +0200 From: "O. Hartmann" To: Trond =?ISO-8859-1?Q?Endrest=F8l?= Cc: FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore Message-ID: <20190409153014.5299494e@freyja> In-Reply-To: References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:k/zU48DkXdCAFVAr8Z3KXOK3VGJiZEyf8UWJDCbQksBiqL+Mk+z k/5PAeAFxLwFrJ3mYS33sOKybHiRx4Za8wxthOV7z+F5/ewmgGmc2TDRb5FiC2me0Kj3e/R Elrw0KEhvxpjJCqBrijuPkxGbGvS2tosupfbg0zkLcnrMvXoLGPuk08Be9RjUU9mPvqP0FC jhDzbyYWieqRwDq/oQI/Q== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:IEzv/CFQXtE=:qefXOQe1SsaAMMCTSsTdPO w/T7qNhKfZOZrnBsZ+XabZo/rs/7U4/ETMyC0JfYWnKS+qyjfskjdxMXu5oR72oNEID/xsDFb 7A16CMm4OZDiZU/SP+057v9sDC0TVxKVMA4+mIbnvRMeyAETK7oJfu5KPIRzuoBqm7CYydZ01 JwcYXon/u3CdfNioC7ZKmfid877ihFDqDh+BDhBr43ILHbCUmfiMH9zFgYwT8kocsAc02LENv P3cLPFPUvv7QNNnpR69fIKzUYDWKbjgep4kG/hnTDXSjp8CnN6Ollk5kbUO46TfotdV6bgNUg UgoWZm8T3JnpSQePluEIrcyqWsZfiFNxHJXYOSPUfWM2p7dzleLuGZFIQ4CSguQ4feaDQgQJ2 0EcQ1ugqEQ4Xyn9CtlU9zwJnbaTinhA6k8eb6ZacAirqqimhylP4QQmTLFO8Q592u0h2O7Qzw oPxlTRbEF1oNwZmmEMdAo+GX05myEZIdPNcSs8rQB0YgFLQAHgFnBevTGT4JVSdIe1QaFtQ7p Q3glTGfm91niq1EJQIFf2RXogz2Pe0ZGSKtP17gHI2ctppsk84KV8EFwWTfaLtyIUotbyp9m1 t9yWZTiVyTisF1r6fV5NEQRuuSKRu6AhTUxhbYVJxw9f+y5/wjBYN0haOTFQaUglHxRjW+nTi 7hCtM9VhqufBPM78WrAI4GTeNZuLwOmbx0/SwhReoLhiSDmXVFKxum2nhlYK1Q1SB9txgO375 EmB2joQLh0ABhQstKIenHU0US5vH/q7dDXmCWUUJpLhkooS9bSm5W+952aD4uEXQFhNwvHxFO FMv84K/NBnoE41+/1jtHp5ue32HMHE6APup+jJ4GSqSVV9W71slIwNJettiJVvAEsFapoGgYT yVFZvBCrc7R34MIpzMAR0NHQRgksEsr70m8vh3UVobMN9ab0er6jVVSZQnAwI8gWA01RRjvaS yhwslpt5n+Q== X-Rspamd-Queue-Id: 9B3668D693 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 13:31:38 -0000 On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) Trond Endrest=F8l wrote: > On Tue, 9 Apr 2019 10:06+0200, Trond Endrest=F8l wrote: >=20 > > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > > =20 > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > >=20 > > > Hello, > > >=20 > > > after a bunch of updates this weekend, mounting ZFS filesystems on > > > CURRENT r346025 doesn't work anymore at boot time when ZFS is > > > built-in-kernel. zfs_enable=3D"YES" is set in /etc/rc.conf. > > >=20 > > > After the system has booted, mounting all ZFS filesystems via "zfs mo= unt > > > -a" operates as expected and all filesystems are available as usual. = =20 > >=20 > > I blame r346017: > >=20 > > Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] > > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > > Setting hostid: 0xf9071336. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > Starting file system checks: > > Mounting local filesystems:. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > ELF ldconfig path: /lib /usr/lib /usr/lib/compat > > 32-bit compatibility ldconfig path: /usr/lib32 > >=20 > > [...] > >=20 > > Creating and/or trimming log files. > > Starting syslogd. > > Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/securit= y: > > No such file or directory Setting date via ntp. > > 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset > > -0.992370 sec No core dumps found. > > Clearing /tmp (X related). > > Updating motd:. > > Mounting late filesystems:mount: /usr/compat/linux: No such file or > > directory mount: /usr/compat/linux: No such file or directory > > mount: /usr/compat/linux: No such file or directory > > mount: /usr/compat/linux: No such file or directory > > . > > Mounting /etc/fstab filesystems failed, startup aborted > > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > > Enter full pathname of shell or RETURN for /bin/sh: > > root@freebsd-head-zfs:/ # zfs mount -av > > root@freebsd-head-zfs:/ # mount -al > > root@freebsd-head-zfs:/ # exit > > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > > Setting hostid: 0xf9071336. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > Fast boot: skipping disk checks. > > Mounting local filesystems:. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > ELF ldconfig > > path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compa= t/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE > > 32-bit compatibility ldconfig path: /usr/lib32 > >=20 > > [...] =20 >=20 > At a later point, this happens: >=20 > Starting syslogd. > usage: protect [-i] command > protect [-cdi] -g pgrp | -p pid > Setting date via ntp. >=20 > It looks like syslogd is no longer protected against the OOM killer. >=20 > > Once I manually mount the remaining filesystems, multiuser boot=20 > > proceeds as expected. My kernel has options ZFS, and the boot scripts=20 > > doesn't account for this scenario. =20 >=20 >=20 Hello, thank you for investigating! I think you're correct. I was wondering how th= is change could make it into the tree with this kind of impact. Maybe filing a PR would be fine? Kind regards, oh From owner-freebsd-current@freebsd.org Tue Apr 9 17:37:45 2019 Return-Path: Delivered-To: freebsd-current@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 AEC051566B4F for ; Tue, 9 Apr 2019 17:37:45 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E0A16FCFE for ; Tue, 9 Apr 2019 17:37:45 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Received: from privacychain.ch (unknown [179.54.99.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: rigoletto) by smtp.freebsd.org (Postfix) with ESMTPSA id 9474CEE46 for ; Tue, 9 Apr 2019 17:37:44 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Date: Tue, 9 Apr 2019 14:37:42 -0300 From: Alexandre =?utf-8?Q?C=2E_Guimar=C3=A3es?= To: freebsd-current@FreeBSD.org Subject: ZFS: can't read MOS of zpool... Message-ID: <20190409173742.n65wbq5hhnpej7zc@privacychain.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="in6wvv5bxpdendg5" Content-Disposition: inline User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: 4E0A16FCFE X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; NEURAL_HAM_SHORT(-0.97)[-0.972,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 17:37:45 -0000 --in6wvv5bxpdendg5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I can't say the precise point this started but I am convinced that was right after running `zpool upgrade` after upgrading to 12-RELEASE: --- ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zdata --- So, I got another disk to substitute that one, and now I have the same message two times. :-( https://ibb.co/G0sfv3p I suppose that would be very unfortunate to have the same problem in two completely unrelated disks at the same time; however, that error don't occurs with the SSD. Both disks pools were created raw, however I've tried to do using GPT, MBR, and I got the same error messages. --- ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ACS-2 ATA SATA 3.x device ada0: Serial Number 1838DB806764 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada0: Command Queueing enabled ada0: 114480MB (234455040 512 byte sectors) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA8-ACS SATA 2.x device ada1: Serial Number S22KJ56S906708 ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 305245MB (625142448 512 byte sectors) ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: ATA8-ACS SATA 2.x device ada2: Serial Number TNS519GY1G75LG ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 476940MB (976773168 512 byte sectors) --- What more information would be useful? :-) Thank you! :-) --=20 Best Regards, Alexandre C. Guimar=C3=A3es. https://bitbucket.org/rigoletto-freebsd/ --in6wvv5bxpdendg5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE9RbDjoZ0ELBWamGCmSH8wDhAF9kFAlys2GBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 MTZDMzhFODY3NDEwQjA1NjZBNjE4Mjk5MjFGQ0MwMzg0MDE3RDkACgkQmSH8wDhA F9k3cxAAxH7Pt7txtevIaZt0Bos62wNvA3aMzDJfpUwzHgmgvuo5rkfogFPPDa57 iC4Xomb1Z6zizNBkx3poYzv/+otKkqR6cCTfWaTkjZ7gBTCFAPPztXFnABdZ50uZ XP2czy4AXwEIkkZvssC2vx/1te8NjYZ9rizkGCwid/hKWoPGMdEnBc/LFIYU/uLZ fYRTxoUVa3fe2JPloDygs1PvWVhIR+d7upBYIBh45rTuKpPwGRGlEC4QcktFQF8X sXKVgC2qzuLxrdSe+2OYDoAnZcEqynpetsVbYXmKHSNKQuw5E0tPtA2JwdYe712m yCWXYOkcec0ijlU/MYLVYirckhD/TfAe2WYdFbwjIKEwtKCNgaK9RfQhJiVg5SAu 8NetzHzrqlbN1DckMsWm7gYPNYuYYrCrXTgAG8pfYI5jvcOqAzNZumlD2gWTbJwv VAEGGCwKeOATUd4BMH7cOz/TisnkXNj7cXEdk8fP2mh7F93oxXtPuqjKSaHf8gk2 +kxAEt0YG8oyqwIGBE4f1GyuyGD09+Yy0ZERpjE52w7IC6MhCcmTpJz0REv2B/ea E0S3mNumdIePFgNHfjhdqP8v29KbxbKTZkVN+dU7VCvRXtGB9ZOANeX3NE+Tetv9 usknuDg40sM/a6qopSXxz8ZypUvR440FNa4JSHlB/LAkM80FptU= =5OBG -----END PGP SIGNATURE----- --in6wvv5bxpdendg5-- From owner-freebsd-current@freebsd.org Tue Apr 9 17:43:51 2019 Return-Path: Delivered-To: freebsd-current@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 7DD641567049 for ; Tue, 9 Apr 2019 17:43:51 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021901.me.com (pv50p00im-ztdg10021901.me.com [17.58.6.55]) (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 8355E70410 for ; Tue, 9 Apr 2019 17:43:49 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021901.me.com (Postfix) with ESMTPSA id BB9EA880326; Tue, 9 Apr 2019 17:43:40 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: ZFS: can't read MOS of zpool... From: Toomas Soome In-Reply-To: <20190409173742.n65wbq5hhnpej7zc@privacychain.ch> Date: Tue, 9 Apr 2019 20:43:38 +0300 Cc: "freebsd-current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <823B600C-5EE4-4916-ABBB-A8B7E720843D@me.com> References: <20190409173742.n65wbq5hhnpej7zc@privacychain.ch> To: =?utf-8?Q?=22Alexandre_C=2E_Guimar=C3=A3es=22?= X-Mailer: Apple Mail (2.3445.104.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-09_08:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1904090112 X-Rspamd-Queue-Id: 8355E70410 X-Spamd-Bar: ------- X-Spamd-Result: default: False [-7.36 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; MX_GOOD(-0.01)[mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, m x6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.co m, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud .com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icloud.com, mx6.mail.icloud.com, mx4.mail.icloud.com, mx5.mail.icloud.com, mx2.mail.icloud.com, mx3.mail.icloud.com, mx1.mail.icl oud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com,mx1.mail.icloud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com,mx1.mail.icloud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com,mx1.mail.icloud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com,mx1.mail.icloud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com,mx1.mail.icloud.com,mx6.mail.icloud.com,mx4.mail.icloud.com,mx5.mail.icloud.com,mx2.mail.icloud.com,mx3.mail.icloud.com]; NEURAL_HAM_SHORT(-0.97)[-0.970,0]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.zen.spamhaus.org : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[55.6.58.17.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=04042017]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.78)[ip: (-9.59), ipnet: 17.58.0.0/20(-2.15), asn: 714(-2.13), country: US(-0.06)]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 17:43:51 -0000 When did you update the bootblocks last time? You can grab iso/usb image with current and check if loader there can = see your pools - and if yes, update the boot blocks on disk=E2=80=A6 rgds, toomas > On 9 Apr 2019, at 20:37, Alexandre C. Guimar=C3=A3es = wrote: >=20 > Hello, >=20 > I can't say the precise point this started but I am convinced that was > right after running `zpool upgrade` after upgrading to 12-RELEASE: >=20 > --- > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zdata > --- >=20 > So, I got another disk to substitute that one, and now I have the same > message two times. :-( >=20 > https://ibb.co/G0sfv3p >=20 > I suppose that would be very unfortunate to have the same problem in = two > completely unrelated disks at the same time; however, that error don't > occurs with the SSD. >=20 > Both disks pools were created raw, however I've tried to do using GPT, = MBR, > and I got the same error messages. >=20 > --- > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ACS-2 ATA SATA 3.x device > ada0: Serial Number 1838DB806764 > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada0: Command Queueing enabled > ada0: 114480MB (234455040 512 byte sectors) > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ATA8-ACS SATA 2.x device > ada1: Serial Number S22KJ56S906708 > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 305245MB (625142448 512 byte sectors) > ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 > ada2: ATA8-ACS SATA 2.x device > ada2: Serial Number TNS519GY1G75LG > ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada2: Command Queueing enabled > ada2: 476940MB (976773168 512 byte sectors) > --- >=20 > What more information would be useful? :-) >=20 > Thank you! :-) >=20 > --=20 > Best Regards, > Alexandre C. Guimar=C3=A3es. > https://bitbucket.org/rigoletto-freebsd/ From owner-freebsd-current@freebsd.org Tue Apr 9 17:47:49 2019 Return-Path: Delivered-To: freebsd-current@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 31599156726D for ; Tue, 9 Apr 2019 17:47:49 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from dnvrco-cmomta03.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE1BA7068D for ; Tue, 9 Apr 2019 17:47:43 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from bashful.bsd1.net ([74.138.140.144]) by cmsmtp with ESMTPA id DuiGhoYWYWnTiDuiJhO71w; Tue, 09 Apr 2019 17:39:16 +0000 Message-ID: <1dcf7e732f3e7e56785be72b661d3f0b8050ffa7.camel@twc.com> Subject: lsof hangs with latest 13.0-CURRENT snapshot From: David Boyd To: freebsd-current@freebsd.org Date: Tue, 09 Apr 2019 13:39:12 -0400 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfFll87sM6qshMFHOO6mnaHkBYohokSVzRdJNaHzlbGkkH9VaHLyACa0jeb7aQxrVRePf9P7r29rurMIREEGIgaqgrUemf3tGaxlJdhPqbFDKMeveZ0GE jVwIgK/oNIRRKCilJkuM9M2DpwnrODcZpdV6xnTL28tLMPZAo+9c1RRtY5GzRaR/iiKrxxX0mV9J/Q== X-Rspamd-Queue-Id: CE1BA7068D X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of david.boyd49@twc.com designates 107.14.73.232 as permitted sender) smtp.mailfrom=david.boyd49@twc.com X-Spamd-Result: default: False [-4.09 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[twc.com]; R_SPF_ALLOW(-0.20)[+ip4:107.14.73.0/24]; MV_CASE(0.50)[]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[dnvrco-cmedge02.email.rr.com,dnvrco-cmedge01.email.rr.com]; NEURAL_HAM_SHORT(-0.91)[-0.908,0]; RECEIVED_SPAMHAUS_PBL(0.00)[144.140.138.74.zen.spamhaus.org : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; ASN(0.00)[asn:7843, ipnet:107.14.73.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-1.38)[ipnet: 107.14.73.0/24(-3.81), asn: 7843(-3.05), country: US(-0.06)]; DMARC_NA(0.00)[twc.com]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[232.73.14.107.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 17:47:49 -0000 After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from packages) hangs. This is true for bare metal installs and virtual machine installs. How to recreate: Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. as root: lsof /sbin/init By running command with -b option, this error is displayed: lsof: status error on /sbin/init: Resource temporarily unavailable The return code is 1. This probably requires adjustment to lsof, but only the FreeBSD snapshot changed, so I'll start here. Thanks. David Boyd. From owner-freebsd-current@freebsd.org Tue Apr 9 19:02:33 2019 Return-Path: Delivered-To: freebsd-current@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 CCE6615696EC for ; Tue, 9 Apr 2019 19:02:33 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BFA9732E2 for ; Tue, 9 Apr 2019 19:02:33 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Received: from privacychain.ch (unknown [179.54.99.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: rigoletto) by smtp.freebsd.org (Postfix) with ESMTPSA id AD4F7F83D for ; Tue, 9 Apr 2019 19:02:32 +0000 (UTC) (envelope-from rigoletto@FreeBSD.org) Date: Tue, 9 Apr 2019 16:02:31 -0300 From: =?utf-8?Q?=22Alexandre_C=2E_Guimar=C3=A3es=22?= To: freebsd-current@freebsd.org Subject: Re: ZFS: can't read MOS of zpool... Message-ID: <20190409190231.gqfhq4awus2y7hj6@privacychain.ch> References: <20190409173742.n65wbq5hhnpej7zc@privacychain.ch> <823B600C-5EE4-4916-ABBB-A8B7E720843D@me.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="v7qvsbyzydwdjisa" Content-Disposition: inline In-Reply-To: <823B600C-5EE4-4916-ABBB-A8B7E720843D@me.com> User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: 5BFA9732E2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 19:02:34 -0000 --v7qvsbyzydwdjisa Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I don't get those messages when booting from the installation media, all disks are apparently showing up correctly from `gpart list` from there, and I updated the bootblocks: --- # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 --- however the error messages still do persist on the installed system. Do I forgot and am not aware of anything? Thank you. On Tue, Apr 09, 2019 at 08:43:38PM +0300, Toomas Soome wrote: >=20 > When did you update the bootblocks last time? >=20 > You can grab iso/usb image with current and check if loader there can see= your pools - and if yes, update the boot blocks on disk=E2=80=A6 >=20 > rgds, > toomas >=20 > > On 9 Apr 2019, at 20:37, Alexandre C. Guimar=C3=A3es wrote: > >=20 > > Hello, > >=20 > > I can't say the precise point this started but I am convinced that was > > right after running `zpool upgrade` after upgrading to 12-RELEASE: > >=20 > > --- > > ZFS: i/o error - all block copies unavailable > > ZFS: can't read MOS of pool zdata > > --- > >=20 > > So, I got another disk to substitute that one, and now I have the same > > message two times. :-( > >=20 > > https://ibb.co/G0sfv3p > >=20 > > I suppose that would be very unfortunate to have the same problem in two > > completely unrelated disks at the same time; however, that error don't > > occurs with the SSD. > >=20 > > Both disks pools were created raw, however I've tried to do using GPT, = MBR, > > and I got the same error messages. > >=20 > > --- > > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > > ada0: ACS-2 ATA SATA 3.x device > > ada0: Serial Number 1838DB806764 > > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > > ada0: Command Queueing enabled > > ada0: 114480MB (234455040 512 byte sectors) > > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > > ada1: ATA8-ACS SATA 2.x device > > ada1: Serial Number S22KJ56S906708 > > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > > ada1: Command Queueing enabled > > ada1: 305245MB (625142448 512 byte sectors) > > ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 > > ada2: ATA8-ACS SATA 2.x device > > ada2: Serial Number TNS519GY1G75LG > > ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > > ada2: Command Queueing enabled > > ada2: 476940MB (976773168 512 byte sectors) > > --- > >=20 > > What more information would be useful? :-) > >=20 > > Thank you! :-) > >=20 > > --=20 > > Best Regards, > > Alexandre C. Guimar=C3=A3es. > > https://bitbucket.org/rigoletto-freebsd/ >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --=20 Best Regards, Alexandre C. Guimar=C3=A3es. https://bitbucket.org/rigoletto-freebsd/ --v7qvsbyzydwdjisa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE9RbDjoZ0ELBWamGCmSH8wDhAF9kFAlys7EdfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 MTZDMzhFODY3NDEwQjA1NjZBNjE4Mjk5MjFGQ0MwMzg0MDE3RDkACgkQmSH8wDhA F9nVvw/+O+TOx6iVzJoXqgs5cZSbcX6V2HUXbogZ0sBrAWLKCoGXg3lFuCjM8o5S yduApckxVxgm20GjNus0Qn0OQxrb21AD+wIiyjbvFc9Vi5pfYVUoyNEHTsWleewU OC5r3VZ+TDre+FrDRniCAa5uAmnwOGZ5agDyCYWCyUZgWKm/SW9/ZIqZ1C6uQJrD A0SN7iNZQGBLdz2d/fT8X5VGgNpR4Uhwjw/udq+HispKBWa8bcvNU+ZqK15Ams5n r1XZd0z78T1Rwso3pUkYtJdiPW9hIwCmZYbDx1Lqv6eAQ6gMR9wHPifSe5u+SbVB 4C/FQhE5qKR3y14j9kEGM1A/RQlEuDwV34pWGcsjaK9COctQB3llw8IiUaMRxtMk AqC1mBFCG8u76rMoCN90YBMt9RqcAubKrrkhowGpIxwA2b/pXVAwtDzbTOKKe3kA eKVrHT6ZdeIEUfNPlGp/sOuWLIbbGE9ilUT14E0JA42zdB/Z1LWf3wyydd4pVjhS jRXO2anyAHrXc4k4MdNYc4EzVzJg2uAQxykPXExdWDCDAHRPmTcFnQNabU6qGxgU WvGS/vLOEL8ZGjn7oHS4rDb0o/QvJdXOspmqHIGHzXsnAO3Y1tJiTLoCaMSucfBU 5jAjecaJbSZWM0WEZIpwy7n/XfdCfLE6Ioz8iaaE8zPf8KJJzqE= =UQX7 -----END PGP SIGNATURE----- --v7qvsbyzydwdjisa-- From owner-freebsd-current@freebsd.org Tue Apr 9 19:20:54 2019 Return-Path: Delivered-To: freebsd-current@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 B3438156A44B for ; Tue, 9 Apr 2019 19:20:54 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE4E77509A for ; Tue, 9 Apr 2019 19:20:53 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x39JKpBk061699; Tue, 9 Apr 2019 12:20:51 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x39JKprv061698; Tue, 9 Apr 2019 12:20:51 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904091920.x39JKprv061698@gndrsh.dnsmgr.net> Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot In-Reply-To: <1dcf7e732f3e7e56785be72b661d3f0b8050ffa7.camel@twc.com> To: David Boyd Date: Tue, 9 Apr 2019 12:20:51 -0700 (PDT) CC: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: CE4E77509A X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.99 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.59)[0.588,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.44)[0.440,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.04)[0.042,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.03)[ip: (0.12), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.04), country: US(-0.06)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 19:20:54 -0000 > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from packages) > hangs. > > This is true for bare metal installs and virtual machine installs. > > How to recreate: > > Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. > > as root: lsof /sbin/init > > By running command with -b option, this error is displayed: > > lsof: status error on /sbin/init: Resource temporarily unavailable > > The return code is 1. > > This probably requires adjustment to lsof, but only the FreeBSD > snapshot changed, so I'll start here. Where did you get your lsof binary from? lsof has internal knowledge of kernel data structures and must be compiled to match the running system. > Thanks. > David Boyd. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Apr 9 19:36:24 2019 Return-Path: Delivered-To: freebsd-current@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 DFFC6156AFC1 for ; Tue, 9 Apr 2019 19:36:23 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from dnvrco-cmomta01.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B071875CA4 for ; Tue, 9 Apr 2019 19:36:21 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from bashful.bsd1.net ([74.138.140.144]) by cmsmtp with ESMTPA id DwUwhGKbJP088DwUyh1D82; Tue, 09 Apr 2019 19:33:37 +0000 Message-ID: Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot From: David Boyd To: "Rodney W. Grimes" Cc: freebsd-current@freebsd.org Date: Tue, 09 Apr 2019 15:33:33 -0400 In-Reply-To: <201904091920.x39JKprv061698@gndrsh.dnsmgr.net> References: <201904091920.x39JKprv061698@gndrsh.dnsmgr.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfI+w2SPnPf/LCR93tl84DvzNzJVjYCgAaJpmWRocxxrLxhqvY4DWWYvBGjxyZgQviI0p7UmDWbp0GigiMFwQF9JjBRrX0u0uGE8arsMS/B75aFj/LXBW IdX9C+e5jO3VzWXEzXieKHosrR9sjcpTYwQHy1ajyk1AW89IfJj3x7mjEzNZ8ZzFmIAB9MY98ETKGbSZzgpgg3DLRqf3b2QNzSMDGuiKRgaaqtLgZQ33efXk X-Rspamd-Queue-Id: B071875CA4 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of david.boyd49@twc.com designates 107.14.73.232 as permitted sender) smtp.mailfrom=david.boyd49@twc.com X-Spamd-Result: default: False [-4.16 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.14.73.0/24]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[twc.com]; MX_GOOD(-0.01)[cached: dnvrco-cmedge02.email.rr.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; RECEIVED_SPAMHAUS_PBL(0.00)[144.140.138.74.zen.spamhaus.org : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; ASN(0.00)[asn:7843, ipnet:107.14.73.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[twc.com]; IP_SCORE(-1.37)[ipnet: 107.14.73.0/24(-3.78), asn: 7843(-3.02), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[232.73.14.107.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 19:36:24 -0000 On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > packages) > > hangs. > > > > This is true for bare metal installs and virtual machine installs. > > > > How to recreate: > > > > Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. > > > > as root: lsof /sbin/init > > > > By running command with -b option, this error is displayed: > > > > lsof: status error on /sbin/init: Resource temporarily unavailable > > > > The return code is 1. > > > > This probably requires adjustment to lsof, but only the FreeBSD > > snapshot changed, so I'll start here. > > Where did you get your lsof binary from? > > lsof has internal knowledge of kernel data structures > and must be compiled to match the running system. > > > > Thanks. > > David Boyd. lsof was installed via pkg install from pkg.freebsd.org. From owner-freebsd-current@freebsd.org Tue Apr 9 19:41:38 2019 Return-Path: Delivered-To: freebsd-current@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 609CD156B477 for ; Tue, 9 Apr 2019 19:41:38 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B276764CA for ; Tue, 9 Apr 2019 19:41:37 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x39JfYxo061790; Tue, 9 Apr 2019 12:41:34 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x39JfY49061789; Tue, 9 Apr 2019 12:41:34 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot In-Reply-To: To: David Boyd Date: Tue, 9 Apr 2019 12:41:34 -0700 (PDT) CC: "Rodney W. Grimes" , freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 8B276764CA X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-0.19 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.54)[-0.538,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.44)[-0.436,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_HAM_SHORT(-0.14)[-0.139,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.03)[ip: (0.12), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.04), country: US(-0.06)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 19:41:38 -0000 > On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > > packages) > > > hangs. > > > > > > This is true for bare metal installs and virtual machine installs. > > > > > > How to recreate: > > > > > > Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. > > > > > > as root: lsof /sbin/init > > > > > > By running command with -b option, this error is displayed: > > > > > > lsof: status error on /sbin/init: Resource temporarily unavailable > > > > > > The return code is 1. > > > > > > This probably requires adjustment to lsof, but only the FreeBSD > > > snapshot changed, so I'll start here. > > > > Where did you get your lsof binary from? > > > > lsof has internal knowledge of kernel data structures > > and must be compiled to match the running system. > > > > > > > Thanks. > > > David Boyd. > > > lsof was installed via pkg install from pkg.freebsd.org. That does not work well on ^head or for that mater any snapshot, as I said, lsof has internal knowledge of kernel data structures and must match the running kernel for it to work. It should be complaining about a version mismatch, but perhaps it was compiled recently enough that these are matching, but there is still a datastruct that changed. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Apr 9 19:44:12 2019 Return-Path: Delivered-To: freebsd-current@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 BC050156B600; Tue, 9 Apr 2019 19:44:12 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from thebighonker.lerctr.org (unknown [IPv6:2001:470:1f0f:3ad::53:2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59270766F0; Tue, 9 Apr 2019 19:44:12 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=xKM7zEMT6TCUjH28Ayz7c6e0sOg5D6IDl74g1L+Bw4s=; b=RyPmzGCfP8sYgYC7at7WqjsKS3 yZ2mcPb3TP9U4WYZbavIJ4DIV3+jT6xEjGD/EqN0Z6UBQR4GU0ptfrdnSO6C+fKsmvu8eDvfM5+0A MxPBIm7ovp0kGQhnivkH7H/EPLBVZvOLN/Pyn80O+xxki9rq9RvT6BpkpPGqxrpqpGQKgF6Hv10Jz WVjd6HnVCcE6xbWkEX+bu95W8XlJUDqwq09iUn2PLfIehKs/bOJSn1G1Z4YmiHTNn+9zg1YiZtGch 8bIR9vdoL6x//RWY/RLgcflBcmgnEAMu/nVjKzhJ2yuMJ9AfIdlinbHZmD0vV/GdeyObrRaZk+2nJ ncgQ6zMA==; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:bb:dcff:fe50:d900]:52394 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hDwf9-000IGm-M1; Tue, 09 Apr 2019 14:44:07 -0500 Received: from 2600:1700:210:b180:9950:ab98:4498:ec58 by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Tue, 09 Apr 2019 14:44:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 09 Apr 2019 14:44:07 -0500 From: Larry Rosenman To: "Rodney W. Grimes" Cc: David Boyd , freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot In-Reply-To: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> References: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> Message-ID: X-Sender: ler@FreeBSD.org User-Agent: Roundcube Webmail/1.3.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 19:44:13 -0000 On 04/09/2019 2:41 pm, Rodney W. Grimes wrote: >> On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: >> > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to >> > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from >> > > packages) >> > > hangs. >> > > >> > > This is true for bare metal installs and virtual machine installs. >> > > >> > > How to recreate: >> > > >> > > Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. >> > > >> > > as root: lsof /sbin/init >> > > >> > > By running command with -b option, this error is displayed: >> > > >> > > lsof: status error on /sbin/init: Resource temporarily unavailable >> > > >> > > The return code is 1. >> > > >> > > This probably requires adjustment to lsof, but only the FreeBSD >> > > snapshot changed, so I'll start here. >> > >> > Where did you get your lsof binary from? >> > >> > lsof has internal knowledge of kernel data structures >> > and must be compiled to match the running system. >> > >> > >> > > Thanks. >> > > David Boyd. >> >> >> lsof was installed via pkg install from pkg.freebsd.org. > > That does not work well on ^head or for that mater any snapshot, > as I said, lsof has internal knowledge of kernel data structures > and must match the running kernel for it to work. > > It should be complaining about a version mismatch, but perhaps > it was compiled recently enough that these are matching, but > there is still a datastruct that changed. As the lsof maintainer, I heartily agree here.... Compile it against your system, and if it still hangs, make me a bugzilla ticket with the details. Thanks! -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 From owner-freebsd-current@freebsd.org Tue Apr 9 22:08:09 2019 Return-Path: Delivered-To: freebsd-current@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 2EDA8156FD60 for ; Tue, 9 Apr 2019 22:08:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 022CE848A1 for ; Tue, 9 Apr 2019 22:08:07 +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 EA07625B20 for ; Tue, 9 Apr 2019 18:08:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 09 Apr 2019 18:08:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:mime-version:content-type; s= fm2; bh=YEuBTc8Nt/PznB1d+pAX52bZc10SbLcE3eAHnDi+iKs=; b=jJFk1Rt5 wTrFbEx2rcbNsZbLhhuSVFgpbWN7KruAe7o0xcfv9kxZRJbVYEXf61/PjiDfVbsl kjuxlPYUbU7DyrKj+Atls5DLReEE7gOgxiP1J4MQZGQhxeo4gwPTQ/58U1mz+esG evT8qKAiTkjG6sQpm2RpZR+zvQg2aF8dpqNh6eyWTN8/8Zxogv0K/ESgM7O7uRq4 BOhCdRZAlDjQ3qY6j5uzoEkijvlluakQS1q4DO2tSuHeMzkG34eFOokHQ4qbhf3s OblMOhZ4PAk0E99XCZU+3mzHa03InaV/vxhxXwubb8GfFMZganoB6E38AmrnBTqj 35jQBG0eCAN8Zw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=YEuBTc8Nt/PznB1d+pAX52bZc10Sb LcE3eAHnDi+iKs=; b=qjj0KMRfIiLnXpauoamwY0fJNalkX2X9cwnYpTL0XagRj eFu2GJv3EtnKmUmX9F3mpW5CqopBp4olz4NpX+E8FC2mwEO9Z30f2ljfEEpqvJlX bV/3EQTklFtkmx5UIUP+SVitQ7V8wcjRkHbkJqfuzFITpYtZDpM+GW+QNvyW16Gz jDYx94eIJrmHjLNI1OBi8izKsqRAcfyyu0nIYCb860/JkYNvsUWWkT+oxioUYWln OIVEYhx0MyQAsc9OFFYH8jNGsbvmMbLfd135KR0vI72tV1s3GywsvGHPx/o6gOqn 8n6do5Mr/g1H4PlMxaRCutu6SkKacIs2Bq14FF0wg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigddtiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggufgesghdtreertd ervdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseiihiig shhtrdhnvghtqeenucffohhmrghinhepiiihgihsthdrnhgvthenucfkphepkedvrdejtd drledurddutddunecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthhdqlhhishhtshes iiihgihsthdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 4CC8810396 for ; Tue, 9 Apr 2019 18:08:06 -0400 (EDT) Date: Tue, 9 Apr 2019 23:08:04 +0100 From: tech-lists To: freebsd-current@freebsd.org Subject: make buildkernel doesn't Message-ID: <20190409220803.GB57588@rpi3.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DBIVS5p969aUjpLe" Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 022CE848A1 X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=jJFk1Rt5; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=qjj0KMRf; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.26 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-9.10 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zyxst.net]; MX_GOOD(-0.01)[cached: in2-smtp.messagingengine.com]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; IP_SCORE(-3.41)[ip: (-9.04), ipnet: 66.111.4.0/24(-4.59), asn: 11403(-3.35), country: US(-0.06)]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 22:08:09 -0000 --DBIVS5p969aUjpLe Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, fbsd 13-current r346053 amd64 make buildkernel fails near the start here: awk -f /usr/src/sys/tools/usbdevs2h.awk /usr/src/sys/dev/usb/usbdevs -d --- genoffset.o --- cc: error: no such file or directory: 'FLAGS' *** [genoffset.o] Error code 1 more detail at https://rpi3.zyxst.net/errors/13-current/r346053/20190409-kernbuildfail.txt thanks, --=20 J. --DBIVS5p969aUjpLe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAlytF7gACgkQs8o7QhFz NAUdZRAAjUvhkqgRpP6yC0mwnm2OOG7pfqhI5ZNcv34ZekgWUaKtOYZPihhQCvRZ LMyUsC6IvZiGS8V1U5gV2LOQTXbR7B2Cn28i15Lm7JZzx48Sko3U0xr7LWV0C+Iz xRCkN061eSKKsBs+Zu53CFr5vMiB1NFtzpRJbwDVB8xw0Vyvzjca9zDZ5e2zCttd 9BGPKLxPAefFDENO87mtHQTkU3U+iZN7T5uSjNI9Dbs0qhF9BmZg6ArDKzCNrymU iVqPQDVJ7R7v4L0zOtCMRrT+l1kDCkI1AlRaBQiTJLgz1fhb7ODIAj/XUE4B39ag 9QYz+02PhlON2awHpvyIx+Kyow3vG89aiJfyXk4Pan2MZsmngHmoilDSGq1iYRa3 C7+5PsD/XfPcMN9Y3N1DjJ2XTWRt7i4EFowKQKrlVr6oykxqUGylC9hfM8V4Ap+Y u7yoQJ7ObXpbZ84hcd44a26DCjdvfx0A35Vn4pxH2C7+Gt7hFfBXn2indPZCtnas 8r5RRgJHPMl1WA7nJKgT/ZlsGzY0w5e/U1MFr03vSZBbWibH7OGgRRec1zl3Krtb 3D9tAKogJVPI/xZWn04McEMCrDLcnoe4Zo4bNXnyRQhhjJwUGB/jMIdCTGqRfSAT fGnBof9EADqe2Zb8SBd48LdXlnYOE7BRwMzt9rOOhH0ty7GdzL4= =Cy1H -----END PGP SIGNATURE----- --DBIVS5p969aUjpLe-- From owner-freebsd-current@freebsd.org Tue Apr 9 22:36:39 2019 Return-Path: Delivered-To: freebsd-current@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 6D85A1570AC4 for ; Tue, 9 Apr 2019 22:36:39 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F1D38591F for ; Tue, 9 Apr 2019 22:36:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id DzLvhIDcMo7SQDzLxhb3wx; Tue, 09 Apr 2019 16:36:30 -0600 X-Authority-Analysis: v=2.3 cv=Go88BX9C c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=oexKYjalfGEA:10 a=iKhvJSA4AAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=myc0QebvQyQhy0_iO9kA:9 a=QEXdDO2ut3YA:10 a=odh9cflL3HIXMm4fY7Wr:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from DESKTOP-IJTJOA3.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 116CA1877; Tue, 9 Apr 2019 15:36:27 -0700 (PDT) Date: Tue, 09 Apr 2019 15:36:02 -0700 User-Agent: K-9 Mail for Android In-Reply-To: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> References: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot To: freebsd-current@freebsd.org, "Rodney W. Grimes" , David Boyd From: Cy Schubert Message-ID: <3A0D37FF-317F-45CE-88E5-64E4642BACD6@cschubert.com> X-CMAE-Envelope: MS4wfLU6NYjLRfbpaDGi0EzvSkdq2TZOqSh4/OUwit7qeAg5huUHPLvjU9QEmdXptFLAxTUbnZwTlan7dmLip3c1bKlu5Y3XqJK49igsRQnHJEW+hfbw4b4q PZ3iKjeOVO8s+27RxgFiB6ugRVYnh6q+hU0oGMo5BLatMmsipCfVJxoGtTzk1AdHFNDieiNlvWslLHMQoKchtCLDvI2UV7T6Ps1f7v8jvKMxawGEOAec+9tg gtMAX+HZphuqiqf2G/TpAcL3sdbTgIPhtmVBBiuKzao= X-Rspamd-Queue-Id: 8F1D38591F X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-5.39 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11,233.154.66.70.zen.spamhaus.org : 127.0.0.11]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[spqr.komquats.com]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[139.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.20)[ip: (-5.42), ipnet: 64.59.128.0/20(-3.09), asn: 6327(-2.40), country: CA(-0.09)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 22:36:39 -0000 On April 9, 2019 12:41:34 PM PDT, "Rodney W=2E Grimes" wrote: >> On Tue, 2019-04-09 at 12:20 -0700, Rodney W=2E Grimes wrote: >> > > After upgrading from FreeBSD-13=2E0-CURRENT-amd64-20190328-r345620 >to >> > > FreeBSD-13=2E0-CURRENT-amd64-20190404-r345863, lsof (4=2E92 from >> > > packages) >> > > hangs=2E >> > >=20 >> > > This is true for bare metal installs and virtual machine >installs=2E >> > >=20 >> > > How to recreate: >> > > =09 >> > > Install FreeBSD-13=2E0-CURRENT-amd64-20190404-r345863 snapshot=2E >> > >=20 >> > > as root: lsof /sbin/init >> > >=20 >> > > By running command with -b option, this error is displayed: >> > >=20 >> > > lsof: status error on /sbin/init: Resource temporarily >unavailable >> > >=20 >> > > The return code is 1=2E >> > >=20 >> > > This probably requires adjustment to lsof, but only the FreeBSD >> > > snapshot changed, so I'll start here=2E >> >=20 >> > Where did you get your lsof binary from? >> >=20 >> > lsof has internal knowledge of kernel data structures=20 >> > and must be compiled to match the running system=2E >> >=20 >> >=20 >> > > Thanks=2E >> > > David Boyd=2E >>=20 >>=20 >> lsof was installed via pkg install from pkg=2Efreebsd=2Eorg=2E > >That does not work well on ^head or for that mater any snapshot, >as I said, lsof has internal knowledge of kernel data structures >and must match the running kernel for it to work=2E > >It should be complaining about a version mismatch, but perhaps >it was compiled recently enough that these are matching, but >there is still a datastruct that changed=2E Version mismatches are innocuous=2E I tend to use it on -current until it = breaks, rebuilding it as needed=2E Rebuilding is a good time to update the = port while I'm at it=2E This policy has served me well over the years=2E=20 --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E From owner-freebsd-current@freebsd.org Wed Apr 10 01:29:24 2019 Return-Path: Delivered-To: freebsd-current@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 C90D7157424F for ; Wed, 10 Apr 2019 01:29:24 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 616048A175 for ; Wed, 10 Apr 2019 01:29:22 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1554859753; bh=9Wd79zpx OLxyotqi1kPOSPcP44abn1zIpO+/Afz34HM=; b=O9LtDVwbk1RCsBQzA/7onmVr aX+Qfl/XucMXmGb5e9k3L9EqqAHe5HL/nRi5q34zwN7QmWnNlzCaF88rYjYuxBFf 066peknbgRNlXgrYXXEBQJ+d39sw1Xhui346tlR91pgaqd5GJKCbVbKdK4FYHHhE Oy8/zzYl8rhEpCXpMjA= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 22879F20E; Tue, 9 Apr 2019 21:29:13 -0400 (EDT) Subject: Re: r346025: ZFS filesystems do not mount anymore To: "O. Hartmann" , =?UTF-8?Q?Trond_Endrest=c3=b8l?= Cc: FreeBSD CURRENT References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> <20190409153014.5299494e@freyja> From: Michael Butler Openpgp: preference=signencrypt Message-ID: <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> Date: Tue, 9 Apr 2019 21:29:12 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190409153014.5299494e@freyja> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 616048A175 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protected-networks.net header.s=201508 header.b=O9LtDVwb; spf=pass (mx1.freebsd.org: domain of imb@protected-networks.net designates 202.12.127.228 as permitted sender) smtp.mailfrom=imb@protected-networks.net X-Spamd-Result: default: False [-1.58 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[protected-networks.net:+]; MX_GOOD(-0.01)[sarah.protected-networks.net,mail.protected-networks.net]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.01)[country: US(-0.06)]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.66)[-0.664,0]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.61)[0.607,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[protected-networks.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 01:29:25 -0000 On 2019-04-09 09:30, O. Hartmann wrote: > On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) > Trond Endrestøl wrote: > >> On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote: >> >>> On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: >>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA256 >>>> >>>> Hello, >>>> >>>> after a bunch of updates this weekend, mounting ZFS filesystems on >>>> CURRENT r346025 doesn't work anymore at boot time when ZFS is >>>> built-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. >>>> >>>> After the system has booted, mounting all ZFS filesystems via "zfs mount >>>> -a" operates as expected and all filesystems are available as usual. >>> >>> I blame r346017: >>> >>> Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] >>> Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. >>> Setting hostid: 0xf9071336. >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> Starting file system checks: >>> Mounting local filesystems:. >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> ELF ldconfig path: /lib /usr/lib /usr/lib/compat >>> 32-bit compatibility ldconfig path: /usr/lib32 >>> >>> [...] >>> >>> Creating and/or trimming log files. >>> Starting syslogd. >>> Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/security: >>> No such file or directory Setting date via ntp. >>> 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset >>> -0.992370 sec No core dumps found. >>> Clearing /tmp (X related). >>> Updating motd:. >>> Mounting late filesystems:mount: /usr/compat/linux: No such file or >>> directory mount: /usr/compat/linux: No such file or directory >>> mount: /usr/compat/linux: No such file or directory >>> mount: /usr/compat/linux: No such file or directory >>> . >>> Mounting /etc/fstab filesystems failed, startup aborted >>> ERROR: ABORTING BOOT (sending SIGTERM to parent)! >>> Enter full pathname of shell or RETURN for /bin/sh: >>> root@freebsd-head-zfs:/ # zfs mount -av >>> root@freebsd-head-zfs:/ # mount -al >>> root@freebsd-head-zfs:/ # exit >>> Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. >>> Setting hostid: 0xf9071336. >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> Fast boot: skipping disk checks. >>> Mounting local filesystems:. >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> interface zfsctrl.1 already present in the KLD 'kernel'! >>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>> kldload: an error occurred while loading module zfs. Please check dmesg(8) >>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>> ELF ldconfig >>> path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE >>> 32-bit compatibility ldconfig path: /usr/lib32 >>> >>> [...] >> >> At a later point, this happens: >> >> Starting syslogd. >> usage: protect [-i] command >> protect [-cdi] -g pgrp | -p pid >> Setting date via ntp. >> >> It looks like syslogd is no longer protected against the OOM killer. >> >>> Once I manually mount the remaining filesystems, multiuser boot >>> proceeds as expected. My kernel has options ZFS, and the boot scripts >>> doesn't account for this scenario. >> >> > > Hello, > > thank you for investigating! I think you're correct. I was wondering how this > change could make it into the tree with this kind of impact. > > Maybe filing a PR would be fine? > I just confirmed that the change at SVN r346017 after 'mergemaster -U' yields a (ZFS-based) system which can only be brought into normal service through: a single-user boot mount -a mount -u -o rw / zfs mount -a Reverting this change restores normal operation at start-up. ZFS is also compiled into the kernel on my system, imb From owner-freebsd-current@freebsd.org Wed Apr 10 04:51:18 2019 Return-Path: Delivered-To: freebsd-current@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 41EEB1577A12 for ; Wed, 10 Apr 2019 04:51:18 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3AA18F24E; Wed, 10 Apr 2019 04:51:16 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pl1-x62f.google.com with SMTP id cv12so598110plb.9; Tue, 09 Apr 2019 21:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Muegjs8qIve3FdahaphUW6anJqnKLtywqsF63huUaD0=; b=OSR+IKgaRdAZSdTIDhWLsi79dzb7ehn14nyzl2AhCbs1maIO7/wN3o08W9jluiO+uB lk1vBC0mpge2qs4OcHfyfeb39jufS9yO0UyMCSYCeNWQZKPPEHQ/qAyEfdNagXcqIerg 2fNvEISbUwhL2ywuuVHi0nM7cZ+MAdI/FFmtMYJ3IjwS7AfmanVQJCFNFOuQQon33IjV 80pl4NGIp2/JauG38oKUPkHSbWdCYbLMPDO7RS10cEn/5LnMKSuJmyKd6lDCUrnFZw0g ksGAcu2NYY3akXYwgnA5rZQkIl4w/x3G89hiQ1GJAC/dQh7FxGR8HqJm3DhNDHcFQnT0 BANQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Muegjs8qIve3FdahaphUW6anJqnKLtywqsF63huUaD0=; b=jNBmBKLz/xzztsx2X9YEWTdZRV9OJvk/w67L37vsIopI5IRHg+8duGdjUfKcWBAf1r I4lxE6LleGHhlOwfiU135OriMzYkUaF+4mekmW7BP7sfftSkhvt/fHwzejWK3OrOP02T Ln0b6ytEyA/yVqngPmbFupDBjsDpV63K2yRqlbPrJ/uUIphPlROppbM6rf2+IxMSESKP M4flS+fsjZXFkfGgFhftBkr/m6vH9ZhL8auv6MkC+JTITswL2iu0/qlNVxW5kSo4qGcf s+58J+0Mtmzw3ni9QpjxWdz5pVgYvXZH3naWekniKkjFo0PkxJrQKX6+d2+piv8dHIZ/ X3ag== X-Gm-Message-State: APjAAAWS5mvId0qMyjs5LapynlblVO7NY0lRtJg4XA1McBoiqn63Hp9w V6Tb3c8hu7SvPmML3PftYyyBoCY9rqU= X-Google-Smtp-Source: APXvYqwR3hyyN62ynQnR9/tHZWXBzVgdLjHBPeyFItAiqHtoJxy1iaNHNlI0lBtr/DRMxriSOj0BGg== X-Received: by 2002:a17:902:e109:: with SMTP id cc9mr42385530plb.148.1554871874682; Tue, 09 Apr 2019 21:51:14 -0700 (PDT) Received: from [192.168.20.22] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id j67sm57666003pfc.72.2019.04.09.21.51.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Apr 2019 21:51:13 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: r346025: ZFS filesystems do not mount anymore From: Enji Cooper X-Mailer: iPhone Mail (16E227) In-Reply-To: <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> Date: Tue, 9 Apr 2019 21:51:12 -0700 Cc: "O. Hartmann" , =?utf-8?Q?Trond_Endrest=C3=B8l?= , FreeBSD CURRENT , crees@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4422B7AB-B398-472B-9F66-00624853EE3D@gmail.com> References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> <20190409153014.5299494e@freyja> <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> To: Michael Butler X-Rspamd-Queue-Id: A3AA18F24E X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=OSR+IKga; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::62f as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.26 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.85)[-0.847,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.90)[ip: (-9.32), ipnet: 2607:f8b0::/32(-2.94), asn: 15169(-2.18), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[f.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 04:51:18 -0000 > On Apr 9, 2019, at 18:29, Michael Butler wrot= e: >=20 >> On 2019-04-09 09:30, O. Hartmann wrote: >> On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) >> Trond Endrest=C3=B8l wrote: >>=20 >>>> On Tue, 9 Apr 2019 10:06+0200, Trond Endrest=C3=B8l wrote: >>>>=20 >>>>> On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: >>>>>=20 >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA256 >>>>>=20 >>>>> Hello, >>>>>=20 >>>>> after a bunch of updates this weekend, mounting ZFS filesystems on >>>>> CURRENT r346025 doesn't work anymore at boot time when ZFS is >>>>> built-in-kernel. zfs_enable=3D"YES" is set in /etc/rc.conf. >>>>>=20 >>>>> After the system has booted, mounting all ZFS filesystems via "zfs mou= nt >>>>> -a" operates as expected and all filesystems are available as usual. =20= >>>>=20 >>>> I blame r346017: >>>>=20 >>>> Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] >>>> Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. >>>> Setting hostid: 0xf9071336. >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> Starting file system checks: >>>> Mounting local filesystems:. >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> ELF ldconfig path: /lib /usr/lib /usr/lib/compat >>>> 32-bit compatibility ldconfig path: /usr/lib32 >>>>=20 >>>> [...] >>>>=20 >>>> Creating and/or trimming log files. >>>> Starting syslogd. >>>> Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/securit= y: >>>> No such file or directory Setting date via ntp. >>>> 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset >>>> -0.992370 sec No core dumps found. >>>> Clearing /tmp (X related). >>>> Updating motd:. >>>> Mounting late filesystems:mount: /usr/compat/linux: No such file or >>>> directory mount: /usr/compat/linux: No such file or directory >>>> mount: /usr/compat/linux: No such file or directory >>>> mount: /usr/compat/linux: No such file or directory >>>> . >>>> Mounting /etc/fstab filesystems failed, startup aborted >>>> ERROR: ABORTING BOOT (sending SIGTERM to parent)! >>>> Enter full pathname of shell or RETURN for /bin/sh: >>>> root@freebsd-head-zfs:/ # zfs mount -av >>>> root@freebsd-head-zfs:/ # mount -al >>>> root@freebsd-head-zfs:/ # exit >>>> Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. >>>> Setting hostid: 0xf9071336. >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> Fast boot: skipping disk checks. >>>> Mounting local filesystems:. >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> interface zfsctrl.1 already present in the KLD 'kernel'! >>>> linker_load_file: /boot/kernel/zfs.ko - unsupported file type >>>> kldload: an error occurred while loading module zfs. Please check dmesg= (8) >>>> for more details. /etc/rc: WARNING: Unable to load kernel module zfs >>>> ELF ldconfig >>>> path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compa= t/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE >>>> 32-bit compatibility ldconfig path: /usr/lib32 >>>>=20 >>>> [...] =20 >>>=20 >>> At a later point, this happens: >>>=20 >>> Starting syslogd. >>> usage: protect [-i] command >>> protect [-cdi] -g pgrp | -p pid >>> Setting date via ntp. >>>=20 >>> It looks like syslogd is no longer protected against the OOM killer. >>>=20 >>>> Once I manually mount the remaining filesystems, multiuser boot=20 >>>> proceeds as expected. My kernel has options ZFS, and the boot scripts=20= >>>> doesn't account for this scenario. =20 >>>=20 >>>=20 >>=20 >> Hello, >>=20 >> thank you for investigating! I think you're correct. I was wondering how t= his >> change could make it into the tree with this kind of impact. >>=20 >> Maybe filing a PR would be fine? >>=20 >=20 > I just confirmed that the change at SVN r346017 after 'mergemaster -U' > yields a (ZFS-based) system which can only be brought into normal > service through: >=20 > a single-user boot > mount -a > mount -u -o rw / > zfs mount -a >=20 > Reverting this change restores normal operation at start-up. >=20 > ZFS is also compiled into the kernel on my system, >=20 > imb CCing crees@, the author of r346017, for context. I will file a PR soon if o= ne hasn=E2=80=99t already been filed. -Enji= From owner-freebsd-current@freebsd.org Wed Apr 10 05:12:34 2019 Return-Path: Delivered-To: freebsd-current@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 62A7C1578308 for ; Wed, 10 Apr 2019 05:12:34 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93B008FD83; Wed, 10 Apr 2019 05:12:33 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pl1-x62f.google.com with SMTP id g12so624216pll.11; Tue, 09 Apr 2019 22:12:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=G0N3Cmlk22pSQmQoMMGd3Ma5U0h4Hrfyl7MYPxeRnL8=; b=nvIbU37DTbfjvwSxEpfImMFm1j4IW4f2P3YymUufXuBEjbxNYl8f/Rwg6fCs2xNZRu mdDc1aHdhzZ51XaI2EAKL+/7D6M8vOqwgCqtfKlpYBcuDmB/k23+g+/cQWWoJHSaR5rS amd0JOyfbkBc3VZr31yInsMkYKIzbeMcDsEbISYugAu6uTqK+frEwh+MhbtHG6PvGvk0 1jRSbt/c4HeGLLdDuYveAY8A+qWSwS1IvIttbUOAWB/cLuUyU2pqU1NtWUpPe2UjPFpj ev5Gjegi2r2tg+/HbUI2Xz7uwU7Fv1Tz3j4GUKza3WJMp5xMouX6OHXyWHbUMSKe08sp F4/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=G0N3Cmlk22pSQmQoMMGd3Ma5U0h4Hrfyl7MYPxeRnL8=; b=hcQF8s97CL5BdMq4rKaSZto+V2yXO7SdOKJhrwUEuR6aDULq/QrJfR3cZmmU61UX58 uXkz4QltW1oowv5LSZUQ0lQtt9Dy5cLXUCt/J3D4mWgXroQ6hetOBTggFFkff7mXT1WE x9z84mnXUawxfZCnD2uM59oMzX4gzX/9nW909bKsVP4c5HqRtkWHEzM+GeHU4V0ZjUGs tYVsuNR+8Fku3dnRLr6EMYxqgRMVMZAOC2/hqH58vBVmRkMtRnmDlL+S3I24XOBMboYq BWp04MHFluseu+i/t8JNmNB6SnuyvXz/Wz8QKvUaRwGf2Y17C+vjZR+zKgBmcNHvNomv P0uw== X-Gm-Message-State: APjAAAX36k7MtCNVBpYl+aQcRX2TB9Fy8xDPunrC6OVXdqk79YG0KFz1 dmfvAbUm4FWgwW/aPVEJLEc= X-Google-Smtp-Source: APXvYqxyrjC8QWuPPLkTUoXXR62vWZcEUv7Ao7C6y636KnDk8Cc63QSFSQtBz79SdBEDJamBHX6lKQ== X-Received: by 2002:a17:902:8bc3:: with SMTP id r3mr42508588plo.53.1554873152554; Tue, 09 Apr 2019 22:12:32 -0700 (PDT) Received: from [192.168.20.21] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id l184sm84509638pfc.98.2019.04.09.22.12.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Apr 2019 22:12:31 -0700 (PDT) From: "Enji Cooper (yaneurabeya)" Message-Id: <19CA3A5D-4E41-4F17-A788-B9545F104EC5@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: r346025: ZFS filesystems do not mount anymore Date: Tue, 9 Apr 2019 22:12:30 -0700 In-Reply-To: <4422B7AB-B398-472B-9F66-00624853EE3D@gmail.com> Cc: "O. Hartmann" , =?utf-8?Q?Trond_Endrest=C3=B8l?= , FreeBSD CURRENT , crees@freebsd.org To: Michael Butler References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> <20190409153014.5299494e@freyja> <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> <4422B7AB-B398-472B-9F66-00624853EE3D@gmail.com> X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: 93B008FD83 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=nvIbU37D; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::62f as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.41 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.91)[ip: (-9.35), ipnet: 2607:f8b0::/32(-2.94), asn: 15169(-2.18), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[f.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 05:12:34 -0000 > On Apr 9, 2019, at 21:51, Enji Cooper wrote: =E2=80=A6 > CCing crees@, the author of r346017, for context. I will file a PR = soon if one hasn=E2=80=99t already been filed. I filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237172= to track the issue. Cheers! -Enji From owner-freebsd-current@freebsd.org Wed Apr 10 06:21:58 2019 Return-Path: Delivered-To: freebsd-current@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 082401579911 for ; Wed, 10 Apr 2019 06:21:58 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A6AA091A25; Wed, 10 Apr 2019 06:21:56 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id E6cJh3TvtldkPE6cKhhbUc; Wed, 10 Apr 2019 00:21:54 -0600 X-Authority-Analysis: v=2.3 cv=Ko4zJleN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=8nJEP1OIZ-IA:10 a=oexKYjalfGEA:10 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=IwKF7nNvhf1yLLCTi6cA:9 a=wPNLvfGTeEIA:10 a=1rTF-VXdzdgA:10 a=XJcsq8paoUoA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=di9ubeNldx8Bp97d9axH:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id C3BB6354; Tue, 9 Apr 2019 23:21:50 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x3A6LodR069938; Tue, 9 Apr 2019 23:21:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x3A6Lo4P069917; Tue, 9 Apr 2019 23:21:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201904100621.x3A6Lo4P069917@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Enji Cooper (yaneurabeya)" , crees@freebsd.org cc: Michael Butler , "O. Hartmann" , =?utf-8?Q?Trond_Endrest=C3=B8l?= , FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore In-Reply-To: Message from "Enji Cooper (yaneurabeya)" of "Tue, 09 Apr 2019 22:12:30 -0700." <19CA3A5D-4E41-4F17-A788-B9545F104EC5@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Tue, 09 Apr 2019 23:21:50 -0700 X-CMAE-Envelope: MS4wfHXaZdqo6DWk7Fl+dkyBCXayxxY6fb0G8QzAD88HeJGo370c02+aIi05bCF8jkxDaH+84J+AIOcqVhJ+0/EeIfK6IE2CgdqFie73X9eOIF1Mu6bNO/kD A88HnllReHKbqN/SY5Wvd6NxFppdQE/EcXNFeiuKzOUjzpQbPeZ79nmMf1K+6qqReOXQwqlx0cwbK/q/aaqoYbu9MUnwVopSlCQbJ9GOb/BC3vLx0xpJoqNn H6L/DwdqhiDdRej8ylRlLTOLdDPVK5rgGI1fboUOyBvht+jHV1LZT8XXgOS49+ElpkZfYGdRoXZA3mbchBGyl5A4Vh0qVLpQJuhee5mfOu+3HVN01KCP93PD uHjQI7pLLwHVIjCy6GNiQ9TzcD12nw== X-Rspamd-Queue-Id: A6AA091A25 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-5.04 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.95)[-0.951,0]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_LOW(-0.10)[9.134.59.64.list.dnswl.org : 127.0.5.1]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.37)[ip: (-6.28), ipnet: 64.59.128.0/20(-3.10), asn: 6327(-2.40), country: CA(-0.09)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 06:21:58 -0000 In message <19CA3A5D-4E41-4F17-A788-B9545F104EC5@gmail.com>, "Enji Cooper (yane urabeya)" writes: > > > On Apr 9, 2019, at 21:51, Enji Cooper wrote: > > … > > > CCing crees@, the author of r346017, for context. I will file a PR soon if > one hasn’t already been filed. > > I filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237172 to tra > ck the issue. This should probably be reverted until it is tested and resolved. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Wed Apr 10 09:44:46 2019 Return-Path: Delivered-To: freebsd-current@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 BD0C2157DBAB for ; Wed, 10 Apr 2019 09:44:46 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF5B197F40 for ; Wed, 10 Apr 2019 09:44:45 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3A9hagL064723; Wed, 10 Apr 2019 02:43:36 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3A9hZiF064722; Wed, 10 Apr 2019 02:43:35 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904100943.x3A9hZiF064722@gndrsh.dnsmgr.net> Subject: Re: r346025: ZFS filesystems do not mount anymore In-Reply-To: <201904100621.x3A6Lo4P069917@slippy.cwsent.com> To: Cy Schubert Date: Wed, 10 Apr 2019 02:43:35 -0700 (PDT) CC: "Enji Cooper (yaneurabeya)" , crees@freebsd.org, Michael Butler , "O. Hartmann" , =?UTF-8?Q?Trond_Endrest=C3=B8l?= , FreeBSD CURRENT X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: EF5B197F40 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-0.14 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.39)[-0.389,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.03)[ip: (0.12), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.04), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.59)[-0.586,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_HAM_SHORT(-0.08)[-0.082,0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 09:44:46 -0000 > In message <19CA3A5D-4E41-4F17-A788-B9545F104EC5@gmail.com>, "Enji > Cooper (yane > urabeya)" writes: > > > > > On Apr 9, 2019, at 21:51, Enji Cooper wrote: > > > > ??? > > > > > CCing crees@, the author of r346017, for context. I will file a PR soon if > > one hasn???t already been filed. > > > > I filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237172 to tra > > ck the issue. > > This should probably be reverted until it is tested and resolved. Has been reverted, we may want to clarify the policy when a none source committer has approval for a commit to src that turns out to need reverted they need to revert they do not need an approval to revert, or that this approval is implicit? crees delayed the revert of this while waiting for that approval. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed Apr 10 20:05:37 2019 Return-Path: Delivered-To: freebsd-current@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 BE327156B11B; Wed, 10 Apr 2019 20:05:37 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-yb1-f193.google.com (mail-yb1-f193.google.com [209.85.219.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AEE787FBD; Wed, 10 Apr 2019 20:05:36 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-yb1-f193.google.com with SMTP id c15so1323730ybk.8; Wed, 10 Apr 2019 13:05:36 -0700 (PDT) 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:cc; bh=a7bT3XRnKun6fSZk7mIObYmJnVFv97fTgaqYvfUoFGA=; b=XuoxjggXc5vzXBbWOLq9HgUT6mrQR92pxpkfajGaXQRoALmplRmjM4vIrkS/nRc9hp IMf6zzdgyrr6J0aViJuuTnjhFKafz/KTXGMIiolDnLjePPsxXfe1SIMwZHZnztyOQH7i mYwL3GEZzUBUMmfo+AYco2c6h//I0QsGql2+1Q9o/J8pEudB8LlP6pm8eYobF57J+W3K Ldf88VtyBskRPDT6etCtWJ5H9DwYeLP7Q9NcwY1qyIgB7TIokyK7Bs5RUYDm9Avr02Jn J12VStymrFe6IYVrEg7Ue+kKLHRisWw7GBMWa3WP76D/CW3rKGnglA+qRYWXm7ZwVgsb HATA== X-Gm-Message-State: APjAAAUwE0NzI30UpOEE/NFQPlfcwax3dmBP8ioThvQGYjteLj6SLesS NXcaZV0zRY48RpUqLTcJHEi+Vhp+bT4Ct/RiXs9/rYWi X-Google-Smtp-Source: APXvYqxsdzBXg+eQhtbrKyXE6OLH8MqD73X92z0nwOTRQ76eP3dHy1JSbetZI7VZsivzPRw/l0sX5IrrGu8Q18K9xhY= X-Received: by 2002:a25:b004:: with SMTP id q4mr36565037ybf.34.1554921439447; Wed, 10 Apr 2019 11:37:19 -0700 (PDT) MIME-Version: 1.0 From: Li-Wen Hsu Date: Thu, 11 Apr 2019 03:37:08 +0900 Message-ID: Subject: FreeBSD CI Weekly Report 2019-04-07 To: freebsd-testing@freebsd.org Cc: FreeBSD Current , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 9AEE787FBD X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of lwhsufreebsd@gmail.com designates 209.85.219.193 as permitted sender) smtp.mailfrom=lwhsufreebsd@gmail.com X-Spamd-Result: default: False [-4.07 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.84)[-0.835,0]; RCVD_IN_DNSWL_NONE(0.00)[193.219.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.19), country: US(-0.06)]; FORGED_SENDER(0.30)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[193.219.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 20:05:38 -0000 (bcc -current and -stable for more audience) FreeBSD CI Weekly Report 2019-04-07 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-04-01 to 2019-04-07. During this period, we have: * 1841 builds (96% passed, 4% failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 314 test runs (34.7% passed, 65% unstable, 0.3% exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 4 doc buils (100% passed) (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/s/BymrvPI_4 and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * sys.geom.class.eli.online_resize_test.online_resize https://bugs.freebsd.org/237128 * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * sys.netmap.ctrl-api-test.main https://bugs.freebsd.org/237129 * sys.opencrypto.runtests.main https://bugs.freebsd.org/237130 * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * lib.libc.sys.sendfile_test.fd_positive_shm_v4 * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 * lib.libc.gen.floatunditf_test.floatunditf * lib.libc.stdio.printfloat_test.hexadecimal_rounding * lib.msun.ctrig_test.test_small_inputs * lib.msun.precision_test.t_precision https://bugs.freebsd.org/236936 * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sys.netmap.ctrl-api-test.main https://bugs.freebsd.org/237129 * sys.opencrypto.runtests.main https://bugs.freebsd.org/237130 * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * https://ci.freebsd.org/job/FreeBSD-stable-11-amd64-test/ * usr.bin.procstat.procstat_test.kernel_stacks * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * sys.netmap.ctrl-api-test.main https://bugs.freebsd.org/237129 * sys.opencrypto.runtests.main https://bugs.freebsd.org/237130 * usr.bin.procstat.procstat_test.kernel_stacks * local.kyua.* (31 cases) * local.lutok.* (3 cases) * lib.libc.sys.sendfile_test.fd_positive_shm_v4 * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 ## Failing Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * common.ip.t_dtrace_contrib.tst_ipv4localsctp_ksh * common.ip.t_dtrace_contrib.tst_localsctpstate_ksh * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * usr.bin.procstat.procstat_test.command_line_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 ## Oepn Issues ### New * https://bugs.freebsd.org/237077 possible race in build: /usr/src/sys/amd64/linux/linux_support.s:38:2: error: expected relocatable expression ### In progress * https://bugs.freebsd.org/236936 4 test cases failing on i386 after r345562 ### Cause build fails * [233735: Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory](https://bugs.freebsd.org/233735) * [233769: Possible build race: ld: error: unable to find library -lgcc_s](https://bugs.freebsd.org/233769) ### Others [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) ## Other News * Some PF tests are filing for a while because of py27-pcap-0.6.5, thanks for kp@'s report and bofh@ committed update of py-pcap-0.6.6. From owner-freebsd-current@freebsd.org Thu Apr 11 01:24:08 2019 Return-Path: Delivered-To: freebsd-current@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 9A93915737B9 for ; Thu, 11 Apr 2019 01:24:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670054.outbound.protection.outlook.com [40.107.67.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 843446E05A; Thu, 11 Apr 2019 01:24:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM (52.132.84.84) by QB1PR01MB3987.CANPRD01.PROD.OUTLOOK.COM (52.132.84.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.15; Thu, 11 Apr 2019 01:24:03 +0000 Received: from QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM ([fe80::9c13:e118:131c:f3fd]) by QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM ([fe80::9c13:e118:131c:f3fd%2]) with mapi id 15.20.1792.009; Thu, 11 Apr 2019 01:24:03 +0000 From: Rick Macklem To: Mateusz Guzik CC: "kib@freebsd.org" , "freebsd-current@FreeBSD.org" Subject: Do the pidhashtbl_locks added by r340742 need to be sx locks? Thread-Topic: Do the pidhashtbl_locks added by r340742 need to be sx locks? Thread-Index: AQHU8AP7fWJXG48RU0WTxwDO79KhQw== Date: Thu, 11 Apr 2019 01:24:03 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e5a506d9-4f9b-48f4-ebc5-08d6be1c6267 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:QB1PR01MB3987; x-ms-traffictypediagnostic: QB1PR01MB3987: x-microsoft-antispam-prvs: x-forefront-prvs: 00046D390F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(136003)(39860400002)(376002)(396003)(189003)(199004)(6436002)(450100002)(52536014)(53936002)(4326008)(5660300002)(9686003)(25786009)(2906002)(256004)(786003)(54906003)(316002)(14444005)(55016002)(99286004)(74482002)(86362001)(6916009)(186003)(97736004)(105586002)(6506007)(81156014)(102836004)(476003)(68736007)(8936002)(81166006)(106356001)(7696005)(8676002)(74316002)(33656002)(305945005)(486006)(478600001)(14454004)(71190400001)(71200400001)(46003); DIR:OUT; SFP:1101; SCL:1; SRVR:QB1PR01MB3987; H:QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: EIHmTzOEQohohEESDS9dMFbbTKh9XcIea41kVDE4xpOQ+qEhuHRBBtw4DEZr0c4y7ZD+lNCzmpNqDaIMY4fmOOcFhqygeS+dkngliiVtUk5ehDc3Smm+qHpr5EUphmR3hb+s4i81N/BM6/0hyfYuWJZCxWlUsdngXHHuP55Zd3mCZvMsSVBw/4KXkNU1uvGxB1lbjKAVfNQb+MkjT1BW4vQhubm6n9JRvwAegbg9h3PvHWnODyf94d+okcK3JJJ4p3heGf1LUvD3X5b2VJWgpIXW29h9TFgCU4ro+3ZQ8KfnGvY8IiKEKSTMn1eXf6jkTp59EtP6+x9xEkxRsouJTEWbc9flM0o8A4EMHbiZ7gJxTaa/jiQ1n1kkq6yic/XdWWUmF2bgNwlYzuoPX8lPnymbdH51QvSqqx8gIHlZj38= 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: e5a506d9-4f9b-48f4-ebc5-08d6be1c6267 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2019 01:24:03.7382 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: QB1PR01MB3987 X-Rspamd-Queue-Id: 843446E05A X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.54 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-2.99 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[uoguelph.ca]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.98)[ipnet: 40.64.0.0/10(-2.61), asn: 8075(-2.23), country: US(-0.06)]; MX_GOOD(-0.01)[mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com]; NEURAL_HAM_SHORT(-0.70)[-0.702,0]; RCVD_IN_DNSWL_NONE(0.00)[54.67.107.40.list.dnswl.org : 127.0.3.0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; MIME_TRACE(0.00)[0:+] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2019 01:24:08 -0000 Hi, I finally got around to looking at what effect replacing pfind_locked() wit= h pfind() has for the NFSv4 client and it is broken. The problem is that the NFS code needs to call some variant of "pfind()" wh= ile holding a mutex lock. The current _pfind() code uses the pidhashtbl_locks, which are "sx" locks. There are a few ways to fix this: 1 - Create a custom version of _pfind() for the NFS client with the sx_X() = calls removed, plus replace the locking of allproc_lock with locking of all= the pidhashtbl_locks, so that the "sx" locks are acquired before the mute= x. --> Not very efficient, but since it is only done once/sec, I can liv= e with it. 2 - Similar to the above, but still lock the allproc_lock and use a loop of FOREACH_PROC_IN_SYSTEM(p) instead of a hash list for the pid in the custom pfind(). (I don't know if this would be preferable to locking a= ll the pidhashtbl_locks for other users of pfind()?) 3 - Convert the pidhashtbl_locks to mutexes. Then the NFS client doesn't ne= ed to acquire any proc related locks and it just works. I can't see anywhere that "sleeps" while holding the pidhashtbl_locks,= so I think they can be converted, although I haven't tried it yet? >From my perspective, #3 seems the better solution. What do others think? rick From owner-freebsd-current@freebsd.org Thu Apr 11 01:49:33 2019 Return-Path: Delivered-To: freebsd-current@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 0A4301574324 for ; Thu, 11 Apr 2019 01:49:33 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 230646EB3B; Thu, 11 Apr 2019 01:49:32 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qk1-x744.google.com with SMTP id o129so2510924qke.8; Wed, 10 Apr 2019 18:49:32 -0700 (PDT) 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=uipVgq/RBBxwfCt++UEEj9xjz8vy7Z1AVMBJ/tB+WAs=; b=JLW46ihneAjeOx9AJdZehfbk1Wu6ILaAuTzGEGOvBDn0Z+xxsttP/7uQBkMkmOkuJM gmmsioDeWdi3XlXouLn2udYgpj9QHSXf+GjIvh3xOGasCFLJchF1Is1t6QoloygBGaKq /Ae05hOhe0q5egTfpduJnXlTS4R2FUCAqdSi+ahPQgEv/bifW8in1R1RgcYLdd8WC/r2 iaYWPWuSlJ8JJ9JBFThuhKl2KzP7AcEPQbQ+jLvzI2i6UCyZDvxH41BOgoRRuz6pVza1 dgq0A0B1QumVuYKyZ5JyouMJ2xCmR6JdruAN7heaCuOvZVUbHyc87GNcmZHPBXE1J14/ 1gUA== 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=uipVgq/RBBxwfCt++UEEj9xjz8vy7Z1AVMBJ/tB+WAs=; b=BCnA4WOQwBG8nr7w7z62zYrq5wAuVj9//IACvcta9X0dVriRIoXtd17R8tWneJcgqd jjP3QnQJNfIvEjFNc7dfrXoRXcu6ZOPTcdn5LJqil7UcKJDqx8zXmI22LrQhN74BIf39 B0HXzpUapZBvnryWviZFmycvOuoDrTeA2WlZIiHZGFihhqagU+Dgxhtg9CCyf3Fe3OGZ CFO50vBZ+wYIdhHPDrh4zh0TgPUJ4bSXHlgqhjNdLjEUAFJ/ag8x/WNAtcic+Wl2ubu0 6CN7k5lPiscqFqOuNDCEE5wPi5jnfvvGd7GXOo+W5wB15biI1VnqYhzL6e4wqeJLBeit m2cQ== X-Gm-Message-State: APjAAAVJNXSRiAeqfBe83b+jXBeGM0FkZnna9Pf2aEpJAErAc244ed7S jqLPYsSKvKcL2Qa41wDVTBtI+ZrVQTfyFf92/UI= X-Google-Smtp-Source: APXvYqwGjjKsYHalieeSmUX26WJ1QrLs589EF3VP5x/ZOWzysU6jhjTILCG/j28qDbUBTGpejM8I/YD2jnlYKQBOuFQ= X-Received: by 2002:a05:620a:126d:: with SMTP id b13mr36286606qkl.174.1554947371756; Wed, 10 Apr 2019 18:49:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:3353:0:0:0:0:0 with HTTP; Wed, 10 Apr 2019 18:49:31 -0700 (PDT) In-Reply-To: References: From: Mateusz Guzik Date: Thu, 11 Apr 2019 03:49:31 +0200 Message-ID: Subject: Re: Do the pidhashtbl_locks added by r340742 need to be sx locks? To: Rick Macklem Cc: "kib@freebsd.org" , "freebsd-current@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 230646EB3B X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=JLW46ihn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mjguzik@gmail.com designates 2607:f8b0:4864:20::744 as permitted sender) smtp.mailfrom=mjguzik@gmail.com X-Spamd-Result: default: False [-3.24 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.54)[-0.543,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.69)[ip: (1.77), ipnet: 2607:f8b0::/32(-2.96), asn: 15169(-2.19), country: US(-0.06)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2019 01:49:33 -0000 On 4/11/19, Rick Macklem wrote: > Hi, > > I finally got around to looking at what effect replacing pfind_locked() > with > pfind() has for the NFSv4 client and it is broken. > > The problem is that the NFS code needs to call some variant of "pfind()" > while > holding a mutex lock. The current _pfind() code uses the pidhashtbl_locks, > which are "sx" locks. > > There are a few ways to fix this: > 1 - Create a custom version of _pfind() for the NFS client with the sx_X() > calls > removed, plus replace the locking of allproc_lock with locking of all > the > pidhashtbl_locks, so that the "sx" locks are acquired before the > mutex. > --> Not very efficient, but since it is only done once/sec, I can live > with it. > 2 - Similar to the above, but still lock the allproc_lock and use a loop of > FOREACH_PROC_IN_SYSTEM(p) instead of a hash list for the pid in the > custom pfind(). (I don't know if this would be preferable to locking > all > the pidhashtbl_locks for other users of pfind()?) > 3 - Convert the pidhashtbl_locks to mutexes. Then the NFS client doesn't > need > to acquire any proc related locks and it just works. > I can't see anywhere that "sleeps" while holding the pidhashtbl_locks, > so I > think they can be converted, although I haven't tried it yet? > > From my perspective, #3 seems the better solution. > What do others think? > Changing the lock type to rwlock may be doable and worthwhile on its own, but I don't think it would constitute the right fix. Preferably there would be an easy to use mechanism which allows registering per-process callbacks. Currently it can be somewhat emulated with EVENTHANDLERs, but it would give calls for all exiting processes, not only the ones of interest. Then there would be no need to periodically scan as you would always get notified on process exit. Note the current code does not ref processes it is interested in any manner and just performs a timestamp check to see if it got the one it expected (with pid reuse in mind). So I think a temporary hack which will do the trick will take the current approach further: rely on struct proc being type-stable (i.e. never being freed) and also store the pointer. You can always safely PROC_LOCK it, do checks to see the proc is alive and has the right timestamp, all without needing to pfind or similar. -- Mateusz Guzik From owner-freebsd-current@freebsd.org Thu Apr 11 04:41:38 2019 Return-Path: Delivered-To: freebsd-current@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 BF581157891A for ; Thu, 11 Apr 2019 04:41:37 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670060.outbound.protection.outlook.com [40.107.67.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 893FF749CE; Thu, 11 Apr 2019 04:41:36 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM (52.132.84.84) by QB1PR01MB3874.CANPRD01.PROD.OUTLOOK.COM (52.132.88.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.14; Thu, 11 Apr 2019 04:41:34 +0000 Received: from QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM ([fe80::9c13:e118:131c:f3fd]) by QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM ([fe80::9c13:e118:131c:f3fd%2]) with mapi id 15.20.1792.009; Thu, 11 Apr 2019 04:41:34 +0000 From: Rick Macklem To: Mateusz Guzik CC: "kib@freebsd.org" , "freebsd-current@FreeBSD.org" Subject: Re: Do the pidhashtbl_locks added by r340742 need to be sx locks? Thread-Topic: Do the pidhashtbl_locks added by r340742 need to be sx locks? Thread-Index: AQHU8AP7fWJXG48RU0WTxwDO79KhQ6Y2MZSAgAArjKw= Date: Thu, 11 Apr 2019 04:41:34 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e34e1c18-2047-4770-ce72-08d6be37fa04 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:QB1PR01MB3874; x-ms-traffictypediagnostic: QB1PR01MB3874: x-microsoft-antispam-prvs: x-forefront-prvs: 00046D390F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(366004)(39860400002)(396003)(376002)(189003)(199004)(71200400001)(106356001)(305945005)(2906002)(476003)(68736007)(1411001)(74482002)(53936002)(186003)(71190400001)(8936002)(97736004)(229853002)(6436002)(7696005)(8676002)(52536014)(33656002)(81156014)(486006)(81166006)(105586002)(478600001)(74316002)(6246003)(5660300002)(14454004)(316002)(786003)(76176011)(86362001)(256004)(55016002)(102836004)(6506007)(99286004)(46003)(25786009)(446003)(4326008)(14444005)(54906003)(11346002)(6916009)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:QB1PR01MB3874; H:QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: n3a2zvZ46gYT8njBce0xcFziD1CjRlfO4XEIrq2YbHlXIrOgdigF3UcM57YR2VtIVgbCnSMbn7A383eBJGLd3RycQshQOJlTq0sIazaC5kyFAOjNBB+w3t7wuqblkVMROS3XwIka7gx7Fh0HQlw9xqpEV2icz6c0934F9mRYbrSJa6ryMAsZnPpoEL8GtjIk14u8xEXRUUIJkqXBBWRPgYo8APlte8T1nEw+3jQbXLWNTXRUfQN45OGX290dnTenhgeQzUerOKCt9pXw7DwZWxDcB7DvFZfs88zgswIee1PUuEUgoAD5SuYS9vxcJjRub5XGtPSgWCeDliCCszO6CYU9pn+AmSI0u4yF/rpnhXOI04IBVkSpGCg+t30BvkDWJG/vbhAVcPrLfuQrRqebP1E3wS/rWT1SP0GbuME+lZY= 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: e34e1c18-2047-4770-ce72-08d6be37fa04 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2019 04:41:34.5730 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: QB1PR01MB3874 X-Rspamd-Queue-Id: 893FF749CE X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.60 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [0.00 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.85)[-0.852,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; NEURAL_HAM_LONG(-0.61)[-0.610,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[uoguelph.ca]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.77)[0.774,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx2.hc184-76.ca.iphmx.com]; RCVD_IN_DNSWL_NONE(0.00)[60.67.107.40.list.dnswl.org : 127.0.3.0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2019 04:41:38 -0000 Mateusz Guzik wrote: >On 4/11/19, Rick Macklem wrote: >> Hi, >> >> I finally got around to looking at what effect replacing pfind_locked() >> with >> pfind() has for the NFSv4 client and it is broken. >> >> The problem is that the NFS code needs to call some variant of "pfind()" >> while >> holding a mutex lock. The current _pfind() code uses the pidhashtbl_lock= s, >> which are "sx" locks. >> >> There are a few ways to fix this: >> 1 - Create a custom version of _pfind() for the NFS client with the sx_X= () >> calls >> removed, plus replace the locking of allproc_lock with locking of = all >> the >> pidhashtbl_locks, so that the "sx" locks are acquired before the >> mutex. >> --> Not very efficient, but since it is only done once/sec, I can = live >> with it. >> 2 - Similar to the above, but still lock the allproc_lock and use a loop= of >> FOREACH_PROC_IN_SYSTEM(p) instead of a hash list for the pid in the >> custom pfind(). (I don't know if this would be preferable to lockin= g >> all >> the pidhashtbl_locks for other users of pfind()?) >> 3 - Convert the pidhashtbl_locks to mutexes. Then the NFS client doesn't >> need >> to acquire any proc related locks and it just works. >> I can't see anywhere that "sleeps" while holding the pidhashtbl_loc= ks, >> so I >> think they can be converted, although I haven't tried it yet? >> >> From my perspective, #3 seems the better solution. >> What do others think? >> > >Changing the lock type to rwlock may be doable and worthwhile on its own, >but I don't think it would constitute the right fix. > >Preferably there would be an easy to use mechanism which allows >registering per-process callbacks. Currently it can be somewhat emulated >with EVENTHANDLERs, but it would give calls for all exiting processes, not >only the ones of interest. Then there would be no need to periodically >scan as you would always get notified on process exit. Long ago when I first did the NFSv4 code for OpenBSD2.6, I had a callback f= unction pointer in "struct proc" which the NFS code set non-null to get a callback. { The code still has remnants of that because it still has nfscl_cleanup_co= mmon(), which was code shared by that callback and this approach which was used = for the Mac OS X port, where I couldn't change "struct proc". } I have never added anything like that for FreeBSD, but I suppose we could l= ook at doing it that way. To be honest, since the current code works fine and can be difficult to tes= t well, I hesitate to change to using a callback. >Note the current code does not ref processes it is interested in any >manner and just performs a timestamp check to see if it got the one it >expected (with pid reuse in mind). > >So I think a temporary hack which will do the trick will take the current >approach further: rely on struct proc being type-stable (i.e. never being >freed) and also store the pointer. You can always safely PROC_LOCK it, do >checks to see the proc is alive and has the right timestamp... Hmm, so you are saying that every element of the proc_zone always has a val= id p_mtx field in it that can be safely PROC_LOCK()'d no matter if the element refers to a process at that time? I would also need help with the code to determine if the structure refers t= o a process that currently exists with the same pid and creation time. I suppose saving "p" with the lock/open owner string and then doing what yo= u suggest is possible, but it would take some work. For now, I can just grab all the pidhashtbl_locks once/sec and fix head so = it works. rick From owner-freebsd-current@freebsd.org Thu Apr 11 04:56:25 2019 Return-Path: Delivered-To: freebsd-current@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 42C0A157930D for ; Thu, 11 Apr 2019 04:56:25 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qt1-x844.google.com (mail-qt1-x844.google.com [IPv6:2607:f8b0:4864:20::844]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 539EF755CF; Thu, 11 Apr 2019 04:56:24 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qt1-x844.google.com with SMTP id x12so5655250qts.7; Wed, 10 Apr 2019 21:56:24 -0700 (PDT) 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=4IlXWQvua4jRPpwdq0PM5BLSerUNgV8opYEEXaTCgJg=; b=lVML4VvkZ1j+MkFw2BnuDhuV0LBbziSZxNSP2HBoxAjNgoGIO4W+gpGak6D/eqy6mD XPY1bO/hcsnRw2eoYjhQ8A5jX+wWhXfR/hUw/PT5DyqeabGlfN4U7gjNxntOf4JteBtp 8Y4pdZZzCBbMIDpufPF9zx0ZGvjusmKaDDo3wd15mwomYJD77hhyAbWXLOAx4wiZGyen eFFj1iDuphiXtn66tzf0nYzaFE5mg937XCk23ppyKnTwbY2PM0TJ0z7G2Pt+xSh+0S8t 8+d/1wvYL9WE5jKpmlCGSlwFi6iI1K4DnIGp0VtM9v8ul0qSCCEUk5AQLloXCutb6O24 0HNQ== 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=4IlXWQvua4jRPpwdq0PM5BLSerUNgV8opYEEXaTCgJg=; b=r2LGZ7QAB+xRg1J7rNh/4cTbx4AxAcA2IN5ClLa3KKrfcShPKxmtesiRjBL0RJqnz8 kpRtJ5T0rOYFe/jJ+1S1ZnYYf+70ALro0tqtXgMY8pnlBOhFCldcOcixNEsbyuEzqcVf OO1t2GujYwBRtOvDANa55Lgm6MyCjRLriVvVqlQixQpmS78SR2Qg5zUph5UCnIKcH2xM Vhqe4EJhZQeAJ4EmLQHRJ9AvjK2EVwjiBEN+hLxtcZlLuHVFzqql2yLKBJRruOUnXI9F yavNgWiq/+XDTAKafYvyiVFKEU/FDf5RW6tbYR0dqa82oa4IlSwbMGNIuiWYLQTC1U/x x3TQ== X-Gm-Message-State: APjAAAVz32bOV0wNB175d9zToQXrYkc3o9VKsGq5VNpUIHNz/jGJzb83 /cZhYANz8RMEShPx+VDU9MV7YE2lzh7Stsq7VPc= X-Google-Smtp-Source: APXvYqxsPG21krDxMubb9+J8EAbADPbIC1HGqb8bO+JBcDLaF13Ri9Dq6aGxA4MXO6sbFAa1D6XlUQ/jGdLMWb1Ec+M= X-Received: by 2002:ac8:27b0:: with SMTP id w45mr39715019qtw.341.1554958583526; Wed, 10 Apr 2019 21:56:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:3353:0:0:0:0:0 with HTTP; Wed, 10 Apr 2019 21:56:22 -0700 (PDT) In-Reply-To: References: From: Mateusz Guzik Date: Thu, 11 Apr 2019 06:56:22 +0200 Message-ID: Subject: Re: Do the pidhashtbl_locks added by r340742 need to be sx locks? To: Rick Macklem Cc: "kib@freebsd.org" , "freebsd-current@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 539EF755CF X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=lVML4Vvk; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mjguzik@gmail.com designates 2607:f8b0:4864:20::844 as permitted sender) smtp.mailfrom=mjguzik@gmail.com X-Spamd-Result: default: False [-2.80 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.16)[-0.159,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.63)[ip: (2.07), ipnet: 2607:f8b0::/32(-2.96), asn: 15169(-2.19), country: US(-0.06)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2019 04:56:25 -0000 On 4/11/19, Rick Macklem wrote: > Mateusz Guzik wrote: >>On 4/11/19, Rick Macklem wrote: >>> Hi, >>> >>> I finally got around to looking at what effect replacing pfind_locked() >>> with >>> pfind() has for the NFSv4 client and it is broken. >>> >>> The problem is that the NFS code needs to call some variant of "pfind()" >>> while >>> holding a mutex lock. The current _pfind() code uses the >>> pidhashtbl_locks, >>> which are "sx" locks. >>> >>> There are a few ways to fix this: >>> 1 - Create a custom version of _pfind() for the NFS client with the >>> sx_X() >>> calls >>> removed, plus replace the locking of allproc_lock with locking of >>> all >>> the >>> pidhashtbl_locks, so that the "sx" locks are acquired before the >>> mutex. >>> --> Not very efficient, but since it is only done once/sec, I can >>> live >>> with it. >>> 2 - Similar to the above, but still lock the allproc_lock and use a loop >>> of >>> FOREACH_PROC_IN_SYSTEM(p) instead of a hash list for the pid in the >>> custom pfind(). (I don't know if this would be preferable to >>> locking >>> all >>> the pidhashtbl_locks for other users of pfind()?) >>> 3 - Convert the pidhashtbl_locks to mutexes. Then the NFS client doesn't >>> need >>> to acquire any proc related locks and it just works. >>> I can't see anywhere that "sleeps" while holding the >>> pidhashtbl_locks, >>> so I >>> think they can be converted, although I haven't tried it yet? >>> >>> From my perspective, #3 seems the better solution. >>> What do others think? >>> >> >>Changing the lock type to rwlock may be doable and worthwhile on its own, >>but I don't think it would constitute the right fix. >> >>Preferably there would be an easy to use mechanism which allows >>registering per-process callbacks. Currently it can be somewhat emulated >>with EVENTHANDLERs, but it would give calls for all exiting processes, not >>only the ones of interest. Then there would be no need to periodically >>scan as you would always get notified on process exit. > Long ago when I first did the NFSv4 code for OpenBSD2.6, I had a callback > function > pointer in "struct proc" which the NFS code set non-null to get a callback. > { The code still has remnants of that because it still has > nfscl_cleanup_common(), > which was code shared by that callback and this approach which was used > for > the Mac OS X port, where I couldn't change "struct proc". } > I have never added anything like that for FreeBSD, but I suppose we could > look > at doing it that way. > To be honest, since the current code works fine and can be difficult to test > well, > I hesitate to change to using a callback. > >>Note the current code does not ref processes it is interested in any >>manner and just performs a timestamp check to see if it got the one it >>expected (with pid reuse in mind). >> >>So I think a temporary hack which will do the trick will take the current >>approach further: rely on struct proc being type-stable (i.e. never being >>freed) and also store the pointer. You can always safely PROC_LOCK it, do >>checks to see the proc is alive and has the right timestamp... > Hmm, so you are saying that every element of the proc_zone always has a > valid > p_mtx field in it that can be safely PROC_LOCK()'d no matter if the element > refers to a process at that time? > I would also need help with the code to determine if the structure refers > to > a process that currently exists with the same pid and creation time. You can just: PROC_LOCK(p); if (p->p_state != PRS_NORMAL) { /* it's not the one you want, bail */ } /* the current timestamp check goes here */ PROC_UNLOCK(p); > > I suppose saving "p" with the lock/open owner string and then doing what > you > suggest is possible, but it would take some work. > > For now, I can just grab all the pidhashtbl_locks once/sec and fix head so > it works. > -- Mateusz Guzik