Dear Colleagues, I am offering ARM64 server for builds and tests. It has 8 core and a spare 256GB SSD disk to install the OS and to boot from it.
My knowledge and technical capacities are extremely modest, but I am also offering my time. Currently the server runs poor man's OS (namely - Linux) on the other SSD disk. I would happily grant the required access to the server. Kind regards, Marius Gaubas Sent from my iPhone > On 29 Sep 2016, at 14:00, freebsd-current-requ...@freebsd.org wrote: > > Send freebsd-current mailing list submissions to > freebsd-current@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to > freebsd-current-requ...@freebsd.org > > You can reach the person managing the list at > freebsd-current-ow...@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." > > > Today's Topics: > > 1. Re: Destroy GPT partition scheme absolutely, how? (Andriy Gapon) > 2. [HEADS-UP] 11.0-RELEASE status update (Glen Barber) > 3. Re: zpool (online|replace|labelclear) issues, -f option also > failing (Ultima) > 4. [REVISED] [HEADS-UP] 11.0-RELEASE status update (Glen Barber) > 5. Second Call for 2016Q3 quarterly status reports (Benjamin Kaduk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Sep 2016 01:01:44 +0300 > From: Andriy Gapon <a...@freebsd.org> > To: "Andrey V. Elsukov" <bu7c...@yandex.ru>, John Baldwin > <j...@freebsd.org>, freebsd-current@FreeBSD.org > Subject: Re: Destroy GPT partition scheme absolutely, how? > Message-ID: <cc9841a5-9815-2271-3546-e23d83d88...@freebsd.org> > Content-Type: text/plain; charset=utf-8 > >> On 28/09/2016 21:08, Andrey V. Elsukov wrote: >> This is very strange problem, how did you created MBR if you have not >> destroyed GPT? :) > > Using a tool that's not aware of GPT at all? > > -- > Andriy Gapon > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Sep 2016 22:39:02 +0000 > From: Glen Barber <g...@freebsd.org> > To: freebsd-current@FreeBSD.org, freebsd-sta...@freebsd.org > Cc: r...@freebsd.org, freebsd-annou...@freebsd.org > Subject: [HEADS-UP] 11.0-RELEASE status update > Message-ID: <20160928223902.gi88...@freebsd.org> > Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Dear FreeBSD Community: > > Although the FreeBSD 11.0-RELEASE has not yet been officially announced, > many have found images on the Project FTP mirrors. > > However, please be aware the final 11.0-RELEASE will be rebuilt and > republished on the Project mirrors as a result of a few last-minute > security fixes we feel are imperative to include in the final release. > > FreeBSD users already running 11.0-RELEASE will be given instructions on > how to safely upgrade systems to the 11.0-RELEASE-p1 in the final > announcement email. Those building from source code can obtain the > latest security updates from the releng/11.0 branch in Subversion: > > svn://svn.freebsd.org/base/releng/11.0 > > As the FreeBSD Project strives to provide the best possible product, the > Release Engineering team decided to build an updated release to include > the fixes. At present, we expect to have the final release available > Wednesday, October 3rd. If you have not yet downloaded 11.0-RELEASE, > please wait for the official release announcement. > > Thank you in advance for your patience waiting for 11.0-RELEASE, and of > course for understanding the reasons behind the updated release. > > Glen > On behalf of: re@ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJX7EaGAAoJEAMUWKVHj+KTtrgP/iaIozjqDQ2poH1i7J+BewmE > wov+vRcfmGmBvCFLxGPWDsXsYWYw8HCUNrloBesNlUZNe7BoFKliVrBp7KAN5YRE > R+l9AQU8u7UhYoKbM1epB28nDYdLH/veKMpkhyEr2mPglmRDJoJa1JL3xcnRXDj+ > yFeeCH5He/jH/ILiO8ChfY8e3aA+K/qMOSicVENW5M2kGs/q0m/i5UZK2LZ+gT7R > /eMl0USfW2B5LebHViv3a6GRArfTzBYZKYdoxXH7vUZ1zgb9CcEPfhYBxu41RMe3 > I+HquvqzWKPNwG3GhwqPmKfwQt4PHlATkZwddGosIgSmUZRhhD4eR0DWdXD6k/oS > iSi7QR8lef6ALcVTjt65JNqzPF/9eUJsZikcI0Ov6I0TkV2yzAGnUNneZQ6+22AS > //ZhqWkIu7w1hePJ+Af+SZJDzVdUWzVNiAyMmSFkfW3mFaidyhjR0OULnquG6kSS > kdPOdl/RwJzfP3wkFjt56I8YTyk7YQdwNEcEBQUlXlyZOC/NvUH5eebPJ1Va5UDV > q0FHFaYiATKvQyZUO3Ne9eLzBdYQhmaPSrvTGXrZw53hgShIBOEnwkJYiEGgySL3 > vCDro397boLkRL89HUXwuCFurZp/7g/V+I3w4X45y2/GpC/w7isPX/5YYJloETnR > VLGBedKpJbR/5LUJH8Bw > =t8IC > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 3 > Date: Wed, 28 Sep 2016 19:00:42 -0400 > From: Ultima <ultima1...@gmail.com> > To: freebsd-current@freebsd.org, freebsd...@freebsd.org > Subject: Re: zpool (online|replace|labelclear) issues, -f option also > failing > Message-ID: > <canj8om7aog_dy+7vcsbhuk9dcssr60tfzrjhaspzph9nj8v...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > >> Hi, > >> As a start you can use these in /boot/loader.conf to prevent the > confusion about gptid or disk_ident. I disabled gptid at my computer. But > if > I understand you would like to disable disk_ident. For ZFS it should > not matter what you use. > >> $ sysctl kern.geom.label >> kern.geom.label.disk_ident.enable: 1 >> kern.geom.label.gptid.enable: 0 >> kern.geom.label.gpt.enable: 1 >> kern.geom.label.ufs.enable: 1 >> kern.geom.label.ufsid.enable: 1 >> kern.geom.label.reiserfs.enable: 1 >> kern.geom.label.ntfs.enable: 1 >> kern.geom.label.msdosfs.enable: 1 >> kern.geom.label.iso9660.enable: 1 >> kern.geom.label.ext2fs.enable: 1 >> kern.geom.label.debug: 0 > > Thanks for that, this would probably work, but I don't understand why it > would change in the first place. I know that when it occurred it was > offline and I think it came back online when the system was rebooted. I'm > not positive tho. My guess is the scan found it on diskid before dptid, but > then why is gptid first for the others? I'm just going to replace the drive > with itself with gptid because I'v already wiped some data with dd. (even > tho a scrub would prob be good enough) > >> Further. Does ZFS see 14989197580381994958 and > gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 as the same disk? Zpool replace > also has an option to replace the disk 'with itself'. Just provide it one > parameter like this: >> # zpool replace tank 14989197580381994958 >> or >> # zpool replace tank gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 >> Does that help? > > I actually didn't realize this. However the same error persists. > > # zpool replace tank gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 > invalid vdev specification > the following errors must be manually repaired: > /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 is part of active pool > 'tank' > > # zpool replace -f tank /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 > invalid vdev specification > the following errors must be manually repaired: > /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 is part of active pool > 'tank' > >> Oh, while I read your mail again. You have 2 GB swap configured on the > disk so wiping 2MB at the start of the disk does not wipe the freebsd-zfs > metadata of the da14p2 partition. Try wiping 3GB from the start and end of > the disk and repartition it. > > > Thanks for pointing this out! It would probably help if the correct area on > the disk is wiped. Although it still seems that labelclear isn't up for the > task. I really think the force (-f) flag needs a bump in power (for both > replace and labelclear). Am I misunderstanding the use for the labelclear > command? It clears the label that zdb will show for possibly similar > circumstances that i'm encountering? > > # zpool labelclear -f gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 > /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 is a member (ACTIVE) of > pool "tank" > > Apologies, I failed to mention labelclear in my original post. It is > providing similar output as the replace command. > > As the device is offline from the pool. Is this the correct behavior to > show being an (ACTIVE) member of the pool? After wiping the correct area on > the disk via dd, the replace successfully added the drive back to the pool! > Thanks for pointing out my error. > > Thanks for taking a look at this Ronald and Allan! > > Ultima > > > ------------------------------ > > Message: 4 > Date: Wed, 28 Sep 2016 23:35:41 +0000 > From: Glen Barber <g...@freebsd.org> > To: freebsd-current@FreeBSD.org, freebsd-sta...@freebsd.org > Cc: r...@freebsd.org, freebsd-annou...@freebsd.org > Subject: [REVISED] [HEADS-UP] 11.0-RELEASE status update > Message-ID: <20160928233541.gj88...@freebsd.org> > Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Dear FreeBSD Community: > > [Corrected the date.] > > Although the FreeBSD 11.0-RELEASE has not yet been officially announced, > many have found images on the Project FTP mirrors. > > However, please be aware the final 11.0-RELEASE will be rebuilt and > republished on the Project mirrors as a result of a few last-minute > security fixes we feel are imperative to include in the final release. > > FreeBSD users already running 11.0-RELEASE will be given instructions on > how to safely upgrade systems to the 11.0-RELEASE-p1 in the final > announcement email. Those building from source code can obtain the > latest security updates from the releng/11.0 branch in Subversion: > > svn://svn.freebsd.org/base/releng/11.0 > > As the FreeBSD Project strives to provide the best possible product, the > Release Engineering team decided to build an updated release to include > the fixes. At present, we expect to have the final release available > Wednesday, October 5th. If you have not yet downloaded 11.0-RELEASE, > please wait for the official release announcement. > > Thank you in advance for your patience waiting for 11.0-RELEASE, and of > course for understanding the reasons behind the updated release. > > Glen > On behalf of: re@ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJX7FPNAAoJEAMUWKVHj+KT2joP/0/0AOYfTbFUgZeEUXlmdfew > 7nS31bQrBCXi7dgPicfSavdvDfqi4sgiw2/+HY3MxpfLWFJ/WNGveiwryGSiapkA > V3BJ9MCOZb3ZZTbp0JlwbRk1NyGg4ur0S4L6zD+MXuHE95Kts3m/ON8CiGtNUE+1 > rzE7Yr10tsU2Zu1Bvtv8rJa9SfLCln8k2FXtG0pxVWO+cK2xo6v84bjOJdExrB4t > eXYoMSoxIyZd1Kv2nLbL1mG7RrLQFVm4TrurMwALI39hVr+IWIvElmo6wndDhTly > XE8aMtpgUMp9b4PrQM+BgFVooR4ihFl0cslHfDuBGuiVJMQoa63agUfGAkclc9Na > nwiJiwcQStOdHcRAnZNBms9DTeNXDD0whq30JoY45kFRI74wjjqP8oNUCUWEd6e8 > n1puD2Zr2fqX0NziwtRg3Hy0EHM+9rQTEDtyHCG05sqTncyU7p6tkd49FfndXqaq > h/JkHTP1iyQYsq07GZzyhPA04e/i3N8Djwm+WoRgOlSrItJiPQ/FuqKV0cSERvPR > XZm3DPPRt04aOFe7XGrl2IHi+J6LZ5uwYEXiHFb+fPQMuROZ+IJC0Wu56HI2LHGL > f5wyPiNE1NJIeYLzIgk3UUrENaylsW4/NsgLFj6TW//24ekF2NR+Nk8u7mvoJuXq > vcLDdPW7mReqF13WLzh/ > =RcJK > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 5 > Date: Wed, 28 Sep 2016 23:15:12 -0400 (EDT) > From: Benjamin Kaduk <b...@freebsd.org> > To: freebsd-hack...@freebsd.org > Cc: freebsd-current@FreeBSD.org > Subject: Second Call for 2016Q3 quarterly status reports > Message-ID: <alpine.gso.1.10.1609282312120.5...@multics.mit.edu> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Dear FreeBSD Community > > Ten days remain in the submission period -- plase send in your entries for > the 2016Q3 report! > > More details quoted below. > > -Ben (on behalf of monthly@) > >> On Wed, 7 Sep 2016, Benjamin Kaduk wrote: >> >> Dear FreeBSD Community, >> >> The deadline for the next FreeBSD Quarterly Status update is October 7, >> 2016, for work done in July through September. >> >> Status report submissions do not have to be very long. They may be about >> anything happening in the FreeBSD project and community, and provide a >> great way to inform FreeBSD users and developers about what you're working >> on. Submission of reports is not restricted to committers. Anyone doing >> anything interesting and FreeBSD-related can -- and should -- write one! >> >> The preferred and easiest submission method is to use the XML generator >> [1] with the results emailed to the status report team at monthly at >> FreeBSD.org . There is also an XML template [2] which can be filled out >> manually and attached if preferred. For the expected content and style, >> please study our guidelines on how to write a good status report [3]. >> You can also review previous issues [4][5] for ideas on the style and >> format. >> >> We are looking forward to all of your 2016Q3 reports! >> >> Thanks, >> >> Ben (on behalf of monthly@) >> >> [1] https://www.FreeBSD.org/cgi/monthly.cgi >> [2] https://www.FreeBSD.org/news/status/report-sample.xml >> [3] https://www.FreeBSD.org/news/status/howto.html >> [4] https://www.FreeBSD.org/news/status/report-2016-01-2016-03.html >> [4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html >> >> > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > > ------------------------------ > > End of freebsd-current Digest, Vol 675, Issue 6 > *********************************************** _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
