From owner-freebsd-questions@freebsd.org Sun Sep 20 11:57:17 2015 Return-Path: Delivered-To: freebsd-questions@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 648289CEEB7 for ; Sun, 20 Sep 2015 11:57:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA6101CF5 for ; Sun, 20 Sep 2015 11:57:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-125-111.dynamic.qsc.de [92.195.125.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 9745F24F07; Sun, 20 Sep 2015 13:57:12 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t8KBvBhC002091; Sun, 20 Sep 2015 13:57:11 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 20 Sep 2015 13:57:11 +0200 From: Polytropon To: Slawa Olhovchenkov Cc: freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds Message-Id: <20150920135711.381d1c02.freebsd@edvax.de> In-Reply-To: <20150919220222.GE21849@zxy.spb.ru> References: <20150918134804.GU3158@zxy.spb.ru> <86oagzwf8j.fsf@nine.des.no> <20150919125023.GA21849@zxy.spb.ru> <20150919151517.739ab70a.freebsd@edvax.de> <20150919133248.GB21849@zxy.spb.ru> <20150919184712.4d26f3f9.freebsd@edvax.de> <20150919172839.GC21849@zxy.spb.ru> <20150919204745.eeb62abd.freebsd@edvax.de> <20150919193105.GD21849@zxy.spb.ru> <20150919220658.07d652f7.freebsd@edvax.de> <20150919220222.GE21849@zxy.spb.ru> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 11:57:17 -0000 On Sun, 20 Sep 2015 01:02:22 +0300, Slawa Olhovchenkov wrote: > On Sat, Sep 19, 2015 at 10:06:58PM +0200, Polytropon wrote: > > > On Sat, 19 Sep 2015 22:31:05 +0300, Slawa Olhovchenkov wrote: > > > On Sat, Sep 19, 2015 at 08:47:45PM +0200, Polytropon wrote: > > > > > > > > > In the end, it might look like there are few additional packages > > > > > > that will be installed: sys_bin, sys_src, sys_ports and so on. > > > > > > An update you perform with freebsd-update will then be an update > > > > > > on the sys_* packages with pkg, leading to a binarily upgraded > > > > > > operating system. You then _can_ upgrade your ports collection, > > > > > > or you can leave it as is. This is the advantage of FreeBSD: > > > > > > The OS and the additionally installed (3rd party) software are > > > > > > beging dealt with independently. > > > > > > > > > > > > And this is good. :-) > > > > > > > > > > I am don't see advantage of this. > > > > > What's part of systeam I am don't need to install? > > > > > > > > The components won't be that separated. No direct "part of > > > > the system" will exist, like, "do I install sh, or can I > > > > live without it?"; I'd rather assume that there are only > > > > few packages that result in a fully functional (!) operating > > > > system. Still I hope the pkg approach will give you the > > > > flexibility of src.conf - to omit components you _really_ > > > > don't need, and where you _intend_ to leave them out. > > > > > > # man src.conf | col -b | grep -c WITH > > > 227 > > > > > > and many items can't be do as packages. > > > > Correct. I think the approach with pkg for the OS will be > > the same as with most packages: A predefined set of options > > will be the default, from which the packages are built. If > > you _intend_ to use nonstandard options, use the source Luke > > and compile the things yourself. You simply cannot maintain > > 2^227+ packages. :-) > > I am ask about breaking base system to packages. > I am point to some troubles. > What you propolsal? As I mentioned, I'm not in charge of devisions. :-) However, I'd suggest only very few packages, representing the "sane defaults approach" of kernel.txz, base.txz, src.txz and ports.txz (but as pkg-compatible packages), and for everything else, building from source will be done as it is now. Having too many (sub)packages or variations (base with or without lpr, with or without sendmail, with or without crypto, ...) could be problematic. I'm not sure the approach of "flavors" as it is planned for ports (now that they require staging) can be a solution. Remeber that my days of OS development are long gone, and I'm not involved with the pkg project - I'm just a user. :-) > > > > > src? also svn. > > > > > > > > When you simply want the RELEASE sources, installing svn and > > > > having it run is probably more work than simply downloading > > > > src.txz and uncompressing it into /usr/src - again, this is > > > > what pkg would do. > > > > > > Many imporvement happened between releases. > > > If you accpeted RELEASE -- you mostly accpeted GENERIC kernel and > > > don't need source anyway. > > > > Correct - except you _intendedly_ want a non-GENERIC kernel. > > Now in GENERIC kernel included NETMAP and IPSEC. > This is cover 99% cases (when RELEASE is acceptable). GENERIC works fine for most applications, and there's KLD loadable modules for most "extended needs". People requiring a streamlined or even "minimalized" kernel will build from source anyway. > > > > The OS's pkg binary is just a bootstrap loader for the real > > > > one installed as a package. It's possible that the same > > > > approach will be kept when pkg manages the OS components. > > > > > > And I am talk about imposible loading real one. > > > > Without network connection - a big problem. But what's the > > I am talk about updating outdated system, w/o fresh pkg (beacuse you > version is not maintaned some years) and requiment fresh pkg (because > repository with new OS incopatible with you pkg). You already have this problem now, for example, when you're coming from v8 and want to get to v10. Sure, source updates through the major versions is possible, _then_ current pkg is added, databases are transitioned, and everything needs to be reinstalled. In such a case, a fresh installation often is the easier way. (But it really depends on the system in question.) > > use of a binary upgrading tool without being able to reach > > the remote source required? :-) > > For example -- upgrade in isolated network, from CD/USB. That would require fetching all required data with a "connected system", and pkg's or freebsd-update's ability to work with a locally mounted source for operations. In case this source is complete, it should be possible (even though probably a bit invonvenient). > > > > > Next, how to upgrade system? kernel first? ok. for this case kernel > > > > > can't be depend from userland packages. How to upgrade to > > > > > correspondend userland packages? > > > > > > > > I'd say that a "pkg upgrade" of the userland and the kernel > > > > have to go hand in hand, as it is suggested today, because > > > > kernel and world have to be in sync. The operation will be > > > > similar to what you do today with "freebsd-update upgrade". > > > > Of course this requires a good coupling between the pkg port > > > > and the (updated) OS. > > > > > > Upgrading kernel and userland don't match pkg ideology, IMHO. > > > > That's a possible and valid way to see things: pkg is the > > successor of the old pkg_* tools, which dealt with ports, > > not with the OS. > > I think you talk about maintaing base system as .txz pkg? No, I'm just mentionin the compressed archives for comparison. There aren't hundreds of such archives, but only _few_ that represent the system's components (kernel - the system's kernel; base - the OS itself; src - the OS's sources; ports - the ports collection tree). I could imagine that pkg-compatible packages would be organized similarly, instead of many (kernel, init, sh, ls, cp, dd, ifconfig, df, ee, cc, ... you get the idea); if I wanted _that_, I'd use Linux instead. ;-) > > > > If you're worried here, you should have a look at Boot > > > > Environments (as known from Solaris): FreeBSD + ZFS + beadm > > > > is a very good solution for preparing, testing, and maybe > > > > rolling back upgrades. > > > > > > Not now. bsdinstall now use very bad partioning for BE. > > > > When dealing with ZFS, I prefer not to deal with bsdinstall > > and its "sane defaults"... it makes life easier. :-) > > To many manual works, to many studing. > I think standart install must use best practics. That's what I meant with "sane defaults" - they just don't apply everywhere, there is no "one size fits all" set of settings. If you learned the shell commands, in my experience it's far easier to use them. At some point, you'll probably write your own installer script to automate things. > > > > > What about -current? > > > > > > > > The -CURRENT (or -HEAD) development branch will surely not > > > > be available via pkg upgrades. They are, as today, done from > > > > the source. > > > > > > Shit, you talk about unification and SUDDENLY we got two, incopatible > > > way -- for current and fro stable. > > > > It has always been that way: -CURRENT (or -HEAD) is a development > > branch. It's not stable. There are times where the -CURRENT > > version crashes right away. Sometimes, it won't even build! Update > > some hours later, and it works again. Experimental features may > > be introduced in -CURRENT, and two weeks later, those features > > have been removed. There sometimes are (binary) snapshots. Then, > > -STABLE is the branch where "refinement" takes place: It is the > > branch from which -RELEASE will be "distilled". > > How you plan to testing -STABLE if -CURRENT building in differnet way? > Eating your own dog food. They build the same way, just _updating_ them (via source update) is different then on -RELEASE and -RELEASE-pN (binary updates are possible). You can find more information here: https://www.freebsd.org/doc/handbook/current-stable.html Note that those branches aren't made specifically with novice users in mind, and that's why the ways of using (testing) them don't look much comfortable. But as soon as you're familiar with how to get sources updated and build stuff from source, it's easy. Most users will use -RELEASE and -RELEASE-pN (updated with freebsd-update), only few require -STABLE to run "bleeding edge" ports that require "hot" features. > > The branches freebsd-update can follow are -RELEASE and the > > and freebsd-update is gone, right? Not yet. As I said, I read about _plans_ to obsolete it in the future. Currently it works well for supported systems - those versions from its introduction onward. > > errata branch -RELEASE-pN (where N is the patchlevel). For > > following -STABLE or -HEAD, you _have to_ use the source Luke > > (except for the snapshots mentioned). > > and no stadrart way to use snapshots to update, yes? You can download compressed archives, for example here: ftp://ftp.freebsd.org/pub/FreeBSD/development/tarballs/ This is also a way to get snapshots: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/10.2-STABLE ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-CURRENT Even installation images are provided: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ This is a _development_ task which doesn't have an "easy" standardized way for novice users, because this is not a typical task for novice users. :-) > > > > > userland first? ok. Got new libs with missing syscals and we can't run > > > > > any program. > > > > > > > > Dynamic linking to the system's most essential library should > > > > not break things. Stable interfaces are very important here, > > > > so the upgrader won't be so stupid to shoot his own foot. :-) > > > > > > I am talk about reality. Staticaly linked svn, build on 9.x, don't run > > > on 6.x system by missinc syscal. This is fact. As result I am build > > > svn on 6.x system in VirtualBox. > > > > Of course, because v6 and v9 are not using the same ABI (and API). > > This is only guaranteed on -STABLE. If you need to run v6 software > > on a v9 system, the compat6x-i386 port, for example, can be used > > to privode "downward compatibility"; "upward compatibility" requires > > a time machine. :-) > > You propolsal requires a time machine, because for upgrading outdated > system requires run pkg from new OS on outdated OS. Dealing with non-supported OS versions always is kind of magic. ;-) > > > > Please keep in mind that I'm just mentioning my own thoughts > > > > here. I'm not part of the pkg development team. If you have > > > > specific questions regarding the use and implementation of > > > > the upcoming OS updating mechanism, you should contact the > > > > designated maintainers. > > > > > > Who maintained this? > > > > Check out "man pkg": "Please direct questions and issues to the > > pkg@FreeBSD.org mailing list." as well as its "AUTHORS AND > > CONTRIBUTORS" section. > > > > Also see the list of authors here: > > > > https://github.com/freebsd/pkg/blob/master/AUTHORS > > > > They might know (much better than me) how things are going to be > > developed, and what plans they have for the future. > > I am ask about maintainers of breaking OS to pkg. As I said, try to direct your questions to the pkg maintainers, and maybe you can also address the freebsd-current@ mailing list: http://lists.freebsd.org/mailman/listinfo/ They should be more competent in discussing "what's cooking" for the upcoming versions of FreeBSD. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Sep 20 12:51:55 2015 Return-Path: Delivered-To: freebsd-questions@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 E197EA05F42 for ; Sun, 20 Sep 2015 12:51:54 +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 97DB51767 for ; Sun, 20 Sep 2015 12:51:54 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZddTN-000CSY-VN; Sun, 20 Sep 2015 15:12:02 +0300 Date: Sun, 20 Sep 2015 15:12:01 +0300 From: Slawa Olhovchenkov To: Polytropon Cc: freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds Message-ID: <20150920121201.GF21849@zxy.spb.ru> References: <20150919125023.GA21849@zxy.spb.ru> <20150919151517.739ab70a.freebsd@edvax.de> <20150919133248.GB21849@zxy.spb.ru> <20150919184712.4d26f3f9.freebsd@edvax.de> <20150919172839.GC21849@zxy.spb.ru> <20150919204745.eeb62abd.freebsd@edvax.de> <20150919193105.GD21849@zxy.spb.ru> <20150919220658.07d652f7.freebsd@edvax.de> <20150919220222.GE21849@zxy.spb.ru> <20150920135711.381d1c02.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150920135711.381d1c02.freebsd@edvax.de> User-Agent: Mutt/1.5.23 (2014-03-12) 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-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 12:51:55 -0000 On Sun, Sep 20, 2015 at 01:57:11PM +0200, Polytropon wrote: > > > > > The OS's pkg binary is just a bootstrap loader for the real > > > > > one installed as a package. It's possible that the same > > > > > approach will be kept when pkg manages the OS components. > > > > > > > > And I am talk about imposible loading real one. > > > > > > Without network connection - a big problem. But what's the > > > > I am talk about updating outdated system, w/o fresh pkg (beacuse you > > version is not maintaned some years) and requiment fresh pkg (because > > repository with new OS incopatible with you pkg). > > You already have this problem now, for example, when you're > coming from v8 and want to get to v10. Sure, source updates No, two weeks ago I am do this, absolutly no problems. Just work. > through the major versions is possible, _then_ current pkg > is added, databases are transitioned, and everything needs > to be reinstalled. In such a case, a fresh installation often > is the easier way. (But it really depends on the system in > question.) Most of my systems placed in many kilometers from me and often don't have KVM/etc. Fresh installation is not a way. > > > > > If you're worried here, you should have a look at Boot > > > > > Environments (as known from Solaris): FreeBSD + ZFS + beadm > > > > > is a very good solution for preparing, testing, and maybe > > > > > rolling back upgrades. > > > > > > > > Not now. bsdinstall now use very bad partioning for BE. > > > > > > When dealing with ZFS, I prefer not to deal with bsdinstall > > > and its "sane defaults"... it makes life easier. :-) > > > > To many manual works, to many studing. > > I think standart install must use best practics. > > That's what I meant with "sane defaults" - they just don't > apply everywhere, there is no "one size fits all" set of > settings. If you learned the shell commands, in my experience > it's far easier to use them. At some point, you'll probably > write your own installer script to automate things. I am preffer to use already knowledge bestpractics. Also, using shell at install time is noy cute. > > > > > > What about -current? > > > > > > > > > > The -CURRENT (or -HEAD) development branch will surely not > > > > > be available via pkg upgrades. They are, as today, done from > > > > > the source. > > > > > > > > Shit, you talk about unification and SUDDENLY we got two, incopatible > > > > way -- for current and fro stable. > > > > > > It has always been that way: -CURRENT (or -HEAD) is a development > > > branch. It's not stable. There are times where the -CURRENT > > > version crashes right away. Sometimes, it won't even build! Update > > > some hours later, and it works again. Experimental features may > > > be introduced in -CURRENT, and two weeks later, those features > > > have been removed. There sometimes are (binary) snapshots. Then, > > > -STABLE is the branch where "refinement" takes place: It is the > > > branch from which -RELEASE will be "distilled". > > > > How you plan to testing -STABLE if -CURRENT building in differnet way? > > Eating your own dog food. > > They build the same way, just _updating_ them (via source update) > is different then on -RELEASE and -RELEASE-pN (binary updates are > possible). _updating_ also need testing. May be you miss some bugs 'installworld' time, breaking -current? > > > The branches freebsd-update can follow are -RELEASE and the > > > > and freebsd-update is gone, right? > > Not yet. As I said, I read about _plans_ to obsolete it in the > future. Currently it works well for supported systems - those > versions from its introduction onward. > > > > > > errata branch -RELEASE-pN (where N is the patchlevel). For > > > following -STABLE or -HEAD, you _have to_ use the source Luke > > > (except for the snapshots mentioned). > > > > and no stadrart way to use snapshots to update, yes? > > You can download compressed archives, for example here: > > ftp://ftp.freebsd.org/pub/FreeBSD/development/tarballs/ > > This is also a way to get snapshots: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/10.2-STABLE > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-CURRENT OK. download. OK. But downloading don't updated system. And just untar archive break working system. Yes, I am know how untar w/o breaking, but no standart script in base system for do this. And no standart script in base system for apllay this archive direct to etcupdate. > Even installation images are provided: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ > > This is a _development_ task which doesn't have an "easy" > standardized way for novice users, because this is not a > typical task for novice users. :-) 50 years ago unix install is not a typical task for novice users. > > > > > > userland first? ok. Got new libs with missing syscals and we can't run > > > > > > any program. > > > > > > > > > > Dynamic linking to the system's most essential library should > > > > > not break things. Stable interfaces are very important here, > > > > > so the upgrader won't be so stupid to shoot his own foot. :-) > > > > > > > > I am talk about reality. Staticaly linked svn, build on 9.x, don't run > > > > on 6.x system by missinc syscal. This is fact. As result I am build > > > > svn on 6.x system in VirtualBox. > > > > > > Of course, because v6 and v9 are not using the same ABI (and API). > > > This is only guaranteed on -STABLE. If you need to run v6 software > > > on a v9 system, the compat6x-i386 port, for example, can be used > > > to privode "downward compatibility"; "upward compatibility" requires > > > a time machine. :-) > > > > You propolsal requires a time machine, because for upgrading outdated > > system requires run pkg from new OS on outdated OS. > > Dealing with non-supported OS versions always is kind of magic. ;-) Currently no magic required. From owner-freebsd-questions@freebsd.org Sun Sep 20 13:57:44 2015 Return-Path: Delivered-To: freebsd-questions@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 02ED79CF1F0 for ; Sun, 20 Sep 2015 13:57:44 +0000 (UTC) (envelope-from bah@bananmonarki.se) 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 D86E6112B for ; Sun, 20 Sep 2015 13:57:43 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: by mailman.ysv.freebsd.org (Postfix) id D5E9E9CF1EF; Sun, 20 Sep 2015 13:57:43 +0000 (UTC) Delivered-To: questions@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 D4A129CF1EE for ; Sun, 20 Sep 2015 13:57:43 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48F10112A for ; Sun, 20 Sep 2015 13:57:40 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from kw.news4all.se (testbox.usenet4all.se [10.0.0.3]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id t8KDvOGm070911; Sun, 20 Sep 2015 15:57:24 +0200 (CEST) (envelope-from bah@bananmonarki.se) Subject: Re: 10.2 graphics problem To: Polytropon , Glenn English References: <8F541F88-2EAE-434C-B52C-43A744F54ADD@slsware.net> <55FADDE7.9000702@bananmonarki.se> <0F355724-42C6-4DB4-A470-7AC8D7667CEA@slsware.net> <1442592952.3015.19.camel@michaeleichorn.com> <55FC3F90.3090905@bananmonarki.se> <1F197AA4-CE10-4195-B0D5-028C30036CAA@slsware.net> <20150919130100.3e1b013a.freebsd@edvax.de> Cc: freebsdQuestions From: Bernt Hansson Message-ID: <55FEBB44.2000309@bananmonarki.se> Date: Sun, 20 Sep 2015 15:57:24 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150919130100.3e1b013a.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 13:57:44 -0000 On 2015-09-19 13:01, Polytropon wrote: > On Fri, 18 Sep 2015 15:44:33 -0600, Glenn English wrote: >> >> On Sep 18, 2015, Bernt Hansson, and several others, wrote: >> >>>>> There is a second edition of the Handbook, but it is also pretty old >>>>> now. >> >> Yeah, I've got that one too. No mention of ZFS, but very little >> on floppies, and nothing I've come across yet on dialup or SLIP :-) > > And tape? What about tape? Floppy tape? :-) Tape is floppy. > From owner-freebsd-questions@freebsd.org Sun Sep 20 14:14:44 2015 Return-Path: Delivered-To: freebsd-questions@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 6431E9CFBF2 for ; Sun, 20 Sep 2015 14:14:44 +0000 (UTC) (envelope-from freebsd@edvax.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 431071A18 for ; Sun, 20 Sep 2015 14:14:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: by mailman.ysv.freebsd.org (Postfix) id 4068D9CFBEA; Sun, 20 Sep 2015 14:14:44 +0000 (UTC) Delivered-To: questions@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 400BE9CFBE9 for ; Sun, 20 Sep 2015 14:14:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F11801A15 for ; Sun, 20 Sep 2015 14:14:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-125-111.dynamic.qsc.de [92.195.125.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id F15243CC75; Sun, 20 Sep 2015 16:14:34 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t8KEEYPK002489; Sun, 20 Sep 2015 16:14:34 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 20 Sep 2015 16:14:34 +0200 From: Polytropon To: Bernt Hansson Cc: freebsdQuestions Subject: Re: 10.2 graphics problem Message-Id: <20150920161434.97a049bb.freebsd@edvax.de> In-Reply-To: <55FEBB44.2000309@bananmonarki.se> References: <8F541F88-2EAE-434C-B52C-43A744F54ADD@slsware.net> <55FADDE7.9000702@bananmonarki.se> <0F355724-42C6-4DB4-A470-7AC8D7667CEA@slsware.net> <1442592952.3015.19.camel@michaeleichorn.com> <55FC3F90.3090905@bananmonarki.se> <1F197AA4-CE10-4195-B0D5-028C30036CAA@slsware.net> <20150919130100.3e1b013a.freebsd@edvax.de> <55FEBB44.2000309@bananmonarki.se> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 14:14:44 -0000 On Sun, 20 Sep 2015 15:57:24 +0200, Bernt Hansson wrote: > > > On 2015-09-19 13:01, Polytropon wrote: > > On Fri, 18 Sep 2015 15:44:33 -0600, Glenn English wrote: > >> > >> On Sep 18, 2015, Bernt Hansson, and several others, wrote: > >> > >>>>> There is a second edition of the Handbook, but it is also pretty old > >>>>> now. > >> > >> Yeah, I've got that one too. No mention of ZFS, but very little > >> on floppies, and nothing I've come across yet on dialup or SLIP :-) > > > > And tape? What about tape? Floppy tape? :-) > > Tape is floppy. No no, a tape drive connected to a floppy controller - "floppy tape", memories of /dev/rft0... now you must ask: "What's a floppy controller?" Observe: The controller is _not_ floppy. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Sep 20 14:32:44 2015 Return-Path: Delivered-To: freebsd-questions@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 E7879A054A9 for ; Sun, 20 Sep 2015 14:32:44 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::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 A94F11454 for ; Sun, 20 Sep 2015 14:32:44 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by igbkq10 with SMTP id kq10so63774413igb.0 for ; Sun, 20 Sep 2015 07:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=GWHaA/2yf9PD+wBualc4xGmTPDQaZ+Ij+o9hMXyWFeA=; b=th3BviFTJ3jrp7BbG+uc8x2lG5NAMIbq9SBQa8a7+HHD+uNULX4ex40S9zoW4+ld5Q 1zMvbBfYXzpOOpycw6xQ0hLV81moqO5jYx/ZIvC6P+A7FNTHL99hnp9WHx1sy+M5eGo4 j5uAw69pFpfEHmQEFc/nmOhrBY+Fky0QcgdNmIe3ycO2MgKF855OrdBFbFTYMfPlVrXr XV7I4+AIQNgHHB9QDzZNooEHDi1lzjp/n5NXJoM+SpNKYL3049P+yXtCsa7ZOzIv/Vd/ /IQa2bk1igY0TgH5fRn2RslOMrYYEVxf94wbbh/b5rCRurrAsGJmwPtoo3aPB+sKggj3 RlSw== X-Received: by 10.50.30.226 with SMTP id v2mr7069978igh.11.1442759563852; Sun, 20 Sep 2015 07:32:43 -0700 (PDT) Received: from [10.0.10.5] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id kb10sm3589511igb.4.2015.09.20.07.32.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Sep 2015 07:32:42 -0700 (PDT) Message-ID: <55FEC396.4090701@gmail.com> Date: Sun, 20 Sep 2015 10:32:54 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-questions Subject: dhcpd server config help Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 14:32:45 -0000 Hello list; Yesterday had some guests over and when they tried to connect to my WiFi with their cell phones I got a lot of these console messages. Sep 19 09:43:01 mydomain dhcpd: Reclaiming abandoned lease 10.0.10.2. Sep 19 09:43:01 mydomain dhcpd: Abandoning IP address 10.0.10.2: declined. The cause of this is the host system dhcp server is trying to allocate a ip address from its pool that’s already in use. Today I started to investigate this matter. I must have mis-configured something. Following are the config files concerned. Please review and point out errors. Thank You. Content of dhcpd.conf file option domain-name "mydomain.com"; option domain-name-servers 8.8.8.8; # google # 600=10min, 7200=2 hours, 86400=1 day, 604800=1 week, 2592000=30 days default-lease-time 86400; max-lease-time 604800; authoritative; ddns-update-style none; log-facility local1; # No service will be given on this subnet, but declaring it helps the # DHCP server to understand the network topology. subnet 10.152.187.0 netmask 255.255.255.0 { } # This is mydomain.com subnet declaration. # Max of 6 pc on LAN 10.0.10.1 - 10.0.10.6 # 10.0.10.2 is the IP address of the LAN Nic card in FBSD # 10.0.10.7 is the broadcast IP address subnet 10.0.10.0 netmask 255.255.255.248 { range 10.0.10.1 10.0.10.6; option routers 10.0.10.2;} rc.conf file contains this ifconfig_xl0="DHCP" ifconfig_rl0="inet 10.0.10.2" gateway_enable="YES" dhcpd_enable="YES" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd_ifaces="rl0" dhcpd_flags="-q" dhcpd_withumask="022" From owner-freebsd-questions@freebsd.org Sun Sep 20 16:30:19 2015 Return-Path: Delivered-To: freebsd-questions@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 379CD9CF73D for ; Sun, 20 Sep 2015 16:30:19 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (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 007FD102E for ; Sun, 20 Sep 2015 16:30:18 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: by mail.xtaz.uk (Postfix, from userid 1001) id 74B3720AE9EE; Sun, 20 Sep 2015 17:30:14 +0100 (BST) Date: Sun, 20 Sep 2015 17:30:14 +0100 From: Matt Smith To: Ernie Luzar Cc: freebsd-questions Subject: Re: dhcpd server config help Message-ID: <20150920163014.GA99502@xtaz.uk> Mail-Followup-To: Matt Smith , Ernie Luzar , freebsd-questions References: <55FEC396.4090701@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55FEC396.4090701@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 16:30:19 -0000 On Sep 20 10:32, Ernie Luzar wrote: >Hello list; > >Yesterday had some guests over and when they tried to connect to my WiFi >with their cell phones I got a lot of these console messages. > >Sep 19 09:43:01 mydomain dhcpd: Reclaiming abandoned lease 10.0.10.2. >Sep 19 09:43:01 mydomain dhcpd: Abandoning IP address 10.0.10.2: declined. > >The cause of this is the host system dhcp server is trying to allocate a >ip address from its pool that’s already in use. Today I started to >investigate this matter. I must have mis-configured something. >Following are the config files concerned. Please review and point out >errors. Thank You. > > > >Content of dhcpd.conf file >option domain-name "mydomain.com"; >option domain-name-servers 8.8.8.8; # google > ># 600=10min, 7200=2 hours, 86400=1 day, 604800=1 week, 2592000=30 days >default-lease-time 86400; >max-lease-time 604800; >authoritative; >ddns-update-style none; >log-facility local1; > ># No service will be given on this subnet, but declaring it helps the ># DHCP server to understand the network topology. > >subnet 10.152.187.0 netmask 255.255.255.0 { } > ># This is mydomain.com subnet declaration. ># Max of 6 pc on LAN 10.0.10.1 - 10.0.10.6 ># 10.0.10.2 is the IP address of the LAN Nic card in FBSD ># 10.0.10.7 is the broadcast IP address >subnet 10.0.10.0 netmask 255.255.255.248 { >range 10.0.10.1 10.0.10.6; >option routers 10.0.10.2;} > > > >rc.conf file contains this >ifconfig_xl0="DHCP" >ifconfig_rl0="inet 10.0.10.2" > >gateway_enable="YES" > >dhcpd_enable="YES" >dhcpd_conf="/usr/local/etc/dhcpd.conf" >dhcpd_ifaces="rl0" >dhcpd_flags="-q" >dhcpd_withumask="022" > I think the problem is that your FreeBSD server is using 10.0.10.2 as its own IP address but you have told DHCPd to use 10.0.10.1 to 10.0.10.6 as the range to give out to clients that request an IP. The 10.2 address is part of this range. So you should change the range to be outside of anything that you already have in use so that they don't conflict. -- Matt From owner-freebsd-questions@freebsd.org Sun Sep 20 18:44:42 2015 Return-Path: Delivered-To: freebsd-questions@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 33D8CA0555A; Sun, 20 Sep 2015 18:44:42 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id E3ACA14E1; Sun, 20 Sep 2015 18:44:41 +0000 (UTC) (envelope-from des@des.no) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 806178C35; Sun, 20 Sep 2015 18:44:33 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 57292851F; Sun, 20 Sep 2015 20:44:33 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Slawa Olhovchenkov Cc: grarpamp , freebsd-security@freebsd.org, freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds References: <86vbb7dhaa.fsf@nine.des.no> <20150918134804.GU3158@zxy.spb.ru> <86oagzwf8j.fsf@nine.des.no> <20150919125023.GA21849@zxy.spb.ru> Date: Sun, 20 Sep 2015 20:44:33 +0200 In-Reply-To: <20150919125023.GA21849@zxy.spb.ru> (Slawa Olhovchenkov's message of "Sat, 19 Sep 2015 15:50:23 +0300") Message-ID: <868u81vsku.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 18:44:42 -0000 Slawa Olhovchenkov writes: > Dag-Erling Sm=C3=B8rgrav writes: > > freebsd-update will most likely be gone in 11. > What is planed for replacement? Packaged base. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-questions@freebsd.org Sun Sep 20 18:48:17 2015 Return-Path: Delivered-To: freebsd-questions@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 B784AA05740; Sun, 20 Sep 2015 18:48:17 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 746101823; Sun, 20 Sep 2015 18:48:17 +0000 (UTC) (envelope-from des@des.no) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 664C68C3F; Sun, 20 Sep 2015 18:48:16 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 453438521; Sun, 20 Sep 2015 20:48:16 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Dmitry Morozovsky Cc: Slawa Olhovchenkov , freebsd-security@freebsd.org, grarpamp , freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds References: <86vbb7dhaa.fsf@nine.des.no> <20150918134804.GU3158@zxy.spb.ru> <86oagzwf8j.fsf@nine.des.no> Date: Sun, 20 Sep 2015 20:48:16 +0200 In-Reply-To: (Dmitry Morozovsky's message of "Sat, 19 Sep 2015 15:44:10 +0300 (MSK)") Message-ID: <864mipvsen.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 18:48:17 -0000 Dmitry Morozovsky writes: > Dag-Erling Sm=C3=B8rgrav writes: > > freebsd-update will most likely be gone in 11. > Are there any published plans available? The plan is for 11 to have a fully packaged base system. There should be some information in developer summit reports on the wiki. The code is in projects/release-pkg. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-questions@freebsd.org Sun Sep 20 18:51:31 2015 Return-Path: Delivered-To: freebsd-questions@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 73AAAA058E8 for ; Sun, 20 Sep 2015 18:51:31 +0000 (UTC) (envelope-from jon@radel.com) Received: from radel.com (fly.radel.com [70.184.242.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "*.radel.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B4E81BB9 for ; Sun, 20 Sep 2015 18:51:30 +0000 (UTC) (envelope-from jon@radel.com) X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.18.7 (ClamAV engine v0.98.7) Received: from [192.168.43.212] (account jon@radel.com [192.168.43.212] verified) by radel.com (CommuniGate Pro SMTP 6.1.2 _community_) with ESMTPSA id 884110; Sun, 20 Sep 2015 17:51:20 +0000 Content-Type: multipart/signed; boundary=Apple-Mail-97D4C4AD-C75B-4CCC-8813-7E113E162F11; protocol="application/pkcs7-signature"; micalg=sha1 Mime-Version: 1.0 (1.0) Subject: Re: dhcpd server config help From: Jon Radel X-Mailer: iPhone Mail (12H321) In-Reply-To: <20150920163014.GA99502@xtaz.uk> Date: Sun, 20 Sep 2015 13:51:20 -0400 Cc: Ernie Luzar , freebsd-questions Content-Transfer-Encoding: 7bit Message-Id: <8C86C007-5211-4B02-8ABB-BCEDA5156931@radel.com> References: <55FEC396.4090701@gmail.com> <20150920163014.GA99502@xtaz.uk> To: Matt Smith X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 18:51:31 -0000 --Apple-Mail-97D4C4AD-C75B-4CCC-8813-7E113E162F11 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable >>=20 >> # This is mydomain.com subnet declaration. >> # Max of 6 pc on LAN 10.0.10.1 - 10.0.10.6 >> # 10.0.10.2 is the IP address of the LAN Nic card in FBSD >> # 10.0.10.7 is the broadcast IP address >> subnet 10.0.10.0 netmask 255.255.255.248 { >> range 10.0.10.1 10.0.10.6; >> option routers 10.0.10.2;} >>=20 >>=20 >>=20 >>=20 >=20 > I think the problem is that your FreeBSD server is using 10.0.10.2 as its o= wn IP address but you have told DHCPd to use 10.0.10.1 to 10.0.10.6 as the r= ange to give out to clients that request an IP. The 10.2 address is part of t= his range. So you should change the range to be outside of anything that you= already have in use so that they don't conflict. >=20 And while you're at it, I'd suggest allowing your DHCP server to use more th= an 6 addresses. With only 6, it doesn't take many friends over before the po= or thing starts thrashing about trying to find a free address to assign. Giv= e it a couple hundred and be done with it.=20 --Jon Radel= --Apple-Mail-97D4C4AD-C75B-4CCC-8813-7E113E162F11 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIF/DCCBfgw ggTgoAMCAQICEHNU5Tx9a7TNDWBpDfzOARswDQYJKoZIhvcNAQELBQAwgZsxCzAJBgNVBAYTAkdC MRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoT EUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xNTAzMzAwMDAwMDBaFw0xODAzMjkyMzU5 NTlaMIH6MQswCQYDVQQGEwJVUzEOMAwGA1UEERMFMjIxNTAxCzAJBgNVBAgTAlZBMRQwEgYDVQQH EwtTcHJpbmdmaWVsZDEaMBgGA1UECRMRNjkxNyBSaWRnZXdheSBEci4xFTATBgNVBAoTDEpvbiBU LiBSYWRlbDEyMDAGA1UECxMpSXNzdWVkIHRocm91Z2ggSm9uIFQuIFJhZGVsIEUtUEtJIE1hbmFn ZXIxHzAdBgNVBAsTFkNvcnBvcmF0ZSBTZWN1cmUgRW1haWwxEjAQBgNVBAMTCUpvbiBSYWRlbDEc MBoGCSqGSIb3DQEJARYNam9uQHJhZGVsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBAN7VG2H2FtCpo4Of74Ll1UBAf2czZUfeg9rNm587CYgbZJcj+/c+56ZxBDcmSGalDTqBizPJ duRMIuyq8R9qViPzWN238rmVPhpV2PQt8khbJNxT3lXauwK4exK+f8+chywS1eDnesK2pLgQ60n2 7etjaE/xgKLLPXJjeaficomz3cwcbgCRdi5WnN9ogAMRNxWsD6trO9cR+cMldcNln1m65XXTrIii 86+FhZKVpW7yetIcmNcVkjYhfCAh5UGgyKHfK7osuPXgj9h1nSsgDwr5Q0H41bpGLe7AdcFuviOH dmqSuohVSt/VV7JuF2slx2pd0w0eMoNKUKhrFhFsvLUCAwEAAaOCAdUwggHRMB8GA1UdIwQYMBaA FJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBTP1gHXRYR8E0eyRHCj/S+HyppC7DAOBgNV HQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIw RgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAwUwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUu Y29tb2RvLm5ldC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20v Q09NT0RPU0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYI KwYBBQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYBBQUH MAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAYBgNVHREEETAPgQ1qb25AcmFkZWwuY29tMA0G CSqGSIb3DQEBCwUAA4IBAQBLU976AGA/5JD9rkjl7vNfRGDQOEffvwseVmLEmBLot8I8vZ50oxRC LdOH0Zd8uN17J5a4xajP3blnMEdw/CQF4f6Iz8ASG7QOGLSSin+nrqD20Q8lRn8oOyrF100OsPRP Kmff/fekdOMkQOrJ3MCDAHQ2fxuWkxupLBP6PzC49qR8uyPVxIPNetMsuyYhAHtq4DJphd1bJbxi rDffqstQK+M5R+eo47KNWyJ5PD/Q8ug4clobJ7P5W1Xh7KLqnVI2JffYD5+/EEzMpAsKiQTjdxci 1z06TOr/9/Z+68anXuvyambg6OMzkTaTCyD1sE9QExHj+zGiwpUufSj2vGWjMYIDwzCCA78CAQEw gbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcT B1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hB LTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQc1TlPH1rtM0N YGkN/M4BGzAJBgUrDgMCGgUAoIIB5zAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3 DQEJBTEPFw0xNTA5MjAxNzUxMjBaMCMGCSqGSIb3DQEJBDEWBBT5mT52dWhf6/6NUxAuymTGomH9 xzCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBN YW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFB MD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg RW1haWwgQ0ECEHNU5Tx9a7TNDWBpDfzOARswgcMGCyqGSIb3DQEJEAILMYGzoIGwMIGbMQswCQYD VQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRow GAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50 IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEHNU5Tx9a7TNDWBpDfzOARswDQYJ KoZIhvcNAQEBBQAEggEA1hbkQfz3Pk3U1Qo4CWtzHBwsfGJZwE3IqSVVkraogGENjjTcn/9YwHuJ B4bz74w0gemrcMj59hlWDNirjox4yhjGs3801b34Naz8nPzQJO5Cn3iKjCVE+FF6mFB6tOmnAk7N IfSHmryI9BKpl1j240w/4L5kIh3LkywT5vbq9la4eSuN9KF6lBCEWc/Njum33hBQmqHCAmJDKF3x IlyiuOuoaipv9q8F6XOE4vbAvJrkXUSLJKdODoD/5ikK9wmnIV4yme3j0r1EhauXQWeXGuzWyDMZ r1+f/W+4OA+QH87Y7HN75Rrf04uaGQTOIRJoYTNMinitF2AnpVVduMGRCQAAAAAAAA== --Apple-Mail-97D4C4AD-C75B-4CCC-8813-7E113E162F11-- From owner-freebsd-questions@freebsd.org Sun Sep 20 23:14:57 2015 Return-Path: Delivered-To: freebsd-questions@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 439EDA05AB3 for ; Sun, 20 Sep 2015 23:14:57 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E304B1FC8 for ; Sun, 20 Sep 2015 23:14:56 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-75-179-47-202.neo.res.rr.com [75.179.47.202]); by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id 97492218; Sun, 20 Sep 2015 19:14:49 -0400 (EDT) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id 516414ad; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sun, 20 Sep 2015 19:14:48 -0400 (EDT) Message-ID: <1442791013.1220.7.camel@michaeleichorn.com> Subject: Re: HTTPS on freebsd.org, git, reproducible builds From: "Michael B. Eichorn" To: Slawa Olhovchenkov , Polytropon Cc: freebsd-questions@freebsd.org Date: Sun, 20 Sep 2015 19:16:53 -0400 In-Reply-To: <20150920121201.GF21849@zxy.spb.ru> References: <20150919125023.GA21849@zxy.spb.ru> <20150919151517.739ab70a.freebsd@edvax.de> <20150919133248.GB21849@zxy.spb.ru> <20150919184712.4d26f3f9.freebsd@edvax.de> <20150919172839.GC21849@zxy.spb.ru> <20150919204745.eeb62abd.freebsd@edvax.de> <20150919193105.GD21849@zxy.spb.ru> <20150919220658.07d652f7.freebsd@edvax.de> <20150919220222.GE21849@zxy.spb.ru> <20150920135711.381d1c02.freebsd@edvax.de> <20150920121201.GF21849@zxy.spb.ru> Content-Type: multipart/signed; micalg="sha-512"; protocol="application/x-pkcs7-signature"; boundary="=-0NXaCB9ATvY6XGWylVU2" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 23:14:57 -0000 --=-0NXaCB9ATvY6XGWylVU2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Given that this thread moved onto packaging base I just wanted to point folks at some primary source material (from bapt@ himself) =46rom BSDCan2015: Packaging the base system https://youtu.be/Br6izhH5P1I Part I (43 min) https://youtu.be/v7px6ktoDAI Part II (14 min) =46rom BSDNow Podcast: https://youtu.be/gDi09Wfx-9s?t=3D25m4s There is lots of discussion about how things will work and the extent to which base might be broken into packages. Regards, Ike --=-0NXaCB9ATvY6XGWylVU2 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDnzCCA5sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAwUAoIIB2zAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5MjAyMzE2NTNaME8GCSqGSIb3DQEJ BDFCBEBQetpgP0BJtglA3YiGpMZjGlTD3V09vX3xm/O0hCL+vEAMRJQcEY/p87jHzZs6+bxBHdxr ntFaqk8y4dLtOWqxMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQQIDDl3GMIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoT DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25p bmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50 IENBAgMOXcYwDQYJKoZIhvcNAQEBBQAEggEAsu/1v31B3c4FmqSTzqnGAMpciuZD0ZLR2kZqa5iH aoqMWdZ9JlsdCTqikiVmeRfz6AR/jDwCsr26PPIQNVj/A1LWtd2nU98QMJspT2RtNcyUfyfDRM0P /D4OGRdocvPaX/KeeiiXnnaCz3pAMKFUCViJpvQqq6LxZmyW4iJWuUtdSSyhsw/Gl+AV7VVqLB4d nA5aALl9ogR8dkVGTJhggwHRtSoZLAecGS1KUF7qyy/jp2+jSN0FSx7gHS4Wy8fPbnQsq4okzz91 O3lf/yBNKvUjodx8o78dER6D/ouSuZ6dz7fwYtN9reT6cvrset4Ht/u01lkKczonmzvlkg+gXAAA AAAAAA== --=-0NXaCB9ATvY6XGWylVU2-- From owner-freebsd-questions@freebsd.org Mon Sep 21 05:17:38 2015 Return-Path: Delivered-To: freebsd-questions@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 4EADAA0621A for ; Mon, 21 Sep 2015 05:17:38 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from shopzeus.com (shopzeus.com [87.229.70.149]) by mx1.freebsd.org (Postfix) with ESMTP id C9AED1E26 for ; Mon, 21 Sep 2015 05:17:37 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from [127.127.127.127] (localhost [127.127.127.127]) (Authenticated sender: gandalf) by shopzeus.com (Postfix) with ESMTPSA id A2197889B806 for ; Mon, 21 Sep 2015 01:17:29 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopzeus.com; s=shopzeus_com; t=1442812649; bh=/A1zh9OEYJ9HxkWWpnDcJxCKafVb+exoovOSfKqTqIE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=jfUebdmpGwymWnBv9SD+7rGRv7vW94ACB6a/FJdfWb+Q7QagSA3pfQ14PbeOko+zX U9FKqinUvau/HUdwGXCBSuTv0a/nye0IC/rv6ZrrZ0licbIej9HRW2Q/j2PAs1yESu ACjLTF+h6EttNAiYY+NluyGNsfxX9V3IyzYnotkH3u3HFPd7parYSyB+eRBRYBAudc SKRBx3SwkAWjbyWy4RUPuAwd5S2hR/OGIBtvmN/rTbMMHxAneUzXb+jWIpFCj5kt4p 29yTnKHYSfQdQgH9wAc04UuD4NXwxtX5g1Ma0Ok5hqSWKaBVXjTrIfX353RRp1dtiv Cjy8BpIZIplkQ== Subject: Re: Problem upgrading from 10.1 to 10.2 To: freebsd-questions@freebsd.org References: <20150917212506.2334162a@asrock-lan.local.home> From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Message-ID: <55FF92E9.7090204@shopzeus.com> Date: Mon, 21 Sep 2015 07:17:29 +0200 MIME-Version: 1.0 In-Reply-To: <20150917212506.2334162a@asrock-lan.local.home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 05:17:38 -0000 > patches.....10....20....30....40....50....60....70....80....90....100. > done. Applying patches... done. Fetching 4720 files... gunzip: unknown > compression format > 143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94 has > incorrect hash. > root@asrock-lan:~ # uname -a > FreeBSD asrock-lan 10.1-RELEASE-p19 FreeBSD 10.1-RELEASE-p19 #0: Sat > Aug 22 03:55:09 UTC 2015 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > I have seen the posting on the forum about lighthttpd not working as > expected and that everything is switched to Nginx but I am still having > an issue. > > Any ideas what I can do from here? |sudo rm /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94.gz BTW, you have to read and understand https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html - you will see that the uname will change after you first reboot your system. From owner-freebsd-questions@freebsd.org Mon Sep 21 06:21:50 2015 Return-Path: Delivered-To: freebsd-questions@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 74E6AA05ED3 for ; Mon, 21 Sep 2015 06:21:50 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B28A145E for ; Mon, 21 Sep 2015 06:21:49 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8L6LmQM013949 for ; Mon, 21 Sep 2015 00:21:48 -0600 Message-Id: <201509210621.t8L6LmQM013949@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-questions@freebsd.org Subject: spamd: could not create IO::Socket::IP socket on [::1]:783: Permission denied Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 2015 00:21:48 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 06:21:50 -0000 It appears that I have some configuration left to do spamd: could not create IO::Socket::IP socket on [::1]:783: Permission denied server socket setup failed, retry 1: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783 : Permission denied What do I need to do to get spamd to run? -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Mon Sep 21 06:31:54 2015 Return-Path: Delivered-To: freebsd-questions@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 2984FA063D7 for ; Mon, 21 Sep 2015 06:31:54 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 061FD1967 for ; Mon, 21 Sep 2015 06:31:53 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8L6Vqmd014047 for ; Mon, 21 Sep 2015 00:31:52 -0600 Message-Id: <201509210631.t8L6Vqmd014047@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-questions@freebsd.org Subject: X server insecure (must use xauth-style authorization) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 2015 00:31:52 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 06:31:54 -0000 I am getting the message in the Subject line when running exmh. Here is a more complete version of the messages: BgLostPid ps 2456: PID TT STAT TIME COMMAND child process exited abnormally BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored exmh-bg cannot rendez-vous with UI - exiting. Usually this is because Tk send is not working. Check the notes under Frequently Asked Questions #4a and #4b. You can find this under the Help menu. --- I am not sure where this FAQ is that they are referring to. I vaguely remember this MIT-MAGIC-COOKIE-1 stuff from setting up a sun years ago, but don't remember the details. I added the following to my .login, on the assumption that it would fix the problem, but it doesn't; setenv cookie `date +%s%s%s%s | cut -c-32` xauth add unix:0.0 MIT-MAGIC-COOKIE-1 $cookie xauth add `hostname -f1` :0.0 MIT-MAGIC-COOKIE-1 $cookie /usr/local/bin/X -auth /home/reg/.Xauthority What should I be doing? -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Mon Sep 21 06:51:46 2015 Return-Path: Delivered-To: freebsd-questions@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 46C18A06BF4 for ; Mon, 21 Sep 2015 06:51:46 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 259861F94 for ; Mon, 21 Sep 2015 06:51:46 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8L5x4st013836 for ; Sun, 20 Sep 2015 23:59:04 -0600 Message-Id: <201509210559.t8L5x4st013836@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-questions@freebsd.org Subject: X server insecure (must use xauth-style authorization) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 2015 23:59:04 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 06:51:46 -0000 I am getting the message in the Subject line when running exmh. Here is a more complete version of the messages: BgLostPid ps 2456: PID TT STAT TIME COMMAND child process exited abnormally BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored BgRegister X server insecure (must use xauth-style authorization); command ignored exmh-bg cannot rendez-vous with UI - exiting. Usually this is because Tk send is not working. Check the notes under Frequently Asked Questions #4a and #4b. You can find this under the Help menu. --- I am not sure where this FAQ is that they are referring to. I vaguely remember this MIT-MAGIC-COOKIE-1 stuff from setting up a sun years ago, but don't remember the details. I added the following to my .login, on the assumption that it would fix the problem, but it doesn't; setenv cookie `date +%s%s%s%s | cut -c-32` xauth add unix:0.0 MIT-MAGIC-COOKIE-1 $cookie xauth add `hostname -f1` :0.0 MIT-MAGIC-COOKIE-1 $cookie /usr/local/bin/X -auth /home/reg/.Xauthority What should I be doing? -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Mon Sep 21 09:06:14 2015 Return-Path: Delivered-To: freebsd-questions@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 4C2CCA06851; Mon, 21 Sep 2015 09:06:14 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC23A1AA9; Mon, 21 Sep 2015 09:06:13 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id t8L95xnr011616; Mon, 21 Sep 2015 12:05:59 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Mon, 21 Sep 2015 12:05:59 +0300 (MSK) From: Dmitry Morozovsky To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= cc: freebsd-questions@freebsd.org, freebsd-security@freebsd.org, grarpamp , Slawa Olhovchenkov Subject: Re: HTTPS on freebsd.org, git, reproducible builds In-Reply-To: <864mipvsen.fsf@nine.des.no> Message-ID: References: <86vbb7dhaa.fsf@nine.des.no> <20150918134804.GU3158@zxy.spb.ru> <86oagzwf8j.fsf@nine.des.no> <864mipvsen.fsf@nine.des.no> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Mon, 21 Sep 2015 12:06:00 +0300 (MSK) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 09:06:14 -0000 On Sun, 20 Sep 2015, Dag-Erling Sm?rgrav wrote: > > > freebsd-update will most likely be gone in 11. > > Are there any published plans available? > > The plan is for 11 to have a fully packaged base system. There should > be some information in developer summit reports on the wiki. The code > is in projects/release-pkg. That sounds very promisive! Unfortunately I couldn't find any report on the wiki... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-questions@freebsd.org Mon Sep 21 10:39:11 2015 Return-Path: Delivered-To: freebsd-questions@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 92301A057A3 for ; Mon, 21 Sep 2015 10:39:11 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from nodeunit.com (mx01.stoianov.me [37.0.34.67]) by mx1.freebsd.org (Postfix) with ESMTP id 574311C01 for ; Mon, 21 Sep 2015 10:39:10 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from x140e (x140e-wifi.local.home [10.7.7.5]) by nodeunit.com (Postfix) with ESMTPS id 605A6575E1 for ; Mon, 21 Sep 2015 12:39:03 +0200 (CEST) Date: Mon, 21 Sep 2015 12:39:02 +0200 From: George To: freebsd-questions@freebsd.org Subject: Re: Problem upgrading from 10.1 to 10.2 Message-ID: <20150921123902.4c33b061@x140e> In-Reply-To: <55FF92E9.7090204@shopzeus.com> References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 10:39:11 -0000 On Mon, 21 Sep 2015 07:17:29 +0200 Nagy L=C3=A1szl=C3=B3 Zsolt wrote: >=20 > > patches.....10....20....30....40....50....60....70....80....90....100. > > done. Applying patches... done. Fetching 4720 files... gunzip: > > unknown compression format > > 143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94 has > > incorrect hash. > > root@asrock-lan:~ # uname -a > > FreeBSD asrock-lan 10.1-RELEASE-p19 FreeBSD 10.1-RELEASE-p19 #0: Sat > > Aug 22 03:55:09 UTC 2015 > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > > amd64 > > > > I have seen the posting on the forum about lighthttpd not working as > > expected and that everything is switched to Nginx but I am still > > having an issue. > > > > Any ideas what I can do from here? >=20 > |sudo > rm /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec9= 7cbbecd7b55e72ed94.gz I have done that 10 times already, it downloads it and complains again. >=20 > BTW, you have to read and understand > https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > - you will see that the uname will change after you first reboot your > system. I am not sure what you mean by that. I have rebooted many times and done freebsd-update fetch and install many times without any issues. Doesn't uname -a return all identifiers about the kernl which would change if I recompile my kernel... something I have not done. Thanks for trying to help me. >=20 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Mon Sep 21 10:49:09 2015 Return-Path: Delivered-To: freebsd-questions@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 E7A66A05C62 for ; Mon, 21 Sep 2015 10:49:09 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: from trent.utfs.org (trent.utfs.org [IPv6:2a03:3680:0:3::67]) (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 9B95E1FFC for ; Mon, 21 Sep 2015 10:49:09 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: by trent.utfs.org (Postfix, from userid 8) id E8D073DC5D; Mon, 21 Sep 2015 12:48:56 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on trent.utfs.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Received: from trent.utfs.org (localhost [127.0.0.1]) by trent.utfs.org (Postfix) with ESMTP id 0D9C93DC5C; Mon, 21 Sep 2015 12:48:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by trent.utfs.org (Postfix) with ESMTP id E28443DB25; Mon, 21 Sep 2015 12:48:55 +0200 (CEST) Date: Mon, 21 Sep 2015 03:48:55 -0700 (PDT) From: Christian Kujau To: "William A. Mahaffey III" cc: freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds In-Reply-To: <55FCE970.8030206@hiwaay.net> Message-ID: References: <1442578892.1807598.387215049.07156D0F@webmail.messagingengine.com> <1442579551.1810383.387233801.46EBDA6D@webmail.messagingengine.com> <55FC1498.7090902@Plominski.eu> <55FC19B7.1010607@hiwaay.net> <20150918174436.GF85844@kropotkin.auxio> <55FC8C71.3040902@hiwaay.net> <55FCE970.8030206@hiwaay.net> User-Agent: Alpine 2.20.9 (DEB 91 2015-08-14) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-AV-Checked: ClamAV using ClamSMTP (127.0.0.1 (trent) at Mon Sep 21 12:48:56 2015 +0200 (CEST)) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 10:49:10 -0000 On Fri, 18 Sep 2015, William A. Mahaffey III wrote: > On 09/18/15 18:23, Chris Hill wrote: > > On Fri, 18 Sep 2015, William A. Mahaffey III wrote: > > > > [ big snip ] > > > > > [root@kabini1, /etc, 10:07:39am] 353 % sysctl -d net.inet.ip.stealth > > > sysctl: unknown oid 'net.inet.ip.stealth' > > > [root@kabini1, /etc, 5:17:54pm] 354 % sysctl -d net.inet.ip.random_id > > > net.inet.ip.random_id: Assign random ip_id values > > > [root@kabini1, /etc, 5:18:07pm] 355 % uname -a > > > FreeBSD kabini1.local 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug > > > 22 01:54:44 UTC 2015 > > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > [root@kabini1, /etc, 5:18:16pm] 356 % > > > > > > > > > Maybe a 10.n thing ? > > > > Maybe not: > > > > chris@tripel$ uname -mv > > FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 > > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > chris@tripel$ sysctl -d net.inet.ip.stealth > > sysctl: unknown oid 'net.inet.ip.stealth': No such file or directory > > chris@tripel$ sysctl -d net.inet.ip.random_id > > net.inet.ip.random_id: Assign random ip_id values > > > Fair enough, where did the other guy get that 'stealth' setting ? IPSTEALTH has to be enabled in the kernel configuration for this to work. See also: http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028698.html Christian. -- BOFH excuse #55: Plumber mistook routing panel for decorative wall fixture From owner-freebsd-questions@freebsd.org Mon Sep 21 11:05:09 2015 Return-Path: Delivered-To: freebsd-questions@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 31D91A063D8 for ; Mon, 21 Sep 2015 11:05:09 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 D11511980 for ; Mon, 21 Sep 2015 11:05:08 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by wicfx3 with SMTP id fx3so140092419wic.1 for ; Mon, 21 Sep 2015 04:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=ZfPa4icGx3mvAdv+W3LhYO7naDbj68cT2UrI4dJz4pE=; b=sJwifnCgfrzZXk0BKrM9cTHYooUizCjgzwImjrWcPSm/THoHcCEq0cUqEiFbQ4TLNB Es63QSTZeVQgoehayN8xRou3ug32l8+wAldJeMWOb9vl79KyfYvhA8C9jLiOYQx2oLXP RP+3rrYILQc0B82myOaHJnKP7pTrjMTr8UjVwspkfrKdN6SWfyeKPNjGo/vXslUXKqQm 1XdWFkLoyK3pIdf6v4fCzYhhNcHcF8Ldqc+e8ZommDkvU+aswblAUV4ae01aa72oYTLd Z/k9ngLegRIAodeT8jHSVMVDBw5u+Wu+P7t6BHaP7sGIFg5TqWXRCd/hXjVXB2X9jLgj C/4g== X-Received: by 10.180.105.135 with SMTP id gm7mr12088308wib.18.1442833507383; Mon, 21 Sep 2015 04:05:07 -0700 (PDT) Received: from gumby.homeunix.com ([90.195.198.255]) by smtp.gmail.com with ESMTPSA id uc12sm12890106wib.13.2015.09.21.04.05.05 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Sep 2015 04:05:06 -0700 (PDT) Date: Mon, 21 Sep 2015 12:05:02 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: spamd: could not create IO::Socket::IP socket on [::1]:783: Permission denied Message-ID: <20150921120502.529bd60e@gumby.homeunix.com> In-Reply-To: <201509210621.t8L6LmQM013949@deneb.dwf.com> References: <201509210621.t8L6LmQM013949@deneb.dwf.com> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 11:05:09 -0000 On Mon, 21 Sep 2015 00:21:48 -0600 reg@dwf.com wrote: > > It appears that I have some configuration left to do > > > spamd: could not create IO::Socket::IP socket on [::1]:783: > Permission denied server socket setup failed, retry 1: spamd: could > not create IO::Socket::IP socket on [127.0.0.1]:783 > : Permission denied > > What do I need to do to get spamd to run? It depends what you are trying to do Most likely you are trying to start spamd as an unprivileged user rather than starting it as root and letting it drop to the user specified by the -u argument. It has to start as root to use a low port. If you want it to work with user data in home directories it needs to start as root and run without -u. From owner-freebsd-questions@freebsd.org Mon Sep 21 23:08:41 2015 Return-Path: Delivered-To: freebsd-questions@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 CA1F59D094A for ; Mon, 21 Sep 2015 23:08:41 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C91718C9 for ; Mon, 21 Sep 2015 23:08:40 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8LN8dPt028254; Mon, 21 Sep 2015 17:08:39 -0600 Message-Id: <201509212308.t8LN8dPt028254@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: RW cc: freebsd-questions@freebsd.org, reg@deneb.dwf.com Subject: Re: spamd: could not create IO::Socket::IP socket on [::1]:783: Permission denied In-reply-to: <20150921120502.529bd60e@gumby.homeunix.com> References: <201509210621.t8L6LmQM013949@deneb.dwf.com> <20150921120502.529bd60e@gumby.homeunix.com> Comments: In-reply-to RW via freebsd-questions message dated "Mon, 21 Sep 2015 12:05:02 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 2015 17:08:39 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 23:08:41 -0000 > From owner-freebsd-questions@freebsd.org Mon Sep 21 05:05:28 2015 > It depends what you are trying to do > THanks, I was trying to run spamassassin/spamc to see why spamssassin was not marking up the mail sent thru it, and ran the experiment as me rather than root. My bad. -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Tue Sep 22 05:09:01 2015 Return-Path: Delivered-To: freebsd-questions@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 464D6A0299D for ; Tue, 22 Sep 2015 05:09:01 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C6501D67 for ; Tue, 22 Sep 2015 05:09:00 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8M58waq030441; Mon, 21 Sep 2015 23:08:58 -0600 Message-Id: <201509220508.t8M58waq030441@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-questions@freebsd.org, reg@deneb.dwf.com Subject: Is there a doc explaining how to setup spamassassin under FreeBSD. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 2015 23:08:58 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 05:09:01 -0000 I have used Spamassassin under Linux, but just transfering my configuration files (with appropriate directories updated) does not work. In particular, there are no X-Spam-* lines getting added to the messages. Can someone point me at a doc that explains how to install spamassassin on FreeBSD, Im really confused. -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Tue Sep 22 05:17:54 2015 Return-Path: Delivered-To: freebsd-questions@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 D1ABAA02EC4 for ; Tue, 22 Sep 2015 05:17:54 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.225]) by mx1.freebsd.org (Postfix) with ESMTP id 44F3510E1 for ; Tue, 22 Sep 2015 05:17:53 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [70.121.59.224] ([70.121.59.224:57515] helo=[192.168.0.6]) by dnvrco-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 15/DA-15818-9B3E0065; Tue, 22 Sep 2015 05:14:35 +0000 Date: Tue, 22 Sep 2015 00:14:33 -0500 From: Paul Schmehl Reply-To: Paul Schmehl To: reg@dwf.com, freebsd-questions@freebsd.org, reg@deneb.dwf.com Subject: Re: Is there a doc explaining how to setup spamassassin under FreeBSD. Message-ID: In-Reply-To: <201509220508.t8M58waq030441@deneb.dwf.com> References: <201509220508.t8M58waq030441@deneb.dwf.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-RR-Connecting-IP: 107.14.64.118:25 X-Authority-Analysis: v=2.1 cv=FuGL/gbq c=1 sm=1 tr=0 a=Jnt5oOXMh44BVXcArVZt4A==:117 a=Jnt5oOXMh44BVXcArVZt4A==:17 a=ayC55rCoAAAA:8 a=kj9zAlcOel0A:10 a=SOlUAsafAAAA:8 a=nzz-CIdWAAAA:8 a=GzfttSJt_VW5WeIrEdQA:9 a=CjuIK1q_8ugA:10 X-Cloudmark-Score: 0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 05:17:54 -0000 --On September 21, 2015 at 11:08:58 PM -0600 reg@dwf.com wrote: > > I have used Spamassassin under Linux, but just transfering my > configuration files (with appropriate directories updated) > does not work. > > In particular, there are no X-Spam-* lines getting added to > the messages. > > Can someone point me at a doc that explains how to install > spamassassin on FreeBSD, Im really confused. Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell From owner-freebsd-questions@freebsd.org Tue Sep 22 06:08:22 2015 Return-Path: Delivered-To: freebsd-questions@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 5AE47A05E38 for ; Tue, 22 Sep 2015 06:08:22 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from shopzeus.com (shopzeus.com [87.229.70.149]) by mx1.freebsd.org (Postfix) with ESMTP id 1CD52182D for ; Tue, 22 Sep 2015 06:08:21 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from [127.127.127.127] (localhost [127.127.127.127]) (Authenticated sender: gandalf) by shopzeus.com (Postfix) with ESMTPSA id 9FB41889B807 for ; Tue, 22 Sep 2015 02:08:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopzeus.com; s=shopzeus_com; t=1442902093; bh=k2gQ3cTa7RkRRcEkqP9Q8lcqirf1PzEMjvW9A5mLRjQ=; h=Subject:References:To:From:Date:In-Reply-To:From; b=kqAhEG+PvY7wp4FEl0BItCWoWkedBdmL2vGm7bOrEYmZrj9OXYN5O84nocMNIuUbh HGIfU/C1Y4aCM1eo6PzpdTJfUmKydqxPHONgPwFp4cqXiPKoqWOE8uSgtsqLcdICHK kQrVuHqxOtxp2IU+doNrsL0WDoCTmYpGB4rcqGGkZANabUOBO4yL1wrKBVvUToRZW3 Jq6xIyyjKz6+wsWxmIbcyLOKfshjI9ZDZ4w9H5e202JHV5IeHpzzghuNclZrO7QWxJ hEhmy5rcd3/48n/aykp8erzXP2hR9SdLROeIOGV4kuhflX5R4+CL+08iQBNLltzPvt /gHE8c0MO19bw== Subject: [SOLVED] Re: Cannot start opendkim References: <55FBFEB6.3000909@shopzeus.com> <55FC0361.6030706@FreeBSD.org> <55FC0430.8030505@shopzeus.com> <55FD51CA.8020708@kulturflatrate.net> To: freebsd-questions@freebsd.org From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Message-ID: <5600F04D.5010501@shopzeus.com> Date: Tue, 22 Sep 2015 08:08:13 +0200 MIME-Version: 1.0 In-Reply-To: <55FD51CA.8020708@kulturflatrate.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 06:08:22 -0000 >>> As I recall, you can't specify both KeyFile and KeyTable in the same >>> configuration. >> Commented KeyFile and Selector, but still have the same problem. >> > Have a look at these resources: > > https://forums.freebsd.org/threads/opendkim-spf.27201/#post-169910 > > http://www.stevejenkins.com/blog/2010/09/how-to-get-dkim-domainkeys-identified-mail-working-on-centos-5-5-and-postfix-using-opendkim/ The problem was the "Statistics" keyword. After commenting out that line, it started. I got that config file as an example from a website. Apparently, that "Statistics" configuration option is not available in my version of opendkim. From owner-freebsd-questions@freebsd.org Tue Sep 22 06:09:46 2015 Return-Path: Delivered-To: freebsd-questions@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 546E6A05F07 for ; Tue, 22 Sep 2015 06:09:46 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from shopzeus.com (shopzeus.com [87.229.70.149]) by mx1.freebsd.org (Postfix) with ESMTP id 14F5B18E1 for ; Tue, 22 Sep 2015 06:09:45 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from [127.127.127.127] (localhost [127.127.127.127]) (Authenticated sender: gandalf) by shopzeus.com (Postfix) with ESMTPSA id 8B94B889B804 for ; Tue, 22 Sep 2015 02:09:44 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopzeus.com; s=shopzeus_com; t=1442902184; bh=hBbOFkHz5YZwhR2pXd3HYzHwp/VfwTFPItjUtm7TFMo=; h=Subject:To:References:From:Date:In-Reply-To:From; b=A4ISuYWZETp+aTC1r6dve4RvpsXg1qhDmqEa6V4fZZ8ZYMhaOD7u7hdfFJ/l0Wy1w bwkV8WoRmoJHCWUDFPXSlNfi3uEaBKujDAFhQn9Eacs/LjkCIPAAQlbP1rfUDiG0ZE hiAMU+D+dKz/UhdxQmb5oDFyHl05OJ9O4XF5CeySin+W/JtqpViiKbxOb/wPME62UC Xg8/KnctZApfRHJCheziXE3K+eiILn3CwupDF+gjn+IA7vOPe3/bdkgnA52pGgggbd jtbgPZ7XHv7nrl2AulT5DuWRFKVNxP72K8BM7g/Sb1afSPsZmM/v+98mW5vYYMwMVZ DzZ5oLQATwxsA== Subject: Re: Problem upgrading from 10.1 to 10.2 To: freebsd-questions@freebsd.org References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> <20150921123902.4c33b061@x140e> From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Message-ID: <5600F0A8.1060900@shopzeus.com> Date: Tue, 22 Sep 2015 08:09:44 +0200 MIME-Version: 1.0 In-Reply-To: <20150921123902.4c33b061@x140e> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 06:09:46 -0000 >> rm /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94.gz > I have done that 10 times already, it downloads it and complains again. Then it means that the file on the mirror is corrupt. You should try to use a different mirror. From owner-freebsd-questions@freebsd.org Tue Sep 22 12:58:41 2015 Return-Path: Delivered-To: freebsd-questions@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 A5A39A02015 for ; Tue, 22 Sep 2015 12:58:41 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5CE7F1E14 for ; Tue, 22 Sep 2015 12:58:41 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8MCwWif025771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 22 Sep 2015 07:58:33 -0500 Subject: Re: Problem upgrading from 10.1 to 10.2 To: freebsd-questions@freebsd.org References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> <20150921123902.4c33b061@x140e> <5600F0A8.1060900@shopzeus.com> From: "William A. Mahaffey III" Message-ID: <56015078.9090206@hiwaay.net> Date: Tue, 22 Sep 2015 08:04:02 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <5600F0A8.1060900@shopzeus.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 12:58:41 -0000 On 09/22/15 01:15, Nagy László Zsolt wrote: > >>> rm >>> /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94.gz >> I have done that 10 times already, it downloads it and complains again. > Then it means that the file on the mirror is corrupt. You should try > to use a different mirror. How's about someone fix that file on the mirror as well, if it is the default repo/mirror, others might bump into the same thing .... $0.02, no more, no less .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Tue Sep 22 16:10:11 2015 Return-Path: Delivered-To: freebsd-questions@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 0E1A8A06230 for ; Tue, 22 Sep 2015 16:10:11 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from nodeunit.com (mx01.stoianov.me [37.0.34.67]) by mx1.freebsd.org (Postfix) with ESMTP id C72961F38 for ; Tue, 22 Sep 2015 16:10:10 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from x140e (x140e-lan.local.home [10.7.7.4]) by nodeunit.com (Postfix) with ESMTPS id 2293457E41; Tue, 22 Sep 2015 18:10:02 +0200 (CEST) Date: Tue, 22 Sep 2015 18:10:01 +0200 From: George To: "William A. Mahaffey III" Cc: freebsd-questions@freebsd.org Subject: Re: Problem upgrading from 10.1 to 10.2 Message-ID: <20150922181001.474e8232@x140e> In-Reply-To: <56015078.9090206@hiwaay.net> References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> <20150921123902.4c33b061@x140e> <5600F0A8.1060900@shopzeus.com> <56015078.9090206@hiwaay.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 16:10:11 -0000 On Tue, 22 Sep 2015 08:04:02 -0453.75 "William A. Mahaffey III" wrote: > On 09/22/15 01:15, Nagy L=C3=A1szl=C3=B3 Zsolt wrote: > > > >>> rm=20 > >>> /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec= 97cbbecd7b55e72ed94.gz > >> I have done that 10 times already, it downloads it and complains > >> again. > > Then it means that the file on the mirror is corrupt. You should > > try to use a different mirror. >=20 >=20 > How's about someone fix that file on the mirror as well, if it is the=20 > default repo/mirror, others might bump into the same thing .... > $0.02, no more, no less .... >=20 =20 Now I am not able to ping update4.freebsd.org and update1 so I fixed the address to update2 and the first part works now it stops at: ... Applying patches... done Fetching 4716 files... failed. I am in Europe if that helps the people who maintain the servers. How do I go about reporting this to them?? TIA George From owner-freebsd-questions@freebsd.org Tue Sep 22 17:38:17 2015 Return-Path: Delivered-To: freebsd-questions@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 ECBC0A06B8B for ; Tue, 22 Sep 2015 17:38:16 +0000 (UTC) (envelope-from war@dim.lv) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (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 80A001D73 for ; Tue, 22 Sep 2015 17:38:16 +0000 (UTC) (envelope-from war@dim.lv) Received: by wicgb1 with SMTP id gb1so170782145wic.1 for ; Tue, 22 Sep 2015 10:38:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=lhQaZh+NkJsOJaKond5W4kb7GydvG01bCS/nT5GKbiQ=; b=YegUA2aRZ6kZHdWVUXdxvXLLoK+7c3JTj2x0CYWA86TTaRf6RRnN2IFT1nTNrGRCH6 i1ZJhN6vjEyfUJBmWE1/rW/h9Pt9NpS2KNidLKVlpB2SgIW2Ts6xfB+mIOdkgoKW5bhz 8WKvw+g0dPJtUbUTg+DlTaE1rE/tCEPI0XodEXGYSZVBgMYquQRsBYpQd5nZEyFEWj1k +KRexb6vnc53QZhD+9PeQiADq5iPjIUjvNiUOWn3CJJmBoGeI5DlOEf+o7qAb0zm5GbI 6aGOo7cDPfCKQ88823HITHHlh0dLxWFtURJoz7LaUZPYgodwOzyyP1KL0xNqtIpVyOiz jzVA== X-Gm-Message-State: ALoCoQmz8TFj3JUUsaTLJVbVB/UWqWIUq/CH/9X1aIkptw3rgDTf36YX4UH26vi9q29EWqkZYG4O X-Received: by 10.194.240.132 with SMTP id wa4mr26030427wjc.138.1442943494102; Tue, 22 Sep 2015 10:38:14 -0700 (PDT) Received: from [192.168.88.18] (balticom-185-141.balticom.lv. [83.99.185.141]) by smtp.googlemail.com with ESMTPSA id lb10sm2987843wjc.9.2015.09.22.10.38.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Sep 2015 10:38:13 -0700 (PDT) From: Dmitrijs Subject: zfs performance degradation To: freebsd-questions@freebsd.org Message-ID: <56019211.2050307@dim.lv> Date: Tue, 22 Sep 2015 20:38:25 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 17:38:17 -0000 Goog afternoon, I've encountered strange ZFS behavior - serious performance degradation over few days. Right after setup on fresh ZFS (2 hdd in a mirror) I made a test on a file 30Gb size with dd like dd if=test.mkv of=/dev/null bs=64k and got 150+Mbs speed. Today I got only 90Mbs, tested with different blocksizes, many times, speed seems to be stable +-5% nas4free: divx# dd if=test.mkv of=/dev/null bs=64k 484486+1 records in 484486+1 records out 31751303111 bytes transferred in 349.423294 secs (90867734 bytes/sec) Computer\system details: nas4free: /mnt# uname -a FreeBSD nas4free.local 10.2-RELEASE-p2 FreeBSD 10.2-RELEASE-p2 #0 r287260M: Fri Aug 28 18:38:18 CEST 2015 root@dev.nas4free.org:/usr/obj/nas4free/usr/src/sys/NAS4FREE-amd64 amd64 RAM 4Gb I've got brand new 2x HGST HDN724040ALE640, 4Đ¢Đ±, 7200rpm (ada0, ada1) for pool data4. Another pool, data2, performs slightly better even on older\cheaper WD Green 5400 HDDs, up to 99Mbs. nas4free: /mnt# zpool status pool: data2 state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM data2 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 errors: No known data errors pool: data4 state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM data4 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 errors: No known data errors While dd is running, gstat is showing like: dT: 1.002s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 366 366 46648 1.1 0 0 0.0 39.6| ada0 1 432 432 54841 1.0 0 0 0.0 45.1| ada1 so iops are very high, while %busy is quite low. It averages about 50%, rare peaks till 85-90% Even top shows no significant load: last pid: 61983; load averages: 0.44, 0.34, 0.37 up 11+07:51:31 16:44:56 40 processes: 1 running, 39 sleeping CPU: 0.3% user, 0.0% nice, 6.4% system, 1.1% interrupt, 92.1% idle Mem: 21M Active, 397M Inact, 2101M Wired, 56M Cache, 94M Buf, 1044M Free ARC: 1024M Total, 232M MFU, 692M MRU, 160K Anon, 9201K Header, 91M Other Swap: 4096M Total, 4096M Free Not displaying idle processes. PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 61981 root 1 30 0 12364K 2084K zio->i 3 0:09 18.80% dd 61966 root 1 22 0 58392K 7144K select 3 0:24 3.86% proftpd Zpool list: nas4free: /mnt# zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT data2 1.81T 578G 1.25T - 11% 31% 1.00x ONLINE - data4 3.62T 2.85T 797G - 36% 78% 1.00x ONLINE - Could it happen because of pool being 78% full? So I cannot fill puls full? Can anyone please advice how could I fix the situation - or is it normal? I've googled a lot about vmaxnodes, vminnodes but advices are mostly controversial and doesn't help. I can provide additional system output on request. best regards, Dmitry From owner-freebsd-questions@freebsd.org Tue Sep 22 22:27:06 2015 Return-Path: Delivered-To: freebsd-questions@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 BE38DA06184 for ; Tue, 22 Sep 2015 22:27:06 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (70-90-202-97-Albuquerque.hfc.comcastbusiness.net [70.90.202.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84D621A69 for ; Tue, 22 Sep 2015 22:27:05 +0000 (UTC) (envelope-from reg@dwf.com) Received: from deneb.dwf.com (localhost [127.0.0.1]) by deneb.dwf.com (8.14.4/8.14.3) with ESMTP id t8MMQwro001022; Tue, 22 Sep 2015 16:26:58 -0600 Message-Id: <201509222226.t8MMQwro001022@deneb.dwf.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-questions@freebsd.org, reg@deneb.dwf.com Subject: EXMH Font problem, Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Sep 2015 16:26:58 -0600 From: reg@dwf.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 22:27:06 -0000 Im trying to run the EXMH mail reader (from ports). It took one addition (from this list) to get it to compile, but with that it runs, but there is one problem. If one tries to popup either of the 'More' popups of commands, the popup appears (with the right height) but all the entries are blank. Thinking that this might be a font problem (tho the preferences popup(s) work just fine) I tried the preferences/font popup, and this immediately kills exmh. So, anyone have a workarround for this problem? -- Reg.Clemens reg@dwf.com From owner-freebsd-questions@freebsd.org Wed Sep 23 06:43:57 2015 Return-Path: Delivered-To: freebsd-questions@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 E3170A07A36 for ; Wed, 23 Sep 2015 06:43:57 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 75EDE1B37 for ; Wed, 23 Sep 2015 06:43:56 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-169-30.lns20.adl6.internode.on.net (HELO leader.local) ([118.210.169.30]) by ipmail05.adl6.internode.on.net with ESMTP; 23 Sep 2015 16:13:49 +0930 Subject: Re: Problem upgrading from 10.1 to 10.2 To: George References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> <20150921123902.4c33b061@x140e> <5600F0A8.1060900@shopzeus.com> <56015078.9090206@hiwaay.net> <20150922181001.474e8232@x140e> Cc: freebsd-questions@freebsd.org From: Shane Ambler Message-ID: <56024A21.70207@ShaneWare.Biz> Date: Wed, 23 Sep 2015 16:13:45 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150922181001.474e8232@x140e> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 06:43:58 -0000 On 23/09/2015 01:40, George wrote: > On Tue, 22 Sep 2015 08:04:02 -0453.75 > "William A. Mahaffey III" wrote: > >> On 09/22/15 01:15, Nagy LĂƒÂ¡szlĂƒÂ³ Zsolt wrote: >>> >>>>> rm >>>>> /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27ec97cbbecd7b55e72ed94.gz >>>> I have done that 10 times already, it downloads it and complains >>>> again. >>> Then it means that the file on the mirror is corrupt. You should >>> try to use a different mirror. >> >> >> How's about someone fix that file on the mirror as well, if it is the >> default repo/mirror, others might bump into the same thing .... >> $0.02, no more, no less .... >> > > Now I am not able to ping update4.freebsd.org and update1 so I fixed > the address to update2 and the first part works now it stops at: > > ... > Applying patches... done > Fetching 4716 files... failed. > > I am in Europe if that helps the people who maintain the servers. How > do I go about reporting this to them?? You can report bugs at https://bugs.freebsd.org/bugzilla/ -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-questions@freebsd.org Wed Sep 23 17:07:55 2015 Return-Path: Delivered-To: freebsd-questions@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 975E8A0790F for ; Wed, 23 Sep 2015 17:07:55 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com [209.85.192.50]) (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 579F31994 for ; Wed, 23 Sep 2015 17:07:54 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgev79 with SMTP id v79so24497413qge.0 for ; Wed, 23 Sep 2015 10:07:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=HHFQEINQgoD2lEw8/6dCWVsNRzIfg1JZv1RSgynHLCo=; b=m4kQqxMzTTlWhJa/p4nmV3mG4tBdOX157/Z52so74P36pgG1nBwHZaGw/Unem5n+86 PzOsFV2HKWrDUTmN+YBdISCSF/VVTjIkMch020kjBd8IeT0oC4iJW3yVqstFpjVeoK/3 SHezwVfXXU+v4ZzluV7kaV/XPGG4W4+ymK5yhJeMZq3+i3Q3VxlmD1mo5gCtYHR40Skc IGk6vzuwWzoSRx240BFBgJRy0OQ+r+LMg1TxSwEAF0fLg7onn2HRK/J8s+JXW2+gajTa 1pweq9MBcrG5emkEKHHuuGYV8YQtH6CTKEsBrCRJDZ1wpU+TNqSCHhxk1jJpKS1+41TV 9DRg== X-Gm-Message-State: ALoCoQktpCHgExhTshAYsXW7x2RckHWpg+3x/4CoqGErV6Q7eiNLx7eLobhw9Ap3tqujJzBZk0dz X-Received: by 10.140.96.200 with SMTP id k66mr37328549qge.81.1443028074154; Wed, 23 Sep 2015 10:07:54 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id g82sm2842366qhc.32.2015.09.23.10.07.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Sep 2015 10:07:52 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Name/label/id metadata: how do I make it go away From: Paul Kraus In-Reply-To: <5601CB85.8070400@stankevitz.com> Date: Wed, 23 Sep 2015 13:07:49 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> References: <56004C68.4020904@stankevitz.com> <5600F0DF.8000805@stankevitz.com> <5601A82A.7040304@stankevitz.com> <5601B2AF.7040306@stankevitz.com> <5601CB85.8070400@stankevitz.com> To: Chris Stankevitz , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 17:07:55 -0000 On Sep 22, 2015, at 17:43, Chris Stankevitz = wrote: > And if I want to dig deeper into root cause I can ask ZFS "why do you = sometimes select from the consumer collection and sometimes from the = provider collection when putting a pool together". Or if I don't want = to dig deeper I can "deal with it" or I can disable diskid using = kern.geom.label.disk_ident.enable Assuming 10.x, on boot the ZFS code scans all attached devices and = attempts to reassemble any zpools that it finds that were owned by this = system. I suspect which device ZFS uses is based on which it scans (and = finds) first. I actually prefer the /dev/diskid/nnn names as those are tied to the = physical drives. By using them I guarantee that even if a drive = physically (or logically if drives or controllers are added) moves the = system can still find and import the zpool. In the early days of ZFS one = of the best ways to damage a zpool was to rearrange drives so that the = ZFS label (and cache) no longer agreed with reality. I was in the habit = of manually exporting critical zpools before making any hardware changes = and after the changes were complete I would import the pool (sometime = with new device names). ZFS _should_ be robust enough to handle device = movement today, but I am slightly paranoid when it comes to critical = data. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Wed Sep 23 20:08:41 2015 Return-Path: Delivered-To: freebsd-questions@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 21F5BA0619D for ; Wed, 23 Sep 2015 20:08:41 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (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 DB4AE1CD7 for ; Wed, 23 Sep 2015 20:08:40 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgez77 with SMTP id z77so28959013qge.1 for ; Wed, 23 Sep 2015 13:08:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=k2pfNT8WzQ9TsI8zc7+k28sIYpQqn2jmO8fTOy4ulOw=; b=W808luuA08KrZIYFZVKIp4F63kXnRFl5plW6wbw80bFT5Z8T0jS6yu+Q5PrS75ItWy AIHsKXIV4RsLRz9ZjRULVPwl8Bkz+h/t33x9H3fWaVkMMmHcMdMs48hwoXnfdEnoxkP7 zwvuex59JT0tv3bc08LjVm7/BNfZNyTkefic1Sk5LmttDOyHUP+Rupa3UF4UsQGq58vM z7Dg1YFDVNFfLZeyyvB3WV/MuGdg3UBiYzWpQvXkJjIHNpqL4/NP7ASBqMCsJFnjmKov D7o3WzD4zirA5dH+kjLqlVrp2OV7liXT6nrCvdCG/ixKv2U2YUe+Qdt2ThMbNcMj2cPZ raYA== X-Gm-Message-State: ALoCoQkIqVju6Fz53qoDlnvDtpxliW9swekMZTkzkYkKwgnrbh3zmjyN0xo/OZuGNo3YmB86WcUp X-Received: by 10.140.196.193 with SMTP id r184mr40433556qha.77.1443038919068; Wed, 23 Sep 2015 13:08:39 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id 103sm2094134qgx.35.2015.09.23.13.08.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Sep 2015 13:08:37 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: zfs performance degradation From: Paul Kraus In-Reply-To: <56019211.2050307@dim.lv> Date: Wed, 23 Sep 2015 16:08:32 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> References: <56019211.2050307@dim.lv> To: Dmitrijs , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:08:41 -0000 On Sep 22, 2015, at 13:38, Dmitrijs wrote: > I've encountered strange ZFS behavior - serious performance = degradation over few days. Right after setup on fresh ZFS (2 hdd in a = mirror) I made a test on a file 30Gb size with dd like > dd if=3Dtest.mkv of=3D/dev/null bs=3D64k > and got 150+Mbs speed. > I've got brand new 2x HGST HDN724040ALE640, 4=D0=A2=D0=B1, 7200rpm = (ada0, ada1) for pool data4. > Another pool, data2, performs slightly better even on older\cheaper WD = Green 5400 HDDs, up to 99Mbs. > Zpool list: >=20 > nas4free: /mnt# zpool list > NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH = ALTROOT > data2 1.81T 578G 1.25T - 11% 31% 1.00x ONLINE - > data4 3.62T 2.85T 797G - 36% 78% 1.00x ONLINE - >=20 >=20 > Could it happen because of pool being 78% full? So I cannot fill puls = full? > Can anyone please advice how could I fix the situation - or is it = normal? ZFS write performance degrades very steeply when you reach a certain = point in terms of zpool capacity. The exact threshold depends on many = factors including your specific workload. This is essentially due to the = =E2=80=9CCopy on Write=E2=80=9D (CoW) nature of ZFS. When you write to = an existing file ZFS needs to find space for that write operation as it = does not overwrite the existing data. As the zpool fills, it becomes = harder and harder to find contiguous free space and the write operation = ends up fragmenting the data. But, you are seeing READ performance drop. If the file was written when = the ZFS was new (it was one of the first files written) then it is = certainly un-fragmented. But, if you ran the READ test shortly after = writing the file, then some of it will still be in the ARC (Adaptive = Reuse Cache). If there is other activity on the system, then the other = activity will also be using the ARC. If you are rewriting the test file and then reading it, the test file = will be fragmented and that will be part of the performance difference. For my systems (generally VMs using VBox) I have found that 80% is a = good threshold because when I get to 85% capacity the performance drops = to the point where VM I/O starts timing out. So the short answer (way too late for that) is that you can, in fact, = not use all of the capacity of a zpool unless the data is written once, = never modified, and you do not have any snapshots, clones, or the like. P.S. I assume you are not using DeDupe ? You do not have anywhere enough = RAM for that. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Wed Sep 23 20:42:55 2015 Return-Path: Delivered-To: freebsd-questions@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 44786A07A5D for ; Wed, 23 Sep 2015 20:42:55 +0000 (UTC) (envelope-from healer@rpi.edu) Received: from smtp9.server.rpi.edu (gateway.canit.rpi.edu [128.113.2.229]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "canit.localdomain", Issuer "canit.localdomain" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0609A1961 for ; Wed, 23 Sep 2015 20:42:54 +0000 (UTC) (envelope-from healer@rpi.edu) Received: from smtp-auth2.server.rpi.edu (route.canit.rpi.edu [128.113.2.232]) by smtp9.server.rpi.edu (8.14.3/8.14.3/Debian-9.4) with ESMTP id t8NKd64E015218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 23 Sep 2015 16:39:06 -0400 Received: from smtp-auth2.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth2.server.rpi.edu (Postfix) with ESMTP id 11EDB18112 for ; Wed, 23 Sep 2015 16:39:06 -0400 (EDT) Received: from [129.161.61.54] (biotech-lower-wl-295.dynamic2.rpi.edu [129.161.61.54]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: healer) by smtp-auth2.server.rpi.edu (Postfix) with ESMTPSA id F2AF918105 for ; Wed, 23 Sep 2015 16:39:02 -0400 (EDT) Subject: Re: zfs performance degradation To: freebsd-questions@freebsd.org References: <56019211.2050307@dim.lv> From: Bob Healey Message-ID: <56030DE8.20009@rpi.edu> Date: Wed, 23 Sep 2015 16:39:04 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <56019211.2050307@dim.lv> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 7.10] X-CanIt-Incident-Id: 02PkID6TX X-CanIt-Geo: ip=129.161.61.54; country=US; region=Connecticut; city=Hartford; latitude=41.7424; longitude=-72.6905; http://maps.google.com/maps?q=41.7424,-72.6905&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.229 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:42:55 -0000 That sounds similar to the issues I posted about 10 days ago, but my issues seem to be more time than capacity based and go away on reboot. I haven't had time to follow up on my thread due to more pressing issues at work involving Microsoft products, but its still on my TODO list. Bob Healey Systems Administrator Biocomputation and Bioinformatics Constellation and Molecularium healer@rpi.edu (518) 276-4407 On 9/22/2015 1:38 PM, Dmitrijs wrote: > Goog afternoon, > > I've encountered strange ZFS behavior - serious performance > degradation over few days. Right after setup on fresh ZFS (2 hdd in a > mirror) I made a test on a file 30Gb size with dd like > dd if=test.mkv of=/dev/null bs=64k > and got 150+Mbs speed. > > Today I got only 90Mbs, tested with different blocksizes, many times, > speed seems to be stable +-5% > > nas4free: divx# dd if=test.mkv of=/dev/null bs=64k > 484486+1 records in > 484486+1 records out > 31751303111 bytes transferred in 349.423294 secs (90867734 bytes/sec) > > > > Computer\system details: > > nas4free: /mnt# uname -a > FreeBSD nas4free.local 10.2-RELEASE-p2 FreeBSD 10.2-RELEASE-p2 #0 > r287260M: Fri Aug 28 18:38:18 CEST 2015 > root@dev.nas4free.org:/usr/obj/nas4free/usr/src/sys/NAS4FREE-amd64 amd64 > > RAM 4Gb > I've got brand new 2x HGST HDN724040ALE640, 4Đ¢Đ±, 7200rpm (ada0, ada1) > for pool data4. > Another pool, data2, performs slightly better even on older\cheaper WD > Green 5400 HDDs, up to 99Mbs. > > > nas4free: /mnt# zpool status > pool: data2 > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > data2 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > > errors: No known data errors > > pool: data4 > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > data4 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > > errors: No known data errors > > > While dd is running, gstat is showing like: > > dT: 1.002s w: 1.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > 0 366 366 46648 1.1 0 0 0.0 39.6| ada0 > 1 432 432 54841 1.0 0 0 0.0 45.1| ada1 > > > > so iops are very high, while %busy is quite low. It averages about > 50%, rare peaks till 85-90% > > Even top shows no significant load: > > last pid: 61983; load averages: 0.44, 0.34, 0.37 up 11+07:51:31 16:44:56 > 40 processes: 1 running, 39 sleeping > CPU: 0.3% user, 0.0% nice, 6.4% system, 1.1% interrupt, 92.1% idle > Mem: 21M Active, 397M Inact, 2101M Wired, 56M Cache, 94M Buf, 1044M Free > ARC: 1024M Total, 232M MFU, 692M MRU, 160K Anon, 9201K Header, 91M Other > Swap: 4096M Total, 4096M Free > Not displaying idle processes. > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 61981 root 1 30 0 12364K 2084K zio->i 3 0:09 18.80% dd > 61966 root 1 22 0 58392K 7144K select 3 0:24 3.86% proftpd > > > > Zpool list: > > nas4free: /mnt# zpool list > NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT > data2 1.81T 578G 1.25T - 11% 31% 1.00x ONLINE - > data4 3.62T 2.85T 797G - 36% 78% 1.00x ONLINE - > > > Could it happen because of pool being 78% full? So I cannot fill puls > full? > Can anyone please advice how could I fix the situation - or is it normal? > I've googled a lot about vmaxnodes, vminnodes but advices are mostly > controversial and doesn't help. > I can provide additional system output on request. > > best regards, > Dmitry > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Wed Sep 23 20:53:36 2015 Return-Path: Delivered-To: freebsd-questions@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 E2A77A07FBB for ; Wed, 23 Sep 2015 20:53:36 +0000 (UTC) (envelope-from chris@stankevitz.com) Received: from mango.stankevitz.com (mango.stankevitz.com [208.79.93.194]) by mx1.freebsd.org (Postfix) with ESMTP id CE4F81FF3 for ; Wed, 23 Sep 2015 20:53:36 +0000 (UTC) (envelope-from chris@stankevitz.com) Received: from Chriss-MacBook-Pro.local (209-203-101-124.static.twtelecom.net [209.203.101.124]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mango.stankevitz.com (Postfix) with ESMTPSA id 312BC1308; Wed, 23 Sep 2015 13:53:30 -0700 (PDT) Subject: Re: Name/label/id metadata: how do I make it go away To: Paul Kraus , FreeBSD Questions References: <56004C68.4020904@stankevitz.com> <5600F0DF.8000805@stankevitz.com> <5601A82A.7040304@stankevitz.com> <5601B2AF.7040306@stankevitz.com> <5601CB85.8070400@stankevitz.com> <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> From: Chris Stankevitz Message-ID: <5603114C.2060105@stankevitz.com> Date: Wed, 23 Sep 2015 13:53:32 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:53:37 -0000 On 9/23/15 10:07 AM, Paul Kraus wrote: > I actually prefer the /dev/diskid/nnn names as those are tied to the > physical drives. By using them I guarantee that even if a drive > physically (or logically if drives or controllers are added) moves > the system can still find and import the zpool. In the early days of > ZFS one of the best ways to damage a zpool was to rearrange drives so > that the ZFS label (and cache) no longer agreed with reality. I was > in the habit of manually exporting critical zpools before making any > hardware changes and after the changes were complete I would import > the pool (sometime with new device names). ZFS _should_ be robust > enough to handle device movement today, but I am slightly paranoid > when it comes to critical data. Paul, I feel the same way about my data. Like you, I am paranoid and I want to understand exactly what is going on. How can I guarantee that my data is safe when I'm at a loss to explain why my "zpool status" is such a mess? Can you tell me how you go about "preferring and using diskids" when you import a zpool? Do you always import on the command line using "zpool import -d"? Thank you, Chris From owner-freebsd-questions@freebsd.org Wed Sep 23 21:34:39 2015 Return-Path: Delivered-To: freebsd-questions@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 BB380A0721A for ; Wed, 23 Sep 2015 21:34:39 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) (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 780661A5F for ; Wed, 23 Sep 2015 21:34:38 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkdw123 with SMTP id w123so22860515qkd.0 for ; Wed, 23 Sep 2015 14:34:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=iauLD8CfSbLO+YxCUBCUS5WGUG2HMBzKg62Dno0rK58=; b=A/NFRms+IDgWQnXsNMSXPdSlGD49KL9ZcEfDz2l2pepvMSrWqf4H/uzAQTP5rLZ8CY jwBaQN80fzX0o6Y6foHMNRRGl3mnxTkTcyKpLWC1Xgvnd0DlxD/zjAIczQfVsHlgMN4X GanM9oLY4hdAedlDcGilOP+EkkAATyxkYoIXvjqLXEfjIH38TZzCb9YrtzTrXG99rBFY RDbd6Tzddswl/XF8PVUpWOLVedIy0RNTh4ys9RSlPOJpTSOy2FhqQks3cve36oQRsYlQ unKXwiPCzguVo7lDeeFeUQUtYrTtVl7eaElBcMG/8fhvJdSzNQJb6pp6CLO5K9jVhDg6 /Vaw== X-Gm-Message-State: ALoCoQlOw3PxLZUDOLUR3lpNCgTbVCdj+DZhbK79oGQ1h9keDTxHVF0txi1tRWQNlkx59HM+95t/ X-Received: by 10.55.54.75 with SMTP id d72mr39547735qka.52.1443042422207; Wed, 23 Sep 2015 14:07:02 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id s89sm3239831qks.36.2015.09.23.14.07.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Sep 2015 14:07:00 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Name/label/id metadata: how do I make it go away From: Paul Kraus In-Reply-To: <5603114C.2060105@stankevitz.com> Date: Wed, 23 Sep 2015 17:06:55 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <56004C68.4020904@stankevitz.com> <5600F0DF.8000805@stankevitz.com> <5601A82A.7040304@stankevitz.com> <5601B2AF.7040306@stankevitz.com> <5601CB85.8070400@stankevitz.com> <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> <5603114C.2060105@stankevitz.com> To: Chris Stankevitz , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 21:34:39 -0000 On Sep 23, 2015, at 16:53, Chris Stankevitz = wrote: > I feel the same way about my data. Like you, I am paranoid and I want = to understand exactly what is going on. How can I guarantee that my = data is safe when I'm at a loss to explain why my "zpool status" is such = a mess? >=20 > Can you tell me how you go about "preferring and using diskids" when = you import a zpool? Do you always import on the command line using = "zpool import -d=94? I create the zpool using the /dev/diskid/nnn device names. If I build = the zpool using those device names I have not had ZFS use any others on = import. When I have a zpool that does not use the diskid device names I usually = (and very carefully) replace the device with one using the diskid name. = You clearly can=92t do that =93in-place=94 with RAIDz vdevs, but for = mirrors I take the small risk by removing one of the mirror components = and then attach it using the diskid name. If you have even one =93spare=94 drive you can do a walking replacement = of one device at a time to the new naming scheme. I have not run into the exact case you have with device names but no = idea (really) where they came from. If your zpool started under FreeNAS, then you need to be looking at how = 9.x handles device names to figure out where they came from. As far as I = know, FreeNAS is still 9.x based. NOTE: I am running 10.0 and 10.1, I have not gone to 10.2 yet. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 04:47:29 2015 Return-Path: Delivered-To: freebsd-questions@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 E1417A07B5E for ; Thu, 24 Sep 2015 04:47:29 +0000 (UTC) (envelope-from war@dim.lv) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 826CF1880 for ; Thu, 24 Sep 2015 04:47:28 +0000 (UTC) (envelope-from war@dim.lv) Received: by wicge5 with SMTP id ge5so235026877wic.0 for ; Wed, 23 Sep 2015 21:47:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=s0YUVKN7Y0b3LsIjQUMuAvX0Zf974zoc/YZ215s/Ox0=; b=QSEDkGgvMiEBECEihUAdP9k7YEzR59yczy3RnFZJoKtOoxdZA8uTbRo13LpC5ES8uW LRNHp+d+T5esp4T4HFzZhoYa7yznVT2pcSD3VFWuD2pDmJaqqbKU0jN3rlnAUm6bMesW tpC4XSPkbK3zZWMLUX7oQNCbEBnn3wSCtBtROzSag5qDbDUd6IsVpD2IX7DjmnbBDrVm gIQn5KGWCQ0tRZYpaZgUvFNmfEIvQ29GAvV8KcmSeUpwMP/RNzqGJslMbtAM39NTbFzc Iw8CHfhrEPX+8f4Ofe8wWfBsOqs9pmPL54JCoRptzHkQaQ3+JhjCqSHo9E5nFISGYxr7 DVHQ== X-Gm-Message-State: ALoCoQni4Y9z4OhBoDVQjYqW68eoPvPnm0Hwi8r8fwrwu47LBhME2xb5hYBKasQs0ciN5zWza5pF X-Received: by 10.194.248.234 with SMTP id yp10mr44607939wjc.24.1443070041598; Wed, 23 Sep 2015 21:47:21 -0700 (PDT) Received: from [192.168.88.18] (balticom-185-141.balticom.lv. [83.99.185.141]) by smtp.googlemail.com with ESMTPSA id gt4sm3477132wib.21.2015.09.23.21.47.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Sep 2015 21:47:20 -0700 (PDT) Subject: Re: zfs performance degradation To: Paul Kraus , freebsd-questions@freebsd.org References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> From: Dmitrijs Message-ID: <56038054.5060906@dim.lv> Date: Thu, 24 Sep 2015 07:47:16 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 04:47:30 -0000 2015.09.23. 23:08, Paul Kraus Đ¿Đ¸ÑˆĐµÑ‚: > On Sep 22, 2015, at 13:38, Dmitrijs wrote: > >> I've encountered strange ZFS behavior - serious performance degradation over few days. >> >> Could it happen because of pool being 78% full? So I cannot fill puls full? >> Can anyone please advice how could I fix the situation - or is it normal? > > So the short answer (way too late for that) is that you can, in fact, not use all of the capacity of a zpool unless the data is written once, never modified, and you do not have any snapshots, clones, or the like. > > P.S. I assume you are not using DeDupe ? You do not have anywhere enough RAM for that. > > -- > Paul Kraus > paul@kraus-haus.org > Thank you very much for explanation. Am I getting it right - it will not work faster even if I add +4Gb RAM to be 8Gb in total? I am not using DeDuplication and compression, neither planing using them. I've also put down a lot of research for situation here: http://forums.nas4free.org/viewtopic.php?f=66&t=9595 In short: you are right, everything getting slowly when pool fills up. So if I plan to work with data a lot, get decent performance and still be sure I'm on the safe side with mirror-raid1, should I choose another filesystem? Especially, if i do not really need snapshots, clones, etc. Or is it not possible at all, and I should put something like raid0 for work and tolerate slow backup on raid1 at nights? best regards, Dmitriy From owner-freebsd-questions@freebsd.org Thu Sep 24 06:07:34 2015 Return-Path: Delivered-To: freebsd-questions@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 A8CB9A07CE6 for ; Thu, 24 Sep 2015 06:07:34 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::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 3798517B8 for ; Thu, 24 Sep 2015 06:07:34 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by wicge5 with SMTP id ge5so236765969wic.0 for ; Wed, 23 Sep 2015 23:07:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=aMdVze9/rt30cBSBPw0AuWhmJRNClVarIQ65UVWjR58=; b=UH9UpipPgu9n/QBoHSNSHeKnewa+Gl8edKvdJGQh3A6WLgXqyix63DlADJStvBZP7j TQVBnbiZ75F1e+rNuZ9wEOuGvqRtFrxcM83KUJzFfY6ET1nPx1yOd9bGNARp810VgPjq 1xpwxaQg+5xiTbk/UDX+zUjg9cSrhquK79QtpKoIFpLeuDLVLuOiMPQ1eqryEqVLaHFE 4usEaGmE04rmOuDDAcBflfSgWOVXFzup1xV2MAYGMMUy8Pq7eANwr5HiLLdBmI4eoixJ yaBgefFulElXgQouBlzwcxDhiU23JpXPMYxqgNpyMJLLbE8sCotEup/QyQo6kaqvOveu WTqA== MIME-Version: 1.0 X-Received: by 10.194.174.227 with SMTP id bv3mr43408641wjc.142.1443074851753; Wed, 23 Sep 2015 23:07:31 -0700 (PDT) Received: by 10.194.16.231 with HTTP; Wed, 23 Sep 2015 23:07:31 -0700 (PDT) In-Reply-To: <56019211.2050307@dim.lv> References: <56019211.2050307@dim.lv> Date: Thu, 24 Sep 2015 01:07:31 -0500 Message-ID: Subject: Re: zfs performance degradation From: Adam Vande More To: Dmitrijs Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 06:07:34 -0000 On Tue, Sep 22, 2015 at 12:38 PM, Dmitrijs wrote: > Goog afternoon, > > I've encountered strange ZFS behavior - serious performance degradation > over few days. Right after setup on fresh ZFS (2 hdd in a mirror) I made = a > test on a file 30Gb size with dd like > dd if=3Dtest.mkv of=3D/dev/null bs=3D64k > and got 150+Mbs speed. > > Today I got only 90Mbs, tested with different blocksizes, many times, > speed seems to be stable +-5% > I doubt that. Block sizes have a large impact on dd read efficiency regardless of the filesystem. So unless you were testing the speed of cached data, there would have been a significant difference between runs of different block sizes. > > nas4free: divx# dd if=3Dtest.mkv of=3D/dev/null bs=3D64k > 484486+1 records in > 484486+1 records out > 31751303111 bytes transferred in 349.423294 secs (90867734 bytes/sec) > Perfectly normal for the parameters you've imposed. What happens if you use bs=3D1m? > Computer\system details: > > nas4free: /mnt# uname -a > FreeBSD nas4free.local 10.2-RELEASE-p2 FreeBSD 10.2-RELEASE-p2 #0 > r287260M: Fri Aug 28 18:38:18 CEST 2015 root@dev.nas4free.org:/usr/obj/na= s4free/usr/src/sys/NAS4FREE-amd64 > amd64 > > RAM 4Gb > I've got brand new 2x HGST HDN724040ALE640, 4=D0=A2=D0=B1, 7200rpm (ada0,= ada1) for > pool data4. > Another pool, data2, performs slightly better even on older\cheaper WD > Green 5400 HDDs, up to 99Mbs. > What parameters for both are you using here to make this claim? > > While dd is running, gstat is showing like: > > dT: 1.002s w: 1.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > 0 366 366 46648 1.1 0 0 0.0 39.6| ada0 > 1 432 432 54841 1.0 0 0 0.0 45.1| ada1 > > > > so iops are very high, while %busy is quite low. %busy is a misunderstood stat. Do not use it to evaluate if your drive is being utilized efficiently. L(q), ops and seek times are what is interesting. > It averages about 50%, rare peaks till 85-90% > Basically as close to perfect as you'll ever get considering how you invoked dd. ZFS doesn't split sequential reads across a vdev, only a pool and that's only if multiple vdev's were in the pool when the file was written. Your testing methodology is poorly thought and implemented, or at least the way it was presented to us. Testing needing to a methodical, repeatable, testable process accounting for all the variables involved. All I saw was a bunch of haphazard and scattered attempts to test sequential read speed of a ZFS mirror. Is that really an accurate test of the pool workload? Did you clear caches between tests? Why are there other daemons running like proftpd during the testing? Etc, ad nauseam. --=20 Adam From owner-freebsd-questions@freebsd.org Thu Sep 24 09:21:37 2015 Return-Path: Delivered-To: freebsd-questions@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 620BEA07A38 for ; Thu, 24 Sep 2015 09:21:37 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from nodeunit.com (nodeunit.ch [37.0.34.67]) by mx1.freebsd.org (Postfix) with ESMTP id 25B8310D5 for ; Thu, 24 Sep 2015 09:21:36 +0000 (UTC) (envelope-from g.lister@nodeunit.ch) Received: from x140e (x140e-lan.local.home [10.7.7.4]) by nodeunit.com (Postfix) with ESMTPS id 3469D56D79; Thu, 24 Sep 2015 11:21:28 +0200 (CEST) Date: Thu, 24 Sep 2015 11:21:27 +0200 From: George To: Shane Ambler Cc: freebsd-questions@freebsd.org Subject: Re: Problem upgrading from 10.1 to 10.2 Message-ID: <20150924112127.584c2918@x140e> In-Reply-To: <56024A21.70207@ShaneWare.Biz> References: <20150917212506.2334162a@asrock-lan.local.home> <55FF92E9.7090204@shopzeus.com> <20150921123902.4c33b061@x140e> <5600F0A8.1060900@shopzeus.com> <56015078.9090206@hiwaay.net> <20150922181001.474e8232@x140e> <56024A21.70207@ShaneWare.Biz> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 09:21:37 -0000 On Wed, 23 Sep 2015 16:13:45 +0930 Shane Ambler wrote: > On 23/09/2015 01:40, George wrote: > > On Tue, 22 Sep 2015 08:04:02 -0453.75 > > "William A. Mahaffey III" wrote: > > > >> On 09/22/15 01:15, Nagy L=C3=83=C2=A1szl=C3=83=C2=B3 Zsolt wrote: > >>> > >>>>> rm > >>>>> /var/db/freebsd-update/|143f5cd95cd065b2adb90da82ee4b22489babe56a27= ec97cbbecd7b55e72ed94.gz > >>>> I have done that 10 times already, it downloads it and complains > >>>> again. > >>> Then it means that the file on the mirror is corrupt. You should > >>> try to use a different mirror. > >> > >> > >> How's about someone fix that file on the mirror as well, if it is > >> the default repo/mirror, others might bump into the same thing .... > >> $0.02, no more, no less .... > >> > > > > Now I am not able to ping update4.freebsd.org and update1 so I fixed > > the address to update2 and the first part works now it stops at: > > > > ... > > Applying patches... done > > Fetching 4716 files... failed. > > > > I am in Europe if that helps the people who maintain the servers. > > How do I go about reporting this to them?? >=20 > You can report bugs at https://bugs.freebsd.org/bugzilla/ >=20 >=20 For the record, after opening the bug report and being prompted to look with a browser... I remembered that all access goes through a proxy I disabled the proxy for the machine and everything worked as expected. There are no issues reported on the proxy end oddly enough but freebsd-update just says download failed... I guess a timeout of some sort. Thanks to everyone. I am installing the upgrade now. Cheers, George From owner-freebsd-questions@freebsd.org Thu Sep 24 12:52:44 2015 Return-Path: Delivered-To: freebsd-questions@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 1BEA6A08D03 for ; Thu, 24 Sep 2015 12:52:44 +0000 (UTC) (envelope-from raimund.sacherer@logitravel.com) Received: from formentor.toolfactory.net (pina.toolfactory.net [213.97.158.39]) by mx1.freebsd.org (Postfix) with ESMTP id B7D0211D9 for ; Thu, 24 Sep 2015 12:52:43 +0000 (UTC) (envelope-from raimund.sacherer@logitravel.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by formentor.toolfactory.net (Postfix) with ESMTP id 712C01786EE for ; Thu, 24 Sep 2015 14:42:42 +0200 (CEST) Received: from formentor.toolfactory.net ([127.0.0.1]) by localhost (formentor.toolfactory.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Ll_Az9uZ_b9Q for ; Thu, 24 Sep 2015 14:42:42 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by formentor.toolfactory.net (Postfix) with ESMTP id 07F5A1786ED for ; Thu, 24 Sep 2015 14:42:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at logpmzimmta01v.toolfactory.net Received: from formentor.toolfactory.net ([127.0.0.1]) by localhost (formentor.toolfactory.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vI8znpZze_fJ for ; Thu, 24 Sep 2015 14:42:41 +0200 (CEST) Received: from xorrigo.toolfactory.net (xorrigo.toolfactory.net [192.168.2.210]) by formentor.toolfactory.net (Postfix) with ESMTP id E4D221786E2 for ; Thu, 24 Sep 2015 14:42:41 +0200 (CEST) Date: Thu, 24 Sep 2015 14:42:41 +0200 (CEST) From: Raimund Sacherer Reply-To: Raimund Sacherer To: FreeBSD Questions Message-ID: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> In-Reply-To: <1059990807.9456607.1443097747193.JavaMail.zimbra@logitravel.com> Subject: Restructure a ZFS Pool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.2.213] X-Mailer: Zimbra 8.0.8_GA_6184 (ZimbraWebClient - SAF7 (Mac)/8.0.8_GA_6184) Thread-Topic: Restructure a ZFS Pool Thread-Index: rucbOPvwfEmoBa+0XQ6LmkN/GW7+5w== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 12:52:44 -0000 Hello, I have a ZFS pool consisting of 12 4TB drives, where 2 of those drives are dedicated as spares, as this was my first FreeBSD / ZFS server I did some things different than I would do it know and I want to rectify them: # zpool status pool: tank state: ONLINE scan: scrub repaired 0 in 58h52m with 0 errors on Thu Sep 24 02:29:47 2015 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 spares da10 AVAIL da11 AVAIL errors: No known data errors I had the pool fill up to over 80%, then I got it back to about 50-60%, but it feels more sluggish. I use a lot of NFS and we use it to backup some 5 million files in lots of sub-directorys (a/b/c/d/abcd...), besides other big files (SQL dump backups, bacula, etc.) I said above sluggish because I do not have empirical data and I do not know exactly how to test the system correctly, but I read a lot and there seem to be suggestions that if you have NFS etc. that a independent ZIL helps with copy-on-write fragmentation. What I would like to know is if I can eliminate one Spare disk from the pool, and add it as a ZIL again, without having to shutdown/reboot the server? I am also thinking about swapping the spare 4TB disk for a small SSD, but that's immaterial to whether I can perform the change. Also I would appreciate it if someone has some pointers on how to test correctly so I see if there are real benefits before/after this operation. Thank you, Best Ray From owner-freebsd-questions@freebsd.org Thu Sep 24 13:17:08 2015 Return-Path: Delivered-To: freebsd-questions@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 069B4A07FD2 for ; Thu, 24 Sep 2015 13:17:08 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) (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 BEBAC1276 for ; Thu, 24 Sep 2015 13:17:07 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkdw123 with SMTP id w123so29294998qkd.0 for ; Thu, 24 Sep 2015 06:17:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=ZcSzKDTGCsjez3uskXiMSKo3PE47Owc2XlF13o6oGAE=; b=it3l1oeHy4zRy4iGW3DqfBnZSwhBDbbs0ATRx65KDMM2jBFL+Ojov3KGn+mxKzCrs4 u5bLusyAzbvadr0JI3/9L9W4S1HAaO5x52i8idk2D/H9nAaH5Q+PuAG/lLJmkodOav6D tT2AMJa+ofX4WxlDmsaRsl9mhuTFuC0Qyn/iWF3AyKRJybNj44DxEsDNY81RIEV2uNT0 C0hVoPOeRnTEyIyR9NqnVRVJb0ByZvyR8PiqUgJA+LUWTm56vgoAbc9e5f+RpSldshsD e0zKpUWqk2N45m7aUPCL1dNsxw+vRdC1oM9Jq6lWHpQS20OnwhEAqtS3AWqqk2flR546 ybxA== X-Gm-Message-State: ALoCoQkTe/K2rwSvrs2ms9UOdMHNUpnMiTg16t1VmI9RVdMvnaFs+dN3S6g3D86y+Q6Nlnq0knuR X-Received: by 10.55.23.161 with SMTP id 33mr1788610qkx.90.1443100626128; Thu, 24 Sep 2015 06:17:06 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id b104sm3424769qga.7.2015.09.24.06.17.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 06:17:04 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: zfs performance degradation From: Paul Kraus In-Reply-To: <56038054.5060906@dim.lv> Date: Thu, 24 Sep 2015 09:17:02 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> To: Dmitrijs , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:17:08 -0000 On Sep 24, 2015, at 0:47, Dmitrijs wrote: > 2015.09.23. 23:08, Paul Kraus =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> On Sep 22, 2015, at 13:38, Dmitrijs wrote: >>=20 >>> I've encountered strange ZFS behavior - serious performance = degradation over few days. >>>=20 >>> Could it happen because of pool being 78% full? So I cannot fill = puls full? >>> Can anyone please advice how could I fix the situation - or is it = normal? >>=20 >> So the short answer (way too late for that) is that you can, in fact, = not use all of the capacity of a zpool unless the data is written once, = never modified, and you do not have any snapshots, clones, or the like. > Thank you very much for explanation. Am I getting it right - it will = not work faster even if I add +4Gb RAM to be 8Gb in total? I am not = using DeDuplication and compression, neither planing using them. If you are seeing the performance degrade due to the zpool being over = some capacity threshold, then adding RAM will make little difference. If = you are seeing general performance issues, then adding RAM (increasing = ARC) _may_ improve the performance. > So if I plan to work with data a lot, get decent performance and still = be sure I'm on the safe side with mirror-raid1, should I choose another = filesystem? Especially, if i do not really need snapshots, clones, etc. What is your definition of =E2=80=9Cdecent=E2=80=9D performance ? What = does your _real_ workload look like ? Did you have performance issues doing real work which caused you to try = to find the cause -or- were you benchmarking before trying to use the = system for real work ? > Or is it not possible at all, and I should put something like raid0 = for work and tolerate slow backup on raid1 at nights? There are many places in ZFS where you can run into performance = bottlenecks. Remember, ZFS was designed for data integrity (end to end = checksums), data reliability (lots of ways to get redundancy), and = scalability. Performance was secondary from the very beginning. There = are lots of other filesystems with much better performance, there are = few (if any) with more protection for your data. Do not get me wrong, = the performance of ZFS _can_ be very good, but you need to understand = your workload and layout the zpool to accommodate that workload. For example, one of my critical workloads is NFS with sync writes. My = zpool layout is many vdevs of 3-way mirrors with a separate ZIL device = (SLOG). I have not been able to go production with this server yet = because I am waiting on backordered SSDs for the SLOG. The original SSDs = I used just did not have the small block write performance I needed. Another example is one of my _backup_ servers, which has a 6 drive = RAIDz2 zpool layout. In this case I am not terribly concerned about = performance as I am limited by the 1 Gbps network connection. Also note that in general, the _best_ performance you can expect of any = zpool layout is equivalent to _1_ drives worth of I/O per _vdev_. So my = 6 drive RAIDz2 has performance equivalent to _one_ of the drives that = make up that vdev. Which is fine for _my_ workload. The rule of thumb = for performance that I received over on the OpenZFS mailing list a while = back was to assume you can get 100 MB/sec and 100 random I/Ops from a = consumer SATA hard disk drive. I have seen nothing, even using = =E2=80=9Centerprise=E2=80=9D grade HDDs, to convince me that is a bad = rule of thumb. If your workload is strictly sequential you _may_ get = more. So a zpool made up of one single vdev, no matter how many drives, will = average the performance of one of those drives. It does not really = matter if it is a 2-way mirror vdev, a 3-way mirror vdev, a RAIDz2 vdev, = a RAIDz3 vdev, etc. This is more true for write operations that read = (mirrors can achieve higher performance by reading from multiple copies = at once). -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 13:28:57 2015 Return-Path: Delivered-To: freebsd-questions@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 CA15AA085F9 for ; Thu, 24 Sep 2015 13:28:57 +0000 (UTC) (envelope-from terje@elde.net) Received: from rand.keepquiet.net (keepquiet.net [144.76.43.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "keepquiet.net", Issuer "PositiveSSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90FA618EB for ; Thu, 24 Sep 2015 13:28:56 +0000 (UTC) (envelope-from terje@elde.net) Received: from [10.154.73.219] (2.150.50.78.tmi.telenormobil.no [2.150.50.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: terje@elde.net) by rand.keepquiet.net (Postfix) with ESMTPSA id 1EC0DB60; Thu, 24 Sep 2015 13:28:48 +0000 (UTC) References: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> Mime-Version: 1.0 (1.0) In-Reply-To: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: FreeBSD Questions X-Mailer: iPhone Mail (10B500) From: Terje Elde Subject: Re: Restructure a ZFS Pool Date: Thu, 24 Sep 2015 15:28:45 +0200 To: Raimund Sacherer X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:28:57 -0000 On 24. sep. 2015, at 14:42, Raimund Sacherer wrote: > What I would like to know is if I can eliminate one Spare disk from the po= ol, and add it as a ZIL again, without having to shutdown/reboot the server?= I think so, but I'd test/check to make sure.=20 Also, I'd consider the ZIL a spof, and mirror it. Bad things will happen if t= he blue smoke escapes, and if you run a single consumer SSD, it will.=20 Terje= From owner-freebsd-questions@freebsd.org Thu Sep 24 13:31:48 2015 Return-Path: Delivered-To: freebsd-questions@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 8CC7EA0884A for ; Thu, 24 Sep 2015 13:31:48 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com [209.85.220.175]) (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 50FB91BFA for ; Thu, 24 Sep 2015 13:31:47 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkap81 with SMTP id p81so29588833qka.2 for ; Thu, 24 Sep 2015 06:31:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=n0gFCbe+UfZXH0KM1LgS6CrQYJM8q1MV7O8kFccgCcg=; b=MYh116kL/tpqkFrozrrOzCP9vvLBCzJUtfdyqspjmjEcl5/+M+o6JMAO9UAIz0eD/b cYwdj3q/d+GRZTyOkCkaRHXbcVjQhQG9qFkGMsw2LDQjz+SRJNDv87uzUh55K5DYkKgn K5EIIeAgzvXfu9QZ5LnjUGMSVnihF1axdCO9QDzDLLCMXATpfElxMmX/TrljhlWmNo0T QmiP1vzljDeeOwSfxBayhiBCOqOq6rtqrgLp7OesczLeY6NblHFbmD4gUyCbkFho0a3m 7mmit/7MrsoElKda50bh7L5ocvhXXEZkPdIFk4lt3bfcJR28HYwJUyUDnslVvPZJCMQa UztQ== X-Gm-Message-State: ALoCoQk01C37FcXIcJM+poYznETXvsIJGHiQhY7gcsePQoQhO6mU1wW9pmL4OgFjLqaG9c4Fma+n X-Received: by 10.55.40.207 with SMTP id o76mr43285900qko.106.1443101506674; Thu, 24 Sep 2015 06:31:46 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id e63sm2667735qka.5.2015.09.24.06.31.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 06:31:45 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Restructure a ZFS Pool From: Paul Kraus In-Reply-To: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> Date: Thu, 24 Sep 2015 09:31:42 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <9EE24D9C-260A-408A-A7B5-14BACB12DDA9@kraus-haus.org> References: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> To: Raimund Sacherer , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:31:48 -0000 On Sep 24, 2015, at 8:42, Raimund Sacherer = wrote: > I had the pool fill up to over 80%, then I got it back to about = 50-60%, but it feels more sluggish. I use a lot of NFS and we use it to = backup some 5 million files in lots of sub-directorys (a/b/c/d/abcd...), = besides other big files (SQL dump backups, bacula, etc.) >=20 > I said above sluggish because I do not have empirical data and I do = not know exactly how to test the system correctly, but I read a lot and = there seem to be suggestions that if you have NFS etc. that a = independent ZIL helps with copy-on-write fragmentation.=20 A SLOG (Separate Log Device) will not remove existing fragmentation, but = it will help prevent future fragmentation _iff_ (if and only if) the = write operations are synchronous. NFS is not, by itself, sync, but the = write calls on the client _may_ be sync. > What I would like to know is if I can eliminate one Spare disk from = the pool, and add it as a ZIL again, without having to shutdown/reboot = the server? Yes, but unless you can stand loosing data in flight (writes that the = system says have been committed but have only made it to the SLOG), you = really want your SLOG vdev to be a mirror (at least 2 drives). > I am also thinking about swapping the spare 4TB disk for a small SSD, = but that's immaterial to whether I can perform the change.=20 I assume you want to swap instead of just add due to lack of open drive = slots / ports. In a zpool of this size, especially a RAIDz zpool, you really want a = hot spare and a notification mechanism so you can replace a failed drive = ASAP. The resilver time (to replace afield drive) will be limited by the = performance of a _single_ drive for _random_ I/O. See this post = http://pk1048.com/zfs-resilver-observations/ for one of my resilver = operations and the performance of such. > Also I would appreciate it if someone has some pointers on how to test = correctly so I see if there are real benefits before/after this = operation. I use a combination of iozone and filebench to test, but first I = characterize my workload. Once I know what my workload looks like I can = adjust the test parameters to match the workload. If the test results do = not agree with observed behavior, then I tune them until they do. = Recently I needed to test a server before going live. I knew the = workload was NFS for storing VM images. So I ran iozone with 8-64 GB = files and 4 KB to 1 MB blocks, and sync writes (the -o option). The = measurements matched very closely to the observations, so I knew could = trust them and any changes I made would give me valid results. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 13:48:10 2015 Return-Path: Delivered-To: freebsd-questions@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 8EAF3A072BC for ; Thu, 24 Sep 2015 13:48:10 +0000 (UTC) (envelope-from raimund.sacherer@logitravel.com) Received: from formentor.toolfactory.net (pina.toolfactory.net [213.97.158.39]) by mx1.freebsd.org (Postfix) with ESMTP id 1383E1469 for ; Thu, 24 Sep 2015 13:48:09 +0000 (UTC) (envelope-from raimund.sacherer@logitravel.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by formentor.toolfactory.net (Postfix) with ESMTP id 846B91786DC; Thu, 24 Sep 2015 15:48:08 +0200 (CEST) Received: from formentor.toolfactory.net ([127.0.0.1]) by localhost (formentor.toolfactory.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id UruOXbh7nyHB; Thu, 24 Sep 2015 15:48:08 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by formentor.toolfactory.net (Postfix) with ESMTP id EE8D71786DF; Thu, 24 Sep 2015 15:48:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at logpmzimmta01v.toolfactory.net Received: from formentor.toolfactory.net ([127.0.0.1]) by localhost (formentor.toolfactory.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FP-_Kj5HbwHo; Thu, 24 Sep 2015 15:48:07 +0200 (CEST) Received: from xorrigo.toolfactory.net (xorrigo.toolfactory.net [192.168.2.210]) by formentor.toolfactory.net (Postfix) with ESMTP id CED0E1786DC; Thu, 24 Sep 2015 15:48:07 +0200 (CEST) Date: Thu, 24 Sep 2015 15:48:07 +0200 (CEST) From: Raimund Sacherer Reply-To: Raimund Sacherer To: Paul Kraus Cc: FreeBSD Questions Message-ID: <168652008.9504625.1443102487228.JavaMail.zimbra@logitravel.com> In-Reply-To: <9EE24D9C-260A-408A-A7B5-14BACB12DDA9@kraus-haus.org> References: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> <9EE24D9C-260A-408A-A7B5-14BACB12DDA9@kraus-haus.org> Subject: Re: Restructure a ZFS Pool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.2.213] X-Mailer: Zimbra 8.0.8_GA_6184 (ZimbraWebClient - SAF7 (Mac)/8.0.8_GA_6184) Thread-Topic: Restructure a ZFS Pool Thread-Index: nTfL759nTthl4zIXcGmeByOnZf0nNw== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:48:10 -0000 ----- Original Message ----- > From: "Paul Kraus" > To: "Raimund Sacherer" , "FreeBSD Questions" > > Sent: Thursday, September 24, 2015 3:31:42 PM > Subject: Re: Restructure a ZFS Pool > On Sep 24, 2015, at 8:42, Raimund Sacherer > wrote: > > I had the pool fill up to over 80%, then I got it back to about 50-60%, but > > it feels more sluggish. I use a lot of NFS and we use it to backup some 5 > > million files in lots of sub-directorys (a/b/c/d/abcd...), besides other > > big files (SQL dump backups, bacula, etc.) > > > > I said above sluggish because I do not have empirical data and I do not > > know exactly how to test the system correctly, but I read a lot and there > > seem to be suggestions that if you have NFS etc. that a independent ZIL > > helps with copy-on-write fragmentation. > A SLOG (Separate Log Device) will not remove existing fragmentation, but it > will help prevent future fragmentation _iff_ (if and only if) the write > operations are synchronous. NFS is not, by itself, sync, but the write calls > on the client _may_ be sync. Yes, I understood that it will only help preventing fragmentation in the future. I also read that performance is great when using async ZFS, would it be safe to use async ZFS if I have Battery Backed Hardware Raid Controller (1024G ram cache)? The server is a HP G8 and I have configured all discs as single disk mirrors (the only way to get a JBOD on this raid controller). In the event of a power outage, everything should be held in the raid controller by the battery and it should write on disk as soon as power is restored, ... would that be safe environment to switch ZFS to async? If I use async, is there still the *need* for a SLOG device, I read that running ZFS async and using the SLOG is comparable, because both let the writes be ordered and those prevent fragmentation? It is not a critical system (e.g. downtime during the day is possible), but if restores need to be done I'd rather have it run as fast as possible. > > What I would like to know is if I can eliminate one Spare disk from the > > pool, and add it as a ZIL again, without having to shutdown/reboot the > > server? > Yes, but unless you can stand loosing data in flight (writes that the system > says have been committed but have only made it to the SLOG), you really want > your SLOG vdev to be a mirror (at least 2 drives). Shouldn't this scenario be handled by ZFS (writes to SLOG, power out, power on, SLOG is transferred to data disks?) I thought the only dataloss would be writes which are currently in transit TO the SLOG in time of the power outage? And I read somewhere that with ZFS since V28 (IIRC) if the SLOG dies it turns off the log and you loose the (performance) benefit of the SLOG, but the pools should still be operational? > In a zpool of this size, especially a RAIDz zpool, you really want a hot > spare and a notification mechanism so you can replace a failed drive ASAP. > The resilver time (to replace afield drive) will be limited by the > performance of a _single_ drive for _random_ I/O. See this post > http://pk1048.com/zfs-resilver-observations/ for one of my resilver > operations and the performance of such. Thank you for this info, I'l keep it in mind and bookmark your link. > > Also I would appreciate it if someone has some pointers on how to test > > correctly so I see if there are real benefits before/after this operation. > I use a combination of iozone and filebench to test, but first I characterize > my workload. Once I know what my workload looks like I can adjust the test > parameters to match the workload. If the test results do not agree with > observed behavior, then I tune them until they do. Recently I needed to test > a server before going live. I knew the workload was NFS for storing VM > images. So I ran iozone with 8-64 GB files and 4 KB to 1 MB blocks, and sync > writes (the -o option). The measurements matched very closely to the > observations, so I knew could trust them and any changes I made would give > me valid results. Thank you, I will have a look on iozone best Ray From owner-freebsd-questions@freebsd.org Thu Sep 24 13:57:41 2015 Return-Path: Delivered-To: freebsd-questions@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 E5A56A07A4C for ; Thu, 24 Sep 2015 13:57:40 +0000 (UTC) (envelope-from war@dim.lv) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (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 812E619ED for ; Thu, 24 Sep 2015 13:57:39 +0000 (UTC) (envelope-from war@dim.lv) Received: by wicgb1 with SMTP id gb1so251210390wic.1 for ; Thu, 24 Sep 2015 06:57:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=DKMDB+7Tdn9LeJlBrOBCDr/1Wc6crJwunISBbb0h9eA=; b=TOE9BhpzdSjjc54QN3X147uAP3w1HjHvVszwP5GXSva8mB1dzwghv0hvOeD/QVg042 9elFyZNfWf9NppFlwkY+slk7u9QGL6IowNxwGwOUKARclRIgluqb1POXloffX2c8QeKb xUgQPVL82TIDFqUbT9sGBqjGesVCFjri4nWyCkjUhyit8Abvb+LlKhYlNebL1W8qSCDY CNinGWnIuZyzGRkd6+DYiKa/s4kp6cARBo4tQbVZGWRwQ3SXtLH7tpeNwUKqaS5C2fL2 imYf4oKUpAYNfoKMzmqHhB/fof9nx12MJi7NxQfPfZsg1SyLEOKjZFTkAU5q0o4Rglig QITQ== X-Gm-Message-State: ALoCoQk7viWeGiaU+m8X2KkrZ+NK66TrMBF60OiQxQnkdS7sqw+vErxTRLLOu0BUwzEb6lwVRt8K X-Received: by 10.194.184.136 with SMTP id eu8mr47250714wjc.151.1443103057944; Thu, 24 Sep 2015 06:57:37 -0700 (PDT) Received: from [192.168.88.18] (balticom-185-141.balticom.lv. [83.99.185.141]) by smtp.googlemail.com with ESMTPSA id qc4sm12460098wjc.33.2015.09.24.06.57.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2015 06:57:37 -0700 (PDT) Subject: Re: zfs performance degradation To: Paul Kraus , FreeBSD Questions References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> From: Dmitrijs Message-ID: <56040150.90403@dim.lv> Date: Thu, 24 Sep 2015 16:57:36 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:57:41 -0000 2015.09.24. 16:17, Paul Kraus wrote: > So if I plan to work with data a lot, get decent performance and still be sure I'm on the safe side with mirror-raid1, should I choose another filesystem? Especially, if i do not really need snapshots, clones, etc. > What is your definition of “decent†performance ? What does your _real_ workload look like ? > > Did you have performance issues doing real work which caused you to try to find the cause -or- were you benchmarking before trying to use the system for real work ? As we use our file server mostly to store users' backup and hdd images for old and new computers. File sizes mostly go 10-100Gb+. In the daytime the usually have 1 "writer" and several "readers". And datetime performance is very important to us. In the nighttime several "writers" and no "readers". Most file operations are sequential. Working environment mostly ms windows 7. We used to have software mirror raid on one windows 7 computer, shared to our gigabit network. Now we decided to have dedicate box for file storage. In my terms "decent" where performance is limited mostly by gigabit network, not the file operations. So if zfs raid mirror can give me total 100Mbs+ output at least on 1-2 readers - it's ok. When I have total 70-80Mbs and less in perspective - I worry that I'm doing something wrong. And as you see, I'm just beginning to dig into freebsd file systems etc, so my question and answers may be inadequate. >> Or is it not possible at all, and I should put something like raid0 for work and tolerate slow backup on raid1 at nights? > There are many places in ZFS where you can run into performance bottlenecks. Remember, ZFS was designed for data integrity (end to end checksums), data reliability (lots of ways to get redundancy), and scalability. Performance was secondary from the very beginning. There are lots of other filesystems with much better performance, there are few (if any) with more protection for your data. Do not get me wrong, the performance of ZFS _can_ be very good, but you need to understand your workload and layout the zpool to accommodate that workload. Thank you for clarification. I made some research and found out that zfs is really very good system for the points you mentioned. That's why we choose freebsd and zfs. And that's exactly where I need help - to understand how big is price for zfs reliability and options. If we need to buy better CPU, add more RAM, more disks to get better performance - it must be considered, that's one thing. And if there are tweaks, that can be adjusted via settings - that's another thing. > For example, one of my critical workloads is NFS with sync writes. My zpool layout is many vdevs of 3-way mirrors with a separate ZIL device (SLOG). I have not been able to go production with this server yet because I am waiting on backordered SSDs for the SLOG. The original SSDs I used just did not have the small block write performance I needed. > > Another example is one of my _backup_ servers, which has a 6 drive RAIDz2 zpool layout. In this case I am not terribly concerned about performance as I am limited by the 1 Gbps network connection. > > Also note that in general, the _best_ performance you can expect of any zpool layout is equivalent to _1_ drives worth of I/O per _vdev_. So my 6 drive RAIDz2 has performance equivalent to _one_ of the drives that make up that vdev. Which is fine for _my_ workload. The rule of thumb for performance that I received over on the OpenZFS mailing list a while back was to assume you can get 100 MB/sec and 100 random I/Ops from a consumer SATA hard disk drive. I have seen nothing, even using “enterprise†grade HDDs, to convince me that is a bad rule of thumb. If your workload is strictly sequential you _may_ get more. > > So a zpool made up of one single vdev, no matter how many drives, will average the performance of one of those drives. It does not really matter if it is a 2-way mirror vdev, a 3-way mirror vdev, a RAIDz2 vdev, a RAIDz3 vdev, etc. This is more true for write operations that read (mirrors can achieve higher performance by reading from multiple copies at once). Thanks! Now I understand. Although it is strange, that you did not mention how RAM and\or CPU matters. Or do they? I start observing that my 4core Celeron J1900 is throttling writes. Still haven't found at least approximate specification\recommendation as simple as "if you need zfs mirror 2 drives, take at least core i3 or e3 processor, 10 drives - go for e5 xeon, etc". I did not notice cpu impact on windows machine, still i've got " load averages: 1.60, 1.43, 1.24 " on write on zfs. best regards, Dmitriy From owner-freebsd-questions@freebsd.org Thu Sep 24 14:20:10 2015 Return-Path: Delivered-To: freebsd-questions@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 9E8D2A08B0A for ; Thu, 24 Sep 2015 14:20:10 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (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 60E03184B for ; Thu, 24 Sep 2015 14:20:09 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgev79 with SMTP id v79so45179305qge.0 for ; Thu, 24 Sep 2015 07:20:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=Cl/kVNJf8LVb81YYjvzbkCxb7xaCAEtrNjzZSQ5SdYs=; b=HTydHg9sfs5HdFuQ4Mv19hYWW/YNevsQqtr2FbAEswK39FcpesRu6JUVeqHEfX8ynl 7qNj2/3QdPabF+Iog5eooxxIEmdv57Z2w5QFc35CmoptOwUh9TRY8+06dIwA8BAz7h+Q 2zWllutTIdKCCiN2cNrOQddallUKAuydJ2lhuJBVJwk13QMDDxrg7BcTiCnkuTc9KCVO zVdZaQKmRsLqDIGCevAysgUHF0ud0N01CHz+HwHrcOPZw/SMhz21PWihUmF6E7+RngKD ckZ6/x01tM+XhQW3vqER3jZrsSWdeukl4VvwTam2g4YmCD+jS/kDP1f+7CFd5yjsIdxn h18A== X-Gm-Message-State: ALoCoQm18iwgUUGD21XKq+VEyzg/w7OgH3UapZjV5xGi+eGqYnOci339Sc1NhiLS24RuVXJnrqja X-Received: by 10.140.151.140 with SMTP id 134mr46170350qhx.49.1443104408600; Thu, 24 Sep 2015 07:20:08 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id p14sm3505767qge.43.2015.09.24.07.20.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 07:20:06 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Restructure a ZFS Pool From: Paul Kraus In-Reply-To: <168652008.9504625.1443102487228.JavaMail.zimbra@logitravel.com> Date: Thu, 24 Sep 2015 10:20:04 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <0A3AC2BF-0BF6-4CFB-8947-EFA01B58CF93@kraus-haus.org> References: <480627999.9462316.1443098561442.JavaMail.zimbra@logitravel.com> <9EE24D9C-260A-408A-A7B5-14BACB12DDA9@kraus-haus.org> <168652008.9504625.1443102487228.JavaMail.zimbra@logitravel.com> To: Raimund Sacherer , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 14:20:10 -0000 On Sep 24, 2015, at 9:48, Raimund Sacherer wrote: > Yes, I understood that it will only help preventing fragmentation in = the future. I also read that performance is great when using async ZFS, That is an overly general statement. I have seen zpools perform badly = with async as well as sync writes when not configured to match the = workload. > would it be safe to use async ZFS if I have Battery Backed Hardware = Raid Controller (1024G ram cache)? > The server is a HP G8 and I have configured all discs as single disk = mirrors (the only way to get a JBOD on this raid controller). In the = event of a power outage, everything should be held in the raid = controller by the battery and it should write on disk as soon as power = is restored, Turning off sync behavior violates Posix compliance and is not a very = good idea. Also remember that async writes are cached in the ARC=85 so = you need power for the entire server, not just the disk caches, until = all activity has ceased _and_ all pending Transaction Groups (TXG) have = been committed to non-volatile storage. TXGs are generally committed = every 5 seconds, but if you are under heavy write load it may take more = time than that. > ... would that be safe environment to switch ZFS to async?=20 No one can make that call but you. You know your environment, you know = your workload, you know the fallout from lost writes _if_ something goes = wrong. > If I use async, is there still the *need* for a SLOG device, I read = that running ZFS async and using the SLOG is comparable, because both = let the writes be ordered and those prevent fragmentation? It is not a = critical system (e.g. downtime during the day is possible), but if = restores need to be done I'd rather have it run as fast as possible.=20 If you disable sync writes (please do NOT say =93use async=94 as that is = determined by the application code), then you are disabling the ZIL (ZFS = Intent Log) and the SLOG is a device to hold _just_ the ZIL separate = from the data vdevs in the zpool. So, yes, disabling sync writes means = that even if there is a SLOG it will never be used. >> Yes, but unless you can stand loosing data in flight (writes that the = system >> says have been committed but have only made it to the SLOG), you = really want >> your SLOG vdev to be a mirror (at least 2 drives). > Shouldn't this scenario be handled by ZFS (writes to SLOG, power out, = power on, SLOG is transferred to data disks?) Not if the single SLOG device _fails_ =85 In the case of a power = failure, once the system comes back up ZFS will replay the TXGs on the = SLOG and you will not have lost any writes, > I thought the only dataloss would be writes which are currently in = transit TO the SLOG in time of the power outage? Once again, if the application requests sync writes, the application is = not told that the write is complete _until_ it is committed to = non-volatile backing storage, in this case the ZIL/SLOG device(s). So = from the application=92s perspective, no writes are lost because they = were not committed when power failed. This is one of the use cases where = claiming that disabling sync behavior and assuming UPS / battery backed = up cache is just as good as a SLOG device is misleading. The application = is asking for a sync write and it is being lied to. > And I read somewhere that with ZFS since V28 (IIRC) if the SLOG dies = it turns off the log and you loose the (performance) benefit of the = SLOG, but the pools should still be operational? There are separate versions for zpool and zfs, you are referring to = zpool version 28. Log device removal was added in zpool version 19. = `zpool upgrade -v` will tell you which versions / features your system = supports. `zfs upgrade -v` will tell you the same thing for zfs = versions. FreeBSD 10.1 has zfs version 5 and zpool version 28 plus lots = of added features. Feature flags were a way to add features to zpools = while not completely breaking compatibility. So you can remove a failed SLOG device, and if they are mirrored you = still don=92t lose any data. I=92m not sure what happens to a running = zpool if a single (non-mirrored) SLOG device fails. >> In a zpool of this size, especially a RAIDz zpool, you really want = a hot >> spare and a notification mechanism so you can replace a failed drive = ASAP. >> The resilver time (to replace afield drive) will be limited by the >> performance of a _single_ drive for _random_ I/O. See this post >> http://pk1048.com/zfs-resilver-observations/ for one of my resilver >> operations and the performance of such. > Thank you for this info, I'l keep it in mind and bookmark your link. Benchmark your own zpool, if you can. Do a zpool replace on a device and = see how long it takes. That is a reasonable first approximation of how = long it will take to replace a really failed device. I tend to stick = with no bigger than 1 TB drives to keep resilver times reasonable (for = me). I add more vdevs of mirrors as I need capacity. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 14:40:44 2015 Return-Path: Delivered-To: freebsd-questions@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 53460A07648 for ; Thu, 24 Sep 2015 14:40:44 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) (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 164851339 for ; Thu, 24 Sep 2015 14:40:43 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgt47 with SMTP id 47so45762877qgt.2 for ; Thu, 24 Sep 2015 07:40:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=Hkp7eu4Wz/1M7JwEx3glqcVhsiCzcKLqDkb7IH9FAaI=; b=CzFt7O0B27PM1lcLz9fWjK8R6BXA/bWTcaLh/PXeZevKI/rOr6OitajqMV3Z8YJ/oP alNVh61e5N9SCt4UkwwAXMrCaYw6eIFXdZwk9z3K/bH1uzU5kvrjjoCUZIPR+fKj92wC aJAg439/vJ+73ha7n8vyN9mo2DyWcduGe5JMYR9+OqR4pLXcWT3ZnYetWE08E+lRRb6D fC9T07F4/QJaOud01wKS4XxxTgp4wi52QY9ftajI7Oi0AYF6/iUFi28BzYDh7pfB1XLA Upn1syfOwwAy6AMmkWTPmRFNP9kgKCzKNmLwjgZvuKw0x+1VXSOO/0JO6HV/kGvp2Pt+ 4XOw== X-Gm-Message-State: ALoCoQmzGgZc5u5vSe8lHKHyHLI/+Clzf8OBrjvcVMgKMAbuph6c+1pqFCxlbop0Ure7AKdK6nT0 X-Received: by 10.140.130.72 with SMTP id 69mr122272qhc.32.1443105637243; Thu, 24 Sep 2015 07:40:37 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id z19sm3542902qge.38.2015.09.24.07.40.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 07:40:35 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: zfs performance degradation From: Paul Kraus In-Reply-To: <56040150.90403@dim.lv> Date: Thu, 24 Sep 2015 10:40:33 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> To: Dmitrijs , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 14:40:44 -0000 On Sep 24, 2015, at 9:57, Dmitrijs wrote: >>=20 >> So a zpool made up of one single vdev, no matter how many drives, = will average the performance of one of those drives. It does not really = matter if it is a 2-way mirror vdev, a 3-way mirror vdev, a RAIDz2 vdev, = a RAIDz3 vdev, etc. This is more true for write operations that read = (mirrors can achieve higher performance by reading from multiple copies = at once). > Thanks! Now I understand. Although it is strange, that you did not = mention how RAM and\or CPU matters. Or do they? I start observing that = my 4core Celeron J1900 is throttling writes. Do you have compression turned on ? I have only seen ZFS limited by CPU = (assuming relatively modern CPU) when using compression. If you are = using compression, make sure it is lz4 and not just =93on". RAM effects performance in that pending (async) writes are cached in the = ARC. The ARC also caches both demand read data as well as prefetched = read data. There are a number of utilities out there to give you = visibility into the ARC. `sysctl -a | grep arcstats` will get you the = raw data :-) When you benchmark you _must_ use a test set of data that is larger than = your RAM you you will not be testing all the way to / from the drives = :-) That or artificially reduce the size of the ARC (set = vfs.zfs.arc_max=3D=93=94 in /boot/loader.conf). > Still haven't found at least approximate specification\recommendation = as simple as "if you need zfs mirror 2 drives, take at least core i3 or = e3 processor, 10 drives - go for e5 xeon, etc". I did not notice cpu = impact on windows machine, still i've got " load averages: 1.60, 1.43, = 1.24 " on write on zfs. How many cores / threads ? As long as you have more cores / threads than = the load value you are NOT out of CPU resources, but you may be = saturating ONE CPU with compression or other function. I have been using HP Proliant MicroServer N36L, N40L, and N54L for small = file servers and I am only occasionally CPU limited. But my work load on = these boxes is very different from yours. My backup server is a SuperMicro with dual Xeon E5520 (16 total threads) = and 12 GB RAM. I can handily saturate my single 1 Gbps network. I have = compression (lz4) enabled on all datasets. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 15:11:51 2015 Return-Path: Delivered-To: freebsd-questions@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 5299DA086E5 for ; Thu, 24 Sep 2015 15:11:51 +0000 (UTC) (envelope-from war@dim.lv) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 E5E2410CA for ; Thu, 24 Sep 2015 15:11:49 +0000 (UTC) (envelope-from war@dim.lv) Received: by wicge5 with SMTP id ge5so256515910wic.0 for ; Thu, 24 Sep 2015 08:11:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=AtZ2+HNk0hrREJUraaWB9ydtxgevOvgsSenzhZ/hoIU=; b=M+vDNrP8TW+OwqDGT3wGHMeKnKi2d4f3BhDmyWKCCj64TH1NcA20p1dK0HOgKNe794 uyVofd0zNdX9K/SarcWKFT9k/MlXAcdPgiQfM4AslQhYmhp/bOsZvBMUhxez2KsG23IB G1vfYWKt36FyYeMwgfNlTdmKjV8/zEdpNBKEpROQPRToKWCKV59ffCV/B6yrB1pU6ASt 6eIu2oG9aO3E2b9JwAD2v2fs9/stU6Dbe/D85i7gMSh4ShzuLFK9+mYqsLL60UohtgHN p9g9MVd+n2JSQe8FaR+t9CPO6lgcZji6JlLsMhk8SqN3wPsd4m9QQqIfO5ldxPB0amAb 1AKQ== X-Gm-Message-State: ALoCoQljIVBPWsKGfrxHrOyL183lZPhxmYr4Rgh804oOg2YAMiFxG+MtCFBYuFAJ6fN0NGe0l5ZB X-Received: by 10.194.104.39 with SMTP id gb7mr227223wjb.150.1443107507788; Thu, 24 Sep 2015 08:11:47 -0700 (PDT) Received: from [192.168.88.18] (balticom-185-141.balticom.lv. [83.99.185.141]) by smtp.googlemail.com with ESMTPSA id az6sm5892457wib.12.2015.09.24.08.11.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2015 08:11:47 -0700 (PDT) Subject: Re: zfs performance degradation To: Paul Kraus , FreeBSD Questions References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> From: Dmitrijs Message-ID: <560412B2.9070905@dim.lv> Date: Thu, 24 Sep 2015 18:11:46 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 15:11:51 -0000 2015.09.24. 17:40, Paul Kraus wrote: > Do you have compression turned on ? I have only seen ZFS limited by > CPU (assuming relatively modern CPU) when using compression. If you > are using compression, make sure it is lz4 and not just “on". RAM > effects performance in that pending (async) writes are cached in the > ARC. The ARC also caches both demand read data as well as prefetched > read data. There are a number of utilities out there to give you > visibility into the ARC. `sysctl -a | grep arcstats` will get you the > raw data :-) When you benchmark you _must_ use a test set of data that > is larger than your RAM you you will not be testing all the way to / > from the drives :-) That or artificially reduce the size of the ARC > (set vfs.zfs.arc_max=“” in /boot/loader.conf). Nope, no compression, no deduplication, only pure zfs. Even no prefetch, as it is not recommended for machines 4Gb RAM and below. I've tested performance with 40Gb file on 4Gb ram machine, so cache should not count so much. I really hoped that I could get from 2HDD MIRROR at least 1.5x read performance of a single HDD, but it's more tricky as you explained. Now I'm not sure what configuration will make better performance for 4 HDD - raid10 or raid-z2? Or two separate mirrors? Need directions for scale things up in the future. >> Still haven't found at least approximate specification\recommendation as simple as "if you need zfs mirror 2 drives, take at least core i3 or e3 processor, 10 drives - go for e5 xeon, etc". I did not notice cpu impact on windows machine, still i've got " load averages: 1.60, 1.43, 1.24 " on write on zfs. > How many cores / threads ? As long as you have more cores / threads than the load value you are NOT out of CPU resources, but you may be saturating ONE CPU with compression or other function. > > I have been using HP Proliant MicroServer N36L, N40L, and N54L for small file servers and I am only occasionally CPU limited. But my work load on these boxes is very different from yours. > > My backup server is a SuperMicro with dual Xeon E5520 (16 total threads) and 12 GB RAM. I can handily saturate my single 1 Gbps network. I have compression (lz4) enabled on all datasets. I've got http://ark.intel.com/products/78867/Intel-Celeron-Processor-J1900-2M-Cache-up-to-2_42-GHz And 4Gb RAM. Thought it would be sufficient, but now I'm in doubt. I can live with reduced performance for my 1st NAS, but would be nice to have clear performance requirements in mind for planing future storage boxes. I see QNAPs and Synology NAS, they use like 1Ghz CPU and 1Gb of RAM for 4 HDD, so either I'm doing it wrong, either those NASes don't have performance (or safety?) at all. HP Proliant MicroServer is nice, but i've made my diskless system 2-3 times cheaper (200euro vs 530/650euro), so I need a reason or recomendation to spend x2x3 money on the thing, which specification looks the same. best regards, Dmitriy From owner-freebsd-questions@freebsd.org Thu Sep 24 15:26:36 2015 Return-Path: Delivered-To: freebsd-questions@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 2D868A08EFB for ; Thu, 24 Sep 2015 15:26:36 +0000 (UTC) (envelope-from chino@antennex.com) Received: from sageweb.net (sageweb.net [104.51.134.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 024221720 for ; Thu, 24 Sep 2015 15:26:35 +0000 (UTC) (envelope-from chino@antennex.com) Received: from SAGEPLACE (162-230-18-252.lightspeed.crchtx.sbcglobal.net [162.230.18.252]) by sageweb.net (8.15.1/8.15.1) with ESMTP id t8OFQQAc098906; Thu, 24 Sep 2015 10:26:28 -0500 (CDT) (envelope-from chino@antennex.com) X-Authentication-Warning: sageweb.net: Host 162-230-18-252.lightspeed.crchtx.sbcglobal.net [162.230.18.252] claimed to be SAGEPLACE Date: Thu, 24 Sep 2015 10:26:25 -0500 From: "chino@antennex.com" To: freebsd-questions Subject: Find and replace X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 140[en] Mime-Version: 1.0 Message-ID: <2015092410262490833415@antennex.com> X-Scanned-By: milter-spamc/1.15.388 (sageweb.net [104.51.134.145]); Thu, 24 Sep 2015 10:26:28 -0500 X-Spam-Status: NO, hits=-10.00 required=6.00 X-Spam-Report: Content analysis details: (-10.0 points, 6.0 required) | | pts rule name description | ---- ---------------------- -------------------------------------------------- | -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule | -10 ALL_TRUSTED Passed through trusted hosts only via SMTP | Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 15:26:36 -0000 QW0gcnVubmluZyBGQlNELTkuMyBhbmQgYXBhY2hlLTI0DQoNCkkgbmVlZCB0byBmaW5kIGFuZCBy ZXBsYWNlIHNldmVyYWwgc3RyaW5ncyB3aXRoICJub3RoaW5nIiAobm90IHRoZSB3b3JkIGJ1dCBh IGJsYW5rKSBhbmQgSSBjYW5ub3QgcmVjYWxsIGhvdyB0byBoYW5kbGUgdGhlIHN5bnRheCBmb3Ig dGhlICJuZXciIHBvcnRpb24gaWYgdXNpbmcgc2VkIGFzIGJlbG93LiBJbiBvdGhlciB3b3Jkcywg SSB3YW50IHRoZSAqLmh0bWwgZmlsZSB0byBOT1QgZGlzcGxheSB0aGUgZ3JhcGhpYyB3aXRoIHRo ZSBzYW1lIHBpeC5naWYgZmlsZSBuYW1lIG5vdyB0aGVyZSBpbiBhYm91dCAxMDAwIEhUTUwgZmls ZXMuDQpUaGlzIHNjcmlwdDogc2VkIC1pLmJhayBzL29sZC9uZXcvZyBmaWxlTGlrZSB0aGlzOiNm aW5kLCBldGMgfCBzZWQgLWkuYmFrIHMvcGl4LmdpZi8vZyBmaWxlVGhhbmtzIGluIGFkdmFuY2Ug Zm9yIGFueSBoZWxwIQ0KDQoNCldhcm1lc3QgcmVnYXJkcywNCk1hcmsgQ2hpbm8NCi0tDQpjaGlu b0BhbnRlbm5leC5jb20gDQp3d3cuYW50ZW5uZXguY29tDQo= From owner-freebsd-questions@freebsd.org Thu Sep 24 15:44:50 2015 Return-Path: Delivered-To: freebsd-questions@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 A7BB1A07AFF for ; Thu, 24 Sep 2015 15:44:50 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com [209.85.192.44]) (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 688361119 for ; Thu, 24 Sep 2015 15:44:49 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgez77 with SMTP id z77so47746995qge.1 for ; Thu, 24 Sep 2015 08:44:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=6zhhCLMdyuVhj7GYWf9NGQ5YfSzDe4+EAnsC4u5WJUQ=; b=PeGkUNaJx4iwdDZwLBq+pBdXli7wU/Xx9oD1Mw5V49ongFqcnPRjLnOkwUFWw/QomB BPJ8jI8f5F1w0jUmYjsVvwhyED8u8L3tdfBT7+RvX2S7Ooei3dSITEU0xqL9L7TAGNCP 1OukZqnaBeyE4UeYl01WQjC+x9gJ30F9KwVMeKoaqtOBeJgXd+xvKDmU6FJusduBsblL O51YDk6dmtkwjZVZAeq7YruYQFgoF9tqhU7AhzHtjzmjFb0ahdG+GcR+tfEjrX2+e7mO pvln7CsHCQpse3SdAOyumQaptV1sDJjtikfNOwkS0D4RuBRsqGAHd+xPrhrow/yJBv/4 61aQ== X-Gm-Message-State: ALoCoQl9/DzC0tosTSKOhM7kZ0vGCSpXaHPgJGK8XH0AV8SzIjddRFfnMOdGD+eVlSbup4YyU4Ag X-Received: by 10.140.234.195 with SMTP id f186mr573839qhc.25.1443109482850; Thu, 24 Sep 2015 08:44:42 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id b16sm4717657qkj.1.2015.09.24.08.44.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 08:44:40 -0700 (PDT) Subject: Re: zfs performance degradation Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <560412B2.9070905@dim.lv> Date: Thu, 24 Sep 2015 11:44:37 -0400 Cc: FreeBSD Questions Content-Transfer-Encoding: quoted-printable Message-Id: <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> To: Dmitrijs X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 15:44:50 -0000 On Sep 24, 2015, at 11:11, Dmitrijs wrote: > Nope, no compression, no deduplication, only pure zfs. Even no = prefetch, as it is not recommended for machines 4Gb RAM and below. I am very surprised that ZFS is CPU limited on that system. My N54L has = less CPU performance than that and I easily get 60 MB/sec via CIFS = (Samba) from a Mac or Windows client. > I've tested performance with 40Gb file on 4Gb ram machine, so cache = should not count so much. Yup. BTW, b =3D=3D bits B =3D=3D bytes (and to be pedantic, GB =3D=3D = one billion bytes while GiB =3D=3D 2^30 bytes) > I really hoped that I could get from 2HDD MIRROR at least 1.5x read = performance of a single HDD, but it's more tricky as you explained. Yup, remember that ZFS has _lots_ of metadata per fs block and it needs = to read all of that as well as the data. > Now I'm not sure what configuration will make better performance for 4 = HDD - raid10 or raid-z2? Or two separate mirrors? Need directions for = scale things up in the future. Of all the questions you have asked that one is the easiest to answer =85 = a zpool which has 2 vdevs each of which is a 2-way mirror will have = roughly double the performance of a zpool that has one vdev that is a 4 = drive RAIDz2. Performance scales with the number of vdevs, not the = number of drives. I know that is not obvious at first, but when you look = at the design of ZFS (all top level vdevs are striped across) it makes = perfect sense. So a 2 x 2-way mirror will be faster than a 4 drive RAIDz2. At a cost, = the MTTDL (Mean Time To Data Loss) will be better for the RAIDz2 than = the 2 x 2-way mirror. See Richard Ellings post here = http://blog.richardelling.com/2010/02/zfs-data-protection-comparison.html = for a comparison of relative MTTDL for ZFS configurations. Note that I use 3-way mirrors where I need _both_ performance and = reliability and RAIDz2 where I need mostly reliability and performance = is secondary. But =85 back when I was managing lots of data (2007 - = 2012), I did use RADIz2 in production for critical data, but we had 22 = top level vdevs, each a 5 drive RAIDz2 and 10 hot spares. Striping data = across 22 RAIDz2 gave us the performance we needed with the reliability. > I've got = http://ark.intel.com/products/78867/Intel-Celeron-Processor-J1900-2M-Cache= -up-to-2_42-GHz > And 4Gb RAM. That should beat the MicroServer in terms of CPU. I had 8 GB in my N36L = and upgraded to 16 GB in my later N54L. I keep referencing these as they = are more similar to your setup than my bigger SuperMicro servers. Also = note that these MicroServers were the first generation, not the later = Gen 8. I paid about US$200 to US$300 for the bare chassis with CPU and 2 = GB RAM. The Gen 8 are much more expensive and I am looking for something = cheaper for my clients now. > Thought it would be sufficient, but now I'm in doubt. I think that 4 GB is slightly low for a file server, but it should not = be too bad. The CPU should be fine. What are the drives themselves ? = [Because with only 4 GB RAM you _will_ feel the effect of drive = performance, and it is random I/Ops that really matter for ZFS] > I can live with reduced performance for my 1st NAS, but would be nice = to have clear performance requirements in mind for planing future = storage boxes. >=20 > I see QNAPs and Synology NAS, they use like 1Ghz CPU and 1Gb of RAM = for 4 HDD, so either I'm doing it wrong, either those NASes don't have = performance (or safety?) at all. Do they calculate checksums for end-to-end data integrity ? What is their performance like ? The data integrity and reliability features of ZFS do come at a cost. > HP Proliant MicroServer is nice, but i've made my diskless system 2-3 = times cheaper (200euro vs 530/650euro), so I need a reason or = recomendation to spend x2x3 money on the thing, which specification = looks the same. As I said above, I have moved away from the MicroServer Gen 8 due to = cost. The original MicroServer was a very sweet deal and I wish I had = bought a couple of them last December when I could have gotten them for = US$200 each :-(=20 -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 16:02:07 2015 Return-Path: Delivered-To: freebsd-questions@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 4AF89A08587 for ; Thu, 24 Sep 2015 16:02:07 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from cargobay.net (cargobay.net [198.178.123.147]) (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 2C2571DC5 for ; Thu, 24 Sep 2015 16:02:06 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from [192.168.0.14] (cblmdm72-240-160-19.buckeyecom.net [72.240.160.19]) by cargobay.net (Postfix) with ESMTPSA id 4BEB6DE1 for ; Thu, 24 Sep 2015 15:56:37 +0000 (UTC) Subject: Re: Find and replace To: freebsd-questions@freebsd.org References: <2015092410262490833415@antennex.com> From: "Chad J. Milios" Message-ID: <56041E79.1030505@ccsys.com> Date: Thu, 24 Sep 2015 12:02:01 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <2015092410262490833415@antennex.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 16:02:07 -0000 On 9/24/2015 11:26 AM, chino@antennex.com wrote: > Am running FBSD-9.3 and apache-24 > > I need to find and replace several strings with "nothing" (not the word but a blank) and I cannot recall how to handle the syntax for the "new" portion if using sed as below. In other words, I want the *.html file to NOT display the graphic with the same pix.gif file name now there in about 1000 HTML files. > This script: sed -i.bak s/old/new/g fileLike this:#find, etc | sed -i.bak s/pix.gif//g fileThanks in advance for any help! > > > Warmest regards, > Mark Chino > -- > chino@antennex.com > www.antennex.com > you are looking for `xargs`. also consider using the `-print0` operator (thats a zero) with find along with `-0` flag to xargs if your filenames/directories contain any characters special to the shell (like spaces). find /within/this/directory -type f -print0 | xargs -0 sed -i.bak 's/find this/replace with that/g' as a side note, if you do exactly as you described, wont you be left with many broken tags? dont you want to remove the entire tag from your html? From owner-freebsd-questions@freebsd.org Thu Sep 24 16:17:17 2015 Return-Path: Delivered-To: freebsd-questions@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 9E9AEA08D50 for ; Thu, 24 Sep 2015 16:17:17 +0000 (UTC) (envelope-from war@dim.lv) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (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 3C1C6135F for ; Thu, 24 Sep 2015 16:17:16 +0000 (UTC) (envelope-from war@dim.lv) Received: by wicfx3 with SMTP id fx3so119856763wic.0 for ; Thu, 24 Sep 2015 09:17:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=HWi2byK0DLrnS48byiBNZEOoWhc5mlHShbLS9kkxAIs=; b=HDawgbADhjAUDO43oARHrPkL3oKJBZDT0GqgnAdoiUW9FYJ/JP9cVrFPZaPrTw+4W6 cJljfwhRGqOx+2pzywlc/ZFfrQCWyd0ZBxHfMF8vTHFxko39FqlzYcwUh97aDUW6kNYt I4K9wb07dshEcxRjJtQEMrc75yijr+lOl0xNJjHqzPRdO3n03xd84YBvfTLFDZkM5Iyg 5w8XQezar158RbtObz6eqZbrh7h9HRwcdzAkLo5NrfxciHTZoFQ2gdEZvp5szCFme4TR hDMSHve3N/gB95wQpxxybyQDhkn9zf1F/zcbRtF2PIcd+GFnehW2yjiqguz1T4k0VC9R E1rw== X-Gm-Message-State: ALoCoQnLB7iS5W9nqUeVJcYQDAMXDXzKIzVZYnzDUWENVonjRItrKmoy7ZkXiRfgKQjqPXvBmMvL X-Received: by 10.194.120.198 with SMTP id le6mr521488wjb.133.1443111434904; Thu, 24 Sep 2015 09:17:14 -0700 (PDT) Received: from [192.168.88.18] (balticom-185-141.balticom.lv. [83.99.185.141]) by smtp.googlemail.com with ESMTPSA id uq5sm13020100wjc.3.2015.09.24.09.17.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2015 09:17:13 -0700 (PDT) Subject: Re: zfs performance degradation To: Paul Kraus References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> Cc: FreeBSD Questions From: Dmitrijs Message-ID: <56042209.8040903@dim.lv> Date: Thu, 24 Sep 2015 19:17:13 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 16:17:17 -0000 2015.09.24. 18:44, Paul Kraus Đ¿Đ¸ÑˆĐµÑ‚: > On Sep 24, 2015, at 11:11, Dmitrijs wrote: > >> Nope, no compression, no deduplication, only pure zfs. Even no prefetch, as it is not recommended for machines 4Gb RAM and below. > I am very surprised that ZFS is CPU limited on that system. My N54L has less CPU performance than that and I easily get 60 MB/sec via CIFS (Samba) from a Mac or Windows client. I also get about 60-70MB/sec via CIFS or ftp, but my aim is to be limited by network, so 100MB is wanted. Or, to understand why it is not possible on my config :) But simple dd of=/dev/null in the console shows me 110MB/sec... iozone gives me the same 100+Mb/sec both on read and write. That's one of the reasons I'm seeking advice in freebsd-questions@freebsd.org >> Now I'm not sure what configuration will make better performance for 4 HDD - raid10 or raid-z2? Or two separate mirrors? Need directions for scale things up in the future. > Of all the questions you have asked that one is the easiest to answer … a zpool which has 2 vdevs each of which is a 2-way mirror will have roughly double the performance of a zpool that has one vdev that is a 4 drive RAIDz2. Performance scales with the number of vdevs, not the number of drives. I know that is not obvious at first, but when you look at the design of ZFS (all top level vdevs are striped across) it makes perfect sense. > > So a 2 x 2-way mirror will be faster than a 4 drive RAIDz2. At a cost, the MTTDL (Mean Time To Data Loss) will be better for the RAIDz2 than the 2 x 2-way mirror. See Richard Ellings post here http://blog.richardelling.com/2010/02/zfs-data-protection-comparison.html for a comparison of relative MTTDL for ZFS configurations. > > Note that I use 3-way mirrors where I need _both_ performance and reliability and RAIDz2 where I need mostly reliability and performance is secondary. But … back when I was managing lots of data (2007 - 2012), I did use RADIz2 in production for critical data, but we had 22 top level vdevs, each a 5 drive RAIDz2 and 10 hot spares. Striping data across 22 RAIDz2 gave us the performance we needed with the reliability. Thanks, noted. Will educate myself in the given direction. >> Thought it would be sufficient, but now I'm in doubt. > I think that 4 GB is slightly low for a file server, but it should not be too bad. The CPU should be fine. What are the drives themselves ? [Because with only 4 GB RAM you _will_ feel the effect of drive performance, and it is random I/Ops that really matter for ZFS] 2x HGST HDN724040ALE640, 4Tb, 64Mb, 7200. I even ordered 8Gb RAM for tests, but they mistakenly delivered me 4Gb!.. > >> I can live with reduced performance for my 1st NAS, but would be nice to have clear performance requirements in mind for planing future storage boxes. >> >> I see QNAPs and Synology NAS, they use like 1Ghz CPU and 1Gb of RAM for 4 HDD, so either I'm doing it wrong, either those NASes don't have performance (or safety?) at all. > Do they calculate checksums for end-to-end data integrity ? > What is their performance like ? > > The data integrity and reliability features of ZFS do come at a cost. For example, yesterday I explored QNAP TS-451 official site: https://www.qnap.com/i/en/product/model.php?II=143&event=2 (Intel® Celeron® 2.41GHz dual-core processor, 1GB DDR3L, etc) and review: http://www.storagereview.com/qnap_ts451_nas_review 473euro Promised performance of the models is about 100Mb/sec, even up to 200Mb/sec but ok, it's marketing and pretty diagrams ;) I have no personal experience with them, so no idea about checksums and reliability. best regards, Dmitriy From owner-freebsd-questions@freebsd.org Thu Sep 24 16:29:13 2015 Return-Path: Delivered-To: freebsd-questions@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 4F32EA05491 for ; Thu, 24 Sep 2015 16:29:13 +0000 (UTC) (envelope-from freebsd@spam.lifeforms.nl) Received: from tau.lfms.nl (tau.lfms.nl [IPv6:2a00:f320:0:3::30]) (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 D64361A86 for ; Thu, 24 Sep 2015 16:29:12 +0000 (UTC) (envelope-from freebsd@spam.lifeforms.nl) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.0.54]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id A3BA7892CC for ; Thu, 24 Sep 2015 18:29:00 +0200 (CEST) Received: from borax.dt.lfms.nl (borax.dt.lfms.nl [IPv6:2001:1af8:fe00:8414::112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id 6FF7A9C09099 for ; Thu, 24 Sep 2015 18:29:00 +0200 (CEST) From: Walter Hop Subject: Where should a FreeBSD program look for root certificates? Message-Id: <7D343A15-FC7A-4250-A5B8-4A6C35E3D4FC@spam.lifeforms.nl> Date: Thu, 24 Sep 2015 18:29:00 +0200 To: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 16:29:13 -0000 Hi, I've been sorting out a problem with my Go program (a HTTPS client) on = FreeBSD since the upgrade to Go 1.5. It turns out that Go changed its search order in which it looks for root = certificates. Go 1.4 programs would look for /etc/ssl/cert.pem, before trying = /usr/local/share/certs/ca-root-nss.crt [1]. Go 1.5 programs will try /usr/local/share/certs/ca-root-nss.crt first, = and then /etc/ssl/cert.pem [2]. This created an issue for me, as I always assumed that /etc/ssl/cert.pem = is more or less the 'official' location for root certificates in = FreeBSD, so I deploy my private CA root there. But since Go 1.5, Go programs will ignore /etc/ssl/cert.pem if the = ca_root_nss package is present, due to the change in search order. = Therefore my private certificates don=E2=80=99t validate. Is there an official position where FreeBSD programs should look for = this certificate store? I'm considering to open a Go bug to move /etc/ssl/cert.pem higher in the = search order, on the basis of: - Not only OpenBSD, but also FreeBSD uses /etc/ssl/cert.pem - FreeBSD core components, such as libfetch, use /etc/ssl/cert.pem [3] - The location of the ca_root_nss file is an implementation detail of = the package and should not override the core location After seeing libfetch source, I guess it would be a good thing to try = /usr/local/etc/ssl/cert.pem too. However, maybe I'm wrong, maybe /etc/ssl/cert.pem is not 'special' or = sanctioned, and there are good reasons to prefer = /usr/local/share/certs/ca-root-nss.crt which I am not realizing. What do you think Go (or other programs for that matter) should do? Thanks! WH References: 1. = https://github.com/golang/go/blob/release-branch.go1.4/src/crypto/x509/roo= t_unix.go#L16 2. = https://github.com/golang/go/blob/release-branch.go1.5/src/crypto/x509/roo= t_bsd.go#L11 3. = https://github.com/freebsd/freebsd/blob/master/lib/libfetch/common.c#L694 --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-questions@freebsd.org Thu Sep 24 16:40:31 2015 Return-Path: Delivered-To: freebsd-questions@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 4C858A05C60 for ; Thu, 24 Sep 2015 16:40:31 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 2F0921268 for ; Thu, 24 Sep 2015 16:40:30 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id A26F23F78E for ; Thu, 24 Sep 2015 12:40:24 -0400 (EDT) Message-ID: <56042774.6070404@sneakertech.com> Date: Thu, 24 Sep 2015 12:40:20 -0400 From: Quartz MIME-Version: 1.0 To: FreeBSD questions Subject: sync vs async vs zfs Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 16:40:31 -0000 I'm trying to spec out a new system that looks like it might be very sensitive to sync vs async writes. However, after some research and investigation I've come to realize that I don't think I understand a/sync as well as I thought I did and might be confused about some of the fundamentals. Can someone point me to a good "newbie's guide" that explains sync vs async from the ground up? one that makes no assumptions about prior knowledge of filesystems and IO. And likewise, another guide specifically for how they relate to zfs pool/vdev configuration? Thanks in advance. From owner-freebsd-questions@freebsd.org Thu Sep 24 18:46:14 2015 Return-Path: Delivered-To: freebsd-questions@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 35118A08DF9 for ; Thu, 24 Sep 2015 18:46:14 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (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 E959B1E72 for ; Thu, 24 Sep 2015 18:46:12 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgx61 with SMTP id 61so51935278qgx.3 for ; Thu, 24 Sep 2015 11:46:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=OVpPrICU5R+Oq0hbzRFdwMaRI2EEQKKzEYb2eJOIQVM=; b=LjPdTtuKXGYewKlY5lbhlms0QL7faHhcZwLGQnzPOrxoY7+Z6i8YD/b1NOUKx2Eq+k YdviU8EeArHDjXz8f48/mGJJMMcGABxZG8/N+q8Ggk5Eg+XSnFBi0oASsFsA7GXox15m JvcRzT7Wg187I8d4fIYvR8tcycRpzhH21MDP1JUN+fCu9f98nwwNPivtrKpyvXSn5L0j /EhPoOJk77EPTc0/r11JSB0KjyPlx1IfEcXj/MFel6Wc68PJWENwsaLAiHgsZOclcj07 ap1mORVknOj72nxp5YZSEV+etu956AbkZNdC7K9USXyiywzh9pg9BYvuPVk8npkv2R1/ g53A== X-Gm-Message-State: ALoCoQl78+5eu7woRgVj0+Hshw/m6V9JaiHjmwNl9bEhl9B0y6qjh01oC0qdGSgMgGTWRvw3/XmU X-Received: by 10.140.101.119 with SMTP id t110mr1556676qge.71.1443119884003; Thu, 24 Sep 2015 11:38:04 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id 139sm4949302qhh.43.2015.09.24.11.38.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 11:38:01 -0700 (PDT) Subject: Re: zfs performance degradation Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <56042209.8040903@dim.lv> Date: Thu, 24 Sep 2015 14:37:56 -0400 Cc: FreeBSD Questions Content-Transfer-Encoding: quoted-printable Message-Id: <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> To: Dmitrijs X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 18:46:14 -0000 On Sep 24, 2015, at 12:17, Dmitrijs wrote: > I also get about 60-70MB/sec via CIFS or ftp, but my aim is to be = limited by network, so 100MB is wanted.=20 It=92s nice to want things. But be prepared to pay for the things you = want... > Or, to understand why it is not possible on my config :) > But simple dd of=3D/dev/null in the console shows me 110MB/sec=85 dd of anything, but especially of /dev/null is a very poor way of = measuring anything. Turn on compression and and do that test again. > iozone gives me the same 100+Mb/sec both on read and write. What size blocks ? Files ? Random or sequential I/O ? All that matters. > 2x HGST HDN724040ALE640, 4Tb, 64Mb, 7200. Consumer NAS drives=85 I have not purchased anything but an Enterprise = drive for close to 10 years now. The small additional cost is well worth = the longer (5 year) warranty and better build quality=85 there _is_ a = difference. Even looking at the specs, the uncorrectable error spec is a = very good indicator of build quality and these drives are typical 1 in = 10^14 consumer drives. Enterprise drives are typically an order of = magnitude better, 1 in 10^15. In your original post you mentioned WD Green drives, also consumer = grade. In my experience I have seen better performance from WD than = HGST, with Seagate at the bottom of the ladder. I was comparing all = Enterprise drives, and even among those offerings there are differences=85= the WD RE are noticeable faster than the SE. I look at svc_t as the = primary metric for _comparing_ drives. I create a simple striped zpool, = reboot the system to clear counters, then do _lots_ of (typically) = random I/O, then look at iostat -x and compare svc_t, lower numbers are = better. I generally don=92t buy matched drives for mirrors, but different makes = and models if I can. That way of there is a bad production run I don=92t = lose all my drives at once. When a drive fails I RMA it under warranty = and buy 2 more of the same type and capacity, one goes into the server = and the other sits on the shelf. Eventually I have enough drives to grow = the zpool and move on. > For example, yesterday I explored QNAP TS-451 > official site: = https://www.qnap.com/i/en/product/model.php?II=3D143&event=3D2 (Intel=AE = Celeron=AE 2.41GHz dual-core processor, 1GB DDR3L, etc) > and review: http://www.storagereview.com/qnap_ts451_nas_review > 473euro They _might_ be fine products, But I don=92t trust my data to = appliances. _I_ want to control the redundancy. > Promised performance of the models is about 100Mb/sec, even up to = 200Mb/sec but ok, it's marketing and pretty diagrams ;) And all the tests were probably done on empty (to start) volumes. You = can achieve similar numbers with ZFS with similar hardware and LOTS of = parallel clients. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 19:05:59 2015 Return-Path: Delivered-To: freebsd-questions@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 0B2EFA083D3 for ; Thu, 24 Sep 2015 19:05:59 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) (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 966331275 for ; Thu, 24 Sep 2015 19:05:58 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgx61 with SMTP id 61so52423929qgx.3 for ; Thu, 24 Sep 2015 12:05:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=HjXqVzYNdrnQi3pTA0Yz+UTBzBqzvA85ZpbE42h5FOM=; b=hv+hWEVjtqedTtzgETyDB4hXeIg3962u/77FPbHtWa4FK8Yy/3wDKelhvaa6gEiXiG 300cibjD3Lo4LQVKORsP162HIrGxiStaACq4muXEtbL6Anb7nVTKe29naM7rl/ISZGzf 5gKqWu7F5VU+Dtjn6NFmFim8I+YNpDCqfT6mJ7IoEG97BahMTOPTzvULutOgkV7ZfXoD YBCu+pvP8qtrnEggdLI9E1kOcleooA7aWk+x66Kg2ANYwkxYio2V9gxIC/+dZx+hEvFq laEhrbycctdpkc/49C2wtuAoFzECB/zS2+blamtcpxbHck8htE+B3G1+5IS58+Ga4ZFa qusw== X-Gm-Message-State: ALoCoQm/Oczu6aX4j0+CvGvO+8smKB+H/aIcybpia2gfDww0TuIOVCnV6f+jtRJS+/aRnh2M69st X-Received: by 10.140.151.76 with SMTP id 73mr1735917qhx.61.1443121557438; Thu, 24 Sep 2015 12:05:57 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id 200sm4998590qhh.26.2015.09.24.12.05.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 12:05:55 -0700 (PDT) Subject: Re: sync vs async vs zfs Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <56042774.6070404@sneakertech.com> Date: Thu, 24 Sep 2015 15:05:49 -0400 Cc: FreeBSD questions Content-Transfer-Encoding: quoted-printable Message-Id: <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> References: <56042774.6070404@sneakertech.com> To: Quartz X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 19:05:59 -0000 On Sep 24, 2015, at 12:40, Quartz wrote: > I'm trying to spec out a new system that looks like it might be very = sensitive to sync vs async writes. However, after some research and = investigation I've come to realize that I don't think I understand = a/sync as well as I thought I did and might be confused about some of = the fundamentals. Very short answer=85 Both terms refer to writes only, there is no such thing as a sync or = async read. In the case of an async write, the application code (App) asks the = Filesystem (FS) to write some data. The FS is free to do whatever it = wants with the data and respond immediately that is has the data and it = _will_ write it to non-volatile (NV) storage (disk). In the case of a sync write (at least as defined by Posix), the App asks = the FS to write some data and do not return until it is committed to NV = storage. The FS is required (by Posix) to _not_ acknowledge the write = until the data _has_ been committed to NV storage. So in the first case, the FS can accept the data, put it in it=92s = =93write cache=94, typically RAM, and respond to the App that the write = is complete. When the FS has the time it then commits the data to NV = storage. If the system crashes after the App has =93written=94 the data = but before the FS has committed it to NV storage, that data is lost. In the second case, the FS _must_not_ respond to the APP until the data = is committed to NV storage. The App can be certain that the data is = safe. This is critical for, among other things, databases processing = transactions in specific order or time. > Can someone point me to a good "newbie's guide" that explains sync vs = async from the ground up? one that makes no assumptions about prior = knowledge of filesystems and IO. And likewise, another guide = specifically for how they relate to zfs pool/vdev configuration? I don=92t know of a basic guide to this, I just learned it from various = places over 20 years in the business. In terms of ZFS, the ARC acts as both write buffer and read cache. You = can see this easily when running benchmarks such as iozone with files = smaller than the amount of RAM. When making an async write call the FS = responds almost immediately and you are measuring the efficiency of the = ZFS code and memory bandwidth :-) I have seen write performance in the = 10=92s of GB/sec on drives that I know do not have that kind of = bandwidth. Make the ARC too small to hold the entire file or make the = file too big to fit you start seeing the performance of the drives. This = is due (in part) to the TXG design of ZFS. You can watch the drives (via = iostat -x) and see ZFS committing data in bursts (originally up to 30 = seconds apart, now up to 5 seconds apart). Now when you issue a sync write to ZFS, in order to adhere to Posix = requirements, ZFS _must_ commit the data to NV storage before returning = an acknowledgement to the App. So ZFS has the ZIL (ZFS Intent Log). All = sync writes are committed to the ZIL immediately and then incorporated = into the dataset itself as TXGs commit. The ZIL is just space stolen = from the zpool _unless_ you have a Separate Log Device (SLOG), which is = just a special type of vdev (like spare) and is listed as =93log=94 in a = zpool status. By having a SLOG you can do two things, 1) ZFS no longer = needs to steal space from the dataset for the ZIL, so the dataset will = be much less fragmented and 2) you can use a device which is much faster = than the main zpool devices (like a ZeusRAM or fast SSD) and greatly = speed up sync writes. You can see the performance difference between async and sync using = iozone with the -o option. =46rom the iozone manage: "Writes are = synchronously written to disk. (O_SYNC). Iozone will open the files = with the O_SYNC flag. This forces all writes to the file to go = completely to disk before returning to the benchmark.=94 I hope this gets you started =85 -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Thu Sep 24 20:53:27 2015 Return-Path: Delivered-To: freebsd-questions@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 1DFEFA08ACE for ; Thu, 24 Sep 2015 20:53:27 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 F33A51319 for ; Thu, 24 Sep 2015 20:53:26 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id AB2D93F71B for ; Thu, 24 Sep 2015 16:53:24 -0400 (EDT) Message-ID: <560462C4.6030106@sneakertech.com> Date: Thu, 24 Sep 2015 16:53:24 -0400 From: Quartz MIME-Version: 1.0 To: FreeBSD questions Subject: Re: sync vs async vs zfs References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> In-Reply-To: <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 20:53:27 -0000 > Very short answer… OK, thanks. So far that lines up with what I thought I knew. I still think I might be fuzzy on what constitutes an 'app' in this context though, presumably you're also counting services like nfs, etc? Basically, when considering just boring file copies, which things are or are not async and when? Under what circumstances is sync actually used in the real world? >you can > use a device which is much faster than the main zpool devices Also 1) A SLOG's only purpose is to reduce fragmentation and increase sync speed, correct? Re: speed, using a SLOG that's the same speed as the other drives in a pool is mostly pointless, right? 2) Async doesn't really care how your pool is constructed, and a SLOG is really the only thing that seriously makes a difference for sync, correct? From owner-freebsd-questions@freebsd.org Thu Sep 24 21:26:37 2015 Return-Path: Delivered-To: freebsd-questions@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 BE46EA08822 for ; Thu, 24 Sep 2015 21:26:37 +0000 (UTC) (envelope-from dave@dgmm.net) Received: from outbound-queue-2.mail.thdo.gradwell.net (outbound-queue-2.mail.thdo.gradwell.net [212.11.70.35]) by mx1.freebsd.org (Postfix) with ESMTP id 818201D79 for ; Thu, 24 Sep 2015 21:26:37 +0000 (UTC) (envelope-from dave@dgmm.net) Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-2.mail.thdo.gradwell.net (Postfix) with ESMTP id 1CC3E55394 for ; Thu, 24 Sep 2015 22:25:30 +0100 (BST) Received: from cpc7-jarr12-2-0-cust882.16-2.cable.virginm.net (HELO amd.asgard.uk) (92.238.71.115) (smtp-auth username dave%pop3.dgmm.net, mechanism plain) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with ESMTPA; Thu, 24 Sep 2015 22:25:29 +0100 From: Dave To: freebsd-questions@freebsd.org Subject: Re: 10.2 graphics problem Date: Thu, 24 Sep 2015 22:25:28 +0100 Message-ID: <5552406.tZCDeim3VM@amd.asgard.uk> User-Agent: KMail/4.14.3 (FreeBSD/9.3-RELEASE-p24; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <8F541F88-2EAE-434C-B52C-43A744F54ADD@slsware.net> <1F197AA4-CE10-4195-B0D5-028C30036CAA@slsware.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Gradwell-MongoId: 56046a49.14a31-533a-2 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: dave@pop3.dgmm.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 21:26:37 -0000 On Friday 18 September 2015 21:27:15 Warren Block wrote: > I have a bunch of short articles on various subjects mostly related to > FreeBSD, too: http://www.wonkity.com/~wblock/docs/ Thanks for creating that. The PXE page was especially interesting. From owner-freebsd-questions@freebsd.org Thu Sep 24 21:40:35 2015 Return-Path: Delivered-To: freebsd-questions@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 89270A08016 for ; Thu, 24 Sep 2015 21:40:35 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 224251607 for ; Thu, 24 Sep 2015 21:40:35 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by wicge5 with SMTP id ge5so1968023wic.0 for ; Thu, 24 Sep 2015 14:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=SrfD4vy+mIZ+AbTST9SLAumWu2Zmet8PVBitROyybTE=; b=iyawA57oaDL6ErGBewYeT/84IMV58Ihu5cj/cEe1WcKPyWs0DoEdpeVmNKATsCFCqc B0Ko0IHXQYB+uhnBWMoEA/WKErL4Vkh6GNQGCmfCGScPAX6utMhZnq5VAioSvA0SXbjH cHwcWJBJUTiNaEcWQW7kCt09t4qHrtNIVhoZOhaRvQcf+wu1BkTL4rwSDV3Gox5w78P0 Ji4eAsnbMfhY4aH2Sddp7dKWHtAmepzhYRr3pMGq1B0F99ww5XPq6Os98iu4UpRcJSjp xdJtlogd5WJgtJiHNINI0iAwgevLZML4d0FZhCl1MumHSBNG+LsTGCA8O7rqvA32fzmK CmhA== MIME-Version: 1.0 X-Received: by 10.180.104.65 with SMTP id gc1mr8812949wib.67.1443130833424; Thu, 24 Sep 2015 14:40:33 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.28.50.132 with HTTP; Thu, 24 Sep 2015 14:40:33 -0700 (PDT) In-Reply-To: <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> Date: Thu, 24 Sep 2015 23:40:33 +0200 X-Google-Sender-Auth: if9jcgA1gB5bl-Z2c5XtGRrNs5M Message-ID: Subject: Re: zfs performance degradation From: CeDeROM To: Paul Kraus Cc: Dmitrijs , FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 21:40:35 -0000 For RAID/NAS use ondy WD RED drives family :-) Others WILL break timings with hidden error verify mechanisms.. http://www.wdc.com/red -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-questions@freebsd.org Thu Sep 24 23:27:43 2015 Return-Path: Delivered-To: freebsd-questions@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 B96D5A07713 for ; Thu, 24 Sep 2015 23:27:43 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 995391C8A for ; Thu, 24 Sep 2015 23:27:43 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id A0AB33F6D6 for ; Thu, 24 Sep 2015 19:27:41 -0400 (EDT) Message-ID: <560486ED.3030005@sneakertech.com> Date: Thu, 24 Sep 2015 19:27:41 -0400 From: Quartz MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: 10.2 graphics problem References: <8F541F88-2EAE-434C-B52C-43A744F54ADD@slsware.net> <1F197AA4-CE10-4195-B0D5-028C30036CAA@slsware.net> <5552406.tZCDeim3VM@amd.asgard.uk> In-Reply-To: <5552406.tZCDeim3VM@amd.asgard.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 23:27:43 -0000 > Thanks for creating that. The PXE page was especially interesting. As an aside, his notes on syslinux v4 are out of date. In recent versions things have been rearchitected and broken out into a dozen support files with a different directory layout. (Just FYI in case you try to follow the instructions literally). From owner-freebsd-questions@freebsd.org Fri Sep 25 00:58:59 2015 Return-Path: Delivered-To: freebsd-questions@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 897AEA089B8 for ; Fri, 25 Sep 2015 00:58:59 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) (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 479B51959 for ; Fri, 25 Sep 2015 00:58:58 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkfq186 with SMTP id q186so36884020qkf.1 for ; Thu, 24 Sep 2015 17:58:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=FUzQ9SV7JEKPX15qnPvyAaCBFUItNRuNXBZLlR1QOLA=; b=RZjzEziWzi2Czf6RlYv/gybJ/Mc+gOHYpJg6LXJP19xdbohleetlKnMAYdyjt0njrD vOGZagcKwgOgTuwSHAYPvDL7dAtRkIhFVevFHqoes/I06Yb9oKS+LSFit1dw+KRQ5S0u m9D1aIvdtdM34VHYhKtx9/bnJg6Cr8EXc8lG1gQ9SgAd/5Pg2eIndN5nNtXHN6bYPyvw eoCuCrvwSwp69Gqor1JwKM+6e0z+ws3k9ddJzjykW/iiDdEmDvkl1Fn3URGNwu2WYn/I RpW1cwz4ULEvG7bvRitbPdpB6jSCmz+xUh7RWQEdARWTzXMDYMRCRAhBqwujwfKntw+1 cazA== X-Gm-Message-State: ALoCoQkei6y5F733M+0HIiU/58z46guKMeyzfNr2I1YIhlIDEOQ3HL501lfGV7B4xFKQeeM29FGZ X-Received: by 10.55.15.3 with SMTP id z3mr3047513qkg.29.1443142732222; Thu, 24 Sep 2015 17:58:52 -0700 (PDT) Received: from [192.168.2.138] (pool-100-4-179-8.albyny.fios.verizon.net. [100.4.179.8]) by smtp.gmail.com with ESMTPSA id x81sm451642qha.24.2015.09.24.17.58.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 17:58:50 -0700 (PDT) Subject: Re: zfs performance degradation Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: Date: Thu, 24 Sep 2015 20:58:48 -0400 Cc: Dmitrijs , CeDeROM Content-Transfer-Encoding: quoted-printable Message-Id: <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> To: FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 00:58:59 -0000 On Sep 24, 2015, at 17:40, CeDeROM wrote: > For RAID/NAS use ondy WD RED drives family :-) Others WILL break > timings with hidden error verify mechanisms.. >=20 > http://www.wdc.com/red I assume you are referring to the other =93color=94 drives. I have had = no issues with the RE and SE series of Datacenter drives in zpool = configurations. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Fri Sep 25 01:11:13 2015 Return-Path: Delivered-To: freebsd-questions@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 931C6A0925E for ; Fri, 25 Sep 2015 01:11:13 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f48.google.com (mail-qg0-f48.google.com [209.85.192.48]) (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 5601D1FEA for ; Fri, 25 Sep 2015 01:11:13 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgt47 with SMTP id 47so58978513qgt.2 for ; Thu, 24 Sep 2015 18:11:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=+JmkWvdbwXOYmkVTeaBSzylrfIujdPWbMm0wUPdPmGM=; b=J1JxQ52hGvQjBYBay87/9cayoXsZ0KStPObow4IDC1uVZPaoZL3BXPn2AawYWomr5w KZGZPqsjIBp27Fkqcm1YuDPPB6gBO7EtghGlSccq65uWDk5jBwpH4/Rzf+gGwYibdVWX 1O7KaxGrJL5dXFMr4YdvuZMGSONAxXX/0I4ZXVdS2lmk68mn9PyzQUj1BGNqSWjjXoLm Otc/Hy3mnfVPA/l3Xmk+kVQRtsshP+6l+kKv4txbKS6cFXXnWuymj/sl8sI7qbjFw/6Q w0f716fCCXKR5YmcmMMPUbVcr2JHbfBljFND07gvNGnr0sOek6AgiVW6PREN38DigD/G Exhg== X-Gm-Message-State: ALoCoQneW+70X3wU8JQXsN2QKD/7Yp01fUGtkcOhCVVDOLXfg8WJolNYacYY4u12qn7lEQw07+/c X-Received: by 10.140.39.168 with SMTP id v37mr3235453qgv.24.1443143471571; Thu, 24 Sep 2015 18:11:11 -0700 (PDT) Received: from [192.168.2.138] (pool-100-4-179-8.albyny.fios.verizon.net. [100.4.179.8]) by smtp.gmail.com with ESMTPSA id w3sm482814qha.0.2015.09.24.18.11.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 18:11:09 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: sync vs async vs zfs From: Paul Kraus In-Reply-To: <560462C4.6030106@sneakertech.com> Date: Thu, 24 Sep 2015 21:11:07 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> <560462C4.6030106@sneakertech.com> To: Quartz , FreeBSD questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 01:11:13 -0000 On Sep 24, 2015, at 16:53, Quartz wrote: >> Very short answer=85 >=20 > OK, thanks. So far that lines up with what I thought I knew. I still = think I might be fuzzy on what constitutes an 'app' in this context = though, presumably you're also counting services like nfs, etc? Anything that generates a FS read or write request :-) So yes, the = kernel NFS server counts. > Basically, when considering just boring file copies, which things are = or are not async and when? Under what circumstances is sync actually = used in the real world? I expect that system utilities like cp and tar do not do sync writes. = sync writes are supposed to be a special case, used only when needed. I = run into them with VBox writing to <>.vmdk files. > you can >> use a device which is much faster than the main zpool devices >=20 > Also >=20 > 1) A SLOG's only purpose is to reduce fragmentation and increase sync = speed, correct? Re: speed, using a SLOG that's the same speed as the = other drives in a pool is mostly pointless, right? Correct. And I proved that on one of my servers in pre-prodcuction = testing. I was able to find the bottleneck using iozone -o and then = added a mirrored pair of SSD as SLOG write performance went _down_ for = 4KB random writes! I then tested the SSDs on their own and confirmed = that the performance I was seeing was the native performance of the = SSDs. I asked for recommendations of a good, fast SSD over on the = OpenZFS list and ordered a pair of Intel 200 GB S3710 SSDs, they are = back ordered, so the server awaits full production use. =20 > 2) Async doesn't really care how your pool is constructed, and a SLOG = is really the only thing that seriously makes a difference for sync, = correct? Not quite true. Once you get through the ARC the configuration of the = zpool _will_ matter to performance. In fact, for reads, unless you = workload closely matches the prefetch algorithm, the zpool layout will = have an effect on performance. Remember, as a general rule, you get one = spindle=92s (drive=92s) worth of performance per top level vdev in the = zpool. So a zpool with one vdev that is an 8 drive RAIDz2 will have much = less performance than a set of 4 2-way mirrors. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Fri Sep 25 02:05:39 2015 Return-Path: Delivered-To: freebsd-questions@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 38B3FA08427 for ; Fri, 25 Sep 2015 02:05:39 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 183621903 for ; Fri, 25 Sep 2015 02:05:38 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id B2D823F73C for ; Thu, 24 Sep 2015 22:05:36 -0400 (EDT) Message-ID: <5604ABF0.3060007@sneakertech.com> Date: Thu, 24 Sep 2015 22:05:36 -0400 From: Quartz MIME-Version: 1.0 To: FreeBSD questions Subject: Re: sync vs async vs zfs References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> <560462C4.6030106@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 02:05:39 -0000 > I expect that system utilities like cp and tar do not do sync writes. > sync writes are supposed to be a special case, used only when needed. > I run into them with VBox writing to<>.vmdk files. NFS forces sync though, doesn't it? What if you're cp-ing to a mounted share? I'm not sure I totally understand how all this interacts. >> 2) Async doesn't really care how your pool is constructed, and a >> SLOG is really the only thing that seriously makes a difference for >> sync, correct? > > Not quite true. Once you get through the ARC the configuration of the > zpool _will_ matter to performance. Maybe I worded that badly. What I meant was that whereas sync write performance is strongly affected by a SLOG, async writes have no special considerations of their own that don't also affect sync, right? From owner-freebsd-questions@freebsd.org Fri Sep 25 02:10:19 2015 Return-Path: Delivered-To: freebsd-questions@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 3CDACA08718 for ; Fri, 25 Sep 2015 02:10:19 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 187CF1A69 for ; Fri, 25 Sep 2015 02:10:19 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id 22B6D3F74A for ; Thu, 24 Sep 2015 22:10:18 -0400 (EDT) Message-ID: <5604AD09.4080603@sneakertech.com> Date: Thu, 24 Sep 2015 22:10:17 -0400 From: Quartz MIME-Version: 1.0 To: FreeBSD questions Subject: Re: sync vs async vs zfs References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> <560462C4.6030106@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 02:10:19 -0000 >> 1) A SLOG's only purpose is to reduce fragmentation and increase >> sync speed, correct? Re: speed, using a SLOG that's the same speed >> as the other drives in a pool is mostly pointless, right? > > Correct. And I proved that on one of my servers in pre-prodcuction > testing. Tack-on question: would an identical-speed SLOG still speed up the pool by proxy simply by reducing IO load on the vdev(s) and/or reducing head travel on the drives? From owner-freebsd-questions@freebsd.org Fri Sep 25 02:49:41 2015 Return-Path: Delivered-To: freebsd-questions@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 73F2CA09DFA for ; Fri, 25 Sep 2015 02:49:41 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) (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 35B97199B for ; Fri, 25 Sep 2015 02:49:40 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkdw123 with SMTP id w123so37630439qkd.0 for ; Thu, 24 Sep 2015 19:49:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=1bTHte7619r9mi0lri01mfb8Pkkj2qMZ1crc86CZGfE=; b=PBm23MvbwGXLXM892pQn2X8aMxRuxeK65VIFZ//KRVIQoqoLahzb7VHI8plutYZJLj kEzxy6HYngpZseksHlNrBpUHX01qepVz5MWPcc6FX8Pz60Ikh4UmnFmwEWEA4kAK8NB1 /KSEaLW/+taapXLjldZRxIhbM+93ubrNhA3Q6RifK2WYp9+yzQP6sJ/NpRoK1hSFUgqp WORNv5E5vgjI1/9PsLhVbeBVQjeNkq7H2BSPOJj/4B8M5nz/XNJHKLjEcrtcmlqx056J kCHngBWfAgqPVAdaPlY+3W2tmTOWlD7NpkvDGz60l9ATEVu3Z2vMZclYUPthiKZoBxnJ GBJg== X-Gm-Message-State: ALoCoQl7yAzwDGnHzFZrCxG7im5NKfbmSptSjSQ9BAAh2vSRqVyYEw4q2ivCLY8YQJd6yMyeefKn X-Received: by 10.55.23.9 with SMTP id i9mr3586384qkh.22.1443149373913; Thu, 24 Sep 2015 19:49:33 -0700 (PDT) Received: from [192.168.2.138] (pool-100-4-179-8.albyny.fios.verizon.net. [100.4.179.8]) by smtp.gmail.com with ESMTPSA id f86sm629146qkf.0.2015.09.24.19.49.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Sep 2015 19:49:32 -0700 (PDT) Subject: Re: sync vs async vs zfs Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <5604ABF0.3060007@sneakertech.com> Date: Thu, 24 Sep 2015 22:49:29 -0400 Cc: FreeBSD questions Content-Transfer-Encoding: quoted-printable Message-Id: <09CBDA9F-28FD-4579-A648-E6D2F5660A91@kraus-haus.org> References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> <560462C4.6030106@sneakertech.com> <5604ABF0.3060007@sneakertech.com> To: Quartz X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 02:49:41 -0000 On Sep 24, 2015, at 22:05, Quartz wrote: >> I expect that system utilities like cp and tar do not do sync writes. >> sync writes are supposed to be a special case, used only when needed. >> I run into them with VBox writing to<>.vmdk files. >=20 > NFS forces sync though, doesn't it? What if you're cp-ing to a mounted = share? I'm not sure I totally understand how all this interacts. Reading the NFS ver 3 RFC (1813, available here: = https://tools.ietf.org/html/rfc1813, look for the descriptions of the = WRITE and COMMIT procedures), it looks like NFS ver 2 was sync only, = while ver 3 added the ability (at the protocol layer) to require sync = data, sync data + metadata, or async behavior. =46rom some Linux NFS = notes I found it appears that the default Linux behavior is sync, but = you can disable sync on the server side (as you can with ZFS) in which = case the NFS server does not follow the protocol specification. =46rom the FreeBSD man page options for mount_nfs: wcommitsize=3D Set the maximum pending write commit size to the = speci- fied value. This determines the maximum amount of = pend- ing write data that the NFS client is willing to = cache for each file. This implies that the FreeBSD NFS client fully implements the ver 3 = protocol which permits the client to cache data until an fsync call is = made or the amount of data in the client cache reaches =93wcommitsize=94. = Essentially, async behavior. It does not look like (from reading the exports man page) you can = disable handling of sync data, sync data + metadata, or async on the NFS = server side. In other words, the FreeBSD NFS server does what the client = instructs it, as it should to comply with the NFS Ver 3 specification in = the RFC. >>> 2) Async doesn't really care how your pool is constructed, and a >>> SLOG is really the only thing that seriously makes a difference for >>> sync, correct? >>=20 >> Not quite true. Once you get through the ARC the configuration of the >> zpool _will_ matter to performance. >=20 > Maybe I worded that badly. What I meant was that whereas sync write = performance is strongly affected by a SLOG, async writes have no special = considerations of their own that don't also affect sync, right? Correct. Any configuration change that effects async performance will = effect sync performance as well. While the ZIL/SLOG can effect sync = performance, they are not involved in async writer operations at all, so = cannot have nay effect on sync writes. Although, I suppose you _could_ say that an increase in the amount of = RAM available for the ARC may increase async write performance, such an = increase in ARC would have little to no effect on sync writes. While = sync writes _do_ go through the ARC, the ZIL/SLOG insulates the App = trying to write the data from that. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Fri Sep 25 13:12:06 2015 Return-Path: Delivered-To: freebsd-questions@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 DA122A0858C for ; Fri, 25 Sep 2015 13:12:06 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ACEE71F89 for ; Fri, 25 Sep 2015 13:12:06 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from c-66-41-25-68.hsd1.mn.comcast.net ([66.41.25.68] helo=[192.168.0.107]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZfSn8-000ObR-Ld for freebsd-questions@freebsd.org; Fri, 25 Sep 2015 08:11:58 -0500 Subject: Re: zfs performance degradation To: freebsd-questions@freebsd.org References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> From: Graham Allan Message-ID: <5605481D.10902@physics.umn.edu> Date: Fri, 25 Sep 2015 08:11:57 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 13:12:06 -0000 On 9/24/2015 7:58 PM, Paul Kraus wrote: > On Sep 24, 2015, at 17:40, CeDeROM wrote: > >> For RAID/NAS use ondy WD RED drives family :-) Others WILL break >> timings with hidden error verify mechanisms.. >> >> http://www.wdc.com/red > > I assume you are referring to the other “color” drives. I have had no > issues with the RE and SE series of Datacenter drives in zpool > configurations. WD Reds are pretty solid, and I have used hundreds of them in ZFS pools without *apparent* issues, while I would never consider the blue or even less Green for this. However they're still a low-cost option - if I'd had the funds I would much rather have used SE or RE! From owner-freebsd-questions@freebsd.org Fri Sep 25 14:01:29 2015 Return-Path: Delivered-To: freebsd-questions@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 8B70FA083CE for ; Fri, 25 Sep 2015 14:01:29 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) (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 494081BBC for ; Fri, 25 Sep 2015 14:01:28 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkdw123 with SMTP id w123so42312816qkd.0 for ; Fri, 25 Sep 2015 07:01:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=wT9OovMEgbRxCvNAFrjNsM1Jwi7Bt7ThlmcznNWxHp8=; b=gvCyDmsqTzFpKRBBavTMUiS5S7FBh4JoEGg0y4SfJnccMU8J17ZkV5GbeUz2dcW4tP HwmJmRvyjc84N7gM+enMxVe97efqsubM1Y2DCa8WUB0JNUI4RlozfY/gJS6a/d3pFxtp Mzn+hamW0HXBNJFHWKd1hIun/+Ay5M5pJHP55BkhfBLNV7kl9i/mME/s26llsEF0s1YW qwN8/4qZpw+w5Ic649ItFBoXBZmE9k089pgkdqA7CI1Ynw6UOzROeKCFaCQc7B7kPby4 +x02W97LJ8FVfqADKVEaTqm8XZsUO9hHHu3c9lNd+pz1TQ/8vwfZHycmH3hnONBMjRam OjeA== X-Gm-Message-State: ALoCoQm/7r0IVX5yNSv8n59xlBJYsETHmZP44ZSG/CnQ6pAP203A/xKPTU/HafYs7Py+oSdordyz X-Received: by 10.55.25.94 with SMTP id k91mr6328334qkh.51.1443189680828; Fri, 25 Sep 2015 07:01:20 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id r5sm1434931qha.48.2015.09.25.07.01.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Sep 2015 07:01:19 -0700 (PDT) Subject: ZFS ready drives WAS: zfs performance degradation Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <5605481D.10902@physics.umn.edu> Date: Fri, 25 Sep 2015 10:01:18 -0400 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> To: Graham Allan X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 14:01:29 -0000 On Sep 25, 2015, at 9:11, Graham Allan wrote: > On 9/24/2015 7:58 PM, Paul Kraus wrote: >> On Sep 24, 2015, at 17:40, CeDeROM wrote: >>=20 >>> For RAID/NAS use ondy WD RED drives family :-) Others WILL break >>> timings with hidden error verify mechanisms.. >>>=20 >>> http://www.wdc.com/red >>=20 >> I assume you are referring to the other =93color=94 drives. I have = had no >> issues with the RE and SE series of Datacenter drives in zpool >> configurations. >=20 > WD Reds are pretty solid, and I have used hundreds of them in ZFS = pools without *apparent* issues, while I would never consider the blue = or even less Green for this. However they're still a low-cost option - = if I'd had the funds I would much rather have used SE or RE! Your comment reminded me=85 one of the big reasons to only use = Enterprise / Datacenter / NAS rated drives for ZFS is the way the = _drive_ handles errors. Many of the consumer drives will retry a failing = READ many, many times. This _can_ lead to timeout issues in the OS and = ZFS. The reasoning here is that for a consumer, getting a good read is = worth the extra time (I have seen reports of up to 30 seconds before = giving up) because the consumer probably does not have any redundancy. = With ZFS (assuming something more than a basic stripe configuration) you = want the drive to return the read error to the OS as fast as it can so = that the OS and ZFS can deal with it. I have also used WD Green and Purple drives with ZFS, but I do not = expect Enterprise grade operation out of them. I also question the economics of the consumer drives, once you take the = 5 year warranty in account. Looking at Newegg for 2 TB 3.5=94 WD drives: Green $79 2-year Purple $85 3-year Red NAS $90 3-year Black $119 5-year SE $130 5-year Red Pro NAS $134 5-year RE $153 5-year So the premium cost for the Red NAS is $11 over the cheapest option. The premium cost for a 5-year warranty (Black, not rated for 24/7 or = NAS, a high end desktop drive) is $40. The Premium for the cheapest Datacenter drive (SE) is $51, or more than = a 50% increase in cost. But the warranty is more than twice as long = (2-year vs. 5-year). In my experience, most 5-year warranty drives fail in some way during = the warranty period. This is especially true of Seagate. On my home = system, 5 out of 6 Seagate ES.2 series drives failed within 5 years, the = last one failed within 6 months of the warranty expiration. Half of my = HGST drives have failed under warranty (so far, they have not all hit = end of warranty yet), none of my WD RE or SE series have failed, but = they are the youngest drives in my collection. So part of what I am paying for with the Datacenter drives is the = knowledge that I will NOT have to pay to replace that drive for 5 years. -- Paul Kraus paul@kraus-haus.org From owner-freebsd-questions@freebsd.org Fri Sep 25 14:21:53 2015 Return-Path: Delivered-To: freebsd-questions@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 AC0E6A09076 for ; Fri, 25 Sep 2015 14:21:53 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 751221A0C for ; Fri, 25 Sep 2015 14:21:53 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8PELiur002618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 25 Sep 2015 09:21:45 -0500 Subject: Re: ZFS ready drives WAS: zfs performance degradation References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> Cc: freebsd-questions@freebsd.org From: "William A. Mahaffey III" Message-ID: <56055878.3020700@hiwaay.net> Date: Fri, 25 Sep 2015 09:27:14 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 14:21:53 -0000 On 09/25/15 09:07, Paul Kraus wrote: > On Sep 25, 2015, at 9:11, Graham Allan wrote: > >> On 9/24/2015 7:58 PM, Paul Kraus wrote: >>> On Sep 24, 2015, at 17:40, CeDeROM wrote: >>> >>>> For RAID/NAS use ondy WD RED drives family :-) Others WILL break >>>> timings with hidden error verify mechanisms.. >>>> >>>> http://www.wdc.com/red >>> I assume you are referring to the other “color” drives. I have had no >>> issues with the RE and SE series of Datacenter drives in zpool >>> configurations. >> WD Reds are pretty solid, and I have used hundreds of them in ZFS pools without *apparent* issues, while I would never consider the blue or even less Green for this. However they're still a low-cost option - if I'd had the funds I would much rather have used SE or RE! > Your comment reminded me… one of the big reasons to only use Enterprise / Datacenter / NAS rated drives for ZFS is the way the _drive_ handles errors. Many of the consumer drives will retry a failing READ many, many times. This _can_ lead to timeout issues in the OS and ZFS. The reasoning here is that for a consumer, getting a good read is worth the extra time (I have seen reports of up to 30 seconds before giving up) because the consumer probably does not have any redundancy. With ZFS (assuming something more than a basic stripe configuration) you want the drive to return the read error to the OS as fast as it can so that the OS and ZFS can deal with it. > > I have also used WD Green and Purple drives with ZFS, but I do not expect Enterprise grade operation out of them. > > I also question the economics of the consumer drives, once you take the 5 year warranty in account. > > Looking at Newegg for 2 TB 3.5” WD drives: > > Green $79 2-year > Purple $85 3-year > Red NAS $90 3-year > Black $119 5-year > SE $130 5-year > Red Pro NAS $134 5-year > RE $153 5-year > > So the premium cost for the Red NAS is $11 over the cheapest option. > > The premium cost for a 5-year warranty (Black, not rated for 24/7 or NAS, a high end desktop drive) is $40. > > The Premium for the cheapest Datacenter drive (SE) is $51, or more than a 50% increase in cost. But the warranty is more than twice as long (2-year vs. 5-year). > > In my experience, most 5-year warranty drives fail in some way during the warranty period. This is especially true of Seagate. On my home system, 5 out of 6 Seagate ES.2 series drives failed within 5 years, the last one failed within 6 months of the warranty expiration. Half of my HGST drives have failed under warranty (so far, they have not all hit end of warranty yet), none of my WD RE or SE series have failed, but they are the youngest drives in my collection. > > So part of what I am paying for with the Datacenter drives is the knowledge that I will NOT have to pay to replace that drive for 5 years. > > -- > Paul Kraus > paul@kraus-haus.org Jumping in a bit, I have had fabulous luck w/ 7200 RPM 2.5" HGST drives, supposedly enterprise rated, batting 1.000 so far (knock, knock, knock ....). However those are *2.5"*, *NOT* 3.5". I got convinced several years ago that the 2.5" drives were better built specificationally mechanically & made the switch. There are brackets to mount 2 X 2.5" drives in a 3.5" bay, as well as kits to mount 4-6 2.5" drives in a 5.25" bay. Mind you this is for a *very* small sample, < 2 dozen, well-ventilated SOHO, *NOT* data-center, etc., but several are now 5-6 years old & so far, so good. YMMV & all that rot .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Fri Sep 25 19:42:35 2015 Return-Path: Delivered-To: freebsd-questions@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 25C7EA096CD for ; Fri, 25 Sep 2015 19:42:35 +0000 (UTC) (envelope-from healer@rpi.edu) Received: from smtp9.server.rpi.edu (gateway.canit.rpi.edu [128.113.2.229]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "canit.localdomain", Issuer "canit.localdomain" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D915811A6 for ; Fri, 25 Sep 2015 19:42:34 +0000 (UTC) (envelope-from healer@rpi.edu) Received: from smtp-auth1.server.rpi.edu (route.canit.rpi.edu [128.113.2.231]) by smtp9.server.rpi.edu (8.14.3/8.14.3/Debian-9.4) with ESMTP id t8PJgQTO014638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 25 Sep 2015 15:42:26 -0400 Received: from smtp-auth1.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth1.server.rpi.edu (Postfix) with ESMTP id 9C1B2580B1 for ; Fri, 25 Sep 2015 15:42:26 -0400 (EDT) Received: from [129.161.63.163] (biotech-upper-wl-404.dynamic2.rpi.edu [129.161.63.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: healer) by smtp-auth1.server.rpi.edu (Postfix) with ESMTPSA id 81DE158052 for ; Fri, 25 Sep 2015 15:42:26 -0400 (EDT) Subject: Re: Problems with ZFS file servers To: freebsd-questions@freebsd.org References: <55F5CF06.5080602@rpi.edu> <1442191342.426007007.amnhjwng@frv35.fwdcdn.com> <55F62523.7010402@rpi.edu> <1442267713.360040098.um8wwy4s@frv35.fwdcdn.com> From: Bob Healey Message-ID: <5605A3A5.7080905@rpi.edu> Date: Fri, 25 Sep 2015 15:42:29 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1442267713.360040098.um8wwy4s@frv35.fwdcdn.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 7.10] X-CanIt-Incident-Id: 02PlvGq4i X-CanIt-Geo: ip=129.161.63.163; country=US; region=Connecticut; city=Hartford; latitude=41.7424; longitude=-72.6905; http://maps.google.com/maps?q=41.7424,-72.6905&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.229 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 19:42:35 -0000 I've got another machine acting up, this machine is a Sun X2250, originally was running Solaris until this summer when the owner dropped the support contract. A zpool export, reinstall to FreeBSD 10.1, and zpool import and it was back in business. Most of the requested info can be found at http://origami.phys.rpi.edu/~healer/lepton. I am working on getting cacti installed. I am currently trying to rsync a workstation to this pool so I can reload the OS. If I use --bwlimit=10240 or lower, I have no issues, but if I don't rsync freezes on me on the client side. Bob Healey Systems Administrator Biocomputation and Bioinformatics Constellation and Molecularium healer@rpi.edu (518) 276-4407 On 9/14/2015 6:14 PM, Vladislav Prodan wrote: > camcontrol devlist > zpool list > zpool status > zfs list > cat /etc/sysctl.conf > cat /boot/loader.conf From owner-freebsd-questions@freebsd.org Fri Sep 25 20:25:05 2015 Return-Path: Delivered-To: freebsd-questions@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 19047A0958D for ; Fri, 25 Sep 2015 20:25:05 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AE63219FE for ; Fri, 25 Sep 2015 20:25:04 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.2/8.15.2) with ESMTPSA id t8PKOrRo048309 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 25 Sep 2015 21:24:54 +0100 (BST) (envelope-from matthew@FreeBSD.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org DKIM-Filter: OpenDKIM Filter v2.10.3 smtp.infracaninophile.co.uk t8PKOrRo048309 Authentication-Results: smtp.infracaninophile.co.uk/t8PKOrRo048309; dkim=none; dkim-atps=neutral X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6] claimed to be liminal.local Subject: Re: Problems with ZFS file servers To: freebsd-questions@freebsd.org References: <55F5CF06.5080602@rpi.edu> <1442191342.426007007.amnhjwng@frv35.fwdcdn.com> <55F62523.7010402@rpi.edu> <1442267713.360040098.um8wwy4s@frv35.fwdcdn.com> <5605A3A5.7080905@rpi.edu> From: Matthew Seaman X-Enigmail-Draft-Status: N1110 Message-ID: <5605AD8D.4080706@FreeBSD.org> Date: Fri, 25 Sep 2015 21:24:45 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <5605A3A5.7080905@rpi.edu> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bMkHs9PXFiKXUg6QQGveIkcXxM4M2LAjO" X-Virus-Scanned: clamav-milter 0.98.7 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 20:25:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bMkHs9PXFiKXUg6QQGveIkcXxM4M2LAjO Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 25/09/2015 20:42, Bob Healey wrote: > I've got another machine acting up, this machine is a Sun X2250, > originally was running Solaris until this summer when the owner dropped= > the support contract. A zpool export, reinstall to FreeBSD 10.1, and > zpool import and it was back in business. Most of the requested info > can be found at http://origami.phys.rpi.edu/~healer/lepton. I am > working on getting cacti installed. I am currently trying to rsync a > workstation to this pool so I can reload the OS. If I use > --bwlimit=3D10240 or lower, I have no issues, but if I don't rsync free= zes > on me on the client side. I've found, through bitter experience, that you need to apply some tunings to ZFS machines, and quite possibly some kernel patches too. When you're pumping wads of data into a ZFS machine at high speed, it is all too easy to get it to lock up. First up, the default setting where ZFS grabs all but 1GB of available RAM for use by the ARC is nuts. You need to chop that down and give the rest of the OS a fair share of RAM to play with by setting vfs.zfs.arc_max in /boot/loader.conf. What you set it to depends on the application mix on your server, but somewhere around 50% of available RAM seems reasonable to me. Reboot to enable that, obviously. If you're dumping a lot of data (especially if you're writing much more than will fit into system RAM) onto your ZFS box, and don't intend to be using that data actively any time soon, then it's a good idea to set properties to disable the primarycache and secondarycache on the ZFS you're writing to. Or set them to metadata only. Otherwise you'll just blow out your ARC caches which won't help system performance. You can turn caching on or off for specific ZFSes at any time. If that doesn't do enough to make your machine work reliably, then investigate using the patches from PR 187594: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187594 There are several versions of the patch but you should be able to find one that applies to the version of the OS you're using. Cheers, Matthew --bMkHs9PXFiKXUg6QQGveIkcXxM4M2LAjO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 iQJ8BAEBCgBmBQJWBa2UXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT5RIP/RqqZ/kpALiAqRxP+6/G01P3 D+necGn0gfYnEoXSfCjxxCBlcl2X159vKP+vJ5F27cOVTzUJUAhkhhP228G1X71A zOPcUCNQEcYnN+AJ3InNLtm8cnBarBJBBIWScJyZl3jMlOoIy62Q3EkHeCo7X9P2 AW61gulq4KpuloioOjRbT94nYNWY/WXlZWZOXh/lZvUHvSnoZmoL9VxYD+VpTKSz Jg0EQfA4uyzkGoeyvpOWlNrlsxD5yFqgpxSxL5uRcq6mbeNWnRuQ/FsdXav3SME2 pCC7EYDrjiXuLl7Bd/jLnpmFaIUThTxYV+Nn+klCuBav/+4vWWtlsNcj1Pju5Akl LFoy69YEzhSxPSRGA8IuYRMZqgaeBduNlN7v6p4yqBVy7+Xt/CP2EQjR5uBRcT9C TdLJVQXi1iz0LLrCJWPZSbeCEhR5gDEfYxs0cdJNPYNy4UyetSCvoRJSANQhZ8YD r1nsh5r752bwJH7K/X0Nwz2/HwXBdZpCsYgM/V/lMMYm89IcFen9NTaG/GMZIn9U wkGJXS+IBBQNyZ3ZEa2VDt/m6LknFEzqn0fK2LQwZBI+AJiAHZCyZjE1CJINgA8W FNjM1iJO/Ej4rNc05ZkJs4OMHg2c1rPrJSbc4HXzpE9UPwEWILS92ab3yf6YsVVx U4YAdC5XEHPWZWwdI2NH =oGQA -----END PGP SIGNATURE----- --bMkHs9PXFiKXUg6QQGveIkcXxM4M2LAjO-- From owner-freebsd-questions@freebsd.org Fri Sep 25 21:57:53 2015 Return-Path: Delivered-To: freebsd-questions@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 166B8A09202 for ; Fri, 25 Sep 2015 21:57:53 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) Received: from nm46-vm6.bullet.mail.gq1.yahoo.com (nm46-vm6.bullet.mail.gq1.yahoo.com [67.195.87.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDFBE115A for ; Fri, 25 Sep 2015 21:57:52 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1443218071; bh=JLpvl4gG9eW8vOWVya5UIkIX3BkPScvAuU1DDPAaSa0=; h=Date:From:Reply-To:To:Subject:From:Subject; b=GWRd+sWPv6YBGVI+wVMMVH0WvpxeXGV2768ZDSftpVe5IbfKUii41eGrrGFy9beM7FY4jZn30XMmYbbSgXJhU/+/9CcJFCEJ9vTd5WPaUwvwUMjs6tgXeL50vNli6F9IFbOBkwLK8p85Jr0Bc7Fgh7Y0YufDTfp1h4m0/lo09Rapb/trIGqyixOvxmzffRc2sxLsxBuTd+hOxqHH9WUP9vgRA/9YFe/smPzzVt2NXYDK4fOFgSmWOUbYW6UO2eCvlO+i5deFCPGi2D1AhASr3/EPi1TwBYWc3GTSkKdYVNh1G/mFulFx4pfAu9dsTdePnF0K47fSJt406q8SQNEtig== Received: from [127.0.0.1] by nm46.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 21:54:31 -0000 Received: from [216.39.60.182] by nm46.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 21:35:22 -0000 Received: from [98.137.12.207] by tm18.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 21:35:22 -0000 Received: from [127.0.0.1] by omp1015.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 21:35:22 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 905146.36055.bm@omp1015.mail.gq1.yahoo.com X-YMail-OSG: 7ROdTlQVM1mIso5iAxNtcGSanKcHFHCV2.rcN1E6fQAEjgbMEgIM6cBXCVp1XrO K_RjnWu_ylqUw78ulRvcrkAyCcv5Q4Gkzu2E1QhYr4faCbhKwKu02L5MNLSrwpkzrQ34UbCUN_D2 mMpH8L_66uOO1oNQcpYPuvBmoG.YDrp8JK7apNAmRf6x.pgD03AW5BszvMey0Roy.0fUqFOyetB9 BkXuCZx5RHqmrpWkBK.PkkpPYqGpDDGuqfY46wt4nayLtDEfEoOsaAsU2uXBjGyVId2UuwtJ8By6 J.W8dvN6Ia6iMHA_sXa0Z9QlbWQcqa25mcZEj3VEq2FsKZWmGLMpF.QIEhYM4ICPIqxjWUQgmdkq .vThqWij6eTfH_cMyZFd07Ez65J8DbXzPxZr5K.FdRkVfVfb3slTEo4EqpdU6Mq9arQ0waymbfM4 iZbPSYbLZOrw8iZFbH5w_3Fk9TqFMnjdU2SkXvCrbz..Fx.SfKtjg2Rq3eTrXEkFicD2DB03.hNr wpLF_q3vGnLzwGgL5hR0eEQ-- Received: by 98.137.12.251; Fri, 25 Sep 2015 21:35:22 +0000 Date: Fri, 25 Sep 2015 21:35:22 +0000 (UTC) From: Pallav Bose Reply-To: Pallav Bose To: "freebsd-questions@freebsd.org" Message-ID: <472489221.917644.1443216922050.JavaMail.yahoo@mail.yahoo.com> Subject: Interrupt storm and poor disk performance | mfi(4) driver | FreeBSD 8 | Dell PERC H730 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 21:57:53 -0000 Hello, I have a Dell PowerEdge R430 server with a PERC H730 RAID controller. I'm t= rying to get FreeBSD 8 to install and run on this server. At this time, I h= ave a patched version of the mfi(4) driver which attaches to the controller= . I'm aware of mrsas(4), but since I have scripts that use mfiutil(8), I'd = like to continue using the mfi(4) driver. A simple dd test shows SSD performance to be very poor: # dd if=3D/dev/mfid0 of=3D/dev/null bs=3D1m count=3D10241024+0 records in10= 24+0 records out1073741824 bytes transferred in 27.978784 secs (38377001 by= tes/sec) top -PHS shows a lot of CPU time being used by the swi6 s/w interrupt handl= er: last pid: 81270; =C2=A0load averages: =C2=A00.01, =C2=A00.05, =C2=A00.05 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 up 0+05:34:20 =C2=A015:45:51302 processes: 7 runni= ng, 278 sleeping, 17 waitingCPU 0: =C2=A00.0% user, =C2=A00.0% nice, =C2=A0= 0.0% system, 52.6% interrupt, 47.4% idleCPU 1: =C2=A00.0% user, =C2=A00.0% = nice, =C2=A00.0% system, =C2=A00.0% interrupt, =C2=A0100% idleCPU 2: =C2=A0= 0.0% user, =C2=A00.0% nice, =C2=A00.0% system, =C2=A00.0% interrupt, =C2=A0= 100% idleCPU 3: =C2=A00.0% user, =C2=A00.0% nice, =C2=A00.0% system, =C2=A0= 0.0% interrupt, =C2=A0100% idleCPU 4: =C2=A00.0% user, =C2=A00.0% nice, =C2= =A00.0% system, =C2=A00.0% interrupt, =C2=A0100% idleCPU 5: =C2=A00.0% user= , =C2=A00.0% nice, =C2=A00.0% system, =C2=A00.7% interrupt, 99.3% idleMem: = 48M Active, 4044K Inact, 997M Wired, 7144K Cache, 1248K Buf, 30G FreeSwap: =C2=A0 PID USERNAME =C2=A0 =C2=A0PRI NICE =C2=A0 SIZE =C2=A0 =C2=A0RES STAT= E =C2=A0 C =C2=A0 TIME =C2=A0 WCPU COMMAND=C2=A0 =C2=A010 root =C2=A0 =C2= =A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU5 =C2=A0 =C2=A05 = 319:51 100.00% {idle: cpu5}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0= 171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU2 =C2=A0 =C2=A02 293:32 94.58% {id= le: cpu2}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 = =C2=A0 0K =C2=A0 192K CPU3 =C2=A0 =C2=A03 298:46 93.65% {idle: cpu3}=C2=A0 = =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 1= 92K CPU4 =C2=A0 =C2=A04 278:55 92.58% {idle: cpu4}=C2=A0 =C2=A010 root =C2= =A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU1 =C2=A0 = =C2=A01 289:36 92.19% {idle: cpu1}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0= =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K RUN =C2=A0 =C2=A0 0 293:17 85.= 99% {idle: cpu0}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-24 =C2=A0 = =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A02 173:40 47.27% {swi= 6: task queue}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-64 =C2=A0 = =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A05 =C2=A011:50 =C2=A0= 0.00% {irq256: mfi0}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-32 =C2= =A0 =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A01 =C2=A0 6:26 = =C2=A00.00% {swi4: clock} The interrupt rate in case of irq256:mfi0 is very high, in spite of there b= eing no disk activity.=20 # vmstat -iinterrupt =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0total =C2=A0 =C2=A0 =C2=A0 rateirq4: = uart0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0257 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00irq9: acpi0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A01 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00irq18: ehci0 ehci1= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 71739 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A03cpu0: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40226355 =C2=A0 =C2=A0 =C2=A0 1998irq256: m= fi0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3= 642472 =C2=A0 =C2=A0 =C2=A0 =C2=A0180irq257: bge0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 34922 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A01cpu3: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 40229128 =C2=A0 =C2=A0 =C2=A0 1998cpu5: timer = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40228= 959 =C2=A0 =C2=A0 =C2=A0 1998cpu4: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40229014 =C2=A0 =C2=A0 =C2=A0 1998cpu1:= timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 40228629 =C2=A0 =C2=A0 =C2=A0 1998cpu2: timer =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40223967 =C2=A0 =C2=A0 =C2=A0= 1998Total =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0245115443 =C2=A0 =C2=A0 =C2=A012175 Procstat output: # procstat -kk 11 =C2=A0 =C2=A0 =C2=A0 # PID 11 taken from output of top=C2= =A0 PID =C2=A0 =C2=A0TID COMM =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TDN= AME =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 KSTACK=C2=A0 =C2=A011 100008 intr = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi3: vm=C2=A0 =C2=A011 100009 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi1: netisr 0 =C2=A0 mi_switc= h+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A0= 11 100010 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0= =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_tramp= oline+0xe=C2=A0 =C2=A011 100011 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork= _exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100012 intr =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205= ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 1000= 13 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0= =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0= xe=C2=A0 =C2=A011 100014 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi= 4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0= x112 fork_trampoline+0xe=C2=A0 =C2=A011 100015 intr =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithrea= d_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100021 intr= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi5: +=C2=A0 =C2=A011 100023 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi6: Giant task mi_switch+0x2= 05 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 10= 0024 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi6: task queue mi_swi= tch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2= =A011 100027 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi2: cambio = =C2=A0 =C2=A0 mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_tramp= oline+0xe=C2=A0 =C2=A011 100032 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 irq9: acpi0 =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork= _exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100033 intr =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq256: mfi0 =C2=A0 =C2=A0 mi_switch+0x205 ithr= ead_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100034 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq18: ehci0 ehc mi_switch+0x2= 05 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 10= 0039 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi0: uart uart =C2=A0m= i_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0= =C2=A011 100040 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq1: atkbd= 0 # kldload dtraceall# dtrace -n 'profile:::profile-276hz { @pc[stack()]=3Dco= unt(); }'dtrace: description 'profile:::profile-276hz ' matched 1 probe The above dtrace script is supposed to=C2=A0print all the stack traces seen= during the sampling period. The following stack trace occurs a large number of times: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`DELAY+0x64 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`bus_dmamap_load+0x3= a9=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_mapcmd+0x4f= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_startio+0x65=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_wait_command+0x9c= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_tbolt_sync_map_= info+0xb4=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_handle= _map_sync+0x39=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`taskq= ueue_run+0x91=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`intr_e= vent_execute_handlers+0x66=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = kernel`ithread_loop+0x8e=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ke= rnel`fork_exit+0x112=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel= `0xffffffff8050624e=C2=A0Can someone help me debug this problem? It's likel= y that the mfi(4) driver I currently have access to doesn't have all the ne= cessary patches. Thank you. Regards, Pallav From owner-freebsd-questions@freebsd.org Fri Sep 25 22:32:28 2015 Return-Path: Delivered-To: freebsd-questions@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 96A0CA0898D for ; Fri, 25 Sep 2015 22:32:28 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 7173018E8 for ; Fri, 25 Sep 2015 22:32:28 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id 3D6AF3F727 for ; Fri, 25 Sep 2015 18:32:21 -0400 (EDT) Message-ID: <5605CB74.2020908@sneakertech.com> Date: Fri, 25 Sep 2015 18:32:20 -0400 From: Quartz MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: ZFS ready drives WAS: zfs performance degradation References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> In-Reply-To: <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 22:32:28 -0000 > once you take > the 5 year warranty in account. This assumes that the company in question will honorably honor the warranty. It's been our experience that they usually don't. I can't count you the number of times a drive manufacturer has pulled a fast one on a warranty replacement. WD is especially bad about this, they send back a cheaper drive than the original, a bottom-bin refurbished drive with twice the runtime/wear as the original that dies after a month (which mysteriously doesn't qualify for a warranty itself), or randomly insists we have to do a pay-and-reimburse replacement method then loses the records and never reimburses us. I understand that this is all anecdotal, but personally I don't find warranties worth the paper they're written on and never assume getting a functional replacement anymore. Long term it's cheaper to just buy a new drive outright than to waste employee time arguing over the phone for days. I buy exclusively based on ratings and reliability reports now. From owner-freebsd-questions@freebsd.org Fri Sep 25 22:35:06 2015 Return-Path: Delivered-To: freebsd-questions@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 16218A08B31 for ; Fri, 25 Sep 2015 22:35:06 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 E596719F3 for ; Fri, 25 Sep 2015 22:35:05 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id 130273F727 for ; Fri, 25 Sep 2015 18:35:05 -0400 (EDT) Message-ID: <5605CC18.8080607@sneakertech.com> Date: Fri, 25 Sep 2015 18:35:04 -0400 From: Quartz MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: ZFS ready drives WAS: zfs performance degradation References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> <56055878.3020700@hiwaay.net> In-Reply-To: <56055878.3020700@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 22:35:06 -0000 >I got convinced several > years ago that the 2.5" drives were better built This can be true under some cases. Laptop drives are more likely to be knocked around, so sometimes manufacturers will actually build them better to handle it. (Sometimes). From owner-freebsd-questions@freebsd.org Fri Sep 25 23:15:48 2015 Return-Path: Delivered-To: freebsd-questions@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 E4EB5A087E6 for ; Fri, 25 Sep 2015 23:15:47 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) Received: from nm39-vm6.bullet.mail.gq1.yahoo.com (nm39-vm6.bullet.mail.gq1.yahoo.com [98.136.217.109]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B66E11584 for ; Fri, 25 Sep 2015 23:15:47 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1443222826; bh=l2VkkmfHWbj3WjgbGgiVyE8JVYVlS8lEpfSWjetKtvI=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=DsLxZjU9X+WIwcY5mf6rEKta+TqRdVBkFZmHBUUIjckhf8pW99cKgziTX48WOHU0tndv4nUm67v7FgVW3eCp+NUP+WRKJ9Owo1THCNmN5CdVGfeyESmYxFyjYngSaVlL6SIGSTQX/u+D/onz0GCNCssyJVVwBP0695oGB9SZeg8MzP/EyxnEww3Rc+L3nN0fHUyP8d+5Vf94mYFpZNIOFb1zTH9vbKaQEeAgXfxeNXH2VKxxLXivJ6vWeGlfqYXvD4736EshcfqxjFQ7chkGzhfFdQzqBgMWpEScdvpAMuO61G4eeCRZ1pZdyK8y08T1OEATNwgJa8adg5kVJ19bgQ== Received: from [127.0.0.1] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 23:13:46 -0000 Received: from [98.137.12.188] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 23:10:59 -0000 Received: from [98.137.12.207] by tm9.bullet.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 23:10:58 -0000 Received: from [127.0.0.1] by omp1015.mail.gq1.yahoo.com with NNFMP; 25 Sep 2015 23:10:58 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 976681.97086.bm@omp1015.mail.gq1.yahoo.com X-YMail-OSG: QakQrycVM1lZylhY8mr2_xztTN2MTl25F1H4iOXDUv_0C0NohQHr3lquD_zTd57 IMcenU0_WIhpINCKu2JDSZjuDv9GL2DW6TXPh.FZeLL5cAvK6o4C4uaVvXvS.YT0oaBetg4jzQ26 EYy3crpjIm9_muAW4Zvl_raROV_YOwMrgioQf4ik8Th.HUxwaDA6O0iztE6L4SDEIsAMjyeX4PdY TFoVRO0SoB7InJjrShN_Tp0rF1G6FbzDS8AT_SjIrtL3Jqmp.jHyufCoRa65lIdhSRFP0fjfR43L vTf4pjYAxq69Cv906eXn0VkkOi9SVcE9w4ksZP2Br.6Zoc_mBN9bTaTuwm6fU6YQE4n1.3xi.omY XjxHOPE720xTSCaysTrAjoAdYqc0prnIvBhQaMK7Xzl8ZrszYUoR1Y87.WYvHmei_r3EYjVY6kRg pmJeV6MKRJPNSdpYpvwE12RLcsG5Ylm1I33AWiawQGjAZsQcjAoM3ndau6p2jsd6_Q84d6FrwjWa wVLOatxBV9YZfzQAzevfWTew- Received: by 216.39.60.193; Fri, 25 Sep 2015 23:10:58 +0000 Date: Fri, 25 Sep 2015 23:10:58 +0000 (UTC) From: Pallav Bose Reply-To: Pallav Bose To: "freebsd-questions@freebsd.org" Message-ID: <488290978.924887.1443222658131.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <472489221.917644.1443216922050.JavaMail.yahoo@mail.yahoo.com> References: <472489221.917644.1443216922050.JavaMail.yahoo@mail.yahoo.com> Subject: Re: Interrupt storm and poor disk performance | mfi(4) driver | FreeBSD 8 | Dell PERC H730 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 23:15:48 -0000 To add to my earlier email, the mfi(4) driver in my source tree was last sy= nced with FreeBSD 8 stable tree up to https://svnweb.freebsd.org/base?view= =3Drevision&revision=3D250497 I integrated these three patches to get the mfi(4) driver to attach to the = the H730 controller:https://svnweb.freebsd.org/base?view=3Drevision&revisio= n=3D252471 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D256924 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D261535 I can undo my patch work, but then how I should I proceed from here to reso= lve the interrupt storm problem? Thanks,Pallav On Friday, September 25, 2015 2:35 PM, Pallav Bose wrote: =20 Hello, I have a Dell PowerEdge R430 server with a PERC H730 RAID controller. I'm t= rying to get FreeBSD 8 to install and run on this server. At this time, I h= ave a patched version of the mfi(4) driver which attaches to the controller= . I'm aware of mrsas(4), but since I have scripts that use mfiutil(8), I'd = like to continue using the mfi(4) driver. A simple dd test shows SSD performance to be very poor: # dd if=3D/dev/mfid0 of=3D/dev/null bs=3D1m count=3D10241024+0 records in10= 24+0 records out1073741824 bytes transferred in 27.978784 secs (38377001 by= tes/sec) top -PHS shows a lot of CPU time being used by the swi6 s/w interrupt handl= er: last pid: 81270; =C2=A0load averages: =C2=A00.01, =C2=A00.05, =C2=A00.05 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 up 0+05:34:20 =C2=A015:45:51302 processes: 7 runni= ng, 278 sleeping, 17 waitingCPU 0: =C2=A00.0% user, =C2=A00.0% nice, =C2=A0= 0.0% system, 52.6% interrupt, 47.4% idleCPU 1: =C2=A00.0% user, =C2=A00.0% = nice, =C2=A00.0% system, =C2=A00.0% interrupt, =C2=A0100% idleCPU 2: =C2=A0= 0.0% user, =C2=A00.0% nice, =C2=A00.0% system, =C2=A00.0% interrupt, =C2=A0= 100% idleCPU 3: =C2=A00.0% user, =C2=A00.0% nice, =C2=A00.0% system, =C2=A0= 0.0% interrupt, =C2=A0100% idleCPU 4: =C2=A00.0% user, =C2=A00.0% nice, =C2= =A00.0% system, =C2=A00.0% interrupt, =C2=A0100% idleCPU 5: =C2=A00.0% user= , =C2=A00.0% nice, =C2=A00.0% system, =C2=A00.7% interrupt, 99.3% idleMem: = 48M Active, 4044K Inact, 997M Wired, 7144K Cache, 1248K Buf, 30G FreeSwap: =C2=A0 PID USERNAME =C2=A0 =C2=A0PRI NICE =C2=A0 SIZE =C2=A0 =C2=A0RES STAT= E =C2=A0 C =C2=A0 TIME =C2=A0 WCPU COMMAND=C2=A0 =C2=A010 root =C2=A0 =C2= =A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU5 =C2=A0 =C2=A05 = 319:51 100.00% {idle: cpu5}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0= 171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU2 =C2=A0 =C2=A02 293:32 94.58% {id= le: cpu2}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 = =C2=A0 0K =C2=A0 192K CPU3 =C2=A0 =C2=A03 298:46 93.65% {idle: cpu3}=C2=A0 = =C2=A010 root =C2=A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 1= 92K CPU4 =C2=A0 =C2=A04 278:55 92.58% {idle: cpu4}=C2=A0 =C2=A010 root =C2= =A0 =C2=A0 =C2=A0 =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K CPU1 =C2=A0 = =C2=A01 289:36 92.19% {idle: cpu1}=C2=A0 =C2=A010 root =C2=A0 =C2=A0 =C2=A0= =C2=A0171 ki31 =C2=A0 =C2=A0 0K =C2=A0 192K RUN =C2=A0 =C2=A0 0 293:17 85.= 99% {idle: cpu0}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-24 =C2=A0 = =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A02 173:40 47.27% {swi= 6: task queue}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-64 =C2=A0 = =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A05 =C2=A011:50 =C2=A0= 0.00% {irq256: mfi0}=C2=A0 =C2=A011 root =C2=A0 =C2=A0 =C2=A0 =C2=A0-32 =C2= =A0 =C2=A0- =C2=A0 =C2=A0 0K =C2=A0 544K WAIT =C2=A0 =C2=A01 =C2=A0 6:26 = =C2=A00.00% {swi4: clock} The interrupt rate in case of irq256:mfi0 is very high, in spite of there b= eing no disk activity.=20 # vmstat -iinterrupt =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0total =C2=A0 =C2=A0 =C2=A0 rateirq4: = uart0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0257 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00irq9: acpi0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A01 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00irq18: ehci0 ehci1= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 71739 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A03cpu0: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40226355 =C2=A0 =C2=A0 =C2=A0 1998irq256: m= fi0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3= 642472 =C2=A0 =C2=A0 =C2=A0 =C2=A0180irq257: bge0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 34922 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A01cpu3: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 40229128 =C2=A0 =C2=A0 =C2=A0 1998cpu5: timer = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40228= 959 =C2=A0 =C2=A0 =C2=A0 1998cpu4: timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40229014 =C2=A0 =C2=A0 =C2=A0 1998cpu1:= timer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 40228629 =C2=A0 =C2=A0 =C2=A0 1998cpu2: timer =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40223967 =C2=A0 =C2=A0 =C2=A0= 1998Total =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0245115443 =C2=A0 =C2=A0 =C2=A012175 Procstat output: # procstat -kk 11 =C2=A0 =C2=A0 =C2=A0 # PID 11 taken from output of top=C2= =A0 PID =C2=A0 =C2=A0TID COMM =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TDN= AME =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 KSTACK=C2=A0 =C2=A011 100008 intr = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi3: vm=C2=A0 =C2=A011 100009 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi1: netisr 0 =C2=A0 mi_switc= h+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A0= 11 100010 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0= =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_tramp= oline+0xe=C2=A0 =C2=A011 100011 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork= _exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100012 intr =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205= ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 1000= 13 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0= =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0= xe=C2=A0 =C2=A011 100014 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi= 4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork_exit+0= x112 fork_trampoline+0xe=C2=A0 =C2=A011 100015 intr =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 swi4: clock =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithrea= d_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100021 intr= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi5: +=C2=A0 =C2=A011 100023 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi6: Giant task mi_switch+0x2= 05 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 10= 0024 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi6: task queue mi_swi= tch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2= =A011 100027 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi2: cambio = =C2=A0 =C2=A0 mi_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_tramp= oline+0xe=C2=A0 =C2=A011 100032 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 irq9: acpi0 =C2=A0 =C2=A0 =C2=A0mi_switch+0x205 ithread_loop+0x1bf fork= _exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100033 intr =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq256: mfi0 =C2=A0 =C2=A0 mi_switch+0x205 ithr= ead_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 100034 in= tr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq18: ehci0 ehc mi_switch+0x2= 05 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0 =C2=A011 10= 0039 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 swi0: uart uart =C2=A0m= i_switch+0x205 ithread_loop+0x1bf fork_exit+0x112 fork_trampoline+0xe=C2=A0= =C2=A011 100040 intr =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq1: atkbd= 0 # kldload dtraceall# dtrace -n 'profile:::profile-276hz { @pc[stack()]=3Dco= unt(); }'dtrace: description 'profile:::profile-276hz ' matched 1 probe The above dtrace script is supposed to=C2=A0print all the stack traces seen= during the sampling period. The following stack trace occurs a large number of times: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`DELAY+0x64 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`bus_dmamap_load+0x3= a9=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_mapcmd+0x4f= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_startio+0x65=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_wait_command+0x9c= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_tbolt_sync_map_= info+0xb4=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`mfi_handl= e_map_sync+ 0x39=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`tas= kqueue_run+0x91=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 kernel`intr= _event_execute_ handlers+0x66=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 kernel`ithread_loop+0x8e=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 kernel`fork_exit+0x112=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = kernel`0xffffffff8050624e=C2=A0Can someone help me debug this problem? It's= likely that the mfi(4) driver I currently have access to doesn't have all = the necessary patches. Thank you. Regards, Pallav From owner-freebsd-questions@freebsd.org Sat Sep 26 04:06:09 2015 Return-Path: Delivered-To: freebsd-questions@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 1B4B0A09C33 for ; Sat, 26 Sep 2015 04:06:09 +0000 (UTC) (envelope-from info@pk1048.com) Received: from cpanel61.fastdnsservers.com (server61.fastdnsservers.com [216.51.232.61]) (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 E97A814AD for ; Sat, 26 Sep 2015 04:06:08 +0000 (UTC) (envelope-from info@pk1048.com) Received: from pool-100-4-179-8.albyny.fios.verizon.net ([100.4.179.8]:54580 helo=[192.168.2.133]) by cpanel61.fastdnsservers.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1ZfgVc-002GFa-Ms; Fri, 25 Sep 2015 22:50:48 -0500 References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> <5605CB74.2020908@sneakertech.com> In-Reply-To: <5605CB74.2020908@sneakertech.com> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: Cc: "freebsd-questions@freebsd.org" X-Mailer: iPad Mail (12H143) From: PK1048 Subject: Re: ZFS ready drives WAS: zfs performance degradation Date: Fri, 25 Sep 2015 23:50:44 -0400 To: Quartz X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel61.fastdnsservers.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - pk1048.com X-Get-Message-Sender-Via: cpanel61.fastdnsservers.com: authenticated_id: info@pk1048.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 04:06:09 -0000 Are you buying OEM drives ? I have had no issues with either Seagate or HGST= in terms of warranty work, but I _never_ but an OEM drive, I know those inc= lude no warranty. I have yet to need to warranty a WD drive, so don't know that they're like. Sent from my portable device On Sep 25, 2015, at 18:32, Quartz wrote: >> once you take >> the 5 year warranty in account. >=20 > This assumes that the company in question will honorably honor the warrant= y. It's been our experience that they usually don't. I can't count you the n= umber of times a drive manufacturer has pulled a fast one on a warranty repl= acement. WD is especially bad about this, they send back a cheaper drive tha= n the original, a bottom-bin refurbished drive with twice the runtime/wear a= s the original that dies after a month (which mysteriously doesn't qualify f= or a warranty itself), or randomly insists we have to do a pay-and-reimburse= replacement method then loses the records and never reimburses us. >=20 > I understand that this is all anecdotal, but personally I don't find warra= nties worth the paper they're written on and never assume getting a function= al replacement anymore. Long term it's cheaper to just buy a new drive outri= ght than to waste employee time arguing over the phone for days. I buy exclu= sively based on ratings and reliability reports now. >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g" From owner-freebsd-questions@freebsd.org Sat Sep 26 11:09:09 2015 Return-Path: Delivered-To: freebsd-questions@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 291489B8998 for ; Sat, 26 Sep 2015 11:09:09 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.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 DFE6BB84 for ; Sat, 26 Sep 2015 11:09:08 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.169.211] (helo=fabiankeil.de) by smtprelay05.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1ZfnHW-00066m-QR for freebsd-questions@freebsd.org; Sat, 26 Sep 2015 13:04:42 +0200 Date: Sat, 26 Sep 2015 13:04:41 +0200 From: Fabian Keil Cc: freebsd-questions@freebsd.org Subject: Re: Problems with ZFS file servers Message-ID: <4abb7c52.5adf5378@fabiankeil.de> In-Reply-To: <20150925232658.GB42532@neutralgood.org> References: <55F5CF06.5080602@rpi.edu> <1442191342.426007007.amnhjwng@frv35.fwdcdn.com> <55F62523.7010402@rpi.edu> <1442267713.360040098.um8wwy4s@frv35.fwdcdn.com> <5605A3A5.7080905@rpi.edu> <5605AD8D.4080706@FreeBSD.org> <20150925232658.GB42532@neutralgood.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/DdhJIUE69CrDTbt_a6pUFSv"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 11:09:09 -0000 --Sig_/DdhJIUE69CrDTbt_a6pUFSv Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable kpneal@pobox.com wrote: > On Fri, Sep 25, 2015 at 09:24:45PM +0100, Matthew Seaman wrote: > > On 25/09/2015 20:42, Bob Healey wrote: > > > I've got another machine acting up, this machine is a Sun X2250, > > > originally was running Solaris until this summer when the owner dropp= ed > > > the support contract. A zpool export, reinstall to FreeBSD 10.1, and > > > zpool import and it was back in business. Most of the requested info > > > can be found at http://origami.phys.rpi.edu/~healer/lepton. I am > > > working on getting cacti installed. I am currently trying to rsync a > > > workstation to this pool so I can reload the OS. If I use > > > --bwlimit=3D10240 or lower, I have no issues, but if I don't rsync fr= eezes > > > on me on the client side. > >=20 > > I've found, through bitter experience, that you need to apply some > > tunings to ZFS machines, and quite possibly some kernel patches too. > > When you're pumping wads of data into a ZFS machine at high speed, it is > > all too easy to get it to lock up. > >=20 > > First up, the default setting where ZFS grabs all but 1GB of available > > RAM for use by the ARC is nuts. You need to chop that down and give the > > rest of the OS a fair share of RAM to play with by setting > > vfs.zfs.arc_max in /boot/loader.conf. What you set it to depends on the > > application mix on your server, but somewhere around 50% of available > > RAM seems reasonable to me. Reboot to enable that, obviously. >=20 > My personal experience: >=20 > I have swap space configured. My box has 8GB of memory, and when I save > large mailboxes with mutt I see up to 4GB of swap space used.=20 >=20 > It may be the case that adding swap space will eliminate the need to > limit the ARC manually in /boot/loader.conf.=20 Without the ARC patches or manual tuning the swap use could be the result of the ARC failing to adapt to the memory pressure in which case even active processes may start paging that otherwise wouldn't have to. In that situation, adding more swap space may degrade performance even further as it allows the ARC to hold on to the memory even longer. Thus I wouldn't recommend it without analysing the cause of the swap use first. Fabian --Sig_/DdhJIUE69CrDTbt_a6pUFSv Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYGe8MACgkQBYqIVf93VJ00rgCeLRFI57rWupcb8cuFkBKFeQmc QKIAnj8VkLFb+5D2/XR5l+g5lglMbMU+ =BG6V -----END PGP SIGNATURE----- --Sig_/DdhJIUE69CrDTbt_a6pUFSv-- From owner-freebsd-questions@freebsd.org Sat Sep 26 11:42:09 2015 Return-Path: Delivered-To: freebsd-questions@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 E9A80A096D6 for ; Sat, 26 Sep 2015 11:42:09 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AA7B21349 for ; Sat, 26 Sep 2015 11:42:09 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t8QBg7Ri083829 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 26 Sep 2015 05:42:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t8QBg6d3083826; Sat, 26 Sep 2015 05:42:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 26 Sep 2015 05:42:06 -0600 (MDT) From: Warren Block To: Quartz cc: freebsd-questions@freebsd.org Subject: Re: 10.2 graphics problem In-Reply-To: <560486ED.3030005@sneakertech.com> Message-ID: References: <8F541F88-2EAE-434C-B52C-43A744F54ADD@slsware.net> <1F197AA4-CE10-4195-B0D5-028C30036CAA@slsware.net> <5552406.tZCDeim3VM@amd.asgard.uk> <560486ED.3030005@sneakertech.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 26 Sep 2015 05:42:07 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 11:42:10 -0000 On Thu, 24 Sep 2015, Quartz wrote: >> Thanks for creating that. The PXE page was especially interesting. > > As an aside, his notes on syslinux v4 are out of date. In recent versions > things have been rearchitected and broken out into a dozen support files with > a different directory layout. (Just FYI in case you try to follow the > instructions literally). Yes, it's a perennial problem with technical docs. Some time I need to update that. Preferably to include UEFI PXE-boot, too. From owner-freebsd-questions@freebsd.org Sat Sep 26 14:00:34 2015 Return-Path: Delivered-To: freebsd-questions@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 DBE78A089DB for ; Sat, 26 Sep 2015 14:00:34 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF571DD9 for ; Sat, 26 Sep 2015 14:00:34 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8QE0VLw028530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 26 Sep 2015 09:00:32 -0500 To: FreeBSD Questions !!!! From: "William A. Mahaffey III" Subject: dd question Message-ID: <5606A4FF.4090105@hiwaay.net> Date: Sat, 26 Sep 2015 09:06:01 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 14:00:35 -0000 I am preparing a USB stick for use to install FreeBSD 9.3R on 2 new boxen I am bringing online. I already had the FreeBSD 9.3R img dd'ed to that stick last year when I provisioned this box, but for some reason, when I plugged the stick into my USB port today to copy some additional files to it (scripts to be used during installs to partition & slice up HDD's), I got errors in my syslog file & couldn't mount the drive for the copies. No problema, I'll just re-dd the image to the device & start over, all I would lose is output from the previous install (this box, last year this time). However, I notice the dd is proceeding *VERY* slowly: [root@kabini1, /etc, 8:47:59am] 508 % ll /dev/da0* crw-r----- 1 root operator 0xd2 Sep 26 08:29 /dev/da0 crw-r----- 1 root operator 0xcd Sep 26 08:29 /dev/da0a [root@kabini1, /etc, 8:48:09am] 509 % ll /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/ total 1530556 -rw-r--r-- 1 wam users 178749440 Jul 26 2014 FreeBSD-9.3-RELEASE-amd64-bootonly.iso -rw-r--r-- 1 wam users 671152128 Jul 26 2014 FreeBSD-9.3-RELEASE-amd64-disc1.iso -rw-r--r-- 1 wam users 717373440 Jul 26 2014 FreeBSD-9.3-RELEASE-amd64-memstick.img -rw------- 1 wam users 811 Jul 26 2014 checksum.MD5.txt [root@kabini1, /etc, 8:48:19am] 510 % dd if=/net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img of=/dev/da0 94834+0 records in 94834+0 records out 48555008 bytes transferred in 542.035379 secs (89579 bytes/sec) 101599+0 records in 101599+0 records out 52018688 bytes transferred in 580.466607 secs (89615 bytes/sec) I got that output by sending the SIGINFO signal to the dd process from another shell window. My question is: Why so slow (89-ish KB/s) ? I have gigabit switched LAN (125 MB/s theoretical speed), & most other file copies or rsyncs across the LAN go at about 1/3 - 1/2 of theoretical speeds, which is AOK by me. Any ideas ? TIA & have a nice weekend. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Sat Sep 26 14:00:46 2015 Return-Path: Delivered-To: freebsd-questions@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 E7EF0A089FD for ; Sat, 26 Sep 2015 14:00:46 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.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 C16DDE66 for ; Sat, 26 Sep 2015 14:00:46 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id E83AF3F74B for ; Sat, 26 Sep 2015 10:00:44 -0400 (EDT) Message-ID: <5606A50C.2090009@sneakertech.com> Date: Sat, 26 Sep 2015 10:00:44 -0400 From: Quartz MIME-Version: 1.0 To: "freebsd-questions@freebsd.org" Subject: Re: ZFS ready drives WAS: zfs performance degradation References: <56019211.2050307@dim.lv> <37A37E9D-9D65-4553-BBA2-C5B032163499@kraus-haus.org> <56038054.5060906@dim.lv> <782C9CEF-BE07-4E05-83ED-133B7DA96780@kraus-haus.org> <56040150.90403@dim.lv> <60BF2FC3-0342-46C9-A718-52492303522F@kraus-haus.org> <560412B2.9070905@dim.lv> <8D1FF55C-7068-4AB6-8C0E-B4E64C1BB5FA@kraus-haus.org> <56042209.8040903@dim.lv> <2008181C-F0B5-4581-9D15-11911A1DE41B@kraus-haus.org> <6498A090-A2A2-4580-A148-2BCBF68BF2BF@kraus-haus.org> <5605481D.10902@physics.umn.edu> <106217D9-F3DB-4DB5-822E-098041B5BC6F@kraus-haus.org> <5605CB74.2020908@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 14:00:47 -0000 > Are you buying OEM drives Nope, only normal official fully labeled drives here. > I have yet to need to warranty a WD drive, so don't know that they're > like. To be fair, I haven't had to rma drives particularly often, but whenever I do it's always a huge hassle. From owner-freebsd-questions@freebsd.org Sat Sep 26 14:11:51 2015 Return-Path: Delivered-To: freebsd-questions@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 CE857A092C9 for ; Sat, 26 Sep 2015 14:11:51 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F990AA2 for ; Sat, 26 Sep 2015 14:11:51 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8QEBneK004840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 26 Sep 2015 09:11:50 -0500 Subject: Re: dd question To: FreeBSD Questions !!!! References: <5606A4FF.4090105@hiwaay.net> From: "William A. Mahaffey III" Message-ID: <5606A7A4.5000301@hiwaay.net> Date: Sat, 26 Sep 2015 09:17:18 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <5606A4FF.4090105@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 14:11:52 -0000 On 09/26/15 09:05, William A. Mahaffey III wrote: > > > I am preparing a USB stick for use to install FreeBSD 9.3R on 2 new > boxen I am bringing online. I already had the FreeBSD 9.3R img dd'ed > to that stick last year when I provisioned this box, but for some > reason, when I plugged the stick into my USB port today to copy some > additional files to it (scripts to be used during installs to > partition & slice up HDD's), I got errors in my syslog file & couldn't > mount the drive for the copies. No problema, I'll just re-dd the image > to the device & start over, all I would lose is output from the > previous install (this box, last year this time). However, I notice > the dd is proceeding *VERY* slowly: > > > [root@kabini1, /etc, 8:47:59am] 508 % ll /dev/da0* > crw-r----- 1 root operator 0xd2 Sep 26 08:29 /dev/da0 > crw-r----- 1 root operator 0xcd Sep 26 08:29 /dev/da0a > [root@kabini1, /etc, 8:48:09am] 509 % ll > /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/ > total 1530556 > -rw-r--r-- 1 wam users 178749440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-bootonly.iso > -rw-r--r-- 1 wam users 671152128 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-disc1.iso > -rw-r--r-- 1 wam users 717373440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-memstick.img > -rw------- 1 wam users 811 Jul 26 2014 checksum.MD5.txt > [root@kabini1, /etc, 8:48:19am] 510 % dd > if=/net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img > of=/dev/da0 > 94834+0 records in > 94834+0 records out > 48555008 bytes transferred in 542.035379 secs (89579 bytes/sec) > 101599+0 records in > 101599+0 records out > 52018688 bytes transferred in 580.466607 secs (89615 bytes/sec) > > I got that output by sending the SIGINFO signal to the dd process from > another shell window. My question is: Why so slow (89-ish KB/s) ? I > have gigabit switched LAN (125 MB/s theoretical speed), & most other > file copies or rsyncs across the LAN go at about 1/3 - 1/2 of > theoretical speeds, which is AOK by me. Any ideas ? TIA & have a nice > weekend. Update: I got tired of waiting & just copied the img files over from the other box to do the dd in case the interaction of dd & NFS were a problem: [root@kabini1, /etc, 9:12:23am] 511 % cp /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img . [root@kabini1, /etc, 9:12:39am] 512 % dd if=FreeBSD-9.3-RELEASE-amd64-memstick.img of=/dev/da0 3049+0 records in 3049+0 records out 1561088 bytes transferred in 17.511796 secs (89145 bytes/sec) ^C9584+0 records in 9583+0 records out 4906496 bytes transferred in 54.403733 secs (90187 bytes/sec) [root@kabini1, /etc, 9:13:51am] 513 % [root@kabini1, /etc, 9:13:51am] 513 % [root@kabini1, /etc, 9:13:52am] 513 % [root@kabini1, /etc, 9:13:52am] 513 % uname -a FreeBSD kabini1.local 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 01:54:44 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [root@kabini1, /etc, 9:13:55am] 514 % Note that the cp happened pretty quick, 717-ish MiB in about 15 sec., or around 45-ish MB/s, about 1/3 of max, quite acceptable to me. Obviously, the dd is still excruciatingly slow .... What gives ? TIA & have a nice weekend .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Sat Sep 26 15:19:02 2015 Return-Path: Delivered-To: freebsd-questions@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 18A71A08FB4 for ; Sat, 26 Sep 2015 15:19:02 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A88F8DA1 for ; Sat, 26 Sep 2015 15:19:01 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by wicge5 with SMTP id ge5so54461540wic.0 for ; Sat, 26 Sep 2015 08:19:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AdFqxCC8kEtKC7nwGIwt6PNruAHAmdAdgmqNgTGI9CQ=; b=E9jOS2aViJbmr+erkQU6Jjq1D0In7IerwmhZWWWjVdoiOXN48P5UN/gp8EUxm4PRJ8 Wy3Khj9heceNdn3kRuBgcv5kkgD3gHn/SMy8KaHlP4IPXrlFeEX0krVFKsAOMvDcs1MY UrQ5HH1Mcw0O9Wsn7ZrOOwBr4RmgTRDMmIowjDafyE/NltW4lWhGgKosMQEDgHdpFJRm iayaeEfgvs1fbVS+zW9Zdkb+9ruQQgmNcUNKv+inrwaeSJyg5xCwogIj4GC2OugeTCkb UtJyQcc5/m3IIswAMnKE1nPcHtodV5J3vp3hIE6tXz8xCIFma+CgpetJJXBLA5mUj2tT SWaA== MIME-Version: 1.0 X-Received: by 10.180.107.130 with SMTP id hc2mr8489130wib.92.1443280739908; Sat, 26 Sep 2015 08:18:59 -0700 (PDT) Received: by 10.194.16.231 with HTTP; Sat, 26 Sep 2015 08:18:59 -0700 (PDT) In-Reply-To: <5606A4FF.4090105@hiwaay.net> References: <5606A4FF.4090105@hiwaay.net> Date: Sat, 26 Sep 2015 10:18:59 -0500 Message-ID: Subject: Re: dd question From: Adam Vande More To: "William A. Mahaffey III" Cc: "FreeBSD Questions !!!!" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 15:19:02 -0000 On Sat, Sep 26, 2015 at 8:59 AM, William A. Mahaffey III wrote: > > > I am preparing a USB stick for use to install FreeBSD 9.3R on 2 new boxen > I am bringing online. I already had the FreeBSD 9.3R img dd'ed to that > stick last year when I provisioned this box, but for some reason, when I > plugged the stick into my USB port today to copy some additional files to > it (scripts to be used during installs to partition & slice up HDD's), I > got errors in my syslog file & couldn't mount the drive for the copies. No > problema, I'll just re-dd the image to the device & start over, all I would > lose is output from the previous install (this box, last year this time). > However, I notice the dd is proceeding *VERY* slowly: > > > [root@kabini1, /etc, 8:47:59am] 508 % ll /dev/da0* > crw-r----- 1 root operator 0xd2 Sep 26 08:29 /dev/da0 > crw-r----- 1 root operator 0xcd Sep 26 08:29 /dev/da0a > [root@kabini1, /etc, 8:48:09am] 509 % ll > /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/ > total 1530556 > -rw-r--r-- 1 wam users 178749440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-bootonly.iso > -rw-r--r-- 1 wam users 671152128 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-disc1.iso > -rw-r--r-- 1 wam users 717373440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-memstick.img > -rw------- 1 wam users 811 Jul 26 2014 checksum.MD5.txt > [root@kabini1, /etc, 8:48:19am] 510 % dd > if=/net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img > of=/dev/da0 > 94834+0 records in > 94834+0 records out > 48555008 bytes transferred in 542.035379 secs (89579 bytes/sec) > 101599+0 records in > 101599+0 records out > 52018688 bytes transferred in 580.466607 secs (89615 bytes/sec) > > I got that output by sending the SIGINFO signal to the dd process from > another shell window. > Hitting Ctrl-T in the dd terminal is a lot easier. > My question is: Why so slow (89-ish KB/s) ? > Well first off I'd tell dd to use a bigger bs like 1m. -- Adam From owner-freebsd-questions@freebsd.org Sat Sep 26 15:24:48 2015 Return-Path: Delivered-To: freebsd-questions@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 56395A093F3 for ; Sat, 26 Sep 2015 15:24:48 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 3216B2D7 for ; Sat, 26 Sep 2015 15:24:48 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id 95A1133C46; Sat, 26 Sep 2015 11:24:35 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id AAA9C39819; Sat, 26 Sep 2015 11:24:32 -0400 (EDT) From: Lowell Gilbert To: Pallav Bose via freebsd-questions Cc: Pallav Bose Subject: Re: Interrupt storm and poor disk performance | mfi(4) driver | FreeBSD 8 | Dell PERC H730 References: <472489221.917644.1443216922050.JavaMail.yahoo@mail.yahoo.com> Date: Sat, 26 Sep 2015 11:24:32 -0400 In-Reply-To: <472489221.917644.1443216922050.JavaMail.yahoo@mail.yahoo.com> (Pallav Bose via freebsd-questions's message of "Fri, 25 Sep 2015 21:35:22 +0000 (UTC)") Message-ID: <44lhbtyzin.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 15:24:48 -0000 Pallav Bose via freebsd-questions writes: > I have a Dell PowerEdge R430 server with a PERC H730 RAID > controller. I'm trying to get FreeBSD 8 to install and run on this > server. At this time, I have a patched version of the mfi(4) driver > which attaches to the controller. I'm aware of mrsas(4), but since I > have scripts that use mfiutil(8), I'd like to continue using the > mfi(4) driver. I don't see an obvious issue. To be honest, I am not willing to spend much time figuring out problems with an out-of-support release. I am sure that other people act similarly. From owner-freebsd-questions@freebsd.org Sat Sep 26 15:51:48 2015 Return-Path: Delivered-To: freebsd-questions@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 6CB80A0A943 for ; Sat, 26 Sep 2015 15:51:48 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AFB32AD for ; Sat, 26 Sep 2015 15:51:47 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8QFoAV6031957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 26 Sep 2015 10:50:11 -0500 Subject: Re: dd question References: <5606A4FF.4090105@hiwaay.net> Cc: FreeBSD Questions !!!! From: "William A. Mahaffey III" Message-ID: <5606BEB2.3020803@hiwaay.net> Date: Sat, 26 Sep 2015 10:55:40 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 15:51:48 -0000 On 09/26/15 10:25, Adam Vande More wrote: > > > On Sat, Sep 26, 2015 at 8:59 AM, William A. Mahaffey III > > wrote: > > > > I am preparing a USB stick for use to install FreeBSD 9.3R on 2 > new boxen I am bringing online. I already had the FreeBSD 9.3R img > dd'ed to that stick last year when I provisioned this box, but for > some reason, when I plugged the stick into my USB port today to > copy some additional files to it (scripts to be used during > installs to partition & slice up HDD's), I got errors in my syslog > file & couldn't mount the drive for the copies. No problema, I'll > just re-dd the image to the device & start over, all I would lose > is output from the previous install (this box, last year this > time). However, I notice the dd is proceeding *VERY* slowly: > > > [root@kabini1, /etc, 8:47:59am] 508 % ll /dev/da0* > crw-r----- 1 root operator 0xd2 Sep 26 08:29 /dev/da0 > crw-r----- 1 root operator 0xcd Sep 26 08:29 /dev/da0a > [root@kabini1, /etc, 8:48:09am] 509 % ll > /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/ > total 1530556 > -rw-r--r-- 1 wam users 178749440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-bootonly.iso > -rw-r--r-- 1 wam users 671152128 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-disc1.iso > -rw-r--r-- 1 wam users 717373440 Jul 26 2014 > FreeBSD-9.3-RELEASE-amd64-memstick.img > -rw------- 1 wam users 811 Jul 26 2014 checksum.MD5.txt > [root@kabini1, /etc, 8:48:19am] 510 % dd > if=/net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img > of=/dev/da0 > 94834+0 records in > 94834+0 records out > 48555008 bytes transferred in 542.035379 secs (89579 bytes/sec) > 101599+0 records in > 101599+0 records out > 52018688 bytes transferred in 580.466607 secs (89615 bytes/sec) > > I got that output by sending the SIGINFO signal to the dd process > from another shell window. > > > Hitting Ctrl-T in the dd terminal is a lot easier. > > My question is: Why so slow (89-ish KB/s) ? > > > Well first off I'd tell dd to use a bigger bs like 1m. > > > -- > Adam Very well, I may try that experimentally. Meanwhile I got tired of waiting (again) & moved the USB drive to my last remaining Linux box & did the dd there: [root@Q6600:/etc, Sat Sep 26, 10:01 AM] 1018 # dd if=/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img of=/dev/sdg 342905+0 records in 342905+0 records out 175567360 bytes (176 MB) copied, 46.5117 s, 3.8 MB/s 440625+0 records in 440625+0 records out 225600000 bytes (226 MB) copied, 78.495 s, 2.9 MB/s 584961+0 records in 584961+0 records out 299500032 bytes (300 MB) copied, 112.507 s, 2.7 MB/s 938865+0 records in 938865+0 records out 480698880 bytes (481 MB) copied, 199.845 s, 2.4 MB/s 1401120+0 records in 1401120+0 records out 717373440 bytes (717 MB) copied, 348.004 s, 2.1 MB/s [root@Q6600:/etc, Sat Sep 26, 10:07 AM] 1019 # uname -a Linux Q6600 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux [root@Q6600:/etc, Sat Sep 26, 10:54 AM] 1020 # I will retry the dd later or on another spare drive to assess. This is a bit distressing if that doesn't go well, however, as I am going to reprovision the Linux box to either CentOS 6 (generation-wise similar to the FC 14 already there) or FreeBSD 9.3R, cutting ties w/ Linux altogether. However, I do occasionally need dd to work correctly, & if I am going to lose that moving away from Linux, that would be a significant factor in my decision making. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Sat Sep 26 16:05:13 2015 Return-Path: Delivered-To: freebsd-questions@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 C0F01A0AFAD for ; Sat, 26 Sep 2015 16:05:13 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F1DBC50 for ; Sat, 26 Sep 2015 16:05:13 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t8QG5Ae6008714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 26 Sep 2015 11:05:11 -0500 Subject: Re: dd question To: FreeBSD Questions !!!! References: <5606A4FF.4090105@hiwaay.net> <5606A7A4.5000301@hiwaay.net> From: "William A. Mahaffey III" Message-ID: <5606C236.5060703@hiwaay.net> Date: Sat, 26 Sep 2015 11:10:40 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <5606A7A4.5000301@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 16:05:13 -0000 On 09/26/15 09:16, William A. Mahaffey III wrote: > On 09/26/15 09:05, William A. Mahaffey III wrote: >> >> >> I am preparing a USB stick for use to install FreeBSD 9.3R on 2 new >> boxen I am bringing online. I already had the FreeBSD 9.3R img dd'ed >> to that stick last year when I provisioned this box, but for some >> reason, when I plugged the stick into my USB port today to copy some >> additional files to it (scripts to be used during installs to >> partition & slice up HDD's), I got errors in my syslog file & >> couldn't mount the drive for the copies. No problema, I'll just re-dd >> the image to the device & start over, all I would lose is output from >> the previous install (this box, last year this time). However, I >> notice the dd is proceeding *VERY* slowly: >> >> >> [root@kabini1, /etc, 8:47:59am] 508 % ll /dev/da0* >> crw-r----- 1 root operator 0xd2 Sep 26 08:29 /dev/da0 >> crw-r----- 1 root operator 0xcd Sep 26 08:29 /dev/da0a >> [root@kabini1, /etc, 8:48:09am] 509 % ll >> /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/ >> total 1530556 >> -rw-r--r-- 1 wam users 178749440 Jul 26 2014 >> FreeBSD-9.3-RELEASE-amd64-bootonly.iso >> -rw-r--r-- 1 wam users 671152128 Jul 26 2014 >> FreeBSD-9.3-RELEASE-amd64-disc1.iso >> -rw-r--r-- 1 wam users 717373440 Jul 26 2014 >> FreeBSD-9.3-RELEASE-amd64-memstick.img >> -rw------- 1 wam users 811 Jul 26 2014 checksum.MD5.txt >> [root@kabini1, /etc, 8:48:19am] 510 % dd >> if=/net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img >> of=/dev/da0 >> 94834+0 records in >> 94834+0 records out >> 48555008 bytes transferred in 542.035379 secs (89579 bytes/sec) >> 101599+0 records in >> 101599+0 records out >> 52018688 bytes transferred in 580.466607 secs (89615 bytes/sec) >> >> I got that output by sending the SIGINFO signal to the dd process >> from another shell window. My question is: Why so slow (89-ish KB/s) >> ? I have gigabit switched LAN (125 MB/s theoretical speed), & most >> other file copies or rsyncs across the LAN go at about 1/3 - 1/2 of >> theoretical speeds, which is AOK by me. Any ideas ? TIA & have a nice >> weekend. > > > Update: I got tired of waiting & just copied the img files over from > the other box to do the dd in case the interaction of dd & NFS were a > problem: > > [root@kabini1, /etc, 9:12:23am] 511 % cp > /net/q6600/home/ISOs/BSDs/FreeBSD/9.3/FreeBSD-9.3-RELEASE-amd64-memstick.img > . > [root@kabini1, /etc, 9:12:39am] 512 % dd > if=FreeBSD-9.3-RELEASE-amd64-memstick.img of=/dev/da0 > 3049+0 records in > 3049+0 records out > 1561088 bytes transferred in 17.511796 secs (89145 bytes/sec) > ^C9584+0 records in > 9583+0 records out > 4906496 bytes transferred in 54.403733 secs (90187 bytes/sec) > [root@kabini1, /etc, 9:13:51am] 513 % > [root@kabini1, /etc, 9:13:51am] 513 % > [root@kabini1, /etc, 9:13:52am] 513 % > [root@kabini1, /etc, 9:13:52am] 513 % uname -a > FreeBSD kabini1.local 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat > Aug 22 01:54:44 UTC 2015 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > [root@kabini1, /etc, 9:13:55am] 514 % > > > Note that the cp happened pretty quick, 717-ish MiB in about 15 sec., > or around 45-ish MB/s, about 1/3 of max, quite acceptable to me. > Obviously, the dd is still excruciatingly slow .... What gives ? TIA & > have a nice weekend .... > Well, I got tired of waiting (again) & moved the process to my last remaining Linux box & did the dd there. It completed OK & for grins I inserted it back into this (FreeBSD 9.3R-p24) box. It created 2 devices: [root@kabini1, /etc, 11:04:30am] 529 % lltr /dev/da0* ; date crw-r----- 1 root operator 0xd1 Sep 26 11:01 /dev/da0a crw-r----- 1 root operator 0xd0 Sep 26 11:01 /dev/da0 Sat Sep 26 11:06:37 MCDT 2015 [root@kabini1, /etc, 11:06:37am] 530 % It used to create /dev/da0s1, but no matter, I manually mounted the da0a partition & I can see stuff there, although it reports a bad FS size: [root@kabini1, /etc, 11:07:53am] 530 % df -h ; w ; pstat -hms ; uname -a ; hwclock -r ; date Filesystem Type Size Used Avail Capacity Mounted on /dev/ada0p3 ufs 19G 11G 6.2G 65% / devfs devfs 1.0k 1.0k 0B 100% /dev /dev/stripe/usr_str ufs 58G 10G 43G 19% /usr /dev/stripe/home_str ufs 3.4T 209G 3T 6% /home procfs procfs 4.0k 4.0k 0B 100% /proc tmpfs tmpfs 8.0G 32k 8G 0% /tmp linprocfs linprocfs 4.0k 4.0k 0B 100% /compat/linux/proc fdescfs fdescfs 1.0k 1.0k 0B 100% /dev/fd /dev/da0a ufs 682M 636M -8.8M 101% /media/sd 11:07AM up 12 days, 18:34, 7 users, load averages: 0.10, 0.28, 0.31 USER TTY FROM LOGIN@ IDLE WHAT wam v0 - 13Sep15 12days xinit /home/wam/.xinitrc -- /usr/local/bin/X :0 -auth /home/wam/.serverauth.1133 wam pts/5 :0 13Sep15 6days ssh -2 -X -l wam 4256ee1 wam pts/3 :0 13Sep15 3:36 ssh -2 -X -l wam 4256ee1 wam pts/0 :0 13Sep15 3days ssh -2 -X -l wam 4256ee1 wam pts/2 :0 13Sep15 4days ssh -2 -X -l wam 4256ee1 wam pts/4 :0 13Sep15 23:52 ssh -2 -X -l wam rpib+ wam pts/1 :0 13Sep15 21 ssh -2 -X -l wam rpib+ Device 1M-blocks Used Avail Capacity /dev/ada0p2 4096 1.7M 4G 0% /dev/ada1p2 4096 1.8M 4G 0% /dev/ada2p2 4096 2M 4G 0% /dev/ada3p2 4096 2.2M 4G 0% Total 16384 7.6M 16G 0% FreeBSD kabini1.local 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 01:54:44 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 hwclock: Command not found. Sat Sep 26 11:07:56 MCDT 2015 [root@kabini1, /etc, 11:07:56am] 531 % ll /media/sd/ ; date total 723 -rw-r--r-- 2 root wheel 965 Jul 10 2014 .cshrc -rw-r--r-- 2 root wheel 253 Jul 10 2014 .profile -r--r--r-- 1 root wheel 6197 Jul 10 2014 COPYRIGHT -r--r--r-- 1 root wheel 8553 Jul 10 2014 ERRATA.HTM -r--r--r-- 1 root wheel 3698 Jul 10 2014 ERRATA.TXT -r--r--r-- 1 root wheel 395727 Jul 10 2014 HARDWARE.HTM -r--r--r-- 1 root wheel 122420 Jul 10 2014 HARDWARE.TXT -r--r--r-- 1 root wheel 26579 Jul 10 2014 README.HTM -r--r--r-- 1 root wheel 12965 Jul 10 2014 README.TXT -r--r--r-- 1 root wheel 84828 Jul 10 2014 RELNOTES.HTM -r--r--r-- 1 root wheel 24075 Jul 10 2014 RELNOTES.TXT drwxr-xr-x 2 root wheel 1024 Jul 10 2014 bin/ drwxr-xr-x 7 root wheel 1024 Jul 10 2014 boot/ -rw-r--r-- 1 root wheel 39 Jul 10 2014 cdrom.inf dr-xr-xr-x 2 root wheel 512 Jul 10 2014 dev/ -r--r--r-- 1 root wheel 6593 Jul 10 2014 docbook.css drwxr-xr-x 21 root wheel 2048 Jul 10 2014 etc/ drwxr-xr-x 3 root wheel 1536 Jul 10 2014 lib/ drwxr-xr-x 3 root wheel 512 Jul 10 2014 libexec/ drwxr-xr-x 2 root wheel 512 Jul 10 2014 media/ drwxr-xr-x 2 root wheel 512 Jul 10 2014 mnt/ dr-xr-xr-x 2 root wheel 512 Jul 10 2014 proc/ drwxr-xr-x 2 root wheel 512 Jul 10 2014 rescue/ drwxr-xr-x 2 root wheel 512 Jul 10 2014 root/ drwxr-xr-x 2 root wheel 2560 Jul 10 2014 sbin/ lrwxr-xr-x 1 root wheel 11 Jul 10 2014 sys@ -> usr/src/sys drwxrwxrwt 2 root wheel 512 Jul 10 2014 tmp/ drwxr-xr-x 15 root wheel 512 Jul 10 2014 usr/ drwxr-xr-x 24 root wheel 512 Jul 10 2014 var/ Sat Sep 26 11:07:59 MCDT 2015 [root@kabini1, /etc, 11:07:59am] 532 % The USB drive is a 4 GB Mushkin unit. Did the naming convention for devices change at some point in the various kernel upgrades since last summer ? ISTR that it used to create a da0s1 device for that drive, that's what I have in my fstab file to mount that drive manually w/o the full mount command naming FS-type & mount point or device. Thanks for everything so far & TIA for any more clues .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.