From owner-freebsd-hackers@freebsd.org Mon Dec 26 20:37:03 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45FECC91FA3 for ; Mon, 26 Dec 2016 20:37:03 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 CDFC61809 for ; Mon, 26 Dec 2016 20:36:59 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190f-667ff70000005a18-46-58617e342033 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 7C.18.23064.43E71685; Mon, 26 Dec 2016 15:31:49 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id uBQKVmv2006960; Mon, 26 Dec 2016 15:31:48 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uBQKVjZB015799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Dec 2016 15:31:47 -0500 Date: Mon, 26 Dec 2016 14:31:45 -0600 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: frebsd-current@FreeBSD.org Subject: second call for 2016Q4 status reports Message-ID: <20161226203144.GZ8460@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLIsWRmVeSWpSXmKPExsUixG6nrmtalxhhcHuWicW5fVPYLbZv/sfo wOQx49N8lgDGKC6blNSczLLUIn27BK6M1VO3MBYs4a5onDeJvYFxM2cXIyeHhICJRPPDH0xd jFwcQgJtTBKPXk9hg3A2MkocbDkLlbnKJPF84n52kBYWAVWJ3qXzmUFsNgE1ifUrroHZIgLy Evua3gPVcHAwC8hJHLlsBxIWFtCTmHd+F1gJr4CxRPvp6UwQtqDEyZlPWEBsZgEtiRv/XjJB tEpLLP/HARIWFVCWaJjxgHkCI98sJB2zkHTMQuhYwMi8ilE2JbdKNzcxM6c4NVm3ODkxLy+1 SNdELzezRC81pXQTIyjUOCX5dzDOafA+xCjAwajEw1vBnRAhxJpYVlyZe4hRkoNJSZT3vEpi hBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3qZaoBxvSmJlVWpRPkxKmoNFSZz3UqZ7hJBAemJJ anZqakFqEUxWhoNDSYLXEqRRsCg1PbUiLTOnBCHNxMEJMpwHaHg+2PDigsTc4sx0iPwpRkUp cd4pIAkBkERGaR5cLygVSGTvr3nFKA70ijCvAUgVDzCNwHW/AhrMBDRYvz4eZHBJIkJKqoGR paomPO//5gCVj7t5V9+98YQv5/xlkzmSs5i3rhN7v+GOr82S5HV/HjHO63+y70XnJKZrYRyn yx2K5/GzW33ZWMVV8M71AofZeqFnPKdf8soExAc9uDV10XaB1PN8jjs5O4wj14v/YPKbe2Xr /GtTJD6YMyyY/top6KDuiqsWzSlJF5ckls9SVGIpzkg01GIuKk4EAKw/TJvgAgAA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2016 20:37:03 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2016, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about work that is underway and completed. Submission of reports is not restricted to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly@FreeBSD.org . (Do be sure, though, to save the form output and not the form itself!) There is also an XML template [2] that can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We look forward to seeing your 2016Q4 reports! Happy Holidays, Ben (on behalf of monthly@) [1] https://www.FreeBSD.org/cgi/monthly.cgi [2] https://www.FreeBSD.org/news/status/report-sample.xml [3] https://www.FreeBSD.org/news/status/howto.html [4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html [5] https://www.FreeBSD.org/news/status/report-2016-07-2016-09.html From owner-freebsd-hackers@freebsd.org Mon Dec 26 23:22:37 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDC45C9283D for ; Mon, 26 Dec 2016 23:22:37 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79B2C16C4; Mon, 26 Dec 2016 23:22:37 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 28BC121C9CF; Mon, 26 Dec 2016 23:22:27 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: on BIOS problems with disks larger than 2 TB From: Stefan Bethke In-Reply-To: <490347865.SvN7iQoFWI@ralph.baldwin.cx> Date: Tue, 27 Dec 2016 00:22:25 +0100 Cc: Andriy Gapon , John Baldwin Content-Transfer-Encoding: quoted-printable Message-Id: <3BF31AE6-BA3D-498A-9203-500C75F957C5@lassitu.de> References: <6cec427b-4df1-50f0-3014-a96e5f8210f5@FreeBSD.org> <490347865.SvN7iQoFWI@ralph.baldwin.cx> To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2016 23:22:38 -0000 > Am 12.08.2016 um 21:18 schrieb John Baldwin : >=20 > On Tuesday, August 02, 2016 04:35:23 PM Andriy Gapon wrote: >>=20 >> There are some BIOSes out there that do not properly support disks >> larger than 2TB and cause boot problems if there is any data required >> for boot at offsets larger than 2 TB (TiB, rather). >>=20 >> The most typical victim is the ZFS boot if a boot pool includes disk >> areas beyond 2TB, because a kernel, or zfsloader or any configuration >> files required by the loader may end up in those "inaccessible" = areas. >>=20 >> It's obvious why 2TiB is a magic value here: >> 2^32 * 512 =3D 2^41 =3D 2 * 2^40 >> So the problem seems to happen when an LBA is treated as a 32-bit >> integer (unsigned). >>=20 >> I happen to own one of affected systems and I have done some more >> investigation. As far as I can see, the only actual problem in my = case >> is that a disk size in 512b sectors is reported modulo 2^32 by INT = 13h >> AH=3D48h. If I "fix up" the parameter, then everything else (i.e. = actual >> data reads) seems to work just fine after that. >>=20 >> I suspect that a large subclass of other problematic systems may have >> exactly the same problem. >>=20 >> Does anyone have an idea about how we could auto-detect and and >> auto-correct that problem? >> Would that be worth the trouble at all? Given the gradual = de-orbiting >> of BIOS systems. >=20 > Hmm, I'm not sure how easy it is to handle this case (i.e. how do you = know > if an LBA beyond the size is really legit due to truncation vs coming = from > corrupted metadata). Related is that tsoome's bcache stuff wants to = know > where the end of the disk is (to avoid reading off the end), so just > ignoring the size is not easy. Having just been bitten by this, an early indication that the BIOS is = deficient would be most welcome. I have two systems (Asus P6-P8H61E) which BIOS seems to be limited to 2 = TB. For about two years, everything seemed to be fine, until the latest = make world, when the new loader, kernel, and modules suddenly ended up = too far back on the disk: All buffers synced. Uptime: 32d4h27m58s re0: link state changed to DOWN re0: link st/boot/config: -DhS115200 ZFS: i/o error - all block copies unavailable Invalid format FreeBSD/x86 boot Default: tank/be/default:/boot/kernel/kernel boot:=20 ZFS: i/o error - all block copies unavailable Invalid format Of course, the systems are remote and I can=E2=80=99t access them = physically easily. Luckily, I did manage to loader the old loader and kernel, and could = bring the system up again, but I will need to try to update the BIOS on = the machine, or even create a root ZFS pool that is far enough forward = on the main disk. If the BIOS limitation cannot be worked around, gptboot/gptzfsboot = should at least try and read (for example) the backup GPT. This way, = they could emit a warning that parts of the disk are not accessible = through the BIOS, and that future boots might suddenly stop working. If = I had known that the BIOS had this problem when I was setting up these = systems, I could have easily created a root pool and a separate data = pool, instead of just a root pool. Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-hackers@freebsd.org Wed Dec 28 11:55:22 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19A8BC94CD5 for ; Wed, 28 Dec 2016 11:55:22 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A49B110D3 for ; Wed, 28 Dec 2016 11:55:21 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id a197so280750012wmd.0 for ; Wed, 28 Dec 2016 03:55:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=gxPuUEHn5mMKEHY6jbUOkk2PH4In4e1R887n0wXfdqk=; b=idFsuOzIhOQxQN21bdKcG2CQAE1EyTXspW+RQFsg/zUiWqeukXU1DXOg9Spsg3PHN5 h9PzZdn/kNJEvFxNFlwrDgAORuR+67RKhhDMDuutv6rr4rsfZdfHkRZ81Nh5mkO3aWu1 +ZijH7aucWzOhABHzAaHP6F0LAupuf/6XsuKGr2vKVZukzwyWEg7tsXvEYpPhV2DAI0a FcCu+G9IraBppy0s8SP+4liQX1v14qEWDXIfcE/TNuk31eHGKm3RFTfL/aTwWiJJCpv5 vsjjZ347EnAFQ+5wYSOHDggR8foeweyHCLpsTpnwK0S8sJY1ExVB9zarfJ/6n5A4xmvq 9sGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=gxPuUEHn5mMKEHY6jbUOkk2PH4In4e1R887n0wXfdqk=; b=ki1UqEpZ69UEvp+pfFiUE3SN3taweH9QMWzGSRfgnR0FfI0rIsWVUgOIdRVRlo40gl ZqjCSjmL1VBtrfchkJLsvkkMRuqycokoQfzTSVSgrz4V77v8p8oJT6ZxAtGFrTzROr6G b1THeXIWcfoqU8HIQYDYsIRwGXT23GGmiAswbcBcEjr7wrhySBNnExOnPNZKLtJ3uTOK HfF6tNF1/zH/DlAO3/0romImOVgHZgG0oYJX2VBGMZ2jYvQbxdSMNzmA5EdvHZUBloy3 KC92U+R5W2VMkC+zSjjTJU9Ru1xHezKrH7dGhzXlW6c14xSjgazbNJuqsoW3oNiI5upr 58Jg== X-Gm-Message-State: AIkVDXKL69zPYonHtaP/5n67FhgJFf33/gp4jsQeG84kzaP3uxYwCU56HYDHflrzhV8Y3g== X-Received: by 10.28.175.204 with SMTP id y195mr33981980wme.106.1482926120000; Wed, 28 Dec 2016 03:55:20 -0800 (PST) Received: from [192.168.2.30] ([2.190.151.123]) by smtp.googlemail.com with ESMTPSA id d184sm60782081wmd.8.2016.12.28.03.55.17 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 28 Dec 2016 03:55:18 -0800 (PST) Message-ID: <5863A822.7050000@gmail.com> Date: Wed, 28 Dec 2016 15:25:14 +0330 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: FreeBSD Hackers Subject: wlan interface parent Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 11:55:22 -0000 Hi What is the right method to get the parent device name of a given WLAN interface in userland code? I could not find any relevant ioctl command in . Thanks. -- Best regards Hooman Fazaeli From owner-freebsd-hackers@freebsd.org Wed Dec 28 12:03:30 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7FB6C93BE7 for ; Wed, 28 Dec 2016 12:03:30 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 816FA1C7F for ; Wed, 28 Dec 2016 12:03:30 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-wm0-x233.google.com with SMTP id k184so111957368wme.1 for ; Wed, 28 Dec 2016 04:03:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3K99gdRB365JgELySC44gAjYBku9bjuo15yxBZkW1rg=; b=kghLIbi7tCovnAqm6RHeEgfI4uvWkiwfgFPD+1hATDOno7QNu1UArFdbvEOBp3vAzd cmEhy3o1bQlameXAESJ1VuIQH5blMj6YERDlvdu4w0mfoQk1FO/FFMuAkQTJGXMduER9 z0yLi8srKkV/EJzZDwfzufOAvca8+YWpmHzb/DHX/WkBKaYIK+FMyHJRRlH1z6+5MNuG DC41WvfaGE8n0icH+OFtraIb5WqgOL5BP9V6/B9sQqcPYEWGEr3Rhpq1SM4z2EyXRYmv NiZDk0Uf/3q5T0s8HwRQr6zg7DNmsR2xlxOJnkIm6EYjuacjdZqylp6XvASEAP/FH41L CiZg== 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=3K99gdRB365JgELySC44gAjYBku9bjuo15yxBZkW1rg=; b=ifoC2PEevOlu8uum8gNGI/D1w9WGvYa+5sO+6joI5Gbkob1T6ET9uAhB9DQovI0Qia uq8tJAtwwHCfDPwM80+v7OZIXo+ZdpyotroGr8v4Nhu2fj+SmfNubJXVWH6iQOHcNYSf XdbKrymhyJMExRyPwypkBplea8coUAcjEHb3+89YqirGzi1p2TtOK2Sd+tHaDrSlGBTl lwnimOKPqDnEBVPi/Rjw22angU8U+v3OeJ8+Ve9kaaH7I7ljPWtQ4bWb0DsF1TzLfsXd X4SGq08IaIX9FpYGIzQrkTc0uyG4SFaHbgujAVNPYCAp7J0GGtLsMbv4QJM3JFA1Wost Yqlw== X-Gm-Message-State: AIkVDXLHVF5er4IlVS6HVEWBnOSMLLPSiB7YrgSzOncxfpEC2wYSP51C/2DcgIeQuLSpVI3q8sM1QlzN9dQLlsms X-Received: by 10.28.143.20 with SMTP id r20mr33210385wmd.2.1482926609052; Wed, 28 Dec 2016 04:03:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.227.165 with HTTP; Wed, 28 Dec 2016 04:03:28 -0800 (PST) In-Reply-To: <5863A822.7050000@gmail.com> References: <5863A822.7050000@gmail.com> From: Oliver Pinter Date: Wed, 28 Dec 2016 13:03:28 +0100 Message-ID: Subject: Re: wlan interface parent To: Hooman Fazaeli Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 12:03:31 -0000 Hi! On Wed, Dec 28, 2016 at 12:55 PM, Hooman Fazaeli wrote: > Hi > > What is the right method to get the parent device name of a given > WLAN interface in userland code? I could not find any relevant ioctl > command in . Try with sysctls if you want to detect the name from script of user-space op@blackbird ~> sysctl -d net.wlan.devices net.wlan.devices: names of available 802.11 devices op@blackbird ~> sysctl net.wlan.devices net.wlan.devices: iwm0 op@blackbird ~> sysctl net.wlan.0.%parent net.wlan.0.%parent: iwm0 op@blackbird ~> > > Thanks. > > -- > Best regards > Hooman Fazaeli > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Wed Dec 28 18:12:09 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E974C95D7B for ; Wed, 28 Dec 2016 18:12:09 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) (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 097F71E7E for ; Wed, 28 Dec 2016 18:12:08 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.11/8.12.11) with ESMTP id uBSHj9Ml048262 for ; Wed, 28 Dec 2016 12:45:10 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.11/8.12.11/Submit) id uBSHj9X4048261 for freebsd-hackers@freebsd.org; Wed, 28 Dec 2016 12:45:09 -0500 (EST) (envelope-from wayne) Date: Wed, 28 Dec 2016 12:45:09 -0500 From: Michael Wayne To: freebsd-hackers@freebsd.org Subject: ZFS failure leads to panic/boot loop Message-ID: <20161228174509.GR32352@manor.msen.com> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 18:12:09 -0000 11.0 server installed from initial setup with ZFS mirrored drives. Ran fine for a few weeks sitting in the rack, then became unresponsive. Plugging in a console showed it was in a panic / boot loop due to ZFS. Would like suggestions on what is wrong that caused this problem as well as how to proceed to recover from it. Typing this from a phone photo of the console screen so showing only what I believe to be relevant; I can supply actual addresses if required. Boot gets to: [...] uhub2: 4 ports... panic: Solaris(panic) blkptr at 0xfffffe0003244b80 has invalid CHECKSUM 0 cpuid - 0 KDB: stack backtrace [...] zfs_panic_recover zfs_blkptr_verify zio_read spa_load_verify From owner-freebsd-hackers@freebsd.org Wed Dec 28 19:54:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4D5CC95D98 for ; Wed, 28 Dec 2016 19:54:33 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9DBE11B1B for ; Wed, 28 Dec 2016 19:54:33 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9A1EDC95D97; Wed, 28 Dec 2016 19:54:33 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97E0FC95D96 for ; Wed, 28 Dec 2016 19:54:33 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1121B1B1A for ; Wed, 28 Dec 2016 19:54:32 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from beeb.leiden.webweaving.org (5ED29A06.cm-7-3c.dynamic.ziggo.nl [94.210.154.6]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id uBSJfpiT026103 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 28 Dec 2016 20:41:53 +0100 (CET) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED29A06.cm-7-3c.dynamic.ziggo.nl [94.210.154.6] claimed to be beeb.leiden.webweaving.org From: Dirk-Willem van Gulik Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall Message-Id: Date: Wed, 28 Dec 2016 20:41:51 +0100 To: FreeBSD Hackers X-Mailer: Apple Mail (2.3259) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Wed, 28 Dec 2016 20:41:53 +0100 (CET) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 19:54:33 -0000 On a default ZFS install (late 2014, 10.x) of a few years hence it seems = sysinstall selected 64k as the default size of partition 1: with the = bootblock: sudo gpart show =3D> 34 7814037101 ada0 GPT (3.6T) 34 6 - free - (3.0K) 40 128 1 freebsd-boot (64K) 168 67108864 2 freebsd-swap (32G) 67109032 7746928096 3 freebsd-zfs (3.6T) 7814037128 7 - free - (3.5K) =E2=80=A6. lots of disks snipped =E2=80=A6.. =3D> 34 7814037101 ada35 GPT (3.6T) 34 6 - free - (3.0K) 40 128 1 freebsd-boot (64K) 168 67108864 2 freebsd-swap (32G) 67109032 7746928096 3 freebsd-zfs (3.6T) 7814037128 7 - free - (3.5K) Fair to assume that this (the 64k) is the reason that from 11.x onwards;=20= gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0=20 fails with an immediate: gpart: /dev/ada1p1: not enough space=20 as gptzfsboot has grown in recent years to something towards the 90k = mark ? -r--r--r-- 1 root wheel 88898 Dec 24 11:52 /boot/gptzfsboot =09 And I guess avoiding a rebuild would mean something like gently = disabling swap; shifting partition 1 & 2 carefully an so on ? Or is = there a more clever way? ZFS has *already* been upgraded. Or am I missing something ? Thanks, Dw= From owner-freebsd-hackers@freebsd.org Wed Dec 28 21:13:15 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13C00C953E9 for ; Wed, 28 Dec 2016 21:13:15 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 EC33B1DC0 for ; Wed, 28 Dec 2016 21:13:14 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id A6F5FDF22 for ; Wed, 28 Dec 2016 21:04:17 +0000 (UTC) Subject: Re: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall To: freebsd-hackers@freebsd.org References: From: Allan Jude Message-ID: <068c90c2-61c0-2fbc-3984-0bc937e19d63@freebsd.org> Date: Wed, 28 Dec 2016 16:04:17 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 21:13:15 -0000 On 2016-12-28 14:41, Dirk-Willem van Gulik wrote: > On a default ZFS install (late 2014, 10.x) of a few years hence it seems sysinstall selected 64k as the default size of partition 1: with the bootblock: > > sudo gpart show > => 34 7814037101 ada0 GPT (3.6T) > 34 6 - free - (3.0K) > 40 128 1 freebsd-boot (64K) > 168 67108864 2 freebsd-swap (32G) > 67109032 7746928096 3 freebsd-zfs (3.6T) > 7814037128 7 - free - (3.5K) > > …. lots of disks snipped ….. > > => 34 7814037101 ada35 GPT (3.6T) > 34 6 - free - (3.0K) > 40 128 1 freebsd-boot (64K) > 168 67108864 2 freebsd-swap (32G) > 67109032 7746928096 3 freebsd-zfs (3.6T) > 7814037128 7 - free - (3.5K) > > Fair to assume that this (the 64k) is the reason that from 11.x onwards; > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > > fails with an immediate: > > gpart: /dev/ada1p1: not enough space > > as gptzfsboot has grown in recent years to something towards the 90k mark ? > > -r--r--r-- 1 root wheel 88898 Dec 24 11:52 /boot/gptzfsboot > > And I guess avoiding a rebuild would mean something like gently disabling swap; shifting partition 1 & 2 carefully an so on ? Or is there a more clever way? ZFS has *already* been upgraded. > > Or am I missing something ? > > Thanks, > > Dw > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > swapoff -a; gpart resize ...; swapon -a is likely your best bet. The other option is to rebuild gptzfsboot without GELI support, and then it will be under 64 KB. -- Allan Jude From owner-freebsd-hackers@freebsd.org Thu Dec 29 11:53:09 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCF25C96458 for ; Thu, 29 Dec 2016 11:53:09 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 8E5431B6D for ; Thu, 29 Dec 2016 11:53:09 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cMZGc-0002rc-9E for freebsd-hackers@freebsd.org; Thu, 29 Dec 2016 14:53:06 +0300 Date: Thu, 29 Dec 2016 14:53:06 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org Subject: DCI support Message-ID: <20161229115306.GJ37118@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 11:53:09 -0000 Intel Skylake CPU have DCI access to JTAG. Is posible to use this under FreeBSD? From owner-freebsd-hackers@freebsd.org Thu Dec 29 11:59:31 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 592C9C96730 for ; Thu, 29 Dec 2016 11:59:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 1F9F71EA5 for ; Thu, 29 Dec 2016 11:59:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cMZ7F-0002ZX-17 for freebsd-hackers@freebsd.org; Thu, 29 Dec 2016 14:43:25 +0300 Date: Thu, 29 Dec 2016 14:43:24 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org Subject: loader.conf from loader prompt Message-ID: <20161229114324.GI37118@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 11:59:31 -0000 I am need set/unset some values (from loader.conf) from loader prompt. Or add content of some file to loader.conf from loader prompt. Or interactivly enable/disable some lines from loader.conf Is this posible? From owner-freebsd-hackers@freebsd.org Thu Dec 29 14:40:58 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4C2FC95F75 for ; Thu, 29 Dec 2016 14:40:58 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 B0696163C for ; Thu, 29 Dec 2016 14:40:58 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 88EF720B72; Thu, 29 Dec 2016 09:40:57 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Thu, 29 Dec 2016 09:40:57 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=lo /KPBFWM2CYowuwAi2PoOMiYVg=; b=cd71YsP2jsKKubvQwhaNlcrWV18aS9YqKR WtaStR3wBunz7VqdUqpJze8UjiT9LGMQeWbbOmot7Pkq+TerpjOQ3QsEP9OJyHXY nerEu1pykC6ZbT5otsbi/EbgTWvpvyhWw+AGn5SoE7W0dvNYoVokHOArHCGfgbn+ D9AdodJGQ= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 626D59EE25; Thu, 29 Dec 2016 09:40:57 -0500 (EST) Message-Id: <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> From: Mark Felder To: Slawa Olhovchenkov , freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-9c115fcf Date: Thu, 29 Dec 2016 08:40:57 -0600 References: <20161229114324.GI37118@zxy.spb.ru> Subject: Re: loader.conf from loader prompt In-Reply-To: <20161229114324.GI37118@zxy.spb.ru> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 14:40:58 -0000 On Thu, Dec 29, 2016, at 05:43, Slawa Olhovchenkov wrote: > I am need set/unset some values (from loader.conf) from loader prompt. > Or add content of some file to loader.conf from loader prompt. > Or interactivly enable/disable some lines from loader.conf > > Is this posible? > Yes. Check the loader(8) man page or the "help" command at the loader prompt. -- Mark Felder ports-secteam member feld@FreeBSD.org From owner-freebsd-hackers@freebsd.org Thu Dec 29 14:45:25 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53B26C961A8 for ; Thu, 29 Dec 2016 14:45:25 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 300FF19B7 for ; Thu, 29 Dec 2016 14:45:24 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D781B20842 for ; Thu, 29 Dec 2016 09:45:23 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Thu, 29 Dec 2016 09:45:23 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=yoBMFPKPhrppFLpk0jsmhWSfp aU=; b=JBzkOD1dSJ6s0A38NeWf6Z7l1e36VEbzmlrVVbFsHhPG3BcLZdTpKibM8 S0chvdcblcHe/jdNER88cR804je4CTrc8x3APtZPZME+PiSY82IgWncRjOk92kNt 0MTrEZX20y8Qxn5pvzGlSoZepjIL5iqFuwA8QY9YVEc7XyTgxc= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id AE1F19EE25; Thu, 29 Dec 2016 09:45:23 -0500 (EST) Message-Id: <1483022723.3853404.832175825.1897001A@webmail.messagingengine.com> From: Mark Felder To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-9c115fcf Date: Thu, 29 Dec 2016 08:45:23 -0600 Subject: vm.kmem_size_scale tunable only accepts whole numbers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 14:45:25 -0000 Hello, Is there a reason why vm.kmem_size_scale only accepts whole numbers? FreeNAS sets vm.kmem_size to 1.25*hw.realmem, but a smarter way of setting this would to be able to use vm.kmem_size_scale with rational numbers. Thanks! -- Mark Felder ports-secteam member feld@FreeBSD.org From owner-freebsd-hackers@freebsd.org Thu Dec 29 14:53:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE43DC9642E for ; Thu, 29 Dec 2016 14:53:06 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 91CF81E2F; Thu, 29 Dec 2016 14:53:06 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cMc4m-0007s4-LK; Thu, 29 Dec 2016 17:53:04 +0300 Date: Thu, 29 Dec 2016 17:53:04 +0300 From: Slawa Olhovchenkov To: Mark Felder Cc: freebsd-hackers@freebsd.org Subject: Re: loader.conf from loader prompt Message-ID: <20161229145304.GK37118@zxy.spb.ru> References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 14:53:06 -0000 On Thu, Dec 29, 2016 at 08:40:57AM -0600, Mark Felder wrote: > > > On Thu, Dec 29, 2016, at 05:43, Slawa Olhovchenkov wrote: > > I am need set/unset some values (from loader.conf) from loader prompt. > > Or add content of some file to loader.conf from loader prompt. > > Or interactivly enable/disable some lines from loader.conf > > > > Is this posible? > > > > Yes. Check the loader(8) man page or the "help" command at the loader > prompt. Already did, don't help. For example, what I need enter in loader prompt for next equalent: == mfsroot_load="YES" mfsroot_type="md_image" mfsroot_name="/boot/md.img" == set mfsroot_load="YES" set mfsroot_type="md_image" set mfsroot_name="/boot/md.img" boot don't work. `load -t md_image /boot/md.img` can't be before kernel load. What I am missing? From owner-freebsd-hackers@freebsd.org Thu Dec 29 19:18:18 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E2D8C96FF5 for ; Thu, 29 Dec 2016 19:18:18 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 732601B4C for ; Thu, 29 Dec 2016 19:18:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 6d1b3ee0-cdfb-11e6-8c89-112185c90658 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 6d1b3ee0-cdfb-11e6-8c89-112185c90658; Thu, 29 Dec 2016 19:17:23 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBTJH8S8001739; Thu, 29 Dec 2016 12:17:09 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483039028.16152.54.camel@freebsd.org> Subject: Re: loader.conf from loader prompt From: Ian Lepore To: Slawa Olhovchenkov , Mark Felder Cc: freebsd-hackers@freebsd.org Date: Thu, 29 Dec 2016 12:17:08 -0700 In-Reply-To: <20161229145304.GK37118@zxy.spb.ru> References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> <20161229145304.GK37118@zxy.spb.ru> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 19:18:18 -0000 On Thu, 2016-12-29 at 17:53 +0300, Slawa Olhovchenkov wrote: > On Thu, Dec 29, 2016 at 08:40:57AM -0600, Mark Felder wrote: > > > > > > > > > On Thu, Dec 29, 2016, at 05:43, Slawa Olhovchenkov wrote: > > > > > > I am need set/unset some values (from loader.conf) from loader > > > prompt. > > > Or add content of some file to loader.conf from loader prompt. > > > Or interactivly enable/disable some lines from loader.conf > > > > > > Is this posible? > > > > > Yes. Check the loader(8) man page or the "help" command at the > > loader > > prompt. > Already did, don't help. > > For example, what I need enter in loader prompt for next equalent: > == > mfsroot_load="YES" > mfsroot_type="md_image" > mfsroot_name="/boot/md.img" > == > > set mfsroot_load="YES" > set mfsroot_type="md_image" > set mfsroot_name="/boot/md.img" > boot > > don't work. > > `load -t md_image /boot/md.img` can't be before kernel load. > > What I am missing? > I don't know of an easy way to do this... it seems like it should be possible to make the forth interpreter read and act on another config file by entering some command at the prompt, but I see nothing about that in the docs, and I've never been able to read forth code. To do it the hard way, first do "load kernel" then do the "load -t md_image" as you show above, then you should be able to do "boot" and have it load any other foo_load=YES modules and start. -- Ian From owner-freebsd-hackers@freebsd.org Thu Dec 29 19:22:28 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72D09C962B4 for ; Thu, 29 Dec 2016 19:22:28 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 4FD331063 for ; Thu, 29 Dec 2016 19:22:28 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 73081D8A0 for ; Thu, 29 Dec 2016 19:22:26 +0000 (UTC) Subject: Re: loader.conf from loader prompt To: freebsd-hackers@freebsd.org References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> <20161229145304.GK37118@zxy.spb.ru> From: Allan Jude Message-ID: <4e00321e-75bd-bec2-5d03-44aa0fb62298@freebsd.org> Date: Thu, 29 Dec 2016 14:22:22 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161229145304.GK37118@zxy.spb.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9QiRWVOH9KCL2JIQmiIsKxDMcGhaliqXC" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 19:22:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9QiRWVOH9KCL2JIQmiIsKxDMcGhaliqXC Content-Type: multipart/mixed; boundary="r7POc85Id9DnwNNj8g65hdjSFxa0cceLe"; protected-headers="v1" From: Allan Jude To: freebsd-hackers@freebsd.org Message-ID: <4e00321e-75bd-bec2-5d03-44aa0fb62298@freebsd.org> Subject: Re: loader.conf from loader prompt References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> <20161229145304.GK37118@zxy.spb.ru> In-Reply-To: <20161229145304.GK37118@zxy.spb.ru> --r7POc85Id9DnwNNj8g65hdjSFxa0cceLe Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-12-29 09:53, Slawa Olhovchenkov wrote: > On Thu, Dec 29, 2016 at 08:40:57AM -0600, Mark Felder wrote: >=20 >> >> >> On Thu, Dec 29, 2016, at 05:43, Slawa Olhovchenkov wrote: >>> I am need set/unset some values (from loader.conf) from loader prompt= =2E >>> Or add content of some file to loader.conf from loader prompt. >>> Or interactivly enable/disable some lines from loader.conf >>> >>> Is this posible? >>> >> >> Yes. Check the loader(8) man page or the "help" command at the loader >> prompt. >=20 > Already did, don't help. >=20 > For example, what I need enter in loader prompt for next equalent: > =3D=3D > mfsroot_load=3D"YES" > mfsroot_type=3D"md_image" > mfsroot_name=3D"/boot/md.img" > =3D=3D >=20 > set mfsroot_load=3D"YES" > set mfsroot_type=3D"md_image" > set mfsroot_name=3D"/boot/md.img" > boot >=20 > don't work. >=20 > `load -t md_image /boot/md.img` can't be before kernel load. >=20 > What I am missing? >=20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 To run loader commands from a file: include /path/to/file To see what variables are already set: show Read an additional/alternate loader.conf file: read-conf /path/to/file --=20 Allan Jude --r7POc85Id9DnwNNj8g65hdjSFxa0cceLe-- --9QiRWVOH9KCL2JIQmiIsKxDMcGhaliqXC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJYZWJyAAoJEBmVNT4SmAt+BjsP/A2sWkaRtaCo860V0srS3+rE TcV+T9AKuHjGfXCrvHXTo3r0waaMQBP6Q0PLZ8ltE8638e4g4ILYVRqumEbCHbUu vZ7im+e2nPCvKK7uCrGbhW5aaVXXHcIfye4ArihVSG8zP25ad2CdrjKEA1COeBv9 4hpv6HC1Ri81yyjR9MBUshi07+4Eb9n/ouGVKyyvajZnzlO2AmtQariyOXXHw6Zm rnTVbvUseiU4ypPK/7gELHVHFIvL6XQNV7OOQaKe0E1CCd3uflHsv/wt9YlOnBU8 e++3uBBKPocBi0pNZ68IRa5Cb3OLnCatClr+sbczYKqWZLzUV5yj5JuihVy2L1Es Emp3Ch9Qhx6l6Li1ZLBwYyLMBy6MrMzZMFlKccFZ8g85vy3rPojs+9pgYxurw9Ip CuaE0FLO637Se/KN0iR2efwh/hLURIOEObEBZz2GoHCrGs/NwJ8A5ghWBp5retzB ycKUOUvy/ohImyK7nFP3ITV7XyC1QSx6Sqa0ZmdSEpFXmlKt3+71ZUKQDciD52wJ Us4zryKvBHsyZxzuHT6ZJ11MfLvaJYX/sYm6vup8WXs+uJa8lwrrr/WVVF2mzr2A +lsDsGD3PWQIqWe0hmswaCfy/LtB6L8vQMXgnvukColv5+ftrXH7R25tyfNVjUAG EiHrRG4/51orVuxIpibH =1Amc -----END PGP SIGNATURE----- --9QiRWVOH9KCL2JIQmiIsKxDMcGhaliqXC-- From owner-freebsd-hackers@freebsd.org Thu Dec 29 19:57:37 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDF6EC96CF5 for ; Thu, 29 Dec 2016 19:57:37 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 5B85813A8 for ; Thu, 29 Dec 2016 19:57:36 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 081ad895-ce01-11e6-9357-bffcd86bd944 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 081ad895-ce01-11e6-9357-bffcd86bd944; Thu, 29 Dec 2016 19:57:32 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBTJvO86001799; Thu, 29 Dec 2016 12:57:24 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483041444.16152.57.camel@freebsd.org> Subject: Re: loader.conf from loader prompt From: Ian Lepore To: Allan Jude , freebsd-hackers@freebsd.org Date: Thu, 29 Dec 2016 12:57:24 -0700 In-Reply-To: <4e00321e-75bd-bec2-5d03-44aa0fb62298@freebsd.org> References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> <20161229145304.GK37118@zxy.spb.ru> <4e00321e-75bd-bec2-5d03-44aa0fb62298@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 19:57:37 -0000 On Thu, 2016-12-29 at 14:22 -0500, Allan Jude wrote: > On 2016-12-29 09:53, Slawa Olhovchenkov wrote: > > > > On Thu, Dec 29, 2016 at 08:40:57AM -0600, Mark Felder wrote: > > > > > > > > > > > > > > On Thu, Dec 29, 2016, at 05:43, Slawa Olhovchenkov wrote: > > > > > > > > I am need set/unset some values (from loader.conf) from loader > > > > prompt. > > > > Or add content of some file to loader.conf from loader prompt. > > > > Or interactivly enable/disable some lines from loader.conf > > > > > > > > Is this posible? > > > > > > > Yes. Check the loader(8) man page or the "help" command at the > > > loader > > > prompt. > > Already did, don't help. > > > > For example, what I need enter in loader prompt for next equalent: > > == > > mfsroot_load="YES" > > mfsroot_type="md_image" > > mfsroot_name="/boot/md.img" > > == > > > > set mfsroot_load="YES" > > set mfsroot_type="md_image" > > set mfsroot_name="/boot/md.img" > > boot > > > > don't work. > > > > `load -t md_image /boot/md.img` can't be before kernel load. > > > > What I am missing? > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freeb > > sd.org" > > > To run loader commands from a file: > include /path/to/file > > To see what variables are already set: > show > > Read an additional/alternate loader.conf file: > read-conf /path/to/file > > I can't see any evidence that read-conf does anything.  If I name a nonexistant file it doesn't complain.  If I name an existing file that does load_uftdi=YES, then doing a show afterwards doesn't show that variable being set, and the module doesn't get loaded. Forth is so... 1973.  I wonder what ever happened to the project to use lua as the loader command language? -- Ian From owner-freebsd-hackers@freebsd.org Thu Dec 29 20:04:49 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 158F8C96FB1 for ; Thu, 29 Dec 2016 20:04:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 E102419CE for ; Thu, 29 Dec 2016 20:04:48 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 0365871e-ce02-11e6-acc0-c7e6c9ad01d6 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 0365871e-ce02-11e6-acc0-c7e6c9ad01d6; Thu, 29 Dec 2016 20:04:32 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBTK4eU6001824; Thu, 29 Dec 2016 13:04:40 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483041880.16152.59.camel@freebsd.org> Subject: Re: loader.conf from loader prompt From: Ian Lepore To: Allan Jude , freebsd-hackers@freebsd.org Date: Thu, 29 Dec 2016 13:04:40 -0700 In-Reply-To: <1483041444.16152.57.camel@freebsd.org> References: <20161229114324.GI37118@zxy.spb.ru> <1483022457.3851552.832172593.724798DE@webmail.messagingengine.com> <20161229145304.GK37118@zxy.spb.ru> <4e00321e-75bd-bec2-5d03-44aa0fb62298@freebsd.org> <1483041444.16152.57.camel@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 20:04:49 -0000 On Thu, 2016-12-29 at 12:57 -0700, Ian Lepore wrote: > If I name an existing file that > does load_uftdi=YES Er, I mean of course uftdi_load=YES -- Ian From owner-freebsd-hackers@freebsd.org Thu Dec 29 20:45:11 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23AF8C96F64 for ; Thu, 29 Dec 2016 20:45:11 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C32ED146B for ; Thu, 29 Dec 2016 20:45:10 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id uBTKj3gY044413 for ; Thu, 29 Dec 2016 15:45:08 -0500 (EST) (envelope-from george+freebsd@m5p.com) To: freebsd-hackers@FreeBSD.org From: George Mitchell Subject: Even lighter weight directory protocol? Message-ID: Date: Thu, 29 Dec 2016 15:44:51 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OOD3lDInmX1C2HnVSmMGXSipbfDJQXVPd" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Thu, 29 Dec 2016 15:45:09 -0500 (EST) X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 20:45:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OOD3lDInmX1C2HnVSmMGXSipbfDJQXVPd Content-Type: multipart/mixed; boundary="KPopWmnxAvbXl1u7x0WEVm81tOJ3qLsp5"; protected-headers="v1" From: George Mitchell To: freebsd-hackers@FreeBSD.org Message-ID: Subject: Even lighter weight directory protocol? --KPopWmnxAvbXl1u7x0WEVm81tOJ3qLsp5 Content-Type: multipart/mixed; boundary="------------51975B6EE972367B05AE16F1" This is a multi-part message in MIME format. --------------51975B6EE972367B05AE16F1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I use NIS to propagate /etc/passwd and /etc/group, and really nothing else. I have been thinking about shifting to LDAP, to avoid some of the really embarrassing failure modes of NIS, except that I would like to kill the sadist who named this a "lightweight" protocol. I've thought about a simple cron/rsync job (and maybe that's what I'll do in the end). But are there any other directory-ish systems out there that are, let's say, bantamweight or flyweight? -- George --------------51975B6EE972367B05AE16F1-- --KPopWmnxAvbXl1u7x0WEVm81tOJ3qLsp5-- --OOD3lDInmX1C2HnVSmMGXSipbfDJQXVPd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlhldc8ACgkQwRES3m+p 4fmjSg/+PsNU30VKr5vgMv6QFiACz9loxqffjSnQkf16qi3XF8xEIdK2IhAExEXU vLqtAV4pJrpf6PXr6jWRHyECnt90LgfRR9b7tSP7Edk7x/Yc5ASf8GL1yBvgIPXK ZJvOs9yv2K7uslJdfQpw4AS1J9XNXw6QEobwON1mK1Fb1lhURNLxWbN8lcGyFJmO 30AYSp2QcS+DLHyBPuazK8+IbO6p6IgU4M0oW2/dbsRKx2uWRi7dGgiOUmMZIqxr JvsgiT/Sh0BtXpDeHr+Ro+EsNH6BNh6bfe7Us7AfgeTOkECMA6HUTtCOPvMTJtgW t/X5HcCU64hMZQpHcTQKG3g4YKIc767AvYMyyNO0sqEM4++Jaco65YBeT0nypsP2 V6mkOOxjvpWfi1C5NiUQEC1UcKuxuummP6GKKILhSGPTvYZK1tkbjIDJuPYLZupH IR4tLjJSvudHpRd2cupzEZClTm7XBWRajx/03k2v6o4JfwKsGX21ymHM6b6/Z4S/ lIVciNSILNYb7Q5SFG59e0ihux7T6knTHM7DoVQCU90749tOuJkrPZON9JfJKW0T p77tD+xgMsGB6pLhlqhJufIfky0Dh0oIVU7IfZ4000KyfCI1HUNrAI3Z0Zb/E+E7 zwvlpOaN+RhncG/PrZoM2EYvnaTbCWCG511MLkE7n1FoYSYd7UY= =ZH9D -----END PGP SIGNATURE----- --OOD3lDInmX1C2HnVSmMGXSipbfDJQXVPd-- From owner-freebsd-hackers@freebsd.org Thu Dec 29 20:50:18 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55DABC9618A for ; Thu, 29 Dec 2016 20:50:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AC7C1779 for ; Thu, 29 Dec 2016 20:50:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-qk0-x22a.google.com with SMTP id t184so281989064qkd.0 for ; Thu, 29 Dec 2016 12:50:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9Hz1iawqHRd4SROEoMk9m/bl8rCHVfc2t+lJnmpsRLM=; b=SkL/thURKuGmtlWs/2JXF24N5BnS61xHQLD0Kh+/uae3osqAKE/0xJR1HHT/I51nqi k3vWJpZI9LPlnDcynsuCDsJIEooqrwUh0bHhBUkeUItaf0XI83aDKAQt+dCHF+GXWcQE +sw3O1aT/Dcn6Zv9a2hedSU7txBnkwfFjbl1J9FIOm72Bds0LJagcgG2a/XCaeTnI/bO tUKAJLSRWbMFTmxBIe4RzGe3uNvHCWwLBQ+aqUl8y3QgLvQkstv2qqFtQwh5W1JBemmx H8fiCblTYFY806fxrz7io5d8pMKwO+9JYKQbR4bbcugvLdF11PWtHs91XLYEKi+VbJm7 BUtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9Hz1iawqHRd4SROEoMk9m/bl8rCHVfc2t+lJnmpsRLM=; b=PbH7gi4Q9cSWreyhxSZwJ4xj2Sq2Y7iriqzUEnKTpDXK1ddE7AVIG90hXttNVsCa1W Q2PI6HDh1btiiIR09GD0UncQwq5yba5lHHNjE4r8W6yMjDmkX0GQ//cPdD2EsGBXNd9X GNl67GCOp7/9f9BQF45pEIjLDDRsUgT4/0NRiUv864n2O2dc1hTLHxnTP/RFnLtJNtT0 ODieDqUj3/+ttwq7JkH2zg+u+tEMj4Dwb+vdv7/xWsDWWZ7ez4V/ARFp2QC/D+Lkvtgw 5g1C8fNZ7ZsHJxCta2bxr/FiEeao7xanM7KePKh6vhbvOKw1AlZiE/Pi/G8NLjNYJ7Aa 4DNA== X-Gm-Message-State: AIkVDXKCWiIjEauYXlz8dnO9SHrs+2KibOD8XJwAcLPwPuEboNoiB3tHe/ORK2ZGjpd8kKZ53rZGw2JK4jICKg== X-Received: by 10.55.66.73 with SMTP id p70mr47835504qka.63.1483044617297; Thu, 29 Dec 2016 12:50:17 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.12.181.208 with HTTP; Thu, 29 Dec 2016 12:50:16 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Thu, 29 Dec 2016 13:50:16 -0700 X-Google-Sender-Auth: A08LWpWhvYpiMGwwH-9O72W6Pn4 Message-ID: Subject: Re: Even lighter weight directory protocol? To: George Mitchell Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 20:50:18 -0000 On Thu, Dec 29, 2016 at 1:44 PM, George Mitchell wrote: > I use NIS to propagate /etc/passwd and /etc/group, and really nothing > else. I have been thinking about shifting to LDAP, to avoid some of > the really embarrassing failure modes of NIS, except that I would like > to kill the sadist who named this a "lightweight" protocol. I've > thought about a simple cron/rsync job (and maybe that's what I'll do > in the end). But are there any other directory-ish systems out there > that are, let's say, bantamweight or flyweight? -- George Many years ago I used cfengine to sync /etc/password and similar files. But it's really not as good as a real directory protocol. For one thing, users can only change their passwords on the master server. NIS is better. I'm afraid I don't know of any alternatives that aren't NIS or LDAP. KRB5 is good, but it only handles authentication, so it generally has to be paired with either NIS or LDAP. -Alan From owner-freebsd-hackers@freebsd.org Fri Dec 30 01:30:49 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8295BC97791 for ; Fri, 30 Dec 2016 01:30:49 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3541511C4; Fri, 30 Dec 2016 01:30:49 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id uBU1Uf6h046422; Thu, 29 Dec 2016 20:30:47 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: Even lighter weight directory protocol? To: freebsd-hackers@freebsd.org References: Cc: asomers@freebsd.org From: George Mitchell Message-ID: <3e7f6678-85e7-2203-7c0a-2500add42541@m5p.com> Date: Thu, 29 Dec 2016 20:30:33 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dPsLvrJLLHNWbgWW8vt1uU6uSmkBLXjLE" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Thu, 29 Dec 2016 20:30:47 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 01:30:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dPsLvrJLLHNWbgWW8vt1uU6uSmkBLXjLE Content-Type: multipart/mixed; boundary="vIq3w2QfXe90dGaOQBuG8exb8Udhvhc86"; protected-headers="v1" From: George Mitchell To: freebsd-hackers@freebsd.org Cc: asomers@freebsd.org Message-ID: <3e7f6678-85e7-2203-7c0a-2500add42541@m5p.com> Subject: Re: Even lighter weight directory protocol? References: In-Reply-To: --vIq3w2QfXe90dGaOQBuG8exb8Udhvhc86 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 12/29/16 15:50, Alan Somers wrote: > [...] > Many years ago I used cfengine to sync /etc/password and similar > files. But it's really not as good as a real directory protocol. For > one thing, users can only change their passwords on the master server. > [...] Actually, in my situation, this is a feature instead of a bug. But I'm too lazy to set up cfengine, and I think I'll just use cron and rasync after all. Thanks for your response! -- George --vIq3w2QfXe90dGaOQBuG8exb8Udhvhc86-- --dPsLvrJLLHNWbgWW8vt1uU6uSmkBLXjLE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlhluLkACgkQwRES3m+p 4fndiQ/+L2cTKzmbyG+E6XolCvpgnUWypzJsbm78M9juJpkxQmK7ttIeAB43prJK 8sEnVDxqG3nTUkhqmRRUIMR0lxDFyionPcMEfxzf21IqWjllrux9Nj82E5Jsh8MQ eCm3eBgLL0w+UfbR9MCfK96FpVsaf0GjNQl8teLocPfhifcNwRNAtChkkv9TjGLp 2ykxZKeedDoH5T3V5g9YldV0C7fajSFpUDLGqttAMKaItjX2NJkY3hXR8kdIIAX+ FA2lJvN5B4E2U0fruec3VMe3tLWbCLMJ519TqmGVEANSBpgD3oi3VXK4XmIXhj3j BqapMFG0IdallOj3n3wLZSDBtTqyG27JIjpJ2cNcf1eqVE2odaGDUc6JsaHz7Fa4 UYhvbCWClgFy0yiSxQXMaqU3EC8JE2Pn5N5cxIDYm/YZrwnbDzfRZmgfzepMki2K xZjygPzYuTRcf58ZZ8Psi3rYZVirnAUxPVTo9ArBAnYCPdNYa05/3ejPpPiKG6CQ Q0sOwAv7UqByjLaNILmlS/vzfc3UV7E9x3c5AqK5XKUSE0R4zvlT0LsgNBLxB+Ge OwyhI92aQxGFcex2vsbeEYcAbFyAvhg3zANlTH3K6Cc/xADprqXDNYJlnoAd5Isi 2XhUyD6sHbt9GIgWLadN7akakX62XsEnrWngACFMQuWBVGH4gHc= =HHvf -----END PGP SIGNATURE----- --dPsLvrJLLHNWbgWW8vt1uU6uSmkBLXjLE-- From owner-freebsd-hackers@freebsd.org Fri Dec 30 01:32:50 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69355C97A0F for ; Fri, 30 Dec 2016 01:32:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 4D1991714 for ; Fri, 30 Dec 2016 01:32:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 16776D226 for ; Fri, 30 Dec 2016 01:32:43 +0000 (UTC) Subject: Re: Even lighter weight directory protocol? To: freebsd-hackers@freebsd.org References: <3e7f6678-85e7-2203-7c0a-2500add42541@m5p.com> From: Allan Jude Message-ID: Date: Thu, 29 Dec 2016 20:32:42 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3e7f6678-85e7-2203-7c0a-2500add42541@m5p.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 01:32:50 -0000 On 2016-12-29 20:30, George Mitchell wrote: > On 12/29/16 15:50, Alan Somers wrote: >> [...] >> Many years ago I used cfengine to sync /etc/password and similar >> files. But it's really not as good as a real directory protocol. For >> one thing, users can only change their passwords on the master server. >> [...] > > Actually, in my situation, this is a feature instead of a bug. But > I'm too lazy to set up cfengine, and I think I'll just use cron and > rasync after all. Thanks for your response! -- George > Make sure you have it run pwd_mkdb after copying master.passwd -- Allan Jude From owner-freebsd-hackers@freebsd.org Fri Dec 30 11:58:46 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 234A2C962D3 for ; Fri, 30 Dec 2016 11:58:46 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD3511D7 for ; Fri, 30 Dec 2016 11:58:46 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 094B4C962D2; Fri, 30 Dec 2016 11:58:46 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08F62C962D1 for ; Fri, 30 Dec 2016 11:58:46 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84F0E11D3 for ; Fri, 30 Dec 2016 11:58:45 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from beeb.leiden.webweaving.org (5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id uBUBvHvt059403 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Dec 2016 12:57:18 +0100 (CET) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20] claimed to be beeb.leiden.webweaving.org Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: ZFS - directory entry From: Dirk-Willem van Gulik In-Reply-To: <20161214185154.GT61036@server.rulingia.com> Date: Fri, 30 Dec 2016 12:57:16 +0100 Cc: FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: <20161214185154.GT61036@server.rulingia.com> To: Peter Jeremy X-Mailer: Apple Mail (2.3259) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Fri, 30 Dec 2016 12:57:19 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 11:58:46 -0000 > On 14 Dec 2016, at 19:51, Peter Jeremy wrote: >=20 > On 2016-Dec-14 16:27:00 +0100, Dirk-Willem van Gulik = wrote: >> A rather odd directory entry (in /root, the home dir of root/toor) = appeared on a bog standard FreeBSD 10.2 (p18) lightly loaded machine = under ZFS during/post a backup: >>=20 >> $ ls -la /root | tail -q >> ---------- 1 root wheel 9223372036854775807 Jan 1 1970 = ?%+?kD?H???x,?5?Dh;*s!?h???jw??????\h?:????????``?13?@?????OA????????Puux?= ???>=20 >> OS and ZFS is installed with a bog standard sysinstall. =E2=80=98SMART=E2= =80=99 nor smartd have reported anything. nothing in dmesg, syslog of = boot log. Any suggestions as how to debug or get to the root of this ?=20= >>=20 >> And in particular - what is a risk of a reboot (to get a kernel with = debug, etc) causing the issue to =E2=80=98go away=E2=80=99 - and hence = stopping the forensic ? >=20 > Do you have ECC RAM? If not, it's possible this is an artifact of = some RAM > corruption, rather than on-disk corruption. >=20 > I'm surprised by the slow scrub, though they are very slow disks. You = might > like to use gstat or zpool iostat to see if one of the disks is slower = than > the others - indicating a possible problem with it. For the record - no such imbalance was found (all disks a specced = performance; SMART data yielded nothing either). Scrub found nothing. A = zfs send & compares of snapshots prior and post the entry did not yield = anything conclusive (But -1 entries in that directory). A reboot did not fix the issue =E2=80=94 i.e. it appeared resident on = disk post reboot (and in zfs send). An extensive lowlevel/bios memtest = (memtest.exe et.al. through PXE) did not find any HW issues; nor did a = SMART level disk check on all disks. Ultimately the =E2=80=98file=E2=80=99 was deleted with a simple = =E2=80=98rm=E2=80=99. Took about 3 seconds to return with a prompt. And = that was it. A post remove =E2=80=9Czfs send=E2=80=9D followed by a "zfs scrub" found = no ill effect/lost data (nor did tripwire throughout it all). So very odd all in all - and mildly unsatisfying :) Dw From owner-freebsd-hackers@freebsd.org Fri Dec 30 12:34:38 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DD2AC97971 for ; Fri, 30 Dec 2016 12:34:38 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A835112F2 for ; Fri, 30 Dec 2016 12:34:37 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from beeb.leiden.webweaving.org (5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id uBUCXH2q002706 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Dec 2016 13:33:19 +0100 (CET) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20] claimed to be beeb.leiden.webweaving.org Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall From: Dirk-Willem van Gulik In-Reply-To: <068c90c2-61c0-2fbc-3984-0bc937e19d63@freebsd.org> Date: Fri, 30 Dec 2016 13:33:17 +0100 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <10FC4055-5650-4C68-A07B-FBA7BF6BB60A@webweaving.org> References: <068c90c2-61c0-2fbc-3984-0bc937e19d63@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.3259) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Fri, 30 Dec 2016 13:33:19 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 12:34:38 -0000 > On 28 Dec 2016, at 22:04, Allan Jude wrote: >=20 > On 2016-12-28 14:41, Dirk-Willem van Gulik wrote: >> On a default ZFS install (late 2014, 10.x) of a few years hence it = seems sysinstall selected 64k as the default size of partition 1: with = the bootblock: >>=20 >> sudo gpart show >> =3D> 34 7814037101 ada0 GPT (3.6T) >> 34 6 - free - (3.0K) >> 40 128 1 freebsd-boot (64K) >> 168 67108864 2 freebsd-swap (32G) >> 67109032 7746928096 3 freebsd-zfs (3.6T) >> 7814037128 7 - free - (3.5K) >>=20 >> =E2=80=A6. lots of disks snipped =E2=80=A6.. >>=20 >> =3D> 34 7814037101 ada35 GPT (3.6T) >> 34 6 - free - (3.0K) >> 40 128 1 freebsd-boot (64K) >> 168 67108864 2 freebsd-swap (32G) >> 67109032 7746928096 3 freebsd-zfs (3.6T) >> 7814037128 7 - free - (3.5K) >>=20 >> Fair to assume that this (the 64k) is the reason that from 11.x = onwards;=20 >>=20 >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0=20 >>=20 >> fails with an immediate: >>=20 >> gpart: /dev/ada1p1: not enough space=20 >>=20 >> as gptzfsboot has grown in recent years to something towards the 90k = mark ? >>=20 >> -r--r--r-- 1 root wheel 88898 Dec 24 11:52 /boot/gptzfsboot >> =09 >> And I guess avoiding a rebuild would mean something like gently = disabling swap; shifting partition 1 & 2 carefully an so on ? Or is = there a more clever way? ZFS has *already* been upgraded. >>=20 >> Or am I missing something ? >=20 > swapoff -a; gpart resize ...; swapon -a >=20 > is likely your best bet. Aye - indeed a #!/bin/sh # gen 0 35 | while read I camcontrol devlist | grep ada | awk -F, '{ print $2 }' | sed -e = 's/)//=E2=80=98 | while read I do gpart delete -i 2 ada$I gpart resize -i 1 -s 512k ada$I gpart add -t freebsd-swap -i 2 ada$I gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 = ada$I done solved the issue for all machines affected.=20 We=E2=80=99ve since spotted quite a few systems with too small a = bootblock - so I guess sysinstall has historically been a bit stingy - = and it may be an idea to include something like above logic in man-page = or the upgrade logic. > The other option is to rebuild gptzfsboot without GELI support, and = then > it will be under 64 KB. Unfortunately - we rather rely on GELI and PKCS#11. Dw.= From owner-freebsd-hackers@freebsd.org Fri Dec 30 12:44:15 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2F3FC97C0B for ; Fri, 30 Dec 2016 12:44:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 7E585186C for ; Fri, 30 Dec 2016 12:44:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cMwXX-000HB1-Dp for freebsd-hackers@freebsd.org; Fri, 30 Dec 2016 15:44:07 +0300 Date: Fri, 30 Dec 2016 15:44:07 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org Subject: How to safely remove rest of GTP? Message-ID: <20161230124407.GN37118@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 12:44:15 -0000 How to safely remove rest of GPT? Disk have actual data (part of ZFS), I am don't need to destroy this data. GEOM: da6: the primary GPT table is corrupt or invalid. GEOM: da6: using the secondary instead -- recovery strongly advised. GEOM: da22: the primary GPT table is corrupt or invalid. GEOM: da22: using the secondary instead -- recovery strongly advised. GEOM: da6: the primary GPT table is corrupt or invalid. GEOM: da6: using the secondary instead -- recovery strongly advised. GEOM: da22: the primary GPT table is corrupt or invalid. GEOM: da22: using the secondary instead -- recovery strongly advised. From owner-freebsd-hackers@freebsd.org Fri Dec 30 16:00:30 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A671C972B3 for ; Fri, 30 Dec 2016 16:00:30 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30EB018C9 for ; Fri, 30 Dec 2016 16:00:29 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-qt0-x232.google.com with SMTP id p16so394572821qta.0 for ; Fri, 30 Dec 2016 08:00:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bOioGlwKpYc9VVD5I19L1MDcGSIVmCKg+SER7zoZFEc=; b=N3ph/0ktUrTyIOxIRZleOkNxuuNy21zJ0P8/SgqjRUp8MxaWPyDBv0nRuuvkn55Y/b 5I2D1j3UOwhDDuQRLR7S9yMlNmf8U6oFiWjeHfehN3ZLqCWwXKugxe2ChWaS71M47XUu l6WYnyEZEaEqu1IVCEJHnARaMy5eh3hB7fVFlvZ5XZWGpxJDvloJgx78a7eYNYBjjbSM CukaH+7ITTeZl8tRqyVb0PNrlW8Nae0nOzEbDevZYN26thuiXT078T5VvjPWhq9/wIk5 9KEr560THVQ0kZ3KLh9B9BRsYrj8qbKChcjL92rR/y2mPJa6K+FQN3swzKKCdPLiNhMS McdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=bOioGlwKpYc9VVD5I19L1MDcGSIVmCKg+SER7zoZFEc=; b=LIXJ6Uiwfw7smYmXWXLtxh0Rqc7Q77IXM0sUshZGbxAeFx6Hs5CswWNETMPy3iQd1g 24P4J0UOP0rtKCNYru8yMHS1Wh5/Kuec7XOC7U1G4B3K/zpT19B+uyJrOB99K914YWr0 ldjgLe6gTvsuc9hod/rDiDaExGiQwiB4Ibn92y+NxtaGSpX19kbAl3LoAUv9lDiCBeLQ clt0rkAQRc9sGGRI7hMj2fke7XbCpBpQdSYxe6piHTiDFLcnjtm4QTd/L9fPr8XUMUzA N14hbCZIfDA7Qh0U7TPWvt7KnzwS7AzUUajOvCohR1O1nZJ0xsf/1Yi29trut62ipbkU bH8w== X-Gm-Message-State: AIkVDXL5ndjhj9fD4xLLGvGm2y7gWgjTRsH7so4aa0CCx9kHDgbrp4M+ZdrRPd8mLcJTi/FjEtix61z1TQwodw== X-Received: by 10.200.37.221 with SMTP id f29mr47288939qtf.123.1483113628592; Fri, 30 Dec 2016 08:00:28 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.12.181.208 with HTTP; Fri, 30 Dec 2016 08:00:28 -0800 (PST) In-Reply-To: <20161230124407.GN37118@zxy.spb.ru> References: <20161230124407.GN37118@zxy.spb.ru> From: Alan Somers Date: Fri, 30 Dec 2016 09:00:28 -0700 X-Google-Sender-Auth: pRgpRo_K6MlmYt1SIB9JhVrkYPs Message-ID: Subject: Re: How to safely remove rest of GTP? To: Slawa Olhovchenkov Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 16:00:30 -0000 On Fri, Dec 30, 2016 at 5:44 AM, Slawa Olhovchenkov wrote: > How to safely remove rest of GPT? > Disk have actual data (part of ZFS), I am don't need to destroy this > data. > > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. It sounds like you created a GPT partition table, then created a ZFS Pool on the raw device, leaving part of the GPT partition table hanging around. If you're very careful, you can use dd to erase the GPT partition table. The following command worked for me. YMMV. dd if=/dev/zero of=/dev/vtbd1 bs=8192 count=2 -Alan From owner-freebsd-hackers@freebsd.org Fri Dec 30 16:11:46 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51799C97780 for ; Fri, 30 Dec 2016 16:11:46 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EDE3123B; Fri, 30 Dec 2016 16:11:46 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id t184so300736574qkd.0; Fri, 30 Dec 2016 08:11:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uVMcuwT6DJKq5m6wcmoA6gqkGAferTvL+vYH/QIA+c0=; b=YzX/hBzMlmEArydYala7EP3dj9hOyVVl3jwm+Qvjmsp7JzgPDafHFZnmj46qbYGwCG jyHar2MgWYJ3eWsgVPU8mMgThAYwROz64HcHAxHu0tMhpVsGxEbQCsmOplGgr6FhaA+p IiIItzQ7ZOeSvVv7PICx+ht9AWWtfruWP3zvf7Zv/f1MYO++6I8lDT8McDri7aJ19YCT zn4fWCxB7cSbmKQPo/D4BQ8JmKF6332k9Hvc5a1FLt0ZqfBrL+3P8w8/WejTYTevbJAX 3xH9tPS9n1hodJtrTT4JTvdTisTblZKAf7g40RqM5dUqFGXwvypDcN+YEj5XOcY+Fo+c bi7Q== 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=uVMcuwT6DJKq5m6wcmoA6gqkGAferTvL+vYH/QIA+c0=; b=q+hw20I7ucJSxNFQ/De3r23mZpWCspSI9bWnJcnBIBTyNefd+U05nWBg1QWSKJn5UL 5dSRCHTTuGrlt3LVJx3/MRAukzORU/+5mR900/kaxikwnisn93jzNHXh1nf2pMMO2yj7 tu8uXUyTE4+qe66xpeue/culLdelI+sRxdWab4N9BuATBAHGou7J48r2l835QKJbPDFt kvEuZE/5IZNn1RgNR+ycaFgrHXF5le7dYAFri6Gs2y91LiKoHWtPHJf6TAok7zufdXnl 7RLHEDAanRHbaVtkh3M0R1yXdKuBs25YiTLN1aXk98OhpeWFrMDmJAHYvtsciI/hvyWR nd+g== X-Gm-Message-State: AIkVDXLQ3nCBlQgVsk+IGPRf6snUhMPmQI3Lyu8yzbsrxnQCQi36Ohj9JMUm6mhZ9LdMLo9fNI3fzYnnN2GDNw== X-Received: by 10.55.195.148 with SMTP id r20mr45073665qkl.45.1483114305013; Fri, 30 Dec 2016 08:11:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.161.131 with HTTP; Fri, 30 Dec 2016 08:11:44 -0800 (PST) In-Reply-To: References: <20161230124407.GN37118@zxy.spb.ru> From: Andrey Fesenko Date: Fri, 30 Dec 2016 19:11:44 +0300 Message-ID: Subject: Re: How to safely remove rest of GTP? To: Alan Somers Cc: Slawa Olhovchenkov , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 16:11:46 -0000 On Fri, Dec 30, 2016 at 7:00 PM, Alan Somers wrote: > On Fri, Dec 30, 2016 at 5:44 AM, Slawa Olhovchenkov wrote: >> How to safely remove rest of GPT? >> Disk have actual data (part of ZFS), I am don't need to destroy this >> data. >> >> GEOM: da6: the primary GPT table is corrupt or invalid. >> GEOM: da6: using the secondary instead -- recovery strongly advised. >> GEOM: da22: the primary GPT table is corrupt or invalid. >> GEOM: da22: using the secondary instead -- recovery strongly advised. >> GEOM: da6: the primary GPT table is corrupt or invalid. >> GEOM: da6: using the secondary instead -- recovery strongly advised. >> GEOM: da22: the primary GPT table is corrupt or invalid. >> GEOM: da22: using the secondary instead -- recovery strongly advised. > > > dd if=/dev/zero of=/dev/vtbd1 bs=8192 count=2 > >> secondary instead It's last sector on the disk From owner-freebsd-hackers@freebsd.org Fri Dec 30 16:28:56 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74D8AC97DD5 for ; Fri, 30 Dec 2016 16:28:56 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id B80C21122; Fri, 30 Dec 2016 16:28:55 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: How to safely remove rest of GTP? To: Slawa Olhovchenkov , freebsd-hackers@freebsd.org References: <20161230124407.GN37118@zxy.spb.ru> From: "Andrey V. Elsukov" Message-ID: Date: Fri, 30 Dec 2016 19:28:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161230124407.GN37118@zxy.spb.ru> Content-Type: multipart/mixed; boundary="------------ECE39D6E59BD255AAD9727C9" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 16:28:56 -0000 This is a multi-part message in MIME format. --------------ECE39D6E59BD255AAD9727C9 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 30.12.2016 15:44, Slawa Olhovchenkov wrote: > How to safely remove rest of GPT? > Disk have actual data (part of ZFS), I am don't need to destroy this > data. > > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. You may try attached patch, I did only basic tests, so first try somewhere :) -- WBR, Andrey V. Elsukov --------------ECE39D6E59BD255AAD9727C9 Content-Type: text/x-patch; name="gpart_safe_destroy.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="gpart_safe_destroy.diff" Index: sys/geom/part/g_part_gpt.c =================================================================== --- sys/geom/part/g_part_gpt.c (revision 310784) +++ sys/geom/part/g_part_gpt.c (working copy) @@ -690,7 +690,8 @@ g_part_gpt_destroy(struct g_part_table *basetable, * Wipe the first 2 sectors to clear the partitioning. Wipe the last * sector only if it has valid secondary header. */ - basetable->gpt_smhead |= 3; + if (table->state[GPT_ELT_PRIHDR] == GPT_STATE_OK) + basetable->gpt_smhead |= 3; if (table->state[GPT_ELT_SECHDR] == GPT_STATE_OK && table->lba[GPT_ELT_SECHDR] == pp->mediasize / pp->sectorsize - 1) basetable->gpt_smtail |= 1; --------------ECE39D6E59BD255AAD9727C9-- From owner-freebsd-hackers@freebsd.org Fri Dec 30 16:41:23 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B66CC96368 for ; Fri, 30 Dec 2016 16:41:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 D07DA1887 for ; Fri, 30 Dec 2016 16:41:22 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: cbcdc681-ceae-11e6-9357-bffcd86bd944 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id cbcdc681-ceae-11e6-9357-bffcd86bd944; Fri, 30 Dec 2016 16:41:23 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBUGfFw1001304; Fri, 30 Dec 2016 09:41:15 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483116075.16152.75.camel@freebsd.org> Subject: Re: How to safely remove rest of GTP? From: Ian Lepore To: Slawa Olhovchenkov , freebsd-hackers@freebsd.org Date: Fri, 30 Dec 2016 09:41:15 -0700 In-Reply-To: <20161230124407.GN37118@zxy.spb.ru> References: <20161230124407.GN37118@zxy.spb.ru> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 16:41:23 -0000 On Fri, 2016-12-30 at 15:44 +0300, Slawa Olhovchenkov wrote: > How to safely remove rest of GPT? > Disk have actual data (part of ZFS), I am don't need to destroy this > data. > > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. > GEOM: da6: the primary GPT table is corrupt or invalid. > GEOM: da6: using the secondary instead -- recovery strongly advised. > GEOM: da22: the primary GPT table is corrupt or invalid. > GEOM: da22: using the secondary instead -- recovery strongly advised. > You need to zero out the backup gpt header.  Geom locates that header using (mediasize / sectorsize) - 1.  I think mediasize/sectorsize is exactly what's displayed by diskinfo -v as "mediasize in sectors", so that number - 1 would be lastsector in:  dd if=/dev/zero of=/dev/da6 bs= oseek= count=1 -- Ian From owner-freebsd-hackers@freebsd.org Fri Dec 30 16:46:55 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D49EEC965F7 for ; Fri, 30 Dec 2016 16:46:55 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 98D981C8D; Fri, 30 Dec 2016 16:46:55 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cN0KS-000NNd-Qs; Fri, 30 Dec 2016 19:46:52 +0300 Date: Fri, 30 Dec 2016 19:46:52 +0300 From: Slawa Olhovchenkov To: "Andrey V. Elsukov" Cc: freebsd-hackers@freebsd.org Subject: Re: How to safely remove rest of GTP? Message-ID: <20161230164652.GO37118@zxy.spb.ru> References: <20161230124407.GN37118@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 16:46:55 -0000 On Fri, Dec 30, 2016 at 07:28:19PM +0300, Andrey V. Elsukov wrote: > On 30.12.2016 15:44, Slawa Olhovchenkov wrote: > > How to safely remove rest of GPT? > > Disk have actual data (part of ZFS), I am don't need to destroy this > > data. > > > > GEOM: da6: the primary GPT table is corrupt or invalid. > > GEOM: da6: using the secondary instead -- recovery strongly advised. > > GEOM: da22: the primary GPT table is corrupt or invalid. > > GEOM: da22: using the secondary instead -- recovery strongly advised. > > GEOM: da6: the primary GPT table is corrupt or invalid. > > GEOM: da6: using the secondary instead -- recovery strongly advised. > > GEOM: da22: the primary GPT table is corrupt or invalid. > > GEOM: da22: using the secondary instead -- recovery strongly advised. > > You may try attached patch, I did only basic tests, so first try > somewhere :) What purpose of this patch? > -- > WBR, Andrey V. Elsukov > Index: sys/geom/part/g_part_gpt.c > =================================================================== > --- sys/geom/part/g_part_gpt.c (revision 310784) > +++ sys/geom/part/g_part_gpt.c (working copy) > @@ -690,7 +690,8 @@ g_part_gpt_destroy(struct g_part_table *basetable, > * Wipe the first 2 sectors to clear the partitioning. Wipe the last > * sector only if it has valid secondary header. > */ > - basetable->gpt_smhead |= 3; > + if (table->state[GPT_ELT_PRIHDR] == GPT_STATE_OK) > + basetable->gpt_smhead |= 3; > if (table->state[GPT_ELT_SECHDR] == GPT_STATE_OK && > table->lba[GPT_ELT_SECHDR] == pp->mediasize / pp->sectorsize - 1) > basetable->gpt_smtail |= 1; > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Fri Dec 30 17:09:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 463FBC97028 for ; Fri, 30 Dec 2016 17:09:33 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 8B6251DE8; Fri, 30 Dec 2016 17:09:32 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: How to safely remove rest of GTP? To: Slawa Olhovchenkov References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> Cc: freebsd-hackers@freebsd.org From: "Andrey V. Elsukov" Message-ID: <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> Date: Fri, 30 Dec 2016 20:08:55 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161230164652.GO37118@zxy.spb.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 17:09:33 -0000 On 30.12.2016 19:46, Slawa Olhovchenkov wrote: > On Fri, Dec 30, 2016 at 07:28:19PM +0300, Andrey V. Elsukov wrote: > >> On 30.12.2016 15:44, Slawa Olhovchenkov wrote: >>> How to safely remove rest of GPT? >>> Disk have actual data (part of ZFS), I am don't need to destroy this >>> data. >>> >>> GEOM: da6: the primary GPT table is corrupt or invalid. >>> GEOM: da6: using the secondary instead -- recovery strongly advised. >>> GEOM: da22: the primary GPT table is corrupt or invalid. >>> GEOM: da22: using the secondary instead -- recovery strongly advised. >>> GEOM: da6: the primary GPT table is corrupt or invalid. >>> GEOM: da6: using the secondary instead -- recovery strongly advised. >>> GEOM: da22: the primary GPT table is corrupt or invalid. >>> GEOM: da22: using the secondary instead -- recovery strongly advised. >> >> You may try attached patch, I did only basic tests, so first try >> somewhere :) > > What purpose of this patch? In case when you have not valid primary header, `gpart destroy` will not touch first two sectors. In you case you can wipe only last sector, like Ian suggested, but use 'gpart destroy -F da6' instead of dd. -- WBR, Andrey V. Elsukov From owner-freebsd-hackers@freebsd.org Fri Dec 30 17:37:19 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3068FC97A57 for ; Fri, 30 Dec 2016 17:37:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 BA3A713B1 for ; Fri, 30 Dec 2016 17:37:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 9b3efa97-ceb6-11e6-9357-bffcd86bd944 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 9b3efa97-ceb6-11e6-9357-bffcd86bd944; Fri, 30 Dec 2016 17:37:17 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBUHbATt001417; Fri, 30 Dec 2016 10:37:10 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483119430.16152.83.camel@freebsd.org> Subject: Re: How to safely remove rest of GTP? From: Ian Lepore To: "Andrey V. Elsukov" , Slawa Olhovchenkov Cc: freebsd-hackers@freebsd.org Date: Fri, 30 Dec 2016 10:37:10 -0700 In-Reply-To: <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 17:37:19 -0000 On Fri, 2016-12-30 at 20:08 +0300, Andrey V. Elsukov wrote: > On 30.12.2016 19:46, Slawa Olhovchenkov wrote: > > > > On Fri, Dec 30, 2016 at 07:28:19PM +0300, Andrey V. Elsukov wrote: > > > > > > > > On 30.12.2016 15:44, Slawa Olhovchenkov wrote: > > > > > > > > How to safely remove rest of GPT? > > > > Disk have actual data (part of ZFS), I am don't need to destroy > > > > this > > > > data. > > > > > > > > GEOM: da6: the primary GPT table is corrupt or invalid. > > > > GEOM: da6: using the secondary instead -- recovery strongly > > > > advised. > > > > GEOM: da22: the primary GPT table is corrupt or invalid. > > > > GEOM: da22: using the secondary instead -- recovery strongly > > > > advised. > > > > GEOM: da6: the primary GPT table is corrupt or invalid. > > > > GEOM: da6: using the secondary instead -- recovery strongly > > > > advised. > > > > GEOM: da22: the primary GPT table is corrupt or invalid. > > > > GEOM: da22: using the secondary instead -- recovery strongly > > > > advised. > > > You may try attached patch, I did only basic tests, so first try > > > somewhere :) > > What purpose of this patch? > In case when you have not valid primary header, `gpart destroy` will > not  > touch first two sectors. In you case you can wipe only last sector, > like  > Ian suggested, but use 'gpart destroy -F da6' instead of dd. > If you gpart destroy -F da6 won't that also clear the valid MBR at the start of the disk?  I think Slawa needs to preserve that. I think it would be really useful if gpart recover could help with this somehow.  There is a valid mbr, and a partially-valid gpt (only the backup is valid).  So gpart recover should provide a way to recover the gpt by refreshing the primary gpt and the pbmr, or recover the mbr by wiping the backup gpt.  I'm not sure what the syntax would be to specify that, though. This didn't used to be a problem until the changes that made the backup gpt get used automatically without any sysadmin intervention. -- Ian From owner-freebsd-hackers@freebsd.org Fri Dec 30 17:40:20 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8753BC97C02 for ; Fri, 30 Dec 2016 17:40:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 4A2AF1692; Fri, 30 Dec 2016 17:40:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cN1AA-000Ok3-9K; Fri, 30 Dec 2016 20:40:18 +0300 Date: Fri, 30 Dec 2016 20:40:18 +0300 From: Slawa Olhovchenkov To: Ian Lepore Cc: "Andrey V. Elsukov" , freebsd-hackers@freebsd.org Subject: Re: How to safely remove rest of GTP? Message-ID: <20161230174018.GP37118@zxy.spb.ru> References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> <1483119430.16152.83.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1483119430.16152.83.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 17:40:20 -0000 On Fri, Dec 30, 2016 at 10:37:10AM -0700, Ian Lepore wrote: > On Fri, 2016-12-30 at 20:08 +0300, Andrey V. Elsukov wrote: > > On 30.12.2016 19:46, Slawa Olhovchenkov wrote: > > > > > > On Fri, Dec 30, 2016 at 07:28:19PM +0300, Andrey V. Elsukov wrote: > > > > > > > > > > > On 30.12.2016 15:44, Slawa Olhovchenkov wrote: > > > > > > > > > > How to safely remove rest of GPT? > > > > > Disk have actual data (part of ZFS), I am don't need to destroy > > > > > this > > > > > data. > > > > > > > > > > GEOM: da6: the primary GPT table is corrupt or invalid. > > > > > GEOM: da6: using the secondary instead -- recovery strongly > > > > > advised. > > > > > GEOM: da22: the primary GPT table is corrupt or invalid. > > > > > GEOM: da22: using the secondary instead -- recovery strongly > > > > > advised. > > > > > GEOM: da6: the primary GPT table is corrupt or invalid. > > > > > GEOM: da6: using the secondary instead -- recovery strongly > > > > > advised. > > > > > GEOM: da22: the primary GPT table is corrupt or invalid. > > > > > GEOM: da22: using the secondary instead -- recovery strongly > > > > > advised. > > > > You may try attached patch, I did only basic tests, so first try > > > > somewhere :) > > > What purpose of this patch? > > In case when you have not valid primary header, `gpart destroy` will > > notš > > touch first two sectors. In you case you can wipe only last sector, > > likeš > > Ian suggested, but use 'gpart destroy -F da6' instead of dd. > > > > If you gpart destroy -F da6 won't that also clear the valid MBR at the > start of the disk? šI think Slawa needs to preserve that. I am don't have any partition scheme on disk -- whole disk for ZFS. May be someone use some scheme before, on other server, before insert. I am don't need it. > I think it would be really useful if gpart recover could help with this > somehow. šThere is a valid mbr, and a partially-valid gpt (only the > backup is valid). šSo gpart recover should provide a way to recover the > gpt by refreshing the primary gpt and the pbmr, or recover the mbr by > wiping the backup gpt. šI'm not sure what the syntax would be to > specify that, though. > > This didn't used to be a problem until the changes that made the backup > gpt get used automatically without any sysadmin intervention. This is other case, but may be usefull too. From owner-freebsd-hackers@freebsd.org Fri Dec 30 17:48:51 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AADBAC970EA for ; Fri, 30 Dec 2016 17:48:51 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id B6C5A1062; Fri, 30 Dec 2016 17:48:50 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: How to safely remove rest of GTP? To: Ian Lepore , Slawa Olhovchenkov References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> <1483119430.16152.83.camel@freebsd.org> Cc: freebsd-hackers@freebsd.org From: "Andrey V. Elsukov" Message-ID: <071295b5-f7d8-d09b-13f9-416524a1f654@FreeBSD.org> Date: Fri, 30 Dec 2016 20:48:13 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <1483119430.16152.83.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 17:48:51 -0000 On 30.12.2016 20:37, Ian Lepore wrote: >> In case when you have not valid primary header, `gpart destroy` will >> not >> touch first two sectors. In you case you can wipe only last sector, >> like >> Ian suggested, but use 'gpart destroy -F da6' instead of dd. >> > > If you gpart destroy -F da6 won't that also clear the valid MBR at the > start of the disk? I think Slawa needs to preserve that. As I said, it will not touch first two sectors, where PMBR and primary GPT headers are. > I think it would be really useful if gpart recover could help with this > somehow. There is a valid mbr, and a partially-valid gpt (only the > backup is valid). So gpart recover should provide a way to recover the > gpt by refreshing the primary gpt and the pbmr, `gpart recover` will restore GPT using information from backup header and table and construct new PMBR. After that you need to write bootcode if needed. > or recover the mbr by > wiping the backup gpt. This is what the patch does. You need to use `gpart destroy -F` to CORRUPTED GPT, this command will wipe last sector where GPT backup header is located. Since GPT is in CORRUPT state, the primary header will not be overwrited by this command. When both primary and backup headers and tables are valid, `gpart destroy` overwites PMBR, primary and backup headers. > I'm not sure what the syntax would be to > specify that, though. > > This didn't used to be a problem until the changes that made the backup > gpt get used automatically without any sysadmin intervention. For some users the problem was that they could not find their GPT, that declares its reliability. -- WBR, Andrey V. Elsukov From owner-freebsd-hackers@freebsd.org Fri Dec 30 18:25:51 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E211C97152 for ; Fri, 30 Dec 2016 18:25:51 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 E9A371EDE for ; Fri, 30 Dec 2016 18:25:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 303CED3A3 for ; Fri, 30 Dec 2016 18:25:49 +0000 (UTC) Subject: Re: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall To: freebsd-hackers@freebsd.org References: <068c90c2-61c0-2fbc-3984-0bc937e19d63@freebsd.org> <10FC4055-5650-4C68-A07B-FBA7BF6BB60A@webweaving.org> From: Allan Jude Message-ID: <0ac24a2a-ae82-be4a-d162-b0c62e5b0d13@freebsd.org> Date: Fri, 30 Dec 2016 13:25:48 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <10FC4055-5650-4C68-A07B-FBA7BF6BB60A@webweaving.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 18:25:51 -0000 On 2016-12-30 07:33, Dirk-Willem van Gulik wrote: > >> On 28 Dec 2016, at 22:04, Allan Jude wrote: >> >> On 2016-12-28 14:41, Dirk-Willem van Gulik wrote: >>> On a default ZFS install (late 2014, 10.x) of a few years hence it seems sysinstall selected 64k as the default size of partition 1: with the bootblock: >>> >>> sudo gpart show >>> => 34 7814037101 ada0 GPT (3.6T) >>> 34 6 - free - (3.0K) >>> 40 128 1 freebsd-boot (64K) >>> 168 67108864 2 freebsd-swap (32G) >>> 67109032 7746928096 3 freebsd-zfs (3.6T) >>> 7814037128 7 - free - (3.5K) >>> >>> …. lots of disks snipped ….. >>> >>> => 34 7814037101 ada35 GPT (3.6T) >>> 34 6 - free - (3.0K) >>> 40 128 1 freebsd-boot (64K) >>> 168 67108864 2 freebsd-swap (32G) >>> 67109032 7746928096 3 freebsd-zfs (3.6T) >>> 7814037128 7 - free - (3.5K) >>> >>> Fair to assume that this (the 64k) is the reason that from 11.x onwards; >>> >>> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 >>> >>> fails with an immediate: >>> >>> gpart: /dev/ada1p1: not enough space >>> >>> as gptzfsboot has grown in recent years to something towards the 90k mark ? >>> >>> -r--r--r-- 1 root wheel 88898 Dec 24 11:52 /boot/gptzfsboot >>> >>> And I guess avoiding a rebuild would mean something like gently disabling swap; shifting partition 1 & 2 carefully an so on ? Or is there a more clever way? ZFS has *already* been upgraded. >>> >>> Or am I missing something ? >> >> swapoff -a; gpart resize ...; swapon -a >> >> is likely your best bet. > > Aye - indeed a > > #!/bin/sh > > # gen 0 35 | while read I > > camcontrol devlist | grep ada | awk -F, '{ print $2 }' | sed -e 's/)//‘ | while read I > do > gpart delete -i 2 ada$I > gpart resize -i 1 -s 512k ada$I > gpart add -t freebsd-swap -i 2 ada$I > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada$I > done > > solved the issue for all machines affected. > > We’ve since spotted quite a few systems with too small a bootblock - so I guess sysinstall has historically been a bit stingy - and it may be an idea to include something like above logic in man-page or the upgrade logic. > >> The other option is to rebuild gptzfsboot without GELI support, and then >> it will be under 64 KB. > > Unfortunately - we rather rely on GELI and PKCS#11. > This would only apply to gptzfsboot, the new feature I introduced in 11.0 that allows you to have even the /boot directory encrypted (rather than having an unencrypted ufs partition, or a 2nd zpool that is not encrypted). If you are upgrading from 10.x or earlier, you can use gptzfsboot without GELI, since it didn't exist before. > Dw. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Allan Jude From owner-freebsd-hackers@freebsd.org Fri Dec 30 18:36:40 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28D42C973F1 for ; Fri, 30 Dec 2016 18:36:40 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B029E13E4 for ; Fri, 30 Dec 2016 18:36:39 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from beeb.leiden.webweaving.org (5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id uBUIZJmr033758 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Dec 2016 19:35:20 +0100 (CET) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED06D14.cm-7-1b.dynamic.ziggo.nl [94.208.109.20] claimed to be beeb.leiden.webweaving.org Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall From: Dirk-Willem van Gulik In-Reply-To: <0ac24a2a-ae82-be4a-d162-b0c62e5b0d13@freebsd.org> Date: Fri, 30 Dec 2016 19:35:19 +0100 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <068c90c2-61c0-2fbc-3984-0bc937e19d63@freebsd.org> <10FC4055-5650-4C68-A07B-FBA7BF6BB60A@webweaving.org> <0ac24a2a-ae82-be4a-d162-b0c62e5b0d13@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.3259) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Fri, 30 Dec 2016 19:35:20 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 18:36:40 -0000 > On 30 Dec 2016, at 19:25, Allan Jude wrote: >>=20 >>> The other option is to rebuild gptzfsboot without GELI support, and = then >>> it will be under 64 KB. >>=20 >> Unfortunately - we rather rely on GELI and PKCS#11. >=20 > This would only apply to gptzfsboot, the new feature I introduced in > 11.0 that allows you to have even the /boot directory encrypted = (rather > than having an unencrypted ufs partition, or a 2nd zpool that is not > encrypted). >=20 > If you are upgrading from 10.x or earlier, you can use gptzfsboot > without GELI, since it didn't exist before. Ah - good to know. thanks for that! We=E2=80=99re not quite there yet - as we need a modicum of PKCS#11 to = negotiate with the TPM (or on low end archive machines; a USB = smartcard/token) - i.e a tad beyond geli_passphrase(). Dw.= From owner-freebsd-hackers@freebsd.org Fri Dec 30 19:02:48 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17B9FC97C00 for ; Fri, 30 Dec 2016 19:02:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 EB2B914A8 for ; Fri, 30 Dec 2016 19:02:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 94ecd58e-cec2-11e6-8c89-112185c90658 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 94ecd58e-cec2-11e6-8c89-112185c90658; Fri, 30 Dec 2016 19:03:00 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uBUJ2i5g001602; Fri, 30 Dec 2016 12:02:44 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1483124564.16152.85.camel@freebsd.org> Subject: Re: How to safely remove rest of GTP? From: Ian Lepore To: "Andrey V. Elsukov" , Slawa Olhovchenkov Cc: freebsd-hackers@freebsd.org Date: Fri, 30 Dec 2016 12:02:44 -0700 In-Reply-To: <071295b5-f7d8-d09b-13f9-416524a1f654@FreeBSD.org> References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> <1483119430.16152.83.camel@freebsd.org> <071295b5-f7d8-d09b-13f9-416524a1f654@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 19:02:48 -0000 On Fri, 2016-12-30 at 20:48 +0300, Andrey V. Elsukov wrote: > On 30.12.2016 20:37, Ian Lepore wrote: > > > > > > > > In case when you have not valid primary header, `gpart destroy` > > > will > > > not > > > touch first two sectors. In you case you can wipe only last > > > sector, > > > like > > > Ian suggested, but use 'gpart destroy -F da6' instead of dd. > > > > > If you gpart destroy -F da6 won't that also clear the valid MBR at > > the > > start of the disk?  I think Slawa needs to preserve that. > As I said, it will not touch first two sectors, where PMBR and > primary  > GPT headers are. > > > > > I think it would be really useful if gpart recover could help with > > this > > somehow.  There is a valid mbr, and a partially-valid gpt (only the > > backup is valid).  So gpart recover should provide a way to recover > > the > > gpt by refreshing the primary gpt and the pbmr, > `gpart recover` will restore GPT using information from backup > header  > and table and construct new PMBR. After that you need to write > bootcode  > if needed. > > > > > or recover the mbr by > > wiping the backup gpt. > This is what the patch does. You need to use `gpart destroy -F` to  > CORRUPTED GPT, this command will wipe last sector where GPT backup  > header is located. Since GPT is in CORRUPT state, the primary header  > will not be overwrited by this command. > > When both primary and backup headers and tables are valid, `gpart  > destroy` overwites PMBR, primary and backup headers. > > > > > I'm not sure what the syntax would be to > > specify that, though. > > > > This didn't used to be a problem until the changes that made the > > backup > > gpt get used automatically without any sysadmin intervention. > For some users the problem was that they could not find their GPT, > that  > declares its reliability. > Do you seriously believe that people are going to just do a gpart destroy -F on a device with a valid MBR as a method of preserving that mbr?  If that's the kind of thinking behind the gpart interface, I guess that helps explain why it's so nearly impossible to understand and use already. -- Ian From owner-freebsd-hackers@freebsd.org Fri Dec 30 19:04:44 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CF83C97D08 for ; Fri, 30 Dec 2016 19:04:44 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 6BEC016BA; Fri, 30 Dec 2016 19:04:43 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: How to safely remove rest of GTP? To: Ian Lepore , Slawa Olhovchenkov References: <20161230124407.GN37118@zxy.spb.ru> <20161230164652.GO37118@zxy.spb.ru> <22d5dece-f14b-3bef-b3dd-8bb6226e0d28@FreeBSD.org> <1483119430.16152.83.camel@freebsd.org> <071295b5-f7d8-d09b-13f9-416524a1f654@FreeBSD.org> <1483124564.16152.85.camel@freebsd.org> Cc: freebsd-hackers@freebsd.org From: "Andrey V. Elsukov" Message-ID: <1b8d6b48-8e8e-95f0-22d6-f75cc9025c11@FreeBSD.org> Date: Fri, 30 Dec 2016 22:04:06 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <1483124564.16152.85.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2016 19:04:44 -0000 On 30.12.2016 22:02, Ian Lepore wrote: > > Do you seriously believe that people are going to just do a gpart > destroy -F on a device with a valid MBR as a method of preserving that > mbr? If that's the kind of thinking behind the gpart interface, I > guess that helps explain why it's so nearly impossible to understand > and use already. People, who have valid MBR will never see messages about corrupt GPT. -- WBR, Andrey V. Elsukov From owner-freebsd-hackers@freebsd.org Sat Dec 31 12:26:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CF54C98C43 for ; Sat, 31 Dec 2016 12:26:33 +0000 (UTC) (envelope-from shea@shealevy.com) Received: from smtprelay.hostedemail.com (smtprelay0223.hostedemail.com [216.40.44.223]) (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 0315518EA for ; Sat, 31 Dec 2016 12:26:32 +0000 (UTC) (envelope-from shea@shealevy.com) Received: from smtprelay.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by smtpgrave05.hostedemail.com (Postfix) with ESMTP id D1623183EB8 for ; Sat, 31 Dec 2016 02:58:59 +0000 (UTC) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay01.hostedemail.com (Postfix) with ESMTP id 165F5235A7 for ; Sat, 31 Dec 2016 02:58:52 +0000 (UTC) X-Session-Marker: 7368656140736865616C6576792E636F6D X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, shea@shealevy.com, :, RULES_HIT:41:355:379:871:966:968:973:988:989:1000:1260:1313:1314:1345:1381:1437:1516:1518:1534:1540:1575:1711:1730:1747:1777:1792:2196:2199:2393:2559:2562:3138:3139:3140:3141:3142:3352:3622:3690:3865:3866:3867:3868:3870:3871:3872:3874:4362:4385:5007:6261:6506:6747:7281:7909:9010:9040:10004:10848:11658:11914:12296:12663:13138:13161:13192:13229:13231:14096:14180:14721:21060:21080:21433:30034:30041:30054:30070:30075, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:1, LUA_SUMMARY:none X-HE-Tag: mist57_132c622e7ce63 X-Filterd-Recvd-Size: 2518 Received: from localhost (238.sub-174-192-30.myvzw.com [174.192.30.238]) (Authenticated sender: shea@shealevy.com) by omf08.hostedemail.com (Postfix) with ESMTPA for ; Sat, 31 Dec 2016 02:58:51 +0000 (UTC) From: Shea Levy To: freebsd-hackers@freebsd.org Subject: Detecting changes when mapping /dev/devstat Date: Fri, 30 Dec 2016 21:58:49 -0500 Message-ID: <87r34o3ity.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 12:26:33 -0000 --=-=-= Content-Type: text/plain Hi all, What is the appropriate way to detect changes when accessing devstat info via a mapping of /dev/devstat? I'm interested both in changes to the device list as a whole and new statistics on a given device. For new stats on a given device, it seems the only way to detect a new stat is to check the sequence number for that device. Is that right? For changes in the device list, it's a bit less clear. My hope was that I could map space for one more struct devstat than the current numdevs and just check to see if some field or other is nonzero, but in my glances through subr_devstat.c I'm not sure if there are any guarantees about those fields for structures past the current list, especially if a device was added and removed. Is there anything doable here? Thanks, Shea P.S. I wasn't quite sure which list was appropriate for this question, please feel free to point me to another! --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE6ESKvwKkwnxgMLnaXAvWlX2G/icFAlhnHukACgkQXAvWlX2G /icRQw//QqWGAy+nTglYUMMP1H9/JD+UHlFj3bbewU+yGELA/boVHauAqT53VmiE qbYr0W+d7lc0NgkUSVJzTOZfcxMKFqAuGZu3B/u3FVf1fif7VqBu80egqYmt2AaG FKrRfOUA/y6MJq0SRfNUCLeia7BIbaUMLOiqzWcmRZH7p0Tl9V4ZzhKq6sADWKEg 6BOKN9DN2U4v/4ZYtom9jZwKpecf/Vzp4rdCeweAi1cVuTlHul7QFk36lBKQJhhb +5zrFsiJfmVpxnZgHM9gXLlGotm+EB70tBzvKcUFe27MZx3L6gZOiz3zUpXsWm88 RZWX5F3p+A6TxhxcROnvsbKTCots/2vZYzhfufYhsyF12Kr2om9c4T+W201il1gv d9HNpjMjBHM0oHLAHEo3GVVlkWVHu4RdxJ08tTlMGlrmfdXhks/nbOk/1jk3QfNJ pLs+CvihnO7iYGzF4Llyp+sCpJJRh1GH53fs71260qJidtVgSjKXbMQsI4upoqLr fhorfPHvxiG0flOXOH3ngJMMgLuNOtMsIXIKP59ypj6f5kLEe+cDAY9JDNFjrnRv D4H5pZx3rQtMdMrdsnU8Xk+lmxu+/GwXn57TXzb1orxGpA5sJBtPDeanq7UJqEoc VhN6E53YC5epiCiKbL0/yzePOUf5WYgiFEU7PmBRYxDyuvBOXTc= =OEO6 -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-hackers@freebsd.org Sat Dec 31 21:29:18 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43E7EC98907 for ; Sat, 31 Dec 2016 21:29:18 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CECB01AAE for ; Sat, 31 Dec 2016 21:29:17 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-wm0-f45.google.com with SMTP id a197so342996561wmd.0 for ; Sat, 31 Dec 2016 13:29:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=7QqT7a4gjubnJXJbFLKRKsoYKd+UKB2LmWZZ5VJbbOU=; b=HwTR6BbFhOpt5Y7pqPoYkboIONcPb7AevXX7/D0Cw1VW21mbMXSZgg9ffLF2to3847 DC4hQdxWrBnSoJCF9/9sbKNaISV8sy48/MUCa8vVcSOWIJ+Z8qsHwpI/GG0zDLhnBx0c I03wONrZS5BJmQYKoYN11at/nnwi5wP8ZMR0YONbgmHIFGVXgQ7W1FfiSv79hhUYGjM0 bKEKuI7sPonGzczrL9xAZ/Uyl7K0SACiuin8YjsCZ76xnLfYHcZiOFVGz5e64uSH1oLI 8NoGBR1Vjnqxkmr86LNqlRsZ+NsswjgsruPAMADcNJ/uYh1ikjVo9EmVvi3oh2F4ULAC 2hjQ== X-Gm-Message-State: AIkVDXIqreoxMTpbxxbLEzSHVKGxyQZJLW1Q9keJCjLFrnevlHDOtDJeGbUnmhT2VCFltg== X-Received: by 10.28.147.204 with SMTP id v195mr37085248wmd.35.1483209143950; Sat, 31 Dec 2016 10:32:23 -0800 (PST) Received: from mail-wj0-f173.google.com (mail-wj0-f173.google.com. [209.85.210.173]) by smtp.gmail.com with ESMTPSA id i15sm79230844wjs.16.2016.12.31.10.32.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Dec 2016 10:32:23 -0800 (PST) Received: by mail-wj0-f173.google.com with SMTP id v7so399138147wjy.2 for ; Sat, 31 Dec 2016 10:32:23 -0800 (PST) X-Received: by 10.195.9.102 with SMTP id dr6mr34659901wjd.209.1483209143701; Sat, 31 Dec 2016 10:32:23 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.194.29.72 with HTTP; Sat, 31 Dec 2016 10:32:23 -0800 (PST) In-Reply-To: <87r34o3ity.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> References: <87r34o3ity.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> From: Conrad Meyer Date: Sat, 31 Dec 2016 10:32:23 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Detecting changes when mapping /dev/devstat To: Shea Levy Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 21:29:18 -0000 Shea, You might try looking at how devstat(8) uses the interface. http://devstat.googlecode.com/ ("pkg install devstat"). Best, Conrad On Fri, Dec 30, 2016 at 6:58 PM, Shea Levy wrote: > Hi all, > > What is the appropriate way to detect changes when accessing devstat > info via a mapping of /dev/devstat? I'm interested both in changes to > the device list as a whole and new statistics on a given device. > > For new stats on a given device, it seems the only way to detect a new > stat is to check the sequence number for that device. Is that right? > > For changes in the device list, it's a bit less clear. My hope was that > I could map space for one more struct devstat than the current numdevs > and just check to see if some field or other is nonzero, but in my > glances through subr_devstat.c I'm not sure if there are any guarantees > about those fields for structures past the current list, especially if a > device was added and removed. Is there anything doable here? > > Thanks, > Shea > > P.S. I wasn't quite sure which list was appropriate for this question, > please feel free to point me to another! From owner-freebsd-hackers@freebsd.org Sat Dec 31 23:55:22 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CF4AC993AF for ; Sat, 31 Dec 2016 23:55:22 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from know-smtprelay-omc-5.server.virginmedia.net (know-smtprelay-omc-5.server.virginmedia.net [80.0.253.69]) by mx1.freebsd.org (Postfix) with ESMTP id C1CDF13BC for ; Sat, 31 Dec 2016 23:55:21 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from [192.168.1.100] ([86.10.211.13]) by know-smtprelay-5-imp with bizsmtp id SnuA1u0090HtmFq01nuBX4; Sat, 31 Dec 2016 23:54:11 +0000 X-Originating-IP: [86.10.211.13] X-Spam: 0 X-Authority: v=2.1 cv=CMjXJkfD c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=2rVjqWD_AAAA:8 a=6I5d2MoRAAAA:8 a=itly7gIdAAAA:8 a=RjPDKtDqiy2f7rW6hKgA:9 a=BQbBQ-zkD3WcWA8U:21 a=FpCIXuNfG5tgObC0:21 a=QEXdDO2ut3YA:10 a=ZUGwP7LCt9cA:10 a=fDaRge6A_D4A:10 a=_p-igaadiZEA:10 a=FSu5OgGmP5kA:10 a=ULaUcM2Ibn9MdPUUwucP:22 a=IjZwj45LgO3ly-622nXo:22 a=1RpNR2E4bTkVPcsa2RFZ:22 Subject: nosh version 1.30 To: FreeBSD Hackers , Debian users , Supervision References: <54430B41.3010301@NTLWorld.com> From: Jonathan de Boyne Pollard Message-ID: <76c00c13-4cc9-ed9c-f48f-81a3f050b80b@NTLWorld.com> Date: Sat, 31 Dec 2016 23:53:24 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <54430B41.3010301@NTLWorld.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 23:55:22 -0000 The nosh package is now up to version 1.30 . * http://jdebp.eu./Softwares/nosh/ * https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project * http://jdebp.info./Softwares/nosh/ service bundles --------------- As usual, there are more service bundles, including for the UWSGI "Emperor" and the new services in FreeBSD/TrueOS 11 such as ypldap. There are now services to run Sendmail in the same manner as the services that run exim. Note that this is slightly different to the old FreeBSD division of labour. There are individually controllable services for SMTP Submission, SMTP Relay, the Submission queue runner, and the Relay queue runner. doco ---- The Guide has been extended with several new chapters, including a gazetteer of interesting directories, a chapter on log file post-processing, a chapter on logging security, a chapter on per-user service management, and some notes for individual services. The commands list has moved from the blurb into the Guide, too, as it seems like something that an administrator might find handy to have available when there's no Internet connection. * http://jdebp.eu./Softwares/nosh/guide.html service management ------------------ There's now a hardlimit chain-loading command, analogous to softlimit. The convert-systemd-services utility now makes use of this and permits setting separate hard and soft limits, or only one or the other, with settings like LimitOFILE=32:128 and LimitNPROC=:infinity . There's now a local-reaper chain-loading command, that can turn "local reaper" status for the current process on or off. Have a care when using this, per the note on the manual page. There is a LocalReaper=true extension to systemd service units for this. netlink-datagram-socket-listen is now available on the BSDs for script compatibility. It always aborts with an address family error. There's a new hangup subcommand of system-control, equivalent to the existing -H option to svc . enhancements to system-control stop/start/reset and single-shot services ------------------------------------------------------------------------ This is the first big item for 1.30 : The start and stop subcommands of system-control now operate more quickly. Instead of polling once per second, they monitor the supervise/status files of each service that is in the process of being started and stopped, with kevent(). In addition, system-control now supports the notion of services that become ready when their main process has exited, marked with a new flag file in the service directory. convert-systemd-units has been modified to convert "oneshot" services to this, instead of to services that put all of the run code into the start program. Thus "oneshot" services that are running their actual main programs are reported as "running" by svstat, rather than as "starting". This takes advantage of the extended status information that service-manager has been writing to the status file since version 1.28. The sharp-eyed may have noticed that in version 1.28 the output of "svstat"/"system-control status" gained information about the exit statuses of the start, run, restart, and stop programs. This is what system-control now uses to detect whether ready-after-run services ran before they stopped. (Detection of ready-after-run services that are running with no processes, because they are "remain" services, can be and is done with just the daemontools-encore-compatible status information.) Old-style "oneshot"s will continue to work as before, as of course they become ready as soon as the run process is spawned, which is after they have run their programs as part of start. The benefit of this new style, apart from reporting a running service as actually "running", which should help with nagios monitoring and the like, is that "oneshot" services converted from systemd no longer have to be marked as RemainAfterExit=true in order to avoid a dummy "pause" process hanging around. This is the case for old-style "oneshot" services. They have to run something in run, after all, and that something has to keep running in order for the service to be considered ready and services ordered after it to be unblocked. A ready-after-run service, however, unblocks ordered-after services if it has reached the stopped state via a run, thus puts its programs in run, thus doesn't have to have a dummy pause process, and can be RemainAfterExit=false without adding to the process list. log file management ------------------- export-to-rsyslog had a bug that caused it to skip old log files (the @nnnnnnnnnnnnnnnnnnnnnnnn.s ones) in catch-up mode. This has been corrected. There is now a follow-log-directories command that can substitute for tail -F . It knows the actual structure of log directories, operates using one or more cursors like export-to-rsyslog does, and copes correctly with cyclog/multilog log rotation (which GNU tail, at least, apparently has problems with when the timing is particularly wrong on a loaded system). See also http://jdebp.eu./FGA/do-not-use-logrotate.html build ----- More warnings are now turned on with clang++ during the build, and a lot of the resultant warnings have been eliminated where appropriate. The check for eg++ in preference to g++ is now limited to OpenBSD, where (at least on OpenBSD 5.9) eg++ is still ahead of g++ by a wide margin. Per-user service management --------------------------- Changes in per-user service management are the second big item for 1.30 : The per-user service manager instances are now invoked via userenv, so all per-user services that you run under nosh service management, D-BUS servers or otherwise, will have your own HOME, SHELL, and USER set. Several per-user daemon softwares were expecting HOME to be set. To match what the Desktop Bus people are doing, the dbus socket path for the per-user D-BUS broker has changed from "/run/user/$USER/dbus/user_bus_socket" to "/run/user/$USER/bus". In theory, this is addressable (in D-BUS speak) as "unix:runtime=yes". In practice, there is no version of D-BUS available on stable/release FreeBSD, TrueOS, or Debian that understands this address syntax. So one still has to use "unix:path=/run/user/$USER/bus". The Desktop Bus people and the desktop environments people are also switching from per-login D-BUS brokers to per-user D-BUS brokers. The nosh toolset has already had this for over a year, since the middle of 2015. Each real-person user account has an optional per-user service management service (e.g. user-services@fred). What is new is that per-user service bundle areas are now populated with a whole load of service bundles for real services, many relating to GUI desktop environments, and the per-user D-BUS broker has moved to there, from being a system-level service bundle. The configuration import subsystem creates these new per-user service bundles in the home directories of individual real users, under ~fred/.config/service-bundles/services/ and ~fred/.config/service-bundles/targets/ (for user fred). These run per-user services for a whole load of things, from GNOME editor and emacs through dconf and KDE Notify to urxvtd and GNOME Terminal. The configuration import subsystem also sets up a bypass for D-BUS's broken "bus activation" mechanism, so that instead of attempting to run these D-BUS servers directly, the D-BUS broker instead tells the nosh per-user service manager to run them. This takes the form of a replacement dbus-daemon-launch-helper, and the per-user D-BUS brokers now employ a modified configuration file that invokes it. There's a full explanation of how this all works in the new chapter on demand-starting user-level Desktop Bus services in the nosh Guide. Notes: * For emacs as a per-user service, you must have a very recent emacs with its very-late-to-the-party --new-daemon option. * GNOME Weather and its interaction with GeoClue2 are only partly tested, because the versions of them available for the test platforms were attempting to contact a weather service that the U.S. Government discontinued in June 2016; and this was hardwired into their code.