From owner-freebsd-stable@freebsd.org Sun Jan 29 04:18:04 2017 Return-Path: Delivered-To: freebsd-stable@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 E5E78CC4CDE for ; Sun, 29 Jan 2017 04:18:04 +0000 (UTC) (envelope-from prvs=0202ebff89=ari@ish.com.au) Received: from fish.ish.com.au (202-161-115-54.static.tpgi.com.au [202.161.115.54]) (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 AD4EA1C28 for ; Sun, 29 Jan 2017 04:18:03 +0000 (UTC) (envelope-from prvs=0202ebff89=ari@ish.com.au) Received: from [10.242.2.7] (port=63324 helo=Aristedess-MacBook-Pro.local) by fish.ish.com.au with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1cXgte-0003lF-2w for freebsd-stable@freebsd.org; Sun, 29 Jan 2017 15:15:22 +1100 To: freebsd-stable From: Aristedes Maniatis Subject: Boot partition size Message-ID: Date: Sun, 29 Jan 2017 15:15:19 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pQrLu5AiIcPD82cwNSVHC4BsuP5w0bQDK" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 04:18:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pQrLu5AiIcPD82cwNSVHC4BsuP5w0bQDK Content-Type: multipart/mixed; boundary="7DhjG6891GgXbC7nUrL51JD24iLSXV3j9"; protected-headers="v1" From: Aristedes Maniatis To: freebsd-stable Message-ID: Subject: Boot partition size --7DhjG6891GgXbC7nUrL51JD24iLSXV3j9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable As recently as last October, the best official advice was to make a 64kB = boot partition. https://wiki.freebsd.org/action/diff/RootOnZFS/GPTZFSBoot/Mirror?action=3D= diff&rev1=3D16&rev2=3D17 Now that turns out to be absolutely terrible advice and some people (like= me) have dozens of machines that will never be upgradable to FreeBSD 11 = or higher. It looks like there is no reasonable method of upgrade that do= esn't involve replacing every hard disk on every machine (that's hundred = of disks) with larger models. I use a zvol for swap, so I can't make swap= smaller to solve the problem. I started with FreeBSD 4.1 and in 16 years... sigh... The ashift pain some years ago was also caused by FreeBSD default recomme= ndations and settings not anticipating future needs quickly enough. But t= his mess now is completely self-inflicted foot shooting. 1. Why is the recommendation now 128kB and not much much higher? When tha= t limit is broken in a couple of years, will there be another round of an= noyed users? Is someone concerned that ZFS users are running hard disks o= ver under 500Mb and need to save space? Surely the recommendation should = be 512kB? 2. Is there any possible short term future where ZFS volumes can be shrun= k, or will I be replacing every hard disk (or rebuilding the machine from= scratch)? 3. Is there any possibility of getting a gptzfsboot which is 64kB but mis= sing certain features I might not need? eg. a RAIDZ2 version that skips s= upport for RAIDZ3 4. Will support be added to freebsd-update to warn users BEFORE they try = to upgrade and kill their system? Please cc me, I'm not subscribed. Ari Maniatis --=20 --------------------------> Aristedes Maniatis CEO, ish https://www.ish.com.au GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A --7DhjG6891GgXbC7nUrL51JD24iLSXV3j9-- --pQrLu5AiIcPD82cwNSVHC4BsuP5w0bQDK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAliNbFgACgkQ72p9Lj5JECqxiQCdHe9aJKtLKFtYOb14g//hLkx3 0wsAniP/GdSMJiu2B/u+ZivYN2jLfsYx =VSmB -----END PGP SIGNATURE----- --pQrLu5AiIcPD82cwNSVHC4BsuP5w0bQDK-- From owner-freebsd-stable@freebsd.org Sun Jan 29 04:50:36 2017 Return-Path: Delivered-To: freebsd-stable@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 DDBDDCC594C for ; Sun, 29 Jan 2017 04:50:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B09B8C61 for ; Sun, 29 Jan 2017 04:50:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id c7so82085154itd.1 for ; Sat, 28 Jan 2017 20:50:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=w6qjF9hGQKv2w2m0tUqu6Jq3z7+iLthZc+eac1CMH9M=; b=xwxbb5+PwAf+puElrV/cv/dG5+xEgb7XpuNjEchdq54KDKI3t11O3x5TPmKtY3T+0j 87Zlh77lPG3JWNKaecTAWrN3OZibtnr10TuZ+HmlWxkv21C4yennjjjt6sw+AR45e3pH xMVE/WOuCDJFCfl2KjXyoD12MXo3GKDSjsura51ZpbQ2mT5iIVocKNOg8OauRsYFCtEH 9CRnMbysNe3xJJUQGq4d3o4tgGjk+y4FbTvgzaAQ7L4ZtCATJ4/9d9JJz4eOedFW6DlO 9cwHKET/YzOMC0fj1ehu1tZiislL+4Fe6QcHSRXyQh3tPPOHs9BItHEDBfeUK5Fnd0sb Illw== 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:content-transfer-encoding; bh=w6qjF9hGQKv2w2m0tUqu6Jq3z7+iLthZc+eac1CMH9M=; b=jSaG7127cwty66jMnCYjlehkgq4ILlymzdhzXFdNoL2GS4KBVpiR2VTOEoSyXzYw9X vcUPoBCPrwiKyQD0N/bIb8OLKbY3pyg1oLzf6nkJ+H0VSwLgGBXQBRAnBLTT5UApQT36 HUI98/pLKsoF2fzk9oiARkyH3wQwJCZAW7n95kdy2LZDPNQUXDiK4lymwEslHd9US7sR YfejwsFBdTLNVjPawtN1rtUCr6tpiEGkrVxFj/2m4jhsji4lqQGRz5s6JwqEr5lh+85v oM9D6kUltg32QSc1eN4sEFAWpFYPHAnXbruMhStP9R5wJGh+e83UiTWt2b9uNTXRWi/8 6k6Q== X-Gm-Message-State: AIkVDXIdilq/+Dv1nyb9Gn92rA2NaEpTJ4Na1nikzUFfvnyYKIAW2RDsFNCD7H2Q1FmQrwzeKz9VA3yBTStpEw== X-Received: by 10.36.116.71 with SMTP id o68mr11236303itc.60.1485665435868; Sat, 28 Jan 2017 20:50:35 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.145.217 with HTTP; Sat, 28 Jan 2017 20:50:35 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Sat, 28 Jan 2017 21:50:35 -0700 X-Google-Sender-Auth: foaf9btj7_mMW-Ztd1Enp3p-2h0 Message-ID: Subject: Re: Boot partition size To: Aristedes Maniatis Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 04:50:37 -0000 On Sat, Jan 28, 2017 at 9:15 PM, Aristedes Maniatis wrote: > As recently as last October, the best official advice was to make a 64kB = boot partition. > > https://wiki.freebsd.org/action/diff/RootOnZFS/GPTZFSBoot/Mirror?action= =3Ddiff&rev1=3D16&rev2=3D17 > > > Now that turns out to be absolutely terrible advice and some people (like= me) have dozens of machines that will never be upgradable to FreeBSD 11 or= higher. It looks like there is no reasonable method of upgrade that doesn'= t involve replacing every hard disk on every machine (that's hundred of dis= ks) with larger models. I use a zvol for swap, so I can't make swap smaller= to solve the problem. > > I started with FreeBSD 4.1 and in 16 years... sigh... If things boot now, you won't have to upgrade the boot blocks. It isn't done by default, and the older boot blocks will boot newer /boot/loader versions. > The ashift pain some years ago was also caused by FreeBSD default recomme= ndations and settings not anticipating future needs quickly enough. But thi= s mess now is completely self-inflicted foot shooting. > > > 1. Why is the recommendation now 128kB and not much much higher? When tha= t limit is broken in a couple of years, will there be another round of anno= yed users? Is someone concerned that ZFS users are running hard disks over = under 500Mb and need to save space? Surely the recommendation should be 512= kB? Unless you are running on tiny disks, you should use 512kB for maximum future proofing. Given the bloat that's happened in boot1/boot2 over the years, this is the only sensible default. > 2. Is there any possible short term future where ZFS volumes can be shrun= k, or will I be replacing every hard disk (or rebuilding the machine from s= cratch)? Not easily. However, there's several options available to you: (1) not upgrading the boot partition (2) shrinking a swap partition to snag some space (3) putting a larger boot partition at the 'end' of the disk where there's usually runt sectors due to how gpart (bogusly imho, but I've not been successful at advocating this viewpoint) rounds. There's up to an entire cylinder at the end (though LBAs make CHS bogus), which might be useful. It's also possible to move the start of the boot partition to a smaller LBA, which gives us more than the 44k we currently have. We may also be able to write a smaller GPT area if we use only a couple of partitions on the disk. The only caveat in doing this is that pmbr reads the entire partition in, and it has to be less than about 534k in size. There's no size header on it. > 3. Is there any possibility of getting a gptzfsboot which is 64kB but mis= sing certain features I might not need? eg. a RAIDZ2 version that skips sup= port for RAIDZ3 64k is likely an unrealistic goal. We're crowding that limit today when we remove the SKEIN code. Removing it just removes the ability to boot encrypted ZFS volumes. However, the boot blocks on the disks aren't normally upgraded, and if they are booting your system ZFS volumes today, they are necessarily not encrypted. While the boot blocks fit into 64k today with some crazy gymnastics, upgrades in compiler technology likely will make this not a realistic goal (or alternatively, a lot of work). > 4. Will support be added to freebsd-update to warn users BEFORE they try = to upgrade and kill their system? Boot partitions usually aren't upgraded, so I'm not sure this is an issue. The project doesn't upgrade boot blocks by default. While there have been some events in the past that necessitated the upgrade, they have been rare and kinda optional. In this case, there's no compelling reason to upgrade the boot blocks that I can see... A quick look at freebsd-update shows no calls to gpart or dd, which is necessary to change them. Warner > > > Please cc me, I'm not subscribed. > > > Ari Maniatis > > > -- > --------------------------> > Aristedes Maniatis > CEO, ish > https://www.ish.com.au > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > From owner-freebsd-stable@freebsd.org Sun Jan 29 05:43:54 2017 Return-Path: Delivered-To: freebsd-stable@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 30D48CC27EA for ; Sun, 29 Jan 2017 05:43:54 +0000 (UTC) (envelope-from prvs=0202ebff89=ari@ish.com.au) Received: from fish.ish.com.au (202-161-115-54.static.tpgi.com.au [202.161.115.54]) (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 DD4791FF6 for ; Sun, 29 Jan 2017 05:43:52 +0000 (UTC) (envelope-from prvs=0202ebff89=ari@ish.com.au) Received: from [10.242.2.3] (port=63854 helo=Aristedess-MacBook-Pro.local) by fish.ish.com.au with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1cXiH7-0008SN-03; Sun, 29 Jan 2017 16:43:41 +1100 Subject: Re: Boot partition size To: Warner Losh References: Cc: freebsd-stable From: Aristedes Maniatis Message-ID: <54f66195-2929-ef8c-ac53-deaec574c182@ish.com.au> Date: Sun, 29 Jan 2017 16:43:37 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rL5axKutVWHgo7raGgiE7St7sv5LQSVqW" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 05:43:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rL5axKutVWHgo7raGgiE7St7sv5LQSVqW Content-Type: multipart/mixed; boundary="Jsg592IK9vor78sjCEDpr2FWiMIt3B4sk"; protected-headers="v1" From: Aristedes Maniatis To: Warner Losh Cc: freebsd-stable Message-ID: <54f66195-2929-ef8c-ac53-deaec574c182@ish.com.au> Subject: Re: Boot partition size References: In-Reply-To: --Jsg592IK9vor78sjCEDpr2FWiMIt3B4sk Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks for your reply Warner, On 29/1/17 3:50pm, Warner Losh wrote: > Unless you are running on tiny disks, you should use 512kB for maximum > future proofing. Given the bloat that's happened in boot1/boot2 over > the years, this is the only sensible default. Then you ('you' in the very generic FreeBSD committers with permission se= nse) should get the wiki changed (link in my previous email) to give bett= er advice. The advice of 128kB seems bad. More people will be hurt. =20 >> 2. Is there any possible short term future where ZFS volumes can be sh= runk, or will I be replacing every hard disk (or rebuilding the machine f= rom scratch)? > Not easily. However, there's several options available to you: (1) not > upgrading the boot partition That seems contrary to the advice that zpool provides when you upgrade a = pool. It specifically tells you that it is really important to upgrade th= e boot partition. But it doesn't tell you this is impossible due to space= requirements *before* you upgrade the pool. Is your suggestion to continue upgrading the OS, but never upgrade the po= ol? > (2) shrinking a swap partition to snag > some space=20 Yes, except I put my swap into a zvol. I did this when I lost a disk once= with a dedicated swap partition and that caused the system to crash. So = I realised that dedicated swap was a really bad idea and I needed to choo= se between zvol and gmirror. I chose zvol to avoid having one more thing = to check and worry about. > (3) putting a larger boot partition at the 'end' of the > disk where there's usually runt sectors due to how gpart (bogusly > imho, but I've not been successful at advocating this viewpoint) > rounds. There's up to an entire cylinder at the end (though LBAs make > CHS bogus), which might be useful. It's also possible to move the > start of the boot partition to a smaller LBA, which gives us more than > the 44k we currently have. We may also be able to write a smaller GPT > area if we use only a couple of partitions on the disk. I read that the boot partition had to be the first partition on disk. Is = that wrong? > In this case, there's no compelling > reason to upgrade the boot blocks that I can see... A quick look at > freebsd-update shows no calls to gpart or dd, which is necessary to > change them. But if we are using new ZFS code, and we upgrade the zpool, might that no= t require new boot code to be able to boot the system? I've already got one system I upgraded to FreeBSD 11, upgraded the pool o= nce everything looked good, and now I cannot upgrade the boot code. I don= 't want to restart the machine... ever. That's possibly unrealistic, alth= ough I could boot from USB in an emergency I guess. Ari Maniatis --=20 --------------------------> Aristedes Maniatis CEO, ish https://www.ish.com.au GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A --Jsg592IK9vor78sjCEDpr2FWiMIt3B4sk-- --rL5axKutVWHgo7raGgiE7St7sv5LQSVqW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAliNgQkACgkQ72p9Lj5JECpUMQCbB4DbCY7KnNFYFhuVc03xhZlU ykwAnjtR3Gb8IAk2r/OyW/weKMHpjJ9f =Busl -----END PGP SIGNATURE----- --rL5axKutVWHgo7raGgiE7St7sv5LQSVqW-- From owner-freebsd-stable@freebsd.org Sun Jan 29 14:12:48 2017 Return-Path: Delivered-To: freebsd-stable@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 26204CC7E6D for ; Sun, 29 Jan 2017 14:12:48 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 DFBB1C30 for ; Sun, 29 Jan 2017 14:12:47 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cXqDk-000KNs-Qm; Sun, 29 Jan 2017 14:12:44 +0000 Date: Sun, 29 Jan 2017 14:12:44 +0000 From: Gary Palmer To: Aristedes Maniatis Cc: freebsd-stable Subject: Re: Boot partition size Message-ID: <20170129141244.GA63867@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 14:12:48 -0000 On Sun, Jan 29, 2017 at 03:15:19PM +1100, Aristedes Maniatis wrote: > As recently as last October, the best official advice was to make a 64kB boot partition. > > https://wiki.freebsd.org/action/diff/RootOnZFS/GPTZFSBoot/Mirror?action=diff&rev1=16&rev2=17 > > > Now that turns out to be absolutely terrible advice and some people (like me) have dozens of machines that will never be upgradable to FreeBSD 11 or higher. It looks like there is no reasonable method of upgrade that doesn't involve replacing every hard disk on every machine (that's hundred of disks) with larger models. I use a zvol for swap, so I can't make swap smaller to solve the problem. > > I started with FreeBSD 4.1 and in 16 years... sigh... > > The ashift pain some years ago was also caused by FreeBSD default recommendations and settings not anticipating future needs quickly enough. But this mess now is completely self-inflicted foot shooting. > > > 1. Why is the recommendation now 128kB and not much much higher? When that limit is broken in a couple of years, will there be another round of annoyed users? Is someone concerned that ZFS users are running hard disks over under 500Mb and need to save space? Surely the recommendation should be 512kB? > > 2. Is there any possible short term future where ZFS volumes can be shrunk, or will I be replacing every hard disk (or rebuilding the machine from scratch)? It is highly unlikely that ZFS volumes will be able to be reduced in size even in the long term. I believe that requires a piece of work that has been rated as very difficult to do without violating layering policies inside the ZFS code. The alternative is, assuming you have a pool with redundancy (e.g. mirror) is to do a backup, drop one half of the mirror, create a new pool on the now unused disk, zfs send | zfs receive, boot from the new pool and then drop the old pool and add the disk to the mirror It's a pain and a bit of a shuffle but it's possible. I did it on my server once when I found that FreeBSD 9 didn't detect the disks as 4k and the alignment was all wrong. I worked through the procedure in a VM to validate it first, but found that in production I'd managed to hard code the boot pool name in /boot/loader.conf which meant that it didn't reboot and use the bootfs flag on the pool, it just sat at the "Cannot mount root" prompt. Took me a while to find that loader.conf setting and kill it. Regards, Gary > > 3. Is there any possibility of getting a gptzfsboot which is 64kB but missing certain features I might not need? eg. a RAIDZ2 version that skips support for RAIDZ3 > > 4. Will support be added to freebsd-update to warn users BEFORE they try to upgrade and kill their system? > > > > Please cc me, I'm not subscribed. > > > Ari Maniatis > > > -- > --------------------------> > Aristedes Maniatis > CEO, ish > https://www.ish.com.au > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > From owner-freebsd-stable@freebsd.org Sun Jan 29 17:13:59 2017 Return-Path: Delivered-To: freebsd-stable@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 A3531CC7588; Sun, 29 Jan 2017 17:13:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AD14337; Sun, 29 Jan 2017 17:13:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-241-75.lns20.per4.internode.on.net [121.45.241.75]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v0THDlUr000341 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 29 Jan 2017 09:13:51 -0800 (PST) (envelope-from julian@freebsd.org) To: freebsd-current , FreeBSD Stable From: Julian Elischer Subject: ldd linker script /usr/lib/libc.so fail Message-ID: <5278922c-a736-26ec-17a8-d9a1a684439e@freebsd.org> Date: Mon, 30 Jan 2017 01:13:42 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 17:13:59 -0000 Hi the linker script /usr/lib/libc.so fails when you are using the --sysroot options because it contains absolute paths. Does anyone know if there is a way to add the sysroot to the script? currently teh on ein our sysroot looks like: $ cat /usr/build/buildroot/tools/x86_FBSD1X_gcc4.2.4/usr/lib/libc.so /* $FreeBSD$ */ GROUP ( /lib/libc.so.7 /usr/lib/libc_nonshared.a /usr/lib/libssp_nonshared.a ) but I'd like to do something like: GROUP ( ${sysroot}/lib/libc.so.7 ${sysroot}/usr/lib/libc_nonshared.a ${sysroot}/usr/lib/libssp_nonshared.a ) but don't think I can do that from what I see below however it shouldn't be needed. Is this a bug in our version of ld? or am I misreading it? I quote from one such source : https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Using_ld_the_GNU_Linker/simple-commands.html ================================================ INPUT(file, file, …), INPUT(file file …) The INPUT command directs the linker to include the named files in the link, as though they were named on the command line. For example, if you always want to include subr.o any time you do a link, but you can't be bothered to put it on every link command line, then you can put INPUT (subr.o) in your linker script. In fact, if you like, you can list all of your input files in the linker script, and then invoke the linker with nothing but a -T option. In case a /sysroot prefix/ is configured, and the filename starts with the / character, and the script being processed was located inside the /sysroot prefix/, the filename will be looked for in the /sysroot prefix/. Otherwise, the linker will try to open the file in the current directory. If it is not found, the linker will search through the archive library search path. See the description of -L in Section 3.1 /Command Line Options/ . If you use INPUT (-lfile), ld will transform the name to libfile.a, as with the command line argument -l. When you use the INPUT command in an implicit linker script, the files will be included in the link at the point at which the linker script file is included. This can affect archive searching. GROUP(file, file, …), GROUP(file file …) The GROUP command is like INPUT, except that the named files should all be archives, and they are searched repeatedly until no new undefined references are created. ========================================= From owner-freebsd-stable@freebsd.org Sun Jan 29 17:36:56 2017 Return-Path: Delivered-To: freebsd-stable@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 8B3BFCC7DB6; Sun, 29 Jan 2017 17:36:56 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D098135B; Sun, 29 Jan 2017 17:36:56 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-241-75.lns20.per4.internode.on.net [121.45.241.75]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v0THap9Y000435 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 29 Jan 2017 09:36:54 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: [IGNORE] ldd linker script /usr/lib/libc.so fail [IGNORE] To: freebsd-current , FreeBSD Stable References: <5278922c-a736-26ec-17a8-d9a1a684439e@freebsd.org> From: Julian Elischer Message-ID: <4439daf4-4173-110d-bd15-d144fed91ceb@freebsd.org> Date: Mon, 30 Jan 2017 01:36:45 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <5278922c-a736-26ec-17a8-d9a1a684439e@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 17:36:56 -0000 Tracked this down to a rogue copy of libc.so in an unexpected place which was being found earlier than the real one. On 30/1/17 1:13 am, Julian Elischer wrote: > Hi > > the linker script /usr/lib/libc.so fails when you are using the > --sysroot options because it > > contains absolute paths. > > > Does anyone know if there is a way to add the sysroot to the script? > > currently teh on ein our sysroot looks like: > > $ cat /usr/build/buildroot/tools/x86_FBSD1X_gcc4.2.4/usr/lib/libc.so > /* $FreeBSD$ */ > GROUP ( /lib/libc.so.7 /usr/lib/libc_nonshared.a > /usr/lib/libssp_nonshared.a ) > > but I'd like to do something like: > > GROUP ( ${sysroot}/lib/libc.so.7 ${sysroot}/usr/lib/libc_nonshared.a > ${sysroot}/usr/lib/libssp_nonshared.a ) > > but don't think I can do that > > from what I see below however it shouldn't be needed. > > Is this a bug in our version of ld? or am I misreading it? > > > I quote from one such source : > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Using_ld_the_GNU_Linker/simple-commands.html > > > ================================================ > INPUT(file, file, …), INPUT(file file …) > > The INPUT command directs the linker to include the named files in > the link, as though they were named on the command line. > > For example, if you always want to include subr.o any time you do > a link, but you can't be bothered to put it on every link command > line, then you can put INPUT (subr.o) in your linker script. > > In fact, if you like, you can list all of your input files in the > linker script, and then invoke the linker with nothing but a -T > option. > > In case a /sysroot prefix/ is configured, and the filename starts > with the / character, and the script being processed was located > inside the /sysroot prefix/, the filename will be looked for in > the /sysroot prefix/. Otherwise, the linker will try to open the > file in the current directory. If it is not found, the linker will > search through the archive library search path. See the > description of -L in Section 3.1 /Command Line Options/ > . > > > If you use INPUT (-lfile), ld will transform the name to > libfile.a, as with the command line argument -l. > > When you use the INPUT command in an implicit linker script, the > files will be included in the link at the point at which the > linker script file is included. This can affect archive searching. > > GROUP(file, file, …), GROUP(file file …) > > The GROUP command is like INPUT, except that the named files > should all be archives, and they are searched repeatedly until no > new undefined references are created. > > ========================================= > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-stable@freebsd.org Mon Jan 30 03:20:51 2017 Return-Path: Delivered-To: freebsd-stable@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 57D98CC610A for ; Mon, 30 Jan 2017 03:20:51 +0000 (UTC) (envelope-from fjwcash@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 13900155F; Mon, 30 Jan 2017 03:20:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id s140so117240056qke.0; Sun, 29 Jan 2017 19:20:51 -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=2uNesTdRM3u+gAQSI7tJ6uKDFS+8N7QjbCYaa9g15cg=; b=FWzrZAuO3kHstm6sK+mChIJ6AecwtsAWjyeA1dAq0L5lX1Iy5FigJR4NvBSOtAU84C hU3zdC5SkBRAWOQfFiHMAB8uzBeEytLQpdYTV+EGAysYIp+asFmLy/lYJr0C5aPFDapp UbTRXxtrXQsr3jCAeFXLq3f87Q/1Fil+wQo2Bu0Nql9NKc4+9QjSkNUbyiAcJIJu9rgV Y67fasYqPeUp5p4eJPeY5bwYprCVV2URu2CO0bzgVa7jktUaFMD4dh3X2BIp6KX3GEU+ ofKMcmqy7XdoviALZ/Rlz13UP/QF9CZY13r8XrFwHOuuX5sp7nIZ/eYC8BEEBCKBtFLM mqdg== 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=2uNesTdRM3u+gAQSI7tJ6uKDFS+8N7QjbCYaa9g15cg=; b=GGBYMQnCrg0EpflOcvbAo5BRSKh8+iw9qyzLoqzMw7lm4U7lTSoPxze+NiPNfdFNP5 Eps79R+0qoXHb8LUVJ9raW3UXBEyPOEcGthRy1WhEGFZ+1khbycmm/aMQ1hvjYLplWSD ZgnKYhKZr4ivJEixlsoBm7riF/IoYlHSI/vHR2KtVHYphg2N9ZDdJ+z0uXQpHnuN9HeP LhphNeMMr5TLICilf3l/gOEjTmZa8k8f0Zs6J2+Tsk6hlUdNowkaayrPccsT2xvZStia X/yM7IkHNHlYev3qvLdouBzEo5U9XuDTnbbbcqGKWmP1i4FJcMmYD234SdFUQSYxVul+ 6Psg== X-Gm-Message-State: AIkVDXLjGwhbc/BMsQcCa9mg5UC40Z3IeT0mKCqp0yGyf1T87wt7IdGWAlOMTjsQ6PVOL2EgzOAjMteofadnGg== X-Received: by 10.55.95.131 with SMTP id t125mr449724qkb.279.1485746450152; Sun, 29 Jan 2017 19:20:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.28.202 with HTTP; Sun, 29 Jan 2017 19:20:49 -0800 (PST) Received: by 10.140.28.202 with HTTP; Sun, 29 Jan 2017 19:20:49 -0800 (PST) In-Reply-To: <20170129141244.GA63867@in-addr.com> References: <20170129141244.GA63867@in-addr.com> From: Freddie Cash Date: Sun, 29 Jan 2017 19:20:49 -0800 Message-ID: Subject: Re: Boot partition size To: Gary Palmer Cc: FreeBSD Stable , Aristedes Maniatis Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 03:20:51 -0000 On Jan 29, 2017 6:13 AM, "Gary Palmer" wrote: On Sun, Jan 29, 2017 at 03:15:19PM +1100, Aristedes Maniatis wrote: > As recently as last October, the best official advice was to make a 64kB boot partition. > > https://wiki.freebsd.org/action/diff/RootOnZFS/ GPTZFSBoot/Mirror?action=diff&rev1=16&rev2=17 > > > Now that turns out to be absolutely terrible advice and some people (like me) have dozens of machines that will never be upgradable to FreeBSD 11 or higher. It looks like there is no reasonable method of upgrade that doesn't involve replacing every hard disk on every machine (that's hundred of disks) with larger models. I use a zvol for swap, so I can't make swap smaller to solve the problem. > > I started with FreeBSD 4.1 and in 16 years... sigh... > > The ashift pain some years ago was also caused by FreeBSD default recommendations and settings not anticipating future needs quickly enough. But this mess now is completely self-inflicted foot shooting. > > > 1. Why is the recommendation now 128kB and not much much higher? When that limit is broken in a couple of years, will there be another round of annoyed users? Is someone concerned that ZFS users are running hard disks over under 500Mb and need to save space? Surely the recommendation should be 512kB? > > 2. Is there any possible short term future where ZFS volumes can be shrunk, or will I be replacing every hard disk (or rebuilding the machine from scratch)? It is highly unlikely that ZFS volumes will be able to be reduced in size even in the long term. I believe that requires a piece of work that has been rated as very difficult to do without violating layering policies inside the ZFS code. The alternative is, assuming you have a pool with redundancy (e.g. mirror) is to do a backup, drop one half of the mirror, create a new pool on the now unused disk, zfs send | zfs receive, boot from the new pool and then drop the old pool and add the disk to the mirror You can also format a larger drive with the correct partition sizes, and do a "zpool replace" (for raidz vdevs) or "zpool detach/attach" (for mirror vdevs). No send/recv required. And, you may be able to do that on the existing disks, as ZFS now leaves a MB or two of "slack space" at the end of the device used in the vdev. This allows for using drives/partitions that are the same size in MB but have different numbers of sectors. This was an issue on the early ZFS days. So, you may be able to resize the freebsd-zfs partition by a handful of KB without actually changing the size of the vdev. Cheers, Freddie From owner-freebsd-stable@freebsd.org Mon Jan 30 03:41:34 2017 Return-Path: Delivered-To: freebsd-stable@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 D78C6CC65F5 for ; Mon, 30 Jan 2017 03:41:34 +0000 (UTC) (envelope-from prvs=0203e18048=ari@ish.com.au) Received: from fish.ish.com.au (202-161-115-54.static.tpgi.com.au [202.161.115.54]) (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 997C01ED3 for ; Mon, 30 Jan 2017 03:41:33 +0000 (UTC) (envelope-from prvs=0203e18048=ari@ish.com.au) Received: from ip-136.ish.com.au ([203.29.62.136]:52695) by fish.ish.com.au with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1cY2qF-0005wU-2F; Mon, 30 Jan 2017 14:41:19 +1100 Subject: Re: Boot partition size To: Freddie Cash , Gary Palmer References: <20170129141244.GA63867@in-addr.com> Cc: FreeBSD Stable From: Aristedes Maniatis Message-ID: <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> Date: Mon, 30 Jan 2017 14:41:16 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iQeOmGAst09KKmExv35b7JxurdkcFCpi8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 03:41:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iQeOmGAst09KKmExv35b7JxurdkcFCpi8 Content-Type: multipart/mixed; boundary="eK9rjVJGwHIeWmbAwp6b3s3k8LUjvigcM"; protected-headers="v1" From: Aristedes Maniatis To: Freddie Cash , Gary Palmer Cc: FreeBSD Stable Message-ID: <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> Subject: Re: Boot partition size References: <20170129141244.GA63867@in-addr.com> In-Reply-To: --eK9rjVJGwHIeWmbAwp6b3s3k8LUjvigcM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 30/1/17 2:20pm, Freddie Cash wrote: > And, you may be able to do that on the existing disks, as ZFS now leave= s a MB or two of "slack space" at the end of the device used in the vdev.= This allows for using drives/partitions that are the same size in MB but= have different numbers of sectors. This was an issue on the early ZFS da= ys. >=20 > So, you may be able to resize the freebsd-zfs partition by a handful of= KB without actually changing the size of the vdev. Brilliant, thank you. That worked a treat with a new boot size of 256k. Note that this page: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror= needs to be adjusted. This line: gpart add -b 34 -s 128k -t freebsd-boot ad0 needs to instead be gpart add -a 4k -s 512k -t freebsd-boot ad0 I don't have edit rights. Probably someone needs to clean up and merge ma= ny of these pages: https://wiki.freebsd.org/RootOnZFS/ Ari --=20 --------------------------> Aristedes Maniatis CEO, ish https://www.ish.com.au GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A --eK9rjVJGwHIeWmbAwp6b3s3k8LUjvigcM-- --iQeOmGAst09KKmExv35b7JxurdkcFCpi8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAliOtdwACgkQ72p9Lj5JECpT4gCdE8D8Ih2TBi/pnhAR1uxhHAOn ODcAnjdcfRGdVAxQLvBiTxUue93w2EbS =ICch -----END PGP SIGNATURE----- --iQeOmGAst09KKmExv35b7JxurdkcFCpi8-- From owner-freebsd-stable@freebsd.org Mon Jan 30 18:41:23 2017 Return-Path: Delivered-To: freebsd-stable@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 C9184CC8588 for ; Mon, 30 Jan 2017 18:41:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B700D9CD for ; Mon, 30 Jan 2017 18:41:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id B3587CC8587; Mon, 30 Jan 2017 18:41:23 +0000 (UTC) Delivered-To: stable@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 B3078CC8586 for ; Mon, 30 Jan 2017 18:41:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (ingresso-1-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:411::2]) (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 852E99CB for ; Mon, 30 Jan 2017 18:41:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cYGtF-000CnM-VK for stable@freebsd.org; Mon, 30 Jan 2017 18:41:21 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87_1 (FreeBSD)) (envelope-from ) id 1cYGtF-000I5u-Sz for stable@freebsd.org; Mon, 30 Jan 2017 18:41:21 +0000 To: stable@freebsd.org Subject: HASt and write amplification on the seconday Message-Id: From: Pete French Date: Mon, 30 Jan 2017 18:41:21 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 18:41:23 -0000 I have a pair of machines which I have been runnig HAST on for a number of years. It works well, it does what Ineed it to do, and I havent considered the details until recently. As I udnesratnd it though, the minimum size of block copied is set by default to something quite arge (2 meg). I see whay, but as I am using ZFS on top I am generating lots of writes which are scattered across the disc (ZFS not known for keeping writes all in the same place!). So, is each 512 byte write being turned into a 2 meg write on the secondary ? If so this worries me, as I am about to replcae these drives with SSD's, which I do not want to wearn out with excessive writes. Am I worrying over nothing ? Should I try and tune the HAST sizes and the zpool ashift to match, or will that trash performances 9some limited experiments suggest it will). -pete. From owner-freebsd-stable@freebsd.org Tue Jan 31 12:03:33 2017 Return-Path: Delivered-To: freebsd-stable@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 15FC7CC9520 for ; Tue, 31 Jan 2017 12:03:33 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 CE558FB2; Tue, 31 Jan 2017 12:03:32 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id l126so28176322qkc.1; Tue, 31 Jan 2017 04:03:32 -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=hPcxOwt3XvRHnco45CzG4oflR2Biw/0THD3eTlJf/DQ=; b=QCTAT0WR3xTsdJ2Ybtj9MWKWg0xhtTXZH8nUrqRBxyNxKNv/5c1TxEGiQbfevuTYPw c6RpapxlEOMRAnannV7WBNyAQecKnmZrStcKwqco8pcEaxvcII2KlqcZGSxEZhgMtnhi afUGUaXPryEv/6HeRf3ezPvTaGvQdbEUp9MtxDABZqGDHakSklZMgS3U36HSPRB2hj9o q7X85nyDldKwmL/3zNM+riIWNzOzbk1FTTPmxa5In2em7d2/x78jLAUcxl7Bqq7qkc+o /3e1QU6WmUC3AEiuw30YmjEq/vYx2uIOEIu7hSuHPECyLOMGBAdJzRcLnmqFG5fLGQ/j CehA== 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=hPcxOwt3XvRHnco45CzG4oflR2Biw/0THD3eTlJf/DQ=; b=h7K6l6V1bxwr1EnSegz061S3sciNfTMLim3UY5zTvChVyZGeSyOTtzs2lfDnT34gW1 0JqQ3wK7x03P4qni/zFBYXax9yDR3vYafxzmnZ92RBOSPaTP7JnYx4j/q8EuJneTOLWR HqD1DVK2/ucLG9BwDxYBF8rR5/4r4P+6SoxJrKn9tMLBNiEYecg4pwhVZELiV9AA6EQ0 qwBg0fmD8eB7484y2W0ZZIoI+GWfU1MgUbga3J5I3aNMIhN6aNp6obSPfvTUUgwWTUIM kAXxJ19FIgMkJuhjKfG4+pDE6a2O7Ttaa428/ozAKzMUw4+jVbGRPY2nFn6te9Ruw/Sk Hfww== X-Gm-Message-State: AIkVDXIPhIg3kE/LYqzbZ3+rPy9u+ydPeXz/HiAp4jHMzqUkPvDpFfDzLLSN0H5VDe/FA1jIvX76FL4h92ROIA== X-Received: by 10.55.137.69 with SMTP id l66mr28153926qkd.133.1485864211980; Tue, 31 Jan 2017 04:03:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.173.40 with HTTP; Tue, 31 Jan 2017 04:03:31 -0800 (PST) In-Reply-To: <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> From: krad Date: Tue, 31 Jan 2017 12:03:31 +0000 Message-ID: Subject: Re: Boot partition size To: Aristedes Maniatis Cc: Freddie Cash , Gary Palmer , FreeBSD Stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 12:03:33 -0000 Its worth noting you should also go for GPT layout and have a 100meg or so partition provisioned as well so you can do a uefi boot. Even if you arent going to use it right now. On 30 January 2017 at 03:41, Aristedes Maniatis wrote: > On 30/1/17 2:20pm, Freddie Cash wrote: > > And, you may be able to do that on the existing disks, as ZFS now leaves > a MB or two of "slack space" at the end of the device used in the vdev. > This allows for using drives/partitions that are the same size in MB but > have different numbers of sectors. This was an issue on the early ZFS days. > > > > So, you may be able to resize the freebsd-zfs partition by a handful of > KB without actually changing the size of the vdev. > > > Brilliant, thank you. That worked a treat with a new boot size of 256k. > > > Note that this page: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror > needs to be adjusted. This line: > > gpart add -b 34 -s 128k -t freebsd-boot ad0 > > needs to instead be > > gpart add -a 4k -s 512k -t freebsd-boot ad0 > > > I don't have edit rights. Probably someone needs to clean up and merge > many of these pages: https://wiki.freebsd.org/RootOnZFS/ > > > Ari > > > > -- > --------------------------> > Aristedes Maniatis > CEO, ish > https://www.ish.com.au > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > > From owner-freebsd-stable@freebsd.org Tue Jan 31 14:00:09 2017 Return-Path: Delivered-To: freebsd-stable@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 14305CCAC57 for ; Tue, 31 Jan 2017 14:00:09 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (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 83F181484 for ; Tue, 31 Jan 2017 14:00:08 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id k127so236914995vke.0 for ; Tue, 31 Jan 2017 06:00:08 -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=rBzJSkOhrLRfdUcE+pASX6s1YbNddxDMZ53mlPzg7XA=; b=YzqsPvA0RmxGOFJWXHfIrwg4GifC8zbpt0gxq9oOtMCS3uHOlgijZvGx5ICPCis86D l23ozY0xwiOWFOGLKgTXeFCa8U5y9kKz0GJjHPzuqANFb5IeZR1d4lDG/c0HnDYGmL9N HBUOOdPa+Lu+u/y+ZY9mb63JrXg+KQAV5IqejCa4Zu2AZfkdJSk06mAxhY9CONbgIjKZ WV0u4P2MAQe2WDJdpOcVb4E/7/bFFlMcvmSLeTPyYeCgnPcQOgOpG9oFzhiqdq0Z5Z2s ayG5Omtn/UD66zUWWnB9oEZCubDBA6ZzZq+6Pjz4P86VvYGsxMzQjz4vcUTk7jkr9MvF vQEw== 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=rBzJSkOhrLRfdUcE+pASX6s1YbNddxDMZ53mlPzg7XA=; b=EaSnxUlAcP5k1wyC4hl/F9ZGqenqxA0ptn96RmBxAbxIH1tM06yBN8JSXtTo59ePPJ WbYJ+OUuqaXus/wtGqaX5D9+qjZaYRqAXVSs8gWq+lWS0bywxjXQtY93z3pnqbcy1KG4 sjdHKuJ1GnBgvf+a4xnI9EbpDI4mjF5tfr/zbzs2W8ljOYwLgGIPRB6xEjZo7nwiB4qZ Vb0DCRqJdqzNfjK54wDwy46PELU0vsfCBuuQsNA1dCZeUG8kkmvFaJgTcBVUvp/GnYAP 3eLDKHt/8kqA+cfh3qGwTPX1PLs/8GC15hlfaxh7bX8zrE4IYZHOf+SUdtu00yYILUwb W8LQ== X-Gm-Message-State: AIkVDXJkBzzwvt3/3EyhYRGoD0lVRqH/ONCRi7X1QQyEQqkdqqKXq65qXc+SHDlu1HR9dUtXdf5WUuqxlNMxJA== X-Received: by 10.31.107.210 with SMTP id k79mr10318273vki.99.1485871202207; Tue, 31 Jan 2017 06:00:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.48.201 with HTTP; Tue, 31 Jan 2017 06:00:01 -0800 (PST) In-Reply-To: References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> From: Andreas Nilsson Date: Tue, 31 Jan 2017 15:00:01 +0100 Message-ID: Subject: Re: Boot partition size To: krad Cc: Aristedes Maniatis , FreeBSD Stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 14:00:09 -0000 Well, 100mb might be relevant if you ever want to dual-boot. The relevant efi file seems to be < 100k It may go up in size, but I doubt we will see a 100x increase. /A On Tue, Jan 31, 2017 at 1:03 PM, krad wrote: > Its worth noting you should also go for GPT layout and have a 100meg or so > partition provisioned as well so you can do a uefi boot. Even if you arent > going to use it right now. > > > On 30 January 2017 at 03:41, Aristedes Maniatis wrote: > > > On 30/1/17 2:20pm, Freddie Cash wrote: > > > And, you may be able to do that on the existing disks, as ZFS now > leaves > > a MB or two of "slack space" at the end of the device used in the vdev. > > This allows for using drives/partitions that are the same size in MB but > > have different numbers of sectors. This was an issue on the early ZFS > days. > > > > > > So, you may be able to resize the freebsd-zfs partition by a handful of > > KB without actually changing the size of the vdev. > > > > > > Brilliant, thank you. That worked a treat with a new boot size of 256k. > > > > > > Note that this page: https://wiki.freebsd.org/ > RootOnZFS/GPTZFSBoot/Mirror > > needs to be adjusted. This line: > > > > gpart add -b 34 -s 128k -t freebsd-boot ad0 > > > > needs to instead be > > > > gpart add -a 4k -s 512k -t freebsd-boot ad0 > > > > > > I don't have edit rights. Probably someone needs to clean up and merge > > many of these pages: https://wiki.freebsd.org/RootOnZFS/ > > > > > > Ari > > > > > > > > -- > > --------------------------> > > Aristedes Maniatis > > CEO, ish > > https://www.ish.com.au > > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Tue Jan 31 14:35:08 2017 Return-Path: Delivered-To: freebsd-stable@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 E0412CC9751 for ; Tue, 31 Jan 2017 14:35:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (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 B762D949 for ; Tue, 31 Jan 2017 14:35:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x244.google.com with SMTP id f200so4114106itf.3 for ; Tue, 31 Jan 2017 06:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aLJf5n+YlScvGOg1GyBl2MEjRtghqezufuSUhbr5s/8=; b=CQVxEOObl+1Ivi0YGQuZDpbC+AFXarrDR0ZR1ra51BEhbrzJwmhoeIjPpt+iGhT3oB N86atZhNmQRyMNKtbkhy0k6hv/L6LZ17r9xQJnOXQgwjBhi2RdBfGw9iVvDFc3arY6rr CAqQqe78V/L5s6qamF5rXP+3UfihuWhBbWC8iUrPloocLQguWa7tu+9dwSBK4IboqZ9a XtHCzEdD5ZOBrNs9pWKk4rBWml7sFf9U5a9ZQIPnFkt62whopThHwJVZ+2dpCNXSP7Xj u2+JQ62uZc6AVmDjI4ufFZas0SKyPgo1vaIa2n7U9kax5zV15/u917NaaUJm4iJJfGh3 Vh3w== 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=aLJf5n+YlScvGOg1GyBl2MEjRtghqezufuSUhbr5s/8=; b=WhqtA4zxcWwxUZcbJ2UeAeK79Blhtz4L2XkswOzcu7+7W+rvCu604VBXNAyPELxmDo dBsxkwknV5x+HSEY6LOlAUDhpdJtSycBV/23y2T/SbqcLvUYTdq5NaW56QaEV9/OAT7Y Wn5zu588zQ2hWHR6uUVaUz83o0AvOUGOW0CorcmSiVnwCekwtOEW3eEcVh7pB0se2tkh 0+NQpHwKn+6VJYaG5U65BsJrahGFL0BA4VFGxuiKNSggQPaO7ZjpR9oE99fvQuPLyVFt PIYID9RjLO+5sixZI1k5IxG3NI7ZgOU+36dcxlFaWxKw1CWwZgSpO7WlZ8szYPiRAChx xYww== X-Gm-Message-State: AIkVDXKwq1msRV/SjHaTq3bQPc8rUN1gHCBlBiFxaXmFWZU9OS8g5wQ3VXvQcJ+laUp83WzAfh3IYgttAwlCxg== X-Received: by 10.36.93.213 with SMTP id w204mr21740793ita.60.1485873307915; Tue, 31 Jan 2017 06:35:07 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.145.217 with HTTP; Tue, 31 Jan 2017 06:35:07 -0800 (PST) X-Originating-IP: [69.53.245.200] In-Reply-To: References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> From: Warner Losh Date: Tue, 31 Jan 2017 07:35:07 -0700 X-Google-Sender-Auth: RVWPqc9D2t612d0npMJ_KydF338 Message-ID: Subject: Re: Boot partition size To: Andreas Nilsson Cc: krad , FreeBSD Stable , Aristedes Maniatis Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 14:35:09 -0000 The UEFI standard suggests something large like 100MB. There are a number of firmware updating programs that run as .efi images. It would be prudent to allow more than the bare minimum in case you wind up needing them down the line. boot1.efi is likely to grow significantly in the future. Maybe not 100x, a 1MB is likely once it has all the features it needs. 10MB might be a safe upper bound. Warner On Tue, Jan 31, 2017 at 7:00 AM, Andreas Nilsson wrote: > Well, 100mb might be relevant if you ever want to dual-boot. The relevant > efi file seems to be < 100k > > It may go up in size, but I doubt we will see a 100x increase. > > /A > > On Tue, Jan 31, 2017 at 1:03 PM, krad wrote: > >> Its worth noting you should also go for GPT layout and have a 100meg or so >> partition provisioned as well so you can do a uefi boot. Even if you arent >> going to use it right now. >> >> >> On 30 January 2017 at 03:41, Aristedes Maniatis wrote: >> >> > On 30/1/17 2:20pm, Freddie Cash wrote: >> > > And, you may be able to do that on the existing disks, as ZFS now >> leaves >> > a MB or two of "slack space" at the end of the device used in the vdev. >> > This allows for using drives/partitions that are the same size in MB but >> > have different numbers of sectors. This was an issue on the early ZFS >> days. >> > > >> > > So, you may be able to resize the freebsd-zfs partition by a handful of >> > KB without actually changing the size of the vdev. >> > >> > >> > Brilliant, thank you. That worked a treat with a new boot size of 256k. >> > >> > >> > Note that this page: https://wiki.freebsd.org/ >> RootOnZFS/GPTZFSBoot/Mirror >> > needs to be adjusted. This line: >> > >> > gpart add -b 34 -s 128k -t freebsd-boot ad0 >> > >> > needs to instead be >> > >> > gpart add -a 4k -s 512k -t freebsd-boot ad0 >> > >> > >> > I don't have edit rights. Probably someone needs to clean up and merge >> > many of these pages: https://wiki.freebsd.org/RootOnZFS/ >> > >> > >> > Ari >> > >> > >> > >> > -- >> > --------------------------> >> > Aristedes Maniatis >> > CEO, ish >> > https://www.ish.com.au >> > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >> > >> > >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Tue Jan 31 19:52:12 2017 Return-Path: Delivered-To: freebsd-stable@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 CA52CCCA478 for ; Tue, 31 Jan 2017 19:52:12 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from ims11.isendservice.com.br (ims11.isendservice.com.br [54.232.115.234]) by mx1.freebsd.org (Postfix) with ESMTP id 47331C2B for ; Tue, 31 Jan 2017 19:52:12 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims11.isendservice.com.br (Postfix) with ESMTP id 381F84C0E4 for ; Tue, 31 Jan 2017 17:22:10 -0200 (BRST) Date: Tue, 31 Jan 2017 17:22:10 -0200 (BRST) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: joel.ferreira@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <1133367589.581398.1485890530160.JavaMail.root@ims11> Subject: =?ISO-8859-1?Q?O_Que_Voc=EA_Quer_ser_Amanh=E3=3F_Curso?= =?ISO-8859-1?Q?s_T=E9cnicos_2017_na_Faculdade_SENAI?= bounce-key: <2420-22522874-1630031> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 19:52:12 -0000 From owner-freebsd-stable@freebsd.org Tue Jan 31 20:59:07 2017 Return-Path: Delivered-To: freebsd-stable@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 4F3B8CCAF16 for ; Tue, 31 Jan 2017 20:59:07 +0000 (UTC) (envelope-from dwood@vaul-tec.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3EEBF1C36 for ; Tue, 31 Jan 2017 20:59:07 +0000 (UTC) (envelope-from dwood@vaul-tec.net) Received: by mailman.ysv.freebsd.org (Postfix) id 3E352CCAF15; Tue, 31 Jan 2017 20:59:07 +0000 (UTC) Delivered-To: stable@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 3DE2CCCAF14 for ; Tue, 31 Jan 2017 20:59:07 +0000 (UTC) (envelope-from dwood@vaul-tec.net) Received: from smtpout-1.iphouse.net (smtpout-1.iphouse.net [IPv6:2001:4980:0:4002::140]) by mx1.freebsd.org (Postfix) with ESMTP id 270471C35 for ; Tue, 31 Jan 2017 20:59:06 +0000 (UTC) (envelope-from dwood@vaul-tec.net) Received: from boron.staff.iphouse.net (fwext-5.staff.iphouse.net [216.250.176.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpout-1.iphouse.net (Postfix) with ESMTPSA id 3561033C47 for ; Tue, 31 Jan 2017 14:59:00 -0600 (CST) From: Dan Wood Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: SVN_UPDATE not respected by /usr/ports/Makefile? Message-Id: <0E4EBB09-750E-4194-9D6B-DA50D14C64A6@vaul-tec.net> Date: Tue, 31 Jan 2017 14:58:59 -0600 To: stable@freebsd.org X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 20:59:07 -0000 Using a fresh install of FreeBSD 11.0-RELEASE-p1, I was trying to use = /usr/bin/svnlite as a ports upgrade.=20 I've set SVN_UPDATE=3Dyes and SVN=3D/usr/bin/svnlite in /etc/make.conf = IAW the manfile for make.conf, but running 'make update' within = /usr/ports seems to try portsnap regardless. I haven't preseeded /usr/ports/ with svnlite, but I'm wondering if = there's any guidance regarding using svnlite or if there's a pending = update to the portion of the ports documentation regarding svn that = reflects svnlite as part of the base install. --=20 Dan Wood= From owner-freebsd-stable@freebsd.org Tue Jan 31 23:22:56 2017 Return-Path: Delivered-To: freebsd-stable@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 B16AFCCA2AD for ; Tue, 31 Jan 2017 23:22:56 +0000 (UTC) (envelope-from karenedwards@analyticsdba.com) Received: from vps.target-db.com (vps1.target-db.com [137.74.178.179]) (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 5983A16CB for ; Tue, 31 Jan 2017 23:22:55 +0000 (UTC) (envelope-from karenedwards@analyticsdba.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=analyticsdba.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=6m5uWNraZP+pC0S0TJcG4WlCbi6KD3WIS1ybR2474aI=; b=jX6sR1M+jiGlb/IePtd+NmeQmZ o53bgwYoJigLvxqT2WCehcLhm5C+7tatfL9sR7EmbILR0ms3OMLqy10KPV3PvReIxTifoHD1LhPzk GYq/xjNLgNwnZpHUeldHkJufa13lz0MRWpxp+TsNhMoaUGf4hKZKXQTxjIRirA6XhApSqMBRws6/z KoJEA41DmVrchl47iXf6DPPri7xp9ag5NU8cdyStASHK0EJnMftXym2hgYu3Qlq9s6cAYAbR3MocH 7aNLEiSf+s5n49Qeefe06lnlF1bBAUIGeZ/si1q8mGp45lK9xqE1wsFhIieahO4bmPSfQ8YpjXRLc pnOA6Ayw==; Received: from [103.5.134.74] (port=56529 helo=DESKTOPFD1OTRJ) by vps.target-db.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from ) id 1cYcBP-0006iu-3S for freebsd-stable@FreeBSD.ORG; Tue, 31 Jan 2017 22:55:31 +0530 From: "Karen Edwards" To: Subject: Follow-up Date: Tue, 31 Jan 2017 12:23:27 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdJ75qy7R2/fe6bKThyz3v4HpPMG2A== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.target-db.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - analyticsdba.com X-Get-Message-Sender-Via: vps.target-db.com: authenticated_id: karenedwards@analyticsdba.com X-Authenticated-Sender: vps.target-db.com: karenedwards@analyticsdba.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 23:22:56 -0000 Hello Hope all is well! I was trying to reach you today in regards to an email I sent you last quarter. Any chance you can review the below email and let me know if this information is still of interest to you. We are a database organization. We provide Business executives contact information. This information can be used for marketing initiatives like, Email marketing, Direct mail marketing and cold calling. With so many database offers these days- it's very difficult to know who has the right contact data. Get some samples before you decide on your database vendor. Please email me the following parameters to run counts and samples for your review: Industry: Geography: Titles: Keep me informed for any additional details. I look forward to hearing from you. Regards Karen Edward 505 20th St N, Birmingham, AL 35203, USA Enter your e-mail address in order to get unsubscribed click here From: Karen Edwards Sent: Wednesday, November 23, 2016 2:12 PM To: freebsd-stable@FreeBSD.ORG Subject: RE: Conference Call This is Karen from analyticsdb. We are a database organization. We provide Business executive contact information. Below are few examples: Industry Specific Lists: Agriculture, Business Services, Chambers of Commerce, Cities, Towns & Municipalities, Construction, Consumer Services, Cultural, Education, Energy, Utilities & Waste Treatment, Finance, Government, Healthcare, Hospitality, Insurance, Law Firms & Legal Services, Manufacturing, Media & Internet, Metals & Mining, Organizations, Real Estate, Retail, Software, Telecommunications, Transportation etc.. Technology specific Lists SAP users list, PeopleSoft Users list, SIEBEL customers List, Oracle Application Customers List, Microsoft Dynamic user List, Sales force User List, Microsoft Exchange user List, Quick Books List, Lawson Users List, Act Users List , JD Edward Users List, ASP Users List, Microsoft GP Applications Users List, Net Suite Users List, IBM DBMS Application Users List, McAfee Users List, MS Dynamics GP (Great Plains) and many more Title Specific Lists: C-level executives List - CEO, CFO, CIO, CTO, CMO, CISO, CSO, COO Key decision makers List - All C-level, VP level, Director level executives HR Executives List - VP of HR, HR Director & HR Manager etc., Marketing Executives List - CMO, VP of Marketing, Director of Marketing, Marketing Managers IT Executives List - CIO, CTO, CISO, IT-VP, IT-Director, IT Manager, MIS Manager etc., Thanks and let me know. Karen Edward 505 20th St N, Birmingham, AL 35203, USA Enter your e-mail address in order to get unsubscribed click here From owner-freebsd-stable@freebsd.org Wed Feb 1 01:32:54 2017 Return-Path: Delivered-To: freebsd-stable@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 BF642CCB6BD for ; Wed, 1 Feb 2017 01:32:54 +0000 (UTC) (envelope-from karenedwards@analyticsdba.com) Received: from vps.target-db.com (vps.target-db.com [137.74.178.178]) (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 6D9CFA5F for ; Wed, 1 Feb 2017 01:32:54 +0000 (UTC) (envelope-from karenedwards@analyticsdba.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=analyticsdba.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=9RQiEOQ1BbkqgPm2omUOwW77GnhWA0rrZiFIFp5F+KM=; b=odUkKrtcIwLS+yQE1dDA4bb8XA eU4Uc4c92+ZdWXjCWwYRaBqbEPNKGJXUk7ys/a32H81QySRLunvDzmwWNWhkKSgG2oIQvfX/w+q9t 9IiMNd7KS22TPDZdzwzo9YlP7hYvM40WCY4FB0j5F/VPy+VIFcLSZq4hi8GzeQAKrwYGCl1FYG4zX MkLUSs2ZTv0YedfsCkEs+XzhDYJAJox70/2v8qZWpIuleFda9Z6NspqjTyeuJETfna30nJfHp0cGy zNHBKjzufdPhKCaPOzuI4JaXcZjgZd4/h8/zKEw4qUnWAVaPEIAKCe2yYPubkTyEUHmOS1dPxB7Kz 0sH+Ej4A==; Received: from [103.5.134.74] (port=57080 helo=DESKTOPFD1OTRJ) by vps.target-db.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from ) id 1cYcbs-0000lm-0P for freebsd-stable@FreeBSD.ORG; Tue, 31 Jan 2017 23:22:52 +0530 From: "Karen Edwards" To: Subject: Follow-up Date: Tue, 31 Jan 2017 12:52:07 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdJ76rplOh19yAz9S42Id0bLe7Ce0w== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.target-db.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - analyticsdba.com X-Get-Message-Sender-Via: vps.target-db.com: authenticated_id: karenedwards@analyticsdba.com X-Authenticated-Sender: vps.target-db.com: karenedwards@analyticsdba.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 01:32:54 -0000 Hello Hope all is well! I was trying to reach you today in regards to an email I sent you last quarter. Any chance you can review the below email and let me know if this information is still of interest to you. We are a database organization. We provide Business executives contact information. This information can be used for marketing initiatives like, Email marketing, Direct mail marketing and cold calling. With so many database offers these days- it's very difficult to know who has the right contact data. Get some samples before you decide on your database vendor. Please email me the following parameters to run counts and samples for your review: Industry: Geography: Titles: Keep me informed for any additional details. I look forward to hearing from you. Regards Karen Edward 505 20th St N, Birmingham, AL 35203, USA Enter your e-mail address in order to get unsubscribed click here From: Karen Edwards Sent: Wednesday, November 23, 2016 2:12 PM To: freebsd-stable@FreeBSD.ORG Subject: RE: Conference Call This is Karen from analyticsdb. We are a database organization. We provide Business executive contact information. Below are few examples: Industry Specific Lists: Agriculture, Business Services, Chambers of Commerce, Cities, Towns & Municipalities, Construction, Consumer Services, Cultural, Education, Energy, Utilities & Waste Treatment, Finance, Government, Healthcare, Hospitality, Insurance, Law Firms & Legal Services, Manufacturing, Media & Internet, Metals & Mining, Organizations, Real Estate, Retail, Software, Telecommunications, Transportation etc.. Technology specific Lists SAP users list, PeopleSoft Users list, SIEBEL customers List, Oracle Application Customers List, Microsoft Dynamic user List, Sales force User List, Microsoft Exchange user List, Quick Books List, Lawson Users List, Act Users List , JD Edward Users List, ASP Users List, Microsoft GP Applications Users List, Net Suite Users List, IBM DBMS Application Users List, McAfee Users List, MS Dynamics GP (Great Plains) and many more Title Specific Lists: C-level executives List - CEO, CFO, CIO, CTO, CMO, CISO, CSO, COO Key decision makers List - All C-level, VP level, Director level executives HR Executives List - VP of HR, HR Director & HR Manager etc., Marketing Executives List - CMO, VP of Marketing, Director of Marketing, Marketing Managers IT Executives List - CIO, CTO, CISO, IT-VP, IT-Director, IT Manager, MIS Manager etc., Thanks and let me know. Karen Edward 505 20th St N, Birmingham, AL 35203, USA Enter your e-mail address in order to get unsubscribed click here From owner-freebsd-stable@freebsd.org Wed Feb 1 08:38:16 2017 Return-Path: Delivered-To: freebsd-stable@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 A935ACCBB01 for ; Wed, 1 Feb 2017 08:38:16 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 612BDB9E for ; Wed, 1 Feb 2017 08:38:16 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-qt0-x235.google.com with SMTP id k15so258352810qtg.3 for ; Wed, 01 Feb 2017 00:38:16 -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=Lms31UINfaC5vKwWfUYxu9EbvYJXEADgvV7hYJNJ+nY=; b=YHx7tEdA9AzVZK5yPj9Ciwg7K+pAwKfFGPQ9l1G3oh1zJ1QgR6dRYmH2ndexuidRoi oI+cYTbWGqTjHGl9b6qxPfUI6H8qfaG8hweFzhbv8WRSRchzm3UY4hLNs4DO2fnDztzQ +x7PFs77Hbkbhds1mM+uvrHcnCWzcZjBF9bLx7tikbtcBGTe2VALPd4jByX/kjf8NGhI xchvXvR0x9x8RDh1PmJpdQj7EJKilvMaEZXq62Kp+BjWQThzRzUBD8G+tgUit0ABz0P4 sywgdaU/8QWb1+N/PYBrJxmh3/0rh2YypmZlvg1p4CMHodLMnTrB0XlTjMMFb6mr9mjs v75g== 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=Lms31UINfaC5vKwWfUYxu9EbvYJXEADgvV7hYJNJ+nY=; b=MAo8vpF/o28BqHRC+cX5CJJQTjRBL9IVEDxYAkxHywE9bLt+6HopZcCn6zBsZyhNFR XGt/wwV5sjEgvg3SDA10/BUvjtyatENNdp5dJudI+DTlj6lhzmaf0L0ity65uCaMcJkR sfPgRMwkzzJFU3DDsrXZ6NLpik+iV650HEL6I+gQudzHqlQQ552FQjKf6DgFKHg2ReDd UeVP2EZ5r7FD9jDjezbgvG1iObIRt/KgRiqhYVwjVPvRrHt+G7/xzdq+IXEZu+0yYpwO UtX90Pp1s1mf8H0wt59H2/QESeEPqxK8N8474yKxeNfh2ZtGr55oyGtl1X+mxBuQfhil rgAg== X-Gm-Message-State: AIkVDXLBrPD9BynjpdHmEBhVivhSCoiffcYUVfE7pzEuzjz8IksC59/DV5d2Zu8uIzJkBw3YZBGMIrX2nCpiqA== X-Received: by 10.200.43.201 with SMTP id n9mr1603152qtn.243.1485938295382; Wed, 01 Feb 2017 00:38:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.173.40 with HTTP; Wed, 1 Feb 2017 00:38:15 -0800 (PST) In-Reply-To: References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> From: krad Date: Wed, 1 Feb 2017 08:38:15 +0000 Message-ID: Subject: Re: Boot partition size To: Warner Losh Cc: Andreas Nilsson , FreeBSD Stable , Aristedes Maniatis Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 08:38:16 -0000 Are we really that worried about 90-99 MB when we are talking about many TB drives? Even the entry-mid range SSD are in the region of 256-512 GB these days? On 31 January 2017 at 14:35, Warner Losh wrote: > The UEFI standard suggests something large like 100MB. There are a > number of firmware updating programs that run as .efi images. It > would be prudent to allow more than the bare minimum in case you wind > up needing them down the line. boot1.efi is likely to grow > significantly in the future. Maybe not 100x, a 1MB is likely once it > has all the features it needs. 10MB might be a safe upper bound. > > Warner > > On Tue, Jan 31, 2017 at 7:00 AM, Andreas Nilsson > wrote: > > Well, 100mb might be relevant if you ever want to dual-boot. The > relevant > > efi file seems to be < 100k > > > > It may go up in size, but I doubt we will see a 100x increase. > > > > /A > > > > On Tue, Jan 31, 2017 at 1:03 PM, krad wrote: > > > >> Its worth noting you should also go for GPT layout and have a 100meg or > so > >> partition provisioned as well so you can do a uefi boot. Even if you > arent > >> going to use it right now. > >> > >> > >> On 30 January 2017 at 03:41, Aristedes Maniatis wrote: > >> > >> > On 30/1/17 2:20pm, Freddie Cash wrote: > >> > > And, you may be able to do that on the existing disks, as ZFS now > >> leaves > >> > a MB or two of "slack space" at the end of the device used in the > vdev. > >> > This allows for using drives/partitions that are the same size in MB > but > >> > have different numbers of sectors. This was an issue on the early ZFS > >> days. > >> > > > >> > > So, you may be able to resize the freebsd-zfs partition by a > handful of > >> > KB without actually changing the size of the vdev. > >> > > >> > > >> > Brilliant, thank you. That worked a treat with a new boot size of > 256k. > >> > > >> > > >> > Note that this page: https://wiki.freebsd.org/ > >> RootOnZFS/GPTZFSBoot/Mirror > >> > needs to be adjusted. This line: > >> > > >> > gpart add -b 34 -s 128k -t freebsd-boot ad0 > >> > > >> > needs to instead be > >> > > >> > gpart add -a 4k -s 512k -t freebsd-boot ad0 > >> > > >> > > >> > I don't have edit rights. Probably someone needs to clean up and merge > >> > many of these pages: https://wiki.freebsd.org/RootOnZFS/ > >> > > >> > > >> > Ari > >> > > >> > > >> > > >> > -- > >> > --------------------------> > >> > Aristedes Maniatis > >> > CEO, ish > >> > https://www.ish.com.au > >> > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > >> > > >> > > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@ > freebsd.org" > >> > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > From owner-freebsd-stable@freebsd.org Wed Feb 1 09:57:04 2017 Return-Path: Delivered-To: freebsd-stable@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 43D9DCCBC09 for ; Wed, 1 Feb 2017 09:57:04 +0000 (UTC) (envelope-from eekee57@fastmail.fm) 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 17D4F1D87 for ; Wed, 1 Feb 2017 09:57:03 +0000 (UTC) (envelope-from eekee57@fastmail.fm) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6151D20C86 for ; Wed, 1 Feb 2017 04:57:02 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Wed, 01 Feb 2017 04:57:02 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; 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=mesmtp; bh=lO4qvNFEpvkxx8mszlg/SpFTOC s=; b=KwhvdK4Ws/EXZ1yqXEG+sm+1c2uuwu4Wf90gGMJBBRnYqsa9zkPMub9G30 INDoijwrWhVg1tiXrE9NJw4g4KRFbmz+BVkyRn5xZn9AR+ToAPYdbhuy16nafAkQ 0g39eUMT7A+S3aa/wETUXs4jR0wl+tRnVwlj5pDx369zc3jls= 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 4qvNFEpvkxx8mszlg/SpFTOCs=; b=EyzIFG5AiNtUTtQ2Tbtamc86IXvkgrmzJe tPGw+IXyDh6h4TAgijGVnbVy+fpWcCPiElSNXAqGAKfTQqLSPMfM3ZqZRRdL7EYq vV/xsXs7jKf6IDn0xwaYN5xeqFaVnnDHlTrPXP6mcB4PGAz+0jpHZUbvbL6POWOw NDExmYTWE= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 42FD762719; Wed, 1 Feb 2017 04:57:02 -0500 (EST) Message-Id: <1485943022.2832548.866509920.1E2FDFF5@webmail.messagingengine.com> From: Ethan Grammatikidis To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-e9b51b02 Date: Wed, 01 Feb 2017 09:57:02 +0000 In-Reply-To: References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> Subject: Re: Boot partition size X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 09:57:04 -0000 On Wed, Feb 1, 2017, at 08:38 AM, krad wrote: > Are we really that worried about 90-99 MB when we are talking about many TB > drives? Even the entry-mid range SSD are in the region of 256-512 GB these > days? Indeed. I've been using 100MB boot partitions for many years now, because I see no point in allocating anything less. I'm not even the type to always have the latest hardware, the last disks I bought were 720GB. 100MB is only 10% of 1GB. The first hard disk I ever bought for myself, in the 1990s, affordable when I had almost no spending money, was 4GB. -- I'm too old to use vi. From owner-freebsd-stable@freebsd.org Wed Feb 1 11:20:02 2017 Return-Path: Delivered-To: freebsd-stable@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 C418DCCA728 for ; Wed, 1 Feb 2017 11:20:02 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F000A08 for ; Wed, 1 Feb 2017 11:20:01 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cYsx7-0005sa-3S for freebsd-stable@freebsd.org; Wed, 01 Feb 2017 12:19:53 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Wed, 01 Feb 2017 12:19:52 +0100 Subject: update /usr/ports to same version as pkg upgrade? MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 7b320cd02cd98c580351ccd23ba1512a X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 11:20:02 -0000 Hi, Is it possible to update the /usr/ports tree to the same version as is used by the default pkg repositories? I use some ports which are not distributed as pkgs. When I 'portsnap auto' the ports tree gets new updates which are not in the pkgs yet and I don't want to rebuild those. I'm also able to fetch the ports tree by svn if that gives more possibilities than portsnap for this. So, is there a way to know from which svn revision the pkgs are build by the FreeBSD servers? Or something similar. Regards, Ronald. From owner-freebsd-stable@freebsd.org Wed Feb 1 11:53:16 2017 Return-Path: Delivered-To: freebsd-stable@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 6F06ECCB2D5 for ; Wed, 1 Feb 2017 11:53:16 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 020EF82 for ; Wed, 1 Feb 2017 11:53:16 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 640A2AB8B for ; Wed, 1 Feb 2017 11:53:11 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=infracaninophile.co.uk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201601-infracaninophile; t=1485949991; bh=tn4x3xKYvX1NMpq3r+eAGLle9vSJPgXJ2mpKzkEI8Wc=; h=Subject:To:References:From:Date:In-Reply-To; z=Subject:=20Re:=20update=20/usr/ports=20to=20same=20version=20as=2 0pkg=20upgrade?|To:=20freebsd-stable@freebsd.org|References:=20|From:=20Matthew =20Seaman=20|Date:=20Wed,=201=20F eb=202017=2011:53:01=20+0000|In-Reply-To:=20; b=YAdGcgMI189ljyUGb5BKI3brXzFL4RWJzuIt2/DCFmPtScuxnosQGwX+W+pjkKHGu Sa6krQiK2/OnNdrYOXgn/ufBN5LNwCLBSIsyqn8UbIjNxJmbW1rPePoMHHMbylmfEv 1nXK7z1JKvAG/d5REO+/0fotOK7jyxUqt9kYdV5A= Subject: Re: update /usr/ports to same version as pkg upgrade? To: freebsd-stable@freebsd.org References: From: Matthew Seaman Message-ID: Date: Wed, 1 Feb 2017 11:53:01 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="57vhQlmDTeRBbKGPG8HOQBfjjs3DAFVxH" X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_RP_RNBL,RDNS_NONE,SPF_FAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 11:53:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --57vhQlmDTeRBbKGPG8HOQBfjjs3DAFVxH Content-Type: multipart/mixed; boundary="sL63HN5w5hBF0Ujrorr3DjbsHiW51mFdv"; protected-headers="v1" From: Matthew Seaman To: freebsd-stable@freebsd.org Message-ID: Subject: Re: update /usr/ports to same version as pkg upgrade? References: In-Reply-To: --sL63HN5w5hBF0Ujrorr3DjbsHiW51mFdv Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/02/01 11:19, Ronald Klop wrote: > Is it possible to update the /usr/ports tree to the same version as is > used by the default pkg repositories? > I use some ports which are not distributed as pkgs. When I 'portsnap > auto' the ports tree gets new updates which are not in the pkgs yet and= > I don't want to rebuild those. > I'm also able to fetch the ports tree by svn if that gives more > possibilities than portsnap for this. >=20 > So, is there a way to know from which svn revision the pkgs are build b= y > the FreeBSD servers? Or something similar. The precise revision number used for pkg builds isn't published, so no it's not possible to synchronise exactly. However, what you can do is download the appropriate quarterly branch of the ports. At the moment that's something like: svn co https://svn.freebsd.org/ports/branches/2017Q1 /usr/ports This is the branch that the official packages are built from, and it changes a lot more slowly than HEAD, so your chances of running into version conflicts are much reduced. You will have to remember to 'svn switch' to each new quarterly branch, but that's only four times a year. Cheers, Matthew --sL63HN5w5hBF0Ujrorr3DjbsHiW51mFdv-- --57vhQlmDTeRBbKGPG8HOQBfjjs3DAFVxH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYkcwiXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn38YP/1xIgUG5m5ESyNnKi3+G2Bii xvtR2wxWTEyY5Nx8nkRfiGaOD6285cSj4hUzD6lK3vzJmJO+H8w8GgtggcNDViRz e+VkrE3bHoROlTITs6UuPgzzq5YWuWcjoJPJQLKQWK1iQJUzDHW+4ymsEtMT4nDM t90rgfV1cdSiTiYBs+CaachdgXJnsIp8Q+NyA31acQj8eRg3ZMNdUWoa2UgIVUjY 2PlR8G+xkDIWoqX/1/Qu5HOUDBR1ZjRkD1F3TJza8RuzLBp4/kCTDVmjrjbBqgvR JQXF8q2SNy5ns486CdiRhY9jw+9QlkXiTwsHwRkvgbHehoxU4jqSa6LHbNyFSE9E +OFnwCUf/ijufdhh7WJFbgT2qy/4KQuItdKgAZPqgGV+rYxyuuJTvRnO6RDHhnxH xlmKUixtuzc+YrJAhFNjKKSG4mwBItOxflbBNVcAKxByzrKNklNv3OJDgt6hyw81 BsCJsFJsvv8UxGy1IRMSnBZHigD9BlXMfLDqpnIMjp9hPeQ7w3fgwOtvpkRFLwLW RrP/84SWqJ3VQSvjDbL0pHSmUtgoRiiE3VwnmH6VQ7qdiTWGFjtpn0aFofciCpzd a7FtvrvgMrqJDz4aJtDrysWtmwGrw9A0T0TpRqQEHdAotZJjancyOgQ9nb2lM6pY iNZg3fad+h4eZnH8qGlz =chlY -----END PGP SIGNATURE----- --57vhQlmDTeRBbKGPG8HOQBfjjs3DAFVxH-- From owner-freebsd-stable@freebsd.org Wed Feb 1 12:02:31 2017 Return-Path: Delivered-To: freebsd-stable@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 7CF19CCBDD0 for ; Wed, 1 Feb 2017 12:02:31 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43633C4C for ; Wed, 1 Feb 2017 12:02:30 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cYtcJ-0007AP-AF; Wed, 01 Feb 2017 13:02:27 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org, "Jakub Lach" Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. References: <1483038391207-6154963.post@n6.nabble.com> Date: Wed, 01 Feb 2017 13:02:26 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <1483038391207-6154963.post@n6.nabble.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.9 X-Spam-Status: No, score=0.9 required=5.0 tests=ALL_TRUSTED, BAYES_50, URI_HEX autolearn=disabled version=3.4.0 X-Scan-Signature: 2c269fdec788119c0964d98755c55204 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 12:02:31 -0000 On Thu, 29 Dec 2016 20:06:31 +0100, Jakub Lach wrote: > Hello, > > I've recently tried to make a switch to a bigger memory card in some > device; what I've discovered, is that FreeBSD is cp-ing garbage to a > mounted FAT32 fs after first 10-20 GB (depending on luck). > > What I mean by garbage are non removable 'files' with random names > which cannot be escaped. The fastest way to get rid of them is newfs. > > I've initially thought the problem were faulty memory card(s) but > I was able to test them (mounted as FAT32 still) with sysutils/f3. > They are fine, the utility writes(!) and reads them correctly. > > However, as soon as cp (-a) gets involved, the garbage appears, > sometimes with CAM errors and reboots. > > Additionally, I saw exactly the same errors with FAT32 on HDD > mounted via USB, so the cards are not a problem. > > What I can do? > > 1. Reading is not at all affected, I can backup (cp -a) mounted FAT32 > cards to UFS2 (local disk) without problems. > 2. I can mount FAT32 and test the cards with sysutils/f3. The medium > (card) is tested via the same USB dual card reader as below. > > What I can't do reliably, as garbage appears after first 10-20 GB? > > 1. I can't cp (-a) from UFS2 to mounted FAT32 partition. Smaller writes > are a matter of luck. > 2. I can't cp (-a) from FAT32 (mounted fs on memory card A in dual card > reader) > to another FAT32 (mounted fs on memory card B in a dual card reader). > Same > problem as above. > > Any ideas? I see nobody replied. I don't have an answer, but this might help. You can try the freebsd-fs mailinglist. It is about filesystems. You can also provide more information about your system. What version of FreeBSD are you running? 'uname -a' and the content of /var/run/dmesg.boot as a starter. You can file a problem report (PR) at https://bugs.freebsd.org/ with a reproducable test case. Does the problem also occur if you use rsync to copy the files? Regards, Ronald. > > > > -- > View this message in context: > http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963.html > Sent from the freebsd-stable mailing list archive at Nabble.com. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Wed Feb 1 12:38:08 2017 Return-Path: Delivered-To: freebsd-stable@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 75E11CCB268 for ; Wed, 1 Feb 2017 12:38:08 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5D515F57 for ; Wed, 1 Feb 2017 12:38:08 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id EE4343BBA79B for ; Wed, 1 Feb 2017 04:19:00 -0800 (PST) Date: Wed, 1 Feb 2017 05:38:07 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485952687570-6164655.post@n6.nabble.com> In-Reply-To: References: <1483038391207-6154963.post@n6.nabble.com> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 12:38:08 -0000 As it shows your interest, I appreciate your answer very much. I was a bit let down then, I had to (using the same card reader), cp -r using borrowed Apple iMac. It worked as it should. It was FreeBSD 11.0-STABLE #0 r310265 amd64 as in subject, I will reconsider retesting now and filling a PR, with a different data set and medium though. Thanks. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164655.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 12:51:05 2017 Return-Path: Delivered-To: freebsd-stable@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 E4CADCCB63E for ; Wed, 1 Feb 2017 12:51:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C231160C for ; Wed, 1 Feb 2017 12:51:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v11CoxAO049165 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Feb 2017 14:50:59 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v11CoxAO049165 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v11Coxrn049164; Wed, 1 Feb 2017 14:50:59 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Feb 2017 14:50:59 +0200 From: Konstantin Belousov To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. Message-ID: <20170201125059.GB3018@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485952687570-6164655.post@n6.nabble.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 12:51:06 -0000 On Wed, Feb 01, 2017 at 05:38:07AM -0700, Jakub Lach wrote: > As it shows your interest, I appreciate your answer very much. > > I was a bit let down then, I had to (using the same card reader), > cp -r using borrowed Apple iMac. It worked as it should. > > It was FreeBSD 11.0-STABLE #0 r310265 amd64 as in subject, > I will reconsider retesting now and filling a PR, with a different > data set and medium though. Thanks. Does that happen on any device which carries FAT fs, or since you mentioned a card reader, does it happen with any other filesystem carried by a volume on the card ? In other words, why do you blame FAT and not the card reader ? From owner-freebsd-stable@freebsd.org Wed Feb 1 13:02:46 2017 Return-Path: Delivered-To: freebsd-stable@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 CBE26CCBC85 for ; Wed, 1 Feb 2017 13:02:46 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id BAB3B3E1 for ; Wed, 1 Feb 2017 13:02:45 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 9B79E3BBAD22 for ; Wed, 1 Feb 2017 04:43:38 -0800 (PST) Date: Wed, 1 Feb 2017 06:02:45 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485954165392-6164661.post@n6.nabble.com> In-Reply-To: <20170201125059.GB3018@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:02:46 -0000 Yes, it has happened also with another device. Which was not a card reader (HDD mounted by USB), and I have used the same card reader configuration to copy the memory card content with iMac. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164661.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 13:05:24 2017 Return-Path: Delivered-To: freebsd-stable@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 16D47CCBDC5 for ; Wed, 1 Feb 2017 13:05:24 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 055C9936 for ; Wed, 1 Feb 2017 13:05:23 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 2EA0F3BBADCC for ; Wed, 1 Feb 2017 04:46:16 -0800 (PST) Date: Wed, 1 Feb 2017 06:05:23 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485954322961-6164662.post@n6.nabble.com> In-Reply-To: <1485954165392-6164661.post@n6.nabble.com> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:05:24 -0000 Moreover, sysutils/f3 was reading and writing with this memory card configuration fine. Which is why I don't _blame_ fs, I only know that FAT + cp -r consistently gave me problems, for one reason or another. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164662.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 13:18:32 2017 Return-Path: Delivered-To: freebsd-stable@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 34828CC2338 for ; Wed, 1 Feb 2017 13:18:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B626711C9 for ; Wed, 1 Feb 2017 13:18:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v11DIRm4055511 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Feb 2017 15:18:27 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v11DIRm4055511 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v11DIQvL055510; Wed, 1 Feb 2017 15:18:26 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Feb 2017 15:18:26 +0200 From: Konstantin Belousov To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. Message-ID: <20170201131826.GD3018@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485954165392-6164661.post@n6.nabble.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:18:32 -0000 On Wed, Feb 01, 2017 at 06:02:45AM -0700, Jakub Lach wrote: > Yes, it has happened also with another device. Which was not a card reader > (HDD > mounted by USB), and I have used the same card reader configuration to copy > the memory card content with iMac. Is your card reader USB-attached, same as the HDD you mentioned ? Test with UFS filesystem put onto a card or HDD, does system read garbage or panics due to metadata inconsistency, under the load ? From owner-freebsd-stable@freebsd.org Wed Feb 1 13:27:39 2017 Return-Path: Delivered-To: freebsd-stable@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 4CE30CC26F3 for ; Wed, 1 Feb 2017 13:27:39 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 375A01958 for ; Wed, 1 Feb 2017 13:27:39 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: by mailman.ysv.freebsd.org (Postfix) id 33B83CC26F1; Wed, 1 Feb 2017 13:27:39 +0000 (UTC) Delivered-To: stable@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 31B39CC26F0 for ; Wed, 1 Feb 2017 13:27:39 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailhost.dlr.de", Issuer "DLR CA - G02" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FCFB1957 for ; Wed, 1 Feb 2017 13:27:38 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by mailhost.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 1 Feb 2017 14:27:24 +0100 Received: from DLREXMBX01.intra.dlr.de ([fe80::d198:77e5:d411:fccd]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 14:27:28 +0100 From: To: Subject: Building i386 on i386 Thread-Topic: Building i386 on i386 Thread-Index: AdJ8jsIk+oZJEO2+SxixgpsGKSw/wQ== Date: Wed, 1 Feb 2017 13:27:28 +0000 Message-ID: <611243783F62AF48AFB07BC25FA4B1061CED9AB0@DLREXMBX01.intra.dlr.de> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-TM-AS-Product-Ver: SMEX-11.0.0.4255-8.100.1062-22858.006 X-TM-AS-Result: No--12.807600-5.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:27:39 -0000 Hi, is $subj still supposed to work on 11.0? I get a 'virtual memory exhausted'= during linking of clang. harti From owner-freebsd-stable@freebsd.org Wed Feb 1 13:52:02 2017 Return-Path: Delivered-To: freebsd-stable@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 BD6EBCCB189 for ; Wed, 1 Feb 2017 13:52:02 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id ABC8BCB6 for ; Wed, 1 Feb 2017 13:52:02 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id BB8653BBB5F9 for ; Wed, 1 Feb 2017 05:32:54 -0800 (PST) Date: Wed, 1 Feb 2017 06:52:01 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485957121778-6164672.post@n6.nabble.com> In-Reply-To: <20170201131826.GD3018@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:52:02 -0000 Yes, HDD and card reader was USB mounted. This time, I've copied about 12G from 38G from internal SSD (UFS2) to HDD via USB (FAT32), then system panicked with CAM errors. http://pastebin.ca/3762654 Apart from that, there are no corrupted files in the way there were with card reader. I will newfs now this HDD and try again. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164672.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 14:03:00 2017 Return-Path: Delivered-To: freebsd-stable@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 5CB2CCCB435 for ; Wed, 1 Feb 2017 14:03:00 +0000 (UTC) (envelope-from s-tlk@s-tlk.org) Received: from mail.s-tlk.org (s-tlk.org [84.201.39.20]) by mx1.freebsd.org (Postfix) with ESMTP id 1E19B12F4 for ; Wed, 1 Feb 2017 14:02:59 +0000 (UTC) (envelope-from s-tlk@s-tlk.org) Received: from priv (priv [10.1.0.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.s-tlk.org (Postfix) with ESMTPSA id 9BFAE53D1F4; Wed, 1 Feb 2017 14:53:59 +0100 (CET) Date: Wed, 1 Feb 2017 14:53:59 +0100 (CET) From: Michael Schnell X-X-Sender: michi@priv.s-tlk.org To: Ronald Klop cc: freebsd-stable@freebsd.org Subject: Re: update /usr/ports to same version as pkg upgrade? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:03:00 -0000 Hello, On Wed, 1 Feb 2017, Ronald Klop wrote: > Hi, > > Is it possible to update the /usr/ports tree to the same version as is used > by the default pkg repositories? > I use some ports which are not distributed as pkgs. When I 'portsnap auto' > the ports tree gets new updates which are not in the pkgs yet and I don't > want to rebuild those. > I'm also able to fetch the ports tree by svn if that gives more possibilities > than portsnap for this. > > So, is there a way to know from which svn revision the pkgs are build by the > FreeBSD servers? Or something similar. I once raised a request for this on github and it was "mostly" implemented, but I never found how it works: https://github.com/freebsd/pkg/issues/328 Greetings Michael From owner-freebsd-stable@freebsd.org Wed Feb 1 14:16:31 2017 Return-Path: Delivered-To: freebsd-stable@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 00849CCB7EA for ; Wed, 1 Feb 2017 14:16:31 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id E282F186F for ; Wed, 1 Feb 2017 14:16:29 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 869AE3BBBB90 for ; Wed, 1 Feb 2017 05:57:21 -0800 (PST) Date: Wed, 1 Feb 2017 07:16:28 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485958588529-6164674.post@n6.nabble.com> In-Reply-To: <1485957121778-6164672.post@n6.nabble.com> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:16:31 -0000 I'm not sure if it's the same thing. Most of the times the corruption was silent then. Nonetheless, the outcome was the same after newfs HDD with UFS2- http://www.pastebin.ca/3762661 I would 'blame' USB now, if only I did not migrate/clone the whole system to SSD via dump/the same USB not very long ago?? -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164674.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 14:18:44 2017 Return-Path: Delivered-To: freebsd-stable@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 2477DCCB93C for ; Wed, 1 Feb 2017 14:18:44 +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 D946A1B4D for ; Wed, 1 Feb 2017 14:18:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cYvk9-0006VQ-01; Wed, 01 Feb 2017 17:18:41 +0300 Date: Wed, 1 Feb 2017 17:18:40 +0300 From: Slawa Olhovchenkov To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. Message-ID: <20170201141840.GD79121@zxy.spb.ru> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485957121778-6164672.post@n6.nabble.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-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:18:44 -0000 On Wed, Feb 01, 2017 at 06:52:01AM -0700, Jakub Lach wrote: > Yes, HDD and card reader was USB mounted. > > This time, I've copied about 12G from 38G from internal SSD (UFS2) to > HDD via USB (FAT32), then system panicked with CAM errors. I am have like issuse on laptop w/ broken USB controller. From owner-freebsd-stable@freebsd.org Wed Feb 1 14:25:19 2017 Return-Path: Delivered-To: freebsd-stable@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 B5A26CCBC15 for ; Wed, 1 Feb 2017 14:25:19 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id A30E812F for ; Wed, 1 Feb 2017 14:25:19 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 60F1C3BBBF55 for ; Wed, 1 Feb 2017 06:06:11 -0800 (PST) Date: Wed, 1 Feb 2017 07:25:18 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485959118559-6164677.post@n6.nabble.com> In-Reply-To: <20170201141840.GD79121@zxy.spb.ru> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <20170201141840.GD79121@zxy.spb.ru> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:25:19 -0000 I would think so, if only I would not clone the disk/system via the same USB port mere weeks ago. Moreover, sysutils/f3 fully writes and validates (checksums) 30G+ memory cards via the same port without problems. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164677.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 14:31:30 2017 Return-Path: Delivered-To: freebsd-stable@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 6F5CCCCBD42 for ; Wed, 1 Feb 2017 14:31:30 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6053D3 for ; Wed, 1 Feb 2017 14:31:29 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([83.193.128.235]) by mwinf5d42 with ME id fSPq1u00A54s3Hf03SPqKe; Wed, 01 Feb 2017 15:23:51 +0100 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Wed, 01 Feb 2017 15:23:51 +0100 X-ME-IP: 83.193.128.235 To: FreeBSD Current Cc: FreeBSD-STABLE Mailing List From: Claude Buisson Subject: Recent FreeBSD, NFSv4 and /var/db/mounttab Message-ID: <20c2baca-ba91-19b4-db95-5352b56019c1@orange.fr> Date: Wed, 1 Feb 2017 15:23:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:31:30 -0000 Hi, Last month, I started switching all my systems (stable/9, stable/10, stable/11 and current) to NFSv4, and I found that: on current (svn 312652) an entry is added to /var/db/mounttab by mount_nfs(8), but not suppressed by umount(8). It can be suppressed by rpc.umntall(8). The same anomaly appears on stable/11 after upgrading to svn 312950. It is relatively easy to trace this anomaly to r308871 on current and its MFHs (r309517 for stable/11). Patching sbin/umount/umount.c to restore the RPC call for NFSv4 makes umount(8) suppress the mounttab entry as before. I do not know what is the proper solution, as suppressing the modification of mounttab by mount_nfs(8) for NFSv4 could be an (more complicated) alternative ! Thanks for your attention, Claude Buisson From owner-freebsd-stable@freebsd.org Wed Feb 1 14:31:58 2017 Return-Path: Delivered-To: freebsd-stable@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 57040CCBE69 for ; Wed, 1 Feb 2017 14:31:58 +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 161EA8BE for ; Wed, 1 Feb 2017 14:31:58 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cYvwy-0006pL-2k; Wed, 01 Feb 2017 17:31:56 +0300 Date: Wed, 1 Feb 2017 17:31:56 +0300 From: Slawa Olhovchenkov To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. Message-ID: <20170201143156.GE79121@zxy.spb.ru> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <20170201141840.GD79121@zxy.spb.ru> <1485959118559-6164677.post@n6.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485959118559-6164677.post@n6.nabble.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-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:31:58 -0000 On Wed, Feb 01, 2017 at 07:25:18AM -0700, Jakub Lach wrote: > I would think so, if only I would not clone the disk/system via the same USB > port mere weeks ago. > Moreover, sysutils/f3 fully writes and validates (checksums) 30G+ memory > cards via the same port without problems. In my case controller don't always be broken, only from some time. Data corruption over my USB depends on data access pattern. From owner-freebsd-stable@freebsd.org Wed Feb 1 14:48:41 2017 Return-Path: Delivered-To: freebsd-stable@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 722BFCCB7E8 for ; Wed, 1 Feb 2017 14:48:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08A6316A8 for ; Wed, 1 Feb 2017 14:48:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v11EmZmG023631 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Feb 2017 16:48:35 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v11EmZmG023631 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v11EmZV2023630; Wed, 1 Feb 2017 16:48:35 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Feb 2017 16:48:35 +0200 From: Konstantin Belousov To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. Message-ID: <20170201144835.GE2092@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <1485958588529-6164674.post@n6.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485958588529-6164674.post@n6.nabble.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 14:48:41 -0000 On Wed, Feb 01, 2017 at 07:16:28AM -0700, Jakub Lach wrote: > I'm not sure if it's the same thing. Most of the times the corruption was > silent > then. > > Nonetheless, the outcome was the same after newfs HDD with UFS2- > > http://www.pastebin.ca/3762661 > > I would 'blame' USB now, if only I did not migrate/clone the whole system to > SSD > via dump/the same USB not very long ago?? Note that in the paste above you get write errors reported, while the corruption happens while you read from the volume. From owner-freebsd-stable@freebsd.org Wed Feb 1 15:56:27 2017 Return-Path: Delivered-To: freebsd-stable@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 7DC34CCBF6C for ; Wed, 1 Feb 2017 15:56:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 67BCE1EE3 for ; Wed, 1 Feb 2017 15:56:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6418FCCBF6B; Wed, 1 Feb 2017 15:56:27 +0000 (UTC) Delivered-To: stable@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 63B8FCCBF6A for ; Wed, 1 Feb 2017 15:56:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA6E1EE2 for ; Wed, 1 Feb 2017 15:56:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.avinity.tv (unknown [77.95.97.98]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 21E1EADE9; Wed, 1 Feb 2017 16:56:23 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_8C7BF409-E015-44CB-9002-4CEC4234173F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Building i386 on i386 From: Dimitry Andric In-Reply-To: <611243783F62AF48AFB07BC25FA4B1061CED9AB0@DLREXMBX01.intra.dlr.de> Date: Wed, 1 Feb 2017 16:56:16 +0100 Cc: stable@freebsd.org Message-Id: References: <611243783F62AF48AFB07BC25FA4B1061CED9AB0@DLREXMBX01.intra.dlr.de> To: Hartmut.Brandt@dlr.de X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 15:56:27 -0000 --Apple-Mail=_8C7BF409-E015-44CB-9002-4CEC4234173F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 01 Feb 2017, at 14:27, Hartmut.Brandt@dlr.de wrote: >=20 > is $subj still supposed to work on 11.0? I get a 'virtual memory = exhausted' during linking of clang. How much memory does your machine have? I build this regularly, on a VM = with 2G RAM (and 4G swap). -Dimitry --Apple-Mail=_8C7BF409-E015-44CB-9002-4CEC4234173F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAliSBSQACgkQsF6jCi4glqNwdQCgxgNFjHvbRreC1Oz/DWnb8UWD d1oAoJviiqzflOdLepCZpsJxhrjCIdmn =Jh2g -----END PGP SIGNATURE----- --Apple-Mail=_8C7BF409-E015-44CB-9002-4CEC4234173F-- From owner-freebsd-stable@freebsd.org Wed Feb 1 16:06:58 2017 Return-Path: Delivered-To: freebsd-stable@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 EF595CCB2FF for ; Wed, 1 Feb 2017 16:06:58 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D9767849 for ; Wed, 1 Feb 2017 16:06:58 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: by mailman.ysv.freebsd.org (Postfix) id D5E4ACCB2FE; Wed, 1 Feb 2017 16:06:58 +0000 (UTC) Delivered-To: stable@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 D3E15CCB2FD for ; Wed, 1 Feb 2017 16:06:58 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailhost.dlr.de", Issuer "DLR CA - G02" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 203C4847; Wed, 1 Feb 2017 16:06:57 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by mailhost.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 1 Feb 2017 17:05:38 +0100 Received: from DLREXMBX01.intra.dlr.de ([fe80::d198:77e5:d411:fccd]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 17:05:42 +0100 From: To: CC: Subject: RE: Building i386 on i386 Thread-Topic: Building i386 on i386 Thread-Index: AdJ8jsIk+oZJEO2+SxixgpsGKSw/wQADJRYAAAJkX3A= Date: Wed, 1 Feb 2017 16:05:41 +0000 Message-ID: <611243783F62AF48AFB07BC25FA4B1061CED9BCE@DLREXMBX01.intra.dlr.de> References: <611243783F62AF48AFB07BC25FA4B1061CED9AB0@DLREXMBX01.intra.dlr.de> In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-Product-Ver: SMEX-11.0.0.4255-8.100.1062-22860.000 X-TM-AS-Result: No--2.587500-5.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 16:06:59 -0000 The problem is not the memory but the 2GB process limit. harti -----Original Message----- From: Dimitry Andric [mailto:dim@FreeBSD.org]=20 Sent: Wednesday, February 01, 2017 4:56 PM To: Brandt, Hartmut Cc: stable@freebsd.org Subject: Re: Building i386 on i386 On 01 Feb 2017, at 14:27, Hartmut.Brandt@dlr.de wrote: >=20 > is $subj still supposed to work on 11.0? I get a 'virtual memory exhauste= d' during linking of clang. How much memory does your machine have? I build this regularly, on a VM wi= th 2G RAM (and 4G swap). -Dimitry From owner-freebsd-stable@freebsd.org Wed Feb 1 16:22:21 2017 Return-Path: Delivered-To: freebsd-stable@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 43354CCBB17 for ; Wed, 1 Feb 2017 16:22:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2B70A1593 for ; Wed, 1 Feb 2017 16:22:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2AC66CCBB15; Wed, 1 Feb 2017 16:22:21 +0000 (UTC) Delivered-To: stable@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 2A748CCBB13 for ; Wed, 1 Feb 2017 16:22:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F2F7158C; Wed, 1 Feb 2017 16:22:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v11GLxmI039054 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Feb 2017 18:22:00 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v11GLxmI039054 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v11GLxA8039053; Wed, 1 Feb 2017 18:21:59 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Feb 2017 18:21:59 +0200 From: Konstantin Belousov To: Hartmut.Brandt@dlr.de Cc: dim@FreeBSD.org, stable@freebsd.org Subject: Re: Building i386 on i386 Message-ID: <20170201162159.GH2092@kib.kiev.ua> References: <611243783F62AF48AFB07BC25FA4B1061CED9AB0@DLREXMBX01.intra.dlr.de> <611243783F62AF48AFB07BC25FA4B1061CED9BCE@DLREXMBX01.intra.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <611243783F62AF48AFB07BC25FA4B1061CED9BCE@DLREXMBX01.intra.dlr.de> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 16:22:21 -0000 On Wed, Feb 01, 2017 at 04:05:41PM +0000, Hartmut.Brandt@dlr.de wrote: > The problem is not the memory but the 2GB process limit. Did you configured PAE ? Normal (non-PAE) kernels with default configuration of U/K split provide 3G to userspace. On amd64 kernel running 32bit processes, you get 4G for userspace. > > harti > > -----Original Message----- > From: Dimitry Andric [mailto:dim@FreeBSD.org] > Sent: Wednesday, February 01, 2017 4:56 PM > To: Brandt, Hartmut > Cc: stable@freebsd.org > Subject: Re: Building i386 on i386 > > On 01 Feb 2017, at 14:27, Hartmut.Brandt@dlr.de wrote: > > > > is $subj still supposed to work on 11.0? I get a 'virtual memory exhausted' during linking of clang. > > How much memory does your machine have? I build this regularly, on a VM with 2G RAM (and 4G swap). > > -Dimitry > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Wed Feb 1 19:54:41 2017 Return-Path: Delivered-To: freebsd-stable@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 C5DC2CCCD7E for ; Wed, 1 Feb 2017 19:54:41 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id B323A11CF for ; Wed, 1 Feb 2017 19:54:40 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 660233BC45BB for ; Wed, 1 Feb 2017 11:35:31 -0800 (PST) Date: Wed, 1 Feb 2017 12:54:40 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1485978880230-6164736.post@n6.nabble.com> In-Reply-To: <20170201144835.GE2092@kib.kiev.ua> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <1485958588529-6164674.post@n6.nabble.com> <20170201144835.GE2092@kib.kiev.ua> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 19:54:41 -0000 OK, I just have successfully wrote both problematic cards in the same USB card reader/port as the USB HDD above, using the same data set. The only CAM errors were at the same time as cards have run out of space. Now testing cping between them, but as they are on the same dual card reader/USB port it's unbearably slow. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164736.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Wed Feb 1 21:49:15 2017 Return-Path: Delivered-To: freebsd-stable@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 40815CCB92E; Wed, 1 Feb 2017 21:49:15 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670082.outbound.protection.outlook.com [40.107.67.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC73EDAA; Wed, 1 Feb 2017 21:49:14 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Wed, 1 Feb 2017 21:49:12 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0874.021; Wed, 1 Feb 2017 21:49:12 +0000 From: Rick Macklem To: Claude Buisson , FreeBSD Current CC: FreeBSD-STABLE Mailing List Subject: Re: Recent FreeBSD, NFSv4 and /var/db/mounttab Thread-Topic: Recent FreeBSD, NFSv4 and /var/db/mounttab Thread-Index: AQHSfJfpteLPu545NESwV/c/JyXxzaFUr0tB Date: Wed, 1 Feb 2017 21:49:12 +0000 Message-ID: References: <20c2baca-ba91-19b4-db95-5352b56019c1@orange.fr> In-Reply-To: <20c2baca-ba91-19b4-db95-5352b56019c1@orange.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: f1dafccb-6ce1-4b13-4fa7-08d44aec28ca x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0189; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0189; 7:G/FvNf6N6gdavP23DJnat0zCSG2ionBfpWS8ahuA2kxPxrMTankMWpP4gVDojZkza1UlyDbxuXsBHCCyiBI7NrrBkPHMarOIaO7joWG/9TgfDx+nAv+x5fpsjwxQfqeBXgEQtnOayGzPX9hrg4HYIolblNS5aeOu9MqwmyZrDe1CtVG8/xxXJtSXXkpFuDhg5WI+PJSXD29DSUzvaRjSIJx+g4CPHwNPiwUKyM2MoR8ZrjfYWVSE+RK2vSqWBMQpJs+dwXAwnpOzXaaeEsqqvyZotI8uK3jjuk78vN2JwLRZL86Jo1Sxcdxdwb5Arf+3R3aX62wHxB2KxKEMb+zIFRDLw1bsTxtNRjlPDZl1mDnYLm2cg76eSRv8kvbYhHSSmqF486+4vT9eagcCFeBpMgmBCLOwXLglAh44SlV6qlOJ2PNw/tsOK53ALIhwjOICFP5+AknI6NLGCOo52d/7LV/duxxnFEah+rfwnvBEj1e2FJUUq7PFrCOB5zn77xDy9okX28GcgIJncROaB7P5IjeQLqptCK4OJ8O9LDvMZwRomIsGw/G6rUSa7Kfq5lbp x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123560025)(20161123564025)(20161123562025)(20161123558025)(20161123555025)(6042181)(6072148); SRVR:YTXPR01MB0189; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0189; x-forefront-prvs: 0205EDCD76 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(189002)(24454002)(199003)(2906002)(305945005)(53936002)(3280700002)(81156014)(50986999)(106116001)(101416001)(8936002)(74316002)(9686003)(105586002)(229853002)(76176999)(54356999)(6436002)(38730400001)(77096006)(6506006)(33656002)(55016002)(81166006)(4326007)(74482002)(106356001)(92566002)(68736007)(102836003)(2900100001)(3660700001)(97736004)(2950100002)(122556002)(7696004)(5660300001)(86362001)(8676002)(5001770100001)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0189; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2017 21:49:12.1695 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0189 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 21:49:15 -0000 Claude Buisson wrote: >Hi, > >Last month, I started switching all my systems (stable/9, stable/10, >stable/11 and current) to NFSv4, and I found that: > > on current (svn 312652) an entry is added to /var/db/mounttab by >mount_nfs(8), but not suppressed by umount(8). It can be suppressed by >rpc.umntall(8). > >The same anomaly appears on stable/11 after upgrading to svn 312950. > >It is relatively easy to trace this anomaly to r308871 on current and >its MFHs (r309517 for stable/11). > >Patching sbin/umount/umount.c to restore the RPC call for NFSv4 makes >umount(8) suppress the mounttab entry as before. > >I do not know what is the proper solution, as suppressing the >modification of mounttab by mount_nfs(8) for NFSv4 could be an (more >complicated) alternative ! This would be the correct fix. The entries in mounttab are meaningless. Even for NFSv3, all they do is provide a "best guess" answer for "showmount". - The Mount protocol is not part of NFSv4. I had a patch which disabled it for NFSv4 servers, but some folk liked the idea of having "showmount -= e" to work, so I didn't commit it. rick ps: I had actually thought mount_nfs(8) didn't do a Mount protocol RPC for NFSv4, but I guess it is. That needs to be fixed, since NFSv4 ser= vers don't need to support Mount at all. From owner-freebsd-stable@freebsd.org Thu Feb 2 08:27:29 2017 Return-Path: Delivered-To: freebsd-stable@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 8D720CCCA5C for ; Thu, 2 Feb 2017 08:27:29 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 7A2E615DC for ; Thu, 2 Feb 2017 08:27:28 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 0A1703BCE868 for ; Thu, 2 Feb 2017 00:08:15 -0800 (PST) Date: Thu, 2 Feb 2017 01:27:27 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1486024047585-6164851.post@n6.nabble.com> In-Reply-To: <1485978880230-6164736.post@n6.nabble.com> References: <1483038391207-6154963.post@n6.nabble.com> <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <1485958588529-6164674.post@n6.nabble.com> <20170201144835.GE2092@kib.kiev.ua> <1485978880230-6164736.post@n6.nabble.com> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 08:27:29 -0000 To sum up, looks like I cannot replicate original problem (corruption) with the USB dual card reader any more, and the HDD via USB thing is something different (maybe hardware related as it's exactly the same with UFS/FAT). -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164851.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Thu Feb 2 15:46:57 2017 Return-Path: Delivered-To: freebsd-stable@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 8BB8ACCD703 for ; Thu, 2 Feb 2017 15:46:57 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 785EE908 for ; Thu, 2 Feb 2017 15:46:56 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 6EAAB3BD5DE8 for ; Thu, 2 Feb 2017 07:27:41 -0800 (PST) Date: Thu, 2 Feb 2017 08:46:56 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1486050416215-6164918.post@n6.nabble.com> In-Reply-To: <1486024047585-6164851.post@n6.nabble.com> References: <1485952687570-6164655.post@n6.nabble.com> <20170201125059.GB3018@kib.kiev.ua> <1485954165392-6164661.post@n6.nabble.com> <20170201131826.GD3018@kib.kiev.ua> <1485957121778-6164672.post@n6.nabble.com> <1485958588529-6164674.post@n6.nabble.com> <20170201144835.GE2092@kib.kiev.ua> <1485978880230-6164736.post@n6.nabble.com> <1486024047585-6164851.post@n6.nabble.com> Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 15:46:57 -0000 I just now successfully copied 38G (second data set) to the same HDD via USB (after it has passed extended SMART), both with UFS2 and FAT32 fs (6 CAM write errors in the second case, but as far as I can see, data is ok). I think I hit something unrelated above, and as I've said, cannot replicate first issue I had. -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164918.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Thu Feb 2 17:21:43 2017 Return-Path: Delivered-To: freebsd-stable@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 917D2CCD103 for ; Thu, 2 Feb 2017 17:21:43 +0000 (UTC) (envelope-from sem33@yandex-team.ru) Received: from forwardcorp1h.cmail.yandex.net (forwardcorp1h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::e5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BC8475 for ; Thu, 2 Feb 2017 17:21:42 +0000 (UTC) (envelope-from sem33@yandex-team.ru) Received: from smtpcorp1p.mail.yandex.net (smtpcorp1p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:10]) by forwardcorp1h.cmail.yandex.net (Yandex) with ESMTP id 771A720C25 for ; Thu, 2 Feb 2017 20:21:29 +0300 (MSK) Received: from smtpcorp1p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtpcorp1p.mail.yandex.net (Yandex) with ESMTP id 751BF6E40BB9 for ; Thu, 2 Feb 2017 20:21:29 +0300 (MSK) Received: from unknown (unknown [2a02:6b8:0:401:9180:9848:ad4f:fc50]) by smtpcorp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id MIaPluN11t-LTkmCDux; Thu, 02 Feb 2017 20:21:29 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1486056089; bh=CuUb3dYhUWiyC3QL8lg7pD5ga1k7uXiyJl2pB8xnenU=; h=To:From:Subject:Message-ID:Date; b=Y7gNqOD9xMdqH084EeJamNt09LWtbcysp7t1aG3QZsJ5/eZmwZ2Y/jls7zF2A3J41 e0jlul/opSSvPkFFsKJ9YWrVR3OvsAm6ar1Jvdw0nVLP31fihCeKYC/jS+4KBp8xPC IGagxiV+HeZKqBVuegGUQvYVa+30xptZD3zijSxM= Authentication-Results: smtpcorp1p.mail.yandex.net; dkim=pass header.i=@yandex-team.ru To: freebsd-stable@freebsd.org From: Sergey Matveychuk Subject: kernel installation problem on STABLE-11 Message-ID: Date: Thu, 2 Feb 2017 20:21:29 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 17:21:43 -0000 Hi. On FreeBSD 11.0 kernel installation procedure is broken. It does not work without COMPILER_TYPE=clang: make[2]: "/usr/src/share/mk/bsd.compiler.mk" line 145: Unable to determine compiler type for CC=cc . Consider setting COMPILER_TYPE. Command 'make installworld COMPILER_TYPE=clang KERNCONF=MYKERNERL' works fine. And it looks like it works without COMPILER_TYPE=clang if you buildworld before. But I'm not sure. From owner-freebsd-stable@freebsd.org Thu Feb 2 17:27:46 2017 Return-Path: Delivered-To: freebsd-stable@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 4EF35CCD2F4 for ; Thu, 2 Feb 2017 17:27:46 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 03BA33BA for ; Thu, 2 Feb 2017 17:27:45 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v12HRbRA058776; Thu, 2 Feb 2017 17:27:37 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v12HRbb4058775; Thu, 2 Feb 2017 09:27:37 -0800 (PST) (envelope-from david) Date: Thu, 2 Feb 2017 09:27:37 -0800 From: David Wolfskill To: Sergey Matveychuk Cc: freebsd-stable@freebsd.org Subject: Re: kernel installation problem on STABLE-11 Message-ID: <20170202172737.GR1442@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Sergey Matveychuk , freebsd-stable@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uquXjW9+X8a4Yk6h" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 17:27:46 -0000 --uquXjW9+X8a4Yk6h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 02, 2017 at 08:21:29PM +0300, Sergey Matveychuk wrote: > Hi. >=20 > On FreeBSD 11.0 kernel installation procedure is broken. It does not=20 > work without COMPILER_TYPE=3Dclang: That state ment appears to be ... overly broad. I've been doing daily builld/installs of stable/11 on my laptop & a build machine; for me: g1-252(11.0-S)[1] egrep -i 'clang|cc|compile' /etc/src* /etc/make.conf g1-252(11.0-S)[2] echo $? 1 g1-252(11.0-S)[3] > make[2]: "/usr/src/share/mk/bsd.compiler.mk" line 145: Unable to=20 > determine compiler type for CC=3Dcc . Consider setting COMPILER_TYPE. >=20 > Command 'make installworld COMPILER_TYPE=3Dclang KERNCONF=3DMYKERNERL' wo= rks=20 > fine. >=20 > And it looks like it works without COMPILER_TYPE=3Dclang if you buildworl= d=20 > before. But I'm not sure. Oh -- well, I always buildworld before buildkernel before installkernel, of course. > ....=20 Links to pages showing what builds worked for me are at . Peace, david --=20 David H. Wolfskill david@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying con-man??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --uquXjW9+X8a4Yk6h Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYk2wJXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X5VUH/0EkV1skoi89unlkojxnGFGX nANd2pvr7hmKSFcqDyWE+ZqNQNY8isnG31fiW2P2hOCwIXEQe3PsgitBOgyYQarE D7Oe095POevkwFZYaAqMlTMMkurSQdREQa6t2rflb8+xsMx1s6BHXkXrRDdW/F0v rAC4Gv42bBUuY8MQCMzGyyjQLibDlOPVy64kkRac97+WBkO5bhy5EbbTtbos91tl /zE++3LCg+z51ziv0hNUM9Ma5BdHmvAnV6+lTKzOucjy6Zn5TVgQa3YY+p84mefl tfAg1qOh4miPyl0nKbSEb5ljcOsLpTBSiMuTK5VeVdHoLw1SLyflrYIo+eagBTw= =spNt -----END PGP SIGNATURE----- --uquXjW9+X8a4Yk6h-- From owner-freebsd-stable@freebsd.org Thu Feb 2 18:01:40 2017 Return-Path: Delivered-To: freebsd-stable@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 3DA64CCDFB3 for ; Thu, 2 Feb 2017 18:01:40 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::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 F0C50BA for ; Thu, 2 Feb 2017 18:01:39 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3vDnqz1zB7z7h for ; Thu, 2 Feb 2017 19:01:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1486058491; x=1488650492; bh=GrKKr82CywpdnC+GRgOgsLGWZx9iSVAm5Ii gFK0QowI=; b=SSZ5vgb1b1fDKbltTUBw0iAEngSwR9TMRB2XOs+8YZ9IUhpP82R sfHVXBiAFRELmyAXMxP9uVbFDzc5JWk5KY9VRO7ORJ1uhAR0EH0CjH2QfwGbcDoA fM5gnBnADWMcP1GAlxkMPW/z/aV4wDZKWVlQivV6jSRyluG7sagCN4vs= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id vTF_jhET15X6 for ; Thu, 2 Feb 2017 19:01:31 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3vDnqt0wpcz7f for ; Thu, 2 Feb 2017 19:01:30 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3vDnqt03p9z1Mv for ; Thu, 2 Feb 2017 19:01:30 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Thu, 02 Feb 2017 19:01:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 02 Feb 2017 19:01:29 +0100 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: vt(4) gibberish characters in 11.0 with nvidia Organization: Jozef Stefan Institute Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 18:01:40 -0000 I have recently upgraded two hosts with identical nvidia boards (GeForce GT 730, fresh driver nvidia-driver-375.26 from ports), one has been following 11-STABLE every now and then, the other was on 10.3. So they are now at 11.0-RELEASE-p7 or on a recent 11-STABLE respectively. The problem now showing on both hosts is that a virtual terminal console driver (vt(4), no special settings) now shows gibberish character-cells in an approx 90x24 raster. Character cells are of varying colors, some textured, so it looks as if the font loaded was just random junk. The boot screen sequence looks fine up to the moment when the X starts. The X11 screen (with KDE) is fine too. It's just the ttyv0-ttyv7 consoles which are broken. Solved my immediate problem by adding hw.vga.textmode=1 to /boot/loader.conf, so that ttyv consoles now look fine (in fact much nicer, as the vt fonts are pretty squashed and ugly to my eyes). What puzzles me is what has changed recently, as both hosts were happily using vt consoles in graphical mode until the upgrade. (btw, I do have nvidia-modeset.ko and nvidia.ko loaded) Mark From owner-freebsd-stable@freebsd.org Thu Feb 2 18:26:56 2017 Return-Path: Delivered-To: freebsd-stable@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 82A81CCE68A for ; Thu, 2 Feb 2017 18:26:56 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 4C0FE138F for ; Thu, 2 Feb 2017 18:26:56 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-io0-x22a.google.com with SMTP id l66so188752983ioi.1 for ; Thu, 02 Feb 2017 10:26:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p4dnb2WcwP4givVWOTQcqB2dlWVAK06LoEVSsQPY80k=; b=XyRgDVa8oiLmLBL+f3rKnZkCcPFxF9WDAEuoV1M5nsXiw+x29oRCzhP30htU81UCD8 wMqqOQ1bx1IKRpVzmYZWWvsRPo1LV5vDmEBvPMjyo41p92NJGiTkX4wRb+uHLt2KMcJp Sg2flSqa6YVIbxBP0dN+OQ4ro8t6f0kaEcp5DhsngwHtnTn/WA44P10v2BMLap9Nu8bu m2YlEuPPcjBomxzad/asGbiFN9LjzxQuOV5tS94Ui5jTtpwm3rXLQ51K/uUVDwIgMUmO 5Q+7sf+pvauUdikVzmyLWFeq1v3SbULzIwbz+21DpJg5kLipqb/14ut6JHotTX3o1g0J 9Ymw== 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=p4dnb2WcwP4givVWOTQcqB2dlWVAK06LoEVSsQPY80k=; b=S6OKQNDBgx0lTvjwTwSeebbrypGzAw6mOFopPw0pQdpSNmqtAgY9eBgyIN8Q7FQzMr xQbZg20eDvGB80ZbtI/WBs3cnpPJfMMGhg9CcGj/RVAKzT6E2P7rUPpN9qBa96bJOZC5 F+oENPCfmDwIMZKn6yhtzlrPzsMyf9vqlxv1tIrcvp/qitlvJMar0r5zuxFoKySVaEmH x33uv/+hDSUhuVn/6Ij49H2a8ap/+9Qd5cUqWH3779w0otlN7X90pytY+y8TQVny5Kn3 0sIh8d0ea8acE6IIKdmtZ7X2E6FkVCYZEBdxPeOBL1eC25caSiaFG2EmnNkzCwkrBOuY UfwA== X-Gm-Message-State: AIkVDXJecM8rSmLUgFiLaN2VAXYfc7rEaZvlwGHI1HrYCTgNmseOg9OjrDMLjBDy5Orf9Ls2F2L6f0H/1C4I4w== X-Received: by 10.107.59.69 with SMTP id i66mr7528555ioa.10.1486060015453; Thu, 02 Feb 2017 10:26:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.52.200 with HTTP; Thu, 2 Feb 2017 10:26:54 -0800 (PST) X-Originating-IP: [203.99.129.1] In-Reply-To: References: From: Jonathan Chen Date: Fri, 3 Feb 2017 07:26:54 +1300 Message-ID: Subject: Re: kernel installation problem on STABLE-11 To: Sergey Matveychuk Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 18:26:56 -0000 On 3 February 2017 at 06:21, Sergey Matveychuk wrote: > And it looks like it works without COMPILER_TYPE=clang if you buildworld > before. But I'm not sure. /usr/src/UPDATING recommends that buildworld should always be done before buildkernel. Cheers. -- Jonathan Chen From owner-freebsd-stable@freebsd.org Thu Feb 2 18:55:23 2017 Return-Path: Delivered-To: freebsd-stable@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 CFB14CCECA4 for ; Thu, 2 Feb 2017 18:55:23 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::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 6277395D for ; Thu, 2 Feb 2017 18:55:23 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3vDq213jm6zgk for ; Thu, 2 Feb 2017 19:55:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1486061717; x=1488653718; bh=Xkoas8/dySgUSqCbH6Rl5sZ0F2DXe9iMuuw T/1R+gLs=; b=G+lSIy8Zsy1IO77aAATjFiumnbG/aylLoB4Tb0mC63I8tuI+CTp zchgL/+ezXGt1/tnDbD1alte+Mp9I4m7izVLAl7hOsI7oSE1NM214ai9PbXIjAzR 9N7h7BP/xQTLqiY75FyG4fexdTNFDESpvXzAcLj4N+4t1AypZKyglZAM= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id AI5Ve89Xgpnn for ; Thu, 2 Feb 2017 19:55:17 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3vDq1x01Tkzgh for ; Thu, 2 Feb 2017 19:55:17 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3vDq1w6HDsz66 for ; Thu, 2 Feb 2017 19:55:16 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Thu, 02 Feb 2017 19:55:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 02 Feb 2017 19:55:16 +0100 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: net.inet.udp.log_in_vain strange syslog reports Organization: Jozef Stefan Institute Message-ID: <76681a24b7935674585b5ac585f4575c@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 18:55:23 -0000 11.0-RELEASE-p7, net.inet.udp.log_in_vain=1 The following syslog entries seem to indicate some buffer overruns in the reporting code (not all log lines are broken, just some). (the actual failed connection attempts were indeed there, it's just that the reported IP address is highly suspicious) Mark Connection attempt to UDP 193.2.4.2:53 from 95.87.1521242:26375 Connection attempt to UDP 193.2.4.2:53 from 95.87.1521242:55806 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:54530 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:55504 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:54530 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:49526 Connection attempt to UDP 193.2.4.2:53 from 95.8231520242:56838 Connection attempt to UDP 193.2.4.2:53 from 95.8231520242:32768 Connection attempt to UDP 193.2.4.2:53 from 95.8241523242:5387 Connection attempt to UDP 193.2.4.2:53 from 95.8241523242:54530 Connection attempt to UDP 193.2.4.2:53 from 21.823154.242:46692 Connection attempt to UDP 193.2.4.2:53 from 21.823154.242:32768 Connection attempt to UDP 193.2.4.2:53 from 19387.154.242:51931 Connection attempt to UDP 193.2.4.2:53 from 19387.154.242:59881 Connection attempt to UDP 193.2.4.2:53 from 212873154.242:53424 Connection attempt to UDP 193.2.4.2:53 from 212873154.242:53937 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:46692 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:52594 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:59639 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:50869 Connection attempt to UDP 193.2.4.2:53 from 19382.1587242:55806 Connection attempt to UDP 193.2.4.2:53 from 19382.1587242:54650 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:54322 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:49871 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:57807 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:51931 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:52930 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:50869 Connection attempt to UDP 193.2.4.2:53 from 212823152.242:56838 Connection attempt to UDP 193.2.4.2:53 from 212823152.242:32768 Connection attempt to UDP 193.2.4.2:53 from 21.8231521242:63724 Connection attempt to UDP 193.2.4.2:53 from 21.8231521242:55222 Connection attempt to UDP 193.2.4.2:53 from 1948249.230.46:52599 Connection attempt to UDP 193.2.4.2:53 from 1948249.230.46:38496 Connection attempt to UDP 193.2.4.2:53 from 2128235.209.250:43608 Connection attempt to UDP 193.2.4.2:53 from 2128235.209.250:47257 Connection attempt to UDP 193.2.4.2:53 from 19387.1594242:54324 Connection attempt to UDP 193.2.4.2:53 from 19387.1594242:34613 Connection attempt to UDP 193.2.4.2:53 from 2128235.2124180:54377 Connection attempt to UDP 193.2.4.2:53 from 2128235.2124180:50869 Connection attempt to UDP 193.2.4.2:53 from 95.87.1547242:51698 Connection attempt to UDP 193.2.4.2:53 from 95.87.1547242:55222 Connection attempt to UDP 193.2.4.2:53 from 193.2.4.2242:55222 Connection attempt to UDP 193.2.4.2:53 from 19.8241523242:38496 Connection attempt to UDP 193.2.4.2:53 from 19.8241523242:55135 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:50370 Connection attempt to UDP 193.2.4.2:53 from 95.824154.242:64533 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:55222 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:56228 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:53424 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:61230 Connection attempt to UDP 193.2.4.2:53 from 212823154.242:59716 Connection attempt to UDP 193.2.4.2:53 from 212823154.242:53424 Connection attempt to UDP 193.2.4.2:53 from 19387.154.242:36439 Connection attempt to UDP 193.2.4.2:53 from 19387.154.242:60638 Connection attempt to UDP 193.2.4.2:53 from 19387.1521242:59008 Connection attempt to UDP 193.2.4.2:53 from 19387.1521242:35505 Connection attempt to UDP 193.2.4.2:53 from 19.824154.242:54322 Connection attempt to UDP 193.2.4.2:53 from 19.824154.242:30943 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:51752 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:35165 Connection attempt to UDP 193.2.4.2:53 from 95.87.1587242:36439 Connection attempt to UDP 193.2.4.2:53 from 95.87.1587242:57311 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:36439 Connection attempt to UDP 193.2.4.2:53 from 19387.1587242:59280 Connection attempt to UDP 193.2.4.2:53 from 19487.154.242:53424 Connection attempt to UDP 193.2.4.2:53 from 19487.154.242:53247 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:35165 Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:50473 Connection attempt to UDP 193.2.4.2:53 from 21287.154.242:56838 Connection attempt to UDP 193.2.4.2:53 from 21287.154.242:63658 Connection attempt to UDP 193.2.4.2:53 from 21287.154.242:54322 Connection attempt to UDP 193.2.4.2:53 from 21287.154.242:60637 From owner-freebsd-stable@freebsd.org Fri Feb 3 02:31:59 2017 Return-Path: Delivered-To: freebsd-stable@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 CBDA2CCDB27; Fri, 3 Feb 2017 02:31:59 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (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 8E1FF1B07; Fri, 3 Feb 2017 02:31:59 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yb0-x22d.google.com with SMTP id o65so2045961ybo.2; Thu, 02 Feb 2017 18:31:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=dButyUbQ5iTvPrQO/TVCBj8PpIAxBy/Ic44tS/rHWbo=; b=JbexhR1vcawix1HvD9Rr+gmlorncrCHAsQJPWCQCGebMcvHLHEnWuv24bST8TP66Pr dRVCyyUTFnSyjNOMPY5FtOlpIySA0N4x1abQHKLKmXSWIu1vD9MMOuOZc1gUsKj6Knfz fqi31n/tVDL16mesu0kD0Otejx6hAaX5xA/qs1bkq5OK5qG5OuweZpvLfk4y0eeS9Ib3 m/0uaMeuWJ0ooEfZWEfCIvehwMYqlGiqkZwrt9JQWWv0yO1ISy3Wqd61qPHZ3W+1TJEN 2KpBr5luLixmTG7Ju26d8en1WIlq6hQTDK37A5Uc8kwii8oWTP6Su0cZsvodw7gNZqid nhEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dButyUbQ5iTvPrQO/TVCBj8PpIAxBy/Ic44tS/rHWbo=; b=OXcehSapoTSaSoYUNNa3py+UmZP8C+IX3cKVLPS7lVPvw+S9ni5Tsq8MwGXrVTra9V s8k3qflxQLh4q6AIayjGc14hG6T7msg/NDv4S/UbnyM2Jdpc7FXbA0ZRgtkkDM9TJgbN Ra0KwffdVFyRHvyot1GV1VZmxSurq7zOSFY+sHXE7JjUTW7acYqMyMMgjqsN7iP2cMYY 9Rauw1taa85Yetc1iQEKTcT8RDCTR/udFCPj3L4KYXiZIq8ou/satldcdr90fBVqfZc/ nJtebppGt1hl18iUCGSs2uh8g2nuESrahLUzzmCMtGRU8WmxWpinpTHkQM6KdQyk9SH6 kO+Q== X-Gm-Message-State: AIkVDXLzwkF0keeiaxseUK6JkdpRwsYIyZWdEUUJ9m/+AuLXKHZN0PgeOwFBDLz6eI9QM/oTqp1ge5W/SMrEUw== X-Received: by 10.37.248.2 with SMTP id u2mr4670497ybd.52.1486089118503; Thu, 02 Feb 2017 18:31:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.52.65 with HTTP; Thu, 2 Feb 2017 18:31:58 -0800 (PST) From: Ultima Date: Thu, 2 Feb 2017 21:31:58 -0500 Message-ID: Subject: zfs snapshot_limit is not respected To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 02:31:59 -0000 I recently moved some data on a box with limited space. I decided I should limit the snapshots so that space would not become an issue. I just check back a week later to find out the box is hitting the borderline. Doing I quick check I realized that the snapshot_limit is not being respected. # uname -a FreeBSD R1 11.0-STABLE FreeBSD 11.0-STABLE #17 r312232: Sun Jan 15 10:59:10 EST 2017 root@S1:/usr/src/11-STABLE/obj/usr/src/11-STABLE/src/sys/MYKERNEL amd64 # zfs create zroot/bhyve/test # zfs set snapshot_limit=0 zroot/bhyve/test # zfs snapshot zroot/bhyve/test@1 # zfs snapshot zroot/bhyve/test@2 # zfs snapshot zroot/bhyve/test@3 # zfs list -t snapshot | grep zroot/bhyve/test zroot/bhyve/test@1 0 - 88K - zroot/bhyve/test@2 0 - 88K - zroot/bhyve/test@3 0 - 88K - # zfs get all zroot/bhyve/test | grep snapshot zroot/bhyve/test usedbysnapshots 0 - zroot/bhyve/test snapshot_limit 0 local zroot/bhyve/test snapshot_count 3 local Also wanted to verify 0 was not being mistaken for none. # for snapshot in `zfs list -t snapshot | grep zroot/bhyve/test | awk '{print $1}'`; do zfs destroy $snapshot ; done # zfs get all zroot/bhyve/test | grep snapshot zroot/bhyve/test usedbysnapshots 0 - zroot/bhyve/test snapshot_limit 0 local zroot/bhyve/test snapshot_count 0 local # zfs set snapshot_limit=1 zroot/bhyve/test # zfs snapshot zroot/bhyve/test@1 # zfs snapshot zroot/bhyve/test@2 # zfs snapshot zroot/bhyve/test@3 # zfs get all zroot/bhyve/test | grep snapshot zroot/bhyve/test usedbysnapshots 0 - zroot/bhyve/test snapshot_limit 1 local zroot/bhyve/test snapshot_count 3 local Also tested on head FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #26 r312388: Wed Jan 18 12:38:52 EST 2017 root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG amd64 From owner-freebsd-stable@freebsd.org Fri Feb 3 08:30:37 2017 Return-Path: Delivered-To: freebsd-stable@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 0332DCCE21A for ; Fri, 3 Feb 2017 08:30:37 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 734D7ABF for ; Fri, 3 Feb 2017 08:30:36 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id v138U6HS087034 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Feb 2017 09:30:06 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id v138U5xT087031; Fri, 3 Feb 2017 09:30:06 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 3 Feb 2017 09:30:05 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Jonathan Chen cc: Sergey Matveychuk , freebsd-stable@freebsd.org Subject: Re: kernel installation problem on STABLE-11 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 08:30:37 -0000 On Fri, 3 Feb 2017 07:26+1300, Jonathan Chen wrote: > On 3 February 2017 at 06:21, Sergey Matveychuk wrote: > > And it looks like it works without COMPILER_TYPE=clang if you buildworld > > before. But I'm not sure. > > /usr/src/UPDATING recommends that buildworld should always be done > before buildkernel. In fact, the top Makefile will enforce that order when both targets are given: .ORDER: buildworld installworld .ORDER: buildworld distributeworld .ORDER: buildworld buildkernel .ORDER: installworld distribution .ORDER: installworld installkernel .ORDER: buildkernel installkernel .ORDER: buildkernel installkernel.debug .ORDER: buildkernel reinstallkernel .ORDER: buildkernel reinstallkernel.debug -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@freebsd.org Fri Feb 3 12:42:53 2017 Return-Path: Delivered-To: freebsd-stable@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 C2478CCD0D4; Fri, 3 Feb 2017 12:42:53 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 8E9EE16DE; Fri, 3 Feb 2017 12:42:53 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cZdCV-0004Kq-NV; Fri, 03 Feb 2017 12:42:51 +0000 Date: Fri, 3 Feb 2017 12:42:51 +0000 From: Gary Palmer To: Ultima Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: zfs snapshot_limit is not respected Message-ID: <20170203124251.GA68015@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 12:42:53 -0000 On Thu, Feb 02, 2017 at 09:31:58PM -0500, Ultima wrote: > I recently moved some data on a box with limited space. I decided I should > limit the snapshots so that space would not become an issue. I just check > back a week later to find out the box is hitting the borderline. Doing I > quick check I realized that the snapshot_limit is not being respected. > > # uname -a > FreeBSD R1 11.0-STABLE FreeBSD 11.0-STABLE #17 r312232: Sun Jan 15 10:59:10 > EST 2017 root@S1:/usr/src/11-STABLE/obj/usr/src/11-STABLE/src/sys/MYKERNEL > amd64 > > # zfs create zroot/bhyve/test > # zfs set snapshot_limit=0 zroot/bhyve/test > # zfs snapshot zroot/bhyve/test@1 > > > # zfs snapshot zroot/bhyve/test@2 > # zfs snapshot zroot/bhyve/test@3 > # zfs list -t snapshot | grep zroot/bhyve/test > zroot/bhyve/test@1 0 - > 88K - > zroot/bhyve/test@2 0 - > 88K - > zroot/bhyve/test@3 0 - > 88K - > # zfs get all zroot/bhyve/test | grep snapshot > zroot/bhyve/test usedbysnapshots 0 - > zroot/bhyve/test snapshot_limit 0 local > zroot/bhyve/test snapshot_count 3 local > > Also wanted to verify 0 was not being mistaken for none. > > # for snapshot in `zfs list -t snapshot | grep zroot/bhyve/test | awk > '{print $1}'`; do zfs destroy $snapshot ; done > > # zfs get all zroot/bhyve/test | grep snapshot > zroot/bhyve/test usedbysnapshots 0 - > zroot/bhyve/test snapshot_limit 0 local > zroot/bhyve/test snapshot_count 0 local > > # zfs set snapshot_limit=1 zroot/bhyve/test > # zfs snapshot zroot/bhyve/test@1 > # zfs snapshot zroot/bhyve/test@2 > # zfs snapshot zroot/bhyve/test@3 > # zfs get all zroot/bhyve/test | grep snapshot > zroot/bhyve/test usedbysnapshots 0 - > zroot/bhyve/test snapshot_limit 1 local > zroot/bhyve/test snapshot_count 3 local > > > Also tested on head > FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #26 r312388: Wed Jan 18 > 12:38:52 EST 2017 > root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG > amd64 Hi, I suspect this line from the manpage is key: The limit is not enforced if the user is allowed to change the limit Regards, Gary From owner-freebsd-stable@freebsd.org Fri Feb 3 15:27:49 2017 Return-Path: Delivered-To: freebsd-stable@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 E2221CCE701; Fri, 3 Feb 2017 15:27:49 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 8F80FC59; Fri, 3 Feb 2017 15:27:49 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yb0-x22c.google.com with SMTP id 123so6869657ybe.3; Fri, 03 Feb 2017 07:27:49 -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=90z5R+cAE8kRp+53gjHy5SjNSxArbYP8OHsumqA/KhI=; b=kN/HAPFFp2mxF40sPpRcerux4+folvEhDEEJ+JKf6eE2TV7/W8MbG9S5ui5l6JvwlM wRawdPuksTlE3kHOh8FlK2RqaZn/UJjL0iHR0BaJRHwxUT7maWa/rHi2D2ZnBIKYlCf3 8DGg/wCXVfl/lnZpeiKO8gq2SMTM+6xYY1vgnWygPNG7omWxJdi/jsrcbTr4CV37XdF+ xcbVPXAjsSJvwmwgrpBtX1dKsoAkZ+b9fgsadZH+i3v8jksgHEt+5SlSeF/Ldj9/OMps uk2Oc5uYMFECkp7Z6yZg2hm55ytVZDxAKeTZfQUfreUE8bY2onzvpreKBuZeC/ubzFUi GRUw== 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=90z5R+cAE8kRp+53gjHy5SjNSxArbYP8OHsumqA/KhI=; b=MEz5yiywi1GIDNQpmQ8OTVNyGtnZDz1RqUDOjoe0LiChF5SJJrglxeQbgMsdM8TEmd wsIiiRdDn6SeTtCGm9t10q6ZV9Htjjfz/TyD8+RjCOMrIgS+KpyHWi1Cvhj7zzSvziSq cjhmYbrbVjmCiROHI74KI3QcosVeB3ZLMPjqbzKYIB40wjdyGydkkX5bg8FWPI9jUZwx Il6kBBMUcdRZXBM5zDSslqYFGU9u4m5wbCVhzRYMaGM5YPvParbPDh2V5V2fWnhU8R3n diihIRL4KRN5ZDfeJA2PlIJNwWzXoZ3ndx0OxyEOlJkYxoXh2jYDsCOcmCg6jWQJHKZy hJDQ== X-Gm-Message-State: AIkVDXJKncecFJDMjmkV9241CdcxuTYc5V6h4lizevSjsCF+oYUhI7c6ig7km9Xwwv4dV9rJH8vApkZGOthrAA== X-Received: by 10.37.248.2 with SMTP id u2mr6440810ybd.52.1486135668573; Fri, 03 Feb 2017 07:27:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.52.65 with HTTP; Fri, 3 Feb 2017 07:27:48 -0800 (PST) In-Reply-To: <20170203124251.GA68015@in-addr.com> References: <20170203124251.GA68015@in-addr.com> From: Ultima Date: Fri, 3 Feb 2017 10:27:48 -0500 Message-ID: Subject: Re: zfs snapshot_limit is not respected To: Gary Palmer Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 15:27:50 -0000 Hey Gary, You are probably right. Do you know how to "lock" this property by chance? I'v read this exact line several times trying to understand the exact meaning. The "user is allowed to change the limit" I *think* is referring to the zfs allow command. The problem is that I checked the dataset and it is showing no permissions granted to a user. So I guess user in this case is also including the root user, but how does one lock the property from root? I keep going through the manpage looking for something I may have missed but keep coming up empty. Thanks for replying, Ultima On Fri, Feb 3, 2017 at 7:42 AM, Gary Palmer wrote: > On Thu, Feb 02, 2017 at 09:31:58PM -0500, Ultima wrote: > > I recently moved some data on a box with limited space. I decided I > should > > limit the snapshots so that space would not become an issue. I just check > > back a week later to find out the box is hitting the borderline. Doing I > > quick check I realized that the snapshot_limit is not being respected. > > > > # uname -a > > FreeBSD R1 11.0-STABLE FreeBSD 11.0-STABLE #17 r312232: Sun Jan 15 > 10:59:10 > > EST 2017 root@S1:/usr/src/11-STABLE/obj/usr/src/11-STABLE/src/sys/ > MYKERNEL > > amd64 > > > > # zfs create zroot/bhyve/test > > # zfs set snapshot_limit=0 zroot/bhyve/test > > # zfs snapshot zroot/bhyve/test@1 > > > > > > # zfs snapshot zroot/bhyve/test@2 > > # zfs snapshot zroot/bhyve/test@3 > > # zfs list -t snapshot | grep zroot/bhyve/test > > zroot/bhyve/test@1 0 - > > 88K - > > zroot/bhyve/test@2 0 - > > 88K - > > zroot/bhyve/test@3 0 - > > 88K - > > # zfs get all zroot/bhyve/test | grep snapshot > > zroot/bhyve/test usedbysnapshots 0 - > > zroot/bhyve/test snapshot_limit 0 local > > zroot/bhyve/test snapshot_count 3 local > > > > Also wanted to verify 0 was not being mistaken for none. > > > > # for snapshot in `zfs list -t snapshot | grep zroot/bhyve/test | awk > > '{print $1}'`; do zfs destroy $snapshot ; done > > > > # zfs get all zroot/bhyve/test | grep snapshot > > zroot/bhyve/test usedbysnapshots 0 - > > zroot/bhyve/test snapshot_limit 0 local > > zroot/bhyve/test snapshot_count 0 local > > > > # zfs set snapshot_limit=1 zroot/bhyve/test > > # zfs snapshot zroot/bhyve/test@1 > > # zfs snapshot zroot/bhyve/test@2 > > # zfs snapshot zroot/bhyve/test@3 > > # zfs get all zroot/bhyve/test | grep snapshot > > zroot/bhyve/test usedbysnapshots 0 - > > zroot/bhyve/test snapshot_limit 1 local > > zroot/bhyve/test snapshot_count 3 local > > > > > > Also tested on head > > FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #26 r312388: Wed Jan 18 > > 12:38:52 EST 2017 > > root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG > > amd64 > > Hi, > > I suspect this line from the manpage is key: > > The limit is not enforced if the user is allowed to change the limit > > Regards, > > Gary > From owner-freebsd-stable@freebsd.org Fri Feb 3 16:12:10 2017 Return-Path: Delivered-To: freebsd-stable@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 1A6E0CCF536; Fri, 3 Feb 2017 16:12:10 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 DA64E8C7; Fri, 3 Feb 2017 16:12:09 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cZgT2-0003hV-22; Fri, 03 Feb 2017 16:12:08 +0000 Date: Fri, 3 Feb 2017 16:12:07 +0000 From: Gary Palmer To: Ultima Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: zfs snapshot_limit is not respected Message-ID: <20170203161207.GB68015@in-addr.com> References: <20170203124251.GA68015@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 16:12:10 -0000 On Fri, Feb 03, 2017 at 10:27:48AM -0500, Ultima wrote: > Hey Gary, > > You are probably right. Do you know how to "lock" this property by chance? > I'v read this exact line several times trying to understand the exact > meaning. The "user is allowed to change the limit" I *think* is referring > to the zfs allow command. The problem is that I checked the dataset and it > is showing no permissions granted to a user. So I guess user in this case > is also including the root user, but how does one lock the property from > root? I keep going through the manpage looking for something I may have > missed but keep coming up empty. Hi, I suspect you can't lock root out, but you could allow a different user to create snapshots. If you use that user to create snapshots, they should be subject to the snapshot limit, assuming you don't let them change that property. Regards, Gary > Thanks for replying, > Ultima > > On Fri, Feb 3, 2017 at 7:42 AM, Gary Palmer wrote: > > > On Thu, Feb 02, 2017 at 09:31:58PM -0500, Ultima wrote: > > > I recently moved some data on a box with limited space. I decided I > > should > > > limit the snapshots so that space would not become an issue. I just check > > > back a week later to find out the box is hitting the borderline. Doing I > > > quick check I realized that the snapshot_limit is not being respected. > > > > > > # uname -a > > > FreeBSD R1 11.0-STABLE FreeBSD 11.0-STABLE #17 r312232: Sun Jan 15 > > 10:59:10 > > > EST 2017 root@S1:/usr/src/11-STABLE/obj/usr/src/11-STABLE/src/sys/ > > MYKERNEL > > > amd64 > > > > > > # zfs create zroot/bhyve/test > > > # zfs set snapshot_limit=0 zroot/bhyve/test > > > # zfs snapshot zroot/bhyve/test@1 > > > > > > > > > # zfs snapshot zroot/bhyve/test@2 > > > # zfs snapshot zroot/bhyve/test@3 > > > # zfs list -t snapshot | grep zroot/bhyve/test > > > zroot/bhyve/test@1 0 - > > > 88K - > > > zroot/bhyve/test@2 0 - > > > 88K - > > > zroot/bhyve/test@3 0 - > > > 88K - > > > # zfs get all zroot/bhyve/test | grep snapshot > > > zroot/bhyve/test usedbysnapshots 0 - > > > zroot/bhyve/test snapshot_limit 0 local > > > zroot/bhyve/test snapshot_count 3 local > > > > > > Also wanted to verify 0 was not being mistaken for none. > > > > > > # for snapshot in `zfs list -t snapshot | grep zroot/bhyve/test | awk > > > '{print $1}'`; do zfs destroy $snapshot ; done > > > > > > # zfs get all zroot/bhyve/test | grep snapshot > > > zroot/bhyve/test usedbysnapshots 0 - > > > zroot/bhyve/test snapshot_limit 0 local > > > zroot/bhyve/test snapshot_count 0 local > > > > > > # zfs set snapshot_limit=1 zroot/bhyve/test > > > # zfs snapshot zroot/bhyve/test@1 > > > # zfs snapshot zroot/bhyve/test@2 > > > # zfs snapshot zroot/bhyve/test@3 > > > # zfs get all zroot/bhyve/test | grep snapshot > > > zroot/bhyve/test usedbysnapshots 0 - > > > zroot/bhyve/test snapshot_limit 1 local > > > zroot/bhyve/test snapshot_count 3 local > > > > > > > > > Also tested on head > > > FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #26 r312388: Wed Jan 18 > > > 12:38:52 EST 2017 > > > root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG > > > amd64 > > > > Hi, > > > > I suspect this line from the manpage is key: > > > > The limit is not enforced if the user is allowed to change the limit > > > > Regards, > > > > Gary > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Fri Feb 3 16:44:02 2017 Return-Path: Delivered-To: freebsd-stable@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 84919CCE050; Fri, 3 Feb 2017 16:44:02 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 35655177B; Fri, 3 Feb 2017 16:44:02 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yb0-x231.google.com with SMTP id w194so7664274ybe.0; Fri, 03 Feb 2017 08:44:02 -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=DSwEZUv9I7ly4VSc/iYaj5I+vRlU7Wvz5KkTTdiRjdg=; b=pHg+aUedD3UxK6K17pXg8f2p/Uv+DID12DY4TagUnfI9+a40B0z8b+E17K+PCTqin0 l+Hu0oqMTwxnftRS0nEDBQqTazOmbmxt9uUTODJMO09rjAi9Z2EnViEcUB8wd2KW1qQF 4DWueGjrMCIP1msYSFVDLlMTmTscYA9yIkpKJVhNhXrNIH+04UodIJQZwhNuahIeJsyK BfMPBFXn9Yvug029zLhnE6jysptop+OGqZi6ytW+p5BulXjP1eTvYLlnR+HuPYEWmydz likhWGGe5P0RCA5lAaHKqiP3VoV/IHZmyvTrZzdTkkSHah2GQnR/6UqB5g92W3KRkMXl z9nA== 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=DSwEZUv9I7ly4VSc/iYaj5I+vRlU7Wvz5KkTTdiRjdg=; b=Mol+9YYXydtn643+HbS7w3VHf7SJjJddNthiHwk3EVHelbk9uNx4WdoxyTHvtSJC0J ZD/twrBJ7uTkcyJv8abciuGhuR8hHFUnX/9znQA+6mvBVxhp9U3Y/f81TcPpC3G7zf+1 inEkGQijCarhv4AMB+wM88g2Lg0hAI+Ne0jJ5uBfvdSr8wK55N67yzx3CqulfJwvm044 cZrqxeOVaeZjCdMYBz6sulKgWaboVOH+aOhTnrSYkxsKqXqUClCzlOZYNsIYJre2kEyT PMzMVvNSL2DUUTqQYTYRM34fKMx/NK464tiJDidrtS1nT7s/kG5PPgSVNX7GDDdsHrxs VLgg== X-Gm-Message-State: AIkVDXKuo/GLw/VC5oZiZowefaQT4ZonC2CJwruT/c6ZdnjLpUNXYtR7wgep2HFu7voru55DEIGEwl1N27nAUg== X-Received: by 10.37.56.208 with SMTP id f199mr6592142yba.94.1486140241182; Fri, 03 Feb 2017 08:44:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.52.65 with HTTP; Fri, 3 Feb 2017 08:44:00 -0800 (PST) In-Reply-To: <20170203161207.GB68015@in-addr.com> References: <20170203124251.GA68015@in-addr.com> <20170203161207.GB68015@in-addr.com> From: Ultima Date: Fri, 3 Feb 2017 11:44:00 -0500 Message-ID: Subject: Re: zfs snapshot_limit is not respected To: Gary Palmer Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 16:44:02 -0000 Yes just tested this and it is how it works. Thanks for the explanation. Ultima From owner-freebsd-stable@freebsd.org Fri Feb 3 17:44:48 2017 Return-Path: Delivered-To: freebsd-stable@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 72788CCF7F5 for ; Fri, 3 Feb 2017 17:44:48 +0000 (UTC) (envelope-from stephen.joseph@united-email.info) Received: from mserver.united-email.info (mail.united-email.info [137.59.52.162]) by mx1.freebsd.org (Postfix) with ESMTP id C69AF77E for ; Fri, 3 Feb 2017 17:44:47 +0000 (UTC) (envelope-from stephen.joseph@united-email.info) Received: from UnitedPC (unknown [202.133.79.30]) by mserver.united-email.info (Postfix) with ESMTPA id 33619193ECF for ; Fri, 3 Feb 2017 23:16:04 +0530 (IST) Reply-To: From: "Stephen Joseph" To: Subject: Ask a question Date: Fri, 3 Feb 2017 12:44:04 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdJ+RGhnECI+w0VGQTqebZiz/NzUwQ== Content-Language: en-us x-cr-hashedpuzzle: APJS AlJ1 CFwi Cxr8 DX2U DmHl Ejl6 FIng FnV3 FuFv Gqp1 IMNf ISxH JRS+ JpmF KCDY; 1; ZgByAGUAZQBiAHMAZAAtAHMAdABhAGIAbABlAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {736C4557-A5D0-4392-87A2-54DB2B617D4C}; cwB0AGUAcABoAGUAbgAuAGoAbwBzAGUAcABoAEAAdQBuAGkAdABlAGQALQBlAG0AYQBpAGwALgBpAG4AZgBvAA==; Fri, 03 Feb 2017 17:44:02 GMT; QQBzAGsAIABhACAAcQB1AGUAcwB0AGkAbwBuAA== x-cr-puzzleid: {736C4557-A5D0-4392-87A2-54DB2B617D4C} Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 17:44:48 -0000 Hi, My name is Stephen Joseph, the Business Development Manager at one of = the leading email database providing companies.=20 Our area of expertise lies specifically in the major industrial lists = like: Agriculture, Business Services, Chambers of Commerce, Cities, Towns & Municipalities, Construction, Consumer Services, Cultural, Education, Energy, Utilities & Waste Treatment, Finance, Government, Healthcare, Hospitality, Insurance, Law Firms & Legal Services, Manufacturing, Media = & Internet, Metals & Mining, Organizations, Real Estate, Retail, Software, Telecommunications, Transportation, etc. Building long term relationships with our clients is something we = strongly believe in and we go to great lengths to ensure our valuable clients = receive first rate service. Some of the most popular services we offer include: =FC List service #1 - B2B & B2C Email Lists =FC List service #2 -Data Processing & Email Appending =FC List service #3 - Email Campaigning =20 We=92d welcome the opportunity to discuss your email list needs.=20 Best Regards, =20 Stephen Joseph | Business Development Associate | T: +1 610 572 4885 Global Business Data =96 Email Append =96 Data Append. =20 If you are not interested in receiving further emails, please reply back with =93LEAVEOUT=94 in the subject line=94. =20 From owner-freebsd-stable@freebsd.org Fri Feb 3 19:05:32 2017 Return-Path: Delivered-To: freebsd-stable@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 DDC6ECCF564 for ; Fri, 3 Feb 2017 19:05:32 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id C9BCD2F3 for ; Fri, 3 Feb 2017 19:05:32 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from ford.home.vangyzen.net (unknown [76.164.15.242]) by smtp.vangyzen.net (Postfix) with ESMTPSA id EA78056469; Fri, 3 Feb 2017 13:05:31 -0600 (CST) Subject: Re: net.inet.udp.log_in_vain strange syslog reports To: Mark Martinec , freebsd-stable@freebsd.org References: <76681a24b7935674585b5ac585f4575c@ijs.si> From: Eric van Gyzen Message-ID: Date: Fri, 3 Feb 2017 13:05:27 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <76681a24b7935674585b5ac585f4575c@ijs.si> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 19:05:33 -0000 On 02/02/2017 12:55, Mark Martinec wrote: > 11.0-RELEASE-p7, net.inet.udp.log_in_vain=1 > > The following syslog entries seem to indicate some buffer overruns > in the reporting code (not all log lines are broken, just some). > > (the actual failed connection attempts were indeed there, > it's just that the reported IP address is highly suspicious) > > Mark > > > Connection attempt to UDP 193.2.4.2:53 from 95.87.1521242:26375 There is no buffer overrun, so no cause for alarm. The problem is concurrent usage of a single string buffer by multiple threads. The buffer is inside inet_ntoa(), defined in sys/libkern/inet_ntoa.c. In this case, it is called from udp_input(). Would you like to test the following patch? Eric diff --git a/sys/netinet/udp_usrreq.c b/sys/netinet/udp_usrreq.c index 173c44c..ca2dda1 100644 --- a/sys/netinet/udp_usrreq.c +++ b/sys/netinet/udp_usrreq.c @@ -674,13 +674,13 @@ udp_input(struct mbuf **mp, int *offp, int proto) INPLOOKUP_RLOCKPCB, ifp, m); if (inp == NULL) { if (udp_log_in_vain) { - char buf[4*sizeof "123"]; + char src[4*sizeof "123"]; + char dst[4*sizeof "123"]; - strcpy(buf, inet_ntoa(ip->ip_dst)); log(LOG_INFO, "Connection attempt to UDP %s:%d from %s:%d\n", - buf, ntohs(uh->uh_dport), inet_ntoa(ip->ip_src), - ntohs(uh->uh_sport)); + inet_ntoa_r(ip->ip_dst, dst), ntohs(uh->uh_dport), + inet_ntoa_r(ip->ip_src, src), ntohs(uh->uh_sport)); } UDPSTAT_INC(udps_noport); if (m->m_flags & (M_BCAST | M_MCAST)) { From owner-freebsd-stable@freebsd.org Sat Feb 4 00:13:29 2017 Return-Path: Delivered-To: freebsd-stable@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 D09D3CCEFDF for ; Sat, 4 Feb 2017 00:13:29 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 445081010 for ; Sat, 4 Feb 2017 00:13:28 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sat, 04 Feb 2017 01:12:15 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 86689747-C0CD-48FF-9BA5-CF5D1E35BE3C.1 envelope-from (authenticated bits=0); Sat, 04 Feb 2017 01:12:13 +0100 From: Rainer Duffner Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Problem with FreeBSD as a XenServer Guest - how to debug? Message-Id: Date: Sat, 4 Feb 2017 01:12:11 +0100 To: freebsd-stable Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=14 total_conn=8 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 2209, bad: 1, connections: 2606, history: 2208, asn_score: 732, asn_connections: 819, asn_good: 732, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 00:13:29 -0000 Hi, I=E2=80=99ve opened a PR on this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681 and asked on freebsd-virtualization. But nothing came out of it. Basically, I/O is very slow inside the FreeBSD guest. Linux guests are = OK. FreeBSD 10 or 11 doesn=E2=80=99t make a difference. Haven=E2=80=99t been able to try 12. How can one debug this? Rainer= From owner-freebsd-stable@freebsd.org Sat Feb 4 09:54:44 2017 Return-Path: Delivered-To: freebsd-stable@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 24731CCF3BA for ; Sat, 4 Feb 2017 09:54:44 +0000 (UTC) (envelope-from florian.ermisch@alumni.tu-berlin.de) Received: from mail-2.alumni.tu-berlin.de (mail-2.alumni.tu-berlin.de [130.149.5.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D90D41041 for ; Sat, 4 Feb 2017 09:54:43 +0000 (UTC) (envelope-from florian.ermisch@alumni.tu-berlin.de) X-tubIT-Incoming-IP: 78.52.8.167 Received: from x4e3408a7.dyn.telefonica.de ([78.52.8.167] helo=floh-lg-g4.fritz.box) by mailbox.alumni.tu-berlin.de (exim-4.84_2) with esmtpsa [TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256] id 1cZwxU-0005FM-A3; Sat, 04 Feb 2017 10:48:40 +0100 Date: Sat, 04 Feb 2017 10:48:38 +0100 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Problem with FreeBSD as a XenServer Guest - how to debug? To: freebsd-stable@freebsd.org,Rainer Duffner From: Florian Ermisch Message-ID: <37CEE483-1901-4B8A-AB89-654D6C4DA6C7@alumni.tu-berlin.de> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 09:54:44 -0000 Hi Rainer, isn't Amazon AWS xen-based? I know Colin Percival (cperciva@) is running=20 tarsnap=2Ecom on AWS, maybe he knows how=20 to tune it properly? Looks like he's the one providing FreeBSD=20 images for AWS, too: https://aws=2Eamazon=2Ecom/marketplace/pp/B01LWSWRED/ Amazon is probably running a heavily patched version of Xen but looking at the images'=20 sysctls & stuff and running one on your Xen- Server might provide some insights - or at least datapoints=2E And then there's DTrace to dive into the=20 kernel's inner workings*=E2=80=A6 Oh, does Xen still provide emulation for other storage controllers like SATA or SAS? If so you may get an at least bearable performance using those=2E Regards, Florian Am 4=2E Februar 2017 01:12:11 MEZ schrieb Rainer Duffner : > Hi, >=20 > I=E2=80=99ve opened a PR on this: >=20 > https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D212681 >=20 > and asked on freebsd-virtualization=2E But nothing came out of it=2E >=20 > Basically, I/O is very slow inside the FreeBSD guest=2E Linux guests are > OK=2E > FreeBSD 10 or 11 doesn=E2=80=99t make a difference=2E > Haven=E2=80=99t been able to try 12=2E >=20 >=20 > How can one debug this? >=20 >=20 >=20 >=20 > Rainer > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd=2Eorg" From owner-freebsd-stable@freebsd.org Sat Feb 4 13:27:01 2017 Return-Path: Delivered-To: freebsd-stable@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 BB089CCE955 for ; Sat, 4 Feb 2017 13:27:01 +0000 (UTC) (envelope-from xenophon@irtnog.org) Received: from mx1.irtnog.org (rrcs-24-123-13-61.central.biz.rr.com [24.123.13.61]) by mx1.freebsd.org (Postfix) with ESMTP id 8A31E1C99 for ; Sat, 4 Feb 2017 13:27:00 +0000 (UTC) (envelope-from xenophon@irtnog.org) Received: from uxeprdbsdmx01.irtnog.net (localhost [127.0.0.1]) by mx1.irtnog.org (Postfix) with ESMTP id C51CD1C8559 for ; Sat, 4 Feb 2017 08:18:31 -0500 (EST) X-Virus-Scanned: amavisd-new at irtnog.org Received: from mx1.irtnog.org ([127.0.0.1]) by uxeprdbsdmx01.irtnog.net (mx1.irtnog.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CP8f97H5HAPr for ; Sat, 4 Feb 2017 08:18:29 -0500 (EST) Received: from cinip100ntsbs.irtnog.net (cinip100ntsbs.irtnog.net [10.63.1.100]) by mx1.irtnog.org (Postfix) with ESMTP for ; Sat, 4 Feb 2017 08:18:29 -0500 (EST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: Swapping from a zvol results in a deadman panic Date: Sat, 4 Feb 2017 08:18:28 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Swapping from a zvol results in a deadman panic Thread-Index: AdJ+6Q1Qu8mx9sRTTwumuchR8Q4d8g== From: "Matthew X. Economou" To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 13:27:01 -0000 My FreeBSD 10.3-RELEASE-p16 server crashes in the middle of a Poudriere bulk run (see below). This crash happens even if I lower vfs.zfs.arc_max or tweak vm.v_free_min/target/reserved/severe. I'm looking for configuration advice in case I missed something obvious, since this seems to work on Illumos- and Linux-derived O/Ses, but failing that, I'd like to get some advice as to how to go about debugging this. I doubt the deadman timer causes the system to stop responding. It's more likely a race condition elsewhere. The pool itself uses 4k sectors and is geli-encrypted. I configured the swap zvol based on root-on-ZFS install instructions found in the FreeBSD wiki: zfs create -V 6G -o org.freebsd:swap=3Don -o checksum=3Doff -o compression=3Doff -o dedup=3Doff -o sync=3Ddisabled -o = primarycache=3Dnone zroot/swap The ZoL wiki recommends a slightly different zvol configuration: zfs create -V 4G -b $(getconf PAGESIZE) -o logbias=3Dthroughput -o sync=3Dalways -o primarycache=3Dmetadata -o = com.sun:auto-snapshot=3Dfalse rpool/swap I'm not sure how much of this applies to FreeBSD due to differences in kernel design/implementation. Does anyone have an idea of what might be going on and how I might get this working? last pid: 35097; load averages: 0.54, 4.38, 5.99 up 0+05:23:35 03:27:19 94 processes: 1 running, 89 sleeping, 4 waiting CPU: 0.1% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.9% idle Mem: 911M Active, 1983M Inact, 979M Wired, 772K Cache, 320K Buf, 14M Free ARC: 220M Total, 12M MFU, 45M MRU, 34M Anon, 6645K Header, 122M Other Swap: 6144M Total, 574M Used, 5570M Free, 9% Inuse panic: I/O to pool 'zroot' appears to be hung on vdev guid 13314812526404996608 at '/dev/da0p3.eli'. cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff8098e3e0 at kdb_backtrace+0x60 #1 0xffffffff809510b6 at vpanic+0x126 #2 0xffffffff80950f83 at panic+0x43 #3 0xffffffff81a3ddd3 at vdev_deadman+0x123 #4 0xffffffff81a3dce0 at vdev_deadman+0x30 #5 0xffffffff81a3dce0 at vdev_deadman+0x30 #6 0xffffffff81a325a5 at spa_deadman+0x85 #7 0xffffffff80966c2b at softclock_call_cc+0x17b #8 0xffffffff80967054 at softclock+0x94 #9 0xffffffff8091c9eb at intr_event_execute_handlers+0xab #10 0xffffffff8091ce36 at ithread_loop+0x96 #11 0xffffffff8091a53a at fork_exit+0x9a #12 0xffffffff80d3be0e at fork_trampoline+0xe Uptime: 1h8m24s --=20 "The lyf so short, the craft so longe to lerne." From owner-freebsd-stable@freebsd.org Sat Feb 4 17:00:25 2017 Return-Path: Delivered-To: freebsd-stable@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 9DE0CCD0595 for ; Sat, 4 Feb 2017 17:00:25 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id EA90913DA for ; Sat, 4 Feb 2017 17:00:24 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sat, 04 Feb 2017 18:00:22 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 1064C2B9-87B2-4799-8798-80895AE5084E.1 envelope-from (authenticated bits=0); Sat, 04 Feb 2017 18:00:19 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Problem with FreeBSD as a XenServer Guest - how to debug? From: Rainer Duffner In-Reply-To: <37CEE483-1901-4B8A-AB89-654D6C4DA6C7@alumni.tu-berlin.de> Date: Sat, 4 Feb 2017 18:00:16 +0100 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9D72A1D4-C728-4405-8101-11734D092615@ultra-secure.de> References: <37CEE483-1901-4B8A-AB89-654D6C4DA6C7@alumni.tu-berlin.de> To: Florian Ermisch X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=14 total_conn=1 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 2213, bad: 1, connections: 2610, history: 2212, asn_score: 736, asn_connections: 823, asn_good: 736, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 17:00:25 -0000 > Am 04.02.2017 um 10:48 schrieb Florian Ermisch = : >=20 > Hi Rainer, >=20 > isn't Amazon AWS xen-based? > I know Colin Percival (cperciva@) is running=20 > tarsnap.com on AWS, maybe he knows how=20 > to tune it properly? It=E2=80=99s not a question of tuning. It=E2=80=99s a factor of 5 that FreeBSD is slower. On SSDs, it=E2=80=99s = 10 to 15x. > Looks like he's the one providing FreeBSD=20 > images for AWS, too: https://aws.amazon.com/marketplace/pp/B01LWSWRED/ > Amazon is probably running a heavily patched > version of Xen but looking at the images'=20 > sysctls & stuff and running one on your Xen- > Server might provide some insights - or at > least datapoints. >=20 > And then there's DTrace to dive into the=20 > kernel's inner workings*=E2=80=A6 >=20 Yes, but I don=E2=80=99t even know there to start. My knowledge of Dtrace is very, very limited. > Oh, does Xen still provide emulation for other > storage controllers like SATA or SAS? If so > you may get an at least bearable performance > using those. FreeBSD 10 and 11 contain the =E2=80=9Eoptimal=E2=80=9C support for Xen = DomU support out-of-the box, AFAIK (the documentation / wiki for Xen is = in a horrible state IMO).