Post on freebsd.org
Hi, How are you? Current working for a client who is interested in buying paid advertising articles with links on good business, news , casino forex and other relevant sites. So, if you are interested in selling article placement on sites so please send me your websites URL with price to have an article with my website links. Looking for a good business relationship. Other than that being a freelancer The provided services by me are: ·Content writing, ·Web Design/HTML/Animation ·SEO, SMM, ·Media Buying, ·Facebook, ·Facebook likes, ·Twitter working, I have 10 years experience in this field. Currently I am searching for some more clients. Please let me know if you are interested in my services. Looking forward to hearing from you. Thanks And Regards Shweta Seo, Smo, Content Writing And Web Designing Service Provider Contact: Skpye: Seo1seo1 Contact Number: +919993036692 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
CFT: FreeBSD Package Base
FreeBSD Community, I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 13-current using "TrueOS-inspired" packaged base. These are stock FreeBSD images which will allow users to perform all updating via the 'pkg' command directly. Rather than trying to answer all questions in this announcement, we've created a FAQ page with more details. Please refer to this page, and let us know if you have additional questions that we can include on that page going forward. Additionally, I will be hosting a Package Base working group at BSDCan 2019, and welcome user and developer attendance to discuss this and other ongoing package work: https://wiki.freebsd.org/DevSummit/201905/PackageBase FAQ - https://trueos.github.io/pkgbase-docs/ Download Links - FreeBSD 12-STABLE: https://pkg.trueos.org/iso/freebsd12-pkgbase/ FreeBSD 13-CURRENT: https://pkg.trueos.org/iso/freebsd-pkgbase/ -- Kris Moore Vice President of Engineering iXsystems, Inc Ph: (408) 943-4100 Ph: (408) 943-4101 The Groundbreaking TrueNAS M-Series - Enterprise Storage & Servers Driven By Open Source ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Concern: ZFS Mirror issues (12.STABLE and firmware 19 .v. 20) [[UPDATE w/more tests]]
On 4/20/2019 15:56, Steven Hartland wrote: > Thanks for extra info, the next question would be have you eliminated > that corruption exists before the disk is removed? > > Would be interesting to add a zpool scrub to confirm this isn't the > case before the disk removal is attempted. > > Regards > Steve > > On 20/04/2019 18:35, Karl Denninger wrote: >> >> On 4/20/2019 10:50, Steven Hartland wrote: >>> Have you eliminated geli as possible source? >> No; I could conceivably do so by re-creating another backup volume >> set without geli-encrypting the drives, but I do not have an extra >> set of drives of the capacity required laying around to do that. I >> would have to do it with lower-capacity disks, which I can attempt if >> you think it would help. I *do* have open slots in the drive >> backplane to set up a second "test" unit of this sort. For reasons >> below it will take at least a couple of weeks to get good data on >> whether the problem exists without geli, however. >> Ok, following up on this with more data First step taken was to create a *second* backup pool (I have the backplane slots open, fortunately) with three different disks but *no encryption.* I ran both side-by-side for several days, with the *unencrypted* one operating with one disk detached and offline (pulled physically) just as I do normally. Then I swapped the two using the same paradigm. The difference was *dramatic* -- the resilver did *not* scan the entire disk; it only copied the changed blocks and was finished FAST. A subsequent scrub came up 100% clean. Next I put THOSE disks in the vault (so as to make sure I didn't get hosed if something went wrong) and re-initialized the pool in question, leaving only the "geli" alone (in other words I zpool destroy'd the pool and then re-created it with all three disks connected and geli-attached.) The purpose for doing this was to eliminate the possibility of old corruption somewhere, or some sort of problem with multiple, spanning years, in-place "zpool upgrade" commands. Then I ran a base backup to initialize all three volumes, detached one and yanked it out of the backplane, as would be the usual, leaving the other two online and operating. I ran backups as usual for most of last week after doing this, with the 61.eli and 62-1.eli volumes online, and 62-2 physically out of the backplane. Today I swapped them again as I usually do (e.g. offline 62.1, geli detach, camcontrol standby and then yank it -- then insert the 62-2 volume, geli attach and zpool online) and this is happening: [\u@NewFS /home/karl]# zpool status backup pool: backup state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sun Apr 28 12:57:47 2019 2.48T scanned at 202M/s, 1.89T issued at 154M/s, 3.27T total 1.89T resilvered, 57.70% done, 0 days 02:37:14 to go config: NAME STATE READ WRITE CKSUM backup DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 gpt/backup61.eli ONLINE 0 0 0 11295390187305954877 OFFLINE 0 0 0 was /dev/gpt/backup62-1.eli gpt/backup62-2.eli ONLINE 0 0 0 errors: No known data errors The "3.27T" number is accurate (by "zpool list") for the space in use. There is not a snowball's chance in Hades that anywhere near 1.89T of that data (thus far, and it ain't done as you can see!) was modified between when all three disks were online and when the 62-2.eli volume was swapped back in for 62.1.eli. No possible way. Maybe some 100-200Gb of data has been touched across the backed-up filesystems in the last three-ish days but there's just flat-out no way it's more than that; this would imply an entropy of well over 50% of the writeable data on this box in less than a week! That's NOT possible. Further it's not 100%; it shows 2.48T scanned but 1.89T actually written to the other drive. So something is definitely foooged here and it does appear that geli is involved in it. Whatever is foooging zfs the resilver process thinks it has to recopy MOST (but not all!) of the blocks in use, it appears, from the 61.eli volume to the 62-2.eli volume. The question is what would lead ZFS to think it has to do that -- it clearly DOES NOT as a *much* smaller percentage of the total TXG set on 61.eli was modified while 62-2.eli was offline and 62.1.eli was online. Again I note that on 11.1 and previous this resilver was a rapid operation; whatever was actually changed got copied but the system never copied *nearly everything* on a resilver, including data that had not been changed at all, on a mirrored set. Obviously on a Raidz volume you have to go through the entire data structure because parity has to be recomputed
Re: CFT: FreeBSD Package Base
On Apr 28, 2019, at 3:52 PM, wrote: FreeBSD Community, I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 13-current using "TrueOS-inspired" packaged base. These are stock FreeBSD images which will allow users to perform all updating via the 'pkg' command directly. Rather than trying to answer all questions in this announcement, we've created a FAQ page with more details. Please refer to this page, and let us know if you have additional questions that we can include on that page going forward. I currently keep my FreeBSD/arm and FreeBSD/arm64 systems up to date via PkgBase in FreeBSD 12. It works well for me (crossbuilding and hosting the PkgBase repository on a FreeBSD/amd64 system). What is the difference between the above CFT-created PkgBase and one created via "make packages" using the native build system (https://wiki.freebsd.org/PkgBase)? Looking at the FAQ you linked (https://trueos.github.io/pkgbase-docs/), it seems the above CFT system is less granular than the one currently produced via the in-tree "make packages" (which could be a good thing from a simplicity standpoint). Is there anything else? Is the above CFT-produced packages the system that will ultimately become the way packaged base is produced in FreeBSD 13.0-RELEASE, or is it just an alternative you want people to try out and evaluate? I guess I'm not clear what "TrueOS-inspired" packaged base means. :-) Cheers, Paul. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: CFT: FreeBSD Package Base
Paul, We also started with the current in-base package system, but ultimately abandonded it for a variety of reasons that made unsuitable for us to use in FreeNAS. Some of those were the chaos with having so many hundreds of packages, and the issues when you started combining them with various WITH_*/WITHOUT_* flags. This system doesn't touch the FreeBSD build and instead allows building source / packages directly from ports and poudriere. (Keeping base and ports in sync far easier) "TrueOS-inspired" was just reference to the fact we've been incubating this in TrueOS for about 6 months now to shake out some issues and test our designs. The hope is to envigorate the FreeBSD project to have a discussion about getting real base packages in a release sooner rather than later, especially since current efforts seem somewhat stalled. We're hoping the design we're using here is compelling enough that it can be adopted in FreeBSD. Some cool asides, being able to 'pkg install src' and have /usr/src be kept in sync with the current packages is super handy. 😉 -- Kris Moore Vice President of Engineering iXsystems, Inc Ph: (408) 943-4100 Ph: (408) 943-4101 The Groundbreaking TrueNAS M-Series - Enterprise Storage & Servers Driven By Open Source -Original Message- From: Paul Mather Sent: Sunday, April 28, 2019 6:22 PM To: k...@ixsystems.com Cc: FreeBSD Stable Subject: Re: CFT: FreeBSD Package Base On Apr 28, 2019, at 3:52 PM, wrote: > FreeBSD Community, > > > > I'm pleased to announce a CFT for builds of FreeBSD 12-stable and > 13-current using "TrueOS-inspired" packaged base. These are stock > FreeBSD images which will allow users to perform all updating via the > 'pkg' command directly. > Rather than trying to answer all questions in this announcement, we've > created a FAQ page with more details. Please refer to this page, and > let us know if you have additional questions that we can include on > that page going forward. I currently keep my FreeBSD/arm and FreeBSD/arm64 systems up to date via PkgBase in FreeBSD 12. It works well for me (crossbuilding and hosting the PkgBase repository on a FreeBSD/amd64 system). What is the difference between the above CFT-created PkgBase and one created via "make packages" using the native build system (https://wiki.freebsd.org/PkgBase)? Looking at the FAQ you linked (https://trueos.github.io/pkgbase-docs/), it seems the above CFT system is less granular than the one currently produced via the in-tree "make packages" (which could be a good thing from a simplicity standpoint). Is there anything else? Is the above CFT-produced packages the system that will ultimately become the way packaged base is produced in FreeBSD 13.0-RELEASE, or is it just an alternative you want people to try out and evaluate? I guess I'm not clear what "TrueOS-inspired" packaged base means. :-) Cheers, Paul. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CFT: FreeBSD Package Base
> On Apr 28, 2019, at 6:21 PM, Paul Mather wrote: > > On Apr 28, 2019, at 3:52 PM, wrote: > >> FreeBSD Community, >> >> >> >> I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 13-current >> using "TrueOS-inspired" packaged base. These are stock FreeBSD images which >> will allow users to perform all updating via the 'pkg' command directly. >> Rather than trying to answer all questions in this announcement, we've >> created a FAQ page with more details. Please refer to this page, and let us >> know if you have additional questions that we can include on that page going >> forward. > > > I currently keep my FreeBSD/arm and FreeBSD/arm64 systems up to date via > PkgBase in FreeBSD 12. It works well for me (crossbuilding and hosting the > PkgBase repository on a FreeBSD/amd64 system). > > What is the difference between the above CFT-created PkgBase and one created > via "make packages" using the native build system > (https://wiki.freebsd.org/PkgBase)? Looking at the FAQ you linked > (https://trueos.github.io/pkgbase-docs/), it seems the above CFT system is > less granular than the one currently produced via the in-tree "make packages" > (which could be a good thing from a simplicity standpoint). Is there > anything else? > > Is the above CFT-produced packages the system that will ultimately become the > way packaged base is produced in FreeBSD 13.0-RELEASE, or is it just an > alternative you want people to try out and evaluate? I guess I'm not clear > what "TrueOS-inspired" packaged base means. :-) What are the plans to get rid of the hellscape known as “mergemaster”? Is there anything exciting and new there either in base or any of the ixSystems projects? Thanks, Charles > > Cheers, > > Paul. > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: CFT: FreeBSD Package Base
Its on the agenda for next months Working Group. That and tooling to help migrating to pkg base and keeping /etc files intact. -- Kris Moore Vice President of Engineering iXsystems, Inc Ph: (408) 943-4100 Ph: (408) 943-4101 The Groundbreaking TrueNAS M-Series - Enterprise Storage & Servers Driven By Open Source -Original Message- From: Charles Sprickman Sent: Sunday, April 28, 2019 9:30 PM To: Paul Mather Cc: k...@ixsystems.com; FreeBSD Stable Subject: Re: CFT: FreeBSD Package Base > On Apr 28, 2019, at 6:21 PM, Paul Mather wrote: > > On Apr 28, 2019, at 3:52 PM, wrote: > >> FreeBSD Community, >> >> >> >> I'm pleased to announce a CFT for builds of FreeBSD 12-stable and >> 13-current using "TrueOS-inspired" packaged base. These are stock >> FreeBSD images which will allow users to perform all updating via the 'pkg' >> command directly. >> Rather than trying to answer all questions in this announcement, >> we've created a FAQ page with more details. Please refer to this >> page, and let us know if you have additional questions that we can >> include on that page going forward. > > > I currently keep my FreeBSD/arm and FreeBSD/arm64 systems up to date via > PkgBase in FreeBSD 12. It works well for me (crossbuilding and hosting the > PkgBase repository on a FreeBSD/amd64 system). > > What is the difference between the above CFT-created PkgBase and one created > via "make packages" using the native build system > (https://wiki.freebsd.org/PkgBase)? Looking at the FAQ you linked > (https://trueos.github.io/pkgbase-docs/), it seems the above CFT system is > less granular than the one currently produced via the in-tree "make packages" > (which could be a good thing from a simplicity standpoint). Is there > anything else? > > Is the above CFT-produced packages the system that will ultimately > become the way packaged base is produced in FreeBSD 13.0-RELEASE, or > is it just an alternative you want people to try out and evaluate? I > guess I'm not clear what "TrueOS-inspired" packaged base means. :-) What are the plans to get rid of the hellscape known as “mergemaster”? Is there anything exciting and new there either in base or any of the ixSystems projects? Thanks, Charles > > Cheers, > > Paul. > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
