From owner-freebsd-questions@freebsd.org Sun Jul 8 00:35:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 511D61041666 for ; Sun, 8 Jul 2018 00:35:28 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (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 B28A875006 for ; Sun, 8 Jul 2018 00:35:27 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x444.google.com with SMTP id h10-v6so7413524wre.6 for ; Sat, 07 Jul 2018 17:35:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aQeX2RYUBLw6vBesrx5l3ob1kdg5p6w7MwxECG7HFRg=; b=EaiV/70b9YOkPiygoMFQl82CvnedpdgH1e5RJlJDDJb5Cgd1m8d5q2FWW+NaOli9AZ TfM5krzi49MbLt3aFrIY22D74JSNsnCXRxWckcJkZug1aaLMFGjbBq79eDlCSKSSCg6F lti2VyzCBH7lTkxilBfGhb7M374t3VmAa4m8260/2nK9l3HPiVvhr/SNylJlaolxPuqu Cwf/hgSa4I1C/8xKJrhybDdl3DSGuqs/lbQTb+gVejTQz1/10wQkZF284nl+y8qIET3e miGJ13lRBXIxMlsOZr3pscdGM7xPnTcJuOEpUT4c8T/6uDg3+FCCSTvSAvno0yAyCIAP dKDQ== X-Gm-Message-State: APt69E3TGNs9sLnrVVd7NYOYd5C99zPO5zNQ035EAo0Fc5u0YFgDAvV0 Akro0yZXMQDZoG/dgMAEEr1dKA== X-Google-Smtp-Source: AAOMgpfa5GyowDejxRU+BYoItGKw/61+DfDp+lDuIqTQTAotTYJfOs9Prjw4d66QxdL5LNsWNkx+4A== X-Received: by 2002:adf:a541:: with SMTP id j1-v6mr12413141wrb.155.1531010126389; Sat, 07 Jul 2018 17:35:26 -0700 (PDT) Received: from gumby.homeunix.com ([2.222.27.178]) by smtp.gmail.com with ESMTPSA id j131-v6sm15216484wmb.25.2018.07.07.17.35.24 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 07 Jul 2018 17:35:25 -0700 (PDT) Date: Sun, 8 Jul 2018 01:35:23 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: A request for unnested UFS implementation in MBR Message-ID: <20180708013523.3f52a997@gumby.homeunix.com> In-Reply-To: References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <20180707231908.65a2e973.freebsd@edvax.de> <20180708001336.4097d20e.freebsd@edvax.de> <6bbfdaad-6872-1a6b-f176-471e57ac8d0a@yandex.com> <20180708004645.5a39c930.freebsd@edvax.de> <939bdcac-d9c3-2863-0e83-e1e87b61ded8@yandex.com> <20180708011444.82511c6a.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 00:35:28 -0000 On Sun, 8 Jul 2018 04:52:11 +0530 Manish Jain wrote: > On 07/08/18 04:44, Polytropon wrote: > > They don't. With GPT, there is no need for BSD labels anymore. > > All I am saying is exactly the same possibility for MBR. > > We can create a UFS implementation, perhaps named ufs, that gets > recorded directly in MBR table. Right now the implementation is > freebsd::freebsd-ufs. > > If someone could just touch a few things, it improves things for > eternity when we do not have bother about the extra layer (BSD). Any > extra filesystems the user needs should be found in the EBR, not in > the BSD. > > Why should a PC have multiple nesting schemas ? It only pains the > user in the future when the need for the extra nest was only in the > past (when there presumably was no EBR nest). I think it did exist, but BSD avoided the mistake made by Linux in adopting the EBR kludge. If you need multiple OSs instances on a drive, it's self-evidently better to label their partitions hierarchically rather then number them in a flat space. From owner-freebsd-questions@freebsd.org Sun Jul 8 00:42:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57ACC10422B4 for ; Sun, 8 Jul 2018 00:42:10 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C05BF755E1 for ; Sun, 8 Jul 2018 00:42:09 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x22b.google.com with SMTP id s14-v6so17429812wmc.1 for ; Sat, 07 Jul 2018 17:42:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ytO5JDZRlUJjZGkKSbkbe1/j9+pDApeFeNIXY9oEsiY=; b=W7dLaVZSKOyhOF91ZDL1XloGinGgcsAwUJJlS8dvdGUgmwbwAMjJPZKVMuAgGdIzEG UmnLyfYje3aenOyGG0gtQgoAkjmvUxmVwLtTcPZGTmy7fgpRO9PjvyWXtK6jqwDB4Mfp E1frKYy5cFBKPDTa9KyZOpufS828h8tjD9AqCAEZwXu/dhqhwFQ0VM0cH3TKF0Vgi+pt sWCY6vH5bspdUyRLHeNtU9ZH6IVhuDdVfyZo0wA2oNDBXG9r/niNVfHhj48qK3XHHvyB NHkTp3bV0fHPqgGr3tgo7GFfPWtJIm68MnErZSUPFXQnnelNB2s7pbnRm74ohEXizJjS u6Ug== X-Gm-Message-State: APt69E1V5lf6hPDmvycXkGmNGbvOcdYVQXEmzWSi/IwCRwiSVn2UZFJ7 qdclgwEBemfw9QkcuurFlJ553g== X-Google-Smtp-Source: AAOMgpe9iopKKKrC105HmNF9bDUzjeOEPd4VuhIOOTvYlem47t3wvL4ENQQKPEuy3SkXWiWQrMOpuA== X-Received: by 2002:a1c:9c0b:: with SMTP id f11-v6mr9208872wme.148.1531010528318; Sat, 07 Jul 2018 17:42:08 -0700 (PDT) Received: from gumby.homeunix.com ([2.222.27.178]) by smtp.gmail.com with ESMTPSA id z193-v6sm16210604wmc.14.2018.07.07.17.42.07 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 07 Jul 2018 17:42:07 -0700 (PDT) Date: Sun, 8 Jul 2018 01:42:06 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: A request for unnested UFS implementation in MBR Message-ID: <20180708014206.24a268a6@gumby.homeunix.com> In-Reply-To: <20180708014204.57b34879.freebsd@edvax.de> References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <20180707224648.5187be22@gumby.homeunix.com> <0753eec0-674f-842f-2dae-c8405b004dc1@yandex.com> <20180708000437.2dd95933@gumby.homeunix.com> <20180708014204.57b34879.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 00:42:10 -0000 On Sun, 8 Jul 2018 01:42:04 +0200 Polytropon wrote: > From my understanding (and explained off-list), FreeBSD > requires a 'a' BSD-labeled partition (inside a slice in > case of MBR, or on a disk if "dedicated") to boot from. > It doesn't seem to be possible to label a partition 'a' > without using labels. > > The label 'c' for data partitions is implicit and will > be synonymous for "the whole thing" (slice, disk), as > it is generated by using newfs on a MBR slice directly > (no matter if "DOS primary partition" or "logical volume > inside DOS extended partition"). It's certainly possible to put UFS on a disk, or an MBR partition, without labelling. I don't recall seeing a 'c' but I might be wrong. From owner-freebsd-questions@freebsd.org Sun Jul 8 01:18:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DC3410463E7 for ; Sun, 8 Jul 2018 01:18:49 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA5A3776F5 for ; Sun, 8 Jul 2018 01:18:48 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0M51UE-1g1ukz1BBG-00zJUF; Sun, 08 Jul 2018 03:05:43 +0200 Date: Sun, 8 Jul 2018 03:05:43 +0200 From: Polytropon To: RW Cc: RW via freebsd-questions Subject: Re: A request for unnested UFS implementation in MBR Message-Id: <20180708030543.39dc87b5.freebsd@edvax.de> In-Reply-To: <20180708014206.24a268a6@gumby.homeunix.com> References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <20180707224648.5187be22@gumby.homeunix.com> <0753eec0-674f-842f-2dae-c8405b004dc1@yandex.com> <20180708000437.2dd95933@gumby.homeunix.com> <20180708014204.57b34879.freebsd@edvax.de> <20180708014206.24a268a6@gumby.homeunix.com> 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-Provags-ID: V03:K1:5KJcrS48O3Sbwws9EgD6r35J9CwtyEWhZqJs3Mb4YghgxROSRzg CMIrQJn/hI+QynuCgxDEbsyLiOWf21fOnkCVGCofQB7qSuIR1Np8HLOBUnl11CBQ5Xt1Ota CteIyY7zrFZYFxgY+zQ0Q5LvgP1l2ej8g7nZ2GInPdh9h6pvhA+tgFmTr0YvnJOaG85fWXw wfh/wxNy5O+FZ4MJDBSCg== X-UI-Out-Filterresults: notjunk:1;V01:K0:hfUM5K7/xeA=:wmZJ5vhJlrf4q0GtdsLoal /JoeLFVDVHfoyJUb2x7Fk9rYClV5+x4Xq4WbTTlXr0J2ALgpoOChyuIKxiuldIjm75Q7vISro 3vPyfPj0oUXTXSXCLSuYNX/XW1Gy5iVim/t+vyZ9vcucc338AMHWJhP1yGLuvLqBRoml2yKEA nUlXoF1VHSL8WuSPCPWqgpSYcW/kq2QiM4yIineFvtk+I6pfkd00zi5OlxI/9FalVLvqpLNXO UxJxjAMXz8ASbex0kdRBmiFkFeAqPOpIVtiW3UAWUT1bPz2+KDRDUXHUFwkfbJxk71tABUUTC Ii4XimJNvya2zEPd+lQiaGfDG/Czm1/rqnLra8VyA93Sht2Ay+HoEnrf+6OfKYwaLk9Jm45Iu SfBOPx1BegNZh8MYEdINDY/znWlg+ka3PrlTgd2e61KF6DajUhvetTCNlQU2ZCVo0ls6+IPkA RBi4R8BdT0oomJyHXXkelrVmpnWVJw5IzGeopRO4/KAJh31PODmSm4cEHXFR+52Ee/IvirB06 8t2Ldoh/N07frr6Xk7n7ABa1CE7Z+qlD9Rx9ma/wNoQAXJWGMeSUTr67SCxgVDtVbjcPrp5H2 sWO37ecrMmym9xokYhXNtgyT4kDtuSARWK/kJ6Jd7mVL9c+gxm2kTHQsNJ7Z7oziHagBcDiJr Yjfxou10QxXZ+uOEtPZBNfRm7FRIcT9jgGGpTdndjckjpGEblO5vxPtTCFbn7H2XiQxiXoXur FMdQNpErygdgOPvD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 01:18:49 -0000 On Sun, 8 Jul 2018 01:42:06 +0100, RW via freebsd-questions wrote: > On Sun, 8 Jul 2018 01:42:04 +0200 > Polytropon wrote: > > > > From my understanding (and explained off-list), FreeBSD > > requires a 'a' BSD-labeled partition (inside a slice in > > case of MBR, or on a disk if "dedicated") to boot from. > > It doesn't seem to be possible to label a partition 'a' > > without using labels. > > > > The label 'c' for data partitions is implicit and will > > be synonymous for "the whole thing" (slice, disk), as > > it is generated by using newfs on a MBR slice directly > > (no matter if "DOS primary partition" or "logical volume > > inside DOS extended partition"). > > It's certainly possible to put UFS on a disk, or an MBR partition, > without labelling. Of course it is, I do it all the time for data disks. :-) If you have a disk da0 in your system and you "newfs /dev/da0", then you get a UFS filesystem /dev/da0c which is equivalent to /dev/da0, and you can "mount -t ufs /dev/da0 /mnt". This works the same for a slice ("DOS primary partition"), for example "newfs /dev/da0s1" and then "mount -t ufs /dev/da0s1 /mnt", where da0s1c equals da0s1. Again, 'c' means "the whole thing" (disk, slice). The other letters are usually reserved for use in this way: a boot partition b swap c "the whole thing" d user-defined (for example /tmp) e user-defined (for example /var) f user-defined (for example /usr) g user-defined (for example /opt) h user-defined (for example /home) There is a limit on letters. :-) Initially, this is how the BSDs partitioned a disk, and this existed long before MBR. That's why the requirement of a boot partition - where should the OS boot from? The logical conclusion is: If you want to use an 'a' partition for being able to boot from, you have to create labels. FreeBSD won't boot from a 'c' partition. >From "man 8 boot": The automatic boot will attempt to load /boot/loader from partition `a' of either the floppy or the hard disk. There is no word about this mechanism working with 'c', too. Of course, this would be subject to an interesting experiment: Create a slice and directly format it. Put /boot/loader on it, as well as a kernel and maybe the whole OS. Instruct the boot loader to boot from it (e. g., boot device = /dev/ada0s7). > I don't recall seeing a 'c' but I might be wrong. The 'c' isn't needed anymore as c == . As there is no actual BSD label, you can't see it even if you use the traditional disklabel / bsdlabel tool. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Jul 8 01:17:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CFCA1046122 for ; Sun, 8 Jul 2018 01:17:44 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from forward103p.mail.yandex.net (forward103p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5752775AD for ; Sun, 8 Jul 2018 01:17:43 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from mxback1g.mail.yandex.net (mxback1g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:162]) by forward103p.mail.yandex.net (Yandex) with ESMTP id 319802181D69; Sun, 8 Jul 2018 04:17:41 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback1g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id XWFXye1pTx-Hf10odqu; Sun, 08 Jul 2018 04:17:41 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531012661; bh=47+84kacJGDUws3+tqr4wBSqfktQYRnbYtXkp36ufAc=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=caEvfLxbtvmYfcCSAkkyWEgDTk3PZkwElm1b30S5K4okIA9SZYUJMrPTdKomMKkPt d7hDJEuEaH8I/1lSgnwq6QhTM7ZyFanvp4lEWlkgVym0IsLViib7Y/LNr89bUIkPqz xRYLeJynjVGG+4dFN8rHD+51Wc424EJyWxwxjjI8= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id U0jr4Nlmk5-Hd34hWxs; Sun, 08 Jul 2018 04:17:40 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531012660; bh=47+84kacJGDUws3+tqr4wBSqfktQYRnbYtXkp36ufAc=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=trewKVGtuK4OIOerel8OOHn1Ka0Mv1eiltClyW83wgUXRW0K39dTBBh7qucj7DGJx 2X2WAPty4Re71jFGLCOXMtzVKYxzpG5bHnP5pLsmgCrc32wKFXwHUR8SmXqFUeRhhe gfNJ3iHfl4Q/lTLQAUSYk7sRdOTqeiBBDIcF45Bo= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@yandex.com Subject: Re: A request for unnested UFS implementation in MBR To: RW , freebsd-questions@freebsd.org References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <20180707231908.65a2e973.freebsd@edvax.de> <20180708001336.4097d20e.freebsd@edvax.de> <6bbfdaad-6872-1a6b-f176-471e57ac8d0a@yandex.com> <20180708004645.5a39c930.freebsd@edvax.de> <939bdcac-d9c3-2863-0e83-e1e87b61ded8@yandex.com> <20180708011444.82511c6a.freebsd@edvax.de> <20180708013523.3f52a997@gumby.homeunix.com> From: Manish Jain Message-ID: <50aade00-40a4-ffd9-3900-b18145d5cd47@yandex.com> Date: Sun, 8 Jul 2018 06:45:37 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180708013523.3f52a997@gumby.homeunix.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 01:17:44 -0000 On 07/08/18 06:05, RW via freebsd-questions wrote: > On Sun, 8 Jul 2018 04:52:11 +0530 > Manish Jain wrote: > >> On 07/08/18 04:44, Polytropon wrote: >>> They don't. With GPT, there is no need for BSD labels anymore. >> >> All I am saying is exactly the same possibility for MBR. >> >> We can create a UFS implementation, perhaps named ufs, that gets >> recorded directly in MBR table. Right now the implementation is >> freebsd::freebsd-ufs. >> >> If someone could just touch a few things, it improves things for >> eternity when we do not have bother about the extra layer (BSD). Any >> extra filesystems the user needs should be found in the EBR, not in >> the BSD. >> >> Why should a PC have multiple nesting schemas ? It only pains the >> user in the future when the need for the extra nest was only in the >> past (when there presumably was no EBR nest). > > I think it did exist, but BSD avoided the mistake made by Linux in > adopting the EBR kludge. > > If you need multiple OSs instances on a drive, it's self-evidently > better to label their partitions hierarchically rather then number > them in a flat space. Hi RW, I submit to the wisdom of choices BSD made, and continues to make. Which is why I use FreeBSD - very proudly - as my only OS. Noone can legitimately claim better claim better solutions than envisaged by Berkeley. But in my humble opinion, the right way to treat MBR is simply as GPT (with the number of partitions permitted not 128, but 3 - with 128 non-bootable extras relegated to a system the MBR schema itself provides for). Who gains today for the loss of the user who cannot create UFS partitions in MBR ? Thanks and a hope that someone will see a point in my humble request. Manish Jain From owner-freebsd-questions@freebsd.org Sun Jul 8 02:34:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3801EFDA1EE for ; Sun, 8 Jul 2018 02:34:31 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from mail.cyberleo.net (paka.cyberleo.net [216.226.128.180]) (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 CBBE27AFC0 for ; Sun, 8 Jul 2018 02:34:30 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from [172.18.169.172] (unknown [164.52.229.194]) by mail.cyberleo.net (Postfix) with ESMTPSA id C556D5A16F; Sat, 7 Jul 2018 22:34:22 -0400 (EDT) Subject: Re: Fwd: A request for unnested UFS implementation in MBR To: Manish Jain , FreeBSD Questions References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> From: CyberLeo Message-ID: Date: Sat, 7 Jul 2018 21:34:21 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 02:34:31 -0000 On 07/07/2018 03:50 PM, Manish Jain wrote: > Hi, > > I made a request for FreeBSD UFS filesystem to the freebsd-fs list. Just > for opinions on this list, I am forwarding that request underneath. > > Tx > Manish Jain > > > -------- Forwarded Message -------- > Subject: A request for unnested UFS implementation in MBR > Date: Sat, 7 Jul 2018 11:29:55 +0530 > From: Manish Jain > To: freebsd-fs@freebsd.org > > Hi all, > > I am a longtime user of FreeBSD, which now serves as my only OS. > > There is one request I wished to make for FreeBSD filesystems. While UFS > implementation under GPT is unnested just as Ext2, the MBR > implementation of UFS continues to piggyback on an unnecessary nest (in > a BSD slice). > > Can it not be considered as an alternative to provide a UFS partition > (unnested) under MBR too ? > > Existing users could continue to use the freebsd::freebsd-ufs scheme, > while fresh usage could have the alternative of UFS directly recorded in > the MBR. > > I should perhaps note that unlike most users who have shifted to GPT of > late, I much prefer MBR because 1) the scheme's design by itself keeps > the number of slices/partitions in a disk manageable; and 2) I can use > the boot0 manager, my favourite boot manager. You can create a UFS filesystem on any disk device, including an unlabeled slice of any type code, right now. This might even be safe if you never run any OS that might misinterpret the type codes you have used! Simply create your desired layout with your chosen type codes, and run newfs on the appropriate device node. The FreeBSD kernel does not care about type codes when mounting filesystems enumerated in the fstab or via device nodes provided manually. However, you cannot boot FreeBSD using the native bootstrap without GPT or a BSD label on your boot device, as MBR offers no designated place to put the second stage bootstrap. Hope this helps! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Element9 Communications http://www.Element9.net Furry Peace! - http://www.fur.com/peace/ From owner-freebsd-questions@freebsd.org Sun Jul 8 08:52:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C54A1029A98 for ; Sun, 8 Jul 2018 08:52:23 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D8938A2C0 for ; Sun, 8 Jul 2018 08:52:22 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.2]) (Authenticated sender: mayuresh@kathe.in) by relay7-d.mail.gandi.net (Postfix) with ESMTPA id 57DD720008 for ; Sun, 8 Jul 2018 08:52:14 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Jul 2018 14:22:14 +0530 From: Mayuresh Kathe To: freebsd-questions@freebsd.org Subject: [commercial] sendmail setup request Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in Message-ID: X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 08:52:23 -0000 hi, i own a domain (kathe.in) for which email services are provided by the domain registrar itself. email services include imap, smtp and webmail. the problem is that i lean more towards using mailx under bsd and at the same time also wish to have my mails stored online (or rather non-locally). i might be wrong, but i have concluded that the best and also the most economical solution would be to go for either rootbsd or digitalocean using a freebsd instance and run sendmail to provide email services in and out of the instance. and now comes the real bummer, i don't have any idea about how to setup sendmail to allow the above. if there is anyone with expertise in setting up sendmail under freebsd i would be more than willing to pay her/his charges for the same. thank you. From owner-freebsd-questions@freebsd.org Sun Jul 8 11:49:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 362C4103D2CC for ; Sun, 8 Jul 2018 11:49:44 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id DD82C70D6B for ; Sun, 8 Jul 2018 11:49:43 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vvelox.net (localhost [127.0.0.1]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id 3F81622AC7E0 for ; Sun, 8 Jul 2018 06:49:35 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Jul 2018 06:49:35 -0500 From: "Zane C. B-H." To: freebsd-questions@freebsd.org Subject: displaying long SSIDs Message-ID: <1b3bc11511677689ed03347dd34bb29b@vvelox.net> X-Sender: v.velox@vvelox.net User-Agent: Roundcube Webmail/1.3.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 11:49:44 -0000 Howdy! Is there any way to display long SSIDs with list scan for ifconfig? In the SSID column it truncates them and appends '...'. Trying to figure out how to get that working, since 'wpa_cli scan' results in a disconnect and unless it has just been started 'wpa_cli scan_results' just shows the currently connected one. 'ifconfig wlan0 list scan' will consistently work though, minus the truncating of names. From owner-freebsd-questions@freebsd.org Sun Jul 8 13:15:40 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F8971045EEC for ; Sun, 8 Jul 2018 13:15:40 +0000 (UTC) (envelope-from vvelox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2E39874227 for ; Sun, 8 Jul 2018 13:15:40 +0000 (UTC) (envelope-from vvelox@vvelox.net) Received: from vixen42.vulpes.vvelox.net (vixen42.vulpes.vvelox.net [192.168.15.2]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id 6EE8E22AC7DE; Sun, 8 Jul 2018 08:15:37 -0500 (CDT) Date: Sun, 8 Jul 2018 08:15:37 -0500 From: "Zane C. B-H." To: freebsd-questions@freebsd.org Cc: mayuresh@kathe.in Subject: Re: [commercial] sendmail setup request Message-ID: <20180708081537.64e89936@vixen42.vulpes.vvelox.net> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 13:15:40 -0000 On Sun, 08 Jul 2018 14:22:14 +0530 Mayuresh Kathe wrote: > hi, > > i own a domain (kathe.in) for which email services are provided by the > domain registrar itself. email services include imap, smtp and > webmail. > > the problem is that i lean more towards using mailx under bsd and at > the same time also wish to have my mails stored online (or rather > non-locally). > > i might be wrong, but i have concluded that the best and also the most > economical solution would be to go for either rootbsd or digitalocean > using a freebsd instance and run sendmail to provide email services in > and out of the instance. > > and now comes the real bummer, i don't have any idea about how to > setup sendmail to allow the above. > > if there is anyone with expertise in setting up sendmail under freebsd > i would be more than willing to pay her/his charges for the same. On another note, just because FreeBSD comes with sendmail by default does not mean you have to use it. Personally I would suggest sparing your sanity and checking out Postfix instead. As far as off site storage goes, I personally would use that for backup instead of general mail store. From owner-freebsd-questions@freebsd.org Sun Jul 8 16:32:50 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AB261038EB6 for ; Sun, 8 Jul 2018 16:32:50 +0000 (UTC) (envelope-from srs0=tog7=jy=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id CEF2A7D39F for ; Sun, 8 Jul 2018 16:32:49 +0000 (UTC) (envelope-from srs0=tog7=jy=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 41NvBx6GsXz2fjQS; Sun, 8 Jul 2018 09:32:41 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Signal 6 From: Doug Hardie In-Reply-To: Date: Sun, 8 Jul 2018 09:32:41 -0700 Cc: freebsd-questions Content-Transfer-Encoding: quoted-printable Message-Id: <9D5EC5A8-6AB3-43EA-9641-C0FA26972E3B@mail.sermon-archive.info> References: <0D66C7A3-EBE6-475C-8360-CAFEAEA4D328@mail.sermon-archive.info> To: Michael Sierchio X-Mailer: Apple Mail (2.3445.8.2) X-Virus-Scanned: clamav-milter 0.99.4 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 16:32:50 -0000 -- Doug > On 29 June 2018, at 08:56, Michael Sierchio = wrote: >=20 > Are there process limits? Yes - defaults as best as I can tell. brain# limits Resource limits (current): cputime infinity secs filesize infinity kB datasize 33554432 kB stacksize 524288 kB coredumpsize infinity kB memoryuse infinity kB memorylocked infinity kB maxprocesses 12128 openfiles 232812 sbsize infinity bytes vmemoryuse infinity kB pseudo-terminals infinity swapuse infinity kB kqueues infinity umtxp infinity brain# limits -p 47719 This is the current process in question - = owned by root Resource limits (current): pseudo-terminals 47719 brain# limits -U root Resource limits for class root: cputime infinity secs filesize infinity kB datasize infinity kB stacksize infinity kB coredumpsize infinity kB memoryuse infinity kB memorylocked infinity kB maxprocesses infinity openfiles infinity sbsize infinity bytes vmemoryuse infinity kB pseudo-terminals infinity swapuse infinity kB kqueues infinity umtxp infinity I am guessing that stacksize limits the heap? But I can't tell which = value is used by that process. > malloc() will call abort() if internal structures are munged (e.g., by = heap overflow). I am suspecting this is the cause, but how do you tell what the heap = usage is? >=20 > calling free() on a corrupted pointer does that reliably This process runs on a number of different machines. Only the one has = the issue so I suspect that it is data dependent. This one handles the = most data. >=20 > is the root partition big enough for the dump? Yes - single partition system. 191 Gb available in the / partition. >=20 > =3D M >=20 > On Fri, Jun 29, 2018 at 8:40 AM, Doug Hardie wrote: > I have a daemon process that runs forever (almost). Something is = killing it with a signal 6, but no core dump is done. If I manually = kill it with kill -6, then the log message shows core dumped and a core = file is created. The process has no reference to SIG_ABRT, so I suspect = the kernel is doing the kill and is overriding the core dump. I have = previously encountered a similar issue where swap space was running out = and the kernel killed this process without a core dump. In that case = there were quite a few messages logged about swap space issues before = the process was killed. There are no swap messages logged this time. >=20 > /etc/sysctl.conf contains: > kern.sugid_coredump=3D1 > kern.corefile=3D/crash/%N.core >=20 > /crash is a directory in the root file system. >=20 > Other than swap issues, when would the kernel kill a process without a = core dump? >=20 > -- Doug >=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" >=20 >=20 >=20 > --=20 > "Well," Brahma said, "even after ten thousand explanations, a fool is = no wiser, but an intelligent person requires only two thousand five = hundred." >=20 > - The Mah=C4=81bh=C4=81rata From owner-freebsd-questions@freebsd.org Sun Jul 8 21:23:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32C531034043 for ; Sun, 8 Jul 2018 21:23:42 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FC488CA40 for ; Sun, 8 Jul 2018 21:23:41 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue001 [212.227.15.167]) with ESMTPA (Nemesis) id 0LovIK-1gGrAN1bXA-00etEV; Sun, 08 Jul 2018 23:23:15 +0200 Date: Sun, 8 Jul 2018 23:23:14 +0200 From: Polytropon To: mayuresh@kathe.in Cc: freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Message-Id: <20180708232314.204d7f12.freebsd@edvax.de> In-Reply-To: References: 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-Provags-ID: V03:K1:hIByiJB42vYskZZWzq0QZeEeabCRzNdDBDMxdfu41o7zN25ynOZ 16mZB/eUuwraCzWdfxT5j2idkAFcDV7GGMQ/qJE1/7/sXSaUrbBgkUy5HWUHApaO5uU4lTo taXQx4Nw/j/GKlnJ5f4m+06RV0LU6ISbbZ39vc3yH9KN0KUSnDoSwDO6xkVG+PR9O33KA3F pvguVIvWwj8HRbCUsSDGw== X-UI-Out-Filterresults: notjunk:1;V01:K0:VXXExRSueqQ=:IFdWPve4PdHb6aYwEC3Oj0 gTEWsYbyv3/CnYbWAU1B80dQojFM6AZnhuP0wMpHfGHdexbJwFf6Jf4CwQ3mq6ROsNRrGX9pG AaKCbFp7cDW4WevqO2M3u/a6B1XIzoGishaacEOfSMMpWDoaX2JT7ZmtYPIKLjQeMPqYdfO8v WGzeBlRLUHyubzJc7GOrHPGIwFU9Ddoi2oZNe2Y5cfuEkzjqn1PIYjiq1pQ9JMeUFOWx/zZ/o 0+8+JnL78cplAIH0qdTtgR2AmyEpg0jZGYdBDpnS02Ii+XNGyhd+DMdtVU1Z9HDx0OaJNUZrO kcyVLRDTo1nWXXVX7UsNZvmc3NG3KA4iWGVRzuCa9X0YvJQVH87jxl340Y9FMz3luZh29BxAf jTO/z+mE3LPGkXMyGM8bmvBhgXt+htAJO3xtpGum4fr9rlJHn3YSo+1UoH04+jUB6uFiizLm0 rpk3r8pevz+0wd/DikYe7JoeQU2WyH/dPehk/H3yf8L6UbuIDHa7MNEI3Ll0pPs7pOo0B5Ani J7piz36vba3HkDBJ7U4kL4xJ/kJVRqpz7EOPpckRNJwDMpS4uVUtA7zT4RfHI2uc7NQFl1r0O 5HWK+jqJKHBVh8jUp6e8Rs13hAhzGW1CFBE1hVPZmZKPTFm+J8TvfVvdJsYafKuxpF7l9nuzZ tcfc1BWVABhwuuIyibZL2X8p4xhlRQbr1pwnS9q+1sMVbJJAp9YVAj0CueqJWBWNxcMSwljXg 7ygR0ZOjOHpSJg7L X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 21:23:42 -0000 On Sun, 08 Jul 2018 14:22:14 +0530, Mayuresh Kathe wrote: > i own a domain (kathe.in) for which email services are provided by the > domain registrar itself. email services include imap, smtp and webmail. > > the problem is that i lean more towards using mailx under bsd and at > the same time also wish to have my mails stored online (or rather > non-locally). > > i might be wrong, but i have concluded that the best and also the most > economical solution would be to go for either rootbsd or digitalocean > using a freebsd instance and run sendmail to provide email services in > and out of the instance. > > and now comes the real bummer, i don't have any idea about how to setup > sendmail to allow the above. I don't want to sound impolite, but did you ask yourself if you're asking the right question here? Maybe I didn't fully understand your goals, so allow me to ask: 1. Do you want to stay with your domain provider as the "keeper of the mail" and just want to be able to use xmail instead of a (usually annoying) webmailer? 2. Are you prepared to run your own mail infrastructure? Do you want to provide the "all and everything" yourself, usually POP3 + SMTP + IMAP + Webmail? If no. 1 is fine for you, have a look at local IMAP mirroring. There is still one problem, though: The program mailx (just like the system's native mail command) uses mbox for storing messages. IMAP mirroring tools usually use MailDir. Sure, you can convert between the two, but it's additional work. For an example of an IMAP mirroring tool, check out OfflineIMAP. No. 2 is more difficult to deal with, that's for sure. Running your own infrastructure and having your peers properly interact with it (!) isn't as easy as it was decades ago. "Reputation", anti-spam, anti-virus, encryption and certificates, "score", all this needs to be done, along with installing, updating and of course properly configuring the services you need. Even though I'm initially a "sendmail person", nowadays I tend to suggest Postfix. It's a lot easier to work with, and the integration of tools for IMAP or for a webmailer is also quite convenient. There's plenty of documentation, but it usually assumes that you are at least familiar with basic concepts of mail operations. And there are decisions ahead because there is no "the ONE setup", as almost every functionality can be provided by more than one software product that is available on FreeBSD. Here are a few resources: https://forums.freebsd.org/threads/postfix-courier-imap-mysql-and-freebsd.19470/ https://forums.freebsd.org/threads/imap-installation.8396/ https://www.freebsddiary.org/dovecot.php http://www.postfix.org/BASIC_CONFIGURATION_README.html https://help.ubuntu.com/community/PostfixBasicSetupHowto -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jul 9 05:20:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02A0210429A0; Mon, 9 Jul 2018 05:20:29 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay11.mail.gandi.net (relay11.mail.gandi.net [217.70.178.231]) (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 6CEB680F34; Mon, 9 Jul 2018 05:20:27 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.1]) (Authenticated sender: mayuresh@kathe.in) by relay11.mail.gandi.net (Postfix) with ESMTPA id EC80B10000A; Mon, 9 Jul 2018 05:20:18 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Jul 2018 05:20:18 +0000 From: Mayuresh Kathe To: Polytropon Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: <20180708232314.204d7f12.freebsd@edvax.de> References: <20180708232314.204d7f12.freebsd@edvax.de> Message-ID: <6e21b74531c2b6ca7ca89cfc37add6a2@kathe.in> X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 05:20:29 -0000 On 2018-07-08 09:23 PM, Polytropon wrote: > On Sun, 08 Jul 2018 14:22:14 +0530, Mayuresh Kathe wrote: >> i own a domain (kathe.in) for which email services are provided by the >> domain registrar itself. email services include imap, smtp and >> webmail. >> >> the problem is that i lean more towards using mailx under bsd and at >> the same time also wish to have my mails stored online (or rather >> non-locally). >> >> i might be wrong, but i have concluded that the best and also the most >> economical solution would be to go for either rootbsd or digitalocean >> using a freebsd instance and run sendmail to provide email services in >> and out of the instance. >> >> and now comes the real bummer, i don't have any idea about how to >> setup >> sendmail to allow the above. > > I don't want to sound impolite, but did you ask yourself if > you're asking the right question here? Maybe I didn't fully > understand your goals, so allow me to ask: > > 1. Do you want to stay with your domain provider as the "keeper > of the mail" and just want to be able to use xmail instead > of a (usually annoying) webmailer? > > 2. Are you prepared to run your own mail infrastructure? Do > you want to provide the "all and everything" yourself, > usually POP3 + SMTP + IMAP + Webmail? > [snip] my goals are very basic and hence quite simple. i should be able to log into the freebsd instance as my username which would be the same as my email address (mayuresh@kathe.in) and use mailx to go through my emails. i don't need imap nor webmail. i know it must be a simple sendmail setup, but frankly, i'm not capable enough to understand the in-and-out of sendmail to be able to configure it to my requirement. thanks polytropon, and yes, you were not at all impolite. :-) From owner-freebsd-questions@freebsd.org Mon Jul 9 05:37:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 169CD1044534 for ; Mon, 9 Jul 2018 05:37:12 +0000 (UTC) (envelope-from srs0=+2ih=jz=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id ACAE581BBD for ; Mon, 9 Jul 2018 05:37:11 +0000 (UTC) (envelope-from srs0=+2ih=jz=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 41PDc62XgMz2fjRB; Sun, 8 Jul 2018 22:37:10 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Signal 6 From: Doug Hardie In-Reply-To: Date: Sun, 8 Jul 2018 22:37:09 -0700 Cc: freebsd-questions Content-Transfer-Encoding: quoted-printable Message-Id: References: <0D66C7A3-EBE6-475C-8360-CAFEAEA4D328@mail.sermon-archive.info> To: Michael Sierchio X-Mailer: Apple Mail (2.3445.8.2) X-Virus-Scanned: clamav-milter 0.99.4 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 05:37:12 -0000 > On 29 June 2018, at 08:57, Michael Sierchio = wrote: >=20 > One way to find out is to register a handler for SIGABRT and print and = flush the context. Registering a handler is easy. The stack is shown through backtrace(). = However, if the backtrace is in the main code, it shows the complete = stack. If it is in an interrupt handler function then it only shows the = call to backtrace. Is there some way to give it access to the complete = stack? >=20 > On Fri, Jun 29, 2018 at 8:56 AM, Michael Sierchio = wrote: > Are there process limits? >=20 > malloc() will call abort() if internal structures are munged (e.g., by = heap overflow). >=20 > calling free() on a corrupted pointer does that reliably >=20 > is the root partition big enough for the dump? >=20 > =3D M >=20 > On Fri, Jun 29, 2018 at 8:40 AM, Doug Hardie wrote: > I have a daemon process that runs forever (almost). Something is = killing it with a signal 6, but no core dump is done. If I manually = kill it with kill -6, then the log message shows core dumped and a core = file is created. The process has no reference to SIG_ABRT, so I suspect = the kernel is doing the kill and is overriding the core dump. I have = previously encountered a similar issue where swap space was running out = and the kernel killed this process without a core dump. In that case = there were quite a few messages logged about swap space issues before = the process was killed. There are no swap messages logged this time. >=20 > /etc/sysctl.conf contains: > kern.sugid_coredump=3D1 > kern.corefile=3D/crash/%N.core >=20 > /crash is a directory in the root file system. >=20 > Other than swap issues, when would the kernel kill a process without a = core dump? >=20 > -- Doug >=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" >=20 >=20 >=20 > --=20 > "Well," Brahma said, "even after ten thousand explanations, a fool is = no wiser, but an intelligent person requires only two thousand five = hundred." >=20 > - The Mah=C4=81bh=C4=81rata >=20 >=20 >=20 > --=20 > "Well," Brahma said, "even after ten thousand explanations, a fool is = no wiser, but an intelligent person requires only two thousand five = hundred." >=20 > - The Mah=C4=81bh=C4=81rata From owner-freebsd-questions@freebsd.org Mon Jul 9 05:40:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C03910449A2; Mon, 9 Jul 2018 05:40:26 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) (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 67A3481D1A; Mon, 9 Jul 2018 05:40:25 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (localhost [127.0.0.1]) by mail.cs.ait.ac.th (Postfix) with ESMTP id A58BB61F82; Mon, 9 Jul 2018 12:40:10 +0700 (+07) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.ait.ac.th; h= content-type:content-type:mime-version:message-id:date:date :in-reply-to:subject:subject:from:from:received:received :received; s=selector1; t=1531114810; x=1532929211; bh=K809XEqef +EgOq0Tj2RAXy8RW6QEHpLnTBZ7ATrgj8E=; b=Ouo7ZAzHNOasOrIrGltqAtYrJ OEAi7GtVZcfu/Os6xx9vaq4swL5W7yBhw16T/r5hLyX9Q+oQEahhNGUqL7JXDOBX RMD9llkhRaYEPUGgyeLIkQ6ma/58UZGkmZBkGWxde0yXbEQ8MwwKdC81x0diHWcU or6m/I0op0ySPKbloI= X-Virus-Scanned: amavisd-new at cs.ait.ac.th Received: from mail.cs.ait.ac.th ([127.0.0.1]) by mail.cs.ait.ac.th (mail.cs.ait.ac.th [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id qp1bJCTUaEbo; Mon, 9 Jul 2018 12:40:10 +0700 (+07) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cs.ait.ac.th (Postfix) with ESMTPS id 0E6E561F81; Mon, 9 Jul 2018 12:40:09 +0700 (+07) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.15.2/8.15.2/Submit) id w695e5hr048349; Mon, 9 Jul 2018 12:40:05 +0700 (ICT) (envelope-from on@banyan.cs.ait.ac.th) From: Olivier To: mayuresh@kathe.in Cc: freebsd@edvax.de, freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request In-Reply-To: <6e21b74531c2b6ca7ca89cfc37add6a2@kathe.in> (message from Mayuresh Kathe on Mon, 09 Jul 2018 05:20:18 +0000) Date: Mon, 09 Jul 2018 12:40:05 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 05:40:26 -0000 Mayuresh Kathe writes: > my goals are very basic and hence quite simple. > i should be able to log into the freebsd instance as my username > which would be the same as my email address (mayuresh@kathe.in) > and use mailx to go through my emails. > i don't need imap nor webmail. > i know it must be a simple sendmail setup, but frankly, i'm not > capable enough to understand the in-and-out of sendmail to be > able to configure it to my requirement. If your needs are really limited to what you describe, you may consider using fetchmail to get the mail from your current mail server (at your registrar). Fetchmail should dump your mail on your FreeBSD system and you will be able to use mailx. That way, you avoid all the problems of setting up a machine intended to receive mail. The configuration to send mail from your FreeBSD/mailx machine should be quite simple (just a few lines to tell sendmail to push your outgoing mail to the mail server at your registrar). If you really inted to set-up your onw complete mail system, goodluck, because it is a lot of work to do :) Good luck, Olivier > > thanks polytropon, and yes, you were not at all impolite. :-) > _______________________________________________ > 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 Jul 9 06:33:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B65E10234EC; Mon, 9 Jul 2018 06:33:00 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (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 6680B84194; Mon, 9 Jul 2018 06:32:58 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.4]) (Authenticated sender: mayuresh@kathe.in) by relay5-d.mail.gandi.net (Postfix) with ESMTPA id C33721C000E; Mon, 9 Jul 2018 06:32:50 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Jul 2018 06:32:50 +0000 From: Mayuresh Kathe To: Olivier Cc: freebsd@edvax.de, freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: References: Message-ID: X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:33:00 -0000 On 2018-07-09 05:40 AM, Olivier wrote: > Mayuresh Kathe writes: > >> my goals are very basic and hence quite simple. >> i should be able to log into the freebsd instance as my username >> which would be the same as my email address (mayuresh@kathe.in) >> and use mailx to go through my emails. >> i don't need imap nor webmail. >> i know it must be a simple sendmail setup, but frankly, i'm not >> capable enough to understand the in-and-out of sendmail to be >> able to configure it to my requirement. > > If your needs are really limited to what you describe, you may consider > using fetchmail to get the mail from your current mail server (at your > registrar). Fetchmail should dump your mail on your FreeBSD system and > you will be able to use mailx. That way, you avoid all the problems of > setting up a machine intended to receive mail. > > The configuration to send mail from your FreeBSD/mailx machine should > be > quite simple (just a few lines to tell sendmail to push your outgoing > mail to the mail server at your registrar). > > If you really inted to set-up your onw complete mail system, goodluck, > because it is a lot of work to do :) my needs are indeed limited to what i have described, on reading it, you would notice that i do not wish to have my mails be stored locally. i want to have the mails on a server instance so that i can access them from a machine other than mine via ssh. i know that setting up a complete mail system would be a lot of work, and that's why i have tagged my emails with the "commercial" tag as well as mentioned in my first mail in this thread that i wouldn't mind paying the fees required by someone who can build me that sendmail configuration. From owner-freebsd-questions@freebsd.org Mon Jul 9 06:40:53 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A59E1024479 for ; Mon, 9 Jul 2018 06:40:53 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68BD284595 for ; Mon, 9 Jul 2018 06:40:52 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue101 [212.227.15.183]) with ESMTPA (Nemesis) id 0MQw3C-1fWTlP2cBy-00UHb5; Mon, 09 Jul 2018 08:35:29 +0200 Date: Mon, 9 Jul 2018 08:35:26 +0200 From: Polytropon To: Olivier Cc: mayuresh@kathe.in, freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Message-Id: <20180709083526.c4b4924f.freebsd@edvax.de> In-Reply-To: References: <6e21b74531c2b6ca7ca89cfc37add6a2@kathe.in> 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-Provags-ID: V03:K1:CHxndl3gnrvwTX/56wEOykjRQwUV8qLB0wkq/9KQwiO9tAhUReX zkBkt64llcgF3g0b+b3Bk2hyaFr/EOj1xBh0FVDLfMqRzYCmaTe79QCLykvHsqPK42O8BEp H9axv0gZBVIM7VSqar+S8dYsR95uMMxX2m0YyVx+yeqWjhSEuFVuLVRYWHKP2KFX6NWF6O5 3du8hQUir5S02EHmQ6UmA== X-UI-Out-Filterresults: notjunk:1;V01:K0:2suJbt1FXxs=:Qb2/fwVwRVgJFGNGZTjBPV v/j2KMG9+Ur7atedDClGfqXGq78kogcTjMHYvrTOU92bfKQutILAjB+kzz7CVx8w23eFzh26F 4KhTFl0lhMdtgIGnEO7yFXGjGrpCd+6sqYY54aW+kERRyK+BgK9LxG6JXvU76sYEe91foe1vE XEtD6w69+DS8Eq70l7kpwtO3hYlYLL4L+YjXjW215LiRau9mZGulsGHfDsgamaO8pEwNicFK+ 7HW5suhItElZP356DngO9d1F4BJbH6iq2IiGaM1e+a6URUn5SGEyxikqyLVCdv0iFxCNCmnBK iqPVyg623VpHrPwKfDWoOCx12ACkHmFfIFFUgjaO3jM6Qyasw+Mj8dPEs9oNAV33htLFIlOvl DC+a6jNSOkkOxoUs3QSf6sbctVMUHSWdMURJjU6H4bgR8g1wEuxRT8RyS7c5yJQDp3mz5XEmb y4theqhlrOD0nkKboABWnCniCSSmUTmt9RdI3pYtHvIq66IoEJlya9BGAtiyt/HskVfbCn2BJ EDwXUXly5eRPw02OJX7BSDG4nnfSPsP1/O+PUjQUUDyyWVE7dmlfNStKhlOzmKCiQoKFS3wpQ 72k8xB9Q4kWW6NUbA1pX2VsbDqpkIZvZHg7k8REgAqAoX3k/FS8sq/GEz1NGCRXTOUoHyz1+9 m6UGD53O7N3tGQ3/E714cFk2nv/dBZBvAfMNR8y/OZzEvidJOLHWMRH6VKMYEGBJQY7X53jSP vvGgKpTUyvQD7cZ2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:40:53 -0000 On Mon, 09 Jul 2018 12:40:05 +0700, Olivier wrote: > Mayuresh Kathe writes: > > > my goals are very basic and hence quite simple. > > i should be able to log into the freebsd instance as my username > > which would be the same as my email address (mayuresh@kathe.in) > > and use mailx to go through my emails. > > i don't need imap nor webmail. > > i know it must be a simple sendmail setup, but frankly, i'm not > > capable enough to understand the in-and-out of sendmail to be > > able to configure it to my requirement. > > If your needs are really limited to what you describe, you may consider > using fetchmail to get the mail from your current mail server (at your > registrar). Fetchmail should dump your mail on your FreeBSD system and > you will be able to use mailx. That way, you avoid all the problems of > setting up a machine intended to receive mail. The requirement included "storing message non-locally", but fetchmail can "copy" messages, i. e., leave them on the server, and upon invocation, only load the unread messages). Check "man fetchmail" for the keep / nokeep keyword. The advantage of fetchmail is that it puts the received messages into the system's mail spool where the locally (or remotely) logged-in users can get it from. It's stored in the mbox format which mail and mailx can handle natively. And fetchmail can be called via cron, or interactively when needed. > The configuration to send mail from your FreeBSD/mailx machine should be > quite simple (just a few lines to tell sendmail to push your outgoing > mail to the mail server at your registrar). Depending on the registrar or the ISP, two possibilities could be considered: a) use of a mail relay - in this case, a simple addition called SmartHost to the system's sendmail configuration usually is sufficient, but it depends on the ISP to provide such a facility; or b) use the local sendmail to "forward" the messages received locally to the regular SMTP "input" of the registrar. Both constructs have advantages and disadvantages. Again, mail and mailx can be used for this approach, as they send to (or via) local sendmail per default. However, there's a 3rd option which _might_ work: c) use the local sendmail to directly send the messages to the recipients. This option often fails, especially from dynamic IPs, or from static IPs within ISP ranges that are considered "dirty" because there is some "Windows" box in the ISP's address range that permanently spams the world. Summary: This whole construct would "mimic" IMAP. In an inconvenient manner. But it would work. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jul 9 06:41:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C67D102455C; Mon, 9 Jul 2018 06:41:20 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) (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 AAD478462C; Mon, 9 Jul 2018 06:41:19 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (localhost [127.0.0.1]) by mail.cs.ait.ac.th (Postfix) with ESMTP id 2E69961F81; Mon, 9 Jul 2018 13:41:16 +0700 (+07) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.ait.ac.th; h= content-type:content-type:mime-version:message-id:date:date :in-reply-to:subject:subject:from:from:received:received :received; s=selector1; t=1531118475; x=1532932876; bh=RFf5pmX6E +wMlCuyb1UzEx2KvopfBfYeB/4peoSaOVI=; b=pJxfO4l3+4OYam8/xVFobc9UC FLkKlztvCgTFlLC2jOyPVD5Pou60Fg4M4/Ag5Xvmh8dEoq0ANTWnMx1YnaHuldDw BZR3HMMW0jdIPCMQiXtSfde3/xtK9IGOt0jda8C9Cr8YukuzudMqxtZAworqBDDn +0r+s3TNIeWmOHGc7U= X-Virus-Scanned: amavisd-new at cs.ait.ac.th Received: from mail.cs.ait.ac.th ([127.0.0.1]) by mail.cs.ait.ac.th (mail.cs.ait.ac.th [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Q977CmoiH3zl; Mon, 9 Jul 2018 13:41:15 +0700 (+07) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cs.ait.ac.th (Postfix) with ESMTPS id A46D061F82; Mon, 9 Jul 2018 13:41:15 +0700 (+07) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.15.2/8.15.2/Submit) id w696fERF048756; Mon, 9 Jul 2018 13:41:14 +0700 (ICT) (envelope-from on@banyan.cs.ait.ac.th) From: Olivier To: mayuresh@kathe.in Cc: freebsd@edvax.de, freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request In-Reply-To: (message from Mayuresh Kathe on Mon, 09 Jul 2018 06:32:50 +0000) Date: Mon, 09 Jul 2018 13:41:14 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:41:20 -0000 Mayuresh Kathe writes: > i want to have the mails on a server instance so that i can access them > from a machine other than mine via ssh. That's the FreeBSD/fetchmail machine I was takling about. That it is local to you or that you access it with SSH make little difference, the main point if using fetchmail instead of configuring a full sendmail. But it is only an idea that you may want to consider or think it is not worth it. Either way, I won't take it personally :) Best regards, Olivier From owner-freebsd-questions@freebsd.org Mon Jul 9 06:45:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92D871024FD7 for ; Mon, 9 Jul 2018 06:45:23 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay10.mail.gandi.net (relay10.mail.gandi.net [217.70.178.230]) (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 20D5784BAF for ; Mon, 9 Jul 2018 06:45:23 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.4]) (Authenticated sender: mayuresh@kathe.in) by relay10.mail.gandi.net (Postfix) with ESMTPA id EA05324000F for ; Mon, 9 Jul 2018 06:45:15 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Jul 2018 06:45:15 +0000 From: Mayuresh Kathe To: freebsd-questions@freebsd.org Subject: backspace not working with mg Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in Message-ID: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:45:23 -0000 my backspace key functions just right with 'ee' but not under "mg". the system just beeps and the cursor just sits where it was. i am a "vi" guy, but now am migrating to "mg" because the nature of work for me going forward would involve a "lisp-1" system and "mg" provides nice parentheses matching feature without the bloat i would have to tolerate if using "gnu emacs". From owner-freebsd-questions@freebsd.org Mon Jul 9 06:48:40 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FF271025586; Mon, 9 Jul 2018 06:48:40 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D702384DAE; Mon, 9 Jul 2018 06:48:39 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.4]) (Authenticated sender: mayuresh@kathe.in) by relay7-d.mail.gandi.net (Postfix) with ESMTPA id ED48920009; Mon, 9 Jul 2018 06:48:36 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Jul 2018 06:48:36 +0000 From: Mayuresh Kathe To: Olivier Cc: freebsd@edvax.de, freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: References: Message-ID: X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:48:40 -0000 On 2018-07-09 06:41 AM, Olivier wrote: > Mayuresh Kathe writes: > >> i want to have the mails on a server instance so that i can access >> them >> from a machine other than mine via ssh. > > That's the FreeBSD/fetchmail machine I was takling about. That it is > local to you or that you access it with SSH make little difference, the > main point if using fetchmail instead of configuring a full sendmail. > > But it is only an idea that you may want to consider or think it is not > worth it. Either way, I won't take it personally :) aah, it just clicked just now. will try out your approach soon. thanks olivier. :-) From owner-freebsd-questions@freebsd.org Mon Jul 9 06:52:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 913CD1025DBF for ; Mon, 9 Jul 2018 06:52:04 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFFC7851D7 for ; Mon, 9 Jul 2018 06:52:03 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue101 [212.227.15.183]) with ESMTPA (Nemesis) id 0MFcKD-1fqUQM30Q1-00EgKf; Mon, 09 Jul 2018 08:45:51 +0200 Date: Mon, 9 Jul 2018 08:45:50 +0200 From: Polytropon To: mayuresh@kathe.in Cc: Olivier , freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Message-Id: <20180709084550.00af3854.freebsd@edvax.de> In-Reply-To: References: 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-Provags-ID: V03:K1:mpKYyym6FTAlYluKg5FI4kWY+hsCEQ5+YTm1W6o51FXej9Cj8RG m64kDEZgdHDU3qQeLzMuDUPmlQF1M8HZaG9zI1n5iJ+VAyYAxiSrXUNBkQt3XLUEybeQr27 LTl63elFII/xw8hvJdSblbbpAs2wa86ND/UhDKW5KfhRThrjz6J72yRQEfPAdOi4f+e8cce IJl91eGtyCxgCe+3UP8Yg== X-UI-Out-Filterresults: notjunk:1;V01:K0:ToPAfHzOgJE=:BgbO3WANyxwr33lzUmDSXb K1GBPE/Rq3P4A8AdYumA9Fa0tanj1xW0XSnBryc6R/276uheVzd2/7IDa6cypYSCwXcsN7hBd WsFa2VYqJXBuu3RNzk3EFVohsq4EZRBtXMb5jyMIwlwxU1+UBL6RL7/wxOUPlDT4V1LbXO30w 5OuDDgbhXoZ8sp/NzLGPFdT38dXR2KU8ha4mZnU8OJ1EqkiGVXoxbtCrwHTjF+k1WLoNiolvN g+oF5E1Qoo++6IR3TumTnTPAsW/gMCxz47pfwZ4Gp/U/QNo7Edhcql7hY6FUdz9auG+Sj9j1A WOoQO+thjy3ZLjW3VSmTk3z7p/VEzKhfQvMTZ09MXxHeDALE1wipaqyPmbuoXIWFrouQvGlJK +Nzgydzlji0uF0SvcJhnJaXXKrxaLA7tZNplMoCXUBot7BYMMS3syRphqFNQJgDYfmh2lkzy6 LRE4cW+j/G0cgGgCtIz6R08dBZjM5rwiWjdO5bDT//siDQbDL4opTq9wkuOX7NhuH1AJ40sA6 9Sdln+5kBgixa89f2lWgewRTz2SFo1cAAlggzfRq25MeKgiQG8Kn4wvMeG27nj2U2rl10Nlou LTbcMhwLJF8ylfnvHBdWyGMN8K94jBoaGwkobhpt5LdIbdshxIFVOM1AZ35TpjDEUoym5Evs2 NNWUhFnrpsUfM+RJuUrDfO45UKcVZOhn76CFuczDMZTtb9m5cVRgELnaeFjAJr92zwzkKrUyt fVgTf24EG78xMv76 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 06:52:04 -0000 On Mon, 09 Jul 2018 06:32:50 +0000, Mayuresh Kathe wrote: > On 2018-07-09 05:40 AM, Olivier wrote: > > Mayuresh Kathe writes: > > > >> my goals are very basic and hence quite simple. > >> i should be able to log into the freebsd instance as my username > >> which would be the same as my email address (mayuresh@kathe.in) > >> and use mailx to go through my emails. > >> i don't need imap nor webmail. > >> i know it must be a simple sendmail setup, but frankly, i'm not > >> capable enough to understand the in-and-out of sendmail to be > >> able to configure it to my requirement. > > > > If your needs are really limited to what you describe, you may consider > > using fetchmail to get the mail from your current mail server (at your > > registrar). Fetchmail should dump your mail on your FreeBSD system and > > you will be able to use mailx. That way, you avoid all the problems of > > setting up a machine intended to receive mail. > > > > The configuration to send mail from your FreeBSD/mailx machine should > > be > > quite simple (just a few lines to tell sendmail to push your outgoing > > mail to the mail server at your registrar). > > > > If you really inted to set-up your onw complete mail system, goodluck, > > because it is a lot of work to do :) > > my needs are indeed limited to what i have described, on reading it, you > would notice that i do not wish to have my mails be stored locally. > i want to have the mails on a server instance so that i can access them > from a machine other than mine via ssh. That doesn't imply you have to run your own mail _server_. You can construct a toolset to remotely manipulate the messages stored at your registrar / provider and put that on a virtual server (or a server of your own) to connect to. See my previous message for which tools can be used. > i know that setting up a complete mail system would be a lot of work, > and > that's why i have tagged my emails with the "commercial" tag as well as > mentioned in my first mail in this thread that i wouldn't mind paying > the fees required by someone who can build me that sendmail > configuration. You probably don't need a mail server. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jul 9 08:23:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A942D102ECC6 for ; Mon, 9 Jul 2018 08:23:00 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 265508A5D8 for ; Mon, 9 Jul 2018 08:22:59 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1531124580; x=1533716580; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=cl6zzd2Mxf0w59e8AycLRZmtkDSKzbuHCBOZ9Rt0JtU=; b=e1anaBG2RExm93tc+ps6kxnBiJALBxMt0RjBkU6IL+uAyG1ubku2UI+qnQLgtFUlGHVqVnbo4RA30dVNadgseZRBvUVH4jUfs3ZiRYCOoHDjBNDdQDHz1Bve+POpnVfIWMsRAFg4ocAQQtlkfeo2pxbmWB6Z2qKmTCzANLKUbdw= X-Thread-Info: NDI1MC4xMi4xOGYwMDAwMDFmZGRlMDUuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r3.us-east.aws.in.socketlabs.com (r3.us-east.aws.in.socketlabs.com [54.165.229.15]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 9 Jul 2018 03:22:44 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r3.us-east.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 9 Jul 2018 03:22:43 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fcQVO-0008rK-AO; Mon, 09 Jul 2018 07:22:42 +0000 Date: Mon, 9 Jul 2018 08:22:42 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: mayuresh@kathe.in Subject: Re: [commercial] sendmail setup request Message-Id: <20180709082242.bb41ad9ead4419c94e9769e8@sohara.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 08:23:01 -0000 On Mon, 09 Jul 2018 06:32:50 +0000 Mayuresh Kathe wrote: > my needs are indeed limited to what i have described, on reading it, you > would notice that i do not wish to have my mails be stored locally. > i want to have the mails on a server instance so that i can access them > from a machine other than mine via ssh. This is somewhat at odds with wanting to use mailx to read your mail because mailx can only handle mail that is local to the machine running mailx, it reads and writes files rather than talking to a service, it does talk to a local sendmail instance to send mail though. What you could do is get a BSD VPS and use fetchmail on that to collect your mail from kathe.in and do a minimal outgoing only configuration of sendmail to use the kathe.in SMTP server as a smarthost for which you should find plenty of tutorial material. Then you can access your mail by logging into your VPS and *only* by logging in to your VPS, miss a payment and your mail is gone forever. The disadvantage of non-local storage is that you don't own that storage. Setting up a cron job at home to rsync your VPS home directory to your own machine would be a very good thing to do if you go this way. An alternative is to use fetchmail on your local machine and rsync your mail to the VPS for reading, that way you own the master copy. What I would do (and do) is keep my mail locally (I run an imap server but fetchmail works too) and set up a VPN so that I could access my own network remotely[1]. There are a good many tutorials on setting up openvpn to provide a VPN service. Alternatively just expose a listening ssh socket to the world (disable login by password in ssh if you do that) which is what I did before I got round to setting up openvpn. [1] This assumes that you have an always-on system, decent network connectivity, a public IP address (or an IPV6 tunnel) and control over your firewall. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Mon Jul 9 12:08:58 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 462E41044DA3 for ; Mon, 9 Jul 2018 12:08:58 +0000 (UTC) (envelope-from jontheil@gmail.com) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD9D494675 for ; Mon, 9 Jul 2018 12:08:57 +0000 (UTC) (envelope-from jontheil@gmail.com) Received: by mail-vk0-x233.google.com with SMTP id t4-v6so10191883vke.9 for ; Mon, 09 Jul 2018 05:08:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=GXNN6E3vBRe682IGOeQT3W3X1hfWO6sEthMyW+ipKv0=; b=GyFluoe4fmCktZaQZEixDx0oTp6t31Etdz+ZFaNSzyUMvLkdDLq7Z/+ffToI+jMR4L W5tiCxLxJgaX2jClJZePA/dgdUcRBzGgAQosaODrsRHv18P1nKnckh7VoWWgbpmnrDq8 jq3uMwg3H5AVVSLtEm5j5aigbdCzLa9VoLxIeYYUJ92DkM+mIR4fcdlYpfCpwMW7V5bc jNKNGU/Keyejqwkd6aojG+ZCK1myhHWGfvxYMskXueJ1xw9BGbpd/u3GpkKItF7FkCfB l9VHD37UZjEyUu2z0hdpyfB9M5QsOI65C0swYha1Nq5daDto8HPc5xNxqwVeDBExjJTo o5vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=GXNN6E3vBRe682IGOeQT3W3X1hfWO6sEthMyW+ipKv0=; b=aBrhNP0fa146vBDvq1SO+DtHrKYhusWYjMl+stuude6OsMS4HW+qUirZyyHyppw7sJ eDj2nx664vYrq3VGt5s3eH6dpIuUCZtEkx5ZTpfeWwgFpoeURGjzz1xASntohJ5kGNgU Af6M/UupTFhCLd2XKVt4m/GZN+BZ2Rb0+aC2I9rZWF1Y7LmWEeSa7attXiT5ru8b4c0T uR/47edB8dZr/hqFZBmsFIHBFFk7SVsLsIIRUQvlqMRhbB5qfbXqSsAjEvXhE9NKA4za ls3YqI8IpoBma7TCGazdFmQkihtXs6PA9huBDbMesei1XkCWF6QaWNfsgN84JJbJ1RW1 W4GQ== X-Gm-Message-State: APt69E1yv1v9dow0lE0jD3OgNKPzMqUSw1309AnBTR4BAfhhQPD06WJl 4PBlz0JHL9k90LLBjRLPgMG1j1CNRixavz73vTo= X-Google-Smtp-Source: AAOMgpfQxncXk7/aPtdZs2w8d8HjhaoV52FoOIrmTsov4IpLIhDlgwzxwmE+dhWsZjVhqD8+8O63DXM9KnABzjVDrsE= X-Received: by 2002:a1f:4b86:: with SMTP id y128-v6mr10659071vka.146.1531138136866; Mon, 09 Jul 2018 05:08:56 -0700 (PDT) MIME-Version: 1.0 From: Jon Theil Nielsen Date: Mon, 9 Jul 2018 14:08:46 +0200 Message-ID: Subject: Upgrade messed up - cannot make buildworld from 11.0-RELEASE To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 12:08:58 -0000 Somehow I messed up an upgrade from 11.1-RELEASE to 11.2-RELEASE. I can only boot into an old 11.0 kernel in single user mode. uname -a: FreeBSD 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017 I'm not able to run make buildworld from a 11.1-RELEASE source tree. The first error was a missing include/__undef_min_max which I had to copy manyally: cp /usr/src/contrib/libc++/include/__undef_min_max /usr/include/c++/v1/ Now I'm getting new errors like /usr/include/c++/v1/__split_buffer:13:1: error: unknown type name '_LIBCPP_PUSH_MACROS' and sr/include/c++/v1/__split_buffer:17:1: error: expected unqualified-id. Can anyone suggest a solution? Thanks in advance Jon Theil Nielsen -- Jon Theil Nielsen From owner-freebsd-questions@freebsd.org Mon Jul 9 15:30:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F28CC10309A7 for ; Mon, 9 Jul 2018 15:30:47 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 83C5D7516B for ; Mon, 9 Jul 2018 15:30:47 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id AB240625EE for ; Mon, 9 Jul 2018 11:30:46 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEfxr2fsmO0S for ; Mon, 9 Jul 2018 11:30:42 -0400 (EDT) Received: from inet17.hamilton.harte-lyne.ca (inet17.hamilton.harte-lyne.ca [216.185.71.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Mon, 9 Jul 2018 11:30:42 -0400 (EDT) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet17.hamilton.harte-lyne.ca (Postfix) with ESMTPS id 70798997C2 for ; Mon, 9 Jul 2018 11:22:22 -0400 (EDT) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 3D1F0B94C for ; Mon, 9 Jul 2018 11:22:22 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id ylhUu6roNAlR for ; Mon, 9 Jul 2018 11:22:06 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 7BB4FB945 for ; Mon, 9 Jul 2018 11:22:06 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Mon, 9 Jul 2018 11:22:06 -0400 Message-ID: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> Date: Mon, 9 Jul 2018 11:22:06 -0400 Subject: FreeBSD-11, Amavisd-New Spamassassin and Pyzor From: "James B. Byrne" To: freebsd-questions@harte-lyne.ca Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 15:30:48 -0000 I am not having any success in discovering any documentation on how to get pyzor set up and running on FreeBSd. I cannot even find documentation as to where the configuration bits go. There is no man page that i can locate and no details as to what goes into a configuration file. Pyzor discover is no longer a command and the help messages do not say anything much in the way of guidance. On CentOS all the supplemental DCC and Pyzor config bits went into SA/local.cf but that is no long a valid option given the error messages I receive. I have razor-agents installed. I have setup razor using razor-admin. But I have no idea on how to proceed for this point. Has anyone here have a recipe for configuration? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Mon Jul 9 17:39:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D9DF103ED92 for ; Mon, 9 Jul 2018 17:39:01 +0000 (UTC) (envelope-from peter@boosten.org) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9EC797B307 for ; Mon, 9 Jul 2018 17:39:00 +0000 (UTC) (envelope-from peter@boosten.org) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 5C06E62598 for ; Mon, 9 Jul 2018 13:38:59 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFCOZE4xXPk6 for ; Mon, 9 Jul 2018 13:38:57 -0400 (EDT) Received: from inet17.hamilton.harte-lyne.ca (inet17.hamilton.harte-lyne.ca [216.185.71.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Mon, 9 Jul 2018 13:38:57 -0400 (EDT) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet17.hamilton.harte-lyne.ca (Postfix) with ESMTPS id 3CB3098C30; Mon, 9 Jul 2018 13:38:57 -0400 (EDT) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id E2870BF37; Mon, 9 Jul 2018 13:38:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id dMh6mr8-gbOz; Mon, 9 Jul 2018 13:38:41 -0400 (EDT) X-Greylist: delayed 1103 seconds by postgrey-1.37 at mx32.harte-lyne.ca; Mon, 09 Jul 2018 13:38:41 EDT Received-SPF: Temperror (mailfrom) identity=mailfrom; client-ip=212.54.34.164; helo=smtpq1.mnd.mail.iss.as9143.net; envelope-from=peter@boosten.org; receiver= Received: from smtpq1.mnd.mail.iss.as9143.net (smtpq1.mnd.mail.iss.as9143.net [212.54.34.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPS; Mon, 9 Jul 2018 13:38:40 -0400 (EDT) Received: from [212.54.34.116] (helo=smtp8.mnd.mail.iss.as9143.net) by smtpq1.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fcZpd-0005b5-9E; Mon, 09 Jul 2018 19:20:13 +0200 Received: from 5419f71f.cm-5-2d.dynamic.ziggo.nl ([84.25.247.31] helo=ra.boosten.org) by smtp8.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fcZpd-00027z-7i; Mon, 09 Jul 2018 19:20:13 +0200 Received: from ra.egypt.nl (localhost.egypt.nl [127.0.0.1]) by ra.boosten.org (Postfix) with ESMTP id 4778A3432F73; Mon, 9 Jul 2018 19:20:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at boosten.org Received: from ra.boosten.org ([127.0.0.1]) by ra.egypt.nl (ra.egypt.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyYHTrA11UhC; Mon, 9 Jul 2018 19:20:03 +0200 (CEST) Received: from www.boosten.org (ra.egypt.nl [192.168.13.15]) by ra.boosten.org (Postfix) with ESMTPA id B8D593432F68; Mon, 9 Jul 2018 19:20:03 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 09 Jul 2018 19:20:01 +0200 From: Peter Boosten To: byrnejb@harte-lyne.ca Cc: freebsd-questions@harte-lyne.ca, owner-freebsd-questions@freebsd.org Subject: Re: FreeBSD-11, Amavisd-New Spamassassin and Pyzor Reply-To: peter@boosten.org Mail-Reply-To: peter@boosten.org In-Reply-To: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> References: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> Message-ID: <77694e205a706f0e4517b5bf2058bc86@boosten.org> X-Sender: peter@boosten.org User-Agent: Roundcube Webmail/1.3.6 X-SourceIP: 84.25.247.31 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=A4vYwJeG c=1 sm=1 tr=0 a=JWBJsaPp29SgP5DpYRBqZw==:17 a=IkcTkHD0fZMA:10 a=R9QF1RCXAYgA:10 a=aVHVuTR-Lm0OhpR7U1gA:9 a=QEXdDO2ut3YA:10 none X-Ziggo-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 17:39:01 -0000 James B. Byrne via freebsd-questions schreef op 2018-07-09 17:22: > I am not having any success in discovering any documentation on how to > get pyzor set up and running on FreeBSd. I cannot even find > documentation as to where the configuration bits go. There is no man > page that i can locate and no details as to what goes into a > configuration file. Pyzor discover is no longer a command and the > help messages do not say anything much in the way of guidance. > > On CentOS all the supplemental DCC and Pyzor config bits went into > SA/local.cf but that is no long a valid option given the error > messages I receive. > > > I have razor-agents installed. > > I have setup razor using razor-admin. > > But I have no idea on how to proceed for this point. > > Has anyone here have a recipe for configuration? > Your post triggered me to have a look at my configuration. When I set it up back in 2014, the configuration for pyzor and razor was in the home directory of amavis, which in my case is in /var/amavis. I'm not really sure if these configurations are touched, but I can see some movement in the razor directory (/var/amavis/.razor) Adding the plugins to SA is done in /usr/local/etc/mail/spamassassin/v310.pre (see the sample file), if you use the ports, that is. -- Met vriendelijke groet / Kind regards / Mit freundlichem Gruß Peter Boosten From owner-freebsd-questions@freebsd.org Mon Jul 9 18:01:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E8A810413E3 for ; Mon, 9 Jul 2018 18:01:51 +0000 (UTC) (envelope-from peter@boosten.org) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D6ED47C71B for ; Mon, 9 Jul 2018 18:01:50 +0000 (UTC) (envelope-from peter@boosten.org) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 158AD62598 for ; Mon, 9 Jul 2018 14:01:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7X3aY1T6sMX for ; Mon, 9 Jul 2018 14:01:47 -0400 (EDT) Received: from inet17.hamilton.harte-lyne.ca (inet17.hamilton.harte-lyne.ca [216.185.71.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Mon, 9 Jul 2018 14:01:47 -0400 (EDT) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet17.hamilton.harte-lyne.ca (Postfix) with ESMTPS id D58099CF06; Mon, 9 Jul 2018 14:01:47 -0400 (EDT) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id DAA39BFD9; Mon, 9 Jul 2018 14:01:47 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id Zgab-Zu8mflQ; Mon, 9 Jul 2018 14:01:32 -0400 (EDT) X-Greylist: delayed 943 seconds by postgrey-1.37 at mx32.harte-lyne.ca; Mon, 09 Jul 2018 14:01:32 EDT Received-SPF: Temperror (mailfrom) identity=mailfrom; client-ip=212.54.42.168; helo=smtpq5.tb.mail.iss.as9143.net; envelope-from=peter@boosten.org; receiver= Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net [212.54.42.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPS; Mon, 9 Jul 2018 14:01:31 -0400 (EDT) Received: from [212.54.42.134] (helo=smtp10.tb.mail.iss.as9143.net) by smtpq5.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fcaEM-0005w4-8n; Mon, 09 Jul 2018 19:45:46 +0200 Received: from 5419f71f.cm-5-2d.dynamic.ziggo.nl ([84.25.247.31] helo=ra.boosten.org) by smtp10.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fcaEM-0001CB-7B; Mon, 09 Jul 2018 19:45:46 +0200 Received: from ra.egypt.nl (localhost.egypt.nl [127.0.0.1]) by ra.boosten.org (Postfix) with ESMTP id 6864C3432F73; Mon, 9 Jul 2018 19:45:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at boosten.org Received: from ra.boosten.org ([127.0.0.1]) by ra.egypt.nl (ra.egypt.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cB9KcnFrA-hG; Mon, 9 Jul 2018 19:45:42 +0200 (CEST) Received: from www.boosten.org (ra.egypt.nl [192.168.13.15]) by ra.boosten.org (Postfix) with ESMTPA id B32D43432F68; Mon, 9 Jul 2018 19:45:42 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 09 Jul 2018 19:45:40 +0200 From: Peter Boosten To: byrnejb@harte-lyne.ca Cc: freebsd-questions@harte-lyne.ca, owner-freebsd-questions@freebsd.org Subject: Re: FreeBSD-11, Amavisd-New Spamassassin and Pyzor In-Reply-To: <77694e205a706f0e4517b5bf2058bc86@boosten.org> References: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> <77694e205a706f0e4517b5bf2058bc86@boosten.org> Message-ID: <594f1e8cc6680fc6076ac1cbf35852c5@boosten.org> X-Sender: peter@boosten.org User-Agent: Roundcube Webmail/1.3.6 X-SourceIP: 84.25.247.31 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=YOArNiOx c=1 sm=1 tr=0 a=JWBJsaPp29SgP5DpYRBqZw==:17 a=IkcTkHD0fZMA:10 a=R9QF1RCXAYgA:10 a=n66oMkCmAAAA:8 a=RHfGz9Sy3Qe2FNlxTgEA:9 a=QEXdDO2ut3YA:10 a=vzydz-AuC2c9_yG09K8H:22 none X-Ziggo-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 18:01:51 -0000 Peter Boosten schreef op 2018-07-09 19:20: > James B. Byrne via freebsd-questions schreef op 2018-07-09 17:22: >> I am not having any success in discovering any documentation on how to >> get pyzor set up and running on FreeBSd. I cannot even find >> documentation as to where the configuration bits go. There is no man >> page that i can locate and no details as to what goes into a >> configuration file. Pyzor discover is no longer a command and the >> help messages do not say anything much in the way of guidance. >> >> On CentOS all the supplemental DCC and Pyzor config bits went into >> SA/local.cf but that is no long a valid option given the error >> messages I receive. >> >> >> I have razor-agents installed. >> >> I have setup razor using razor-admin. >> >> But I have no idea on how to proceed for this point. >> >> Has anyone here have a recipe for configuration? >> > > Your post triggered me to have a look at my configuration. When I set > it up back in 2014, the configuration for pyzor and razor was in the > home directory of amavis, which in my case is in /var/amavis. I'm not > really sure if these configurations are touched, but I can see some > movement in the razor directory (/var/amavis/.razor) > > Adding the plugins to SA is done in > /usr/local/etc/mail/spamassassin/v310.pre (see the sample file), if > you use the ports, that is. You might want to have a look at /usr/local/bin/pyzor, and of course on pyzor.org. When you're not running your own pyzor server, you don't actually have to configure anything. -- Met vriendelijke groet / Kind regards / Mit freundlichem Gruß Peter Boosten From owner-freebsd-questions@freebsd.org Mon Jul 9 19:49:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACF311027A80 for ; Mon, 9 Jul 2018 19:49:49 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A08282FBD for ; Mon, 9 Jul 2018 19:49:49 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 1482162598 for ; Mon, 9 Jul 2018 15:49:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSBuomDuf2An for ; Mon, 9 Jul 2018 15:49:44 -0400 (EDT) Received: from inet17.hamilton.harte-lyne.ca (inet17.hamilton.harte-lyne.ca [216.185.71.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Mon, 9 Jul 2018 15:49:43 -0400 (EDT) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet17.hamilton.harte-lyne.ca (Postfix) with ESMTPS id 15DCA9ED36 for ; Mon, 9 Jul 2018 15:49:44 -0400 (EDT) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 51D6CC912 for ; Mon, 9 Jul 2018 15:49:43 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id 2QLvfNLAiLZh; Mon, 9 Jul 2018 15:49:27 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 6B51CC909; Mon, 9 Jul 2018 15:49:27 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Mon, 9 Jul 2018 15:49:27 -0400 Message-ID: In-Reply-To: <594f1e8cc6680fc6076ac1cbf35852c5@boosten.org> References: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> <77694e205a706f0e4517b5bf2058bc86@boosten.org> <594f1e8cc6680fc6076ac1cbf35852c5@boosten.org> Date: Mon, 9 Jul 2018 15:49:27 -0400 Subject: Re: FreeBSD-11, Amavisd-New Spamassassin and Pyzor From: "James B. Byrne" To: "Peter Boosten" Cc: freebsd-questions@harte-lyne.ca Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 19:49:49 -0000 On Mon, July 9, 2018 13:45, Peter Boosten wrote: > Peter Boosten schreef op 2018-07-09 19:20: >> James B. Byrne via freebsd-questions schreef op 2018-07-09 17:22: >>> I am not having any success in discovering any documentation on how >>> to get pyzor set up and running on FreeBSd. I cannot even find >>> documentation as to where the configuration bits go. > > You might want to have a look at /usr/local/bin/pyzor, and of course > on pyzor.org. When you're not running your own pyzor server, you don't > actually have to configure anything. > As it turns out, there is a fair bit of configuration necessary to get DCC, pyzor and Razor2 working with Amavisd-new and Postfix. None of which is particularly well documented. What documentation exists is found in the form of tutorials. These are often out-of-date; or assume too much prior knowledge; or are specific to a different OS to a degree that makes using the examples fraught with hazards. For FreeBSD one begins, after installing the requisite packages, by registering ones instance using razor-admin. Then, to actually get things to work, one must either edit Spamassassin's v310.pre file and uncomment the loadplugins instructions for the necessary bits or add those instructions to the top of local.cf: # DCC is disabled here because it is not open source. See the DCC # license for more details. # loadplugin Mail::SpamAssassin::Plugin::DCC # Pyzor - perform Pyzor message checks. # loadplugin Mail::SpamAssassin::Plugin::Pyzor # Razor2 - perform Razor2 message checks. # loadplugin Mail::SpamAssassin::Plugin::Razor2 Then one has to enable these things in local.cf itself. ifplugin Mail::SpamAssassin::Plugin::Razor2 use_razor2 1 endif ifplugin Mail::SpamAssassin::Plugin::DCC use_dcc 1 endif ifplugin Mail::SpamAssassin::Plugin::Pyzor use_pyzor 1 pyzor_timeout 30 pyzor_path /usr/local/bin/pyzord # pyzor_options --homedir /usr/local/etc/mail/spamassassin/pyzor endif I am still uncertain whether or not I have actually installed pyzor and razor2 correctly. But after these changes avavisd and spamassassin seems to be working, at least to some degree at the moment. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Mon Jul 9 20:14:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5446C102A489 for ; Mon, 9 Jul 2018 20:14:44 +0000 (UTC) (envelope-from eduardo.lemosdesa@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C44818440B for ; Mon, 9 Jul 2018 20:14:43 +0000 (UTC) (envelope-from eduardo.lemosdesa@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id j8-v6so16297080lfb.4 for ; Mon, 09 Jul 2018 13:14:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=1jZaPeAnws/v1BgCW+Tsh+F1FZZqqJgEAulqGHcEqIc=; b=BPy4wkQ3br+Tm1FmreV+9RQOdmgV3Ku4bJo4vnwrs/pY/e6KA39iCjq1w2aN7kXC9Z B7FG+tWkAxq+6MoDqHxQE/qpLm3na/9N7QWSQamoLbqJ5MrwU70vO3xkB/br3efiC+kA tLTZ56gRncGQdm7/TfjK0Nbta8nKqJrSPo2PUeg8RFQMHYiUeN9pHlztJj4NnEgWriq7 nhy2Z945uDbJWd0TB9YI/swkjFmGUUPPc0rEcHVI4Td/1wuS9EQ3rKTBGPO+2i8m+OwY v5HDIHPWxtj0p1l7V8D+Cm3LkrmwPqezwIRFumNfCj8qAEIn83Eax+QADNPHeqXlCBMX T8TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1jZaPeAnws/v1BgCW+Tsh+F1FZZqqJgEAulqGHcEqIc=; b=VMrv/SfhsXQuxwuY6XN90hwnjAK0UwfPTBCh4voZT71LZzJ25FoNqIXBZkd7ErYmDB c37uvWJKLRKFp+96QXrdDRT5amjHJ4wHxWKgkYyyAS4V4HWrawjlllqdXBTCd91hfxWu c/LV4LjypReVKGmhUIC74w8QOWKHaiD2ZG0r7lfL64PnCqc1u2KMQnUYHR/WU3lR87XQ REw2op3tgq75CG4PWFiXRmC+eLAqpw0gOmX1bLbkqYdtFCwBBz+B+RqhHwNc6FEotJ3a YpjBAnH+z6bEas3JggE1O9apep5XXrW9GKBBp+LxS+3yQHJCS/6XnhEW2T+6S61xefUx nlTg== X-Gm-Message-State: APt69E2+26K0uq+UfPS9TeHcirIwIqWNj6FdEAiaOcm/F0IkPu2witNv avVlJ4yz2gvj7MGy/aFG1Vbs6giOfUnLQABArFbr3A== X-Google-Smtp-Source: AAOMgpcnkc4mqI0uq4ZNAEkTjEYKkETlZ2ir1yxDW8GvAKsqo0eBdjc7GHIva4H919+TifFFde6Q8REGgljqfc7Gsho= X-Received: by 2002:a19:c1c4:: with SMTP id r187-v6mr628856lff.90.1531167280813; Mon, 09 Jul 2018 13:14:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eduardo Lemos de Sa Date: Mon, 9 Jul 2018 17:14:26 -0300 Message-ID: Subject: Re: Upgrade messed up - cannot make buildworld from 11.0-RELEASE To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 20:14:44 -0000 Dear Jon On Mon, Jul 9, 2018 at 9:11 AM Jon Theil Nielsen wrote= : > Somehow I messed up an upgrade from 11.1-RELEASE to 11.2-RELEASE. > > I can only boot into an old 11.0 kernel in single user mode. uname -a: > > FreeBSD 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 > UTC 2017 > > I'm not able to run make buildworld from a 11.1-RELEASE source tree. The > first error was a missing include/__undef_min_max which I had to copy > manyally: > > cp /usr/src/contrib/libc++/include/__undef_min_max /usr/include/c++/v1/ > > Now I'm getting new errors like > > /usr/include/c++/v1/__split_buffer:13:1: error: unknown type name > '_LIBCPP_PUSH_MACROS' > > and > > sr/include/c++/v1/__split_buffer:17:1: error: expected unqualified-id. > > Can anyone suggest a solution? > > Thanks in advance > > Jon Theil Nielsen > -- > Jon Theil Nielsen > > I am sorry to cannot help you: I experienced the same problems you described: I tried to upgrade from 11-Release-p11 to 11.2 doing: svn co svn://svn.FreeBSD.org/base/releng/11.2 /usr/src > & system-11.2.log or svn co svn://svn.FreeBSD.org/base/stable/11 /usr/src > & system-stable.log or svnlite up /usr/src After 3 tries, I could have the system compiled (if I use maje -j 6 directive to compile, I got error: this worked only in a serial 1-proc process) but there was a kernel panic followed of cycling reboot process. I work around removing the whole /usr/src and /usr/obj, recreating them, and fetching 11.1 sources: svnlite up /usr/src I did not need to start in a single-user mode: I just pressed 5 (to load a non-default kernel) and chose old-kernel. Booting using old-kernel (11.1) I could rebuild the userland. After this, I gave up to run 11.2-RELEASE. In time, my uname -a returns: FreeBSD matata 11.1-RELEASE-p11 FreeBSD 11.1-RELEASE-p11 #0 r335864: Mon Jul 2 14:44:51 -03 2018 root@matata:/usr/obj/usr/src/sys/GENERIC amd6= 4 I was thinking that this problem happened only with me, but now I see other people that can have the situition Cheers Eduardo --=20 Eduardo Lemos de Sa Professor Titular Dep. Quimica da Universidade Federal do Paran=C3=A1 fone: +55(41)3361-3300 fax: +55(41)3361-3186 From owner-freebsd-questions@freebsd.org Mon Jul 9 20:28:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D71E102BA9C for ; Mon, 9 Jul 2018 20:28:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CCF484FE2 for ; Mon, 9 Jul 2018 20:28:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0MYLUv-1fXvmj3Ujh-00VAHG; Mon, 09 Jul 2018 22:28:24 +0200 Date: Mon, 9 Jul 2018 22:28:24 +0200 From: Polytropon To: mayuresh@kathe.in Cc: freebsd-questions@freebsd.org Subject: Re: backspace not working with mg Message-Id: <20180709222824.74761578.freebsd@edvax.de> In-Reply-To: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> References: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> 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-Provags-ID: V03:K1:I0YeWBnqFVQEIUdsGdGt4PPN6i/1ZPKviGO1oXY/3ZFlg/kS7cQ RGr0va+a+5+eRBnDvadLZqJJkMrYiJfpxqcVZcAF0rcrjVjxDs1ngZbRwvBydAIxrPxIJiV K1gKN4MhwckoShX2qtrNSRkLacquGrDes9Wk8D9kMTqa89K9lJ5mepU55zvUW3JYyTKEY6z zZh+IFfjSSliLSOsZAo0Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:kkBN57cl+9Q=:ARRChIhp1qxJnoXjWHOq2z fHHdqQ5lst4wjEupLEq6+7ES+UVcsPQaah/GmCvgWJJ8wKIA6/URdkJ7E/Ohxa5t50o4sWi7t qJ0qQshFadGD3/f246RhAQeiotfV7JT9k24QL7/6jm8N2jauIieKnbkFj7Rx5OFtEFlZqMYwI iXT82Qz9cCWV7AhTbCShIzEENykotNeMnVr5ILKtTRQvM2x9uDbc88eOunzQa47Tr126MEIe4 Z/uMNgrx5+yPlKZJeYAUqmNcBqq3CFb9NnlUbCmd6s/datxF8WjXZULJ0hZB8Kf94NwGPSbbZ mTsdI4jx6XEfYPa+5pc0MwsjUpGvPUBGPTDnGGYtz35z1tXelMfm2liWwXol5khZQyXu+61i+ vXDCWQbvArcjA1K7DaJED3kC8Lz349zqMkn1paeXzP62kP66pzcLbBkkwuvXuwO2As+uoUeM+ dTwQVs/aX4wJMnuCqkTeUhCEozT50tYRPc055XJbhtDMlq7+JwJYxvfIGmPzOziciNNwYiLrw k89x9x6QITSbVStJ/zd9va5L9gWq9SsBLVf4jXhR0zRVKxu+jJJXwFhdypLIRSQjuaAHvTh6w SaLpv84IikidOLvnat17TMHxoyxvt99ObUEb+IZkZAGFp2NhdLadYyMltKLkkkcde8am9sz22 bcesSHtIDBG/dnQRD7cjRcwKE4I3EOzlj0GDG9xcb9+zcTvkww9zoWTAe6nwlPqLVdzOmv4/6 hjFqrZxFCn+myl17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 20:28:28 -0000 On Mon, 09 Jul 2018 06:45:15 +0000, Mayuresh Kathe wrote: > my backspace key functions just right with 'ee' but not under "mg". > the system just beeps and the cursor just sits where it was. > i am a "vi" guy, but now am migrating to "mg" because the nature > of work for me going forward would involve a "lisp-1" system and > "mg" provides nice parentheses matching feature without the bloat > i would have to tolerate if using "gnu emacs". If parentheses matching for lips is your goal, and you're already a "vi person", why not use vim? It has support for syntax highlighting and will clearly show you the parentheses counterpart. You can also use gvim if you wish to run it on X. Both programs share the same configuration, so it doesn't matter if you're using it locally as gvim on X, or vim via SSH. And you don't have to learn emacs. ;-) Regarding a non-working backspace key: First check if it sends the correct code, it should be ASCII 8, or ^H (Ctrl+H). That is the default on FreeBSD, of course. The command % stty -a will tell you the currently active configuration for the control characters, look for "erase". Then of course check your mg configuration if it overrides something. I don't think this is the default, but it could still be. For testing, load a file with mg, and press Ctrl+H instead of backspace. Does it do what it is supposed to do? Also check your terminal configuration. While xterm usually applies the FreeBSD OS defaults, terminals primarily for use with Linux (and therefore integrated in a voluminous desktop environment) may be configured differently. So if the terminal emulator you're using can be configured, check its options as well. PS. Please don't assume I'm an "anti-emacs person". In fact, I'm a "vi person" being too stupid to understand the magic and the power of emacs, that's why the decision. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jul 9 21:04:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 368DC102FC5B for ; Mon, 9 Jul 2018 21:04:12 +0000 (UTC) (envelope-from thomas@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id AE6F086F92 for ; Mon, 9 Jul 2018 21:04:11 +0000 (UTC) (envelope-from thomas@bsdunix.ch) Received: from [172.15.10.102] (dynamic-82-220-88-115.ftth.solnet.ch [82.220.88.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.bsdunix.ch (Postfix) with ESMTPSA id E62BB1C53C for ; Mon, 9 Jul 2018 21:04:00 +0000 (UTC) To: freebsd-questions@freebsd.org From: freebsdlists@bsdunix.ch Subject: can't import raidz1 zfs pool Message-ID: <5cd39807-aeb8-ddb1-86a3-c3df5f9fd25c@bsdunix.ch> Date: Mon, 9 Jul 2018 23:04:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_50, RDNS_NONE, TW_TX, TW_ZF autolearn=no autolearn_force=no X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on conversation.bsdunix.ch X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 21:04:12 -0000 Hi, I can't import an exported raidz1 pool. The export was done with Freebsd 11.2 and the import too. One disk (ada3 aka /dev/diskid/DISK-ZA18YNHS) was marked as unavailable during the export. "zool import storage" command: pool: storage id: 9514877379131531055 state: FAULTED status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: http://illumos.org/msg/ZFS-8000-3C config: storage FAULTED corrupted data raidz1-0 FAULTED corrupted data 1800501377521064476 UNAVAIL cannot open diskid/DISK-ZA16XZW9 ONLINE diskid/DISK-ZA18JE4E ONLINE diskid/DISK-ZA18Z0L1 ONLINE Disk 1800501377521064476 is ada3 aka /dev/diskid/DISK-ZA18YNH. zool import -f storage fails too. internal error: Unknown Error 122 Abort (core dumped) zdb -Fe storage gives: Configuration for import: vdev_children: 1 version: 5000 pool_guid: 9514877379131531055 name: 'storage' state: 1 hostid: 2232729950 hostname: 'my.machine.com' vdev_tree: type: 'root' id: 0 guid: 9514877379131531055 children[0]: type: 'raidz' id: 0 guid: 12743926568081883225 nparity: 1 metaslab_array: 40 metaslab_shift: 38 ashift: 12 asize: 32006233653248 is_log: 0 create_txg: 4 children[0]: type: 'disk' id: 0 guid: 1800501377521064476 path: '/dev/diskid/DISK-ZA18YNHS' whole_disk: 1 DTL: 58 create_txg: 4 children[1]: type: 'disk' id: 1 guid: 3017550635642283205 whole_disk: 1 DTL: 57 create_txg: 4 path: '/dev/diskid/DISK-ZA16XZW9' children[2]: type: 'disk' id: 2 guid: 1070420248480515562 whole_disk: 1 DTL: 56 create_txg: 4 path: '/dev/diskid/DISK-ZA18JE4E' children[3]: type: 'disk' id: 3 guid: 1151953985479393249 whole_disk: 1 DTL: 55 create_txg: 4 path: '/dev/diskid/DISK-ZA18Z0L1' ZFS_DBGMSG(zdb): spa_import: importing storage, max_txg=-1 (RECOVERY MODE) spa_load(storage, config trusted): LOADING disk vdev '/dev/diskid/DISK-ZA18YNHS': vdev_validate: failed reading config disk vdev '/dev/diskid/DISK-ZA16XZW9': best uberblock found for spa storage. txg 3652256 spa_load(storage, config untrusted): using uberblock with txg=3652256 vdev_copy_path: vdev 3017550635642283205: path changed from '/dev/ada2' to '/dev/diskid/DISK-ZA16XZW9' vdev_copy_path: vdev 1070420248480515562: path changed from '/dev/ada3' to '/dev/diskid/DISK-ZA18JE4E' disk vdev '/dev/diskid/DISK-ZA18YNHS': vdev_validate: failed reading config raidz-0 vdev (guid 12743926568081883225): metaslab_init failed [error=122] raidz-0 vdev (guid 12743926568081883225): vdev_load: metaslab_init failed [error=122] spa_load(storage, config trusted): FAILED: vdev_load failed [error=122] spa_load(storage, config trusted): UNLOADING spa_load(storage, config trusted): spa_load_retry: rewind, max txg: 3652255 spa_load(storage, config trusted): LOADING disk vdev '/dev/diskid/DISK-ZA18YNHS': vdev_validate: failed reading config disk vdev '/dev/diskid/DISK-ZA16XZW9': best uberblock found for spa storage. txg 3652253 disk vdev '/dev/diskid/DISK-ZA16XZW9': failed to read label config spa_load(storage, config untrusted): using uberblock with txg=3652253 spa_load(storage, config untrusted): FAILED: label config unavailable spa_load(storage, config untrusted): UNLOADING Any idea if this can be fixed and how? 3 out of 4 disk the raidz1 are fine. Regards, Tom From owner-freebsd-questions@freebsd.org Mon Jul 9 22:34:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5483103A9EA for ; Mon, 9 Jul 2018 22:34:54 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D85E88B5EB for ; Mon, 9 Jul 2018 22:34:53 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.167]) with ESMTPA (Nemesis) id 0MPc3R-1fgnTk2bAX-004fsY; Tue, 10 Jul 2018 00:34:49 +0200 Date: Tue, 10 Jul 2018 00:34:48 +0200 From: Polytropon To: mayuresh@kathe.in Cc: freebsd-questions@freebsd.org Subject: Re: backspace not working with mg Message-Id: <20180710003448.e51a3d6e.freebsd@edvax.de> In-Reply-To: <20180709222824.74761578.freebsd@edvax.de> References: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> <20180709222824.74761578.freebsd@edvax.de> 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-Provags-ID: V03:K1:NuRGH/LOTIsEXUuAvTR+tQfq7bldbq5KPtyRsRFwb1HYiMY1i/X g+M53Z1Fd54Y9w/6Ot/uvwxlbfZdP5Z83Iou14OgyEGiLpimJGEKQm9f1r5h+JAWvjb11UF gYR2YWwVU+PGb/59Kt1Vbpos4JJQ3k59aOk9fJTpUA3tuacQeuV3SISoD3DfyARA+MKD3hF 0ZjRoz6D+hXrp8Ixb7SgA== X-UI-Out-Filterresults: notjunk:1;V01:K0:KF7xsnwHE3E=:Tec1yDmwnLPD0om4WYZLMv CqGk/XImWGkz9MeY1IrD1eAs21/FQQTH/xVYxhNafwzHVuWYqsuXHcaG8bpziv5L/BF5b5O4T MoaORN4KIKV0i14/c6bwmMaqVPAzfw0NfUncppTQc7uctBEeKi5L0m1VQOXvHbei2NGIpamMb a798AALsAGFMwK6xEC/LsV4OFckkDda3AwRTpG/S8OLWl5TIrpMG6draGs5xoXqY9eW4lI+1e W6SFuYi88LGp7SuDeLhyZ9Pu8LhQ9cq6ptQoJoNZYDB5sriGcyCFEsyPs3Bo6kgaTZ0Khh2ID iqAeKx9etuab8v8DQ+s91t2EEQ686+dhkTZoTHS963iqOjQS8fpyWUgp8E1UVyfgZ9v81o3pQ VGkqSOZ8HIaovtEHP8fo8sTSGO8XJTLVKfRbjkElVRKBuIEp3YGbVs+G62auOhzlzo1YUVykm z3AhyZ1zkgvdh45qiUusWmwID4VV2rHSEw51FJmkyKkB4kLelAt9C7FU7zQjYsdtlFURXskdA NAOgNXhwz/3JJ/syyOAM6tWq6BDHJKfMfjxwTxRwQkVu3fc6w8Tjf+szbFyOdyqCtPV866lQq 90lsZ9yyYI+1F7ifovElfGbu9mUlZLH47BOviPddViHjiDUEil6tmy9SR2hOBdyX/5D9Sbqdd M8ojJRRPJNXVeumcS+jekxtG4451ihuq5pCsXDUHj8L2joRgn+M/N6rx17QBeM4863THdyp6x GO7oyWxGfIScG7fD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 22:34:54 -0000 On Mon, 9 Jul 2018 22:28:24 +0200, Polytropon wrote: > If parentheses matching for lips is your goal, [...] For lisp. LISP! L-I-S-P!!! :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Tue Jul 10 05:58:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19E591049809 for ; Tue, 10 Jul 2018 05:58:08 +0000 (UTC) (envelope-from peter@boosten.org) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A16CC82B8B for ; Tue, 10 Jul 2018 05:58:07 +0000 (UTC) (envelope-from peter@boosten.org) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id B6DF5625F8 for ; Tue, 10 Jul 2018 01:58:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2-1hbxeS6oP for ; Tue, 10 Jul 2018 01:58:04 -0400 (EDT) Received: from inet17.hamilton.harte-lyne.ca (inet17.hamilton.harte-lyne.ca [216.185.71.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Tue, 10 Jul 2018 01:58:04 -0400 (EDT) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet17.hamilton.harte-lyne.ca (Postfix) with ESMTPS id 646399DF5C; Tue, 10 Jul 2018 01:58:04 -0400 (EDT) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 58C32CF5D; Tue, 10 Jul 2018 01:58:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id KxS6qTSlNboF; Tue, 10 Jul 2018 01:57:47 -0400 (EDT) Received-SPF: Temperror (mailfrom) identity=mailfrom; client-ip=212.54.42.164; helo=smtpq1.tb.mail.iss.as9143.net; envelope-from=peter@boosten.org; receiver= Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPS; Tue, 10 Jul 2018 01:57:46 -0400 (EDT) Received: from [212.54.42.136] (helo=smtp12.tb.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fclei-0006cp-GF; Tue, 10 Jul 2018 07:57:44 +0200 Received: from 5419f71f.cm-5-2d.dynamic.ziggo.nl ([84.25.247.31] helo=ra.boosten.org) by smtp12.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1fclei-0008Vc-Eg; Tue, 10 Jul 2018 07:57:44 +0200 Received: from ra.egypt.nl (localhost.egypt.nl [127.0.0.1]) by ra.boosten.org (Postfix) with ESMTP id 952C5343308B; Tue, 10 Jul 2018 07:57:43 +0200 (CEST) X-Virus-Scanned: amavisd-new at boosten.org Received: from ra.boosten.org ([127.0.0.1]) by ra.egypt.nl (ra.egypt.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqICvBxM32LY; Tue, 10 Jul 2018 07:57:37 +0200 (CEST) Received: from www.boosten.org (ra.egypt.nl [192.168.13.15]) by ra.boosten.org (Postfix) with ESMTPA id 16DFE3433087; Tue, 10 Jul 2018 07:57:37 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 10 Jul 2018 07:57:34 +0200 From: Peter Boosten To: byrnejb@harte-lyne.ca Cc: freebsd-questions@harte-lyne.ca, owner-freebsd-questions@freebsd.org Subject: Re: FreeBSD-11, Amavisd-New Spamassassin and Pyzor Reply-To: peter@boosten.org Mail-Reply-To: peter@boosten.org In-Reply-To: References: <071b18a6a1025eb2f27c9091dfc75f90.squirrel@webmail.harte-lyne.ca> <77694e205a706f0e4517b5bf2058bc86@boosten.org> <594f1e8cc6680fc6076ac1cbf35852c5@boosten.org> Message-ID: <0f5f1dbe8742f704adc1fdedca0eebf6@boosten.org> X-Sender: peter@boosten.org User-Agent: Roundcube Webmail/1.3.6 X-SourceIP: 84.25.247.31 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=Gc+jYjfL c=1 sm=1 tr=0 a=JWBJsaPp29SgP5DpYRBqZw==:17 a=IkcTkHD0fZMA:10 a=R9QF1RCXAYgA:10 a=b6nfwRhkAAAA:8 a=4KpQIbDHtWIV50MmThEA:9 a=Wu1FouM_i_aEdmS5:21 a=G9qa4AYJur5wGbHa:21 a=QEXdDO2ut3YA:10 none X-Ziggo-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 05:58:08 -0000 James B. Byrne via freebsd-questions schreef op 2018-07-09 21:49: > > I am still uncertain whether or not I have actually installed pyzor > and razor2 correctly. But after these changes avavisd and > spamassassin seems to be working, at least to some degree at the > moment. > You could put this in your local.cf and watch the headers... pyzor_add_header 1 X-Spam-Status: No, score=0.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, FSL_BULK_SIG=0.001, PYZOR_CHECK=1.392, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no I can check razor by raising the debug level in its configuration file, which in my case is in /var/amavis/.razor My config looks like this: # # Razor2 config file # # Autogenerated by Razor-Agents v2.84 # Wed Jul 9 21:00:24 2014 # Created with all default values # # see razor-agent.conf(5) man page # debuglevel = 0 identity = identity ignorelist = 0 listfile_catalogue = servers.catalogue.lst listfile_discovery = servers.discovery.lst listfile_nomination = servers.nomination.lst logfile = razor-agent.log logic_method = 4 min_cf = ac razordiscovery = discovery.razor.cloudmark.com rediscovery_wait = 172800 report_headers = 1 turn_off_discovery = 0 use_engines = 4,8 whitelist = razor-whitelist If you raise the debug level to 5, that would give you enough evidence. The log will be in the same directory, called razor-agent.log. No need to restart amavis for this. You need to tell spamassassin where razor is, though. I did this: razor_config /var/amavis/.razor/razor-agent.conf You can either do that in local.cf, or in the user_prefs file in amavis' home directory (again, in my case: /var/amavis/.spamassassin/) Hope this helps. -- Met vriendelijke groet / Kind regards / Mit freundlichem Gruß Peter Boosten From owner-freebsd-questions@freebsd.org Tue Jul 10 06:26:14 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77F721022DB2 for ; Tue, 10 Jul 2018 06:26:14 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay10.mail.gandi.net (relay10.mail.gandi.net [217.70.178.230]) (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 F37B883E34 for ; Tue, 10 Jul 2018 06:26:13 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.6]) (Authenticated sender: mayuresh@kathe.in) by relay10.mail.gandi.net (Postfix) with ESMTPA id E8ED5240009; Tue, 10 Jul 2018 06:26:10 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 10 Jul 2018 06:26:10 +0000 From: Mayuresh Kathe To: Polytropon Cc: freebsd-questions@freebsd.org Subject: Re: backspace not working with mg Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: <20180710003448.e51a3d6e.freebsd@edvax.de> References: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> <20180709222824.74761578.freebsd@edvax.de> <20180710003448.e51a3d6e.freebsd@edvax.de> Message-ID: <8829f54510a70c6c18e67c98239827b7@kathe.in> X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-Spam-Level: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 06:26:14 -0000 On 2018-07-09 10:34 PM, Polytropon wrote: > On Mon, 9 Jul 2018 22:28:24 +0200, Polytropon wrote: >> If parentheses matching for lips is your goal, [...] > > For lisp. LISP! L-I-S-P!!! :-) LOL. :-) From owner-freebsd-questions@freebsd.org Tue Jul 10 08:25:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6B121030027 for ; Tue, 10 Jul 2018 08:25:23 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) (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 1BFF489263 for ; Tue, 10 Jul 2018 08:25:22 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (localhost [127.0.0.1]) by mail.cs.ait.ac.th (Postfix) with ESMTP id 5530161F83 for ; Tue, 10 Jul 2018 15:25:11 +0700 (+07) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.ait.ac.th; h= content-type:content-type:mime-version:message-id:date:date :subject:subject:from:from:received:received:received; s= selector1; t=1531211110; x=1533025511; bh=ssQvYBNrJYlFJbq6qOr7Yt RDfF1+yUwQ5sO+1aq9aF0=; b=Tn+D/QtT69Lxxx1bYEav9tcLzs5mR9Joj4majp 5hxXyhflrrYSBYA4wQORn5O5OGnLFORe8URz2h4GtarOKu0ibEGBQD8rG+zamuv8 AY9ucIBlB7TGnYHdW18iK06xRlSD4rATYyYExYgiZ0BVipGnfdye/iyEsiqNesDA +1RZQ= X-Virus-Scanned: amavisd-new at cs.ait.ac.th Received: from mail.cs.ait.ac.th ([127.0.0.1]) by mail.cs.ait.ac.th (mail.cs.ait.ac.th [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lH4DFcLY6gyb for ; Tue, 10 Jul 2018 15:25:10 +0700 (+07) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cs.ait.ac.th (Postfix) with ESMTPS id B4AD061F82 for ; Tue, 10 Jul 2018 15:25:10 +0700 (+07) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.15.2/8.15.2/Submit) id w6A8P93r060215; Tue, 10 Jul 2018 15:25:09 +0700 (ICT) (envelope-from on@banyan.cs.ait.ac.th) From: Olivier To: freebsd-questions@freebsd.org Subject: Fisable ctrl-alt-del reboot Date: Tue, 10 Jul 2018 15:25:09 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 08:25:23 -0000 Hi, I am running a system with FreeBSD and since I updated to 11.1, it seems it ignore the sysctl to disable CTRL+ALT_DEL reboot. Am I the only one to see this behaviour? FreeBSD door.cs.ait.ac.th 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #3 r334472: Fri Jun 22 11:03:48 ICT 2018 root@door.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC i386 $ sysctl hw.syscons.kbd_reboot hw.syscons.kbd_reboot: 0 $ sysctl -d hw.syscons.kbd_reboot hw.syscons.kbd_reboot: enable keyboard reboot But it can still be rebooted from the keyboard. Am I missing something? Thansk in advance, Olivier -- From owner-freebsd-questions@freebsd.org Tue Jul 10 08:45:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EB331032275 for ; Tue, 10 Jul 2018 08:45:07 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id E4A2E8A02C for ; Tue, 10 Jul 2018 08:45:06 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 2E53829E0B; Tue, 10 Jul 2018 17:44:55 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 9F5FC44265; Tue, 10 Jul 2018 17:44:54 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 968CA44264; Tue, 10 Jul 2018 17:44:53 +0900 (JST) Date: Tue, 10 Jul 2018 17:44:32 +0900 (JST) Message-Id: <20180710.174432.1244771672628073392.yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: Fisable ctrl-alt-del reboot From: Yasuhiro KIMURA In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 08:45:07 -0000 From: Olivier Subject: Fisable ctrl-alt-del reboot Date: Tue, 10 Jul 2018 15:25:09 +0700 > I am running a system with FreeBSD and since I updated to 11.1, it seems > it ignore the sysctl to disable CTRL+ALT_DEL reboot. > > Am I the only one to see this behaviour? > > FreeBSD door.cs.ait.ac.th 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #3 r334472: Fri Jun 22 11:03:48 ICT 2018 root@door.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC i386 > > $ sysctl hw.syscons.kbd_reboot > hw.syscons.kbd_reboot: 0 > $ sysctl -d hw.syscons.kbd_reboot > hw.syscons.kbd_reboot: enable keyboard reboot > > But it can still be rebooted from the keyboard. > > Am I missing something? What is the value of kern.vty? If it is 'vt', then you should set kern.vt.kbd_reboot to 0 instead of hw.syscons.kbd_reboot. --- Yasuhiro KIMURA From owner-freebsd-questions@freebsd.org Tue Jul 10 12:53:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9601210492AA for ; Tue, 10 Jul 2018 12:53:08 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 38F7B74FC5 for ; Tue, 10 Jul 2018 12:53:07 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 083F6D821 for ; Tue, 10 Jul 2018 08:53:01 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id rOKmaeXNzYkE for ; Tue, 10 Jul 2018 08:52:45 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 6001DD808 for ; Tue, 10 Jul 2018 08:52:45 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Tue, 10 Jul 2018 08:52:45 -0400 Message-ID: <5e53aa0720bba3538f6c3e27ae368e6f.squirrel@webmail.harte-lyne.ca> Date: Tue, 10 Jul 2018 08:52:45 -0400 Subject: ntpd binds to all ldefined loopback addresses From: "James B. Byrne" To: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 12:53:08 -0000 I have encountered an issue with ntp on FreeBSD-11. This may be either a design feature or a bug; or just a misunderstanding on my part. The host in question has server jails running on it. None of these are running ntpd. However, the host is and is configured to listen on specific addresses: # grep -i listen /etc/ntp.conf ### Set the listening addresses to avoid collisions with jails interface listen 192.168.216.18 interface listen 216.185.71.18 However, when I do a sockstat I see this: # sockstat -l | grep ntp root ntpd 11391 20 udp4 216.185.71.18:123 *:* root ntpd 11391 21 udp4 192.168.216.18:123 *:* root ntpd 11391 22 udp6 ::1:123 *:* root ntpd 11391 23 udp4 127.0.0.1:123 *:* root ntpd 11391 24 udp4 127.0.31.1:123 *:* root ntpd 11391 25 udp4 127.0.32.1:123 *:* root ntpd 11391 26 udp4 127.0.84.1:123 *:* Despite being instructed to only listen on two addresses ntpd has glommed every available loopback address. Is this intentional? if not then how does one configure ntp to only listen on a specific lo address? I have already tried specifying 'listen 127.0.0.1' and this produced no change in ntpd's observed behaviour. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Tue Jul 10 17:18:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 950A1103DC9C for ; Tue, 10 Jul 2018 17:18:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD904812CD for ; Tue, 10 Jul 2018 17:18:08 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue105 [212.227.15.183]) with ESMTPA (Nemesis) id 0LhNMu-1gPBKy1WXw-00malH; Tue, 10 Jul 2018 19:18:00 +0200 Date: Tue, 10 Jul 2018 19:17:57 +0200 From: Polytropon To: Olivier Cc: freebsd-questions@freebsd.org Subject: Re: Fisable ctrl-alt-del reboot Message-Id: <20180710191757.6389ae22.freebsd@edvax.de> In-Reply-To: References: 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-Provags-ID: V03:K1:F8LRz1MerrU7kROaqkmScG9vhg2xJDI5BdA6dsOX6EAcWTyDMxv JURPY6BUoXLSioMpiuWZZI0NBr5yvcD30j4SHPGVVyD4aKLFnYHC7ORbheV7h+rJ9FaHS0u kOd0IFKa2l5xgeUCIDCC2iJ/UHOForRxAWDHdLKgywPH1im2XNlaOZ4wsM30UNYAI3+19bi KyhA39wjDlxq3vEa8+CBw== X-UI-Out-Filterresults: notjunk:1;V01:K0:jGgE1Fm7PhM=:Y06UF8pUEaI/Jx7os+OSAM qUH+MeLHMqF/UguePPBFpnPjJHMjhHyL7iVSsFcFba1N0Wd5TrjcCpm691Rf/KTu4/Mp+4mMX L1oT1u//psI4S5zz31ZlXrQjNPurnKfxOzhh9wqb4DriSeWC1mzJrumjk9xT9nNvOMktUuEmt oAPS1r/qH4cbedWZjZj+f3acgQhKUeCRscbAL8gmVHGy7ApXUm/kwU6ttOxtmlWEhE55umeIj aQ85PYByVgeN5g/TBbmvMeNAx5t9uzlanHpKAkhDQ7a/Km1k5zfMotIu7+ivsvNEWifPLiKkl c3c7w8vIA8eWrs/7O/REe9m4ydCKrYRsPClX0K1a4KqfdthKph/Bq+d1KKTGCVrJzdEq7l36x 4A5JU1OqDlxT9zcnuDzecBvi36eIvDTomDT0pVN+UjixOVLiBEfbNAEQRjXIkvyK44O2iBKI/ x27v2Z2DMmYbWyNRdhaW1LBS45NS1/8ZxDJe1BAV184yvFDrmObB+4tJBbAyBtDU7hzWdd4vP Cc0GJYbZbYSoEJHCVzaeqF87FIXi/JEBL9+DsaROtq6nFTcA2b4o1X0nYN6O3XztgsKTbdebT yamZikGGS/qKgPflShNXO7aCiKC0mu5JTbXQSxLypYU99e+xigEVKyOmNPfFKMhSf3n3T8Jfm 2J42OwCydMaPKPV5Uz4G3SWKtLTXQoS59Q2tMMVHYrPtEnNd+VunD3+5+Ss0DKSPv2ef+etFj fRanCa+vwI4idJ4E X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 17:18:09 -0000 On Tue, 10 Jul 2018 15:25:09 +0700, Olivier wrote: > I am running a system with FreeBSD and since I updated to 11.1, it seems > it ignore the sysctl to disable CTRL+ALT_DEL reboot. > > Am I the only one to see this behaviour? > > FreeBSD door.cs.ait.ac.th 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #3 r334472: Fri Jun 22 11:03:48 ICT 2018 root@door.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC i386 > > $ sysctl hw.syscons.kbd_reboot > hw.syscons.kbd_reboot: 0 > $ sysctl -d hw.syscons.kbd_reboot > hw.syscons.kbd_reboot: enable keyboard reboot > > But it can still be rebooted from the keyboard. > > Am I missing something? If I may guess: This sysctl refers to syscons (sc), while on FreeBSD 10 and later, sc has been obsoleted by vt. Could that be the reason? If you temporarily exchange vt for sc (with "kern.vty=sc" in /boot/loader.conf), you should see the desired behaviour, even though X won't work anymore (if this is important to you). But vt seems to support what you need. See "man 4 vt" for the following configuration entries: In loader.conf(5) or sysctl.conf(5): kern.vt.kbd_halt=1 kern.vt.kbd_poweroff=1 kern.vt.kbd_reboot=1 kern.vt.kbd_debug=1 kern.vt.kbd_panic=0 kern.vt.enable_bell=1 Maybe this can help? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Tue Jul 10 17:40:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEDA6103FB35 for ; Tue, 10 Jul 2018 17:40:38 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 411E482117 for ; Tue, 10 Jul 2018 17:40:38 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x233.google.com with SMTP id n17-v6so25243420wmh.2 for ; Tue, 10 Jul 2018 10:40:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=MagvYQBdNBWha25REMsF84TO8HM3nOWyc5IHQA2D60k=; b=TO5P/yOWigjyWzLA1Q+gHKgKKW1VODsoPWTN+ebg31RV5xQ5Z1DUbE7qBdGcJqHqSN b4CwVEsRLCNwIXSsvLq3PT1/Tgb3uoHAQkpi/WPKPL1jiSRguL8Iew6ptFo/sZZfkicp +DHMfLdtvc+hzrQreSTIzZrL5MnNd3dXMAqbFNW8Dgxz88GyIYXfIrho+6wwtmgTKKkb GTqiSU9YYDSV7EaO6YQgK/DxxbpVkTYBCGpkNCquzQRaiG/+i0KMd7QVRAWldyzmebPI oVZYyqsLF+4WUEmDBflleQ5lKmY59oR04HttudXRrYQ/8lmE1KqU/587RzNKxN0T1z6p IF2w== X-Gm-Message-State: APt69E2K0fALFUsu7me8C0MnAYZmE7UJ1ItgvyXhRr0w7VYWu16WSkU7 Okya5KMSdKLJjPQjxklDaWv1hA== X-Google-Smtp-Source: AAOMgpcJDLnUAK6cEQTLBzV1ahlBx/2OkWQ0mzeUkjKLhX+gRTSTq/xYfp7qC0RD4kn/i2BsxU5R+w== X-Received: by 2002:a1c:1509:: with SMTP id 9-v6mr14486043wmv.142.1531244437026; Tue, 10 Jul 2018 10:40:37 -0700 (PDT) Received: from gumby.homeunix.com ([90.195.199.172]) by smtp.gmail.com with ESMTPSA id z9-v6sm32484727wre.49.2018.07.10.10.40.35 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 10 Jul 2018 10:40:36 -0700 (PDT) Date: Tue, 10 Jul 2018 18:40:32 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Message-ID: <20180710184032.55346a5d@gumby.homeunix.com> In-Reply-To: <20180709083526.c4b4924f.freebsd@edvax.de> References: <6e21b74531c2b6ca7ca89cfc37add6a2@kathe.in> <20180709083526.c4b4924f.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 17:40:39 -0000 On Mon, 9 Jul 2018 08:35:26 +0200 Polytropon wrote: > but fetchmail can "copy" messages, i. e., leave them on the server, > and upon invocation, only load the unread messages). Check > "man fetchmail" for the keep / nokeep keyword. It's already been clarified that the fetchmail instance would also be remote, so this doesn't apply to the OP, but for the record, getmail handles the above better. With IMAP fetchmail handles 'download and leave on server' through the IMAP '/SEEN' flag, it downloads unread mail, marking everything it downloads as read. This has two obvious flaws, anything you read online wont get downloaded, and anything that's downloaded gets marked as read on the server. getmail keeps track of what it's downloaded using timestamped UID+UIDVALIDITY pairs, so: 1. it downloads reliably 2. it wont mark your IMAP mail as read (unless you want it to) 3. it supports an option to delete server-side mail N days after download. From owner-freebsd-questions@freebsd.org Tue Jul 10 19:44:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F78F104AA9C for ; Tue, 10 Jul 2018 19:44:01 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from hz.citrin.ru (hz.citrin.ru [IPv6:2a01:4f8:d16:10c3::2]) (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 8F04488ADE for ; Tue, 10 Jul 2018 19:44:00 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from x220.lan (unknown [IPv6:2601:18a:c680:9888:508a:a8ce:de55:aac4]) by hz.citrin.ru (Postfix) with ESMTPSA id 6B41A2EED30 for ; Tue, 10 Jul 2018 19:43:57 +0000 (UTC) Subject: Re: displaying long SSIDs To: freebsd-questions@freebsd.org References: <1b3bc11511677689ed03347dd34bb29b@vvelox.net> From: Anton Yuzhaninov Openpgp: preference=signencrypt Autocrypt: addr=citrin+bsd@citrin.ru; prefer-encrypt=mutual; keydata= xsBNBFjFfacBCAD1iyEIAXFiLT+egdxB4APkoLh9lWHv7OavCsIwaktbGpvx/FY1tm50Pt6n mF4pNrxrpIjATqWm9Tzl7EieFBeiFqXuq5Kx0zs73BgyXzxMnrzR7vrAc+E9NTr6BXu5Pbhu N4oSUxmSm6MDLoGv/LXEEIDUPaWXG5rXGOs2b0apHsKktrxSHczwLpT8DktnhGUTrsIsrFiv YwxoOmRcIqhmoRvc0blyj1W4fqTBSWfFOGHgbfemG6qWCuFD2nhngYj57FOpH7l3SO0Jd2b9 8/bOr/Jq+7EycTCFGk/48Z/hNmjZ6hizC9GHgRK5idruHggaWeonkwLbrA7RwjHkvQCpABEB AAHNI0FudG9uIFl1emhhbmlub3YgPGNpdHJpbkBjaXRyaW4ucnU+wsCUBBMBCAA+FiEEIzyn DGuZSu1g7YtSkaEDRZW7kZYFAljFfacCGwMFCQWjmoAFCwkIBwIGFQgJCgsCBBYCAwECHgEC F4AACgkQkaEDRZW7kZbyeQgAxG9G5DpXJJAJw8GMXQ9I2488w/Pv2jXsmjr8OsP8g4KOw/RW qjqCThLp2ge0EQxrNyWYd+bFuy3olnTucCwWC/oenSTrPg9JjFsq58mghcCquL/+64ScudRK sxC7pV8NS5UBthohJOAtmT7M68UuuQ5WhngRlRfrrvZ/tUxEQWkc2OFwyMDqAsBAvQzVHjya YmYO8zDY1jjzucqFN/rpmNKTzb4LpJ42Y5C0ap54nKfSbSFQClMPEdDRitCfu6GPKIqYd8Mx 3/1dylT1G7HimeRivcBq55Y02CXwp8tSEBpq4uac1bClQOImhs/UkwUhOU3Iqm3E7q3OOZ/g jQa8Ec7ATQRYxX2nAQgA1WAbaTVz010cXDYZcwzWcgTNnHcFAtMTHjNiioJU72tUphhdnOxw uHcAfDOjsg9d3wQZJORuKfnfeHz9e3rGTooGVJU+7i6A4mEjcM01R7EpqGZzFdCYfoVD0I4S eDOvVTUo1/Tho9MjZ9zLISchp//t+tCcw9513ZtVnXnC6PQ7eHkcAvBCMbUwPmJV4CG4ILR7 DwwjXLYTMPLXPOnld+3TrgH+is2+pf+n1m5pOKkop28/XkpHYKW5yP6Fj6DV/ChzdGGOq1Bi obm1dXSLcdMgw6fWHWAFfszMOxFEdIExNU9fi4lItO3j/4xYZ7CI08cSqldDt9sl0p9G4RdI PwARAQABwsB8BBgBCAAmFiEEIzynDGuZSu1g7YtSkaEDRZW7kZYFAljFfacCGwwFCQWjmoAA CgkQkaEDRZW7kZbPtggA3WigDCXtFSBa3/EnHojgHtp88jSTIuGruqa0ZyMm7Nci0hBBfkWw 9jNVxurRPAnsJ6SnWrdeUno1aOkzizi3yUpPj4Myovr7Kk+PiMM2DWkavlza5YwxFrgOqwmb fddrl4YBijdXe1WK/Nz3mYyx7Olg7WPxzJ8xjslv/D+a05qV2H4IQsTpj24pE6TUur81yxij dNXMowfW2/A2S4OJkHU54rRgOvcjz38Xcb2TU62vb7ulTqdU+bcbOKGdgnd7LMJEi5oJ0q8j q6ijwb2Eh+J2K/I41AUMvkPng59kdrB1AZlULlbTYeDz8yenX3lJ+REVt6eUhPXpPADIjnp8 tQ== Message-ID: <99616b94-7fb1-5c96-41e6-715dcb06f8b1@citrin.ru> Date: Tue, 10 Jul 2018 15:43:55 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1b3bc11511677689ed03347dd34bb29b@vvelox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrin.ru; s=s0; t=1531251837; bh=8UcxnwKCaz0ydWcTzKKQmKLg9anG+zL5b7xyDgGrHSc=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=2Bi571u//0nwoDObFfaCUaa57wqp1Gvd4LsabwLNFTopLCgbNYpNzEtU2tB2y0sVCcXoOuvOjlPAn1SdrqLOg/VoIv5J0dJh+CttVWIbxoYpXtrbi536I32oaT4deP+kOoo1zdicICoj3sf9jsPjtHKyO99s2RLGaLL1J/qjy5w= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 19:44:01 -0000 On 07/08/18 07:49, Zane C. B-H. wrote: > Is there any way to display long SSIDs with list scan for ifconfig? In the > SSID column it truncates them and appends '...'. ifconfig -v wlan0 scan shows untruncated SSID Output is very long so it is handy to see as: ifconfig -v wlan0 scan | less -S From owner-freebsd-questions@freebsd.org Wed Jul 11 02:36:30 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F11F10256E9 for ; Wed, 11 Jul 2018 02:36:30 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) (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 7D3D077EA0 for ; Wed, 11 Jul 2018 02:36:28 +0000 (UTC) (envelope-from Olivier.Nicole@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (localhost [127.0.0.1]) by mail.cs.ait.ac.th (Postfix) with ESMTP id CC35661F86; Wed, 11 Jul 2018 09:36:23 +0700 (+07) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.ait.ac.th; h= content-type:content-type:mime-version:message-id:date:date :in-reply-to:subject:subject:from:from:received:received :received; s=selector1; t=1531276583; x=1533090984; bh=/6kedT/Ai lzeNS5kp3N8KXderZ1BuPDDheB5vgDU14s=; b=UH5yR9z0b5Vn1HzS4UM3Xfesn uM2VEJ1eyK65MHSsZUW6+jEg+h4mYqUeqsjtTf6dhv5j78lHp0bwuqmfd1EKF9qB m44sIIqMrDPPEXPialK7b/VgmegGR80PRbwZ+SmKYtPxinEq7B1vdwCGUZOVQ/N9 rJhvYo09BBMSUiEKHY= X-Virus-Scanned: amavisd-new at cs.ait.ac.th Received: from mail.cs.ait.ac.th ([127.0.0.1]) by mail.cs.ait.ac.th (mail.cs.ait.ac.th [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kGxZpeWPmU5m; Wed, 11 Jul 2018 09:36:23 +0700 (+07) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cs.ait.ac.th (Postfix) with ESMTPS id 2594461F83; Wed, 11 Jul 2018 09:36:23 +0700 (+07) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.15.2/8.15.2/Submit) id w6B2aMW9067429; Wed, 11 Jul 2018 09:36:22 +0700 (ICT) (envelope-from on@banyan.cs.ait.ac.th) From: Olivier To: RW Cc: freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request In-Reply-To: <20180710184032.55346a5d@gumby.homeunix.com> (message from RW via freebsd-questions on Tue, 10 Jul 2018 18:40:32 +0100) Date: Wed, 11 Jul 2018 09:36:22 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 02:36:30 -0000 RW via freebsd-questions writes: > On Mon, 9 Jul 2018 08:35:26 +0200 > Polytropon wrote: > > > >> but fetchmail can "copy" messages, i. e., leave them on the server, >> and upon invocation, only load the unread messages). Check >> "man fetchmail" for the keep / nokeep keyword. > > It's already been clarified that the fetchmail instance would also be > remote, so this doesn't apply to the OP, but for the record, getmail > handles the above better. That is not exacteky what I understood. I think that all the OP wants a way to "use mailx on his mailbiox". Because mailx does not rely on a network protocol, but rather only works on a mbox file local to the machine where mailx command is used, he needs a way to get the messages to the machine where he will be using the command mailx. One way to do that would be to setup the machine as a mail server, but it is a huge task (even if the OP is not interested in setting up IMAP or webmail). One other way is to keep the original server working and fetch the mail from that server to the machine that will be used for mailx. One of the way being fetchmail, I don't know getmail, it may well do the same job: reading mail with IMAP and dumping it into a mbox file. My feeling is that setting the fetch/getmail way acheives the goal of the OP (being able to read mail with mailx) while being many orders of magnitude simpler than having to learn sendmail. Best regards, Olivier > With IMAP fetchmail handles 'download and leave on server' through the > IMAP '/SEEN' flag, it downloads unread mail, marking everything it > downloads as read. This has two obvious flaws, anything you read > online wont get downloaded, and anything that's downloaded gets marked > as read on the server. > > getmail keeps track of what it's downloaded using timestamped > UID+UIDVALIDITY pairs, so: > > 1. it downloads reliably > > 2. it wont mark your IMAP mail as read (unless you want it to) > > 3. it supports an option to delete server-side mail N days > after download. > > _______________________________________________ > 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 Jul 11 19:08:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE2511038375 for ; Wed, 11 Jul 2018 19:08:27 +0000 (UTC) (envelope-from djtherenovator@gmail.com) Received: from mail-ed1-x542.google.com (mail-ed1-x542.google.com [IPv6:2a00:1450:4864:20::542]) (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 4B99E816C6 for ; Wed, 11 Jul 2018 19:08:27 +0000 (UTC) (envelope-from djtherenovator@gmail.com) Received: by mail-ed1-x542.google.com with SMTP id i20-v6so6963380eds.12 for ; Wed, 11 Jul 2018 12:08:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VvaVjy6IG6EnNJU2ocDjaEQYbAMNJHnY0M2nlYLYETo=; b=EurJG6cGo1NkWdHaW62j6dXXMpfyZaCvEb0/crgiUZ7eclz8PMpN+yFw4Ef3C0N7y4 gdWnZlUgMdMjayCuAIejBDGncWYabd4kWWfqUn6lRP6rdS2EL5IH3C0Bom2knR3ulJ2t 20Hsu4Shcb9/J3I6RuTiy9ylWpEqjcFfkkUN7RaCCvduNtuwIVzuvvoV7AqDYSfBTnKJ KnHl9T9TgF43qE+gv1hhHzUSUtohYVPGKF7Z/wcDAdFiEDawhTLcEpkOwkXD34q0eOHZ 0GgGectBijxopZqRqdb3aZfrWbweO0+VpjdhPOqihZj9y/L5/QiR7VeoIG7iQGqQpwRi Ludw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VvaVjy6IG6EnNJU2ocDjaEQYbAMNJHnY0M2nlYLYETo=; b=poMR04pqIKZgJ8aewvqAfBeo2T0aZIKCWbn0I4nOsvdsF0wDln65I26/3RsPeNQBI2 lOs9l5eaDbQK3ZkSy50j/lVrbuqnTW8TSKEB6rIp8XAYDb72/2BGy596gRRmhcXFCQn1 qgSHAxOsFVbauQH7Dpxq576qwVCZTqdftzXvPRNZOEmnXEc6zoZTb0tTT9t+uRFmX4zY e3DRNJv5oIUzapjM4bN01cYvvXe9azbkZXxpu0DYuGLJOoqmcP8XnKzwvjUvy75CHUsd DR3xXLFqRvkMK9nGEms/ODFZWp+Myyv9DRny9uewiYChE3AuGyrN21fO0+loSGkEzVT0 GNDQ== X-Gm-Message-State: APt69E0lm7a+sBvUXbn8SXd//a9zUebyyuYXRWVYpH2h8MYQL+5WYRr9 iF5CJwMzJMJbmtgxlQZbW67McwKm2GQ82j9nKwl5jnL3 X-Google-Smtp-Source: AAOMgpeRLzgufmbd8US49L7JI6PJhHg4mdi/7Fl9K2h5aqMxHfXAI1FKXYQ+bmFNAKSMrVPoHaDY/hnS42mdO0Y3gao= X-Received: by 2002:a50:8e09:: with SMTP id 9-v6mr10800809edw.101.1531336106061; Wed, 11 Jul 2018 12:08:26 -0700 (PDT) MIME-Version: 1.0 From: David Johnson Date: Wed, 11 Jul 2018 12:08:14 -0700 Message-ID: Subject: Help with an Urgent Matter To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 19:08:28 -0000 I have found a FreeBSD OS embedded in my Mac which is fully implemented. I followed the instructions and did the following from your website documentation: in terminal; shutdown -k +1 "message" I get the following: System shutdown time has arrived but you'll have to do it yourself I am not sure what to do at this prompt....what does 'do it yourself mean', and what do I type to complete the process?? Also in addition to the above question.... does the fact that those commands do actually work mean that I am correct in believing that there is a FreeBSD OS embedded in my system? Thank You, Free BSD Lamb Agency From owner-freebsd-questions@freebsd.org Wed Jul 11 19:23:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE9F3103A6D5 for ; Wed, 11 Jul 2018 19:23:19 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic309-21.consmr.mail.ne1.yahoo.com (sonic309-21.consmr.mail.ne1.yahoo.com [66.163.184.147]) (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 CD51F82857 for ; Wed, 11 Jul 2018 19:23:17 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: 4y_qwWoVM1lPTfuVQTjO4SJwzzpSmpp5vhzicm3B0zLLa54IgFv.nfOgfeWrim_ 9XLILB37sj32fHYQJztwJ89cALdzj9akgJZMFLwRHf0Lf7wLZ04OEqInZ5LMOzpOyQdpe5I6CLgf CMk96pWMB.2kn.LPqoGanokgX38R0gf1Kxu2tW6coqG3ljZ7o.ECJHRR5D4RTHDZSEsFXVeD5yZs DUtgOk2Fr77wB_UzccO1Ab0u75otbRhIO7ybrKLF0xPuqqwQTJw7Zj7_heubGUy2y3xuWRAJTSwN WW3dJ3sB.vCOVi78gVKT3RMEjSoamdSY0grAt4JkwcMDQrJBqQQsn7dw5ZgXhFcj_nXPrER3LlMk SF4zinpW9fuwmz68PLoqKJO3EH8XKf8Kxwz.Jmi3WAYSpC23rbTkyBfiPZYGVJ0PLOosZuEiZjY0 Lu7SzAzzGGdEtHicsjaUMrGYOeIjdo4O07bXRii8oyo_ruhAC3jh1FeltXB8W9.D75SBDnVjzpQN B3kgvVv9.SiW8kDQeH5zzRgKyt.nLUWE8atjsAnat_iqdV60RGbPb7Rq.h0jLkpJN85AIfATL00e elbJypcZ_tvuYf9U5XgPjfr.Jho7hPUoIYkC1N4.sWpln1S1ZLHxNrgo.SDahGrLTSdhi3tHAEfQ lm27zHKfAVRVJnCNn4mVl9bELXDGNt44A.ysQnMgFoGlUI.d.goqKG5DrOHKOd6yXhEllbKuEBM7 nSn1V3IfdvLsZaZjJitSGL22QRl_D5n9HmYiwHXcPDaBPr3.ir9Wai_4ulQ0aurSjbKm1jMYWnxZ XLbkp0HWaw7qvpibHuef6.p67GvWs6AJaSIepyLZkAv3fxmANYk9bzvu4Q9xmH4EsXcGRrGjoXyk 1YxpFmyqMt9htBvp3FDfJHfTsgZK7rPmQccCHK4H8EzkrMCIegzxNy4QyXi75a8T0RsAruvR1U5A YTq7Bgp6bDULaNJRYOWa1VWhqbVxxI1FIoM1oGdesFRHHA_xTHCVwOtZ2QAJHHwJaunCVvfKlCfl _cfPqEW8kH239vNvbuZseeatj2weO4AEjdUA- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ne1.yahoo.com with HTTP; Wed, 11 Jul 2018 19:23:08 +0000 Date: Wed, 11 Jul 2018 19:23:06 +0000 (UTC) From: Paul Pathiakis To: freebsd-questions@freebsd.org, David Johnson Message-ID: <1985397816.2919749.1531336986787@mail.yahoo.com> In-Reply-To: References: Subject: Re: Help with an Urgent Matter MIME-Version: 1.0 X-Mailer: WebService/1.1.12062 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 19:23:20 -0000 1.2.=EF=BF=BDWelcome to FreeBSD! |=20 |=20 | |=20 1.2.=EF=BF=BDWelcome to FreeBSD! | | | David,=20 As you can see, Apple borrows a lot from FreeBSD.=C2=A0 The co-joined opera= ting system is called DarwinOS which is the foundation for the Apple Mac OS= X operating system. Not having dealt with a Mac for years, I'm guessing about your issue.=C2=A0= If your command returns a prompt after it runs and spits out that message,= the shutdown command may have been altered. At the prompt, try a simple 'halt' command.=C2=A0 That should shut the mach= ine down. P. On Wednesday, July 11, 2018, 3:09:31 PM EDT, David Johnson wrote: =20 =20 I have found a FreeBSD OS embedded in my Mac which is fully implemented. I followed the instructions and did the following from your website documentation: in terminal;=C2=A0 shutdown -k +1 "message" I get the following: System shutdown time has arrived but you'll have to do it yourself I am not sure what to do at this prompt....what does 'do it yourself mean', and what do I type to complete the process?? Also in addition to the above question.... does the fact that those commands do actually work mean that I am correct in believing that there is a FreeBSD OS embedded in my system? Thank You, Free BSD Lamb Agency _______________________________________________ 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= " =20 From owner-freebsd-questions@freebsd.org Wed Jul 11 19:26:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D322D103AF9B for ; Wed, 11 Jul 2018 19:26:57 +0000 (UTC) (envelope-from Norman.Gray@glasgow.ac.uk) Received: from hillend.cent.gla.ac.uk (hillend.cent.gla.ac.uk [130.209.16.102]) (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 717D282B46 for ; Wed, 11 Jul 2018 19:26:57 +0000 (UTC) (envelope-from Norman.Gray@glasgow.ac.uk) Received: from cas08.campus.gla.ac.uk ([130.209.14.165]) by hillend.cent.gla.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1fdKlE-0006I7-PP; Wed, 11 Jul 2018 20:26:48 +0100 Received: from [130.209.45.140] (130.209.45.140) by cas08.campus.gla.ac.uk (130.209.14.165) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 11 Jul 2018 20:26:48 +0100 From: Norman Gray To: David Johnson CC: Subject: Re: Help with an Urgent Matter Date: Wed, 11 Jul 2018 20:26:48 +0100 X-Mailer: MailMate (1.11.3r5509) Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [130.209.45.140] X-ClientProxiedBy: cas07.campus.gla.ac.uk (130.209.14.164) To cas08.campus.gla.ac.uk (130.209.14.165) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 19:26:58 -0000 Greetings. On 11 Jul 2018, at 20:08, David Johnson wrote: > I have found a FreeBSD OS embedded in my Mac which is fully > implemented. Not really. macOS uses a lot of the FreeBSD 'userland' -- ie, the user commands -- but the kernel is significantly different. There is quite a close relationship between macOS and FreeBSD, though I'm vague on the details (if anyone has any links, I'd be very interested in them). However close it is, one cannot realistically say 'macOS is FreeBSD'! > I followed the instructions and did the following from your website > documentation: > > in terminal; shutdown -k +1 "message" The -k option means: -k Kick everybody off. The -k option does not actually halt the sys- tem, but leaves the system multi-user with logins disabled (for all but super-user). See 'man shutdown' As it happens, I think that 'shutdown -h now' does work on macOS, but it may not be formally supported. That is, there may well be other aspects of a fully controlled shutdown which this will miss. Good wishes, Norman -- Norman Gray : https://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK From owner-freebsd-questions@freebsd.org Wed Jul 11 20:24:05 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CE061040B27 for ; Wed, 11 Jul 2018 20:24:05 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A97CD85A77 for ; Wed, 11 Jul 2018 20:24:04 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id CFAB5E2B9 for ; Wed, 11 Jul 2018 16:23:55 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id 6vMSVGtcTXT9 for ; Wed, 11 Jul 2018 16:23:39 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 1F928E2AE for ; Wed, 11 Jul 2018 16:23:39 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Wed, 11 Jul 2018 16:23:38 -0400 Message-ID: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> Date: Wed, 11 Jul 2018 16:23:38 -0400 Subject: Why can I not get amd64/11.1-RELEASE? From: "James B. Byrne" To: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 20:24:05 -0000 I am experiencing difficulty installing ezjail-admin. Specifically when I run 'ezjail-admin install' I get this: fetch: ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz: Permission denied fetch: ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz: File unavailable (e.g., file not found, no access) fetch: ftp://ftp.freebsd.org/pub/FreeBSD/amd64/amd64/11.1-RELEASE/base.txz: File unavailable (e.g., file not found, no access) . . . Checking out the ftp site I discover this: fetch: ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz: File unavailable (e.g., file not found, no access) So, what is going on and how do I fix this? I can connect and see the files, I just cannot get them: ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE 229 Entering Extended Passive Mode (|||62035|) 150 Here comes the directory listing. -rw-r--r-- 1 ftp ftp 1157 Jul 21 2017 MANIFEST -rw-r--r-- 1 ftp ftp 49166232 Jul 21 2017 base-dbg.txz -rw-r--r-- 1 ftp ftp 104780108 Jul 21 2017 base.txz -rw-r--r-- 1 ftp ftp 1428656 Jul 21 2017 doc.txz -rw-r--r-- 1 ftp ftp 66586424 Jul 21 2017 kernel-dbg.txz -rw-r--r-- 1 ftp ftp 36773692 Jul 21 2017 kernel.txz -rw-r--r-- 1 ftp ftp 12555216 Jul 21 2017 lib32-dbg.txz -rw-r--r-- 1 ftp ftp 18499068 Jul 21 2017 lib32.txz -rw-r--r-- 1 ftp ftp 36756836 Jul 21 2017 ports.txz -rw-r--r-- 1 ftp ftp 147661560 Jul 21 2017 src.txz -rw-r--r-- 1 ftp ftp 4312456 Jul 21 2017 tests.txz 226 Directory send OK. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Wed Jul 11 20:31:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B9A1104171D for ; Wed, 11 Jul 2018 20:31:43 +0000 (UTC) (envelope-from freebsd-en@lists.vlassakakis.de) Received: from dd14614.kasserver.com (dd14614.kasserver.com [85.13.136.14]) (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 8EA3385EE6 for ; Wed, 11 Jul 2018 20:31:42 +0000 (UTC) (envelope-from freebsd-en@lists.vlassakakis.de) Received: from [192.168.3.57] (p54B6BF98.dip0.t-ipconnect.de [84.182.191.152]) by dd14614.kasserver.com (Postfix) with ESMTPSA id 8C1EF43C21BE; Wed, 11 Jul 2018 22:31:33 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Why can I not get amd64/11.1-RELEASE? From: Philipp Vlassakakis X-Priority: 3 (Normal) In-Reply-To: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> Date: Wed, 11 Jul 2018 22:31:33 +0200 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <456DE8C6-2761-4671-AAFE-F15CCC77ADF7@lists.vlassakakis.de> References: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> To: byrnejb@harte-lyne.ca X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 20:31:43 -0000 Can you save any other files? Does a simple =E2=80=9Etouch test=E2=80=9C work? Regards, Philipp > Am 11.07.2018 um 22:23 schrieb James B. Byrne via freebsd-questions = : >=20 > I am experiencing difficulty installing ezjail-admin. Specifically > when I run 'ezjail-admin install' I get this: >=20 > fetch: > = ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.t= xz: > Permission denied > fetch: > = ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.t= xz: > File unavailable (e.g., file not found, no access) > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/amd64/amd64/11.1-RELEASE/base.txz: > File unavailable (e.g., file not found, no access) > . . . >=20 > Checking out the ftp site I discover this: >=20 > fetch: > = ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.t= xz: > File unavailable (e.g., file not found, no access) >=20 > So, what is going on and how do I fix this? I can connect and see the > files, I just cannot get them: >=20 > ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE > 229 Entering Extended Passive Mode (|||62035|) > 150 Here comes the directory listing. > -rw-r--r-- 1 ftp ftp 1157 Jul 21 2017 MANIFEST > -rw-r--r-- 1 ftp ftp 49166232 Jul 21 2017 base-dbg.txz > -rw-r--r-- 1 ftp ftp 104780108 Jul 21 2017 base.txz > -rw-r--r-- 1 ftp ftp 1428656 Jul 21 2017 doc.txz > -rw-r--r-- 1 ftp ftp 66586424 Jul 21 2017 kernel-dbg.txz > -rw-r--r-- 1 ftp ftp 36773692 Jul 21 2017 kernel.txz > -rw-r--r-- 1 ftp ftp 12555216 Jul 21 2017 lib32-dbg.txz > -rw-r--r-- 1 ftp ftp 18499068 Jul 21 2017 lib32.txz > -rw-r--r-- 1 ftp ftp 36756836 Jul 21 2017 ports.txz > -rw-r--r-- 1 ftp ftp 147661560 Jul 21 2017 src.txz > -rw-r--r-- 1 ftp ftp 4312456 Jul 21 2017 tests.txz > 226 Directory send OK. >=20 >=20 > --=20 > *** e-Mail is NOT a SECURE channel *** > Do NOT transmit sensitive data via e-Mail > Do NOT open attachments nor follow links sent by e-Mail >=20 > James B. Byrne mailto:ByrneJB@Harte-Lyne.ca > Harte & Lyne Limited http://www.harte-lyne.ca > 9 Brockley Drive vox: +1 905 561 1241 > Hamilton, Ontario fax: +1 905 561 0757 > Canada L8E 3C3 >=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 Wed Jul 11 21:04:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7084810452BF for ; Wed, 11 Jul 2018 21:04:44 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 13B7687669 for ; Wed, 11 Jul 2018 21:04:44 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 9EBDCE377 for ; Wed, 11 Jul 2018 17:04:43 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id lIDxXm3tFJrb for ; Wed, 11 Jul 2018 17:04:27 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id BFE37E36C for ; Wed, 11 Jul 2018 17:04:26 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Wed, 11 Jul 2018 17:04:26 -0400 Message-ID: <45fabaafa88136c1e63a057f86cce88d.squirrel@webmail.harte-lyne.ca> In-Reply-To: <456DE8C6-2761-4671-AAFE-F15CCC77ADF7@lists.vlassakakis.de> References: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> <456DE8C6-2761-4671-AAFE-F15CCC77ADF7@lists.vlassakakis.de> Date: Wed, 11 Jul 2018 17:04:26 -0400 Subject: Re: Why can I not get amd64/11.1-RELEASE? From: "James B. Byrne" To: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 21:04:44 -0000 On Wed, July 11, 2018 16:31, Philipp Vlassakakis wrote: > Can you save any other files? > Does a simple „touch test“ work? > [root@vhost03 ~]# dir x bash: dir: command not found [root@vhost03 ~]# ll x -rw-r--r-- 1 root wheel 0 Jul 11 16:56 x -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Wed Jul 11 21:50:58 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 059A61049A14 for ; Wed, 11 Jul 2018 21:50:58 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (ns.umpquanet.com [209.216.177.146]) (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 6933589D0C for ; Wed, 11 Jul 2018 21:50:56 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (localhost [127.0.0.1]) by g5.umpquanet.com (8.15.2/8.15.2) with ESMTPS id w6BLU11D085379 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 11 Jul 2018 14:30:01 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by g5.umpquanet.com (8.15.2/8.15.2/Submit) id w6BLTxSG085237 for freebsd-questions@freebsd.org; Wed, 11 Jul 2018 14:29:59 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: g5.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Wed, 11 Jul 2018 14:29:59 -0700 From: Jim Long To: freebsd-questions@freebsd.org Subject: Disk/ZFS activity crash on 11.2-STABLE Message-ID: <20180711212959.GA81029@g5.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 21:50:58 -0000 I have a server running a Supermicro X11DPH-T system board (dmesg below) which is unstable under heavy disk read load. The following command is sufficient to trigger a crash: # zfs send -R pool@snapshot > /dev/null That command takes an unpredictable amount of time to trigger the crash, but I have never seen it complete successfully. Further, crash dumps of this are difficult to obtain (see below), despite the fact that dumps are enabled and tested via: # sysctl debug.kdb.panic=1 As disclosure, this machine sometimes exhibits a second failure mode with a "kernel trap 12 with interrupts disabled." This typically occurs on boot, just about the point where the kernel begins enumerating the CPUs. But that is not (yet) my primary concern. I typically perform the 'zfs send' stress test over an ssh session, although the server is nearby on a test bench. I have not yet been at the console when the panic or crash happens, so I am not certain that the kernel is "panicking gracefully," if you'll pardon the oxymoron, I have yet to find any crash dumps in /var/crash after a disk-induced panic. Is a serial console the next step in troubleshooting this? I am fairly strong in bash scripting, but inexperienced in kernel crash debugging. I already have remote syslogging set on this server, so it's feasible to write certain terse tidbits to syslog ("still alive at xx:yy PDT") and/or dump some key statistics every minute to the server's local ZFS pool, and then see what the last stats dump file shows upon reboot. What are some key stats I should capture at periodic intervals while waiting for the 'zfs send' to induce the crash -- iostat? zfs-stats is also installed, but I'm ignorant about what stats I should dump, and how to infer any post-mortem meaning from them. This problem first appeared when doing a backup of this machine. The 'zfs send' was invoked by a remote host over an ssh session with jumbo frames enabled, achieving a throughput of around 115 MB/sec going out over GigE. To eliminate the network driver as a possible point of failure, I discovered that sending the 'zfs send' output to /dev/null was sufficient to trigger the crash. I may try rate-limiting the output pipe with: # zfs send -R pool@snapshot | pv -Wbrat -L 1M > /dev/null to see whether the -L value has any effect on the ability of this command to complete successfully. After I started drafting this write-up, I finally got a crash dump. I ran the stress script: #!/usr/bin/env bash FILE="/var/crash/zfs-stress.start" SLEEP_TIME=10 # if this script causes a crash, then we should expect to see a # crash dump newer than this file: touch $FILE logger "begin $0" zfs destroy -rv tank@stress-test 2> /dev/null zfs snap -r tank@stress-test logger "begin 'zfs send -R tank@stress-test" zfs send -R tank@stress-test > /dev/null & logger "zfs send running in background" while [ -f $FILE ] && sleep $SLEEP_TIME; do logger "still alive @ $(date +%H:%M:%S)" done -- snip while also running 'systat -vm' in one virtual terminal and writing 'zpool iostat -v' to disk every couple seconds. I did finally observe a panic and this time got a dump. One quirk I forgot to mention is that after this ZFS-induced crash, on the next boot, the /etc/rc somehow does not run dhclient on the primary interface, despite its presence in /etc/rc.conf: ifconfig_ixl0="DHCP" I have no idea whether that is at all related, but it does mean that even if the system reboots after a crash, it is inaccessible except by the physical console. I have to log in as root and say 'dhclient ixl0'. On the NEXT boot, the DHCP client is invoked by /etc/rc as one would expect. I have: rc_debug="YES" defined in /etc/rc.conf but I am not seeing any messages that explain why dhclient is not being executed. I would be very grateful to anyone who has time to examine these post-mortems and offer any suggestions on where to go next. Thank you for your time reading this lengthy trouble report. Jim As promised, dmesg: Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 root@jimsdesk.example.edu:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(efifb): resolution 1680x1050 CPU: Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz (2300.08-MHz K8-class CPU) Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0xd39ffffb Structured Extended Features2=0x8 Structured Extended Features3=0xc000000 XSAVE Features=0xf VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 103079215104 (98304 MB) avail memory = 98749128704 (94174 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs FreeBSD/SMP: 2 package(s) x 12 core(s) x 2 hardware threads ioapic6: Changing APIC ID to 16 ioapic7: Changing APIC ID to 17 ioapic8: Changing APIC ID to 18 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-31 on motherboard ioapic2 irqs 32-39 on motherboard ioapic3 irqs 40-47 on motherboard ioapic4 irqs 48-55 on motherboard ioapic5 irqs 72-79 on motherboard ioapic6 irqs 80-87 on motherboard ioapic7 irqs 88-95 on motherboard ioapic8 irqs 96-103 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #38 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #40 Launched! SMP: AP CPU #29 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #27 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #28 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #42 Launched! SMP: AP CPU #32 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #34 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #37 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #41 Launched! SMP: AP CPU #21 Launched! SMP: AP CPU #18 Launched! SMP: AP CPU #35 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #36 Launched! SMP: AP CPU #31 Launched! SMP: AP CPU #43 Launched! SMP: AP CPU #44 Launched! SMP: AP CPU #45 Launched! SMP: AP CPU #39 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #24 Launched! SMP: AP CPU #25 Launched! SMP: AP CPU #46 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #26 Launched! SMP: AP CPU #33 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #47 Launched! Timecounter "TSC-low" frequency 1150040467 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4590, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: numa-domain 0 on acpi0 cpu1: numa-domain 0 on acpi0 cpu2: numa-domain 0 on acpi0 cpu3: numa-domain 0 on acpi0 cpu4: numa-domain 0 on acpi0 cpu5: numa-domain 0 on acpi0 cpu6: numa-domain 0 on acpi0 cpu7: numa-domain 0 on acpi0 cpu8: numa-domain 0 on acpi0 cpu9: numa-domain 0 on acpi0 cpu10: numa-domain 0 on acpi0 cpu11: numa-domain 0 on acpi0 cpu12: numa-domain 0 on acpi0 cpu13: numa-domain 0 on acpi0 cpu14: numa-domain 0 on acpi0 cpu15: numa-domain 0 on acpi0 cpu16: numa-domain 0 on acpi0 cpu17: numa-domain 0 on acpi0 cpu18: numa-domain 0 on acpi0 cpu19: numa-domain 0 on acpi0 cpu20: numa-domain 0 on acpi0 cpu21: numa-domain 0 on acpi0 cpu22: numa-domain 0 on acpi0 cpu23: numa-domain 0 on acpi0 cpu24: numa-domain 1 on acpi0 cpu25: numa-domain 1 on acpi0 cpu26: numa-domain 1 on acpi0 cpu27: numa-domain 1 on acpi0 cpu28: numa-domain 1 on acpi0 cpu29: numa-domain 1 on acpi0 cpu30: numa-domain 1 on acpi0 cpu31: numa-domain 1 on acpi0 cpu32: numa-domain 1 on acpi0 cpu33: numa-domain 1 on acpi0 cpu34: numa-domain 1 on acpi0 cpu35: numa-domain 1 on acpi0 cpu36: numa-domain 1 on acpi0 cpu37: numa-domain 1 on acpi0 cpu38: numa-domain 1 on acpi0 cpu39: numa-domain 1 on acpi0 cpu40: numa-domain 1 on acpi0 cpu41: numa-domain 1 on acpi0 cpu42: numa-domain 1 on acpi0 cpu43: numa-domain 1 on acpi0 cpu44: numa-domain 1 on acpi0 cpu45: numa-domain 1 on acpi0 cpu46: numa-domain 1 on acpi0 cpu47: numa-domain 1 on acpi0 atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 24000000 Hz quality 950 Event timer "HPET" frequency 24000000 Hz quality 350 Event timer "HPET1" frequency 24000000 Hz quality 340 Event timer "HPET2" frequency 24000000 Hz quality 340 Event timer "HPET3" frequency 24000000 Hz quality 340 Event timer "HPET4" frequency 24000000 Hz quality 340 Event timer "HPET5" frequency 24000000 Hz quality 340 Event timer "HPET6" frequency 24000000 Hz quality 340 Event timer "HPET7" frequency 24000000 Hz quality 340 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_syscontainer0: on acpi0 acpi_syscontainer1: on acpi0 pcib0: port 0xcf8-0xcff numa-domain 0 on acpi0 pcib0: _OSC returned error 0x10 pci0: numa-domain 0 on pcib0 pci0: at device 8.1 (no driver attached) pci0: at device 17.0 (no driver attached) pci0: at device 17.1 (no driver attached) ahci0: port 0x3070-0x3077,0x3060-0x3063,0x3020-0x303f mem 0x9d206000-0x9d207fff,0x9d209000-0x9d2090ff,0x9d180000-0x9d1fffff irq 16 at device 17.5 numa-domain 0 on pci0 ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahciem0: on ahci0 xhci0: mem 0x383ffff00000-0x383ffff0ffff irq 16 at device 20.0 numa-domain 0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0: waiting for BIOS to give up control xhci_interrupt: host controller halted usbus0 numa-domain 0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) pci0: at device 22.4 (no driver attached) ahci1: port 0x3050-0x3057,0x3040-0x3043,0x3000-0x301f mem 0x9d204000-0x9d205fff,0x9d208000-0x9d2080ff,0x9d100000-0x9d17ffff irq 16 at device 23.0 numa-domain 0 on pci0 ahci1: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported ahcich6: at channel 0 on ahci1 ahcich7: at channel 1 on ahci1 ahcich8: at channel 2 on ahci1 ahcich9: at channel 3 on ahci1 ahcich10: at channel 4 on ahci1 ahcich11: at channel 5 on ahci1 ahcich12: at channel 6 on ahci1 ahcich13: at channel 7 on ahci1 ahciem1: on ahci1 pcib1: irq 16 at device 28.0 numa-domain 0 on pci0 pci1: numa-domain 0 on pcib1 pcib2: irq 17 at device 28.5 numa-domain 0 on pci0 pci2: numa-domain 0 on pcib2 pcib3: irq 17 at device 0.0 numa-domain 0 on pci2 pci3: numa-domain 0 on pcib3 vgapci0: port 0x2000-0x207f mem 0x9c000000-0x9cffffff,0x9d000000-0x9d01ffff irq 17 at device 0.0 numa-domain 0 on pci3 vgapci0: Boot video device isab0: at device 31.0 numa-domain 0 on pci0 isa0: numa-domain 0 on isab0 pci0: at device 31.2 (no driver attached) pci0: at device 31.5 (no driver attached) pcib4: numa-domain 0 on acpi0 pcib4: _OSC returned error 0x10 pci4: numa-domain 0 on pcib4 pcib5: irq 39 at device 0.0 numa-domain 0 on pci4 pci5: numa-domain 0 on pcib5 pcib6: mem 0xaae00000-0xaae1ffff irq 32 at device 0.0 numa-domain 0 on pci5 pci6: numa-domain 0 on pcib6 pcib7: irq 38 at device 3.0 numa-domain 0 on pci6 pci7: numa-domain 0 on pcib7 ixl0: mem 0xa9000000-0xa9ffffff,0xaa008000-0xaa00ffff irq 38 at device 0.0 numa-domain 0 on pci7 ixl0: using 1024 tx descriptors and 1024 rx descriptors ixl0: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared ixl0: Using MSIX interrupts with 9 vectors ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active ixl0: Ethernet address: ac:1f:6b:61:54:06 ixl0: SR-IOV ready queues is 0xfffffe0001d13000 ixl0: netmap queues/slots: TX 8/1024, RX 8/1024 ixl1: mem 0xa8000000-0xa8ffffff,0xaa000000-0xaa007fff irq 38 at device 0.1 numa-domain 0 on pci7 ixl1: using 1024 tx descriptors and 1024 rx descriptors ixl1: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared ixl1: Using MSIX interrupts with 9 vectors ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active ixl1: Ethernet address: ac:1f:6b:61:54:07 ixl1: SR-IOV ready queues is 0xfffffe0001e69000 ixl1: netmap queues/slots: TX 8/1024, RX 8/1024 pcib8: numa-domain 0 on acpi0 pcib8: _OSC returned error 0x10 pci8: numa-domain 0 on pcib8 pcib9: irq 47 at device 2.0 numa-domain 0 on pci8 pci9: numa-domain 0 on pcib9 mpr0: port 0x7000-0x70ff mem 0xb8640000-0xb864ffff,0xb8600000-0xb863ffff irq 42 at device 0.0 numa-domain 0 on pci9 mpr0: Firmware: 15.00.03.00, Driver: 18.03.00.00-fbsd mpr0: IOCCapabilities: 7a85c pcib10: numa-domain 0 on acpi0 pcib10: _OSC returned error 0x10 pci10: numa-domain 0 on pcib10 pci10: at device 14.0 (no driver attached) pci10: at device 15.0 (no driver attached) pci10: at device 18.0 (no driver attached) pci10: at device 18.1 (no driver attached) pcib11: numa-domain 1 on acpi0 ixl0: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None ixl0: link state changed to UP ixl1: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: Full ixl1: link state changed to UP pcib11: _OSC returned error 0x10 pci11: numa-domain 1 on pcib11 pci11: at device 8.1 (no driver attached) pcib12: numa-domain 1 on acpi0 pcib12: _OSC returned error 0x10 pci12: numa-domain 1 on pcib12 pcib13: numa-domain 1 on acpi0 pcib13: _OSC returned error 0x10 pci13: numa-domain 1 on pcib13 pcib14: numa-domain 1 on acpi0 pcib14: _OSC returned error 0x10 pci14: numa-domain 1 on pcib14 pci14: at device 14.0 (no driver attached) pci14: at device 15.0 (no driver attached) pci14: at device 18.0 (no driver attached) pci14: at device 18.1 (no driver attached) uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 orm0: at iomem 0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range est0: numa-domain 0 on cpu0 est1: numa-domain 0 on cpu1 est2: numa-domain 0 on cpu2 est3: numa-domain 0 on cpu3 est4: numa-domain 0 on cpu4 est5: numa-domain 0 on cpu5 est6: numa-domain 0 on cpu6 est7: numa-domain 0 on cpu7 est8: numa-domain 0 on cpu8 est9: numa-domain 0 on cpu9 est10: numa-domain 0 on cpu10 est11: numa-domain 0 on cpu11 est12: numa-domain 0 on cpu12 est13: numa-domain 0 on cpu13 est14: numa-domain 0 on cpu14 est15: numa-domain 0 on cpu15 est16: numa-domain 0 on cpu16 est17: numa-domain 0 on cpu17 est18: numa-domain 0 on cpu18 est19: numa-domain 0 on cpu19 est20: numa-domain 0 on cpu20 est21: numa-domain 0 on cpu21 est22: numa-domain 0 on cpu22 est23: numa-domain 0 on cpu23 est24: numa-domain 1 on cpu24 est25: numa-domain 1 on cpu25 est26: numa-domain 1 on cpu26 est27: numa-domain 1 on cpu27 est28: numa-domain 1 on cpu28 est29: numa-domain 1 on cpu29 est30: numa-domain 1 on cpu30 est31: numa-domain 1 on cpu31 est32: numa-domain 1 on cpu32 est33: numa-domain 1 on cpu33 est34: numa-domain 1 on cpu34 est35: numa-domain 1 on cpu35 est36: numa-domain 1 on cpu36 est37: numa-domain 1 on cpu37 est38: numa-domain 1 on cpu38 est39: numa-domain 1 on cpu39 est40: numa-domain 1 on cpu40 est41: numa-domain 1 on cpu41 est42: numa-domain 1 on cpu42 est43: numa-domain 1 on cpu43 est44: numa-domain 1 on cpu44 est45: numa-domain 1 on cpu45 est46: numa-domain 1 on cpu46 est47: numa-domain 1 on cpu47 random: unblocking device. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec ugen0.1: <0x8086 XHCI root HUB> at usbus0 mpr0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 SAS Address from SAS device page0 = 5000c500955fb571 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000a> enclosureHandle<0x0002> slot 0 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c5009550e4f1 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000b> enclosureHandle<0x0002> slot 1 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c50095518c95 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000c> enclosureHandle<0x0002> slot 2 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c500955fb3c5 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000d> enclosureHandle<0x0002> slot 3 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c500955fb021 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000e> enclosureHandle<0x0002> slot 4 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c5009550e891 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000f> enclosureHandle<0x0002> slot 5 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 500304801eb5dbfd mpr0: Found device <4411,End Device> <12.0Gbps> handle<0x0010> enclosureHandle<0x0002> slot 12 mpr0: At enclosure level 0 and connector name ( ) ses0 at ahciem0 bus 0 scbus6 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ses1 at ahciem1 bus 0 scbus15 target 0 lun 0 ses1: SEMB S-E-S 2.00 device ses1: SEMB SES Device ses2 at mpr0 bus 0 scbus16 target 20 lun 0 ses2: Fixed Enclosure Services SPC-3 SCSI device ses2: 1200.000MB/s transfers ses2: Command Queueing enabled ses2: SCSI-3 ENC Device ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 ada0: ACS-3 ATA SATA 3.x device ada0: Serial Number BTYS81150CWH240AGN ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada0: Command Queueing enabled ada0: 228936MB (468862128 512 byte sectors) ada1 at ahcich5 bus 0 scbus5 target 0 lun 0 ada1: ACS-3 ATA SATA 3.x device ada1: Serial Number BTYS814205JS240AGN ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada1: Command Queueing enabled ada1: 228936MB (468862128 512 byte sectors) uhub0: 26 ports with 26 removable, self powered ses2: pass4,da0: Element descriptor: 'Slot00' da1 at mpr0 bus 0 scbus16 target 9 lun 0 da2 at mpr0 bus 0 scbus16 target 10 lun 0 da0 at mpr0 bus 0 scbus16 target 8 lun 0 da5 at mpr0 bus 0 scbus16 target 13 lun 0 da4 at mpr0 bus 0 scbus16 target 12 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number ZC15T3GB0000C832EM0C da2: 1200.000MB/s transfers da2: Command Queueing enabled da2: 3815447MB (976754646 4096 byte sectors) da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number ZC1606NJ0000R833G9JK da0: 1200.000MB/s transfers da0: Command Queueing enabled da0: 3815447MB (976754646 4096 byte sectors) da4: Fixed Direct Access SPC-4 SCSI device da4: Serial Number ZC1606RR0000R833G8YR da4: 1200.000MB/s transfers da4: Command Queueing enabled da4: 3815447MB (976754646 4096 byte sectors) ses2: pass4,da0: SAS Device Slot Element: 1 Phys at Slot 0 ses2: phy 0: SAS device type 1 id 0 da5: da1: Fixed Direct Access SPC-4 SCSI device da1: Serial Number ZC15V7DV0000C8258M38 ugen0.2: at usbus0 da1: 1200.000MB/s transfers da1: Command Queueing enabled da1: 3815447MB (976754646 4096 byte sectors) Fixed Direct Access SPC-4 SCSI device ukbd0da5: Serial Number ZC15KB320000R832RAR7 da5: 1200.000MB/s transfers da5: Command Queueing enabled da5: 3815447MB (976754646 4096 byte sectors) numa-domain 0 on uhub0 da3 at mpr0 bus 0 scbus16 target 11 lun 0 ukbd0: on usbus0 kbd2 at ukbd0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb571 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number ZC1606Q80000R833WKE8 da3: 1200.000MB/s transfers da3: Command Queueing enabled da3: 3815447MB (976754646 4096 byte sectors) ses2: pass5,da1: Element descriptor: 'Slot01' ses2: pass5,da1: SAS Device Slot Element: 1 Phys at Slot 1 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e4f1 ses2: pass6,da2: Element descriptor: 'Slot02' ses2: pass6,da2: SAS Device Slot Element: 1 Phys at Slot 2 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c50095518c95 ses2: pass7,da3: Element descriptor: 'Slot03' ses2: pass7,da3: SAS Device Slot Element: 1 Phys at Slot 3 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb3c5 ses2: pass8,da4: Element descriptor: 'Slot04' ses2: pass8,da4: SAS Device Slot Element: 1 Phys at Slot 4 ugen0.3: at usbus0 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb021 ses2: pass9,da5: Element descriptor: 'Slot05' ses2: pass9,da5: SAS Device Slot Element: 1 Phys at Slot 5 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e891 uhub1 numa-domain 0 on uhub0 uhub1: on usbus0 Trying to mount root from zfs:tank/default/root []... Root mount waiting for: usbus0 uhub1: 4 ports with 3 removable, self powered ugen0.4: at usbus0 ukbd1 numa-domain 0 on uhub1 ukbd1: on usbus0 kbd3 at ukbd1 lo0: link state changed to UP ums0 numa-domain 0 on uhub1 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=0 And pciconf -lvb: hostb0@pci0:0:0:0: class=0x060000 card=0x098115d9 chip=0x20208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E DMI3 Registers' class = bridge subclass = HOST-PCI none0@pci0:0:4:0: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff2c000, size 16384, enabled none1@pci0:0:4:1: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff28000, size 16384, enabled none2@pci0:0:4:2: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff24000, size 16384, enabled none3@pci0:0:4:3: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff20000, size 16384, enabled none4@pci0:0:4:4: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff1c000, size 16384, enabled none5@pci0:0:4:5: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff18000, size 16384, enabled none6@pci0:0:4:6: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff14000, size 16384, enabled none7@pci0:0:4:7: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x383ffff10000, size 16384, enabled none8@pci0:0:5:0: class=0x088000 card=0x00008086 chip=0x20248086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E MM/Vt-d Configuration Registers' class = base peripheral none9@pci0:0:5:2: class=0x088000 card=0x00000000 chip=0x20258086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral ioapic0@pci0:0:5:4: class=0x080020 card=0x20268086 chip=0x20268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0x9d20a000, size 4096, enabled none10@pci0:0:8:0: class=0x088000 card=0x00008086 chip=0x20148086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = base peripheral none11@pci0:0:8:1: class=0x110100 card=0x00008086 chip=0x20158086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = dasp subclass = performance counters none12@pci0:0:8:2: class=0x088000 card=0x00008086 chip=0x20168086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = base peripheral none13@pci0:0:17:0: class=0xff0000 card=0x098115d9 chip=0xa1ec8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' none14@pci0:0:17:1: class=0xff0000 card=0x098115d9 chip=0xa1ed8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' ahci0@pci0:0:17:5: class=0x010601 card=0x098115d9 chip=0xa1d28086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg SSATA Controller [AHCI mode]' class = mass storage subclass = SATA bar [10] = type Memory, range 32, base 0x9d206000, size 8192, enabled bar [14] = type Memory, range 32, base 0x9d209000, size 256, enabled bar [18] = type I/O Port, range 32, base 0x3070, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x3060, size 4, enabled bar [20] = type I/O Port, range 32, base 0x3020, size 32, enabled bar [24] = type Memory, range 32, base 0x9d180000, size 524288, enabled xhci0@pci0:0:20:0: class=0x0c0330 card=0x098115d9 chip=0xa1af8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg USB 3.0 xHCI Controller' class = serial bus subclass = USB bar [10] = type Memory, range 64, base 0x383ffff00000, size 65536, enabled none15@pci0:0:20:2: class=0x118000 card=0x098115d9 chip=0xa1b18086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg Thermal Subsystem' class = dasp bar [10] = type Memory, range 64, base 0x383ffff33000, size 4096, enabled none16@pci0:0:22:0: class=0x078000 card=0x098115d9 chip=0xa1ba8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg CSME: HECI' class = simple comms bar [10] = type Memory, range 64, base 0x383ffff32000, size 4096, enabled none17@pci0:0:22:1: class=0x078000 card=0x098115d9 chip=0xa1bb8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg CSME: HECI' class = simple comms bar [10] = type Memory, range 64, base 0x383ffff31000, size 4096, enabled none18@pci0:0:22:4: class=0x078000 card=0x098115d9 chip=0xa1be8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg CSME: HECI' class = simple comms bar [10] = type Memory, range 64, base 0x383ffff30000, size 4096, enabled ahci1@pci0:0:23:0: class=0x010601 card=0x098115d9 chip=0xa1828086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg SATA Controller [AHCI mode]' class = mass storage subclass = SATA bar [10] = type Memory, range 32, base 0x9d204000, size 8192, enabled bar [14] = type Memory, range 32, base 0x9d208000, size 256, enabled bar [18] = type I/O Port, range 32, base 0x3050, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x3040, size 4, enabled bar [20] = type I/O Port, range 32, base 0x3000, size 32, enabled bar [24] = type Memory, range 32, base 0x9d100000, size 524288, enabled pcib1@pci0:0:28:0: class=0x060400 card=0x098115d9 chip=0xa1908086 rev=0xf9 hdr=0x01 vendor = 'Intel Corporation' device = 'Lewisburg PCI Express Root Port' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:5: class=0x060400 card=0x098115d9 chip=0xa1958086 rev=0xf9 hdr=0x01 vendor = 'Intel Corporation' device = 'Lewisburg PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x098115d9 chip=0xa1c38086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg LPC Controller' class = bridge subclass = PCI-ISA none19@pci0:0:31:2: class=0x058000 card=0x098115d9 chip=0xa1a18086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg PMC' class = memory bar [10] = type Memory, range 32, base 0x9d200000, size 16384, enabled none20@pci0:0:31:4: class=0x0c0500 card=0x098115d9 chip=0xa1a38086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg SMBus' class = serial bus subclass = SMBus bar [10] = type Memory, range 64, base 0, size 256, disabled bar [20] = type I/O Port, range 32, base 0x780, size 32, enabled none21@pci0:0:31:5: class=0x0c8000 card=0x098115d9 chip=0xa1a48086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Lewisburg SPI Controller' class = serial bus bar [10] = type Memory, range 32, base 0xfe010000, size 4096, enabled pcib3@pci0:2:0:0: class=0x060400 card=0x11501a03 chip=0x11501a03 rev=0x04 hdr=0x01 vendor = 'ASPEED Technology, Inc.' device = 'AST1150 PCI-to-PCI Bridge' class = bridge subclass = PCI-PCI vgapci0@pci0:3:0:0: class=0x030000 card=0x098115d9 chip=0x20001a03 rev=0x41 hdr=0x00 vendor = 'ASPEED Technology, Inc.' device = 'ASPEED Graphics Family' class = display subclass = VGA bar [10] = type Memory, range 32, base 0x9c000000, size 16777216, enabled bar [14] = type Memory, range 32, base 0x9d000000, size 131072, enabled bar [18] = type I/O Port, range 32, base 0x2000, size 128, enabled pcib5@pci0:23:0:0: class=0x060400 card=0x098115d9 chip=0x20308086 rev=0x04 hdr=0x01 vendor = 'Intel Corporation' device = 'Sky Lake-E PCI Express Root Port A' class = bridge subclass = PCI-PCI none22@pci0:23:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none23@pci0:23:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic1@pci0:23:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xaaf00000, size 4096, enabled none24@pci0:23:8:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none25@pci0:23:8:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none26@pci0:23:8:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none27@pci0:23:8:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none28@pci0:23:8:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none29@pci0:23:8:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none30@pci0:23:8:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none31@pci0:23:8:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none32@pci0:23:9:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none33@pci0:23:9:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none34@pci0:23:9:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none35@pci0:23:9:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none36@pci0:23:9:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none37@pci0:23:9:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none38@pci0:23:9:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none39@pci0:23:9:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none40@pci0:23:10:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none41@pci0:23:10:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none42@pci0:23:14:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none43@pci0:23:14:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none44@pci0:23:14:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none45@pci0:23:14:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none46@pci0:23:14:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none47@pci0:23:14:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none48@pci0:23:14:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none49@pci0:23:14:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none50@pci0:23:15:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none51@pci0:23:15:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none52@pci0:23:15:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none53@pci0:23:15:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none54@pci0:23:15:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none55@pci0:23:15:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none56@pci0:23:15:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none57@pci0:23:15:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none58@pci0:23:16:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none59@pci0:23:16:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none60@pci0:23:29:0: class=0x088000 card=0x00008086 chip=0x20548086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none61@pci0:23:29:1: class=0x088000 card=0x00008086 chip=0x20558086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none62@pci0:23:29:2: class=0x088000 card=0x00008086 chip=0x20568086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none63@pci0:23:29:3: class=0x088000 card=0x00008086 chip=0x20578086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none64@pci0:23:30:0: class=0x088000 card=0x00008086 chip=0x20808086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none65@pci0:23:30:1: class=0x088000 card=0x00008086 chip=0x20818086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none66@pci0:23:30:2: class=0x088000 card=0x00008086 chip=0x20828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none67@pci0:23:30:3: class=0x088000 card=0x00008086 chip=0x20838086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none68@pci0:23:30:4: class=0x088000 card=0x00008086 chip=0x20848086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none69@pci0:23:30:5: class=0x088000 card=0x00008086 chip=0x20858086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none70@pci0:23:30:6: class=0x088000 card=0x00008086 chip=0x20868086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral pcib6@pci0:24:0:0: class=0x060400 card=0xdeadbeef chip=0x37c08086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI bar [10] = type Memory, range 64, base 0xaae00000, size 131072, enabled pcib7@pci0:25:3:0: class=0x060400 card=0xdeadbeef chip=0x37c58086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ixl0@pci0:26:0:0: class=0x020000 card=0x37d215d9 chip=0x37d28086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection X722 for 10GBASE-T' class = network subclass = ethernet bar [10] = type Prefetchable Memory, range 64, base 0xa9000000, size 16777216, enabled bar [1c] = type Prefetchable Memory, range 64, base 0xaa008000, size 32768, enabled ixl1@pci0:26:0:1: class=0x020000 card=0x37d215d9 chip=0x37d28086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection X722 for 10GBASE-T' class = network subclass = ethernet bar [10] = type Prefetchable Memory, range 64, base 0xa8000000, size 16777216, enabled bar [1c] = type Prefetchable Memory, range 64, base 0xaa000000, size 32768, enabled pcib9@pci0:58:2:0: class=0x060400 card=0x098115d9 chip=0x20328086 rev=0x04 hdr=0x01 vendor = 'Intel Corporation' device = 'Sky Lake-E PCI Express Root Port C' class = bridge subclass = PCI-PCI none71@pci0:58:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none72@pci0:58:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic2@pci0:58:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xb8700000, size 4096, enabled none73@pci0:58:8:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none74@pci0:58:9:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none75@pci0:58:10:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none76@pci0:58:10:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none77@pci0:58:10:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none78@pci0:58:10:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none79@pci0:58:10:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none80@pci0:58:10:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none81@pci0:58:10:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none82@pci0:58:10:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none83@pci0:58:11:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none84@pci0:58:11:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none85@pci0:58:11:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none86@pci0:58:11:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none87@pci0:58:12:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none88@pci0:58:12:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none89@pci0:58:12:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none90@pci0:58:12:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none91@pci0:58:12:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none92@pci0:58:12:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none93@pci0:58:12:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none94@pci0:58:12:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none95@pci0:58:13:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none96@pci0:58:13:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none97@pci0:58:13:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none98@pci0:58:13:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral mpr0@pci0:59:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' class = mass storage subclass = SAS bar [10] = type I/O Port, range 32, base 0x7000, size 256, enabled bar [14] = type Memory, range 64, base 0xb8640000, size 65536, enabled bar [1c] = type Memory, range 64, base 0xb8600000, size 262144, enabled none99@pci0:93:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none100@pci0:93:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic3@pci0:93:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xc5f00000, size 4096, enabled none101@pci0:93:14:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = dasp subclass = performance counters none102@pci0:93:14:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none103@pci0:93:15:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = dasp subclass = performance counters none104@pci0:93:15:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none105@pci0:93:18:0: class=0x110100 card=0x00008086 chip=0x204c8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = dasp subclass = performance counters none106@pci0:93:18:1: class=0x110100 card=0x00008086 chip=0x204d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = dasp subclass = performance counters none107@pci0:93:18:2: class=0x088000 card=0x00008086 chip=0x204e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = base peripheral none108@pci0:93:21:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral none109@pci0:93:22:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral none110@pci0:93:22:4: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral none111@pci0:128:4:0: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff1c000, size 16384, enabled none112@pci0:128:4:1: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff18000, size 16384, enabled none113@pci0:128:4:2: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff14000, size 16384, enabled none114@pci0:128:4:3: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff10000, size 16384, enabled none115@pci0:128:4:4: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff0c000, size 16384, enabled none116@pci0:128:4:5: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff08000, size 16384, enabled none117@pci0:128:4:6: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff04000, size 16384, enabled none118@pci0:128:4:7: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CBDMA Registers' class = base peripheral bar [10] = type Memory, range 64, base 0x393ffff00000, size 16384, enabled none119@pci0:128:5:0: class=0x088000 card=0x00008086 chip=0x20248086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E MM/Vt-d Configuration Registers' class = base peripheral none120@pci0:128:5:2: class=0x088000 card=0x00000000 chip=0x20258086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral ioapic4@pci0:128:5:4: class=0x080020 card=0x20268086 chip=0x20268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xd3700000, size 4096, enabled none121@pci0:128:8:0: class=0x088000 card=0x00008086 chip=0x20148086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = base peripheral none122@pci0:128:8:1: class=0x110100 card=0x00008086 chip=0x20158086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = dasp subclass = performance counters none123@pci0:128:8:2: class=0x088000 card=0x00008086 chip=0x20168086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E Ubox Registers' class = base peripheral none124@pci0:133:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none125@pci0:133:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic5@pci0:133:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xe0f00000, size 4096, enabled none126@pci0:133:8:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none127@pci0:133:8:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none128@pci0:133:8:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none129@pci0:133:8:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none130@pci0:133:8:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none131@pci0:133:8:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none132@pci0:133:8:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none133@pci0:133:8:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none134@pci0:133:9:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none135@pci0:133:9:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none136@pci0:133:9:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none137@pci0:133:9:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none138@pci0:133:9:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none139@pci0:133:9:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none140@pci0:133:9:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none141@pci0:133:9:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none142@pci0:133:10:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none143@pci0:133:10:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none144@pci0:133:14:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none145@pci0:133:14:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none146@pci0:133:14:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none147@pci0:133:14:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none148@pci0:133:14:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none149@pci0:133:14:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none150@pci0:133:14:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none151@pci0:133:14:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none152@pci0:133:15:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none153@pci0:133:15:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none154@pci0:133:15:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none155@pci0:133:15:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none156@pci0:133:15:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none157@pci0:133:15:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none158@pci0:133:15:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none159@pci0:133:15:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none160@pci0:133:16:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none161@pci0:133:16:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none162@pci0:133:29:0: class=0x088000 card=0x00008086 chip=0x20548086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none163@pci0:133:29:1: class=0x088000 card=0x00008086 chip=0x20558086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none164@pci0:133:29:2: class=0x088000 card=0x00008086 chip=0x20568086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none165@pci0:133:29:3: class=0x088000 card=0x00008086 chip=0x20578086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E CHA Registers' class = base peripheral none166@pci0:133:30:0: class=0x088000 card=0x00008086 chip=0x20808086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none167@pci0:133:30:1: class=0x088000 card=0x00008086 chip=0x20818086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none168@pci0:133:30:2: class=0x088000 card=0x00008086 chip=0x20828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none169@pci0:133:30:3: class=0x088000 card=0x00008086 chip=0x20838086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none170@pci0:133:30:4: class=0x088000 card=0x00008086 chip=0x20848086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none171@pci0:133:30:5: class=0x088000 card=0x00008086 chip=0x20858086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none172@pci0:133:30:6: class=0x088000 card=0x00008086 chip=0x20868086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E PCU Registers' class = base peripheral none173@pci0:174:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none174@pci0:174:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic6@pci0:174:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xee700000, size 4096, enabled none175@pci0:174:8:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none176@pci0:174:9:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none177@pci0:174:10:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none178@pci0:174:10:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none179@pci0:174:10:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none180@pci0:174:10:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none181@pci0:174:10:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none182@pci0:174:10:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none183@pci0:174:10:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none184@pci0:174:10:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none185@pci0:174:11:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none186@pci0:174:11:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none187@pci0:174:11:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none188@pci0:174:11:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none189@pci0:174:12:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none190@pci0:174:12:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none191@pci0:174:12:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none192@pci0:174:12:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none193@pci0:174:12:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none194@pci0:174:12:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none195@pci0:174:12:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none196@pci0:174:12:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none197@pci0:174:13:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none198@pci0:174:13:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none199@pci0:174:13:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none200@pci0:174:13:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none201@pci0:215:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none202@pci0:215:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E RAS Configuration Registers' class = base peripheral ioapic7@pci0:215:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral subclass = interrupt controller bar [10] = type Memory, range 32, base 0xfbf00000, size 4096, enabled none203@pci0:215:14:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = dasp subclass = performance counters none204@pci0:215:14:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none205@pci0:215:15:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = dasp subclass = performance counters none206@pci0:215:15:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = base peripheral none207@pci0:215:18:0: class=0x110100 card=0x00008086 chip=0x204c8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = dasp subclass = performance counters none208@pci0:215:18:1: class=0x110100 card=0x00008086 chip=0x204d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = dasp subclass = performance counters none209@pci0:215:18:2: class=0x088000 card=0x00008086 chip=0x204e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M3KTI Registers' class = base peripheral none210@pci0:215:21:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral none211@pci0:215:22:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral none212@pci0:215:22:4: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Sky Lake-E M2PCI Registers' class = base peripheral # grep swap /etc/fstab ; echo #/dev/mirror/swap none swap sw /dev/gpt/swap0 none swap sw #/dev/gpt/swap1 none swap sw # swapinfo -h Device 1024-blocks Used Avail Capacity /dev/gpt/swap0 16777216 0B 16G 0% # ls -ltr /var/crash/ total 3844652 -rw-r--r-- 1 root wheel 5 Jun 21 21:34 minfree -rw------- 1 root wheel 462 Jul 5 11:46 info.0 -rw------- 1 root wheel 5043531776 Jul 5 11:47 vmcore.0 -rw------- 1 root wheel 128912 Jul 5 11:47 core.txt.0 -rw------- 1 root wheel 464 Jul 6 12:24 info.1 -rw------- 1 root wheel 3628683264 Jul 6 12:24 vmcore.1 -rw------- 1 root wheel 127947 Jul 6 12:24 core.txt.1 -rw-r--r-- 1 root wheel 639 Jul 9 12:51 ls.out.0 -rw-r--r-- 1 root wheel 3960 Jul 11 06:36 zpool-iostat.out -rw------- 1 root wheel 464 Jul 11 12:47 info.2 -rw------- 1 root wheel 3777585152 Jul 11 12:48 vmcore.2 -rw------- 1 root wheel 127775 Jul 11 12:48 core.txt.2 -rw-r--r-- 1 root wheel 0 Jul 11 13:12 zfs-stress.start -rw-r--r-- 1 root wheel 2 Jul 11 13:37 bounds -rw------- 1 root wheel 458 Jul 11 13:37 info.3 -rw------- 1 root wheel 7352229888 Jul 11 13:38 vmcore.3 lrwxr-xr-x 1 root wheel 6 Jul 11 13:38 info.last@ -> info.3 lrwxr-xr-x 1 root wheel 8 Jul 11 13:38 vmcore.last@ -> vmcore.3 -rw------- 1 root wheel 143973 Jul 11 13:38 core.txt.3 From owner-freebsd-questions@freebsd.org Wed Jul 11 22:54:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3531A102A974 for ; Wed, 11 Jul 2018 22:54:04 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 B6F008C414 for ; Wed, 11 Jul 2018 22:54:03 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x432.google.com with SMTP id c13-v6so19681558wrt.1 for ; Wed, 11 Jul 2018 15:54:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=h65Mk3FiTBIrCIHhccn8y66AbBMV36JeCLU+KxL0kSs=; b=lRAw01y5tbXjn4ZkURquwWVu5sZDtZW5v7rtVijreIUa23jKZoTGZlgSJgxhKaDQHm 9YvghTdky1URKtD1nyWHBLaN3IGs14yi1n8K1EkmdT1ryF8gZ1Xb8x7BCeAKaU7zO2Bu LR50m3l47KTZeKeZDUDzjVPxZw1/hSxS77DQR9ZdBfHnz0KETT5YpOMNyw7si2Is9ecd iM3HnX2dOwFEeuDPeHGjx+Gc9SfTRv+Yvrns3tfnUSFA37jLdotPYPhiPXysUzXSDk5j Dnn4pTsp3USLGqCzxRupgU2mx88Xub/C6BHeUE0OGXu4dYwt56OzaZP/bInHUWgSxegv zCxA== X-Gm-Message-State: AOUpUlFJx/45CJCfAmfam20Le/p7qxUbHz08rRzjPLv+TTXGGnRwK/Hz 8YOhEMMF/Qq2hppuPvep0a8mfA== X-Google-Smtp-Source: AAOMgpfwgjKP9OCuN6UYMtrJi8jcDFkAG2B94E+XJrekxc4nMdu70Nx7CoQ7/pOhSmSHLQ0Etap9pw== X-Received: by 2002:adf:bb08:: with SMTP id r8-v6mr306260wrg.244.1531349641568; Wed, 11 Jul 2018 15:54:01 -0700 (PDT) Received: from gumby.homeunix.com ([90.220.84.208]) by smtp.gmail.com with ESMTPSA id x6-v6sm23811098wrd.57.2018.07.11.15.53.59 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 11 Jul 2018 15:54:00 -0700 (PDT) Date: Wed, 11 Jul 2018 23:53:57 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: [commercial] sendmail setup request Message-ID: <20180711235357.4fd62b47@gumby.homeunix.com> In-Reply-To: References: <20180710184032.55346a5d@gumby.homeunix.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 22:54:04 -0000 On Wed, 11 Jul 2018 09:36:22 +0700 Olivier wrote: > RW via freebsd-questions writes: > > > On Mon, 9 Jul 2018 08:35:26 +0200 > > Polytropon wrote: > > > > > > > >> but fetchmail can "copy" messages, i. e., leave them on the server, > >> and upon invocation, only load the unread messages). Check > >> "man fetchmail" for the keep / nokeep keyword. > > > > It's already been clarified that the fetchmail instance would also > > be remote, so this doesn't apply to the OP, but for the record, > > getmail handles the above better. > > That is not exacteky what I understood. > > I think that all the OP wants a way to "use mailx on his > mailbiox". Because mailx does not rely on a network protocol, but > rather only works on a mbox file local to the machine where mailx > command is used, he needs a way to get the messages to the machine > where he will be using the command mailx. My understanding is that he wants to be able to ssh into an internet accessible remote server and read his mail, which is currently on a remote IMAP server. As fetchmail would be downloading the mail on an internet accessible server there's no need to leave copies on the IMAP server. Hence the fetchmail 'keep' option is not relevant to the OP and neither are my comments about it. The reason I commented is that fetchmail gets more advocacy than it deserves and I didn't want anyone to get the idea that running fetchmail --keep is a good idea, when it's practically unusable in most common use cases. If you want to retrieve mail from an IMAP server and leave a copy behind it's almost always better to either switch to getmail or work around the problem by having a server-side filter file an extra copy of each mail into a dedicated folder where fetchmail can retrieve and delete. From owner-freebsd-questions@freebsd.org Wed Jul 11 23:25:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B259A102E0F8 for ; Wed, 11 Jul 2018 23:25:28 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5733E8D695 for ; Wed, 11 Jul 2018 23:25:28 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fdOU1-000AcM-KB for freebsd-questions@freebsd.org; Wed, 11 Jul 2018 17:25:17 -0600 Date: Wed, 11 Jul 2018 17:25:17 -0600 From: The Doctor To: freebsd-questions@freebsd.org Subject: recovering an overwritten zfs partition Message-ID: <20180711232517.GA38941@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 23:25:28 -0000 I wonder if an overwritten zfs partition can be recovered? Well, I had to rebuild this server after I corruprted the max sw parameter. Could not back up in time. I wonder if a data recovery is possible. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Our great weariness comes from work not done. -Eric Hoffer From owner-freebsd-questions@freebsd.org Wed Jul 11 23:25:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40AB7102E1DD for ; Wed, 11 Jul 2018 23:25:55 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0B3F8D6CB for ; Wed, 11 Jul 2018 23:25:54 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPA (Nemesis) id 0MeHvO-1fQoHM16Lu-00Pv78; Thu, 12 Jul 2018 01:20:34 +0200 Date: Thu, 12 Jul 2018 01:20:33 +0200 From: Polytropon To: David Johnson Cc: freebsd-questions@freebsd.org Subject: Re: Help with an Urgent Matter Message-Id: <20180712012033.638fa1de.freebsd@edvax.de> In-Reply-To: References: 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-Provags-ID: V03:K1:G2AE22h2/66NAxU3n6J+mfPbP3npiH0adPk7IktqqunKY2ftEVD Ngd1yzNoz4sPp3KuY3src1QvqBEjqJIs+fpLWWKUVmRbSF92sxs6IZbUqTg+wNWQboi58wZ JO91IFHFMRvJTc1SauClHIF069bubu66zwlHFyOoLnxMAvNKNBg2duSajLfyyD5d6/y5iwE ZbYbj8iKgNWV2lDtzcIrw== X-UI-Out-Filterresults: notjunk:1;V01:K0:KKvIr4sJ3O4=:VpI3hL9LraPL72jbF2m/e1 66Yfe5krrBTSGw/vssfqLcURmozq9U/JrDbV5mbVrL5E+L8BpQs+ER7b/Dz60uelAkPUCnbv+ DYTqoI/sjmvUVMhl3ByD07V3wLMi8o/EA25+Bgkyzw56HN/Zs9olvalqnT2uY1eUepVgv/gS0 z7d4Ey+8VL32nJd7Cv7AL2QVq+0jAWaBOQrD4VtvYYQvuijIZRQsUZcFFAlKMc0MDzc2WBywh pZaRo1lKDFHulEcocvNhZ5HIpi2yZH5tTyQt/UtvY23xcbFcur/Cp0gZK4CRgvTSnZlywbAvU eWA+6oKiHLRvvVzId0rCQSX9bONqFHXKnHlNCSDqEopa4vdJ/iymWDzBaOwSdigBsoHUbi3Ix sH/jPOt7xpSsGFEB5bv43Mt+jnUvBUZzuyMWJy5pr/+j4tYkhN5kY0QsiTvehSIOCuA/8ILEv 97TocJXrIauHOEt/GgRx1GGG1jKSKQaCB76zkvLaVfAw/0wgcW5gQ8t6t2Gwfp0UByFQTcykD o1qU/PXhJALtacseSJYOMqk/s9RDPN1askW1aqPMmbHBkMop0mmy0shNEGSltjUjAH0osBqLx 1cSDFsengjvzJe3qVP1rMVCIXEMbzKAH51xM61qcpEv6cke/RaFH793Gqp2XjckquZZWo4Nhx Phx0X5nMYipPWWfzmqHPDzeVhrHMGUFK+6AiLwbw2Jc5uWpQnxBEuhuzR7Fc3kleFB+qF1jOv EJDTqVbubUAsv01y X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 23:25:55 -0000 On Wed, 11 Jul 2018 12:08:14 -0700, David Johnson wrote: > I have found a FreeBSD OS embedded in my Mac which is fully implemented. > I followed the instructions and did the following from your website > documentation: > > in terminal; shutdown -k +1 "message" > > I get the following: > > System shutdown time has arrived > > but you'll have to do it yourself > > > I am not sure what to do at this prompt....what does 'do it yourself > mean', and what do I type to complete the process?? It means you have to shutdown the system yourself, because shutdown -k won't do it. The -k option just logs out any users and prevents further logins. From the manual: -k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all but super-user). Maybe you're searching for something that really shuts down the system? Check those options: -h -> shutdown and halt system (don't power off) related command: halt -p -> shutdown and power off system related command: poweroff -r -> shutdown and reboot system related command: reboot See "man shutdown" for details. On macOS, you'll probably have local access to the manuals. :-) > Also in addition to the above question.... > > does the fact that those commands do actually work mean that I am correct > in > > believing that there is a FreeBSD OS embedded in my system? FreeBSD's userland is in fact part of the macOS software. But it uses a different kernel (Darwin). See the BSD family tree (and Mac OS X / macOS in relation to FreeBSD): https://github.com/freebsd/freebsd/blob/master/share/misc/bsd-family-tree Additional information: http://www.freebsdworld.gr/freebsd/bsd-family-tree.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jul 11 23:36:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E349102F5C8 for ; Wed, 11 Jul 2018 23:36:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDC258DE01 for ; Wed, 11 Jul 2018 23:36:33 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPA (Nemesis) id 0LblS4-1gKC5w1RY4-00jIKg; Thu, 12 Jul 2018 01:30:44 +0200 Date: Thu, 12 Jul 2018 01:30:40 +0200 From: Polytropon To: byrnejb@harte-lyne.ca Cc: "James B. Byrne via freebsd-questions" Subject: Re: Why can I not get amd64/11.1-RELEASE? Message-Id: <20180712013040.7f7caae2.freebsd@edvax.de> In-Reply-To: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> References: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> 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-Provags-ID: V03:K1:hS7TgIJWbHl17bLv3hT+0DkkLU3IMQTHivKvRonFpcAcKU5HRTk +f/6Oufki1Xjrp/yFq25+3SILs0qgFSV1lONFOnuBTMI03uyUEyGz+c6yk5MfoPb46Tah8p T1Bp5qFi9B7vvqu2ONghbW6PiA7J90XCnR/l7C6AQqXgWQLe1uzVWAbO6HSnI/VjN75u5au YTqE9LH9Fx7F1sF9c4UCw== X-UI-Out-Filterresults: notjunk:1;V01:K0:kB8lX29h25I=:2tx5ibmJlIhIx0FRstkwOd KFZgyDJqUlRinJQd2CFA8EqlpJURrj2Bx57m0ogAb5CIhd2XL35KNpD2UWjdkjWHEQVxx9zGA qvvKrtxY1+HwS3tJo7NuYORqDP4c2ufXAJYwTjXCtO/+BKQJFHjyJml9aeEDihLeed9JqVEvn Q22vKpdZk5a1F8G/sLfpaz0rtmFFkVdD3Es683l9grm7qcrLwcxEA1HXq+J4bNIDGIu0WxgGg /oNY+H5DNSMKTmIMYgTccM5kBin2Zk5yzIMVdISttsjHRp6OUH5cDqRTpX1OZTl4FHDyznx+K cWgjRfklFrXJvu+MTlvCzSROP9SLnWsnyrvVHcuNc5zrsJRHOr7Jx8aDbGFmcBzod7sT8UYeB t+X9TLOFnsmtFAM8LMPMbnt4GrLiJ5NSx4o9XnIa+4Mc9YjKYwDlxVoU58p3eP6hpBalCuszH QGaI2HPaKHG+BmmpORh8qverA0bRcx1ecen4mDQpDbWnziKSgjr4ziP8ol6VAR793QEGlbt2r BoaW4c0Vp4hi8kYPCMhYAj7NxIGmkf7AM910TMkaZKBCVcf0/6X+f1rw+5Haqb10EaHYzHr6f NM/9Gg9U6jJqlIM8Pd3mwBvqfOenPoUsl7qzB1bOsciBfsE0TAlp6fW03UlWUCWvM8iVTQW/x fPHvGtushwVaK8WquGRYtOmvVDAKDwc4FWOWW7E+f8Kq2XdNO0GDR0MpHWS+MNliO9x2yNCbM k287u+ouSt6SwXRp X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2018 23:36:34 -0000 On Wed, 11 Jul 2018 16:23:38 -0400, James B. Byrne via freebsd-questions wrote: > I am experiencing difficulty installing ezjail-admin. Specifically > when I run 'ezjail-admin install' I get this: > > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz: > Permission denied > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz: > File unavailable (e.g., file not found, no access) > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/amd64/amd64/11.1-RELEASE/base.txz: > File unavailable (e.g., file not found, no access) > . . . > > Checking out the ftp site I discover this: > > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz: > File unavailable (e.g., file not found, no access) > > So, what is going on and how do I fix this? When I test this, I get a 404. % wget ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz --2018-07-12 01:25:08-- ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz => "base.txz" Resolving ftp.freebsd.org (ftp.freebsd.org)... 213.138.116.78, 2001:41c8:112:8300::15:0 Connecting to ftp.freebsd.org (ftp.freebsd.org)|213.138.116.78|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE ... No such directory "pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE". ^^^^^^^^ It seems that the path is misspelled. Have a close look: The 's' in "snapshots" is missing. However, ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ does not contain a 11.1-RELEASE directory entry, just those: 10.4-STABLE Directory 07/09/2018 20:07:00 11.2-STABLE Directory 07/09/2018 21:39:00 12.0-CURRENT Directory 07/10/2018 02:02:00 ISO-IMAGES Directory 05/09/2018 19:11:00 > I can connect and see the > files, I just cannot get them: > > ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE That's an entirely different path. Please compare: pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE ^^^^^^^^ pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE ^^^^^^^^ The command % fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz should work fine (it will download a 100 MB file). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Jul 12 02:34:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93CB71046027 for ; Thu, 12 Jul 2018 02:34:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 099F975843 for ; Thu, 12 Jul 2018 02:34:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0LoJRp-1gJLuJ3HE9-00gJyf; Thu, 12 Jul 2018 04:34:46 +0200 Date: Thu, 12 Jul 2018 04:34:46 +0200 From: Polytropon To: David Johnson Cc: FreeBSD Questions Subject: Re: Help with an Urgent Matter Message-Id: <20180712043446.33fa58d1.freebsd@edvax.de> In-Reply-To: References: <20180712012033.638fa1de.freebsd@edvax.de> 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-Provags-ID: V03:K1:c8XKGUmCQvCZlQPS99x3G/8rQK8U/CB3y/uQ1dPOJKQTPE8J0p0 uD7iGP5edUiHUZMW297xZq09Zq+fMdE1c5skY8kHIUf3POkIxppgqUdtKdm6yaFRm6T6z/e mqnNGH2NwdP8vV7y2sMRlf82bHcxkh4ti9PZv0qM1JCd3rc03Wc1qCNw7iwmOqBL4lA300J WcH5cP+LTkBAc7CtiYsBQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:DD9Q4m2VHRs=:fFycFYvwv5FVppBybx4xQ/ RfA5WoSlWQvCbB+s4nrVYSegK7ViglA2X6xHVhvSUNV9+5/HGP4nDyX2nrhLSN6FVdggqwnsn oj7ZUiUajClSkarH41FIhVCk5wqiDCMpLAyImIwcq+pHocVZGL09iwY5c/+9PD4D4UGyg0NPk rhVW1JIGJga2yWiGFLykvw9bO+9v1WaVxgtWOmgWLvh7PpsIrdCHAKdyCZDEV9KjfCz1tJSVT mwSfTWfDtGmzRbjmlcjR6DBco69SopjTJ/hSrspuV1WCT6X/vdKwNkgfXYCKFHB9RLPCwe/ld 76bXrYb9fmRchQEeJo7s6ZG2I3GYDZNU+L8Cq8qio1P8R3qb2Co2FTAUS8GGminDTEAae5WC0 Bf4qWmyEfBZGtRGbMX71F+17VOWggHFw7dr5EeWxU/HqV02yfdDjYQRqVw3yuwI/G5xManFtf BLPUQ/Zz+DFQtKZQJm1sxYQggfR/Ik4mKgJ420WOBSv5NiNEoI4xnnLZtRPgH/SBnZwZPDVYF dQBUItZh6l72F6mAZi3eSsuy02t9AanAkT4gXt1y5W8AnB00dhlstrq2qyQGiPh0uo7f5Z/ZU 5sK++i/3iK/O1nEmvXekDski2Tu/izB8sF2M1rnrCgckdkZN79VMw47gpP4Kq03eWBGG6ZLFs 7v/zqMJJk9RDfe2FIDId1E5bQYcfPUnsT3Soimc8j/rqxZnA5j4nNDm0Ljd6bIZNH/kiMUyAz XMUyVP0L8XTa3LEI X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 02:34:57 -0000 Re-including list, hope that's okay. On Wed, 11 Jul 2018 19:05:47 -0700, David Johnson wrote: > Thanks for responding but I don't see the answer that I am looking for or I > don't understand your short answers. > My question is about verifying if there is an active BSD server on my > system. You didn't ask for that specifically. :-) What do you mean by "a server"? Technically, all BSDs contain servers, and macOS won't be much different. The question is if those servers can communicate to the outside. For example, FreeBSD contains a mailserver, sendmail, which is used for in-system delivery. I won't communicate with the outside on its own. The software that macOS consists of might include several servers (web server, mail server, who knows). There are control elements to maintain a few of them. More information should be in the macOS documentation. FreeBSD != macOS. > I am asking this exactly for security reasons: > > "If I use any Free BSD command that shuts down my system: ex: shutdown > -r +1 "message" > and my system does shut down in 1 min..... 'Does this mean that there is an > active embedded BSD file system > within my Mac OS. You're confusing operating system with file system. Apple's Mac operating systems have been using several kinds of filesystems also available on FreeBSD; such as UFS and ZFS. Recent versions of macOS use HFS+ and today APFS. Of course those are able to implement a filesystem hierarchy similar to the one found on FreeBSD (see "man 7 hier"), but also cater to the needs of macOS file storage. The shutdown program, inherited from FreeBSD, is part of macOS (the userland). This has nothing to do with a file- system, which is a specification of how data will be stored on media. > Otherwise why would my system shut down using Free BSD > commands in terminal, and my terminal > is currently asking for a login when I open it for any task. As I said, the FreeBSD userland programs are available on macOS. The whole OS consists mainly of three parts: the Darwin kernel, a FreeBSD-like userland, and the graphical environment Aqua. The terminal behaviour seems to be normal, as you can login with a user account registered on the system (even though I'd assume that an interactive shell will be started for the account you're already logged in with, and which you start the terminal application from, but I might be wrong, I'm not using a Mac at the moment). Maybe this something you can explicitely configure? > Another question is ... > If I do have an embedded Free BSD Filesystem in my Mac, is there a way to > 1.) get a list of all files necessary to support an embedded BSD > filesystem? (this is very important) There is only one filesystem _type_ on your Mac. Depending on what OS version you are using, it's probably HFS+ or APFS. The support for a particular filesystem does not depend on any files specifically, but instead on the kernel or a kernel module that provides support for a particular filesystem in order to map it into the virtual filesystem (VFS) that "uni- fies" the userspace-side of any filesystem access. If you're asking for UFS and ZFS support (those are the two filesystem types primarily used on FreeBSD), I have no idea if they are supported, but I'd assume they are, given that both have been supported by older versions of Mac OS X. > 2. how do I uninstall the embedded filesystem if it does exist. I have > searched Free BSD web but cannot > find any topics regarding an uninstall process. You probably cannot remove components essential to the OS. Sure, you can try randomly deleting files, but that will finally render your system unusable. Keep in mind this is not a "parallel FreeBSD" - it's the macOS userland which is just _derived_ from FreeBSD. The OS cannot function without it, just as it cannot function without a kernel. > Files found which according to Apple are not installed with Sierra... > Rac, RacSignal, Squirrel Server, Squirrel.Mac and the worst of all: This looks like 3rd party software, not something that belongs to the OS. You can delete those with the software management tool provided by macOS. > (Function>/Users/josh****r/ > Documents/Development/GitHub/Squirrel.Mac/Squirrel/RACSignal+SQRLTransactionExtensions.mname > != nilPreventSystemSleepTimeoutActionLogCould not install power assertion: > %liCould not release power assertion:) > > *astericks above show a username from github. What we cannot understand is > why a github user would have his name in hundreds > of places in our computers within minutes after a fresh Sierra install from > the Apple Servers. This seems to be part of the SquirrelMail software that you have installed on your Mac. It's a webmailer, if I remember correctly. Where did you find those messages? Are they in a log file? Is it an error or a warning? Do you run the SquirrelMail software on your Mac, or do you use Safari / Chrome / Firefox to access an instance of that webmailer, and you just found something in a log file or temporary file? > We have had to reinstall Mac High Sierra over 350 times > since August 2016. I don't know why this should have been neccessary. > You should know that my request revolves around a criminal case of Elder > Abuse here in Canada > and I believe that the criminals involved are using Free BSD to control and > destroy evidence in our computers....... If that's true (or if it's just a suspicion), you should be in contact with the authorities. They have tools to forensically analyze a system to see what's going on. Per default, as far as I know, macOS does not exhibit means of remote control. Such a construct would involve a running SSH server, a username and password (!) known to the attacker, the firewall "properly" configured (to allow SSH connections), and the system to be online, of course. I'm not saying this is entirely impossible, but it doesn't ring a bell at the moment. As I said, I'm not a Mac person anymore, so my knowledge is a bit outdated, and I don't get lots of Mac experience in my daily work. As you have learned a lot about the relationship between FreeBSD and macOS, you should contact a macOS-centric discussion forum and maybe the SquirrelMail maintainers. To get this right: You assume that the BSD part of macOS is being used by a remote attacker to destroy evidence, and you conclude that from some SquirrelMail message... ??? Hmmm... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Jul 12 06:34:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCC1D1034F83 for ; Thu, 12 Jul 2018 06:34:27 +0000 (UTC) (envelope-from 010101648d277b6a-102e990a-a0e6-4513-b7ff-6957aeea3a8f-000000@us-west-2.amazonses.com) Received: from a27-53.smtp-out.us-west-2.amazonses.com (a27-53.smtp-out.us-west-2.amazonses.com [54.240.27.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41C9C7F733 for ; Thu, 12 Jul 2018 06:34:27 +0000 (UTC) (envelope-from 010101648d277b6a-102e990a-a0e6-4513-b7ff-6957aeea3a8f-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=7v7vs6w47njt4pimodk5mmttbegzsi6n; d=amazonses.com; t=1531376532; h=To:Subject:Date:From:Reply-To:Message-ID:Mime-Version:Content-Type:Feedback-ID; bh=1HaNdGc63ihPRPO5wPNsI0ehtmQ5rXO7W+oQCcFx3ko=; b=QYcv4+XxL6NlCqDBXQ6S+BXge2TiTjkW08iP4K0Xn4Xm4jAZyG7Tp0goKTceC5mf poX2F66kbbOgyYl1dbFgIlju3PSR5EPCZdLelRRA6Xr0oKJy0kQ9EVQ+q1JaMFbi5Su ZylNsM3j33MgnpR5z+IL9k4GpQHQfkMoDcdB3of4= X-Authentication-Warning: ip-172-31-39-71.us-west-2.compute.internal: apache set sender to support@revglue.uk using -f To: freebsd-questions@FreeBSD.org Subject: =?utf-8?Q?Monetise_your_affiliate_projects_with_RevGlue.com?= X-PHP-Originating-Script: 500:Email.php User-Agent: CodeIgniter Date: Thu, 12 Jul 2018 06:22:12 +0000 From: "RevGlue UK" Reply-To: "support@revglue.uk" X-Sender: support@revglue.uk X-Mailer: CodeIgniter X-Priority: 3 (Normal) Message-ID: <010101648d277b6a-102e990a-a0e6-4513-b7ff-6957aeea3a8f-000000@us-west-2.amazonses.com> Mime-Version: 1.0 X-SES-Outgoing: 2018.07.12-54.240.27.53 Feedback-ID: 1.us-west-2.wSngBhllka0weHaMfcON1VwWNmDmSljTk1JAYZe12PU=:AmazonSES Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 06:34:28 -0000 Hi, I went through your website and found a link http://rapid-shield.com////news/status/report-2015-10-2015-12.html that is showing Rakuten affiliate network integration. I believe you are working as an affiliate or online publisher and utilising the affiliate networks to monetise your websites, blogs or mobile applications. RevGlue.com support affiliates and online publishers with unique set of tools to easily monetise their websites, blogs, mobile applications and social media channels. We work with all UK leading affiliate networks to help you save time and money with data management, affiliate website development and monetising your website users. Browse RevGlue blog section at https://www.revglue.com/blog to understand how you can exploit RevGlue tools to monetise your current websites or setup new projects in minutes. Our affiliate tools consists of affiliate data sets, Wordpress plugins, Wordpress templates and stats that help affiliates to setup new projects such as cashback, coupons, mobile comparison and more. Explore RevGlue affiliate tools at https://www.revglue.com/tools-for-affiliates Our publisher tools are offered totally free to monetise your blogs, website and social media users. Explore RevGlue publisher tools at https://www.revglue.com/tools-for-publishers Create free RevGlue.com user account and try all tools for Free. No credit card is required. RevGlue.com From owner-freebsd-questions@freebsd.org Thu Jul 12 06:34:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F0E61034FB4 for ; Thu, 12 Jul 2018 06:34:34 +0000 (UTC) (envelope-from ldakmail@gmail.com) Received: from mail-vk0-x241.google.com (mail-vk0-x241.google.com [IPv6:2607:f8b0:400c:c05::241]) (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 08FC57F741 for ; Thu, 12 Jul 2018 06:34:34 +0000 (UTC) (envelope-from ldakmail@gmail.com) Received: by mail-vk0-x241.google.com with SMTP id t4-v6so15660436vke.9 for ; Wed, 11 Jul 2018 23:34:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=zi5JechX/G3fELo5jw0Th8prwGxJe5OUntdICMEwgWQ=; b=URWlo7I454Nvv7trBlJGNx5D9NxTZZk8H/M+d81WfbmoYPCWcAdNtBS9WUAsqcNfMx xexKl4JRWJgN0UTexttAEe6W4TmcW8WmJ0r19M8MfaRsUY7gPV58XnhZsTvrEErBykJy wXBmFKLsJaFe4LKdLGH0KVUQ3oa8EHT2F+Rg/sWIrybvtw1Y2moZZNbiPoIw7D/GuH9G Nem/M2QE2H0pelr/YWfazrlOB1gB0AIcc3PcgtKkgVPRba1PUERlHgqyUdSeyiftgX6d 0xPG8y65i68HhoeKKVk9xUO0KcaqdWQRLXFyKFfWW1k7NbF5xN2SqJQfB4wZariSOEbk NxEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zi5JechX/G3fELo5jw0Th8prwGxJe5OUntdICMEwgWQ=; b=ZgQFOv3XmAb6h2Lz9XktHdhHVzqyzUohBk5YRCtDSMZOzd+LMrhXqtv4JCdrqMxfVF I0w/cHpO5wSQVTTtcxaFrr2H87b2k+QCq+XBakazSNF/7peNWNipt1RmE4f3bTS4CXob +L1Pm4YmfG3u9ow6bh01dvBSv6Tycj05LoGfCXeWvsO5WS/rAmLD6P7V4pAhPqury+hv I4Hj754NciYLBznEt9UkbtXrO91N4TnxOGB3BnEJ6xNz3WR2JWI+gPRALJAhnRVq8hbG 0cjM8ZXbc9sjPPx6eQ7O05HoPeghK7x1TWRC2qTmpEiyo6++Dt2DY3v/ZKiMmLmRF35e //Bg== X-Gm-Message-State: AOUpUlH/CmJEwnwrLjN6ViwTl06kzDYQAwtV6WF+Vm9kVXQ5TTS4xxgP MoqbZNtPXD5aQtD5Kb/aR3Ir37YhJhR/2VrfxUw= X-Google-Smtp-Source: AAOMgpfNNn9KheJbk+w8uorga0O6lI8GlwkK2ngySvO5Mag8gWgvVMPs+kYBy1FWlwCEZfnME0AfiQfkoNvfALSKQ2k= X-Received: by 2002:a1f:6045:: with SMTP id u66-v6mr478869vkb.88.1531377272260; Wed, 11 Jul 2018 23:34:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: ldak mail Date: Thu, 12 Jul 2018 07:34:20 +0100 Message-ID: Subject: Re: freebsd-questions Digest, Vol 735, Issue 4 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 06:34:35 -0000 Unsubscribe On Thu, 12 Jul 2018, 00:26 , wrote: > Send freebsd-questions mailing list submissions to > freebsd-questions@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > or, via email, send a message with subject or body 'help' to > freebsd-questions-request@freebsd.org > > You can reach the person managing the list at > freebsd-questions-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-questions digest..." > > > Today's Topics: > > 1. Re: backspace not working with mg (Kevin P. Neal) > 2. Help with an Urgent Matter (David Johnson) > 3. Re: Help with an Urgent Matter (Paul Pathiakis) > 4. Re: Help with an Urgent Matter (Norman Gray) > 5. Why can I not get amd64/11.1-RELEASE? (James B. Byrne) > 6. Re: Why can I not get amd64/11.1-RELEASE? (Philipp Vlassakakis) > 7. Re: Why can I not get amd64/11.1-RELEASE? (James B. Byrne) > 8. Disk/ZFS activity crash on 11.2-STABLE (Jim Long) > 9. Re: [commercial] sendmail setup request (RW) > 10. recovering an overwritten zfs partition (The Doctor) > 11. Re: Help with an Urgent Matter (Polytropon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 11 Jul 2018 13:30:22 -0400 > From: "Kevin P. Neal" > To: Mayuresh Kathe > Cc: freebsd-questions@freebsd.org > Subject: Re: backspace not working with mg > Message-ID: <20180711173022.GA61776@neutralgood.org> > Content-Type: text/plain; charset=us-ascii > > On Mon, Jul 09, 2018 at 06:45:15AM +0000, Mayuresh Kathe wrote: > > my backspace key functions just right with 'ee' but not under "mg". > > the system just beeps and the cursor just sits where it was. > > i am a "vi" guy, but now am migrating to "mg" because the nature > > of work for me going forward would involve a "lisp-1" system and > > "mg" provides nice parentheses matching feature without the bloat > > i would have to tolerate if using "gnu emacs". > > In vi, does the "%" key not do what you want? I use it all the time to > bounce the cursor between open and close parens. > > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > "14. Re-reading No. 13, I realize that it's quite possible I'm losing my > mind. I'm glad that for the most part I'm not aware it's happening." > -- from "20 things I'm thankful for": Fortune, Nov 29, 2004, page 230 > > > ------------------------------ > > Message: 2 > Date: Wed, 11 Jul 2018 12:08:14 -0700 > From: David Johnson > To: freebsd-questions@freebsd.org > Subject: Help with an Urgent Matter > Message-ID: > < > CAGX9N-MnE625yqJ5pkn23YoD5BGJ7o6BOC2nRWKUuhmmT2nHBA@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I have found a FreeBSD OS embedded in my Mac which is fully implemented. > I followed the instructions and did the following from your website > documentation: > > in terminal; shutdown -k +1 "message" > > I get the following: > > System shutdown time has arrived > > but you'll have to do it yourself > > > I am not sure what to do at this prompt....what does 'do it yourself > mean', and what do I type to complete the process?? > > > Also in addition to the above question.... > > does the fact that those commands do actually work mean that I am correct > in > > believing that there is a FreeBSD OS embedded in my system? > > > Thank You, > > Free BSD > > > Lamb Agency > > > ------------------------------ > > Message: 3 > Date: Wed, 11 Jul 2018 19:23:06 +0000 (UTC) > From: Paul Pathiakis > To: freebsd-questions@freebsd.org, David Johnson > > Subject: Re: Help with an Urgent Matter > Message-ID: <1985397816.2919749.1531336986787@mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > 1.2.?Welcome to FreeBSD! > > | > | > | | > 1.2.?Welcome to FreeBSD! > > > | > > | > > | > > > David, > > As you can see, Apple borrows a lot from FreeBSD.? The co-joined operating > system is called DarwinOS which is the foundation for the Apple Mac OSX > operating system. > Not having dealt with a Mac for years, I'm guessing about your issue.? If > your command returns a prompt after it runs and spits out that message, the > shutdown command may have been altered. > At the prompt, try a simple 'halt' command.? That should shut the machine > down. > P. > > On Wednesday, July 11, 2018, 3:09:31 PM EDT, David Johnson < > djtherenovator@gmail.com> wrote: > > I have found a FreeBSD OS embedded in my Mac which is fully implemented. > I followed the instructions and did the following from your website > documentation: > > in terminal;? shutdown -k +1 "message" > > I get the following: > > System shutdown time has arrived > > but you'll have to do it yourself > > > I am not sure what to do at this prompt....what does 'do it yourself > mean', and what do I type to complete the process?? > > > Also in addition to the above question.... > > does the fact that those commands do actually work mean that I am correct > in > > believing that there is a FreeBSD OS embedded in my system? > > > Thank You, > > Free BSD > > > Lamb Agency > _______________________________________________ > 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" > > > ------------------------------ > > Message: 4 > Date: Wed, 11 Jul 2018 20:26:48 +0100 > From: Norman Gray > To: David Johnson > Cc: > Subject: Re: Help with an Urgent Matter > Message-ID: > Content-Type: text/plain; format=flowed > > > Greetings. > > On 11 Jul 2018, at 20:08, David Johnson wrote: > > > I have found a FreeBSD OS embedded in my Mac which is fully > > implemented. > > Not really. macOS uses a lot of the FreeBSD 'userland' -- ie, the user > commands -- but the kernel is significantly different. > > There is quite a close relationship between macOS and FreeBSD, though > I'm vague on the details (if anyone has any links, I'd be very > interested in them). However close it is, one cannot realistically say > 'macOS is FreeBSD'! > > > I followed the instructions and did the following from your website > > documentation: > > > > in terminal; shutdown -k +1 "message" > > The -k option means: > > -k Kick everybody off. The -k option does not actually halt > the sys- > tem, but leaves the system multi-user with logins disabled > (for all > but super-user). > > See 'man shutdown' > > As it happens, I think that 'shutdown -h now' does work on macOS, but it > may not be formally supported. That is, there may well be other aspects > of a fully controlled shutdown which this will miss. > > Good wishes, > > Norman > > > -- > Norman Gray : https://nxg.me.uk > SUPA School of Physics and Astronomy, University of Glasgow, UK > > > ------------------------------ > > Message: 5 > Date: Wed, 11 Jul 2018 16:23:38 -0400 > From: "James B. Byrne" > To: freebsd-questions@freebsd.org > Subject: Why can I not get amd64/11.1-RELEASE? > Message-ID: > <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> > Content-Type: text/plain;charset=iso-8859-1 > > I am experiencing difficulty installing ezjail-admin. Specifically > when I run 'ezjail-admin install' I get this: > > fetch: > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz > : > Permission denied > fetch: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > : > File unavailable (e.g., file not found, no access) > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/amd64/amd64/11.1-RELEASE/base.txz: > File unavailable (e.g., file not found, no access) > . . . > > Checking out the ftp site I discover this: > > fetch: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > : > File unavailable (e.g., file not found, no access) > > So, what is going on and how do I fix this? I can connect and see the > files, I just cannot get them: > > ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE > 229 Entering Extended Passive Mode (|||62035|) > 150 Here comes the directory listing. > -rw-r--r-- 1 ftp ftp 1157 Jul 21 2017 MANIFEST > -rw-r--r-- 1 ftp ftp 49166232 Jul 21 2017 base-dbg.txz > -rw-r--r-- 1 ftp ftp 104780108 Jul 21 2017 base.txz > -rw-r--r-- 1 ftp ftp 1428656 Jul 21 2017 doc.txz > -rw-r--r-- 1 ftp ftp 66586424 Jul 21 2017 kernel-dbg.txz > -rw-r--r-- 1 ftp ftp 36773692 Jul 21 2017 kernel.txz > -rw-r--r-- 1 ftp ftp 12555216 Jul 21 2017 lib32-dbg.txz > -rw-r--r-- 1 ftp ftp 18499068 Jul 21 2017 lib32.txz > -rw-r--r-- 1 ftp ftp 36756836 Jul 21 2017 ports.txz > -rw-r--r-- 1 ftp ftp 147661560 Jul 21 2017 src.txz > -rw-r--r-- 1 ftp ftp 4312456 Jul 21 2017 tests.txz > 226 Directory send OK. > > > -- > *** e-Mail is NOT a SECURE channel *** > Do NOT transmit sensitive data via e-Mail > Do NOT open attachments nor follow links sent by e-Mail > > James B. Byrne mailto:ByrneJB@Harte-Lyne.ca > Harte & Lyne Limited http://www.harte-lyne.ca > 9 Brockley Drive vox: +1 905 561 1241 > Hamilton, Ontario fax: +1 905 561 0757 > Canada L8E 3C3 > > > > ------------------------------ > > Message: 6 > Date: Wed, 11 Jul 2018 22:31:33 +0200 > From: Philipp Vlassakakis > To: byrnejb@harte-lyne.ca > Cc: freebsd-questions@freebsd.org > Subject: Re: Why can I not get amd64/11.1-RELEASE? > Message-ID: > <456DE8C6-2761-4671-AAFE-F15CCC77ADF7@lists.vlassakakis.de> > Content-Type: text/plain; charset=utf-8 > > Can you save any other files? > Does a simple ?touch test? work? > > Regards, > Philipp > > > Am 11.07.2018 um 22:23 schrieb James B. Byrne via freebsd-questions < > freebsd-questions@freebsd.org>: > > > > I am experiencing difficulty installing ezjail-admin. Specifically > > when I run 'ezjail-admin install' I get this: > > > > fetch: > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz > : > > Permission denied > > fetch: > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > : > > File unavailable (e.g., file not found, no access) > > fetch: > > ftp://ftp.freebsd.org/pub/FreeBSD/amd64/amd64/11.1-RELEASE/base.txz: > > File unavailable (e.g., file not found, no access) > > . . . > > > > Checking out the ftp site I discover this: > > > > fetch: > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > : > > File unavailable (e.g., file not found, no access) > > > > So, what is going on and how do I fix this? I can connect and see the > > files, I just cannot get them: > > > > ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE > > 229 Entering Extended Passive Mode (|||62035|) > > 150 Here comes the directory listing. > > -rw-r--r-- 1 ftp ftp 1157 Jul 21 2017 MANIFEST > > -rw-r--r-- 1 ftp ftp 49166232 Jul 21 2017 base-dbg.txz > > -rw-r--r-- 1 ftp ftp 104780108 Jul 21 2017 base.txz > > -rw-r--r-- 1 ftp ftp 1428656 Jul 21 2017 doc.txz > > -rw-r--r-- 1 ftp ftp 66586424 Jul 21 2017 kernel-dbg.txz > > -rw-r--r-- 1 ftp ftp 36773692 Jul 21 2017 kernel.txz > > -rw-r--r-- 1 ftp ftp 12555216 Jul 21 2017 lib32-dbg.txz > > -rw-r--r-- 1 ftp ftp 18499068 Jul 21 2017 lib32.txz > > -rw-r--r-- 1 ftp ftp 36756836 Jul 21 2017 ports.txz > > -rw-r--r-- 1 ftp ftp 147661560 Jul 21 2017 src.txz > > -rw-r--r-- 1 ftp ftp 4312456 Jul 21 2017 tests.txz > > 226 Directory send OK. > > > > > > -- > > *** e-Mail is NOT a SECURE channel *** > > Do NOT transmit sensitive data via e-Mail > > Do NOT open attachments nor follow links sent by e-Mail > > > > James B. Byrne mailto:ByrneJB@Harte-Lyne.ca > > Harte & Lyne Limited http://www.harte-lyne.ca > > 9 Brockley Drive vox: +1 905 561 1241 > > Hamilton, Ontario fax: +1 905 561 0757 > > Canada L8E 3C3 > > > > _______________________________________________ > > 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" > > > > ------------------------------ > > Message: 7 > Date: Wed, 11 Jul 2018 17:04:26 -0400 > From: "James B. Byrne" > To: freebsd-questions@freebsd.org > Subject: Re: Why can I not get amd64/11.1-RELEASE? > Message-ID: > <45fabaafa88136c1e63a057f86cce88d.squirrel@webmail.harte-lyne.ca> > Content-Type: text/plain;charset=iso-8859-1 > > > On Wed, July 11, 2018 16:31, Philipp Vlassakakis wrote: > > Can you save any other files? > > Does a simple ???touch test??? work? > > > > [root@vhost03 ~]# dir x > bash: dir: command not found > [root@vhost03 ~]# ll x > -rw-r--r-- 1 root wheel 0 Jul 11 16:56 x > > > -- > *** e-Mail is NOT a SECURE channel *** > Do NOT transmit sensitive data via e-Mail > Do NOT open attachments nor follow links sent by e-Mail > > James B. Byrne mailto:ByrneJB@Harte-Lyne.ca > Harte & Lyne Limited http://www.harte-lyne.ca > 9 Brockley Drive vox: +1 905 561 1241 > Hamilton, Ontario fax: +1 905 561 0757 > Canada L8E 3C3 > > > > ------------------------------ > > Message: 8 > Date: Wed, 11 Jul 2018 14:29:59 -0700 > From: Jim Long > To: freebsd-questions@freebsd.org > Subject: Disk/ZFS activity crash on 11.2-STABLE > Message-ID: <20180711212959.GA81029@g5.umpquanet.com> > Content-Type: text/plain; charset=us-ascii > > I have a server running a Supermicro X11DPH-T system board (dmesg below) > which is unstable under heavy disk read load. The following command is > sufficient to trigger a crash: > > # zfs send -R pool@snapshot > /dev/null > > That command takes an unpredictable amount of time to trigger the crash, > but I have never seen it complete successfully. > > Further, crash dumps of this are difficult to obtain (see below), > despite the fact that dumps are enabled and tested via: > > # sysctl debug.kdb.panic=1 > > As disclosure, this machine sometimes exhibits a second failure mode > with a "kernel trap 12 with interrupts disabled." This typically occurs > on boot, just about the point where the kernel begins enumerating the > CPUs. But that is not (yet) my primary concern. > > I typically perform the 'zfs send' stress test over an ssh session, > although the server is nearby on a test bench. I have not yet been at > the console when the panic or crash happens, so I am not certain that > the kernel is "panicking gracefully," if you'll pardon the oxymoron, I > have yet to find any crash dumps in /var/crash after a disk-induced > panic. > > Is a serial console the next step in troubleshooting this? I am fairly > strong in bash scripting, but inexperienced in kernel crash debugging. > I already have remote syslogging set on this server, so it's feasible > to write certain terse tidbits to syslog ("still alive at xx:yy PDT") > and/or dump some key statistics every minute to the server's local ZFS > pool, and then see what the last stats dump file shows upon reboot. > > What are some key stats I should capture at periodic intervals while > waiting for the 'zfs send' to induce the crash -- iostat? zfs-stats is > also installed, but I'm ignorant about what stats I should dump, and how > to infer any post-mortem meaning from them. > > This problem first appeared when doing a backup of this machine. The > 'zfs send' was invoked by a remote host over an ssh session with jumbo > frames enabled, achieving a throughput of around 115 MB/sec going out > over GigE. To eliminate the network driver as a possible point of > failure, I discovered that sending the 'zfs send' output to /dev/null > was sufficient to trigger the crash. I may try rate-limiting the > output pipe with: > > # zfs send -R pool@snapshot | pv -Wbrat -L 1M > /dev/null > > to see whether the -L value has any effect on the ability of this > command to complete successfully. > > After I started drafting this write-up, I finally got a crash dump. I > ran the stress script: > > #!/usr/bin/env bash > > FILE="/var/crash/zfs-stress.start" > SLEEP_TIME=10 > > # if this script causes a crash, then we should expect to see a > # crash dump newer than this file: > > touch $FILE > > logger "begin $0" > > zfs destroy -rv tank@stress-test 2> /dev/null > > zfs snap -r tank@stress-test > > logger "begin 'zfs send -R tank@stress-test" > > zfs send -R tank@stress-test > /dev/null & > > logger "zfs send running in background" > > while [ -f $FILE ] && sleep $SLEEP_TIME; do > > logger "still alive @ $(date +%H:%M:%S)" > > done > > -- snip > > while also running 'systat -vm' in one virtual terminal and writing > 'zpool iostat -v' to disk every couple seconds. I did finally observe a > panic and this time got a dump. > > One quirk I forgot to mention is that after this ZFS-induced crash, on the > next boot, the /etc/rc somehow does not run dhclient on the primary > interface, despite its presence in /etc/rc.conf: > > ifconfig_ixl0="DHCP" > > I have no idea whether that is at all related, but it does mean that > even if the system reboots after a crash, it is inaccessible except by > the physical console. I have to log in as root and say 'dhclient ixl0'. > On the NEXT boot, the DHCP client is invoked by /etc/rc as one would > expect. I have: > > rc_debug="YES" > > defined in /etc/rc.conf but I am not seeing any messages that explain why > dhclient is not being executed. > > I would be very grateful to anyone who has time to examine these > post-mortems > and offer any suggestions on where to go next. > > Thank you for your time reading this lengthy trouble report. > > Jim > > > > As promised, dmesg: > > > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 > root@jimsdesk.example.edu:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM > 6.0.0) > VT(efifb): resolution 1680x1050 > CPU: Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz (2300.08-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4 > > Features=0xbfebfbff > > Features2=0x7ffefbff > AMD Features=0x2c100800 > AMD Features2=0x121 > Structured Extended > Features=0xd39ffffb > Structured Extended Features2=0x8 > Structured Extended Features3=0xc000000 > XSAVE Features=0xf > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr > TSC: P-state invariant, performance statistics > real memory = 103079215104 (98304 MB) > avail memory = 98749128704 (94174 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs > FreeBSD/SMP: 2 package(s) x 12 core(s) x 2 hardware threads > ioapic6: Changing APIC ID to 16 > ioapic7: Changing APIC ID to 17 > ioapic8: Changing APIC ID to 18 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-31 on motherboard > ioapic2 irqs 32-39 on motherboard > ioapic3 irqs 40-47 on motherboard > ioapic4 irqs 48-55 on motherboard > ioapic5 irqs 72-79 on motherboard > ioapic6 irqs 80-87 on motherboard > ioapic7 irqs 88-95 on motherboard > ioapic8 irqs 96-103 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #38 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #16 Launched! > SMP: AP CPU #12 Launched! > SMP: AP CPU #6 Launched! > SMP: AP CPU #17 Launched! > SMP: AP CPU #40 Launched! > SMP: AP CPU #29 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #27 Launched! > SMP: AP CPU #19 Launched! > SMP: AP CPU #13 Launched! > SMP: AP CPU #22 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #28 Launched! > SMP: AP CPU #30 Launched! > SMP: AP CPU #11 Launched! > SMP: AP CPU #42 Launched! > SMP: AP CPU #32 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #34 Launched! > SMP: AP CPU #14 Launched! > SMP: AP CPU #37 Launched! > SMP: AP CPU #20 Launched! > SMP: AP CPU #41 Launched! > SMP: AP CPU #21 Launched! > SMP: AP CPU #18 Launched! > SMP: AP CPU #35 Launched! > SMP: AP CPU #23 Launched! > SMP: AP CPU #10 Launched! > SMP: AP CPU #36 Launched! > SMP: AP CPU #31 Launched! > SMP: AP CPU #43 Launched! > SMP: AP CPU #44 Launched! > SMP: AP CPU #45 Launched! > SMP: AP CPU #39 Launched! > SMP: AP CPU #8 Launched! > SMP: AP CPU #24 Launched! > SMP: AP CPU #25 Launched! > SMP: AP CPU #46 Launched! > SMP: AP CPU #9 Launched! > SMP: AP CPU #26 Launched! > SMP: AP CPU #33 Launched! > SMP: AP CPU #15 Launched! > SMP: AP CPU #7 Launched! > SMP: AP CPU #47 Launched! > Timecounter "TSC-low" frequency 1150040467 Hz quality 1000 > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4590, 0) error 19 > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > nexus0 > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: numa-domain 0 on acpi0 > cpu1: numa-domain 0 on acpi0 > cpu2: numa-domain 0 on acpi0 > cpu3: numa-domain 0 on acpi0 > cpu4: numa-domain 0 on acpi0 > cpu5: numa-domain 0 on acpi0 > cpu6: numa-domain 0 on acpi0 > cpu7: numa-domain 0 on acpi0 > cpu8: numa-domain 0 on acpi0 > cpu9: numa-domain 0 on acpi0 > cpu10: numa-domain 0 on acpi0 > cpu11: numa-domain 0 on acpi0 > cpu12: numa-domain 0 on acpi0 > cpu13: numa-domain 0 on acpi0 > cpu14: numa-domain 0 on acpi0 > cpu15: numa-domain 0 on acpi0 > cpu16: numa-domain 0 on acpi0 > cpu17: numa-domain 0 on acpi0 > cpu18: numa-domain 0 on acpi0 > cpu19: numa-domain 0 on acpi0 > cpu20: numa-domain 0 on acpi0 > cpu21: numa-domain 0 on acpi0 > cpu22: numa-domain 0 on acpi0 > cpu23: numa-domain 0 on acpi0 > cpu24: numa-domain 1 on acpi0 > cpu25: numa-domain 1 on acpi0 > cpu26: numa-domain 1 on acpi0 > cpu27: numa-domain 1 on acpi0 > cpu28: numa-domain 1 on acpi0 > cpu29: numa-domain 1 on acpi0 > cpu30: numa-domain 1 on acpi0 > cpu31: numa-domain 1 on acpi0 > cpu32: numa-domain 1 on acpi0 > cpu33: numa-domain 1 on acpi0 > cpu34: numa-domain 1 on acpi0 > cpu35: numa-domain 1 on acpi0 > cpu36: numa-domain 1 on acpi0 > cpu37: numa-domain 1 on acpi0 > cpu38: numa-domain 1 on acpi0 > cpu39: numa-domain 1 on acpi0 > cpu40: numa-domain 1 on acpi0 > cpu41: numa-domain 1 on acpi0 > cpu42: numa-domain 1 on acpi0 > cpu43: numa-domain 1 on acpi0 > cpu44: numa-domain 1 on acpi0 > cpu45: numa-domain 1 on acpi0 > cpu46: numa-domain 1 on acpi0 > cpu47: numa-domain 1 on acpi0 > atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 > atrtc0: registered as a time-of-day clock, resolution 1.000000s > Event timer "RTC" frequency 32768 Hz quality 0 > attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > Timecounter "HPET" frequency 24000000 Hz quality 950 > Event timer "HPET" frequency 24000000 Hz quality 350 > Event timer "HPET1" frequency 24000000 Hz quality 340 > Event timer "HPET2" frequency 24000000 Hz quality 340 > Event timer "HPET3" frequency 24000000 Hz quality 340 > Event timer "HPET4" frequency 24000000 Hz quality 340 > Event timer "HPET5" frequency 24000000 Hz quality 340 > Event timer "HPET6" frequency 24000000 Hz quality 340 > Event timer "HPET7" frequency 24000000 Hz quality 340 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 > acpi_syscontainer0: on acpi0 > acpi_syscontainer1: on acpi0 > pcib0: port 0xcf8-0xcff numa-domain 0 on acpi0 > pcib0: _OSC returned error 0x10 > pci0: numa-domain 0 on pcib0 > pci0: at device 8.1 (no driver attached) > pci0: at device 17.0 (no driver attached) > pci0: at device 17.1 (no driver attached) > ahci0: port > 0x3070-0x3077,0x3060-0x3063,0x3020-0x303f mem > 0x9d206000-0x9d207fff,0x9d209000-0x9d2090ff,0x9d180000-0x9d1fffff irq 16 at > device 17.5 numa-domain 0 on pci0 > ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ahciem0: on ahci0 > xhci0: mem > 0x383ffff00000-0x383ffff0ffff irq 16 at device 20.0 numa-domain 0 on pci0 > xhci0: 32 bytes context size, 64-bit DMA > usbus0: waiting for BIOS to give up control > xhci_interrupt: host controller halted > usbus0 numa-domain 0 on xhci0 > usbus0: 5.0Gbps Super Speed USB v3.0 > pci0: at device 22.0 (no driver attached) > pci0: at device 22.1 (no driver attached) > pci0: at device 22.4 (no driver attached) > ahci1: port > 0x3050-0x3057,0x3040-0x3043,0x3000-0x301f mem > 0x9d204000-0x9d205fff,0x9d208000-0x9d2080ff,0x9d100000-0x9d17ffff irq 16 at > device 23.0 numa-domain 0 on pci0 > ahci1: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported > ahcich6: at channel 0 on ahci1 > ahcich7: at channel 1 on ahci1 > ahcich8: at channel 2 on ahci1 > ahcich9: at channel 3 on ahci1 > ahcich10: at channel 4 on ahci1 > ahcich11: at channel 5 on ahci1 > ahcich12: at channel 6 on ahci1 > ahcich13: at channel 7 on ahci1 > ahciem1: on ahci1 > pcib1: irq 16 at device 28.0 numa-domain 0 on pci0 > pci1: numa-domain 0 on pcib1 > pcib2: irq 17 at device 28.5 numa-domain 0 on pci0 > pci2: numa-domain 0 on pcib2 > pcib3: irq 17 at device 0.0 numa-domain 0 on pci2 > pci3: numa-domain 0 on pcib3 > vgapci0: port 0x2000-0x207f mem > 0x9c000000-0x9cffffff,0x9d000000-0x9d01ffff irq 17 at device 0.0 > numa-domain 0 on pci3 > vgapci0: Boot video device > isab0: at device 31.0 numa-domain 0 on pci0 > isa0: numa-domain 0 on isab0 > pci0: at device 31.2 (no driver attached) > pci0: at device 31.5 (no driver attached) > pcib4: numa-domain 0 on acpi0 > pcib4: _OSC returned error 0x10 > pci4: numa-domain 0 on pcib4 > pcib5: irq 39 at device 0.0 numa-domain 0 on pci4 > pci5: numa-domain 0 on pcib5 > pcib6: mem 0xaae00000-0xaae1ffff irq 32 at device > 0.0 numa-domain 0 on pci5 > pci6: numa-domain 0 on pcib6 > pcib7: irq 38 at device 3.0 numa-domain 0 on pci6 > pci7: numa-domain 0 on pcib7 > ixl0: 1.9.9-k> mem 0xa9000000-0xa9ffffff,0xaa008000-0xaa00ffff irq 38 at device > 0.0 numa-domain 0 on pci7 > ixl0: using 1024 tx descriptors and 1024 rx descriptors > ixl0: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 > ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared > ixl0: Using MSIX interrupts with 9 vectors > ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active > ixl0: Ethernet address: ac:1f:6b:61:54:06 > ixl0: SR-IOV ready > queues is 0xfffffe0001d13000 > ixl0: netmap queues/slots: TX 8/1024, RX 8/1024 > ixl1: 1.9.9-k> mem 0xa8000000-0xa8ffffff,0xaa000000-0xaa007fff irq 38 at device > 0.1 numa-domain 0 on pci7 > ixl1: using 1024 tx descriptors and 1024 rx descriptors > ixl1: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 > ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared > ixl1: Using MSIX interrupts with 9 vectors > ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active > ixl1: Ethernet address: ac:1f:6b:61:54:07 > ixl1: SR-IOV ready > queues is 0xfffffe0001e69000 > ixl1: netmap queues/slots: TX 8/1024, RX 8/1024 > pcib8: numa-domain 0 on acpi0 > pcib8: _OSC returned error 0x10 > pci8: numa-domain 0 on pcib8 > pcib9: irq 47 at device 2.0 numa-domain 0 on pci8 > pci9: numa-domain 0 on pcib9 > mpr0: port 0x7000-0x70ff mem > 0xb8640000-0xb864ffff,0xb8600000-0xb863ffff irq 42 at device 0.0 > numa-domain 0 on pci9 > mpr0: Firmware: 15.00.03.00, Driver: 18.03.00.00-fbsd > mpr0: IOCCapabilities: > 7a85c > pcib10: numa-domain 0 on acpi0 > pcib10: _OSC returned error 0x10 > pci10: numa-domain 0 on pcib10 > pci10: at device 14.0 (no driver attached) > pci10: at device 15.0 (no driver attached) > pci10: at device 18.0 (no driver attached) > pci10: at device 18.1 (no driver attached) > pcib11: numa-domain 1 on acpi0 > ixl0: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: > None, Autoneg: True, Flow Control: None > ixl0: link state changed to UP > ixl1: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: > None, Autoneg: True, Flow Control: Full > ixl1: link state changed to UP > pcib11: _OSC returned error 0x10 > pci11: numa-domain 1 on pcib11 > pci11: at device 8.1 (no driver attached) > pcib12: numa-domain 1 on acpi0 > pcib12: _OSC returned error 0x10 > pci12: numa-domain 1 on pcib12 > pcib13: numa-domain 1 on acpi0 > pcib13: _OSC returned error 0x10 > pci13: numa-domain 1 on pcib13 > pcib14: numa-domain 1 on acpi0 > pcib14: _OSC returned error 0x10 > pci14: numa-domain 1 on pcib14 > pci14: at device 14.0 (no driver attached) > pci14: at device 15.0 (no driver attached) > pci14: at device 18.0 (no driver attached) > pci14: at device 18.1 (no driver attached) > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > orm0: at iomem 0xc0000-0xc7fff on isa0 > ppc0: cannot reserve I/O port range > est0: numa-domain 0 on cpu0 > est1: numa-domain 0 on cpu1 > est2: numa-domain 0 on cpu2 > est3: numa-domain 0 on cpu3 > est4: numa-domain 0 on cpu4 > est5: numa-domain 0 on cpu5 > est6: numa-domain 0 on cpu6 > est7: numa-domain 0 on cpu7 > est8: numa-domain 0 on cpu8 > est9: numa-domain 0 on cpu9 > est10: numa-domain 0 on cpu10 > est11: numa-domain 0 on cpu11 > est12: numa-domain 0 on cpu12 > est13: numa-domain 0 on cpu13 > est14: numa-domain 0 on cpu14 > est15: numa-domain 0 on cpu15 > est16: numa-domain 0 on cpu16 > est17: numa-domain 0 on cpu17 > est18: numa-domain 0 on cpu18 > est19: numa-domain 0 on cpu19 > est20: numa-domain 0 on cpu20 > est21: numa-domain 0 on cpu21 > est22: numa-domain 0 on cpu22 > est23: numa-domain 0 on cpu23 > est24: numa-domain 1 on cpu24 > est25: numa-domain 1 on cpu25 > est26: numa-domain 1 on cpu26 > est27: numa-domain 1 on cpu27 > est28: numa-domain 1 on cpu28 > est29: numa-domain 1 on cpu29 > est30: numa-domain 1 on cpu30 > est31: numa-domain 1 on cpu31 > est32: numa-domain 1 on cpu32 > est33: numa-domain 1 on cpu33 > est34: numa-domain 1 on cpu34 > est35: numa-domain 1 on cpu35 > est36: numa-domain 1 on cpu36 > est37: numa-domain 1 on cpu37 > est38: numa-domain 1 on cpu38 > est39: numa-domain 1 on cpu39 > est40: numa-domain 1 on cpu40 > est41: numa-domain 1 on cpu41 > est42: numa-domain 1 on cpu42 > est43: numa-domain 1 on cpu43 > est44: numa-domain 1 on cpu44 > est45: numa-domain 1 on cpu45 > est46: numa-domain 1 on cpu46 > est47: numa-domain 1 on cpu47 > random: unblocking device. > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounters tick every 1.000 msec > ugen0.1: <0x8086 XHCI root HUB> at usbus0 > mpr0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on > usbus0 > SAS Address from SAS device page0 = 5000c500955fb571 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000a> > enclosureHandle<0x0002> slot 0 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c5009550e4f1 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000b> > enclosureHandle<0x0002> slot 1 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c50095518c95 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000c> > enclosureHandle<0x0002> slot 2 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c500955fb3c5 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000d> > enclosureHandle<0x0002> slot 3 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c500955fb021 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000e> > enclosureHandle<0x0002> slot 4 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c5009550e891 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000f> > enclosureHandle<0x0002> slot 5 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 500304801eb5dbfd > mpr0: Found device <4411,End Device> <12.0Gbps> > handle<0x0010> enclosureHandle<0x0002> slot 12 > mpr0: At enclosure level 0 and connector name ( ) > ses0 at ahciem0 bus 0 scbus6 target 0 lun 0 > ses0: SEMB S-E-S 2.00 device > ses0: SEMB SES Device > ses1 at ahciem1 bus 0 scbus15 target 0 lun 0 > ses1: SEMB S-E-S 2.00 device > ses1: SEMB SES Device > ses2 at mpr0 bus 0 scbus16 target 20 lun 0 > ses2: Fixed Enclosure Services SPC-3 SCSI device > ses2: 1200.000MB/s transfers > ses2: Command Queueing enabled > ses2: SCSI-3 ENC Device > ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 > ada0: ACS-3 ATA SATA 3.x device > ada0: Serial Number BTYS81150CWH240AGN > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada0: Command Queueing enabled > ada0: 228936MB (468862128 512 byte sectors) > ada1 at ahcich5 bus 0 scbus5 target 0 lun 0 > ada1: ACS-3 ATA SATA 3.x device > ada1: Serial Number BTYS814205JS240AGN > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada1: Command Queueing enabled > ada1: 228936MB (468862128 512 byte sectors) > uhub0: 26 ports with 26 removable, self powered > ses2: pass4,da0: Element descriptor: 'Slot00' > da1 at mpr0 bus 0 scbus16 target 9 lun 0 > da2 at mpr0 bus 0 scbus16 target 10 lun 0 > da0 at mpr0 bus 0 scbus16 target 8 lun 0 > da5 at mpr0 bus 0 scbus16 target 13 lun 0 > da4 at mpr0 bus 0 scbus16 target 12 lun 0 > da2: Fixed Direct Access SPC-4 SCSI device > da2: Serial Number ZC15T3GB0000C832EM0C > da2: 1200.000MB/s transfers > da2: Command Queueing enabled > da2: 3815447MB (976754646 4096 byte sectors) > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number ZC1606NJ0000R833G9JK > da0: 1200.000MB/s transfers > da0: Command Queueing enabled > da0: 3815447MB (976754646 4096 byte sectors) > da4: Fixed Direct Access SPC-4 SCSI device > da4: Serial Number ZC1606RR0000R833G8YR > da4: 1200.000MB/s transfers > da4: Command Queueing enabled > da4: 3815447MB (976754646 4096 byte sectors) > ses2: pass4,da0: SAS Device Slot Element: 1 Phys at Slot 0 > ses2: phy 0: SAS device type 1 id 0 > da5: da1: Fixed Direct Access SPC-4 SCSI device > da1: Serial Number ZC15V7DV0000C8258M38 > ugen0.2: at usbus0 > da1: 1200.000MB/s transfers > da1: Command Queueing enabled > da1: 3815447MB (976754646 4096 byte sectors) > Fixed Direct Access SPC-4 SCSI device > ukbd0da5: Serial Number ZC15KB320000R832RAR7 > da5: 1200.000MB/s transfers > da5: Command Queueing enabled > da5: 3815447MB (976754646 4096 byte sectors) > numa-domain 0 on uhub0 > da3 at mpr0 bus 0 scbus16 target 11 lun 0 > ukbd0: on > usbus0 > kbd2 at ukbd0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb571 > da3: Fixed Direct Access SPC-4 SCSI device > da3: Serial Number ZC1606Q80000R833WKE8 > da3: 1200.000MB/s transfers > da3: Command Queueing enabled > da3: 3815447MB (976754646 4096 byte sectors) > ses2: pass5,da1: Element descriptor: 'Slot01' > ses2: pass5,da1: SAS Device Slot Element: 1 Phys at Slot 1 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e4f1 > ses2: pass6,da2: Element descriptor: 'Slot02' > ses2: pass6,da2: SAS Device Slot Element: 1 Phys at Slot 2 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c50095518c95 > ses2: pass7,da3: Element descriptor: 'Slot03' > ses2: pass7,da3: SAS Device Slot Element: 1 Phys at Slot 3 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb3c5 > ses2: pass8,da4: Element descriptor: 'Slot04' > ses2: pass8,da4: SAS Device Slot Element: 1 Phys at Slot 4 > ugen0.3: at usbus0 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb021 > ses2: pass9,da5: Element descriptor: 'Slot05' > ses2: pass9,da5: SAS Device Slot Element: 1 Phys at Slot 5 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e891 > uhub1 numa-domain 0 on uhub0 > uhub1: on > usbus0 > Trying to mount root from zfs:tank/default/root []... > Root mount waiting for: usbus0 > uhub1: 4 ports with 3 removable, self powered > ugen0.4: at usbus0 > ukbd1 numa-domain 0 on uhub1 > ukbd1: on > usbus0 > kbd3 at ukbd1 > lo0: link state changed to UP > ums0 numa-domain 0 on uhub1 > ums0: on > usbus0 > ums0: 3 buttons and [Z] coordinates ID=0 > > > > And pciconf -lvb: > > > hostb0@pci0:0:0:0: class=0x060000 card=0x098115d9 chip=0x20208086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E DMI3 Registers' > class = bridge > subclass = HOST-PCI > none0@pci0:0:4:0: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff2c000, size 16384, > enabled > none1@pci0:0:4:1: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff28000, size 16384, > enabled > none2@pci0:0:4:2: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff24000, size 16384, > enabled > none3@pci0:0:4:3: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff20000, size 16384, > enabled > none4@pci0:0:4:4: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff1c000, size 16384, > enabled > none5@pci0:0:4:5: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff18000, size 16384, > enabled > none6@pci0:0:4:6: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff14000, size 16384, > enabled > none7@pci0:0:4:7: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff10000, size 16384, > enabled > none8@pci0:0:5:0: class=0x088000 card=0x00008086 chip=0x20248086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E MM/Vt-d Configuration Registers' > class = base peripheral > none9@pci0:0:5:2: class=0x088000 card=0x00000000 chip=0x20258086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > ioapic0@pci0:0:5:4: class=0x080020 card=0x20268086 chip=0x20268086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0x9d20a000, size 4096, enabled > none10@pci0:0:8:0: class=0x088000 card=0x00008086 chip=0x20148086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none11@pci0:0:8:1: class=0x110100 card=0x00008086 chip=0x20158086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = dasp > subclass = performance counters > none12@pci0:0:8:2: class=0x088000 card=0x00008086 chip=0x20168086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none13@pci0:0:17:0: class=0xff0000 card=0x098115d9 chip=0xa1ec8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > none14@pci0:0:17:1: class=0xff0000 card=0x098115d9 chip=0xa1ed8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > ahci0@pci0:0:17:5: class=0x010601 card=0x098115d9 chip=0xa1d28086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SSATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > bar [10] = type Memory, range 32, base 0x9d206000, size 8192, enabled > bar [14] = type Memory, range 32, base 0x9d209000, size 256, enabled > bar [18] = type I/O Port, range 32, base 0x3070, size 8, enabled > bar [1c] = type I/O Port, range 32, base 0x3060, size 4, enabled > bar [20] = type I/O Port, range 32, base 0x3020, size 32, enabled > bar [24] = type Memory, range 32, base 0x9d180000, size 524288, > enabled > xhci0@pci0:0:20:0: class=0x0c0330 card=0x098115d9 chip=0xa1af8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg USB 3.0 xHCI Controller' > class = serial bus > subclass = USB > bar [10] = type Memory, range 64, base 0x383ffff00000, size 65536, > enabled > none15@pci0:0:20:2: class=0x118000 card=0x098115d9 chip=0xa1b18086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg Thermal Subsystem' > class = dasp > bar [10] = type Memory, range 64, base 0x383ffff33000, size 4096, > enabled > none16@pci0:0:22:0: class=0x078000 card=0x098115d9 chip=0xa1ba8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff32000, size 4096, > enabled > none17@pci0:0:22:1: class=0x078000 card=0x098115d9 chip=0xa1bb8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff31000, size 4096, > enabled > none18@pci0:0:22:4: class=0x078000 card=0x098115d9 chip=0xa1be8086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff30000, size 4096, > enabled > ahci1@pci0:0:23:0: class=0x010601 card=0x098115d9 chip=0xa1828086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > bar [10] = type Memory, range 32, base 0x9d204000, size 8192, enabled > bar [14] = type Memory, range 32, base 0x9d208000, size 256, enabled > bar [18] = type I/O Port, range 32, base 0x3050, size 8, enabled > bar [1c] = type I/O Port, range 32, base 0x3040, size 4, enabled > bar [20] = type I/O Port, range 32, base 0x3000, size 32, enabled > bar [24] = type Memory, range 32, base 0x9d100000, size 524288, > enabled > pcib1@pci0:0:28:0: class=0x060400 card=0x098115d9 chip=0xa1908086 > rev=0xf9 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lewisburg PCI Express Root Port' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:28:5: class=0x060400 card=0x098115d9 chip=0xa1958086 > rev=0xf9 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lewisburg PCI Express Root Port' > class = bridge > subclass = PCI-PCI > isab0@pci0:0:31:0: class=0x060100 card=0x098115d9 chip=0xa1c38086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg LPC Controller' > class = bridge > subclass = PCI-ISA > none19@pci0:0:31:2: class=0x058000 card=0x098115d9 chip=0xa1a18086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg PMC' > class = memory > bar [10] = type Memory, range 32, base 0x9d200000, size 16384, > enabled > none20@pci0:0:31:4: class=0x0c0500 card=0x098115d9 chip=0xa1a38086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SMBus' > class = serial bus > subclass = SMBus > bar [10] = type Memory, range 64, base 0, size 256, disabled > bar [20] = type I/O Port, range 32, base 0x780, size 32, enabled > none21@pci0:0:31:5: class=0x0c8000 card=0x098115d9 chip=0xa1a48086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SPI Controller' > class = serial bus > bar [10] = type Memory, range 32, base 0xfe010000, size 4096, enabled > pcib3@pci0:2:0:0: class=0x060400 card=0x11501a03 chip=0x11501a03 > rev=0x04 hdr=0x01 > vendor = 'ASPEED Technology, Inc.' > device = 'AST1150 PCI-to-PCI Bridge' > class = bridge > subclass = PCI-PCI > vgapci0@pci0:3:0:0: class=0x030000 card=0x098115d9 chip=0x20001a03 > rev=0x41 hdr=0x00 > vendor = 'ASPEED Technology, Inc.' > device = 'ASPEED Graphics Family' > class = display > subclass = VGA > bar [10] = type Memory, range 32, base 0x9c000000, size 16777216, > enabled > bar [14] = type Memory, range 32, base 0x9d000000, size 131072, > enabled > bar [18] = type I/O Port, range 32, base 0x2000, size 128, enabled > pcib5@pci0:23:0:0: class=0x060400 card=0x098115d9 chip=0x20308086 > rev=0x04 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCI Express Root Port A' > class = bridge > subclass = PCI-PCI > none22@pci0:23:5:0: class=0x088000 card=0x00008086 chip=0x20348086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none23@pci0:23:5:2: class=0x088000 card=0x00000000 chip=0x20358086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic1@pci0:23:5:4: class=0x080020 card=0x20368086 chip=0x20368086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xaaf00000, size 4096, enabled > none24@pci0:23:8:0: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none25@pci0:23:8:1: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none26@pci0:23:8:2: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none27@pci0:23:8:3: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none28@pci0:23:8:4: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none29@pci0:23:8:5: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none30@pci0:23:8:6: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none31@pci0:23:8:7: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none32@pci0:23:9:0: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none33@pci0:23:9:1: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none34@pci0:23:9:2: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none35@pci0:23:9:3: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none36@pci0:23:9:4: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none37@pci0:23:9:5: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none38@pci0:23:9:6: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none39@pci0:23:9:7: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none40@pci0:23:10:0: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none41@pci0:23:10:1: class=0x088000 card=0x00008086 chip=0x208d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none42@pci0:23:14:0: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none43@pci0:23:14:1: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none44@pci0:23:14:2: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none45@pci0:23:14:3: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none46@pci0:23:14:4: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none47@pci0:23:14:5: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none48@pci0:23:14:6: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none49@pci0:23:14:7: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none50@pci0:23:15:0: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none51@pci0:23:15:1: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none52@pci0:23:15:2: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none53@pci0:23:15:3: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none54@pci0:23:15:4: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none55@pci0:23:15:5: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none56@pci0:23:15:6: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none57@pci0:23:15:7: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none58@pci0:23:16:0: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none59@pci0:23:16:1: class=0x088000 card=0x00008086 chip=0x208e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none60@pci0:23:29:0: class=0x088000 card=0x00008086 chip=0x20548086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none61@pci0:23:29:1: class=0x088000 card=0x00008086 chip=0x20558086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none62@pci0:23:29:2: class=0x088000 card=0x00008086 chip=0x20568086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none63@pci0:23:29:3: class=0x088000 card=0x00008086 chip=0x20578086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none64@pci0:23:30:0: class=0x088000 card=0x00008086 chip=0x20808086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none65@pci0:23:30:1: class=0x088000 card=0x00008086 chip=0x20818086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none66@pci0:23:30:2: class=0x088000 card=0x00008086 chip=0x20828086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none67@pci0:23:30:3: class=0x088000 card=0x00008086 chip=0x20838086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none68@pci0:23:30:4: class=0x088000 card=0x00008086 chip=0x20848086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none69@pci0:23:30:5: class=0x088000 card=0x00008086 chip=0x20858086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none70@pci0:23:30:6: class=0x088000 card=0x00008086 chip=0x20868086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > pcib6@pci0:24:0:0: class=0x060400 card=0xdeadbeef chip=0x37c08086 > rev=0x09 hdr=0x01 > vendor = 'Intel Corporation' > class = bridge > subclass = PCI-PCI > bar [10] = type Memory, range 64, base 0xaae00000, size 131072, > enabled > pcib7@pci0:25:3:0: class=0x060400 card=0xdeadbeef chip=0x37c58086 > rev=0x09 hdr=0x01 > vendor = 'Intel Corporation' > class = bridge > subclass = PCI-PCI > ixl0@pci0:26:0:0: class=0x020000 card=0x37d215d9 chip=0x37d28086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection X722 for 10GBASE-T' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0xa9000000, size > 16777216, enabled > bar [1c] = type Prefetchable Memory, range 64, base 0xaa008000, size > 32768, enabled > ixl1@pci0:26:0:1: class=0x020000 card=0x37d215d9 chip=0x37d28086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection X722 for 10GBASE-T' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0xa8000000, size > 16777216, enabled > bar [1c] = type Prefetchable Memory, range 64, base 0xaa000000, size > 32768, enabled > pcib9@pci0:58:2:0: class=0x060400 card=0x098115d9 chip=0x20328086 > rev=0x04 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCI Express Root Port C' > class = bridge > subclass = PCI-PCI > none71@pci0:58:5:0: class=0x088000 card=0x00008086 chip=0x20348086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none72@pci0:58:5:2: class=0x088000 card=0x00000000 chip=0x20358086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic2@pci0:58:5:4: class=0x080020 card=0x20368086 chip=0x20368086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xb8700000, size 4096, enabled > none73@pci0:58:8:0: class=0x088000 card=0x00008086 chip=0x20668086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none74@pci0:58:9:0: class=0x088000 card=0x00008086 chip=0x20668086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none75@pci0:58:10:0: class=0x088000 card=0x00008086 chip=0x20408086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none76@pci0:58:10:1: class=0x088000 card=0x00008086 chip=0x20418086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none77@pci0:58:10:2: class=0x088000 card=0x00008086 chip=0x20428086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none78@pci0:58:10:3: class=0x088000 card=0x00008086 chip=0x20438086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none79@pci0:58:10:4: class=0x088000 card=0x00008086 chip=0x20448086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none80@pci0:58:10:5: class=0x088000 card=0x00008086 chip=0x20458086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none81@pci0:58:10:6: class=0x088000 card=0x00008086 chip=0x20468086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none82@pci0:58:10:7: class=0x088000 card=0x00008086 chip=0x20478086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none83@pci0:58:11:0: class=0x088000 card=0x00008086 chip=0x20488086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none84@pci0:58:11:1: class=0x088000 card=0x00008086 chip=0x20498086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none85@pci0:58:11:2: class=0x088000 card=0x00008086 chip=0x204a8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none86@pci0:58:11:3: class=0x088000 card=0x00008086 chip=0x204b8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none87@pci0:58:12:0: class=0x088000 card=0x00008086 chip=0x20408086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none88@pci0:58:12:1: class=0x088000 card=0x00008086 chip=0x20418086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none89@pci0:58:12:2: class=0x088000 card=0x00008086 chip=0x20428086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none90@pci0:58:12:3: class=0x088000 card=0x00008086 chip=0x20438086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none91@pci0:58:12:4: class=0x088000 card=0x00008086 chip=0x20448086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none92@pci0:58:12:5: class=0x088000 card=0x00008086 chip=0x20458086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none93@pci0:58:12:6: class=0x088000 card=0x00008086 chip=0x20468086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none94@pci0:58:12:7: class=0x088000 card=0x00008086 chip=0x20478086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none95@pci0:58:13:0: class=0x088000 card=0x00008086 chip=0x20488086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none96@pci0:58:13:1: class=0x088000 card=0x00008086 chip=0x20498086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none97@pci0:58:13:2: class=0x088000 card=0x00008086 chip=0x204a8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none98@pci0:58:13:3: class=0x088000 card=0x00008086 chip=0x204b8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > mpr0@pci0:59:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 > rev=0x02 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' > class = mass storage > subclass = SAS > bar [10] = type I/O Port, range 32, base 0x7000, size 256, enabled > bar [14] = type Memory, range 64, base 0xb8640000, size 65536, > enabled > bar [1c] = type Memory, range 64, base 0xb8600000, size 262144, > enabled > none99@pci0:93:5:0: class=0x088000 card=0x00008086 chip=0x20348086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none100@pci0:93:5:2: class=0x088000 card=0x00000000 chip=0x20358086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic3@pci0:93:5:4: class=0x080020 card=0x20368086 chip=0x20368086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xc5f00000, size 4096, enabled > none101@pci0:93:14:0: class=0x110100 card=0x00008086 chip=0x20588086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none102@pci0:93:14:1: class=0x088000 card=0x00008086 chip=0x20598086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none103@pci0:93:15:0: class=0x110100 card=0x00008086 chip=0x20588086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none104@pci0:93:15:1: class=0x088000 card=0x00008086 chip=0x20598086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none105@pci0:93:18:0: class=0x110100 card=0x00008086 chip=0x204c8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none106@pci0:93:18:1: class=0x110100 card=0x00008086 chip=0x204d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none107@pci0:93:18:2: class=0x088000 card=0x00008086 chip=0x204e8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = base peripheral > none108@pci0:93:21:0: class=0x088000 card=0x00008086 chip=0x20188086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none109@pci0:93:22:0: class=0x088000 card=0x00008086 chip=0x20188086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none110@pci0:93:22:4: class=0x088000 card=0x00008086 chip=0x20188086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none111@pci0:128:4:0: class=0x088000 card=0x00008086 chip=0x20218086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff1c000, size 16384, > enabled > none112@pci0:128:4:1: class=0x088000 card=0x00008086 chip= From owner-freebsd-questions@freebsd.org Thu Jul 12 09:55:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD7A210489C2 for ; Thu, 12 Jul 2018 09:55:09 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3290386F67 for ; Thu, 12 Jul 2018 09:55:08 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from mr185083 (mr185083.univ-rennes1.fr [129.20.185.83]) by mx.zohomail.com with SMTPS id 1531389296736187.27791668280793; Thu, 12 Jul 2018 02:54:56 -0700 (PDT) Date: Thu, 12 Jul 2018 11:54:52 +0200 From: Patrick Lamaiziere To: freebsd-questions@freebsd.org Subject: vim color and copy/paste Message-ID: <20180712115452.48cee92d@mr185083> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ZohoMailClient: External X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 09:55:10 -0000 Hello, Any idea why with Vim in a terminal xterm I cannot copy/paste text when the text is colored (syntax color by sample)? vim-lite-8.0.0134 freebsd 11.2 Thanks ! Regards. From owner-freebsd-questions@freebsd.org Thu Jul 12 10:02:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8307C10495BE for ; Thu, 12 Jul 2018 10:02:13 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 1BBE087606 for ; Thu, 12 Jul 2018 10:02:13 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 1B171289 for ; Thu, 12 Jul 2018 06:02:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 12 Jul 2018 06:02:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=QPALFUwZW0KLL17vzXWjfOFRCiryZ TPhtypBvyKFizQ=; b=Op/QehbP9oxkNFwrCCsfY/n4UdwLoWACtX5hZHSvHQCjG dWQlU93hVdqWJA8Y1SKKZoEUF5TIWuEJ5I72SC2JDnLCNt1OpHY44iKXEIxqztHi G1H/FVB6Q1R9h4ZDcGKqHwrWSnrwGHBsowklw7MqvJTJmo8NlwEsT2iLGB0Rysbo rgbrvbNp3E+gtRaJoBwPxcmSRQyZWWUeQ2lGdeW6QrjK9Fy1KClO9glw19YoPtKd Xh9NaFqScyDdw3Mk2BQa6f6kWpQ6p8BNXezWJZL0JpJm1zbvOlFCLw6ShdMcUfK+ knbGLwa/K+yU42ZUrB4cSUOB30WX6a4PDTNhVrY8Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=QPALFU wZW0KLL17vzXWjfOFRCiryZTPhtypBvyKFizQ=; b=shxwQy4BIWfsSpkJTd1zHO o+4XH6zuAje7uwDzz79Bhowg9d83N5Olf4O/XoSeEmnyPa4z+seUC/vvQwfxQKio yIiTRtJSWEESKoXnLjw0rvYGYYWcPY3XnJsPY2p1knNuAdJcFb9RVoeC4N82tAMP DP2NW2qPjMRmjaeMtnNyXHlIi9qlojovlDXOk/mto8xfhu23Cyj1g0EH1tS2Nrlo 9YMqrBTwMoCxQ+vq2P2CASvoPK/S0vPWsv/3LlroPQ5kHeMAMmmKevGHpD+fhqoQ l9KURZ6KIIOprkIAMu8P8QtjyylCfnNysDdoDRlMGm5MGTdZzngbFz6kUgyS7SqQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 3DF9C10261 for ; Thu, 12 Jul 2018 06:02:11 -0400 (EDT) Subject: Re: vim color and copy/paste To: freebsd-questions@freebsd.org References: <20180712115452.48cee92d@mr185083> From: tech-lists Organization: none Message-ID: Date: Thu, 12 Jul 2018 11:02:10 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: <20180712115452.48cee92d@mr185083> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 10:02:13 -0000 On 12/07/2018 10:54, Patrick Lamaiziere wrote: > Any idea why with Vim in a terminal xterm I cannot copy/paste text > when the text is colored (syntax color by sample)? > > vim-lite-8.0.0134 > freebsd 11.2 Hi, What's in your .vimrc ? In a minimal config, I have just the following: set mouse= otherwise mouse commands get interpreted by vim and I don't want that. -- J. From owner-freebsd-questions@freebsd.org Thu Jul 12 11:19:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 431791029139 for ; Thu, 12 Jul 2018 11:19:16 +0000 (UTC) (envelope-from shellymcadams@webmarketingvendors.com) Received: from mail-it0-x247.google.com (mail-it0-x247.google.com [IPv6:2607:f8b0:4001:c0b::247]) (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 CB6FB8B176 for ; Thu, 12 Jul 2018 11:19:15 +0000 (UTC) (envelope-from shellymcadams@webmarketingvendors.com) Received: by mail-it0-x247.google.com with SMTP id n68-v6so4359012ite.8 for ; Thu, 12 Jul 2018 04:19:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=webmarketingvendors-com.20150623.gappssmtp.com; s=20150623; h=mime-version:message-id:date:subject:from:to; bh=pmTsVhYln1X3PPlqKz7SW59rS5slmqm+PUMS4q9XOug=; b=sz57Mcd+Wloecudcl2x72AqvZ05mC9cHZ4QtJqt+5JsONhhycxRK4decFvSaZzX7Fd 4UCet9pk1eRnYc8p5CAC3IbpAs2BfqYTylEeapd4B0MDhnTs93Te97zUaP7w1oqxOGQ2 fYLsJwgLxm1PD0Qgx3c1IjhzS+BLcm2T6erHv/ObHqZOgqPbrAElMjYGDW5yme91nByB xTMhDe5TeWjFzWR1uZts7fNLCR2HhX65v0t2nFgC81KYN02p5D6wOAQkDjYeJ1Wvr8us zOc36GuVareVCfmgxHkU8LiUJNIKhHKzRqB/7SHIwmfm/6nmMNx33mOVznSNbjEhp2R1 8smw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:message-id:date:subject:from:to; bh=pmTsVhYln1X3PPlqKz7SW59rS5slmqm+PUMS4q9XOug=; b=Of1lTml0npAhMFgdsHmF38HPoB7PGM27GVnN1q4fIyxr3YDe/xmaC9GRnl5bb5X3px S5t8Iou2RuzflZtz0usuOZnFF3NenH4RNmRb9fPzvJgeBNEMCSupQ9G9qO+rwY4g+TA6 vwoctSE+byNtH/RzctOcVA5nfoYnywfm6ofJKmn8lxgDOrbRioIJfH+glpW7MzpqT8I1 4kPzzuuT1Gb4HJLNehvsO5Dt1fydKVXy026D1WUwiC+C11wZhEJF1YdGwJ1MEyIomBT/ 5j0mhwOloqXYqiJb1oQ3J1zQsvcTwFqjIf5zR3LIK6TsiCeTmS2IZrIbvjB+07mSYspf 74Zg== X-Gm-Message-State: AOUpUlHkiy/4sdi/lqCSvcuin4v6F0MV97YZxfVuQlFOJMkZoptyeBH4 2vetnooU6EhfC2+yCVMjwf2SxJUy9ykk X-Google-Smtp-Source: AAOMgpenbmcj48VcH8RFGPz4PzNu6VJ7pZqbhZ6/Q3w1f1Bf/sePP8FoEurReCVVdK6oDWrnlJT3BzboHA== MIME-Version: 1.0 X-Received: by 2002:a24:ad4f:: with SMTP id a15-v6mr601358itj.42.1531394354794; Thu, 12 Jul 2018 04:19:14 -0700 (PDT) Message-ID: <0000000000008755ec0570cb88ab@google.com> Date: Thu, 12 Jul 2018 11:19:14 +0000 Subject: Re : freebsd.org : Boost Your Online Visitor From: shellymcadams@webmarketingvendors.com To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 11:19:16 -0000 Hello freebsd.org Owner, My name is Shelly McAdams, and I'm a SEO Specialist. Most of the people share their anger and frustration once they get my email. But let me show you how there is so many bugs (like broken links, pages that returned 4XX status code upon request, images with no ALT text, pages with no meta description tag, not having an unique meta description, having too long title, etc.), found in freebsd.org. I have a large professional team who can fix all the above issues immediately at an affordable price. I guarantee you will see a drastic change in your Google search ranking once these are fixed. If this is something you are interested in, then allow me to send you a no obligation audit report. Waiting for your response!!! Best Regards, Shelly McAdams SEO Specialist -------------------------------------------------------------------------------- Note: If you are not interested, please email with the subject line "No" and I will be happy to update my data base. From owner-freebsd-questions@freebsd.org Thu Jul 12 13:32:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23F3D1039AFE for ; Thu, 12 Jul 2018 13:32:49 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BA7B5916E6 for ; Thu, 12 Jul 2018 13:32:48 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 0B701E918; Thu, 12 Jul 2018 09:32:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id GHc2DgaV5wBk; Thu, 12 Jul 2018 09:32:31 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 24364E90D; Thu, 12 Jul 2018 09:32:31 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 12 Jul 2018 09:32:30 -0400 Message-ID: <06f0e55cf92b99596f0869b9953915f4.squirrel@webmail.harte-lyne.ca> In-Reply-To: <20180712013040.7f7caae2.freebsd@edvax.de> References: <688231194e76f0359de77528168a96c1.squirrel@webmail.harte-lyne.ca> <20180712013040.7f7caae2.freebsd@edvax.de> Date: Thu, 12 Jul 2018 09:32:30 -0400 Subject: Re: Why can I not get amd64/11.1-RELEASE? From: "James B. Byrne" To: "Polytropon" Cc: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 13:32:49 -0000 On Wed, July 11, 2018 19:30, Polytropon wrote: > On Wed, 11 Jul 2018 16:23:38 -0400, James B. Byrne via > freebsd-questions wrote: >> I am experiencing difficulty installing ezjail-admin. Specifically >> when I run 'ezjail-admin install' I get this: . . . >> fetch: >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz: >> File unavailable (e.g., file not found, no access) >> >> So, what is going on and how do I fix this? > > When I test this, I get a 404. > > % wget > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > --2018-07-12 01:25:08-- > ftp://ftp.freebsd.org/pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE/base.txz > => "base.txz" > Resolving ftp.freebsd.org (ftp.freebsd.org)... 213.138.116.78, > 2001:41c8:112:8300::15:0 > Connecting to ftp.freebsd.org (ftp.freebsd.org)|213.138.116.78|:21... > connected. > Logging in as anonymous ... Logged in! > ==> SYST ... done. ==> PWD ... done. > ==> TYPE I ... done. ==> CWD (1) > /pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE ... > No such directory "pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE". > ^^^^^^^^ > > It seems that the path is misspelled. Have a close look: > The 's' in "snapshots" is missing. > > However, ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ > does not contain a 11.1-RELEASE directory entry, just those: > > 10.4-STABLE Directory 07/09/2018 20:07:00 > 11.2-STABLE Directory 07/09/2018 21:39:00 > 12.0-CURRENT Directory 07/10/2018 02:02:00 > ISO-IMAGES Directory 05/09/2018 19:11:00 > > > >> I can connect and see the >> files, I just cannot get them: >> >> ftp> dir pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE > > That's an entirely different path. Please compare: > > pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE > ^^^^^^^^ > > pub/FreeBSD/snapshot/amd64/amd64/11.1-RELEASE > ^^^^^^^^ > > The command > > % fetch > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/11.1-RELEASE/base.txz > > should work fine (it will download a 100 MB file). > > > The problem was due to a mis-configured pf.conf. PF was blocking ftp traffic. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Thu Jul 12 14:47:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2ED11040C01 for ; Thu, 12 Jul 2018 14:47:18 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AFD29526C for ; Thu, 12 Jul 2018 14:47:18 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 99EABEA59 for ; Thu, 12 Jul 2018 10:47:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id NY1B6sKgbjvQ for ; Thu, 12 Jul 2018 10:47:01 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 0FBC0EA50 for ; Thu, 12 Jul 2018 10:47:01 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 12 Jul 2018 10:47:01 -0400 Message-ID: <817c767ec4571b432831b576bc36d651.squirrel@webmail.harte-lyne.ca> Date: Thu, 12 Jul 2018 10:47:01 -0400 Subject: ezjail install: tar cannot chdir to /usr/jails/fulljail From: "James B. Byrne" To: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 14:47:19 -0000 I am atempting to 9re-)install ezjail on a host which had it previously installed and removed. When it was removed the relics of its exitance were also removed: pkg remove ezjail rm -rf /usr/local/etc/ezjail.conf rm -rf /usr/local/etc/ezjail chflags -R noschg /usr/jails rm -rf /usr/jails zfs destroy -r zroot/ezjail I then restarted the host, just to make sure. Then I reinstalled ezjail: pkg install ezjail Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ezjail: 3.4.2 Number of packages to be installed: 1 Proceed with this action? [y/N]: y [1/1] Installing ezjail-3.4.2... [1/1] Extracting ezjail-3.4.2: 100% and recreated the zfs backing store: zfs create -p zroot/ezjail and edited the new /usr/local/etc/ezjail.conf to use zfs: # grep zfs /usr/local/etc/ezjail.conf ezjail_use_zfs="YES" # Setting this to YES will manage ALL new jails in their own zfs ezjail_use_zfs_for_jails="YES" ezjail_jailzfs="zroot/ezjail" # ezjail_zfs_properties="-o compression=lzjb -o atime=off" # ezjail_zfs_jail_properties="-o dedup=on" But when I ran ezjail-admin install I got this error: ezjail-admin install base.txz 100% of 99 MB 621 kBps 02m45s tar: could not chdir to '/usr/jails/fulljail' # ll /usr/jails total 0 ll /usr/local/etc/ezjail total 0 Have I missed a step? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Thu Jul 12 15:53:36 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8998F1046B63 for ; Thu, 12 Jul 2018 15:53:35 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost2.sentex.ca", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D6EEC7001C for ; Thu, 12 Jul 2018 15:53:34 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5:0:0:0:11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w6CFrWH9054049 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 12 Jul 2018 11:53:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w6CFrUKw090571; Thu, 12 Jul 2018 11:53:30 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Disk/ZFS activity crash on 11.2-STABLE To: Jim Long , freebsd-questions@freebsd.org References: <20180711212959.GA81029@g5.umpquanet.com> From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= xsBNBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAHNHG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT7CwHgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnnOwE0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAcLAXwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> Date: Thu, 12 Jul 2018 11:53:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180711212959.GA81029@g5.umpquanet.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.83 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 15:53:36 -0000 On 7/11/2018 5:29 PM, Jim Long wrote: > Further, crash dumps of this are difficult to obtain (see below), > despite the fact that dumps are enabled and tested via: > while also running 'systat -vm' in one virtual terminal and writing > 'zpool iostat -v' to disk every couple seconds. I did finally observe a > panic and this time got a dump. prior to the crash, if you run gstat does it show the disks at 100% load ? You have a lot of RAM, is ARC by chance using all of it ? Try putting a hard limit on it. So if you have 98G of RAM, place a limit at something like 70G for now. Also, what is the file system like ? Is it a few big files or MANY little files. Post the output of zfs-stats -a > > One quirk I forgot to mention is that after this ZFS-induced crash, on the > next boot, the /etc/rc somehow does not run dhclient on the primary > interface, despite its presence in /etc/rc.conf: > > ifconfig_ixl0="DHCP" Thats odd. does dmesg -a show anything about ixl0 and dhclient ? Perhaps in /usr/local/etc/rc.d/ put a small script like "dhclient-safety.sh" in in it have something like #!/bin/sh LOGGER=/usr/bin/logger case "$1" in start) /bin/ps -auxww | /usr/bin/grep dhclient | $LOGGER /sbin/ifconfig -v ixl0 | $LOGGER killall dhclient /sbin/ifconfig ixl0 down sleep 1 /sbin/ifconfig ixl0 up /sbin/dhclient ixl0 & ;; esac ... At least this way you are not locked out post crash. And speaking of crash, post the contents of the core.txt.3 file in /var/crash ---Mike > > > > As promised, dmesg: > > > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 > root@jimsdesk.example.edu:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) > VT(efifb): resolution 1680x1050 > CPU: Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz (2300.08-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4 > Features=0xbfebfbff > Features2=0x7ffefbff > AMD Features=0x2c100800 > AMD Features2=0x121 > Structured Extended Features=0xd39ffffb > Structured Extended Features2=0x8 > Structured Extended Features3=0xc000000 > XSAVE Features=0xf > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr > TSC: P-state invariant, performance statistics > real memory = 103079215104 (98304 MB) > avail memory = 98749128704 (94174 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs > FreeBSD/SMP: 2 package(s) x 12 core(s) x 2 hardware threads > ioapic6: Changing APIC ID to 16 > ioapic7: Changing APIC ID to 17 > ioapic8: Changing APIC ID to 18 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-31 on motherboard > ioapic2 irqs 32-39 on motherboard > ioapic3 irqs 40-47 on motherboard > ioapic4 irqs 48-55 on motherboard > ioapic5 irqs 72-79 on motherboard > ioapic6 irqs 80-87 on motherboard > ioapic7 irqs 88-95 on motherboard > ioapic8 irqs 96-103 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #38 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #16 Launched! > SMP: AP CPU #12 Launched! > SMP: AP CPU #6 Launched! > SMP: AP CPU #17 Launched! > SMP: AP CPU #40 Launched! > SMP: AP CPU #29 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #27 Launched! > SMP: AP CPU #19 Launched! > SMP: AP CPU #13 Launched! > SMP: AP CPU #22 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #28 Launched! > SMP: AP CPU #30 Launched! > SMP: AP CPU #11 Launched! > SMP: AP CPU #42 Launched! > SMP: AP CPU #32 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #34 Launched! > SMP: AP CPU #14 Launched! > SMP: AP CPU #37 Launched! > SMP: AP CPU #20 Launched! > SMP: AP CPU #41 Launched! > SMP: AP CPU #21 Launched! > SMP: AP CPU #18 Launched! > SMP: AP CPU #35 Launched! > SMP: AP CPU #23 Launched! > SMP: AP CPU #10 Launched! > SMP: AP CPU #36 Launched! > SMP: AP CPU #31 Launched! > SMP: AP CPU #43 Launched! > SMP: AP CPU #44 Launched! > SMP: AP CPU #45 Launched! > SMP: AP CPU #39 Launched! > SMP: AP CPU #8 Launched! > SMP: AP CPU #24 Launched! > SMP: AP CPU #25 Launched! > SMP: AP CPU #46 Launched! > SMP: AP CPU #9 Launched! > SMP: AP CPU #26 Launched! > SMP: AP CPU #33 Launched! > SMP: AP CPU #15 Launched! > SMP: AP CPU #7 Launched! > SMP: AP CPU #47 Launched! > Timecounter "TSC-low" frequency 1150040467 Hz quality 1000 > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4590, 0) error 19 > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > nexus0 > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: numa-domain 0 on acpi0 > cpu1: numa-domain 0 on acpi0 > cpu2: numa-domain 0 on acpi0 > cpu3: numa-domain 0 on acpi0 > cpu4: numa-domain 0 on acpi0 > cpu5: numa-domain 0 on acpi0 > cpu6: numa-domain 0 on acpi0 > cpu7: numa-domain 0 on acpi0 > cpu8: numa-domain 0 on acpi0 > cpu9: numa-domain 0 on acpi0 > cpu10: numa-domain 0 on acpi0 > cpu11: numa-domain 0 on acpi0 > cpu12: numa-domain 0 on acpi0 > cpu13: numa-domain 0 on acpi0 > cpu14: numa-domain 0 on acpi0 > cpu15: numa-domain 0 on acpi0 > cpu16: numa-domain 0 on acpi0 > cpu17: numa-domain 0 on acpi0 > cpu18: numa-domain 0 on acpi0 > cpu19: numa-domain 0 on acpi0 > cpu20: numa-domain 0 on acpi0 > cpu21: numa-domain 0 on acpi0 > cpu22: numa-domain 0 on acpi0 > cpu23: numa-domain 0 on acpi0 > cpu24: numa-domain 1 on acpi0 > cpu25: numa-domain 1 on acpi0 > cpu26: numa-domain 1 on acpi0 > cpu27: numa-domain 1 on acpi0 > cpu28: numa-domain 1 on acpi0 > cpu29: numa-domain 1 on acpi0 > cpu30: numa-domain 1 on acpi0 > cpu31: numa-domain 1 on acpi0 > cpu32: numa-domain 1 on acpi0 > cpu33: numa-domain 1 on acpi0 > cpu34: numa-domain 1 on acpi0 > cpu35: numa-domain 1 on acpi0 > cpu36: numa-domain 1 on acpi0 > cpu37: numa-domain 1 on acpi0 > cpu38: numa-domain 1 on acpi0 > cpu39: numa-domain 1 on acpi0 > cpu40: numa-domain 1 on acpi0 > cpu41: numa-domain 1 on acpi0 > cpu42: numa-domain 1 on acpi0 > cpu43: numa-domain 1 on acpi0 > cpu44: numa-domain 1 on acpi0 > cpu45: numa-domain 1 on acpi0 > cpu46: numa-domain 1 on acpi0 > cpu47: numa-domain 1 on acpi0 > atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 > atrtc0: registered as a time-of-day clock, resolution 1.000000s > Event timer "RTC" frequency 32768 Hz quality 0 > attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > Timecounter "HPET" frequency 24000000 Hz quality 950 > Event timer "HPET" frequency 24000000 Hz quality 350 > Event timer "HPET1" frequency 24000000 Hz quality 340 > Event timer "HPET2" frequency 24000000 Hz quality 340 > Event timer "HPET3" frequency 24000000 Hz quality 340 > Event timer "HPET4" frequency 24000000 Hz quality 340 > Event timer "HPET5" frequency 24000000 Hz quality 340 > Event timer "HPET6" frequency 24000000 Hz quality 340 > Event timer "HPET7" frequency 24000000 Hz quality 340 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 > acpi_syscontainer0: on acpi0 > acpi_syscontainer1: on acpi0 > pcib0: port 0xcf8-0xcff numa-domain 0 on acpi0 > pcib0: _OSC returned error 0x10 > pci0: numa-domain 0 on pcib0 > pci0: at device 8.1 (no driver attached) > pci0: at device 17.0 (no driver attached) > pci0: at device 17.1 (no driver attached) > ahci0: port 0x3070-0x3077,0x3060-0x3063,0x3020-0x303f mem 0x9d206000-0x9d207fff,0x9d209000-0x9d2090ff,0x9d180000-0x9d1fffff irq 16 at device 17.5 numa-domain 0 on pci0 > ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ahciem0: on ahci0 > xhci0: mem 0x383ffff00000-0x383ffff0ffff irq 16 at device 20.0 numa-domain 0 on pci0 > xhci0: 32 bytes context size, 64-bit DMA > usbus0: waiting for BIOS to give up control > xhci_interrupt: host controller halted > usbus0 numa-domain 0 on xhci0 > usbus0: 5.0Gbps Super Speed USB v3.0 > pci0: at device 22.0 (no driver attached) > pci0: at device 22.1 (no driver attached) > pci0: at device 22.4 (no driver attached) > ahci1: port 0x3050-0x3057,0x3040-0x3043,0x3000-0x301f mem 0x9d204000-0x9d205fff,0x9d208000-0x9d2080ff,0x9d100000-0x9d17ffff irq 16 at device 23.0 numa-domain 0 on pci0 > ahci1: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported > ahcich6: at channel 0 on ahci1 > ahcich7: at channel 1 on ahci1 > ahcich8: at channel 2 on ahci1 > ahcich9: at channel 3 on ahci1 > ahcich10: at channel 4 on ahci1 > ahcich11: at channel 5 on ahci1 > ahcich12: at channel 6 on ahci1 > ahcich13: at channel 7 on ahci1 > ahciem1: on ahci1 > pcib1: irq 16 at device 28.0 numa-domain 0 on pci0 > pci1: numa-domain 0 on pcib1 > pcib2: irq 17 at device 28.5 numa-domain 0 on pci0 > pci2: numa-domain 0 on pcib2 > pcib3: irq 17 at device 0.0 numa-domain 0 on pci2 > pci3: numa-domain 0 on pcib3 > vgapci0: port 0x2000-0x207f mem 0x9c000000-0x9cffffff,0x9d000000-0x9d01ffff irq 17 at device 0.0 numa-domain 0 on pci3 > vgapci0: Boot video device > isab0: at device 31.0 numa-domain 0 on pci0 > isa0: numa-domain 0 on isab0 > pci0: at device 31.2 (no driver attached) > pci0: at device 31.5 (no driver attached) > pcib4: numa-domain 0 on acpi0 > pcib4: _OSC returned error 0x10 > pci4: numa-domain 0 on pcib4 > pcib5: irq 39 at device 0.0 numa-domain 0 on pci4 > pci5: numa-domain 0 on pcib5 > pcib6: mem 0xaae00000-0xaae1ffff irq 32 at device 0.0 numa-domain 0 on pci5 > pci6: numa-domain 0 on pcib6 > pcib7: irq 38 at device 3.0 numa-domain 0 on pci6 > pci7: numa-domain 0 on pcib7 > ixl0: mem 0xa9000000-0xa9ffffff,0xaa008000-0xaa00ffff irq 38 at device 0.0 numa-domain 0 on pci7 > ixl0: using 1024 tx descriptors and 1024 rx descriptors > ixl0: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 > ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared > ixl0: Using MSIX interrupts with 9 vectors > ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active > ixl0: Ethernet address: ac:1f:6b:61:54:06 > ixl0: SR-IOV ready > queues is 0xfffffe0001d13000 > ixl0: netmap queues/slots: TX 8/1024, RX 8/1024 > ixl1: mem 0xa8000000-0xa8ffffff,0xaa000000-0xaa007fff irq 38 at device 0.1 numa-domain 0 on pci7 > ixl1: using 1024 tx descriptors and 1024 rx descriptors > ixl1: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 > ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared > ixl1: Using MSIX interrupts with 9 vectors > ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active > ixl1: Ethernet address: ac:1f:6b:61:54:07 > ixl1: SR-IOV ready > queues is 0xfffffe0001e69000 > ixl1: netmap queues/slots: TX 8/1024, RX 8/1024 > pcib8: numa-domain 0 on acpi0 > pcib8: _OSC returned error 0x10 > pci8: numa-domain 0 on pcib8 > pcib9: irq 47 at device 2.0 numa-domain 0 on pci8 > pci9: numa-domain 0 on pcib9 > mpr0: port 0x7000-0x70ff mem 0xb8640000-0xb864ffff,0xb8600000-0xb863ffff irq 42 at device 0.0 numa-domain 0 on pci9 > mpr0: Firmware: 15.00.03.00, Driver: 18.03.00.00-fbsd > mpr0: IOCCapabilities: 7a85c > pcib10: numa-domain 0 on acpi0 > pcib10: _OSC returned error 0x10 > pci10: numa-domain 0 on pcib10 > pci10: at device 14.0 (no driver attached) > pci10: at device 15.0 (no driver attached) > pci10: at device 18.0 (no driver attached) > pci10: at device 18.1 (no driver attached) > pcib11: numa-domain 1 on acpi0 > ixl0: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None > ixl0: link state changed to UP > ixl1: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: Full > ixl1: link state changed to UP > pcib11: _OSC returned error 0x10 > pci11: numa-domain 1 on pcib11 > pci11: at device 8.1 (no driver attached) > pcib12: numa-domain 1 on acpi0 > pcib12: _OSC returned error 0x10 > pci12: numa-domain 1 on pcib12 > pcib13: numa-domain 1 on acpi0 > pcib13: _OSC returned error 0x10 > pci13: numa-domain 1 on pcib13 > pcib14: numa-domain 1 on acpi0 > pcib14: _OSC returned error 0x10 > pci14: numa-domain 1 on pcib14 > pci14: at device 14.0 (no driver attached) > pci14: at device 15.0 (no driver attached) > pci14: at device 18.0 (no driver attached) > pci14: at device 18.1 (no driver attached) > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > orm0: at iomem 0xc0000-0xc7fff on isa0 > ppc0: cannot reserve I/O port range > est0: numa-domain 0 on cpu0 > est1: numa-domain 0 on cpu1 > est2: numa-domain 0 on cpu2 > est3: numa-domain 0 on cpu3 > est4: numa-domain 0 on cpu4 > est5: numa-domain 0 on cpu5 > est6: numa-domain 0 on cpu6 > est7: numa-domain 0 on cpu7 > est8: numa-domain 0 on cpu8 > est9: numa-domain 0 on cpu9 > est10: numa-domain 0 on cpu10 > est11: numa-domain 0 on cpu11 > est12: numa-domain 0 on cpu12 > est13: numa-domain 0 on cpu13 > est14: numa-domain 0 on cpu14 > est15: numa-domain 0 on cpu15 > est16: numa-domain 0 on cpu16 > est17: numa-domain 0 on cpu17 > est18: numa-domain 0 on cpu18 > est19: numa-domain 0 on cpu19 > est20: numa-domain 0 on cpu20 > est21: numa-domain 0 on cpu21 > est22: numa-domain 0 on cpu22 > est23: numa-domain 0 on cpu23 > est24: numa-domain 1 on cpu24 > est25: numa-domain 1 on cpu25 > est26: numa-domain 1 on cpu26 > est27: numa-domain 1 on cpu27 > est28: numa-domain 1 on cpu28 > est29: numa-domain 1 on cpu29 > est30: numa-domain 1 on cpu30 > est31: numa-domain 1 on cpu31 > est32: numa-domain 1 on cpu32 > est33: numa-domain 1 on cpu33 > est34: numa-domain 1 on cpu34 > est35: numa-domain 1 on cpu35 > est36: numa-domain 1 on cpu36 > est37: numa-domain 1 on cpu37 > est38: numa-domain 1 on cpu38 > est39: numa-domain 1 on cpu39 > est40: numa-domain 1 on cpu40 > est41: numa-domain 1 on cpu41 > est42: numa-domain 1 on cpu42 > est43: numa-domain 1 on cpu43 > est44: numa-domain 1 on cpu44 > est45: numa-domain 1 on cpu45 > est46: numa-domain 1 on cpu46 > est47: numa-domain 1 on cpu47 > random: unblocking device. > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounters tick every 1.000 msec > ugen0.1: <0x8086 XHCI root HUB> at usbus0 > mpr0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > SAS Address from SAS device page0 = 5000c500955fb571 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000a> enclosureHandle<0x0002> slot 0 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c5009550e4f1 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000b> enclosureHandle<0x0002> slot 1 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c50095518c95 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000c> enclosureHandle<0x0002> slot 2 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c500955fb3c5 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000d> enclosureHandle<0x0002> slot 3 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c500955fb021 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000e> enclosureHandle<0x0002> slot 4 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 5000c5009550e891 > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000f> enclosureHandle<0x0002> slot 5 > mpr0: At enclosure level 0 and connector name ( ) > mpr0: SAS Address from SAS device page0 = 500304801eb5dbfd > mpr0: Found device <4411,End Device> <12.0Gbps> handle<0x0010> enclosureHandle<0x0002> slot 12 > mpr0: At enclosure level 0 and connector name ( ) > ses0 at ahciem0 bus 0 scbus6 target 0 lun 0 > ses0: SEMB S-E-S 2.00 device > ses0: SEMB SES Device > ses1 at ahciem1 bus 0 scbus15 target 0 lun 0 > ses1: SEMB S-E-S 2.00 device > ses1: SEMB SES Device > ses2 at mpr0 bus 0 scbus16 target 20 lun 0 > ses2: Fixed Enclosure Services SPC-3 SCSI device > ses2: 1200.000MB/s transfers > ses2: Command Queueing enabled > ses2: SCSI-3 ENC Device > ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 > ada0: ACS-3 ATA SATA 3.x device > ada0: Serial Number BTYS81150CWH240AGN > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada0: Command Queueing enabled > ada0: 228936MB (468862128 512 byte sectors) > ada1 at ahcich5 bus 0 scbus5 target 0 lun 0 > ada1: ACS-3 ATA SATA 3.x device > ada1: Serial Number BTYS814205JS240AGN > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada1: Command Queueing enabled > ada1: 228936MB (468862128 512 byte sectors) > uhub0: 26 ports with 26 removable, self powered > ses2: pass4,da0: Element descriptor: 'Slot00' > da1 at mpr0 bus 0 scbus16 target 9 lun 0 > da2 at mpr0 bus 0 scbus16 target 10 lun 0 > da0 at mpr0 bus 0 scbus16 target 8 lun 0 > da5 at mpr0 bus 0 scbus16 target 13 lun 0 > da4 at mpr0 bus 0 scbus16 target 12 lun 0 > da2: Fixed Direct Access SPC-4 SCSI device > da2: Serial Number ZC15T3GB0000C832EM0C > da2: 1200.000MB/s transfers > da2: Command Queueing enabled > da2: 3815447MB (976754646 4096 byte sectors) > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number ZC1606NJ0000R833G9JK > da0: 1200.000MB/s transfers > da0: Command Queueing enabled > da0: 3815447MB (976754646 4096 byte sectors) > da4: Fixed Direct Access SPC-4 SCSI device > da4: Serial Number ZC1606RR0000R833G8YR > da4: 1200.000MB/s transfers > da4: Command Queueing enabled > da4: 3815447MB (976754646 4096 byte sectors) > ses2: pass4,da0: SAS Device Slot Element: 1 Phys at Slot 0 > ses2: phy 0: SAS device type 1 id 0 > da5: da1: Fixed Direct Access SPC-4 SCSI device > da1: Serial Number ZC15V7DV0000C8258M38 > ugen0.2: at usbus0 > da1: 1200.000MB/s transfers > da1: Command Queueing enabled > da1: 3815447MB (976754646 4096 byte sectors) > Fixed Direct Access SPC-4 SCSI device > ukbd0da5: Serial Number ZC15KB320000R832RAR7 > da5: 1200.000MB/s transfers > da5: Command Queueing enabled > da5: 3815447MB (976754646 4096 byte sectors) > numa-domain 0 on uhub0 > da3 at mpr0 bus 0 scbus16 target 11 lun 0 > ukbd0: on usbus0 > kbd2 at ukbd0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb571 > da3: Fixed Direct Access SPC-4 SCSI device > da3: Serial Number ZC1606Q80000R833WKE8 > da3: 1200.000MB/s transfers > da3: Command Queueing enabled > da3: 3815447MB (976754646 4096 byte sectors) > ses2: pass5,da1: Element descriptor: 'Slot01' > ses2: pass5,da1: SAS Device Slot Element: 1 Phys at Slot 1 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e4f1 > ses2: pass6,da2: Element descriptor: 'Slot02' > ses2: pass6,da2: SAS Device Slot Element: 1 Phys at Slot 2 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c50095518c95 > ses2: pass7,da3: Element descriptor: 'Slot03' > ses2: pass7,da3: SAS Device Slot Element: 1 Phys at Slot 3 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb3c5 > ses2: pass8,da4: Element descriptor: 'Slot04' > ses2: pass8,da4: SAS Device Slot Element: 1 Phys at Slot 4 > ugen0.3: at usbus0 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb021 > ses2: pass9,da5: Element descriptor: 'Slot05' > ses2: pass9,da5: SAS Device Slot Element: 1 Phys at Slot 5 > ses2: phy 0: SAS device type 1 id 0 > ses2: phy 0: protocols: Initiator( None ) Target( SSP ) > ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e891 > uhub1 numa-domain 0 on uhub0 > uhub1: on usbus0 > Trying to mount root from zfs:tank/default/root []... > Root mount waiting for: usbus0 > uhub1: 4 ports with 3 removable, self powered > ugen0.4: at usbus0 > ukbd1 numa-domain 0 on uhub1 > ukbd1: on usbus0 > kbd3 at ukbd1 > lo0: link state changed to UP > ums0 numa-domain 0 on uhub1 > ums0: on usbus0 > ums0: 3 buttons and [Z] coordinates ID=0 > > > > And pciconf -lvb: > > > hostb0@pci0:0:0:0: class=0x060000 card=0x098115d9 chip=0x20208086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E DMI3 Registers' > class = bridge > subclass = HOST-PCI > none0@pci0:0:4:0: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff2c000, size 16384, enabled > none1@pci0:0:4:1: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff28000, size 16384, enabled > none2@pci0:0:4:2: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff24000, size 16384, enabled > none3@pci0:0:4:3: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff20000, size 16384, enabled > none4@pci0:0:4:4: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff1c000, size 16384, enabled > none5@pci0:0:4:5: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff18000, size 16384, enabled > none6@pci0:0:4:6: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff14000, size 16384, enabled > none7@pci0:0:4:7: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x383ffff10000, size 16384, enabled > none8@pci0:0:5:0: class=0x088000 card=0x00008086 chip=0x20248086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E MM/Vt-d Configuration Registers' > class = base peripheral > none9@pci0:0:5:2: class=0x088000 card=0x00000000 chip=0x20258086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > ioapic0@pci0:0:5:4: class=0x080020 card=0x20268086 chip=0x20268086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0x9d20a000, size 4096, enabled > none10@pci0:0:8:0: class=0x088000 card=0x00008086 chip=0x20148086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none11@pci0:0:8:1: class=0x110100 card=0x00008086 chip=0x20158086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = dasp > subclass = performance counters > none12@pci0:0:8:2: class=0x088000 card=0x00008086 chip=0x20168086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none13@pci0:0:17:0: class=0xff0000 card=0x098115d9 chip=0xa1ec8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > none14@pci0:0:17:1: class=0xff0000 card=0x098115d9 chip=0xa1ed8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > ahci0@pci0:0:17:5: class=0x010601 card=0x098115d9 chip=0xa1d28086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SSATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > bar [10] = type Memory, range 32, base 0x9d206000, size 8192, enabled > bar [14] = type Memory, range 32, base 0x9d209000, size 256, enabled > bar [18] = type I/O Port, range 32, base 0x3070, size 8, enabled > bar [1c] = type I/O Port, range 32, base 0x3060, size 4, enabled > bar [20] = type I/O Port, range 32, base 0x3020, size 32, enabled > bar [24] = type Memory, range 32, base 0x9d180000, size 524288, enabled > xhci0@pci0:0:20:0: class=0x0c0330 card=0x098115d9 chip=0xa1af8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg USB 3.0 xHCI Controller' > class = serial bus > subclass = USB > bar [10] = type Memory, range 64, base 0x383ffff00000, size 65536, enabled > none15@pci0:0:20:2: class=0x118000 card=0x098115d9 chip=0xa1b18086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg Thermal Subsystem' > class = dasp > bar [10] = type Memory, range 64, base 0x383ffff33000, size 4096, enabled > none16@pci0:0:22:0: class=0x078000 card=0x098115d9 chip=0xa1ba8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff32000, size 4096, enabled > none17@pci0:0:22:1: class=0x078000 card=0x098115d9 chip=0xa1bb8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff31000, size 4096, enabled > none18@pci0:0:22:4: class=0x078000 card=0x098115d9 chip=0xa1be8086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg CSME: HECI' > class = simple comms > bar [10] = type Memory, range 64, base 0x383ffff30000, size 4096, enabled > ahci1@pci0:0:23:0: class=0x010601 card=0x098115d9 chip=0xa1828086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > bar [10] = type Memory, range 32, base 0x9d204000, size 8192, enabled > bar [14] = type Memory, range 32, base 0x9d208000, size 256, enabled > bar [18] = type I/O Port, range 32, base 0x3050, size 8, enabled > bar [1c] = type I/O Port, range 32, base 0x3040, size 4, enabled > bar [20] = type I/O Port, range 32, base 0x3000, size 32, enabled > bar [24] = type Memory, range 32, base 0x9d100000, size 524288, enabled > pcib1@pci0:0:28:0: class=0x060400 card=0x098115d9 chip=0xa1908086 rev=0xf9 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lewisburg PCI Express Root Port' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:28:5: class=0x060400 card=0x098115d9 chip=0xa1958086 rev=0xf9 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lewisburg PCI Express Root Port' > class = bridge > subclass = PCI-PCI > isab0@pci0:0:31:0: class=0x060100 card=0x098115d9 chip=0xa1c38086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg LPC Controller' > class = bridge > subclass = PCI-ISA > none19@pci0:0:31:2: class=0x058000 card=0x098115d9 chip=0xa1a18086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg PMC' > class = memory > bar [10] = type Memory, range 32, base 0x9d200000, size 16384, enabled > none20@pci0:0:31:4: class=0x0c0500 card=0x098115d9 chip=0xa1a38086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SMBus' > class = serial bus > subclass = SMBus > bar [10] = type Memory, range 64, base 0, size 256, disabled > bar [20] = type I/O Port, range 32, base 0x780, size 32, enabled > none21@pci0:0:31:5: class=0x0c8000 card=0x098115d9 chip=0xa1a48086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lewisburg SPI Controller' > class = serial bus > bar [10] = type Memory, range 32, base 0xfe010000, size 4096, enabled > pcib3@pci0:2:0:0: class=0x060400 card=0x11501a03 chip=0x11501a03 rev=0x04 hdr=0x01 > vendor = 'ASPEED Technology, Inc.' > device = 'AST1150 PCI-to-PCI Bridge' > class = bridge > subclass = PCI-PCI > vgapci0@pci0:3:0:0: class=0x030000 card=0x098115d9 chip=0x20001a03 rev=0x41 hdr=0x00 > vendor = 'ASPEED Technology, Inc.' > device = 'ASPEED Graphics Family' > class = display > subclass = VGA > bar [10] = type Memory, range 32, base 0x9c000000, size 16777216, enabled > bar [14] = type Memory, range 32, base 0x9d000000, size 131072, enabled > bar [18] = type I/O Port, range 32, base 0x2000, size 128, enabled > pcib5@pci0:23:0:0: class=0x060400 card=0x098115d9 chip=0x20308086 rev=0x04 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCI Express Root Port A' > class = bridge > subclass = PCI-PCI > none22@pci0:23:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none23@pci0:23:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic1@pci0:23:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xaaf00000, size 4096, enabled > none24@pci0:23:8:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none25@pci0:23:8:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none26@pci0:23:8:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none27@pci0:23:8:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none28@pci0:23:8:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none29@pci0:23:8:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none30@pci0:23:8:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none31@pci0:23:8:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none32@pci0:23:9:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none33@pci0:23:9:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none34@pci0:23:9:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none35@pci0:23:9:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none36@pci0:23:9:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none37@pci0:23:9:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none38@pci0:23:9:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none39@pci0:23:9:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none40@pci0:23:10:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none41@pci0:23:10:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none42@pci0:23:14:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none43@pci0:23:14:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none44@pci0:23:14:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none45@pci0:23:14:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none46@pci0:23:14:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none47@pci0:23:14:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none48@pci0:23:14:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none49@pci0:23:14:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none50@pci0:23:15:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none51@pci0:23:15:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none52@pci0:23:15:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none53@pci0:23:15:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none54@pci0:23:15:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none55@pci0:23:15:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none56@pci0:23:15:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none57@pci0:23:15:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none58@pci0:23:16:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none59@pci0:23:16:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none60@pci0:23:29:0: class=0x088000 card=0x00008086 chip=0x20548086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none61@pci0:23:29:1: class=0x088000 card=0x00008086 chip=0x20558086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none62@pci0:23:29:2: class=0x088000 card=0x00008086 chip=0x20568086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none63@pci0:23:29:3: class=0x088000 card=0x00008086 chip=0x20578086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none64@pci0:23:30:0: class=0x088000 card=0x00008086 chip=0x20808086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none65@pci0:23:30:1: class=0x088000 card=0x00008086 chip=0x20818086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none66@pci0:23:30:2: class=0x088000 card=0x00008086 chip=0x20828086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none67@pci0:23:30:3: class=0x088000 card=0x00008086 chip=0x20838086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none68@pci0:23:30:4: class=0x088000 card=0x00008086 chip=0x20848086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none69@pci0:23:30:5: class=0x088000 card=0x00008086 chip=0x20858086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none70@pci0:23:30:6: class=0x088000 card=0x00008086 chip=0x20868086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > pcib6@pci0:24:0:0: class=0x060400 card=0xdeadbeef chip=0x37c08086 rev=0x09 hdr=0x01 > vendor = 'Intel Corporation' > class = bridge > subclass = PCI-PCI > bar [10] = type Memory, range 64, base 0xaae00000, size 131072, enabled > pcib7@pci0:25:3:0: class=0x060400 card=0xdeadbeef chip=0x37c58086 rev=0x09 hdr=0x01 > vendor = 'Intel Corporation' > class = bridge > subclass = PCI-PCI > ixl0@pci0:26:0:0: class=0x020000 card=0x37d215d9 chip=0x37d28086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection X722 for 10GBASE-T' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0xa9000000, size 16777216, enabled > bar [1c] = type Prefetchable Memory, range 64, base 0xaa008000, size 32768, enabled > ixl1@pci0:26:0:1: class=0x020000 card=0x37d215d9 chip=0x37d28086 rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection X722 for 10GBASE-T' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0xa8000000, size 16777216, enabled > bar [1c] = type Prefetchable Memory, range 64, base 0xaa000000, size 32768, enabled > pcib9@pci0:58:2:0: class=0x060400 card=0x098115d9 chip=0x20328086 rev=0x04 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCI Express Root Port C' > class = bridge > subclass = PCI-PCI > none71@pci0:58:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none72@pci0:58:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic2@pci0:58:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xb8700000, size 4096, enabled > none73@pci0:58:8:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none74@pci0:58:9:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none75@pci0:58:10:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none76@pci0:58:10:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none77@pci0:58:10:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none78@pci0:58:10:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none79@pci0:58:10:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none80@pci0:58:10:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none81@pci0:58:10:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none82@pci0:58:10:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none83@pci0:58:11:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none84@pci0:58:11:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none85@pci0:58:11:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none86@pci0:58:11:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none87@pci0:58:12:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none88@pci0:58:12:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none89@pci0:58:12:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none90@pci0:58:12:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none91@pci0:58:12:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none92@pci0:58:12:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none93@pci0:58:12:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none94@pci0:58:12:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none95@pci0:58:13:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none96@pci0:58:13:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none97@pci0:58:13:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none98@pci0:58:13:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > mpr0@pci0:59:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 rev=0x02 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' > class = mass storage > subclass = SAS > bar [10] = type I/O Port, range 32, base 0x7000, size 256, enabled > bar [14] = type Memory, range 64, base 0xb8640000, size 65536, enabled > bar [1c] = type Memory, range 64, base 0xb8600000, size 262144, enabled > none99@pci0:93:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none100@pci0:93:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic3@pci0:93:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xc5f00000, size 4096, enabled > none101@pci0:93:14:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none102@pci0:93:14:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none103@pci0:93:15:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none104@pci0:93:15:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none105@pci0:93:18:0: class=0x110100 card=0x00008086 chip=0x204c8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none106@pci0:93:18:1: class=0x110100 card=0x00008086 chip=0x204d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none107@pci0:93:18:2: class=0x088000 card=0x00008086 chip=0x204e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = base peripheral > none108@pci0:93:21:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none109@pci0:93:22:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none110@pci0:93:22:4: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none111@pci0:128:4:0: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff1c000, size 16384, enabled > none112@pci0:128:4:1: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff18000, size 16384, enabled > none113@pci0:128:4:2: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff14000, size 16384, enabled > none114@pci0:128:4:3: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff10000, size 16384, enabled > none115@pci0:128:4:4: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff0c000, size 16384, enabled > none116@pci0:128:4:5: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff08000, size 16384, enabled > none117@pci0:128:4:6: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff04000, size 16384, enabled > none118@pci0:128:4:7: class=0x088000 card=0x00008086 chip=0x20218086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CBDMA Registers' > class = base peripheral > bar [10] = type Memory, range 64, base 0x393ffff00000, size 16384, enabled > none119@pci0:128:5:0: class=0x088000 card=0x00008086 chip=0x20248086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E MM/Vt-d Configuration Registers' > class = base peripheral > none120@pci0:128:5:2: class=0x088000 card=0x00000000 chip=0x20258086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > ioapic4@pci0:128:5:4: class=0x080020 card=0x20268086 chip=0x20268086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xd3700000, size 4096, enabled > none121@pci0:128:8:0: class=0x088000 card=0x00008086 chip=0x20148086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none122@pci0:128:8:1: class=0x110100 card=0x00008086 chip=0x20158086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = dasp > subclass = performance counters > none123@pci0:128:8:2: class=0x088000 card=0x00008086 chip=0x20168086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E Ubox Registers' > class = base peripheral > none124@pci0:133:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none125@pci0:133:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic5@pci0:133:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xe0f00000, size 4096, enabled > none126@pci0:133:8:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none127@pci0:133:8:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none128@pci0:133:8:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none129@pci0:133:8:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none130@pci0:133:8:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none131@pci0:133:8:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none132@pci0:133:8:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none133@pci0:133:8:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none134@pci0:133:9:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none135@pci0:133:9:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none136@pci0:133:9:2: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none137@pci0:133:9:3: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none138@pci0:133:9:4: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none139@pci0:133:9:5: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none140@pci0:133:9:6: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none141@pci0:133:9:7: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none142@pci0:133:10:0: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none143@pci0:133:10:1: class=0x088000 card=0x00008086 chip=0x208d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none144@pci0:133:14:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none145@pci0:133:14:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none146@pci0:133:14:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none147@pci0:133:14:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none148@pci0:133:14:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none149@pci0:133:14:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none150@pci0:133:14:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none151@pci0:133:14:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none152@pci0:133:15:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none153@pci0:133:15:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none154@pci0:133:15:2: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none155@pci0:133:15:3: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none156@pci0:133:15:4: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none157@pci0:133:15:5: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none158@pci0:133:15:6: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none159@pci0:133:15:7: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none160@pci0:133:16:0: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none161@pci0:133:16:1: class=0x088000 card=0x00008086 chip=0x208e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none162@pci0:133:29:0: class=0x088000 card=0x00008086 chip=0x20548086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none163@pci0:133:29:1: class=0x088000 card=0x00008086 chip=0x20558086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none164@pci0:133:29:2: class=0x088000 card=0x00008086 chip=0x20568086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none165@pci0:133:29:3: class=0x088000 card=0x00008086 chip=0x20578086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E CHA Registers' > class = base peripheral > none166@pci0:133:30:0: class=0x088000 card=0x00008086 chip=0x20808086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none167@pci0:133:30:1: class=0x088000 card=0x00008086 chip=0x20818086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none168@pci0:133:30:2: class=0x088000 card=0x00008086 chip=0x20828086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none169@pci0:133:30:3: class=0x088000 card=0x00008086 chip=0x20838086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none170@pci0:133:30:4: class=0x088000 card=0x00008086 chip=0x20848086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none171@pci0:133:30:5: class=0x088000 card=0x00008086 chip=0x20858086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none172@pci0:133:30:6: class=0x088000 card=0x00008086 chip=0x20868086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E PCU Registers' > class = base peripheral > none173@pci0:174:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none174@pci0:174:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic6@pci0:174:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xee700000, size 4096, enabled > none175@pci0:174:8:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none176@pci0:174:9:0: class=0x088000 card=0x00008086 chip=0x20668086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none177@pci0:174:10:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none178@pci0:174:10:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none179@pci0:174:10:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none180@pci0:174:10:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none181@pci0:174:10:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none182@pci0:174:10:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none183@pci0:174:10:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none184@pci0:174:10:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none185@pci0:174:11:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none186@pci0:174:11:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none187@pci0:174:11:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none188@pci0:174:11:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none189@pci0:174:12:0: class=0x088000 card=0x00008086 chip=0x20408086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none190@pci0:174:12:1: class=0x088000 card=0x00008086 chip=0x20418086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none191@pci0:174:12:2: class=0x088000 card=0x00008086 chip=0x20428086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none192@pci0:174:12:3: class=0x088000 card=0x00008086 chip=0x20438086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none193@pci0:174:12:4: class=0x088000 card=0x00008086 chip=0x20448086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none194@pci0:174:12:5: class=0x088000 card=0x00008086 chip=0x20458086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none195@pci0:174:12:6: class=0x088000 card=0x00008086 chip=0x20468086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none196@pci0:174:12:7: class=0x088000 card=0x00008086 chip=0x20478086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none197@pci0:174:13:0: class=0x088000 card=0x00008086 chip=0x20488086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none198@pci0:174:13:1: class=0x088000 card=0x00008086 chip=0x20498086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none199@pci0:174:13:2: class=0x088000 card=0x00008086 chip=0x204a8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none200@pci0:174:13:3: class=0x088000 card=0x00008086 chip=0x204b8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none201@pci0:215:5:0: class=0x088000 card=0x00008086 chip=0x20348086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none202@pci0:215:5:2: class=0x088000 card=0x00000000 chip=0x20358086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E RAS Configuration Registers' > class = base peripheral > ioapic7@pci0:215:5:4: class=0x080020 card=0x20368086 chip=0x20368086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > subclass = interrupt controller > bar [10] = type Memory, range 32, base 0xfbf00000, size 4096, enabled > none203@pci0:215:14:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none204@pci0:215:14:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none205@pci0:215:15:0: class=0x110100 card=0x00008086 chip=0x20588086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = dasp > subclass = performance counters > none206@pci0:215:15:1: class=0x088000 card=0x00008086 chip=0x20598086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > class = base peripheral > none207@pci0:215:18:0: class=0x110100 card=0x00008086 chip=0x204c8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none208@pci0:215:18:1: class=0x110100 card=0x00008086 chip=0x204d8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = dasp > subclass = performance counters > none209@pci0:215:18:2: class=0x088000 card=0x00008086 chip=0x204e8086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M3KTI Registers' > class = base peripheral > none210@pci0:215:21:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none211@pci0:215:22:0: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > none212@pci0:215:22:4: class=0x088000 card=0x00008086 chip=0x20188086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Sky Lake-E M2PCI Registers' > class = base peripheral > > > # grep swap /etc/fstab ; echo > #/dev/mirror/swap none swap sw > /dev/gpt/swap0 none swap sw > #/dev/gpt/swap1 none swap sw > > # swapinfo -h > Device 1024-blocks Used Avail Capacity > /dev/gpt/swap0 16777216 0B 16G 0% > > # ls -ltr /var/crash/ > total 3844652 > -rw-r--r-- 1 root wheel 5 Jun 21 21:34 minfree > -rw------- 1 root wheel 462 Jul 5 11:46 info.0 > -rw------- 1 root wheel 5043531776 Jul 5 11:47 vmcore.0 > -rw------- 1 root wheel 128912 Jul 5 11:47 core.txt.0 > -rw------- 1 root wheel 464 Jul 6 12:24 info.1 > -rw------- 1 root wheel 3628683264 Jul 6 12:24 vmcore.1 > -rw------- 1 root wheel 127947 Jul 6 12:24 core.txt.1 > -rw-r--r-- 1 root wheel 639 Jul 9 12:51 ls.out.0 > -rw-r--r-- 1 root wheel 3960 Jul 11 06:36 zpool-iostat.out > -rw------- 1 root wheel 464 Jul 11 12:47 info.2 > -rw------- 1 root wheel 3777585152 Jul 11 12:48 vmcore.2 > -rw------- 1 root wheel 127775 Jul 11 12:48 core.txt.2 > -rw-r--r-- 1 root wheel 0 Jul 11 13:12 zfs-stress.start > -rw-r--r-- 1 root wheel 2 Jul 11 13:37 bounds > -rw------- 1 root wheel 458 Jul 11 13:37 info.3 > -rw------- 1 root wheel 7352229888 Jul 11 13:38 vmcore.3 > lrwxr-xr-x 1 root wheel 6 Jul 11 13:38 info.last@ -> info.3 > lrwxr-xr-x 1 root wheel 8 Jul 11 13:38 vmcore.last@ -> vmcore.3 > -rw------- 1 root wheel 143973 Jul 11 13:38 core.txt.3 > > _______________________________________________ > 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" > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-questions@freebsd.org Thu Jul 12 18:36:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCCC010319B7 for ; Thu, 12 Jul 2018 18:36:00 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (ns.umpquanet.com [209.216.177.146]) (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 1894577D86 for ; Thu, 12 Jul 2018 18:35:59 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (localhost [127.0.0.1]) by g5.umpquanet.com (8.15.2/8.15.2) with ESMTPS id w6CIZDvW080948 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 Jul 2018 11:35:13 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by g5.umpquanet.com (8.15.2/8.15.2/Submit) id w6CIZC00080947; Thu, 12 Jul 2018 11:35:12 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: g5.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Thu, 12 Jul 2018 11:35:12 -0700 From: Jim Long To: Mike Tancsa Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE Message-ID: <20180712183512.GA75020@g5.umpquanet.com> References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 18:36:01 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jul 12, 2018 at 11:53:31AM -0400, Mike Tancsa wrote: > > prior to the crash, if you run gstat does it show the disks at 100% load ? > > You have a lot of RAM, is ARC by chance using all of it ? Try putting a > hard limit on it. So if you have 98G of RAM, place a limit at something > like 70G for now. > Also, what is the file system like ? Is it a few big files or MANY > little files. Post the output of zfs-stats -a > ..snip.. > And speaking > of crash, post the contents of the > core.txt.3 > > file in /var/crash > > ---Mike Mike: Thank you for copying me on your reply, I forgot to request that. I read the digest version of the list, so a direct reply is much more timely. The core.txt.3 file is attached. Your suggestion of dhclient-safety.sh makes sense, I should have thought of using a legacy rc.d script in /usr/local/etc/rc.d/ zfs-stats.out is also attached. Yes, ARC usage is high. top shows: last pid: 2215; load averages: 1.50, 1.69, 1.69 up 0+00:44:59 11:02:00 27 processes: 2 running, 25 sleeping CPU: 0.0% user, 0.0% nice, 9.0% system, 0.1% interrupt, 90.9% idle Mem: 1416K Active, 11M Inact, 2788K Laundry, 91G Wired, 1236M Free ARC: 84G Total, 68M MFU, 83G MRU, 15M Anon, 877M Header, 4078K Other 83G Compressed, 148G Uncompressed, 1.78:1 Ratio Swap: 16G Total, 15M Used, 16G Free I'm re-running the test now. I had shut off hyperthreading to go down to 24 cores, but it's back on now. This server will be a computational resource, not just storage, so I'd like to find a way to stablize the configuration with hyperthreading enabled, if possible. Thanks again, Jim zfs-stress.sh: #!/usr/bin/env bash FILE="/var/crash/zfs-stress.start" SLEEP_TIME=10 # if this script causes a crash, then we should expect to see a # crash dump newer than this file: touch $FILE logger "$0 : begin" echo 'zfs destroy -r mendeleev@stress-test' | sh -v 2>&1 | logger echo 'zfs snap -r mendeleev@stress-test' | sh -v 2>&1 | logger logger "$0 : backgrounding 'zfs send -R mendeleev@stress-test > /dev/null'" zfs send -R mendeleev@stress-test > /dev/null & while [ -f $FILE ] && sleep $SLEEP_TIME; do printf "gstat -ab:\n$(gstat -ab)\n\n" | logger top | head -8 | logger done [ -f $FILE ] || echo "$0 : $FILE has disappeared ... terminating." -- snip --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="core.txt.3" mendeleev3 dumped core - see /var/crash/vmcore.3 Wed Jul 11 13:38:41 PDT 2018 FreeBSD mendeleev3 11.2-STABLE FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 root@jimsdesk:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 38; apic id = 32 fault virtual address = 0x5a fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80dff30d stack pointer = 0x28:0xfffffe17eaaa8440 frame pointer = 0x28:0xfffffe17eaaa8480 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (system_taskq_33) trap number = 12 panic: page fault cpuid = 38 KDB: stack backtrace: #0 0xffffffff80b3d907 at kdb_backtrace+0x67 #1 0xffffffff80af6e77 at vpanic+0x177 #2 0xffffffff80af6cf3 at panic+0x43 #3 0xffffffff80f77fef at trap_fatal+0x35f #4 0xffffffff80f78049 at trap_pfault+0x49 #5 0xffffffff80f77824 at trap+0x2d4 #6 0xffffffff80f5786c at calltrap+0x8 #7 0xffffffff80f7938b at uma_small_alloc+0x5b #8 0xffffffff80de5b72 at keg_alloc_slab+0xe2 #9 0xffffffff80de857e at keg_fetch_slab+0x14e #10 0xffffffff80de7db4 at zone_fetch_slab+0x64 #11 0xffffffff80de7e8f at zone_import+0x3f #12 0xffffffff80de4599 at uma_zalloc_arg+0x3d9 #13 0xffffffff8225b692 at abd_alloc+0x112 #14 0xffffffff8226064e at arc_hdr_alloc_pabd+0x8e #15 0xffffffff8225dbcf at arc_hdr_alloc+0x11f #16 0xffffffff8225f84f at arc_read+0x24f #17 0xffffffff8228342d at traverse_prefetcher+0x18d Uptime: 29m53s Dumping 7011 out of 96901 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/zfs.ko.debug...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /usr/lib/debug//boot/kernel/opensolaris.ko.debug...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/kernel/ums.ko...Reading symbols from /usr/lib/debug//boot/kernel/ums.ko.debug...done. done. Loaded symbols for /boot/kernel/ums.ko #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80af6a8b in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80af6eb1 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80af6cf3 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f77fef in trap_fatal (frame=0xfffffe17eaaa8380, eva=90) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f78049 in trap_pfault (frame=0xfffffe17eaaa8380, usermode=0) at pcpu.h:230 #6 0xffffffff80f77824 in trap (frame=0xfffffe17eaaa8380) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5786c in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff80dff30d in vm_page_alloc_after (object=0x0, pindex=0, req=, mpred=0x0) at vm_phys.h:121 #9 0xffffffff80f7938b in uma_small_alloc (zone=, bytes=, flags=, wait=2305) at /usr/src/sys/amd64/amd64/uma_machdep.c:52 #10 0xffffffff80de5b72 in keg_alloc_slab (keg=0xfffff80162a67780, zone=, wait=2305) at /usr/src/sys/vm/uma_core.c:978 #11 0xffffffff80de857e in keg_fetch_slab (keg=0xfffff80162a67780, zone=0xfffffe000423a000, flags=1) at /usr/src/sys/vm/uma_core.c:2358 #12 0xffffffff80de7db4 in zone_fetch_slab (zone=0xfffffe000423a000, keg=0xfffff80162a67780, flags=1) at /usr/src/sys/vm/uma_core.c:2390 #13 0xffffffff80de7e8f in zone_import (zone=0xfffffe000423a000, bucket=0xfffff80311698018, max=, flags=1) at /usr/src/sys/vm/uma_core.c:2516 #14 0xffffffff80de4599 in uma_zalloc_arg (zone=0xfffffe000423a000, udata=0xfffff801619cbf40, flags=2) at /usr/src/sys/vm/uma_core.c:2546 #15 0xffffffff8225b692 in abd_alloc (size=131072, is_metadata=0) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/abd.c:177 #16 0xffffffff8226064e in arc_hdr_alloc_pabd (hdr=0xfffff807718f8620) at cpufunc.h:98 #17 0xffffffff8225dbcf in arc_hdr_alloc (spa=773887303047704091, psize=, lsize=, compression_type=ZIO_COMPRESS_OFF, type=ARC_BUFC_DATA) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:3248 #18 0xffffffff8225f84f in arc_read (pio=0x0, spa=0xfffffe001d8c3000, bp=0xfffffe002542ab00, done=0, private=0x0, priority=ZIO_PRIORITY_ASYNC_READ, zio_flags=, arc_flags=0xfffffe17eaaa87d4, zb=0xfffffe17eaaa8970) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:5482 #19 0xffffffff8228342d in traverse_prefetcher (spa=0xfffffe001d8c3000, zilog=, bp=0xfffffe002542ab00, zb=0xfffffe17eaaa8970, dnp=, arg=0xfffffe17eb6d11e0) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:520 #20 0xffffffff822828c3 in traverse_visitbp (td=0xfffffe17eaaa91b8, dnp=0xfffffe00e9d62e00, bp=0xfffffe002542ab00, zb=0xfffffe17eaaa8970) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:290 #21 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffffe00e9d62e00, bp=0xfffffe002fe8f180, zb=0xfffffe17eaaa8a50) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #22 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffffe00e9d62e00, bp=0xfffffe00e9d62e40, zb=0xfffffe17eaaa8ab8) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #23 0xffffffff822835f3 in traverse_dnode (td=0xfffffe17eaaa91b8, dnp=0xfffffe00e9d62e00, objset=3530, object=381335) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:473 #24 0xffffffff82283000 in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffffe002a586600, zb=0xfffffe17eaaa8c80) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:344 #25 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffffe008e440580, zb=0xfffffe17eaaa8d60) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #26 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffffe002bdc2000, zb=0xfffffe17eaaa8e40) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #27 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffffe0044482000, zb=0xfffffe17eaaa8f20) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #28 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffffe002b1a2000, zb=0xfffffe17eaaa9000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #29 0xffffffff82282add in traverse_visitbp (td=, dnp=0xfffff801800c6800, bp=0xfffff801800c6840, zb=0xfffffe17eaaa9068) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:322 #30 0xffffffff822835f3 in traverse_dnode (td=0xfffffe17eaaa91b8, dnp=0xfffff801800c6800, objset=3530, object=0) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:473 #31 0xffffffff82282da8 in traverse_visitbp (td=, dnp=0x0, bp=0xfffff801801a8680, zb=0xfffffe17eaaa9218) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:376 #32 0xffffffff82282656 in traverse_prefetch_thread (arg=0xfffffe17eb6d1180) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c:540 #33 0xffffffff82244940 in taskq_run (arg=0xfffff801dafd2ae0, pending=) at /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_taskq.c:110 #34 0xffffffff80b4f114 in taskqueue_run_locked (queue=0xfffff80161a6da00) at /usr/src/sys/kern/subr_taskqueue.c:463 #35 0xffffffff80b50278 in taskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_taskqueue.c:755 #36 0xffffffff80aba383 in fork_exit ( callout=0xffffffff80b501e0 , arg=0xfffff80161a8c200, frame=0xfffffe17eaaa9340) at /usr/src/sys/kern/kern_fork.c:1054 #37 0xffffffff80f5881e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:972 #38 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ ps -axlww UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 -16 0 0 0 vmwait DLs - 0:10.03 [kernel] 0 1 0 0 20 0 5416 1092 wait DLs - 0:00.14 [init] 0 2 0 0 -16 0 0 0 crypto_w DL - 0:00.00 [crypto] 0 3 0 0 -16 0 0 0 crypto_r DL - 0:00.00 [crypto returns] 0 4 0 0 -16 0 0 0 - RL - 0:00.55 [cam] 0 5 0 0 -16 0 0 0 - DL - 0:00.00 [soaiod1] 0 6 0 0 -16 0 0 0 - DL - 0:00.00 [soaiod2] 0 7 0 0 -16 0 0 0 - DL - 0:00.00 [soaiod3] 0 8 0 0 -16 0 0 0 - DL - 0:00.00 [soaiod4] 0 9 0 0 -8 0 0 0 - RL - 0:11.15 [zfskern] 0 10 0 0 -16 0 0 0 audit_wo DL - 0:00.00 [audit] 0 11 0 0 155 0 0 0 - RL - 52:54.37 [idle] 0 12 0 0 -56 0 0 0 - WL - 0:02.28 [intr] 0 13 0 0 -8 0 0 0 - DL - 0:00.01 [geom] 0 14 0 0 -68 0 0 0 - DL - 0:00.06 [usb] 0 15 0 0 -16 0 0 0 waiting_ DL - 0:00.00 [sctp_iterator] 0 16 0 0 -16 0 0 0 - DL - 0:00.04 [rand_harvestq] 0 17 0 0 -16 0 0 0 idle DL - 0:00.00 [enc_daemon0] 0 18 0 0 -16 0 0 0 idle DL - 0:00.02 [enc_daemon1] 0 19 0 0 -16 0 0 0 idle DL - 0:00.00 [enc_daemon2] 0 20 0 0 -16 0 0 0 arc_recl DL - 0:00.28 [pagedaemon] 0 21 0 0 -16 0 0 0 psleep DL - 0:00.00 [vmdaemon] 0 22 0 0 155 0 0 0 pgzero DL - 0:00.00 [pagezero] 0 23 0 0 -16 0 0 0 - DL - 0:00.00 [bufspacedaemon] 0 24 0 0 -16 0 0 0 psleep DL - 0:00.00 [bufdaemon] 0 25 0 0 -16 0 0 0 vlruwt DL - 0:00.00 [vnlru] 0 26 0 0 16 0 0 0 syncer DL - 0:00.00 [syncer] 0 125 1 0 52 0 6268 1972 pause Ds - 0:00.00 [adjkerntz] 0 491 1 0 52 0 6524 2336 select Ds - 0:00.00 [dhclient] 65 553 1 0 20 0 6524 2468 select DCs - 0:00.00 [dhclient] 0 606 1 0 52 0 6580 2216 select Ds - 0:00.00 [moused] 0 620 1 0 20 0 9180 5112 select Ds - 0:00.00 [devd] 0 882 1 0 20 0 6412 2464 select Ds - 0:00.02 [syslogd] 0 1089 1 0 20 0 12432 12512 select Ds - 0:01.04 [ntpd] 0 1171 1 0 25 0 12828 7052 select Ds - 0:00.00 [sshd] 0 1185 1 0 20 0 10432 6372 select Ds - 0:00.00 [sendmail] 25 1196 1 0 52 0 10432 6528 pause Ds - 0:00.00 [sendmail] 0 1204 1 0 20 0 6444 2484 nanslp Ds - 0:00.00 [cron] 0 1283 1 0 20 0 6932 2992 wait Ds - 0:00.00 [login] 0 1284 1 0 20 0 6932 2992 wait Ds - 0:00.00 [login] 0 1285 1 0 52 0 6388 2200 ttyin Ds+ - 0:00.00 [getty] 0 1286 1 0 52 0 6388 2200 ttyin Ds+ - 0:00.00 [getty] 0 1287 1 0 20 0 6932 2992 wait Ds - 0:00.00 [login] 0 1288 1 0 52 0 6388 2200 ttyin Ds+ - 0:00.00 [getty] 0 1289 1 0 52 0 6388 2200 ttyin Ds+ - 0:00.00 [getty] 0 1290 1 0 52 0 6388 2200 ttyin Ds+ - 0:00.00 [getty] 0 1291 1171 0 20 0 13140 8308 select Ds - 0:00.00 [sshd] 0 1293 1291 0 20 0 7776 4040 select Ds+ - 0:00.00 [bash] 0 1411 1283 0 20 0 7776 4040 wait D - 0:00.00 [bash] 0 1444 1411 0 20 0 7776 3636 wait D - 0:00.00 [bash] 0 1450 1444 0 52 0 7768 4444 hdr->b_l D - 0:00.00 [zfs] 0 1477 1287 0 49 0 7776 4036 wait D - 0:00.00 [bash] 0 1499 1477 0 30 10 9292 5396 select DN+ - 0:00.00 [systat] 0 1506 1284 0 20 0 7776 4044 select D+ - 0:00.00 [bash] 0 1570 1506 0 20 0 7776 4040 wait D - 0:00.00 [bash] 0 1590 1411 0 20 0 6276 2072 kqread D+ - 0:00.00 [tail] 0 1596 1444 0 20 0 4220 2000 nanslp DC - 0:00.00 [sleep] 0 1599 1570 0 20 0 4220 2000 nanslp DC - 0:00.00 [sleep] ------------------------------------------------------------------------ vmstat -s 39539081 cpu context switches 2335473 device interrupts 17734 software interrupts 570899 traps 3744909 system calls 26 kernel threads created 912 fork() calls 657 vfork() calls 4 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 706 vnode pager pageins 6346 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 0 page daemon wakeups 0 pages examined by the page daemon 0 clean page reclamation shortfalls 0 pages reactivated by the page daemon 42293 copy-on-write faults 171 copy-on-write optimized faults 525374 zero fill pages zeroed 11 zero fill pages prezeroed 0 intransit blocking page faults 628010 total VM faults taken 533 page faults requiring I/O 0 pages affected by kernel thread creation 36395 pages affected by fork() 22985 pages affected by vfork() 200 pages affected by rfork() 1210386 pages freed 0 pages freed by daemon 0 pages freed by exiting processes 1036 pages active 5628 pages inactive 4623 pages in the laundry queue 24162530 pages wired down 1023 pages free 4096 bytes per page 0 total name lookups cache hits (0% pos + 0% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% ------------------------------------------------------------------------ vmstat -m Type InUse MemUse HighUse Requests Size(s) feeder 7 1K - 7 32 SCSI ENC 146 340K - 3446 16,64,128,256,512,1024,2048,32768,65536 nvlist 104 10K - 104 16,64,128 UART 6 5K - 6 16,1024 acpiintr 1 1K - 1 64 USB 35 54K - 36 16,32,128,256,512,1024,2048,4096 USBdev 25 8K - 25 32,64,128,256,512,1024,4096 acpica 63733 6361K - 720376 16,32,64,128,256,512,1024,2048,4096 acpitask 1 64K - 1 65536 acpisem 85 11K - 85 128 acpidev 293 19K - 293 64 CAM SIM 18 5K - 18 256 CAM XPT 131 12K - 656 16,32,64,128,256,512,1024,2048,65536 CAM DEV 29 58K - 61 2048 CAM CCB 0 0K - 2756925 2048 CAM path 40 2K - 764 32 CAM periph 24 6K - 60 16,32,64,128,256 vtbuf 24 4992K - 46 4096 vt 11 6K - 11 512 CAM I/O Scheduler 8 1K - 8 128 DEVFS3 435 109K - 467 256 DEVFS1 250 125K - 281 512 DEVFS_RULE 55 26K - 55 64,512 DEVFS 57 2K - 58 16,32,128 DEVFSP 4 1K - 4 64 NFSD V4client 1 1K - 1 256 NFSD lckfile 1 1K - 1 256 NFSD session 1 1K - 1 1024 pfs_nodes 21 6K - 21 256 GEOM 705 109K - 5201 16,32,64,128,256,512,1024,2048,4096,8192,16384 raid_data 0 0K - 738 32,128,256 isadev 6 1K - 6 128 pci_link 16 2K - 16 64,128 cdev 3 1K - 3 256 filedesc 23 181K - 431 32,4096,16384 sigio 0 0K - 1 64 filecaps 7 1K - 124 16,32,64 kdtrace 856 204K - 4143 64,256 kenv 121 13K - 125 16,32,64,128,8192 kqueue 60 6K - 1602 64,256,2048 proc-args 415 14K - 1856 16,32,64,128,256 hhook 13 4K - 13 256 ithread 337 57K - 337 32,128,256 KTRACE 100 13K - 100 128 acpi_perf 48 24K - 48 512 linker 196 35K - 206 16,32,64,128,256,512,1024,2048,4096,8192 lockf 23 3K - 139 64,128 loginclass 3 1K - 3 64 devbuf 21124 41984K - 26728 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 temp 208 21K - 3659 16,32,64,128,256,512,1024,2048,4096,16384,65536 module 505 64K - 506 128 mtx_pool 2 16K - 2 8192 osd 7 1K - 98 16,32,64,128,256 pmchooks 1 1K - 1 128 pgrp 29 4K - 106 128 session 22 3K - 35 128 proc 2 256K - 2 subproc 483 445K - 2025 512,4096 cred 51 13K - 427 256 CAM queue 47 139K - 154 16,32,64,128,512,16384 plimit 22 6K - 487 256 uidinfo 4 33K - 18 128,32768 dumper 1 4K - 1 4096 sysctl 0 0K - 1 64 sysctloid 12625 644K - 12914 16,32,64,128,256 sysctltmp 0 0K - 105 16,32,64,256,1024 tidhash 1 256K - 1 callout 49 13448K - 49 umtx 2012 252K - 2012 128 p1003.1b 1 1K - 1 16 SWAP 2 1097K - 2 32 bus 2246 284K - 48881 16,32,64,128,256,512,1024 bus-sc 269 2024K - 40020 16,32,128,256,512,1024,2048,4096,8192,16384,32768,65536 devstat 44 89K - 44 32,4096 eventhandler 109 9K - 109 64,128 gtaskqueue 294 53K - 294 16,32,256,8192 kobj 341 1364K - 1437 4096 Per-cpu 1 1K - 1 32 rman 337 39K - 807 32,128 sbuf 0 0K - 12260 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 toponodes 124 16K - 124 128 taskqueue 189 24K - 204 16,32,64,128,256,512 terminal 11 3K - 11 256 Unitno 23 2K - 533 32,64 vmem 2 640K - 6 16384,65536 ioctlops 0 0K - 119 256,512,1024 select 37 5K - 37 128 iov 0 0K - 273381 16,32,64,128,256,512 msg 4 30K - 4 2048,4096,8192,16384 sem 4 106K - 4 2048,4096 shm 1 32K - 1 32768 tty 15 15K - 15 1024 pts 1 1K - 1 256 mbuf_tag 0 0K - 27 32 shmfd 1 8K - 1 8192 soname 4 1K - 62160 16,32,128 pcb 20 16535K - 99 16,32,128,1024,2048,8192 kbdmux 8 22K - 8 16,512,1024,2048,16384 acl 0 0K - 46 4096 vfscache 4 17025K - 4 512 vfs_hash 1 8192K - 1 vnodes 1 1K - 1 256 mount 220 8K - 506 16,32,64,128,256 statfs 0 0K - 273 512 LED 56 4K - 56 16,128 vnodemarker 0 0K - 1263 512 arc4random 1 32K - 1 32768 BPF 11 18K - 11 128,512,4096 ifnet 4 7K - 4 128,2048 ifaddr 45 13K - 47 16,32,64,128,256,512,2048,4096 ether_multi 17 1K - 22 16,32,64 clone 7 1K - 7 128 ipsec 1 1K - 1 256 lltable 14 4K - 14 256,512 routetbl 25 4K - 30 32,64,128,512 igmp 3 1K - 3 128 in_mfilter 1 1K - 1 1024 in_multi 2 1K - 3 256 ip_moptions 2 1K - 2 64,256 encap_export_host 2 2K - 2 1024 sctp_a_it 0 0K - 2 16 sctp_vrf 1 1K - 1 64 sctp_ifa 4 1K - 4 128 sctp_ifn 2 1K - 2 128 sctp_iter 0 0K - 2 256 hostcache 1 32K - 1 32768 LRO 8 8K - 8 1024 tcpfunc 1 1K - 1 32 syncache 1 68K - 1 in6_mfilter 1 1K - 1 1024 in6_multi 15 2K - 15 32,256 ip6_moptions 2 1K - 2 32,256 ip6opt 3 1K - 3 256 mld 3 1K - 3 128 ip6ndp 4 1K - 4 64,256 inpcbpolicy 13 1K - 213 32 secasvar 1 1K - 1 1024 sahead 1 1K - 1 1024 ipsecpolicy 2 2K - 6 256,1024 ipsec-saq 2 2K - 2 1024 crypto 1 1K - 1 512 rpc 2 16K - 2 8192 audit_evclass 189 6K - 234 32 ufs_quota 1 8192K - 1 vm_pgdata 1 1K - 1 128 UMAHash 47 263131K - 182 512,1024,2048,4096,8192,16384,32768,65536 memdesc 1 4K - 1 4096 mpr 19 559K - 59 16,32,64,128,256,1024,4096,8192,65536 CAM dev queue 18 2K - 18 64 scsi_da 0 0K - 798 32,64,256 ixl 2 8K - 2 4096 sr_iov 2 1K - 2 512 apmdev 1 1K - 1 128 madt_table 0 0K - 1 4096 entropy 1 1K - 11 32,4096 io_apic 9 10K - 9 1024,2048 MCA 97 31K - 97 128,512 msi 30 4K - 30 128 nexusdev 4 1K - 4 16 kstat_data 8 1K - 8 64 solaris 2099399 780112K - 76828357 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 sfs_nodes 36 18K - 36 512 ------------------------------------------------------------------------ vmstat -z ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 384, 0, 238, 2, 238, 0, 0 UMA Zones: 6784, 0, 255, 0, 255, 0, 0 UMA Slabs: 80, 0,22397947, 3,22420279, 0, 0 UMA Hash: 256, 0, 61, 59, 108, 0, 0 4 Bucket: 32, 0, 3237, 12013, 69203, 0, 0 6 Bucket: 48, 0, 920, 12028, 23096, 0, 0 8 Bucket: 64, 0, 299, 11915, 15149, 15, 0 12 Bucket: 96, 0, 473, 10884, 33544, 0, 0 16 Bucket: 128, 0, 574, 8664, 30440, 0, 0 32 Bucket: 256, 0, 1452, 6678, 194385, 139, 0 64 Bucket: 512, 0, 717, 1739, 307173, 138, 0 128 Bucket: 1024, 0, 1090, 1806, 447171, 0, 0 256 Bucket: 2048, 0, 1862, 1830, 200778, 16, 0 vmem btag: 56, 0, 59405, 10033, 64207, 490, 0 VM OBJECT: 240, 0, 1881, 2759, 18824, 0, 0 RADIX NODE: 144, 0, 76564, 3653, 184780, 0, 0 MAP: 240, 0, 3, 61, 3, 0, 0 KMAP ENTRY: 128, 0, 6, 397, 6, 0, 0 MAP ENTRY: 128, 0, 956, 6670, 51520, 0, 0 VMSPACE: 2520, 0, 32, 196, 1575, 0, 0 fakepg: 104, 0, 0, 152, 3, 0, 0 mt_zone: 16400, 0, 408, 0, 408, 0, 0 16: 16, 0, 8889, 9936, 667136, 0, 0 32: 32, 0, 9176, 28824, 5527996, 0, 0 64: 64, 0, 1079474, 14516, 9720798, 0, 0 128: 128, 0, 313193, 12090, 2808003, 0, 0 256: 256, 0, 437062, 11588,56903630, 0, 0 512: 512, 0, 349086, 3970, 2254339, 0, 0 1024: 1024, 0, 2200, 988, 120013, 0, 0 2048: 2048, 0, 285, 2161, 2767034, 0, 0 4096: 4096, 0, 2123, 188, 11336, 0, 0 8192: 8192, 0, 203, 147, 16498, 0, 0 16384: 16384, 0, 31, 69, 6467, 0, 0 32768: 32768, 0, 47, 41, 3360, 0, 0 65536: 65536, 0, 45, 33, 4034, 0, 0 SLEEPQUEUE: 80, 0, 1007, 4883, 1007, 0, 0 64 pcpu: 8, 0, 3013, 2875, 3021, 0, 0 Files: 80, 0, 82, 5668, 18291, 0, 0 filedesc0: 1104, 0, 58, 527, 1600, 0, 0 rl_entry: 40, 0, 153, 11747, 153, 0, 0 TURNSTILE: 136, 0, 1007, 2233, 1007, 0, 0 umtx pi: 96, 0, 0, 0, 0, 0, 0 umtx_shm: 88, 0, 0, 0, 0, 0, 0 MAC labels: 40, 0, 0, 0, 0, 0, 0 PROC: 1424, 0, 57, 367, 1599, 0, 0 THREAD: 1552, 0, 927, 79, 1130, 0, 0 cpuset: 96, 0, 783, 5244, 1097, 0, 0 audit_record: 1248, 0, 0, 0, 0, 0, 0 mbuf_packet: 256, 38679675, 8184, 9034, 12580, 0, 0 mbuf: 256, 38679675, 1, 11145, 13401, 0, 0 mbuf_cluster: 2048, 6043698, 17204, 62, 17204, 0, 0 mbuf_jumbo_page: 4096, 3021848, 0, 3, 7, 0, 0 mbuf_jumbo_9k: 9216, 2686086, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 2014564, 0, 0, 0, 0, 0 FPU_save_area: 2696, 0, 0, 0, 0, 0, 0 g_bio: 376, 0, 36, 9704,11026368, 0, 0 DMAR_MAP_ENTRY: 120, 0, 0, 0, 0, 0, 0 ttyinq: 160, 0, 135, 915, 435, 0, 0 ttyoutq: 256, 0, 72, 978, 232, 0, 0 nvme_request: 128, 0, 0, 0, 0, 0, 0 vtnet_tx_hdr: 24, 0, 0, 0, 0, 0, 0 cryptop: 88, 0, 0, 0, 0, 0, 0 cryptodesc: 72, 0, 0, 0, 0, 0, 0 taskq_zone: 48, 0, 1, 14690, 40583, 0, 0 VNODE: 472, 0, 742, 802, 835, 0, 0 VNODEPOLL: 120, 0, 1, 131, 1, 0, 0 BUF TRIE: 144, 0, 0, 105948, 0, 0, 0 S VFS Cache: 108, 0, 703, 5317, 2375, 0, 0 STS VFS Cache: 148, 0, 0, 0, 0, 0, 0 L VFS Cache: 328, 0, 0, 0, 0, 0, 0 LTS VFS Cache: 368, 0, 0, 0, 0, 0, 0 NAMEI: 1024, 0, 0, 600, 55619, 0, 0 rentr: 24, 0, 0, 0, 0, 0, 0 DIRHASH: 1024, 0, 0, 0, 0, 0, 0 NCLNODE: 576, 0, 0, 0, 0, 0, 0 AIO: 208, 0, 0, 0, 0, 0, 0 AIOP: 32, 0, 0, 0, 0, 0, 0 AIOCB: 752, 0, 0, 0, 0, 0, 0 AIOLIO: 280, 0, 0, 0, 0, 0, 0 Mountpoints: 816, 0, 19, 176, 19, 0, 0 range_seg_cache: 64, 0, 652, 11748, 13476, 0, 0 metaslab_alloc_trace_cache: 64, 0, 0, 12152, 38435, 0, 0 zio_cache: 1040, 0, 2194, 25166,11241661, 0, 0 zio_link_cache: 48, 0, 2178, 34508,13726325, 0, 0 zio_buf_512: 512, 0, 2124, 1356, 535701, 0, 0 zio_data_buf_512: 512, 0, 55, 1313, 258022, 0, 0 zio_buf_1024: 1024, 0, 56, 540, 5534, 0, 0 zio_data_buf_1024: 1024, 0, 42, 546, 101722, 0, 0 zio_buf_1536: 1536, 0, 9, 397, 5057, 0, 0 zio_data_buf_1536: 1536, 0, 15, 381, 62096, 0, 0 zio_buf_2048: 2048, 0, 45, 231, 4257, 0, 0 zio_data_buf_2048: 2048, 0, 12, 184, 43958, 0, 0 zio_buf_2560: 2560, 0, 12, 129, 547, 0, 0 zio_data_buf_2560: 2560, 0, 7, 119, 38734, 0, 0 zio_buf_3072: 3072, 0, 7, 131, 322, 0, 0 zio_data_buf_3072: 3072, 0, 3, 129, 39511, 0, 0 zio_buf_3584: 3584, 0, 2, 45, 257, 0, 0 zio_data_buf_3584: 3584, 0, 4, 55, 47700, 0, 0 zio_buf_4096: 4096, 0, 27, 3945, 3152314, 0, 0 zio_data_buf_4096: 4096, 0, 5, 167, 28855, 0, 0 zio_buf_5120: 5120, 0, 3, 44, 241, 0, 0 zio_data_buf_5120: 5120, 0, 3, 56, 32951, 0, 0 zio_buf_6144: 6144, 0, 5, 48, 177, 0, 0 zio_data_buf_6144: 6144, 0, 4, 53, 22396, 0, 0 zio_buf_7168: 7168, 0, 2, 41, 121, 0, 0 zio_data_buf_7168: 7168, 0, 6, 50, 18886, 0, 0 zio_buf_8192: 8192, 0, 3, 1959, 585154, 0, 0 zio_data_buf_8192: 8192, 0, 9, 52, 16274, 0, 0 zio_buf_10240: 10240, 0, 2, 40, 120, 0, 0 zio_data_buf_10240: 10240, 0, 7, 55, 24350, 0, 0 zio_buf_12288: 12288, 0, 1, 1733, 653471, 0, 0 zio_data_buf_12288: 12288, 0, 8, 52, 19934, 0, 0 zio_buf_14336: 14336, 0, 0, 29, 63, 0, 0 zio_data_buf_14336: 14336, 0, 7, 49, 15583, 0, 0 zio_buf_16384: 16384, 0, 526, 1791, 829422, 0, 0 zio_data_buf_16384: 16384, 0, 8, 54, 14839, 0, 0 zio_buf_20480: 20480, 0, 13, 3915, 663814, 0, 0 zio_data_buf_20480: 20480, 0, 7, 52, 28948, 0, 0 zio_buf_24576: 24576, 0, 4, 2777, 170929, 0, 0 zio_data_buf_24576: 24576, 0, 9, 56, 16217, 0, 0 zio_buf_28672: 28672, 0, 4, 1546, 65027, 0, 0 zio_data_buf_28672: 28672, 0, 3, 54, 11554, 0, 0 zio_buf_32768: 32768, 0, 1033, 4397, 857173, 0, 0 zio_data_buf_32768: 32768, 0, 7, 53, 16143, 0, 0 zio_buf_40960: 40960, 0, 0, 65, 81085, 0, 0 zio_data_buf_40960: 40960, 0, 10, 56, 12373, 0, 0 zio_buf_49152: 49152, 0, 2, 172, 94059, 0, 0 zio_data_buf_49152: 49152, 0, 5, 59, 8868, 0, 0 zio_buf_57344: 57344, 0, 3, 169, 117765, 0, 0 zio_data_buf_57344: 57344, 0, 3, 52, 6590, 0, 0 zio_buf_65536: 65536, 0, 1, 190, 103301, 0, 0 zio_data_buf_65536: 65536, 0, 4, 55, 5741, 0, 0 zio_buf_81920: 81920, 0, 0, 69, 195743, 0, 0 zio_data_buf_81920: 81920, 0, 3, 55, 13127, 0, 0 zio_buf_98304: 98304, 0, 0, 71, 70635, 0, 0 zio_data_buf_98304: 98304, 0, 3, 53, 6340, 0, 0 zio_buf_114688: 114688, 0, 0, 183, 52918, 0, 0 zio_data_buf_114688: 114688, 0, 5, 56, 6532, 0, 0 zio_buf_131072: 131072, 0, 249, 735, 585161, 0, 0 zio_data_buf_131072: 131072, 0, 20933, 1227, 1164901, 0, 0 zio_buf_163840: 163840, 0, 0, 20, 31, 0, 0 zio_data_buf_163840: 163840, 0, 0, 0, 0, 0, 0 zio_buf_196608: 196608, 0, 0, 0, 0, 0, 0 zio_data_buf_196608: 196608, 0, 0, 0, 0, 0, 0 zio_buf_229376: 229376, 0, 0, 0, 0, 0, 0 zio_data_buf_229376: 229376, 0, 0, 0, 0, 0, 0 zio_buf_262144: 262144, 0, 0, 0, 0, 0, 0 zio_data_buf_262144: 262144, 0, 0, 0, 0, 0, 0 zio_buf_327680: 327680, 0, 0, 0, 0, 0, 0 zio_data_buf_327680: 327680, 0, 0, 0, 0, 0, 0 zio_buf_393216: 393216, 0, 0, 0, 0, 0, 0 zio_data_buf_393216: 393216, 0, 0, 0, 0, 0, 0 zio_buf_458752: 458752, 0, 0, 0, 0, 0, 0 zio_data_buf_458752: 458752, 0, 0, 0, 0, 0, 0 zio_buf_524288: 524288, 0, 0, 0, 0, 0, 0 zio_data_buf_524288: 524288, 0, 0, 0, 0, 0, 0 zio_buf_655360: 655360, 0, 0, 0, 0, 0, 0 zio_data_buf_655360: 655360, 0, 0, 0, 0, 0, 0 zio_buf_786432: 786432, 0, 0, 0, 0, 0, 0 zio_data_buf_786432: 786432, 0, 0, 0, 0, 0, 0 zio_buf_917504: 917504, 0, 0, 0, 0, 0, 0 zio_data_buf_917504: 917504, 0, 0, 0, 0, 0, 0 zio_buf_1048576: 1048576, 0, 0, 0, 0, 0, 0 zio_data_buf_1048576: 1048576, 0, 0, 0, 0, 0, 0 zio_buf_1310720: 1310720, 0, 0, 0, 0, 0, 0 zio_data_buf_1310720: 1310720, 0, 0, 0, 0, 0, 0 zio_buf_1572864: 1572864, 0, 0, 0, 0, 0, 0 zio_data_buf_1572864: 1572864, 0, 0, 0, 0, 0, 0 zio_buf_1835008: 1835008, 0, 0, 0, 0, 0, 0 zio_data_buf_1835008: 1835008, 0, 0, 0, 0, 0, 0 zio_buf_2097152: 2097152, 0, 0, 0, 0, 0, 0 zio_data_buf_2097152: 2097152, 0, 0, 0, 0, 0, 0 zio_buf_2621440: 2621440, 0, 0, 0, 0, 0, 0 zio_data_buf_2621440: 2621440, 0, 0, 0, 0, 0, 0 zio_buf_3145728: 3145728, 0, 0, 0, 0, 0, 0 zio_data_buf_3145728: 3145728, 0, 0, 0, 0, 0, 0 zio_buf_3670016: 3670016, 0, 0, 0, 0, 0, 0 zio_data_buf_3670016: 3670016, 0, 0, 0, 0, 0, 0 zio_buf_4194304: 4194304, 0, 0, 0, 0, 0, 0 zio_data_buf_4194304: 4194304, 0, 0, 0, 0, 0, 0 zio_buf_5242880: 5242880, 0, 0, 0, 0, 0, 0 zio_data_buf_5242880: 5242880, 0, 0, 0, 0, 0, 0 zio_buf_6291456: 6291456, 0, 0, 0, 0, 0, 0 zio_data_buf_6291456: 6291456, 0, 0, 0, 0, 0, 0 zio_buf_7340032: 7340032, 0, 0, 0, 0, 0, 0 zio_data_buf_7340032: 7340032, 0, 0, 0, 0, 0, 0 zio_buf_8388608: 8388608, 0, 0, 0, 0, 0, 0 zio_data_buf_8388608: 8388608, 0, 0, 0, 0, 0, 0 zio_buf_10485760: 10485760, 0, 0, 0, 0, 0, 0 zio_data_buf_10485760: 10485760, 0, 0, 0, 0, 0, 0 zio_buf_12582912: 12582912, 0, 0, 0, 0, 0, 0 zio_data_buf_12582912: 12582912, 0, 0, 0, 0, 0, 0 zio_buf_14680064: 14680064, 0, 0, 0, 0, 0, 0 zio_data_buf_14680064: 14680064, 0, 0, 0, 0, 0, 0 zio_buf_16777216: 16777216, 0, 0, 0, 0, 0, 0 zio_data_buf_16777216: 16777216, 0, 0, 0, 0, 0, 0 lz4_ctx: 16384, 0, 0, 82, 34011, 0, 0 abd_chunk: 4096, 0,22283282, 2428,26549803, 0, 0 sa_cache: 144, 0, 687, 2364, 778, 0, 0 dnode_t: 728, 0, 3604, 1041, 11152, 0, 0 arc_buf_hdr_t_full: 224, 0, 2065753, 1549, 2273683, 0, 0 arc_buf_hdr_t_l2only: 88, 0, 0, 0, 0, 0, 0 arc_buf_t: 64, 0, 22140, 10534, 2425480, 0, 0 dmu_buf_impl_t: 232, 0, 24198, 3206, 130259, 0, 0 zil_lwb_cache: 320, 0, 3, 381, 38, 0, 0 zil_zcw_cache: 80, 0, 0, 2400, 156, 0, 0 zfs_znode_cache: 264, 0, 687, 858, 778, 0, 0 pipe: 760, 0, 3, 582, 467, 0, 0 procdesc: 136, 0, 0, 261, 4, 0, 0 ksiginfo: 112, 0, 173, 6967, 1978, 0, 0 itimer: 352, 0, 0, 0, 0, 0, 0 KNOTE: 128, 0, 2, 153, 4, 0, 0 socket: 864, 3100852, 26, 598, 9078, 0, 0 unpcb: 240, 3100864, 11, 2917, 8845, 0, 0 ipq: 56, 188931, 0, 0, 0, 0, 0 udp_inpcb: 464, 3100856, 8, 920, 197, 0, 0 udpcb: 32, 3100875, 8, 8117, 197, 0, 0 tcp_inpcb: 464, 3100856, 4, 172, 9, 0, 0 tcpcb: 1040, 3100854, 4, 50, 9, 0, 0 tcptw: 88, 27810, 0, 0, 0, 0, 0 syncache: 168, 15364, 0, 69, 1, 0, 0 hostcache: 128, 15376, 0, 0, 0, 0, 0 sackhole: 32, 0, 0, 0, 0, 0, 0 tcpreass: 40, 377800, 0, 0, 0, 0, 0 sctp_ep: 1248, 3100854, 0, 0, 0, 0, 0 sctp_asoc: 2408, 40000, 0, 0, 0, 0, 0 sctp_laddr: 48, 80012, 0, 830, 3, 0, 0 sctp_raddr: 736, 80000, 0, 0, 0, 0, 0 sctp_chunk: 152, 400010, 0, 0, 0, 0, 0 sctp_readq: 152, 400010, 0, 0, 0, 0, 0 sctp_stream_msg_out: 112, 400015, 0, 0, 0, 0, 0 sctp_asconf: 40, 400000, 0, 0, 0, 0, 0 sctp_asconf_ack: 48, 400060, 0, 0, 0, 0, 0 udplite_inpcb: 464, 3100856, 0, 0, 0, 0, 0 ripcb: 464, 3100856, 1, 119, 7, 0, 0 IPsec SA lft_c: 16, 0, 0, 0, 0, 0, 0 rtentry: 208, 0, 11, 616, 15, 0, 0 selfd: 64, 0, 72, 10096, 41719, 0, 0 swpctrie: 144, 12087414, 0, 0, 0, 0, 0 swblk: 136, 12087403, 0, 0, 0, 0, 0 ------------------------------------------------------------------------ vmstat -i interrupt total rate cpu0:timer 88671 632 cpu1:timer 77721 554 cpu39:timer 86753 618 cpu8:timer 82602 589 cpu16:timer 243037 1732 cpu5:timer 76733 547 cpu9:timer 81452 580 cpu40:timer 95309 679 cpu4:timer 78734 561 cpu20:timer 89738 639 cpu42:timer 92478 659 cpu38:timer 89811 640 cpu11:timer 78309 558 cpu17:timer 89052 635 cpu15:timer 82714 589 cpu25:timer 80850 576 cpu3:timer 73616 525 cpu33:timer 86913 619 cpu43:timer 90640 646 cpu41:timer 91162 650 cpu21:timer 86331 615 cpu7:timer 79949 570 cpu46:timer 90772 647 cpu36:timer 91137 649 cpu34:timer 87641 624 cpu10:timer 82084 585 cpu14:timer 83376 594 cpu22:timer 89974 641 cpu27:timer 83512 595 cpu23:timer 90143 642 cpu37:timer 87446 623 cpu35:timer 84863 605 cpu30:timer 87731 625 cpu32:timer 91948 655 cpu24:timer 82903 591 cpu6:timer 81815 583 cpu28:timer 88449 630 cpu31:timer 83339 594 cpu44:timer 96889 690 cpu2:timer 79495 566 cpu26:timer 82766 590 cpu29:timer 81603 581 cpu47:timer 89971 641 cpu18:timer 87927 627 cpu13:timer 86471 616 cpu19:timer 85707 611 cpu12:timer 85240 607 cpu45:timer 94199 671 irq264: ahci0 433 3 irq265: xhci0 5164 37 irq267: ixl0:aq 2 0 irq268: ixl0:q0 2023 14 irq269: ixl0:q1 1338 10 irq270: ixl0:q2 477 3 irq271: ixl0:q3 61 0 irq272: ixl0:q4 130 1 irq273: ixl0:q5 2429 17 irq274: ixl0:q6 69 0 irq275: ixl0:q7 79 1 irq276: ixl1:aq 2 0 irq285: mpr0 2323266 16554 Total 6615449 47137 ------------------------------------------------------------------------ pstat -T 82/3100849 files 0M/0M swap space ------------------------------------------------------------------------ pstat -s Device 512-blocks Used Avail Capacity ------------------------------------------------------------------------ iostat tty ada0 ada1 da0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 1 60 24.63 0 0.00 23.87 0 0.00 37.67 249 9.16 0 0 1 0 99 ------------------------------------------------------------------------ ipcs -a Message Queues: T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME Shared Memory: T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME ------------------------------------------------------------------------ ipcs -T msginfo: msgmax: 16384 (max characters in a message) msgmni: 40 (# of message queues) msgmnb: 2048 (max characters in a message queue) msgtql: 40 (max # of messages in system) msgssz: 8 (size of a message segment) msgseg: 2048 (# of message segments in system) shminfo: shmmax: 536870912 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 192 (max number of shared memory identifiers) shmseg: 128 (max shared memory segments per process) shmall: 131072 (max amount of shared memory in pages) seminfo: semmni: 50 (# of semaphore identifiers) semmns: 340 (# of semaphores in system) semmnu: 150 (# of undo structures in system) semmsl: 340 (max # of semaphores per id) semopm: 100 (max # of operations per semop call) semume: 50 (max # of undo entries per process) semusz: 632 (size in bytes of undo structure) semvmx: 32767 (semaphore maximum value) semaem: 16384 (adjust on exit max value) ------------------------------------------------------------------------ nfsstat Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 0 0 0 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 0 0 0 0 0 0 0 0 BioRLHits Misses BioD Hits Misses DirE Hits Misses Accs Hits Misses 0 0 0 0 0 0 0 0 Server Info: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Server Ret-Failed 0 Server Faults 0 Server Cache Stats: Inprog Idem Non-idem Misses 0 0 0 0 Server Write Gathering: WriteOps WriteRPC Opsaved 0 0 0 ------------------------------------------------------------------------ netstat -s tcp: 1201 packets sent 1133 data packets (75258 bytes) 0 data packets (0 bytes) retransmitted 0 data packets unnecessarily retransmitted 0 resends initiated by MTU discovery 68 ack-only packets (58 delayed) 0 URG only packets 0 window probe packets 0 window update packets 0 control packets 1780 packets received 1043 acks (for 75259 bytes) 0 duplicate acks 0 acks for unsent data 1039 packets (40242 bytes) received in-sequence 0 completely duplicate packets (0 bytes) 0 old duplicate packets 0 packets with some dup. data (0 bytes duped) 0 out-of-order packets (0 bytes) 0 packets (0 bytes) of data after window 0 window probes 0 window update packets 0 packets received after close 0 discarded for bad checksums 0 discarded for bad header offset fields 0 discarded because packet too short 0 discarded due to memory problems 0 connection requests 1 connection accept 0 bad connection attempts 0 listen queue overflows 0 ignored RSTs in the windows 1 connection established (including accepts) 0 times used RTT from hostcache 0 times used RTT variance from hostcache 0 times used slow-start threshold from hostcache 5 connections closed (including 0 drops) 0 connections updated cached RTT on close 0 connections updated cached RTT variance on close 0 connections updated cached ssthresh on close 0 embryonic connections dropped 1043 segments updated rtt (of 1025 attempts) 0 retransmit timeouts 0 connections dropped by rexmit timeout 0 persist timeouts 0 connections dropped by persist timeout 0 Connections (fin_wait_2) dropped because of timeout 0 keepalive timeouts 0 keepalive probes sent 0 connections dropped by keepalive 624 correct ACK header predictions 697 correct data packet header predictions 1 syncache entry added 0 retransmitted 0 dupsyn 0 dropped 1 completed 0 bucket overflow 0 cache overflow 0 reset 0 stale 0 aborted 0 badack 0 unreach 0 zone failures 1 cookie sent 0 cookies received 0 hostcache entries added 0 bucket overflow 0 SACK recovery episodes 0 segment rexmits in SACK recovery episodes 0 byte rexmits in SACK recovery episodes 0 SACK options (SACK blocks) received 0 SACK options (SACK blocks) sent 0 SACK scoreboard overflow 0 packets with ECN CE bit set 0 packets with ECN ECT(0) bit set 0 packets with ECN ECT(1) bit set 0 successful ECN handshakes 0 times ECN reduced the congestion window 0 packets with matching signature received 0 packets with bad signature received 0 times failed to make signature due to no SA 0 times unexpected signature received 0 times no signature provided by segment TCP connection count by state: 0 connections in CLOSED state 3 connections in LISTEN state 0 connections in SYN_SENT state 0 connections in SYN_RCVD state 1 connection in ESTABLISHED state 0 connections in CLOSE_WAIT state 0 connections in FIN_WAIT_1 state 0 connections in CLOSING state 0 connections in LAST_ACK state 0 connections in FIN_WAIT_2 state 0 connections in TIME_WAIT state udp: 182 datagrams received 0 with incomplete header 0 with bad data length field 0 with bad checksum 0 with no checksum 5 dropped due to no socket 0 broadcast/multicast datagrams undelivered 0 dropped due to full socket buffers 0 not for hashed pcb 177 delivered 3809 datagrams output 0 times multicast source filter matched ip: 1986 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with data size < data length 0 with ip length > max ip packet size 0 with header length < data size 0 with data length < header length 0 with bad options 0 with incorrect version number 0 fragments received 0 fragments dropped (dup or out of space) 0 fragments dropped after timeout 0 packets reassembled ok 1984 packets for this host 0 packets for unknown/unsupported protocol 0 packets forwarded (0 packets fast forwarded) 2 packets not forwardable 0 packets received for unknown multicast group 0 redirects sent 5024 packets sent from this host 14 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented 0 tunneling packets that can't find gif 0 datagrams with bad address in header icmp: 5 calls to icmp_error 0 errors not generated in response to an icmp message Output histogram: echo reply: 3 destination unreachable: 5 0 messages with bad code fields 0 messages less than the minimum length 0 messages with bad checksum 0 messages with bad length 0 multicast echo requests ignored 0 multicast timestamp requests ignored Input histogram: echo reply: 5 destination unreachable: 6 echo: 3 time exceeded: 8 3 message responses generated 0 invalid return addresses 0 no return routes ipsec: 0 inbound packets violated process security policy 0 inbound packets failed due to insufficient memory 0 invalid inbound packets 0 outbound packets violated process security policy 0 outbound packets with no SA available 0 outbound packets failed due to insufficient memory 0 outbound packets with no route available 0 invalid outbound packets 0 outbound packets with bundled SAs 0 mbufs coalesced during clone 0 clusters coalesced during clone 0 clusters copied during clone 0 mbufs inserted during makespace ah: 0 packets shorter than header shows 0 packets dropped; protocol family not supported 0 packets dropped; no TDB 0 packets dropped; bad KCR 0 packets dropped; queue full 0 packets dropped; no transform 0 replay counter wraps 0 packets dropped; bad authentication detected 0 packets dropped; bad authentication length 0 possible replay packets detected 0 packets in 0 packets out 0 packets dropped; invalid TDB 0 bytes in 0 bytes out 0 packets dropped; larger than IP_MAXPACKET 0 packets blocked due to policy 0 crypto processing failures 0 tunnel sanity check failures esp: 0 packets shorter than header shows 0 packets dropped; protocol family not supported 0 packets dropped; no TDB 0 packets dropped; bad KCR 0 packets dropped; queue full 0 packets dropped; no transform 0 packets dropped; bad ilen 0 replay counter wraps 0 packets dropped; bad encryption detected 0 packets dropped; bad authentication detected 0 possible replay packets detected 0 packets in 0 packets out 0 packets dropped; invalid TDB 0 bytes in 0 bytes out 0 packets dropped; larger than IP_MAXPACKET 0 packets blocked due to policy 0 crypto processing failures 0 tunnel sanity check failures ipcomp: 0 packets shorter than header shows 0 packets dropped; protocol family not supported 0 packets dropped; no TDB 0 packets dropped; bad KCR 0 packets dropped; queue full 0 packets dropped; no transform 0 replay counter wraps 0 packets in 0 packets out 0 packets dropped; invalid TDB 0 bytes in 0 bytes out 0 packets dropped; larger than IP_MAXPACKET 0 packets blocked due to policy 0 crypto processing failures 0 packets sent uncompressed; size < compr. algo. threshold 0 packets sent uncompressed; compression was useless arp: 2 ARP requests sent 1 ARP reply sent 5 ARP requests received 1 ARP reply received 9 ARP packets received 0 total packets dropped due to no ARP entry 0 ARP entrys timed out 0 Duplicate IPs seen ip6: 0 total packets received 0 with size smaller than minimum 0 with data size < data length 0 with bad options 0 with incorrect version number 0 fragments received 0 fragments dropped (dup or out of space) 0 fragments dropped after timeout 0 fragments that exceeded limit 0 packets reassembled ok 0 packets for this host 0 packets forwarded 0 packets not forwardable 0 redirects sent 0 packets sent from this host 0 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented 0 packets that violated scope rules 0 multicast packets which we don't join Mbuf statistics: 0 one mbuf 0 one ext mbuf 0 two or more ext mbuf 0 packets whose headers are not contiguous 0 tunneling packets that can't find gif 0 packets discarded because of too many headers 1 failure of source address selection source addresses on a non-outgoing I/F 1 addresses scope=0xf Source addresses selection rule applied: 1 same address icmp6: 0 calls to icmp6_error 0 errors not generated in response to an icmp6 message 0 errors not generated because of rate limitation 0 messages with bad code fields 0 messages < minimum length 0 bad checksums 0 messages with bad length Histogram of error messages to be generated: 0 no route 0 administratively prohibited 0 beyond scope 0 address unreachable 0 port unreachable 0 packet too big 0 time exceed transit 0 time exceed reassembly 0 erroneous header field 0 unrecognized next header 0 unrecognized option 0 redirect 0 unknown 0 message responses generated 0 messages with too many ND options 0 messages with bad ND options 0 bad neighbor solicitation messages 0 bad neighbor advertisement messages 0 bad router solicitation messages 0 bad router advertisement messages 0 bad redirect messages 0 path MTU changes ipsec6: 0 inbound packets violated process security policy 0 inbound packets failed due to insufficient memory 0 invalid inbound packets 0 outbound packets violated process security policy 0 outbound packets with no SA available 0 outbound packets failed due to insufficient memory 0 outbound packets with no route available 0 invalid outbound packets 0 outbound packets with bundled SAs 0 mbufs coalesced during clone 0 clusters coalesced during clone 0 clusters copied during clone 0 mbufs inserted during makespace rip6: 0 messages received 0 checksum calculations on inbound 0 messages with bad checksum 0 messages dropped due to no socket 0 multicast messages dropped due to no socket 0 messages dropped due to full socket buffers 0 delivered 0 datagrams output pfkey: 0 requests sent from userland 0 bytes sent from userland 0 messages with invalid length field 0 messages with invalid version field 0 messages with invalid message type field 0 messages too short 0 messages with memory allocation failure 0 messages with duplicate extension 0 messages with invalid extension type 0 messages with invalid sa type 0 messages with invalid address extension 0 requests sent to userland 0 bytes sent to userland 0 messages toward single socket 0 messages toward all sockets 0 messages toward registered sockets 0 messages with memory allocation failure ------------------------------------------------------------------------ netstat -m 8185/20179/28364 mbufs in use (current/cache/total) 8170/9096/17266/6043698 mbuf clusters in use (current/cache/total/max) 8184/9034 mbuf+clusters out of packet secondary zone in use (current/cache) 0/3/3/3021848 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/2686086 9k jumbo clusters in use (current/cache/total/max) 0/0/0/2014564 16k jumbo clusters in use (current/cache/total/max) 18386K/23248K/41635K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0 sendfile syscalls 0 sendfile syscalls completed without I/O request 0 requests for I/O initiated by sendfile 0 pages read by sendfile as part of a request 0 pages were valid at time of a sendfile request 0 pages were requested for read ahead by applications 0 pages were read ahead by sendfile 0 times sendfile encountered an already busy page 0 requests for sfbufs denied 0 requests for sfbufs delayed ------------------------------------------------------------------------ netstat -anA Active Internet connections (including servers) Tcpcb Proto Recv-Q Send-Q Local Address Foreign Address (state) fffff803117ab820 tcp4 0 0 192.168.1.13.59 192.168.1.1.20800 ESTABLISHED fffff802d5a41820 tcp4 0 0 127.0.0.1.25 *.* LISTEN fffff802d5e6e410 tcp4 0 0 *.59 *.* LISTEN fffff802d5e6e820 tcp6 0 0 *.59 *.* LISTEN fffff8031113a570 udp4 0 0 127.0.0.1.123 *.* fffff8031113a740 udp6 0 0 fe80::1%lo0.123 *.* fffff8031113a910 udp6 0 0 ::1.123 *.* fffff8031113aae0 udp4 0 0 192.168.1.13.123 *.* fffff8031113acb0 udp4 0 0 *.123 *.* fffff8031113b000 udp6 0 0 *.123 *.* fffff801dae0bae0 udp4 0 0 *.514 *.* fffff801dae0bcb0 udp6 0 0 *.514 *.* Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr fffff8018c7e52d0 stream 0 0 fffff80180926760 0 0 0 /var/run/devd.pipe fffff8018c513780 dgram 0 0 0 fffff801dae115a0 0 fffff8018c4de960 fffff8018c4de960 dgram 0 0 0 fffff801dae115a0 0 fffff8018c7ed000 fffff8018c7ed000 dgram 0 0 0 fffff801dae115a0 0 fffff801e105c5a0 fffff801e105c5a0 dgram 0 0 0 fffff801dae115a0 0 fffff8018c7c3870 fffff801e17c4d20 dgram 0 0 0 fffff801dae11690 0 0 fffff8018c7c3870 dgram 0 0 0 fffff801dae115a0 0 fffff8018c513870 fffff8018c513870 dgram 0 0 0 fffff801dae115a0 0 0 fffff801dae115a0 dgram 0 0 fffff8018c4e91d8 0 fffff8018c513780 0 /var/run/logpriv fffff801dae11690 dgram 0 0 fffff8018c221588 0 fffff801e17c4d20 0 /var/run/log fffff8018c7e51e0 seqpac 0 0 fffff80180926588 0 0 0 /var/run/devd.seqpacket.pipe ------------------------------------------------------------------------ netstat -aL Current listen queue sizes (qlen/incqlen/maxqlen) Proto Listen Local Address tcp4 0/0/10 localhost.smtp tcp4 0/0/128 *.59 tcp6 0/0/128 *.59 unix 0/0/4 /var/run/devd.pipe unix 0/0/4 /var/run/devd.seqpacket.pipe ------------------------------------------------------------------------ fstat fstat: can't read file 1 at 0x20000000008800d fstat: can't read file 2 at 0x4000000000000a0 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20000000008800d fstat: can't read file 2 at 0x4000000000000a0 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2200000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x200000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x200000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2200000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x200000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x200000000 fstat: can't read file 23 at 0xe400000001 fstat: can't read file 29 at 0x1c00000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2200000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x200000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x200000000 fstat: can't read file 23 at 0xe000000000 fstat: can't read file 29 at 0x1c00000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2400000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2200000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x200000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x200000000 fstat: can't read file 23 at 0x9000000000 fstat: can't read file 29 at 0x6800000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x2200000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x200000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x200000000 fstat: can't read file 23 at 0xf400000001 fstat: can't read file 29 at 0x1c00000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0xa00000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x3e00000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x800000000 fstat: can't read file 23 at 0x16c00000001 fstat: can't read file 29 at 0x9800000000 fstat: can't read file 35 at 0x1600000001 fstat: can't read file 41 at 0x4400000001 fstat: can't read file 47 at 0x1800000001 fstat: can't read file 53 at 0x3000000000 fstat: can't read file 59 at 0x3400000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x800000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x600000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x600000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 11 at 0x1a00000000 fstat: can't read file 13 at 0x20007ffffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 17 at 0x600000000 fstat: can't read file 19 at 0x20007ffffffffff fstat: can't read file 20 at 0x4000000001fffff fstat: can't read file 22 at 0x780000ffff fstat: can't read file 23 at 0x4200000001 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x400000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x800000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x800000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x200000000000000 fstat: can't read file 2 at 0x400000000000000 fstat: can't read file 5 at 0x800000000 fstat: can't read file 7 at 0x200000000000002 fstat: can't read file 8 at 0x400000000000000 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 5 at 0x800000000 fstat: can't read file 7 at 0x20007ffffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read file 1 at 0x20007ffffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root sleep 1599 root - - error - root sleep 1599 wd - - error - root sleep 1599 text - - error - root sleep 1599 ctty /dev 261 crw--w---- ttyv1 rw root sleep 1599 0 /dev 261 crw--w---- ttyv1 rw root sleep 1596 root - - error - root sleep 1596 wd - - error - root sleep 1596 text - - error - root sleep 1596 ctty /dev 260 crw--w---- ttyv0 rw root sleep 1596 0 /dev 260 crw--w---- ttyv0 rw root tail 1590 root - - error - root tail 1590 wd - - error - root tail 1590 text - - error - root tail 1590 ctty /dev 260 crw--w---- ttyv0 rw root tail 1590 0 /dev 260 crw--w---- ttyv0 rw root bash 1570 root - - error - root bash 1570 wd - - error - root bash 1570 text - - error - root bash 1570 ctty /dev 261 crw--w---- ttyv1 rw root bash 1570 0 /dev 261 crw--w---- ttyv1 rw root bash 1570 6 /dev 261 crw--w---- ttyv1 rw root bash 1570 12 /dev 261 crw--w---- ttyv1 rw root bash 1506 root - - error - root bash 1506 wd - - error - root bash 1506 text - - error - root bash 1506 ctty /dev 261 crw--w---- ttyv1 rw root bash 1506 0 /dev 261 crw--w---- ttyv1 rw root bash 1506 6 /dev 261 crw--w---- ttyv1 rw root bash 1506 12 /dev 261 crw--w---- ttyv1 rw root systat 1499 root - - error - root systat 1499 wd - - error - root systat 1499 text - - error - root systat 1499 ctty /dev 264 crw--w---- ttyv4 rw root systat 1499 0 /dev 264 crw--w---- ttyv4 rw root bash 1477 root - - error - root bash 1477 wd - - error - root bash 1477 text - - error - root bash 1477 ctty /dev 264 crw--w---- ttyv4 rw root bash 1477 0 /dev 264 crw--w---- ttyv4 rw root bash 1477 6 /dev 264 crw--w---- ttyv4 rw root bash 1477 12 /dev 264 crw--w---- ttyv4 rw root zfs 1450 root - - error - root zfs 1450 wd - - error - root zfs 1450 text - - error - root zfs 1450 ctty /dev 260 crw--w---- ttyv0 rw root zfs 1450 0 /dev 26 crw-rw-rw- null r root zfs 1450 6 /dev 26 crw-rw-rw- null w root bash 1444 root - - error - root bash 1444 wd - - error - root bash 1444 text - - error - root bash 1444 ctty /dev 260 crw--w---- ttyv0 rw root bash 1444 0 /dev 260 crw--w---- ttyv0 rw root bash 1444 6 /dev 260 crw--w---- ttyv0 rw root bash 1444 12 /dev 260 crw--w---- ttyv0 rw root bash 1411 root - - error - root bash 1411 wd - - error - root bash 1411 text - - error - root bash 1411 ctty /dev 260 crw--w---- ttyv0 rw root bash 1411 0 /dev 260 crw--w---- ttyv0 rw root bash 1411 6 /dev 260 crw--w---- ttyv0 rw root bash 1411 12 /dev 260 crw--w---- ttyv0 rw root bash 1293 root - - error - root bash 1293 wd - - error - root bash 1293 text - - error - root bash 1293 ctty /dev 168 crw--w---- pts/0 rw root bash 1293 0 /dev 168 crw--w---- pts/0 rw root bash 1293 6 /dev 168 crw--w---- pts/0 rw root bash 1293 12 /dev 168 crw--w---- pts/0 rw root sshd 1291 root - - error - root sshd 1291 wd - - error - root sshd 1291 text - - error - root sshd 1291 0 /dev 26 crw-rw-rw- null rw root sshd 1291 6 /dev 26 crw-rw-rw- null rw root getty 1290 root - - error - root getty 1290 wd - - error - root getty 1290 text - - error - root getty 1290 ctty /dev 267 crw------- ttyv7 rw root getty 1290 0 /dev 267 crw------- ttyv7 rw root getty 1289 root - - error - root getty 1289 wd - - error - root getty 1289 text - - error - root getty 1289 ctty /dev 266 crw------- ttyv6 rw root getty 1289 0 /dev 266 crw------- ttyv6 rw root getty 1288 root - - error - root getty 1288 wd - - error - root getty 1288 text - - error - root getty 1288 ctty /dev 265 crw------- ttyv5 rw root getty 1288 0 /dev 265 crw------- ttyv5 rw root login 1287 root - - error - root login 1287 wd - - error - root login 1287 text - - error - root login 1287 ctty /dev 264 crw--w---- ttyv4 rw root login 1287 0 /dev 264 crw--w---- ttyv4 rw root getty 1286 root - - error - root getty 1286 wd - - error - root getty 1286 text - - error - root getty 1286 ctty /dev 263 crw------- ttyv3 rw root getty 1286 0 /dev 263 crw------- ttyv3 rw root getty 1285 root - - error - root getty 1285 wd - - error - root getty 1285 text - - error - root getty 1285 ctty /dev 262 crw------- ttyv2 rw root getty 1285 0 /dev 262 crw------- ttyv2 rw root login 1284 root - - error - root login 1284 wd - - error - root login 1284 text - - error - root login 1284 ctty /dev 261 crw--w---- ttyv1 rw root login 1284 0 /dev 261 crw--w---- ttyv1 rw root login 1283 root - - error - root login 1283 wd - - error - root login 1283 text - - error - root login 1283 ctty /dev 260 crw--w---- ttyv0 rw root login 1283 0 /dev 260 crw--w---- ttyv0 rw root cron 1204 root - - error - root cron 1204 wd - - error - root cron 1204 text - - error - root cron 1204 0 /dev 26 crw-rw-rw- null rw smmsp sendmail 1196 root - - error - smmsp sendmail 1196 wd - - error - smmsp sendmail 1196 text - - error - smmsp sendmail 1196 0 /dev 26 crw-rw-rw- null r root sendmail 1185 root - - error - root sendmail 1185 wd - - error - root sendmail 1185 text - - error - root sendmail 1185 0 /dev 26 crw-rw-rw- null r root sshd 1171 root - - error - root sshd 1171 wd - - error - root sshd 1171 text - - error - root sshd 1171 0 /dev 26 crw-rw-rw- null rw root ntpd 1089 root - - error - root ntpd 1089 wd - - error - root ntpd 1089 text - - error - root ntpd 1089 0 /dev 26 crw-rw-rw- null r root ntpd 1089 6 /dev 26 crw-rw-rw- null r root ntpd 1089 12 /dev 26 crw-rw-rw- null r root ntpd 1089 18* local dgram fffff8018c513870 <-> fffff801dae115a0 root syslogd 882 root - - error - root syslogd 882 wd - - error - root syslogd 882 text - - error - root syslogd 882 0 /dev 26 crw-rw-rw- null rw root syslogd 882 6 /dev 26 crw-rw-rw- null rw root devd 620 root - - error - root devd 620 wd - - error - root devd 620 text - - error - root devd 620 0 /dev 26 crw-rw-rw- null rw root devd 620 6 /dev 26 crw-rw-rw- null rw root moused 606 root - - error - root moused 606 wd - - error - root moused 606 text - - error - root moused 606 0 /dev 26 crw-rw-rw- null rw _dhcp dhclient 553 root - - error - _dhcp dhclient 553 wd - - error - _dhcp dhclient 553 jail - - error - _dhcp dhclient 553 text - - error - _dhcp dhclient 553 0 /dev 26 crw-rw-rw- null rw _dhcp dhclient 553 6 /dev 26 crw-rw-rw- null rw root dhclient 491 root - - error - root dhclient 491 wd - - error - root dhclient 491 text - - error - root dhclient 491 0 /dev 26 crw-rw-rw- null rw root dhclient 491 6 /dev 26 crw-rw-rw- null rw root adjkerntz 125 root - - error - root adjkerntz 125 wd - - error - root adjkerntz 125 text - - error - root adjkerntz 125 0 /dev 26 crw-rw-rw- null rw root zfskern 9 root - - error - root zfskern 9 wd - - error - root init 1 root - - error - root init 1 wd - - error - root init 1 text - - error - root kernel 0 root - - error - root kernel 0 wd - - error - ------------------------------------------------------------------------ dmesg Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 root@jimsdesk:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(efifb): resolution 1680x1050 CPU: Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz (2300.07-MHz K8-class CPU) Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0xd39ffffb Structured Extended Features2=0x8 Structured Extended Features3=0xc000000 XSAVE Features=0xf VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 103079215104 (98304 MB) avail memory = 98749128704 (94174 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs FreeBSD/SMP: 2 package(s) x 12 core(s) x 2 hardware threads ioapic6: Changing APIC ID to 16 ioapic7: Changing APIC ID to 17 ioapic8: Changing APIC ID to 18 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-31 on motherboard ioapic2 irqs 32-39 on motherboard ioapic3 irqs 40-47 on motherboard ioapic4 irqs 48-55 on motherboard ioapic5 irqs 72-79 on motherboard ioapic6 irqs 80-87 on motherboard ioapic7 irqs 88-95 on motherboard ioapic8 irqs 96-103 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #39 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #40 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #42 Launched! SMP: AP CPU #38 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #25 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #33 Launched! SMP: AP CPU #43 Launched! SMP: AP CPU #41 Launched! SMP: AP CPU #21 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #46 Launched! SMP: AP CPU #36 Launched! SMP: AP CPU #34 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #27 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #37 Launched! SMP: AP CPU #35 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #32 Launched! SMP: AP CPU #24 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #28 Launched! SMP: AP CPU #31 Launched! SMP: AP CPU #44 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #26 Launched! SMP: AP CPU #29 Launched! SMP: AP CPU #47 Launched! SMP: AP CPU #18 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #45 Launched! Timecounter "TSC-low" frequency 1150036534 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4590, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: numa-domain 0 on acpi0 cpu1: numa-domain 0 on acpi0 cpu2: numa-domain 0 on acpi0 cpu3: numa-domain 0 on acpi0 cpu4: numa-domain 0 on acpi0 cpu5: numa-domain 0 on acpi0 cpu6: numa-domain 0 on acpi0 cpu7: numa-domain 0 on acpi0 cpu8: numa-domain 0 on acpi0 cpu9: numa-domain 0 on acpi0 cpu10: numa-domain 0 on acpi0 cpu11: numa-domain 0 on acpi0 cpu12: numa-domain 0 on acpi0 cpu13: numa-domain 0 on acpi0 cpu14: numa-domain 0 on acpi0 cpu15: numa-domain 0 on acpi0 cpu16: numa-domain 0 on acpi0 cpu17: numa-domain 0 on acpi0 cpu18: numa-domain 0 on acpi0 cpu19: numa-domain 0 on acpi0 cpu20: numa-domain 0 on acpi0 cpu21: numa-domain 0 on acpi0 cpu22: numa-domain 0 on acpi0 cpu23: numa-domain 0 on acpi0 cpu24: numa-domain 1 on acpi0 cpu25: numa-domain 1 on acpi0 cpu26: numa-domain 1 on acpi0 cpu27: numa-domain 1 on acpi0 cpu28: numa-domain 1 on acpi0 cpu29: numa-domain 1 on acpi0 cpu30: numa-domain 1 on acpi0 cpu31: numa-domain 1 on acpi0 cpu32: numa-domain 1 on acpi0 cpu33: numa-domain 1 on acpi0 cpu34: numa-domain 1 on acpi0 cpu35: numa-domain 1 on acpi0 cpu36: numa-domain 1 on acpi0 cpu37: numa-domain 1 on acpi0 cpu38: numa-domain 1 on acpi0 cpu39: numa-domain 1 on acpi0 cpu40: numa-domain 1 on acpi0 cpu41: numa-domain 1 on acpi0 cpu42: numa-domain 1 on acpi0 cpu43: numa-domain 1 on acpi0 cpu44: numa-domain 1 on acpi0 cpu45: numa-domain 1 on acpi0 cpu46: numa-domain 1 on acpi0 cpu47: numa-domain 1 on acpi0 atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 24000000 Hz quality 950 Event timer "HPET" frequency 24000000 Hz quality 350 Event timer "HPET1" frequency 24000000 Hz quality 340 Event timer "HPET2" frequency 24000000 Hz quality 340 Event timer "HPET3" frequency 24000000 Hz quality 340 Event timer "HPET4" frequency 24000000 Hz quality 340 Event timer "HPET5" frequency 24000000 Hz quality 340 Event timer "HPET6" frequency 24000000 Hz quality 340 Event timer "HPET7" frequency 24000000 Hz quality 340 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_syscontainer0: on acpi0 acpi_syscontainer1: on acpi0 pcib0: port 0xcf8-0xcff numa-domain 0 on acpi0 pcib0: _OSC returned error 0x10 pci0: numa-domain 0 on pcib0 pci0: at device 8.1 (no driver attached) pci0: at device 17.0 (no driver attached) pci0: at device 17.1 (no driver attached) ahci0: port 0x3070-0x3077,0x3060-0x3063,0x3020-0x303f mem 0x9d206000-0x9d207fff,0x9d209000-0x9d2090ff,0x9d180000-0x9d1fffff irq 16 at device 17.5 numa-domain 0 on pci0 ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahciem0: on ahci0 xhci0: mem 0x383ffff00000-0x383ffff0ffff irq 16 at device 20.0 numa-domain 0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0: waiting for BIOS to give up control xhci_interrupt: host controller halted usbus0 numa-domain 0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) pci0: at device 22.4 (no driver attached) ahci1: port 0x3050-0x3057,0x3040-0x3043,0x3000-0x301f mem 0x9d204000-0x9d205fff,0x9d208000-0x9d2080ff,0x9d100000-0x9d17ffff irq 16 at device 23.0 numa-domain 0 on pci0 ahci1: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported ahcich6: at channel 0 on ahci1 ahcich7: at channel 1 on ahci1 ahcich8: at channel 2 on ahci1 ahcich9: at channel 3 on ahci1 ahcich10: at channel 4 on ahci1 ahcich11: at channel 5 on ahci1 ahcich12: at channel 6 on ahci1 ahcich13: at channel 7 on ahci1 ahciem1: on ahci1 pcib1: irq 16 at device 28.0 numa-domain 0 on pci0 pci1: numa-domain 0 on pcib1 pcib2: irq 17 at device 28.5 numa-domain 0 on pci0 pci2: numa-domain 0 on pcib2 pcib3: irq 17 at device 0.0 numa-domain 0 on pci2 pci3: numa-domain 0 on pcib3 vgapci0: port 0x2000-0x207f mem 0x9c000000-0x9cffffff,0x9d000000-0x9d01ffff irq 17 at device 0.0 numa-domain 0 on pci3 vgapci0: Boot video device isab0: at device 31.0 numa-domain 0 on pci0 isa0: numa-domain 0 on isab0 pci0: at device 31.2 (no driver attached) pci0: at device 31.5 (no driver attached) pcib4: numa-domain 0 on acpi0 pcib4: _OSC returned error 0x10 pci4: numa-domain 0 on pcib4 pcib5: irq 39 at device 0.0 numa-domain 0 on pci4 pci5: numa-domain 0 on pcib5 pcib6: mem 0xaae00000-0xaae1ffff irq 32 at device 0.0 numa-domain 0 on pci5 pci6: numa-domain 0 on pcib6 pcib7: irq 38 at device 3.0 numa-domain 0 on pci6 pci7: numa-domain 0 on pcib7 ixl0: mem 0xa9000000-0xa9ffffff,0xaa008000-0xaa00ffff irq 38 at device 0.0 numa-domain 0 on pci7 ixl0: using 1024 tx descriptors and 1024 rx descriptors ixl0: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared ixl0: Using MSIX interrupts with 9 vectors ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active ixl0: Ethernet address: ac:1f:6b:61:54:06 ixl0: SR-IOV ready queues is 0xfffffe0001d13000 ixl0: netmap queues/slots: TX 8/1024, RX 8/1024 ixl1: mem 0xa8000000-0xa8ffffff,0xaa000000-0xaa007fff irq 38 at device 0.1 numa-domain 0 on pci7 ixl1: using 1024 tx descriptors and 1024 rx descriptors ixl1: fw 3.1.52349 api 1.5 nvm 3.25 etid 800009e7 oem 1.262.0 ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 768, MDIO shared ixl1: Using MSIX interrupts with 9 vectors ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active ixl1: Ethernet address: ac:1f:6b:61:54:07 ixl1: SR-IOV ready queues is 0xfffffe0001e69000 ixl1: netmap queues/slots: TX 8/1024, RX 8/1024 pcib8: numa-domain 0 on acpi0 pcib8: _OSC returned error 0x10 pci8: numa-domain 0 on pcib8 pcib9: irq 47 at device 2.0 numa-domain 0 on pci8 pci9: numa-domain 0 on pcib9 mpr0: port 0x7000-0x70ff mem 0xb8640000-0xb864ffff,0xb8600000-0xb863ffff irq 42 at device 0.0 numa-domain 0 on pci9 mpr0: Firmware: 15.00.03.00, Driver: 18.03.00.00-fbsd mpr0: IOCCapabilities: 7a85c pcib10: numa-domain 0 on acpi0 pcib10: _OSC returned error 0x10 pci10: numa-domain 0 on pcib10 pci10: at device 14.0 (no driver attached) pci10: at device 15.0 (no driver attached) pci10: at device 18.0 (no driver attached) pci10: at device 18.1 (no driver attached) pcib11: numa-domain 1 on acpi0 ixl0: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None ixl0: link state changed to UP ixl1: Link is up, 1 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: Full ixl1: link state changed to UP pcib11: _OSC returned error 0x10 pci11: numa-domain 1 on pcib11 pci11: at device 8.1 (no driver attached) pcib12: numa-domain 1 on acpi0 pcib12: _OSC returned error 0x10 pci12: numa-domain 1 on pcib12 pcib13: numa-domain 1 on acpi0 pcib13: _OSC returned error 0x10 pci13: numa-domain 1 on pcib13 pcib14: numa-domain 1 on acpi0 pcib14: _OSC returned error 0x10 pci14: numa-domain 1 on pcib14 pci14: at device 14.0 (no driver attached) pci14: at device 15.0 (no driver attached) pci14: at device 18.0 (no driver attached) pci14: at device 18.1 (no driver attached) uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 orm0: at iomem 0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range est0: numa-domain 0 on cpu0 est1: numa-domain 0 on cpu1 est2: numa-domain 0 on cpu2 est3: numa-domain 0 on cpu3 est4: numa-domain 0 on cpu4 est5: numa-domain 0 on cpu5 est6: numa-domain 0 on cpu6 est7: numa-domain 0 on cpu7 est8: numa-domain 0 on cpu8 est9: numa-domain 0 on cpu9 est10: numa-domain 0 on cpu10 est11: numa-domain 0 on cpu11 est12: numa-domain 0 on cpu12 est13: numa-domain 0 on cpu13 est14: numa-domain 0 on cpu14 est15: numa-domain 0 on cpu15 est16: numa-domain 0 on cpu16 est17: numa-domain 0 on cpu17 est18: numa-domain 0 on cpu18 est19: numa-domain 0 on cpu19 est20: numa-domain 0 on cpu20 est21: numa-domain 0 on cpu21 est22: numa-domain 0 on cpu22 est23: numa-domain 0 on cpu23 est24: numa-domain 1 on cpu24 est25: numa-domain 1 on cpu25 est26: numa-domain 1 on cpu26 est27: numa-domain 1 on cpu27 est28: numa-domain 1 on cpu28 est29: numa-domain 1 on cpu29 est30: numa-domain 1 on cpu30 est31: numa-domain 1 on cpu31 est32: numa-domain 1 on cpu32 est33: numa-domain 1 on cpu33 est34: numa-domain 1 on cpu34 est35: numa-domain 1 on cpu35 est36: numa-domain 1 on cpu36 est37: numa-domain 1 on cpu37 est38: numa-domain 1 on cpu38 est39: numa-domain 1 on cpu39 est40: numa-domain 1 on cpu40 est41: numa-domain 1 on cpu41 est42: numa-domain 1 on cpu42 est43: numa-domain 1 on cpu43 est44: numa-domain 1 on cpu44 est45: numa-domain 1 on cpu45 est46: numa-domain 1 on cpu46 est47: numa-domain 1 on cpu47 random: unblocking device. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec mpr0: SAS Address from SAS device page0 = 5000c500955fb571 ugen0.1: <0x8086 XHCI root HUB> at usbus0 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000a> enclosureHandle<0x0002> slot 0 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c5009550e4f1 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000b> enclosureHandle<0x0002> slot 1 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c50095518c95 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000c> enclosureHandle<0x0002> slot 2 mpr0: At enclosure level 0 and connector name ( ) mpr0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 SAS Address from SAS device page0 = 5000c500955fb3c5 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000d> enclosureHandle<0x0002> slot 3 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c500955fb021 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000e> enclosureHandle<0x0002> slot 4 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 5000c5009550e891 mpr0: Found device <401,End Device> <12.0Gbps> handle<0x000f> enclosureHandle<0x0002> slot 5 mpr0: At enclosure level 0 and connector name ( ) mpr0: SAS Address from SAS device page0 = 500304801eb5dbfd mpr0: Found device <4411,End Device> <12.0Gbps> handle<0x0010> enclosureHandle<0x0002> slot 12 mpr0: At enclosure level 0 and connector name ( ) ses0 at ahciem0 bus 0 scbus6 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ses1 at ahciem1 bus 0 scbus15 target 0 lun 0 ses1: SEMB S-E-S 2.00 device ses1: SEMB SES Device ses2 at mpr0 bus 0 scbus16 target 20 lun 0 ses2: Fixed Enclosure Services SPC-3 SCSI device ses2: 1200.000MB/s transfers ses2: Command Queueing enabled ses2: SCSI-3 ENC Device ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 ada0: ACS-3 ATA SATA 3.x device ada0: Serial Number BTYS81150CWH240AGN ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada0: Command Queueing enabled ada0: 228936MB (468862128 512 byte sectors) ada1 at ahcich5 bus 0 scbus5 target 0 lun 0 ada1: ACS-3 ATA SATA 3.x device ada1: Serial Number BTYS814205JS240AGN ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada1: Command Queueing enabled ada1: 228936MB (468862128 512 byte sectors) ses2: pass4,da0: Element descriptor: 'Slot00' da4 at mpr0 bus 0 scbus16 target 12 lun 0 da0 at mpr0 bus 0 scbus16 target 8 lun 0 da1 at mpr0 bus 0 scbus16 target 9 lun 0 da2 at mpr0 bus 0 scbus16 target 10 lun 0 da5 at mpr0 bus 0 scbus16 target 13 lun 0 ses2: pass4,da0: SAS Device Slot Element: 1 Phys at Slot 0 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb571 da1: Fixed Direct Access SPC-4 SCSI device da1: Serial Number ZC15V7DV0000C8258M38 da1: 1200.000MB/s transfers uhub0: da1: Command Queueing enabled da1: 3815447MB (976754646 4096 byte sectors) da4: Fixed Direct Access SPC-4 SCSI device da4: Serial Number ZC1606RR0000R833G8YR da4: 1200.000MB/s transfers da4: Command Queueing enabled da4: 3815447MB (976754646 4096 byte sectors) da5: Fixed Direct Access SPC-4 SCSI device da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number ZC15T3GB0000C832EM0C da2: 1200.000MB/s transfersda0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number ZC1606NJ0000R833G9JK da0: 1200.000MB/s transfers da0: Command Queueing enabled da0: 3815447MB (976754646 4096 byte sectors) 26 ports with 26 removable, self powered da5: Serial Number ZC15KB320000R832RAR7 da5: 1200.000MB/s transfers da5: Command Queueing enabled da5: 3815447MB (976754646 4096 byte sectors) da2: Command Queueing enabled da2: 3815447MB (976754646 4096 byte sectors) ses2: pass5,da1: Element descriptor: 'Slot01' da3 at mpr0 bus 0 scbus16 target 11 lun 0 ses2: pass5,da1: SAS Device Slot Element: 1 Phys at Slot 1 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e4f1 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number ZC1606Q80000R833WKE8 da3: 1200.000MB/s transfers da3: Command Queueing enabled da3: 3815447MB (976754646 4096 byte sectors) ses2: pass6,da2: Element descriptor: 'Slot02' ses2: pass6,da2: SAS Device Slot Element: 1 Phys at Slot 2 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c50095518c95 ugen0.2: at usbus0 ses2: pass7,da3: Element descriptor: 'Slot03' ses2: pass7,da3: SAS Device Slot Element: 1 Phys at Slot 3 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb3c5 ses2: pass8,da4: Element descriptor: 'Slot04' ses2: pass8,da4: SAS Device Slot Element: 1 Phys at Slot 4 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c500955fb021 ses2: pass9,da5: Element descriptor: 'Slot05' ses2: pass9,da5: SAS Device Slot Element: 1 Phys at Slot 5 ses2: phy 0: SAS device type 1 id 0 ses2: phy 0: protocols: Initiator( None ) Target( SSP ) ses2: phy 0: parent 500304801eb5dbff addr 5000c5009550e891 ukbd0 numa-domain 0 on uhub0 ukbd0: on usbus0 Trying to mount root from zfs:mendeleev/default/root []... Root mount waiting for: usbus0 kbd2 at ukbd0 ugen0.3: at usbus0 uhub1 numa-domain 0 on uhub0 uhub1: on usbus0 uhub1: 4 ports with 3 removable, self powered Root mount waiting for: usbus0 ugen0.4: at usbus0 ukbd1 numa-domain 0 on uhub1 ukbd1: on usbus0 kbd3 at ukbd1 /etc/rc: DEBUG: run_rc_command: doit: sysctl_start /etc/rc: DEBUG: checkyesno: hostid_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: hostid_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Setting hostuuid: f6be925a-5a1e-11e8-bbbe-fe161f21af02. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Setting hostid: 0x2fca5b4d. /etc/rc: DEBUG: checkyesno: zfs_enable is set to YES. /etc/rc: DEBUG: load_kld: zfs kernel module already loaded. /etc/rc: DEBUG: run_rc_command: doit: zvol_start /etc/rc: DEBUG: run_rc_command: doit: dumpon_start /etc/rc: DEBUG: checkyesno: ddb_enable is set to NO. /etc/rc: DEBUG: run_rc_command: start_precmd: [ -n "$(geli_make_list)" ] /etc/rc: DEBUG: run_rc_command: start_precmd: find_gbde_devices start /etc/rc: DEBUG: run_rc_command: doit: gbde_start /etc/rc: DEBUG: run_rc_command: doit: ccd_start /etc/rc: DEBUG: run_rc_command: doit: /sbin/swapon -aq /etc/rc: DEBUG: run_rc_command: doit: fsck_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting file system checks: /etc/rc: DEBUG: checkyesno: background_fsck is set to YES. /etc/rc: DEBUG: run_rc_command: doit: root_start /etc/rc: DEBUG: run_rc_command: start_precmd: [ -n "${_mdconfig_list}" ] /etc/rc: DEBUG: checkyesno: hostid_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: hostid_save /etc/rc: DEBUG: run_rc_command: doit: mountcritlocal_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Mounting local filesystems:/etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. . /etc/rc: DEBUG: checkyesno: zfs_enable is set to YES. /etc/rc: DEBUG: load_kld: zfs kernel module already loaded. /etc/rc: DEBUG: run_rc_command: doit: be_start /etc/rc: DEBUG: checkyesno: zfs_enable is set to YES. /etc/rc: DEBUG: load_kld: zfs kernel module already loaded. /etc/rc: DEBUG: run_rc_command: doit: zfs_start /etc/rc: DEBUG: checkyesno: cleanvar_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: cleanvar_prestart /etc/rc: DEBUG: run_rc_command: doit: cleanvar_start /etc/rc: DEBUG: run_rc_command: doit: ldconfig_start /etc/rc: DEBUG: checkyesno: ldconfig_insecure is set to NO. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/perl5/5.26/mach/CORE /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. 32-bit compatibility ldconfig path: /usr/lib32 /etc/rc: DEBUG: checkyesno: kldxref_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: kld_start /etc/rc: DEBUG: set_rcvar_obsolete: $swapfile(old) -> $(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $geli_swap_flags(old) -> $(new) is defined /etc/rc: DEBUG: run_rc_command: doit: : /etc/rc: DEBUG: run_rc_command: doit: adjkerntz -i /etc/rc: DEBUG: checkyesno: atm_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: hostname_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Setting hostname: mendeleev3/etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. . /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_enable(old) -> $ipv6_activate_all_interfaces(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_prefer(old) -> $ip6addrctl_policy(new) is defined /etc/rc: DEBUG: checkyesno: ip6addrctl_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: ip6addrctl_start /etc/rc: DEBUG: checkyesno: ipv6_activate_all_interfaces is set to NO. /etc/rc: DEBUG: checkyesno: ip6addrctl_verbose is set to NO. /etc/rc: DEBUG: run_rc_command: doit: netoptions_start /etc/rc: DEBUG: checkyesno: tcp_extensions is set to YES. /etc/rc: DEBUG: checkyesno: tcp_keepalive is set to YES. /etc/rc: DEBUG: checkyesno: tcp_drop_synfin is set to NO. /etc/rc: DEBUG: checkyesno: ipv6_ipv4mapping is set to NO. /etc/rc: DEBUG: checkyesno: ipv6_privacy is set to NO. /etc/rc: DEBUG: run_rc_command: doit: random_start Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: /etc/rc: DEBUG: entropy read from /var/db/entropy/saved-entropy.1 /etc/rc: DEBUG: entropy read from /var/db/entropy/saved-entropy.2 /etc/rc: DEBUG: entropy read from /var/db/entropy/saved-entropy.3 /etc/rc: DEBUG: entropy read from /var/db/entropy/saved-entropy.4 /etc/rc: DEBUG: entropy read from /entropy /etc/rc: DEBUG: saving entropy to /entropy /etc/rc: DEBUG: saving entropy to /boot/entropy . /etc/rc: DEBUG: run_rc_command: doit: sppp_start /etc/rc: DEBUG: checkyesno: ipfilter_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipnat_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipfs_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: iovctl_start /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_enable(old) -> $ipv6_activate_all_interfaces(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_prefer(old) -> $(new) is defined /etc/rc: DEBUG: checkyesno: netif_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: netif_start /etc/rc: DEBUG: Created wlan(4)s: /etc/rc: DEBUG: Cloned: /etc/rc: DEBUG: checkyesno: ipv6_activate_all_interfaces is set to NO. lo0: link state changed to UP /etc/rc: DEBUG: checkyesno: ipv6_activate_all_interfaces is set to NO. /etc/rc: DEBUG: checkyesno: synchronous_dhclient is set to NO. /etc/rc: DEBUG: checkyesno: ipv6_activate_all_interfaces is set to NO. Starting Network: lo0 ixl0 ixl1. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. lo0: flags=8049 metric 0 mtu 16384 options=680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo ixl0: flags=8843 metric 0 mtu 1500 options=6407bb ether ac:1f:6b:61:54:06 hwaddr ac:1f:6b:61:54:06 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active ixl1: flags=8802 metric 0 mtu 1500 options=6407bb ether ac:1f:6b:61:54:07 hwaddr ac:1f:6b:61:54:07 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active /etc/rc: DEBUG: The following interfaces were not configured: /etc/rc.d/ipfilter: DEBUG: checkyesno: ipfilter_enable is set to NO. /etc/rc: DEBUG: checkyesno: devd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: devd_prestart /etc/rc: DEBUG: checkyesno: devd_enable is set to YES. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting devd. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /sbin/devd /etc/pccard_ether: DEBUG: run_rc_command: start_precmd: checkauto /etc/pccard_ether: DEBUG: run_rc_command: doit: pccard_ether_start /etc/pccard_ether: DEBUG: run_rc_command: start_precmd: checkauto /etc/pccard_ether: DEBUG: run_rc_command: doit: pccard_ether_start /etc/rc.d/netif: DEBUG: checkyesno: netif_enable is set to YES. /etc/rc.d/netif: DEBUG: run_rc_command: doit: netif_start ixl1 /etc/rc.d/netif: DEBUG: Created wlan(4)s: /etc/rc.d/netif: DEBUG: Cloned: /etc/rc.d/netif: DEBUG: checkyesno: ipv6_activate_all_interfaces is set to NO. Starting Network: ixl1. /etc/rc.d/netif: DEBUG: checkyesno: rc_startmsgs is set to YES. ixl1: flags=8802 metric 0 mtu 1500 options=6407bb ether ac:1f:6b:61:54:07 hwaddr ac:1f:6b:61:54:07 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active /etc/rc.d/netif: DEBUG: The following interfaces were not configured: /etc/rc.d/ipfilter: DEBUG: checkyesno: ipfilter_enable is set to NO. /etc/rc.d/bridge: DEBUG: run_rc_command: doit: bridge_start /etc/rc.d/routing: DEBUG: run_rc_command: doit: routing_start static any ixl1 /etc/rc.d/routing: DEBUG: checkyesno: ipv6_gateway_enable is set to NO. /etc/rc.d/dhclient: DEBUG: pid file (/var/run/dhclient.ixl0.pid): not readable. /etc/rc.d/dhclient: DEBUG: run_rc_command: start_precmd: dhclient_prestart /etc/rc.d/dhclient: DEBUG: checkyesno: background_dhclient is set to NO. /etc/rc.d/dhclient: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting dhclient. /etc/rc.d/dhclient: DEBUG: run_rc_command: doit: limits -C daemon /sbin/dhclient ixl0 DHCPDISCOVER on ixl0 to 255.255.255.255 port 67 interval 5 DHCPOFFER from 192.168.1.1 DHCPREQUEST on ixl0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.13 -- renewal in 300 seconds. /etc/rc.d/dhclient: DEBUG: pid file (/var/run/dhclient.ixl1.pid): not readable. /etc/rc.d/dhclient: DEBUG: run_rc_command: start_precmd: dhclient_prestart /etc/rc.d/dhclient: DEBUG: 'ixl1' is not a DHCP-enabled interface /etc/pccard_ether: DEBUG: run_rc_command: start_precmd: checkauto /etc/pccard_ether: DEBUG: run_rc_command: doit: pccard_ether_start /etc/rc.d/syscons: DEBUG: run_rc_command: doit: syscons_setkeyboard /dev/ukbd0 ums0 numa-domain 0 on uhub1 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=0 /etc/rc.d/moused: DEBUG: pid file (/var/run/moused.ums0.pid): not readable. /etc/rc.d/moused: DEBUG: checkyesno: moused_ums0_enable is set to YES. /etc/rc.d/moused: DEBUG: run_rc_command: doit: moused_start ums0 /etc/rc.d/moused: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting ums0 moused/etc/rc.d/moused: DEBUG: checkyesno: rc_startmsgs is set to YES. . /etc/rc: DEBUG: checkyesno: ipsec_enable is set to NO. /etc/rc: DEBUG: checkyesno: atm_enable is set to NO. /etc/rc: DEBUG: checkyesno: pfsync_enable is set to NO. /etc/rc: DEBUG: checkyesno: pflog_enable is set to NO. /etc/rc: DEBUG: checkyesno: pf_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: stf_up /etc/rc: DEBUG: checkyesno: ppp_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: routing_start doall add host 127.0.0.1: gateway lo0 fib 0: route already in table /etc/rc: DEBUG: checkyesno: icmp_bmcastecho is set to NO. /etc/rc: DEBUG: checkyesno: icmp_drop_redirect is set to NO. /etc/rc: DEBUG: checkyesno: icmp_log_redirect is set to NO. /etc/rc: DEBUG: checkyesno: gateway_enable is set to NO. /etc/rc: DEBUG: checkyesno: forward_sourceroute is set to NO. /etc/rc: DEBUG: checkyesno: accept_sourceroute is set to NO. /etc/rc: DEBUG: checkyesno: arpproxy_all is set to NO. add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 /etc/rc: DEBUG: checkyesno: ipv6_gateway_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipv6_gateway_enable is set to NO. /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_firewall_enable(old) -> $(new) is defined /etc/rc: DEBUG: checkyesno: firewall_enable is set to NO. /etc/rc: DEBUG: checkyesno: netwait_enable is set to NO. /etc/rc: DEBUG: checkyesno: local_unbound_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: nsswitch_start /etc/rc: DEBUG: set_rcvar_obsolete: $router_enable(old) -> $routed_enable(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $router(old) -> $routed_program(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $router_flags(old) -> $routed_flags(new) is defined /etc/rc: DEBUG: checkyesno: routed_enable is set to NO. /etc/rc: DEBUG: checkyesno: rtsold_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: static_ndp_start /etc/rc: DEBUG: run_rc_command: doit: static_arp_start /etc/rc: DEBUG: run_rc_command: doit: bridge_start /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_router_enable(old) -> $route6d_enable(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_router(old) -> $route6d_program(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $ipv6_router_flags(old) -> $route6d_flags(new) is defined /etc/rc: DEBUG: checkyesno: route6d_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: defaultroute_start /etc/rc: DEBUG: run_rc_command: start_precmd: mountcritremote_precmd /etc/rc: DEBUG: run_rc_command: doit: mountcritremote_start /etc/rc: DEBUG: checkyesno: dmesg_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: do_dmesg /etc/rc: DEBUG: run_rc_command: doit: devfs_start /etc/rc: DEBUG: checkyesno: devfs_load_rulesets is set to YES. /etc/rc: DEBUG: reading rulesets from file (/etc/defaults/devfs.rules) /etc/rc: DEBUG: found ruleset: devfsrules_hide_all=1 /etc/rc: DEBUG: adding rule (add hide) /etc/rc: DEBUG: found ruleset: devfsrules_unhide_basic=2 /etc/rc: DEBUG: adding rule (add path log unhide) /etc/rc: DEBUG: adding rule (add path null unhide) /etc/rc: DEBUG: adding rule (add path zero unhide) /etc/rc: DEBUG: adding rule (add path crypto unhide) /etc/rc: DEBUG: adding rule (add path random unhide) /etc/rc: DEBUG: adding rule (add path urandom unhide) /etc/rc: DEBUG: found ruleset: devfsrules_unhide_login=3 /etc/rc: DEBUG: adding rule (add path 'ptyp*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyq*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyr*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptys*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyP*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyQ*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyR*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyS*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyl*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptym*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyn*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyo*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyL*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyM*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyN*' unhide) /etc/rc: DEBUG: adding rule (add path 'ptyO*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyp*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyq*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyr*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttys*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyP*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyQ*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyR*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyS*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyl*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttym*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyn*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyo*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyL*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyM*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyN*' unhide) /etc/rc: DEBUG: adding rule (add path 'ttyO*' unhide) /etc/rc: DEBUG: adding rule (add path ptmx unhide) /etc/rc: DEBUG: adding rule (add path pts unhide) /etc/rc: DEBUG: adding rule (add path 'pts/*' unhide) /etc/rc: DEBUG: adding rule (add path fd unhide) /etc/rc: DEBUG: adding rule (add path 'fd/*' unhide) /etc/rc: DEBUG: adding rule (add path stdin unhide) /etc/rc: DEBUG: adding rule (add path stdout unhide) /etc/rc: DEBUG: adding rule (add path stderr unhide) /etc/rc: DEBUG: found ruleset: devfsrules_jail=4 /etc/rc: DEBUG: adding rule (add include $devfsrules_hide_all) /etc/rc: DEBUG: adding rule (add include $devfsrules_unhide_basic) /etc/rc: DEBUG: adding rule (add include $devfsrules_unhide_login) /etc/rc: DEBUG: adding rule (add path zfs unhide) /etc/rc: DEBUG: devfs_rulesets_from_file: no such file (/etc/devfs.rules) /etc/rc: DEBUG: devfs_init_rulesets: devfs rulesets initialized /etc/rc: DEBUG: checkyesno: ipmon_enable is set to NO. /etc/rc: DEBUG: set_rcvar_obsolete: $kerberos5_server_enable(old) -> $kdc_enable(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kerberos5_server(old) -> $kdc_program(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kerberos5_server_flags(old) -> $kdc_flags(new) is defined /etc/rc: DEBUG: checkyesno: kdc_enable is set to NO. /etc/rc: DEBUG: run_rc_command: start_precmd: [ -n "${_mdconfig2_list}" ] /etc/rc: DEBUG: checkyesno: newsyslog_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: newsyslog_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Creating and/or trimming log files/etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. . /etc/rc: DEBUG: checkyesno: syslogd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: syslogd_precmd /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting syslogd. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/syslogd -s /etc/rc: DEBUG: checkyesno: watchdogd_enable is set to NO. /etc/rc: DEBUG: checkyesno: savecore_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: savecore_prestart /etc/rc: DEBUG: run_rc_command: doit: savecore_start savecore: reboot after panic: kdb_sysctl_panic savecore: writing core to /var/crash/vmcore.2 /etc/rc: DEBUG: checkyesno: crashinfo_enable is set to YES. Writing crash summary to /var/crash/core.txt.2. /etc/rc: DEBUG: run_rc_command: doit: archdep_start /etc/rc: DEBUG: run_rc_command: doit: abi_start /etc/rc: DEBUG: checkyesno: sysvipc_enable is set to NO. /etc/rc: DEBUG: checkyesno: linux_enable is set to NO. /etc/rc: DEBUG: checkyesno: svr4_enable is set to NO. /etc/rc: DEBUG: checkyesno: sysvipc_enable is set to NO. /etc/rc: DEBUG: checkyesno: linux_enable is set to NO. /etc/rc: DEBUG: checkyesno: svr4_enable is set to NO. /etc/rc: DEBUG: checkyesno: vm_enable is set to NO. /etc/rc: DEBUG: checkyesno: accounting_enable is set to NO. /etc/rc: DEBUG: checkyesno: ntpdate_enable is set to NO. /etc/rc: DEBUG: checkyesno: rpcbind_enable is set to NO. /etc/rc: DEBUG: checkyesno: nfs_client_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: nisdomain_start /etc/rc: DEBUG: checkyesno: nis_server_enable is set to NO. /etc/rc: DEBUG: checkyesno: nis_client_enable is set to NO. /etc/rc: DEBUG: checkyesno: nis_ypset_enable is set to NO. /etc/rc: DEBUG: checkyesno: amd_enable is set to NO. /etc/rc: DEBUG: checkyesno: atm_enable is set to NO. /etc/rc: DEBUG: checkyesno: auditd_enable is set to NO. /etc/rc: DEBUG: checkyesno: auditdistd_enable is set to NO. /etc/rc: DEBUG: checkyesno: autofs_enable is set to NO. /etc/rc: DEBUG: checkyesno: autofs_enable is set to NO. /etc/rc: DEBUG: checkyesno: autofs_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: cleartmp_start /etc/rc: DEBUG: checkyesno: clear_tmp_enable is set to NO. /etc/rc: DEBUG: checkyesno: clear_tmp_X is set to YES. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Clearing /tmp (X related). /etc/rc: DEBUG: checkyesno: clear_tmp_X is set to YES. /etc/rc: DEBUG: checkyesno: ctld_enable is set to NO. /etc/rc: DEBUG: checkyesno: hastd_enable is set to NO. /etc/rc: DEBUG: checkyesno: iscsid_enable is set to NO. /etc/rc: DEBUG: checkyesno: iscsictl_enable is set to NO. /etc/rc: DEBUG: checkyesno: keyserv_enable is set to NO. /etc/rc: DEBUG: checkyesno: nfsuserd_enable is set to NO. /etc/rc: DEBUG: checkyesno: gssd_enable is set to NO. /etc/rc: DEBUG: checkyesno: quota_enable is set to NO. /etc/rc: DEBUG: checkyesno: mountd_enable is set to NO. /etc/rc: DEBUG: checkyesno: nfs_server_enable is set to NO. /etc/rc: DEBUG: checkyesno: rpc_statd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rpc_lockd_enable is set to NO. /etc/rc: DEBUG: checkyesno: pppoed_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: pwcheck_start /etc/rc: DEBUG: checkyesno: virecover_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: virecover_start Recovering vi editor sessions:. /etc/rc: DEBUG: checkyesno: nis_ypldap_enable is set to NO. /etc/rc: DEBUG: checkyesno: apm_enable is set to NO. /etc/rc: DEBUG: checkyesno: apmd_enable is set to NO. /etc/rc: DEBUG: checkyesno: bootparamd_enable is set to NO. /etc/rc: DEBUG: checkyesno: hcsecd_enable is set to NO. /etc/rc: DEBUG: checkyesno: bthidd_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: local_start /etc/rc: DEBUG: checkyesno: lpd_enable is set to NO. /etc/rc: DEBUG: checkyesno: update_motd is set to YES. /etc/rc: DEBUG: run_rc_command: doit: motd_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Updating motd:/etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. . /etc/rc: DEBUG: run_rc_command: doit: mountlate_start Mounting late filesystems:. /etc/rc: DEBUG: checkyesno: nscd_enable is set to NO. /etc/rc: DEBUG: checkyesno: ntpd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: ntpd_precmd /etc/rc: DEBUG: checkyesno: ntpd_sync_on_start is set to NO. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting ntpd. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drift /etc/rc: DEBUG: checkyesno: powerd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rarpd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rctl_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: rctl_start /etc/rc: DEBUG: checkyesno: sdpd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rfcomm_pppd_server_enable is set to NO. /etc/rc: DEBUG: checkyesno: rtadvd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rwhod_enable is set to NO. /etc/rc: DEBUG: checkyesno: timed_enable is set to NO. /etc/rc: DEBUG: checkyesno: ugidfw_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: utx boot /etc/rc: DEBUG: checkyesno: nis_yppasswdd_enable is set to NO. /etc/rc: DEBUG: checkyesno: smartd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rsyncd_enable is set to NO. /etc/rc: DEBUG: checkyesno: healthd_enable is set to NO. /etc/rc: DEBUG: checkyesno: git_daemon_enable is set to NO. /etc/rc: DEBUG: checkyesno: zfsd_enable is set to NO. /etc/rc: DEBUG: checkyesno: nis_ypxfrd_enable is set to NO. /etc/rc: DEBUG: checkyesno: rpc_ypupdated_enable is set to NO. /etc/rc: DEBUG: checkyesno: ubthidhci_enable is set to NO. /etc/rc: DEBUG: run_rc_command: start_precmd: syscons_precmd /etc/rc: DEBUG: run_rc_command: doit: syscons_start Configuring vt: blanktime. /etc/rc: DEBUG: run_rc_command: doit: /sbin/swapon -aLq /etc/rc: DEBUG: checkyesno: sshd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: sshd_precmd /etc/rc: DEBUG: checkyesno: sshd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: sshd_keygen /etc/rc: DEBUG: checkyesno: sshd_rsa1_enable is set to no. /etc/rc: DEBUG: checkyesno: sshd_rsa_enable is set to yes. /etc/rc: DEBUG: checkyesno: sshd_dsa_enable is set to no. /etc/rc: DEBUG: checkyesno: sshd_ecdsa_enable is set to yes. /etc/rc: DEBUG: checkyesno: sshd_ed25519_enable is set to yes. /etc/rc: DEBUG: checkyesno: sshd_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: sshd_configtest Performing sanity check on sshd configuration. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting sshd. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/sshd /etc/rc: DEBUG: checkyesno: sendmail_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: sendmail_precmd /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_rebuild_aliases is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_cert_create is set to YES. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting sendmail_submit. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost /etc/rc: DEBUG: checkyesno: sendmail_outbound_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_msp_queue_enable is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: sendmail_precmd /etc/rc: DEBUG: checkyesno: sendmail_msp_queue_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_rebuild_aliases is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_cert_create is set to YES. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting sendmail_msp_queue. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/sendmail -L sm-msp-queue -Ac -q30m /etc/rc: DEBUG: checkyesno: cron_dst is set to YES. /etc/rc: DEBUG: checkyesno: cron_enable is set to YES. /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting cron. /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/sbin/cron -s /etc/rc: DEBUG: checkyesno: jail_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: pkg_start /etc/rc.d/sysctl: DEBUG: run_rc_command: doit: sysctl_start last /etc/rc: DEBUG: checkyesno: kern_securelevel_enable is set to NO. /etc/rc: DEBUG: checkyesno: nfscbd_enable is set to NO. /etc/rc: DEBUG: run_rc_command: doit: msgs_start /etc/rc: DEBUG: checkyesno: moused_enable is set to NO. /etc/rc: DEBUG: checkyesno: mixer_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: mixer_start /etc/rc: DEBUG: set_rcvar_obsolete: $kpasswdd_server_enable(old) -> $kpasswdd_enable(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kpasswdd_server(old) -> $kpasswdd_program(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kerberos5_server_enable(old) -> $kdc_enable(new) is defined /etc/rc: DEBUG: checkyesno: kpasswdd_enable is set to NO. /etc/rc: DEBUG: checkyesno: kfd_enable is set to NO. /etc/rc: DEBUG: set_rcvar_obsolete: $kadmind5_server_enable(old) -> $kadmind_enable(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kadmind5_server(old) -> $kadmind_program(new) is defined /etc/rc: DEBUG: set_rcvar_obsolete: $kerberos5_server_enable(old) -> $kdc_enable(new) is defined /etc/rc: DEBUG: checkyesno: kadmind_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipropd_slave_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipropd_master_enable is set to NO. /etc/rc: DEBUG: checkyesno: ipfw_netflow_enable is set to NO. /etc/rc: DEBUG: checkyesno: inetd_enable is set to NO. /etc/rc: DEBUG: checkyesno: hostapd_enable is set to NO. /etc/rc: DEBUG: checkyesno: gptboot_enable is set to YES. /etc/rc: DEBUG: run_rc_command: doit: gptboot_report /etc/rc: DEBUG: run_rc_command: doit: geli2_start /etc/rc: DEBUG: checkyesno: ftpd_enable is set to NO. /etc/rc: DEBUG: checkyesno: ftpproxy_enable is set to NO. /etc/rc: DEBUG: checkyesno: bsnmpd_enable is set to NO. /etc/rc: DEBUG: checkyesno: blacklistd_enable is set to NO. /etc/rc: DEBUG: checkyesno: background_fsck is set to YES. /etc/rc: DEBUG: run_rc_command: start_precmd: bgfsck_start_precmd /etc/rc: DEBUG: run_rc_command: doit: bgfsck_start /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. Starting background file system checks in 60 seconds. Wed Jul 11 12:48:26 PDT 2018 Fatal trap 12: page fault while in kernel mode cpuid = 38; apic id = 32 fault virtual address = 0x5a fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80dff30d stack pointer = 0x28:0xfffffe17eaaa8440 frame pointer = 0x28:0xfffffe17eaaa8480 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (system_taskq_33) trap number = 12 panic: page fault cpuid = 38 KDB: stack backtrace: #0 0xffffffff80b3d907 at kdb_backtrace+0x67 #1 0xffffffff80af6e77 at vpanic+0x177 #2 0xffffffff80af6cf3 at panic+0x43 #3 0xffffffff80f77fef at trap_fatal+0x35f #4 0xffffffff80f78049 at trap_pfault+0x49 #5 0xffffffff80f77824 at trap+0x2d4 #6 0xffffffff80f5786c at calltrap+0x8 #7 0xffffffff80f7938b at uma_small_alloc+0x5b #8 0xffffffff80de5b72 at keg_alloc_slab+0xe2 #9 0xffffffff80de857e at keg_fetch_slab+0x14e #10 0xffffffff80de7db4 at zone_fetch_slab+0x64 #11 0xffffffff80de7e8f at zone_import+0x3f #12 0xffffffff80de4599 at uma_zalloc_arg+0x3d9 #13 0xffffffff8225b692 at abd_alloc+0x112 #14 0xffffffff8226064e at arc_hdr_alloc_pabd+0x8e #15 0xffffffff8225dbcf at arc_hdr_alloc+0x11f #16 0xffffffff8225f84f at arc_read+0x24f #17 0xffffffff8228342d at traverse_prefetcher+0x18d Uptime: 29m53s Dumping 7011 out of 96901 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% ------------------------------------------------------------------------ kernel config options CONFIG_AUTOGENERATED ident GENERIC machine amd64 cpu HAMMER makeoptions WITH_CTF=1 makeoptions DEBUG=-g options XENHVM options USB_DEBUG options ATH_ENABLE_11N options AH_AR5416_INTERRUPT_MITIGATION options AH_SUPPORT_AR5416 options IEEE80211_SUPPORT_MESH options IEEE80211_AMPDU_AGE options IEEE80211_DEBUG options SC_PIXEL_MODE options VESA options AHD_REG_PRETTY_PRINT options AHC_REG_PRETTY_PRINT options PCI_IOV options PCI_HP options ACPI_DMAR options EARLY_AP_STARTUP options DEVICE_NUMA options SMP options KDB_TRACE options KDB options RCTL options RACCT_DEFAULT_TO_DISABLED options RACCT options INCLUDE_CONFIG_FILE options DDB_CTF options KDTRACE_HOOKS options KDTRACE_FRAME options MAC options CAPABILITIES options CAPABILITY_MODE options AUDIT options HWPMC_HOOKS options KBD_INSTALL_CDEV options PRINTF_BUFR_SIZE=128 options _KPOSIX_PRIORITY_SCHEDULING options SYSVSEM options SYSVMSG options SYSVSHM options STACK options KTRACE options SCSI_DELAY=5000 options COMPAT_FREEBSD10 options COMPAT_FREEBSD9 options COMPAT_FREEBSD7 options COMPAT_FREEBSD6 options COMPAT_FREEBSD5 options COMPAT_FREEBSD4 options COMPAT_FREEBSD32 options GEOM_LABEL options GEOM_RAID options GEOM_PART_GPT options PSEUDOFS options PROCFS options CD9660 options MSDOSFS options NFS_ROOT options NFSLOCKD options NFSD options NFSCL options MD_ROOT options QUOTA options UFS_GJOURNAL options UFS_DIRHASH options UFS_ACL options SOFTUPDATES options FFS options SCTP options TCP_OFFLOAD options IPSEC_SUPPORT options IPSEC options INET6 options INET options PREEMPTION options SCHED_ULE options NEW_PCIB options GEOM_PART_MBR options GEOM_PART_EBR_COMPAT options GEOM_PART_EBR options GEOM_PART_BSD device isa device mem device io device uart_ns8250 device cpufreq device acpi device pci device fdc device ahci device ata device mvs device siis device ahc device ahd device esp device hptiop device isp device mpt device mps device mpr device sym device trm device adv device adw device aic device bt device isci device ocs_fc device scbus device ch device da device sa device cd device pass device ses device amr device arcmsr device ciss device dpt device hptmv device hptnr device hptrr device hpt27xx device iir device ips device mly device twa device smartpqi device tws device aac device aacp device aacraid device ida device mfi device mlx device mrsas device pmspcv device twe device nvme device nvd device atkbdc device atkbd device psm device kbdmux device vga device splash device sc device vt device vt_vga device vt_efifb device agp device cbb device pccard device cardbus device uart device ppc device ppbus device lpt device ppi device puc device bxe device de device em device igb device ix device ixv device ixl device ixlv device le device ti device txp device vx device miibus device ae device age device alc device ale device bce device bfe device bge device cas device dc device et device fxp device gem device hme device jme device lge device msk device nfe device nge device pcn device re device rl device sf device sge device sis device sk device ste device stge device tl device tx device vge device vr device wb device xl device wlan device wlan_wep device wlan_ccmp device wlan_tkip device wlan_amrr device an device ath device ath_pci device ath_hal device ath_rate_sample device ipw device iwi device iwn device malo device mwl device ral device wi device wpi device loop device random device padlock_rng device rdrand_rng device ether device vlan device tun device md device gif device firmware device bpf device uhci device ohci device ehci device xhci device usb device ukbd device umass device sound device snd_cmi device snd_csa device snd_emu10kx device snd_es137x device snd_hda device snd_ich device snd_via8233 device mmc device mmcsd device sdhci device virtio device virtio_pci device vtnet device virtio_blk device virtio_scsi device virtio_balloon device hyperv device xenpci device vmx device netmap device crypto ------------------------------------------------------------------------ ddb capture buffer ddb: ddb_capture: kvm_nlist --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="zfs-stats.out" ------------------------------------------------------------------------ ZFS Subsystem Report Thu Jul 12 11:31:07 2018 ------------------------------------------------------------------------ System Information: Kernel Version: 1102501 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 ZFS Storage pool Version: 5000 ZFS Filesystem Version: 5 FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 root 11:31AM up 19 mins, 1 user, load averages: 0.00, 0.00, 0.01 ------------------------------------------------------------------------ System Memory: 0.02% 20.51 MiB Active, 0.01% 13.54 MiB Inact 9.05% 8.34 GiB Wired, 0.00% 0 Cache 90.92% 83.84 GiB Free, -0.00% -204800 Bytes Gap Real Installed: 96.00 GiB Real Available: 98.57% 94.63 GiB Real Managed: 97.45% 92.22 GiB Logical Total: 96.00 GiB Logical Used: 12.65% 12.14 GiB Logical Free: 87.35% 83.86 GiB Kernel Memory: 611.25 MiB Data: 94.07% 575.01 MiB Text: 5.93% 36.24 MiB Kernel Memory Map: 92.22 GiB Size: 0.84% 795.25 MiB Free: 99.16% 91.44 GiB ------------------------------------------------------------------------ ARC Summary: (HEALTHY) Memory Throttle Count: 0 ARC Misc: Deleted: 0 Recycle Misses: 0 Mutex Misses: 0 Evict Skips: 0 ARC Size: 7.09% 6.47 GiB Target Size: (Adaptive) 100.00% 91.22 GiB Min Size (Hard Limit): 12.50% 11.40 GiB Max Size (High Water): 8:1 91.22 GiB ARC Size Breakdown: Recently Used Cache Size: 50.00% 45.61 GiB Frequently Used Cache Size: 50.00% 45.61 GiB ARC Hash Breakdown: Elements Max: 486.60k Elements Current: 100.00% 486.60k Collisions: 6.94k Chain Max: 2 Chains: 6.84k ------------------------------------------------------------------------ ARC Efficiency: 1.44m Cache Hit Ratio: 61.85% 891.12k Cache Miss Ratio: 38.15% 549.71k Actual Hit Ratio: 59.43% 856.26k Data Demand Efficiency: 96.28% 475.56k Data Prefetch Efficiency: 0.00% 449.51k CACHE HITS BY CACHE LIST: Anonymously Used: 3.91% 34.85k Most Recently Used: 59.27% 528.21k Most Frequently Used: 36.81% 328.06k Most Recently Used Ghost: 0.00% 0 Most Frequently Used Ghost: 0.00% 0 CACHE HITS BY DATA TYPE: Demand Data: 51.38% 457.85k Prefetch Data: 0.00% 2 Demand Metadata: 44.71% 398.41k Prefetch Metadata: 3.91% 34.86k CACHE MISSES BY DATA TYPE: Demand Data: 3.22% 17.71k Prefetch Data: 81.77% 449.51k Demand Metadata: 8.57% 47.14k Prefetch Metadata: 6.43% 35.35k ------------------------------------------------------------------------ L2ARC is disabled ------------------------------------------------------------------------ File-Level Prefetch: (HEALTHY) DMU Efficiency: 115.87k Hit Ratio: 0.41% 476 Miss Ratio: 99.59% 115.40k Colinear: 0 Hit Ratio: 100.00% 0 Miss Ratio: 100.00% 0 Stride: 0 Hit Ratio: 100.00% 0 Miss Ratio: 100.00% 0 DMU Misc: Reclaim: 0 Successes: 100.00% 0 Failures: 100.00% 0 Streams: 0 +Resets: 100.00% 0 -Resets: 100.00% 0 Bogus: 0 ------------------------------------------------------------------------ VDEV cache is disabled ------------------------------------------------------------------------ ZFS Tunables (sysctl): kern.maxusers 6392 vm.kmem_size 99019939840 vm.kmem_size_scale 1 vm.kmem_size_min 0 vm.kmem_size_max 1319413950874 vfs.zfs.trim.max_interval 1 vfs.zfs.trim.timeout 30 vfs.zfs.trim.txg_delay 32 vfs.zfs.trim.enabled 1 vfs.zfs.vol.immediate_write_sz 32768 vfs.zfs.vol.unmap_sync_enabled 0 vfs.zfs.vol.unmap_enabled 1 vfs.zfs.vol.recursive 0 vfs.zfs.vol.mode 1 vfs.zfs.version.zpl 5 vfs.zfs.version.spa 5000 vfs.zfs.version.acl 1 vfs.zfs.version.ioctl 7 vfs.zfs.debug 0 vfs.zfs.super_owner 0 vfs.zfs.immediate_write_sz 32768 vfs.zfs.sync_pass_rewrite 2 vfs.zfs.sync_pass_dont_compress 5 vfs.zfs.sync_pass_deferred_free 2 vfs.zfs.zio.dva_throttle_enabled 1 vfs.zfs.zio.exclude_metadata 0 vfs.zfs.zio.use_uma 1 vfs.zfs.zil_slog_bulk 786432 vfs.zfs.cache_flush_disable 0 vfs.zfs.zil_replay_disable 0 vfs.zfs.standard_sm_blksz 131072 vfs.zfs.dtl_sm_blksz 4096 vfs.zfs.min_auto_ashift 12 vfs.zfs.max_auto_ashift 13 vfs.zfs.vdev.trim_max_pending 10000 vfs.zfs.vdev.bio_delete_disable 0 vfs.zfs.vdev.bio_flush_disable 0 vfs.zfs.vdev.queue_depth_pct 1000 vfs.zfs.vdev.write_gap_limit 4096 vfs.zfs.vdev.read_gap_limit 32768 vfs.zfs.vdev.aggregation_limit 131072 vfs.zfs.vdev.trim_max_active 64 vfs.zfs.vdev.trim_min_active 1 vfs.zfs.vdev.scrub_max_active 2 vfs.zfs.vdev.scrub_min_active 1 vfs.zfs.vdev.async_write_max_active 10 vfs.zfs.vdev.async_write_min_active 1 vfs.zfs.vdev.async_read_max_active 3 vfs.zfs.vdev.async_read_min_active 1 vfs.zfs.vdev.sync_write_max_active 10 vfs.zfs.vdev.sync_write_min_active 10 vfs.zfs.vdev.sync_read_max_active 10 vfs.zfs.vdev.sync_read_min_active 10 vfs.zfs.vdev.max_active 1000 vfs.zfs.vdev.async_write_active_max_dirty_percent60 vfs.zfs.vdev.async_write_active_min_dirty_percent30 vfs.zfs.vdev.mirror.non_rotating_seek_inc1 vfs.zfs.vdev.mirror.non_rotating_inc 0 vfs.zfs.vdev.mirror.rotating_seek_offset1048576 vfs.zfs.vdev.mirror.rotating_seek_inc 5 vfs.zfs.vdev.mirror.rotating_inc 0 vfs.zfs.vdev.trim_on_init 1 vfs.zfs.vdev.cache.bshift 16 vfs.zfs.vdev.cache.size 0 vfs.zfs.vdev.cache.max 16384 vfs.zfs.vdev.default_ms_shift 29 vfs.zfs.vdev.min_ms_count 16 vfs.zfs.vdev.max_ms_count 200 vfs.zfs.txg.timeout 5 vfs.zfs.spa_min_slop 134217728 vfs.zfs.spa_slop_shift 5 vfs.zfs.spa_asize_inflation 24 vfs.zfs.deadman_enabled 0 vfs.zfs.deadman_checktime_ms 5000 vfs.zfs.deadman_synctime_ms 1000000 vfs.zfs.debug_flags 0 vfs.zfs.debugflags 0 vfs.zfs.recover 0 vfs.zfs.spa_load_verify_data 1 vfs.zfs.spa_load_verify_metadata 1 vfs.zfs.spa_load_verify_maxinflight 10000 vfs.zfs.max_missing_tvds_scan 0 vfs.zfs.max_missing_tvds_cachefile 2 vfs.zfs.max_missing_tvds 0 vfs.zfs.spa_load_print_vdev_tree 0 vfs.zfs.ccw_retry_interval 300 vfs.zfs.check_hostid 1 vfs.zfs.mg_fragmentation_threshold 85 vfs.zfs.mg_noalloc_threshold 0 vfs.zfs.condense_pct 200 vfs.zfs.metaslab_sm_blksz 4096 vfs.zfs.metaslab.bias_enabled 1 vfs.zfs.metaslab.lba_weighting_enabled 1 vfs.zfs.metaslab.fragmentation_factor_enabled1 vfs.zfs.metaslab.preload_enabled 1 vfs.zfs.metaslab.preload_limit 3 vfs.zfs.metaslab.unload_delay 8 vfs.zfs.metaslab.load_pct 50 vfs.zfs.metaslab.min_alloc_size 33554432 vfs.zfs.metaslab.df_free_pct 4 vfs.zfs.metaslab.df_alloc_threshold 131072 vfs.zfs.metaslab.debug_unload 0 vfs.zfs.metaslab.debug_load 0 vfs.zfs.metaslab.fragmentation_threshold70 vfs.zfs.metaslab.force_ganging 16777217 vfs.zfs.free_bpobj_enabled 1 vfs.zfs.free_max_blocks -1 vfs.zfs.no_scrub_prefetch 0 vfs.zfs.no_scrub_io 0 vfs.zfs.resilver_min_time_ms 3000 vfs.zfs.free_min_time_ms 1000 vfs.zfs.scan_min_time_ms 1000 vfs.zfs.scan_idle 50 vfs.zfs.scrub_delay 4 vfs.zfs.resilver_delay 2 vfs.zfs.top_maxinflight 32 vfs.zfs.zfetch.array_rd_sz 1048576 vfs.zfs.zfetch.max_idistance 67108864 vfs.zfs.zfetch.max_distance 8388608 vfs.zfs.zfetch.min_sec_reap 2 vfs.zfs.zfetch.max_streams 8 vfs.zfs.prefetch_disable 0 vfs.zfs.delay_scale 500000 vfs.zfs.delay_min_dirty_percent 60 vfs.zfs.dirty_data_sync 67108864 vfs.zfs.dirty_data_max_percent 10 vfs.zfs.dirty_data_max_max 4294967296 vfs.zfs.dirty_data_max 4294967296 vfs.zfs.max_recordsize 1048576 vfs.zfs.default_ibs 17 vfs.zfs.default_bs 9 vfs.zfs.send_holes_without_birth_time 1 vfs.zfs.mdcomp_disable 0 vfs.zfs.per_txg_dirty_frees_percent 30 vfs.zfs.nopwrite_enabled 1 vfs.zfs.dedup.prefetch 1 vfs.zfs.dbuf_cache_lowater_pct 10 vfs.zfs.dbuf_cache_hiwater_pct 10 vfs.zfs.dbuf_cache_shift 5 vfs.zfs.dbuf_cache_max_bytes 3060818688 vfs.zfs.l2c_only_size 0 vfs.zfs.mfu_ghost_data_esize 0 vfs.zfs.mfu_ghost_metadata_esize 0 vfs.zfs.mfu_ghost_size 0 vfs.zfs.mfu_data_esize 1380833792 vfs.zfs.mfu_metadata_esize 24497152 vfs.zfs.mfu_size 1440531456 vfs.zfs.mru_ghost_data_esize 0 vfs.zfs.mru_ghost_metadata_esize 0 vfs.zfs.mru_ghost_size 0 vfs.zfs.mru_data_esize 5244487680 vfs.zfs.mru_metadata_esize 109481472 vfs.zfs.mru_size 5392520192 vfs.zfs.anon_data_esize 0 vfs.zfs.anon_metadata_esize 0 vfs.zfs.anon_size 1081344 vfs.zfs.l2arc_norw 1 vfs.zfs.l2arc_feed_again 1 vfs.zfs.l2arc_noprefetch 1 vfs.zfs.l2arc_feed_min_ms 200 vfs.zfs.l2arc_feed_secs 1 vfs.zfs.l2arc_headroom 2 vfs.zfs.l2arc_write_boost 8388608 vfs.zfs.l2arc_write_max 8388608 vfs.zfs.arc_meta_limit 24486549504 vfs.zfs.arc_free_target 167651 vfs.zfs.compressed_arc_enabled 1 vfs.zfs.arc_grow_retry 60 vfs.zfs.arc_shrink_shift 7 vfs.zfs.arc_average_blocksize 8192 vfs.zfs.arc_no_grow_shift 5 vfs.zfs.arc_min 12243274752 vfs.zfs.arc_max 97946198016 vfs.zfs.abd_chunk_size 4096 ------------------------------------------------------------------------ --k1lZvvs/B4yU6o8G-- From owner-freebsd-questions@freebsd.org Thu Jul 12 18:49:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C3EF1033490 for ; Thu, 12 Jul 2018 18:49:57 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost2.sentex.ca", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F06F2790CC for ; Thu, 12 Jul 2018 18:49:55 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5:0:0:0:11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w6CIntlX000394 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 12 Jul 2018 14:49:55 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w6CInqVD092072; Thu, 12 Jul 2018 14:49:52 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Disk/ZFS activity crash on 11.2-STABLE To: Jim Long Cc: freebsd-questions@freebsd.org References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= xsBNBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAHNHG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT7CwHgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnnOwE0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAcLAXwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: Date: Thu, 12 Jul 2018 14:49:53 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180712183512.GA75020@g5.umpquanet.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.83 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 18:49:57 -0000 On 7/12/2018 2:35 PM, Jim Long wrote: > > Yes, ARC usage is high. top shows: > > last pid: 2215; load averages: 1.50, 1.69, 1.69 up 0+00:44:59 11:02:00 > 27 processes: 2 running, 25 sleeping > CPU: 0.0% user, 0.0% nice, 9.0% system, 0.1% interrupt, 90.9% idle > Mem: 1416K Active, 11M Inact, 2788K Laundry, 91G Wired, 1236M Free > ARC: 84G Total, 68M MFU, 83G MRU, 15M Anon, 877M Header, 4078K Other > 83G Compressed, 148G Uncompressed, 1.78:1 Ratio > Swap: 16G Total, 15M Used, 16G Free > > I'm re-running the test now. I had shut off hyperthreading to go down to > 24 cores, but it's back on now. This server will be a computational resource, > not just storage, so I'd like to find a way to stablize the configuration with > hyperthreading enabled, if possible. I would leave HT on. Based on the zfs stats CACHE HITS BY DATA TYPE: Demand Data: 51.38% 457.85k Prefetch Data: 0.00% 2 Demand Metadata: 44.71% 398.41k Prefetch Metadata: 3.91% 34.86k CACHE MISSES BY DATA TYPE: Demand Data: 3.22% 17.71k Prefetch Data: 81.77% 449.51k Demand Metadata: 8.57% 47.14k Prefetch Metadata: 6.43% 35.35k If I read this right, you are not hurting too much for meta data misses. I find things like zfs list -t snapshots REALLY slow down if there is not enough caching for meta data where there are a lot of files and directories. eg. on a box that has several million small files and many many directories, I increased the amount of RAM to vfs.zfs.arc_meta_limit and it helped a LOT. Even then I still see a lot of misses (it was worse before) CACHE HITS BY DATA TYPE: Demand Data: 10.82% 5.58b Prefetch Data: 0.66% 339.34m Demand Metadata: 50.83% 26.22b Prefetch Metadata: 37.69% 19.44b CACHE MISSES BY DATA TYPE: Demand Data: 6.79% 680.20m Prefetch Data: 8.43% 844.48m Demand Metadata: 79.52% 7.97b Prefetch Metadata: 5.26% 527.45m But I dont think thats your case. I would try and set a ceiling. On RELENG_11 you dont need to reboot Try sysctl -w vfs.zfs.arc_max=77946198016 which shaves off 20G from what ARC can gobble up. Not sure if thats your issue, but it is an issue for some users. If you are still hurting for caching, an SSD drive or NVME and make it a caching device for your pool. and what does zpool status show ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-questions@freebsd.org Thu Jul 12 19:46:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B62D103CCAF for ; Thu, 12 Jul 2018 19:46:51 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (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 D10C07C45B for ; Thu, 12 Jul 2018 19:46:50 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway [192.168.151.122]) by nightmare.dreamchaser.org (8.15.2/8.15.2) with ESMTP id w6CJKB4B036048 for ; Thu, 12 Jul 2018 13:20:11 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) To: FreeBSD Mailing List Reply-To: freebsd@dreamchaser.org From: Gary Aitken Subject: 3d modeling recommendations? Message-ID: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> Date: Thu, 12 Jul 2018 13:19:26 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (nightmare.dreamchaser.org [192.168.151.101]); Thu, 12 Jul 2018 13:20:12 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 19:46:51 -0000 Hi all, Can anyone recommend a 3-d graphics drawing program (port) that will generate .stl or .obj files? I need something to create code for driving a 3d printer. Thanks, Gary From owner-freebsd-questions@freebsd.org Thu Jul 12 19:49:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6282103D183 for ; Thu, 12 Jul 2018 19:49:18 +0000 (UTC) (envelope-from youvegotmoxie@gmail.com) Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 324867C5D2 for ; Thu, 12 Jul 2018 19:49:18 +0000 (UTC) (envelope-from youvegotmoxie@gmail.com) Received: by mail-oi0-x244.google.com with SMTP id y207-v6so58017548oie.13 for ; Thu, 12 Jul 2018 12:49:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=DzbTjhnCkjlNfRJ48hOll4yY2IBugxgr85IVD6ThgKg=; b=sqf6edKO0Z7khWp0/TWPDmr38kWXcrKwWoTCcIDy1Sxi1cQwK6jjabqKRUX6FZJ3UJ t+tQLl459Q0/b70QA89H+SOp5pI6g3cG/M0iEOhH1abEcThtnV95MNSsHl7uuUKj/87D 8+Ku9p/Egd2EA9NFPdaRxZS1Z/P8jnrUA4koFPfnHZ2cugSyCn1k90Kb+p/MxXCRASP5 VA5bgSSmkSM2pc7ybqkILEAlsIGJkT01uQkOd/uYKgxez6kIRpvfo7OPre9p8kunCVbp DfNUC+ao6WQhXDiDD6N3CGN79PezxXNV3yHxAF4ckwyJVSrcLL3f++36U+dumV3KOG/s LSqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=DzbTjhnCkjlNfRJ48hOll4yY2IBugxgr85IVD6ThgKg=; b=pMfPMV+wYzsc5fNjUIUARi81Glvfd23vLMbiI+nWuh2wQ2eq+/6VbcQMzHaTGOWymb V+IKTgRkpsCGUo01LJGMDIS0khAD6kn72vFf3E7+u4yG6jU8yFG4V7McApxM3RCUnbY5 og97Gi8dTSQlaoie1ZKr/Gxv6ETkU5pPzkGpc4BDwSNgnacPjqRHESghMXfxu9AmPTu1 +v0iVEb3kAJyVdxEeoGYg15gKuw7GAgIB/aMGogVYDTBJG3hCOve+Dipp0MlgTu2pODM 2OxDkIHw35JDz6J6wuxZfI5BM/+5EddayELkgKBNBqR3yatVEV8rm6VoZWu0s8DzKPiL wklQ== X-Gm-Message-State: AOUpUlEPH0V/lBoaAs3rKuVS6TEAEmRTRAGF+S+hoUXOYiIdld/jCjT0 2f3TUI+Um6NeWnKLsNArqz/h+H0p X-Google-Smtp-Source: AAOMgpfbwftp6ZC/R6DRepBTW8uzrOpSU5hB190loMXDCue3Xxmz1++2NZysygF8vk8QodxFHRlxUw== X-Received: by 2002:aca:5004:: with SMTP id e4-v6mr4066921oib.111.1531424957414; Thu, 12 Jul 2018 12:49:17 -0700 (PDT) Received: from ?IPv6:2620::28a2:4110:6d46:736d:e158:cc27? ([2620:0:28a2:4110:6d46:736d:e158:cc27]) by smtp.gmail.com with ESMTPSA id s142-v6sm9142844oie.48.2018.07.12.12.49.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jul 2018 12:49:16 -0700 (PDT) From: Michael Beasley Message-Id: <2B25B2C6-9D09-498A-B465-94467C828712@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Help with an Urgent Matter Date: Thu, 12 Jul 2018 14:49:15 -0500 In-Reply-To: <20180712165715.GA63961@neutralgood.org> Cc: freebsd-questions@freebsd.org, djtherenovator@gmail.com To: "Kevin P. Neal" References: <20180712012033.638fa1de.freebsd@edvax.de> <20180712043446.33fa58d1.freebsd@edvax.de> <20180712165715.GA63961@neutralgood.org> X-Mailer: Apple Mail (2.3445.6.18) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 19:49:18 -0000 > On Jul 12, 2018, at 11:57 AM, Kevin P. Neal = wrote: >=20 > On Thu, Jul 12, 2018 at 04:34:46AM +0200, Polytropon wrote: >> If you're asking for UFS and ZFS support (those are the two >> filesystem types primarily used on FreeBSD), I have no idea >> if they are supported, but I'd assume they are, given that >> both have been supported by older versions of Mac OS X. >=20 > There's no ZFS on macOS today. I don't remember the status of UFS and = can't > check since I'm not at home ATM. That=E2=80=99s not entirely accurate. While there is no 1st party = support for ZFS from Apple there is the OpenZFS on OSX project which = does provide ZFS support for macOS. https://openzfsonosx.org/ >=20 >>> You should know that my request revolves around a criminal case of = Elder >>> Abuse here in Canada >>> and I believe that the criminals involved are using Free BSD to = control and >>> destroy evidence in our computers....... >>=20 >> If that's true (or if it's just a suspicion), you should >> be in contact with the authorities. They have tools to >> forensically analyze a system to see what's going on. >=20 > Seconded, strongly. >=20 > The general rule is that the legal authorities should be the ones to > handle criminal matters. >=20 >> Per default, as far as I know, macOS does not exhibit means >> of remote control. Such a construct would involve a running >> SSH server, a username and password (!) known to the attacker, >> the firewall "properly" configured (to allow SSH connections), >> and the system to be online, of course. >=20 > Some kind of remote desktop could also be a way to do this. >=20 > If remote access is suspected then why is the computer connected to = the > Internet? >=20 >> As you have learned a lot about the relationship between >> FreeBSD and macOS, you should contact a macOS-centric discussion >> forum and maybe the SquirrelMail maintainers. To get this >> right: You assume that the BSD part of macOS is being used >> by a remote attacker to destroy evidence, and you conclude >> that from some SquirrelMail message... ??? >>=20 >> Hmmm... >=20 > Agreed. At the very least there's no evidence of FreeBSD here. Parts > of macOS that came from FreeBSD, sure, but not FreeBSD itself. >=20 > --=20 > Kevin P. Neal = http://www.pobox.com/~kpn/ >=20 > "It sounded pretty good, but it's hard to tell how it will work out > in practice." -- Dennis Ritchie, ~1977, "Summary of a DEC 32-bit = machine" > _______________________________________________ > 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 Thu Jul 12 20:23:32 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCCDF1041536 for ; Thu, 12 Jul 2018 20:23:32 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F6877E01F for ; Thu, 12 Jul 2018 20:23:32 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1531427012; x=1534019012; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=57DNDSnOFS+BdPXNTEP+d2HJnFMR4+ZAjXLjtkOvSd0=; b=HJjid66nQGA3gyIzpnPqvIWU5wLJhKnaiufBN4oqUcKHUq1ar2f2rpgXL7I326kI3+yEkRNkMuvHSqwqwg3QkYe6qHL5JPSw8sxrN4MzH0Pnf6+OAtPyXcgc7XnZHQTPZ/MehLPcDsHfSc9eU+0jYg/Bve7VeHFODIAlj72ZfCI= X-Thread-Info: NDI1MC4xMi4xOTMwMDAwMDAxZDA5OGMuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r2.us-east.aws.in.socketlabs.com (r2.us-east.aws.in.socketlabs.com [54.85.171.149]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 12 Jul 2018 16:23:16 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r2.us-east.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 12 Jul 2018 16:23:13 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fdi7L-000HjJ-6g; Thu, 12 Jul 2018 20:23:11 +0000 Date: Thu, 12 Jul 2018 21:23:11 +0100 From: Steve O'Hara-Smith To: freebsd@dreamchaser.org Cc: FreeBSD Mailing List Subject: Re: 3d modeling recommendations? Message-Id: <20180712212311.57a9d9dcdb6e242cfd070713@sohara.org> In-Reply-To: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> References: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 20:23:33 -0000 On Thu, 12 Jul 2018 13:19:26 -0600 Gary Aitken wrote: > Hi all, > > Can anyone recommend a 3-d graphics drawing program (port) that will > generate .stl or .obj files? I need something to create code for driving > a 3d printer. I'm quite fond of openscad which is in the ports - details at: http://www.openscad.org/ It's based around text files describing what is to be drawn, writing scad files is a lot like writing a program with extrusion and CSG as primitives. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Thu Jul 12 20:46:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3035D10441E5 for ; Thu, 12 Jul 2018 20:46:44 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 823AF7F845 for ; Thu, 12 Jul 2018 20:46:43 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 997787180F6; Thu, 12 Jul 2018 15:46:36 -0500 (CDT) Subject: Re: 3d modeling recommendations? To: Steve O'Hara-Smith , freebsd@dreamchaser.org Cc: FreeBSD Mailing List References: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> <20180712212311.57a9d9dcdb6e242cfd070713@sohara.org> From: Valeri Galtsev Message-ID: <8c48216d-7899-e545-0837-3cad1e410a64@kicp.uchicago.edu> Date: Thu, 12 Jul 2018 15:46:36 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180712212311.57a9d9dcdb6e242cfd070713@sohara.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 20:46:44 -0000 On 07/12/18 15:23, Steve O'Hara-Smith wrote: > On Thu, 12 Jul 2018 13:19:26 -0600 > Gary Aitken wrote: > >> Hi all, >> >> Can anyone recommend a 3-d graphics drawing program (port) that will >> generate .stl or .obj files? I need something to create code for driving >> a 3d printer. > > I'm quite fond of openscad which is in the ports - details at: > > http://www.openscad.org/ > > It's based around text files describing what is to be drawn, > writing scad files is a lot like writing a program with extrusion and CSG > as primitives. I used FreeCAD quite successfully to send models to 3D printing company (and we printed them in house as well). There is FreeCAD package (as well as port). I'm sure there is openscad package on FreeBSD as well though I never used it (will try it out next time I need to model something). Thanks. Valeri > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jul 12 21:12:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CE1C10470E0 for ; Thu, 12 Jul 2018 21:12:46 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA7280C7D for ; Thu, 12 Jul 2018 21:12:46 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1531429966; x=1534021966; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=2YVOaaEku/Q/cXzXXAzO2yZR1sbKU/EK35GxoXhz8QQ=; b=v8bIUhYrpJOKpyGbgSI75oQgYn8ein2JgpT3QV4kor+qBXp7LRdf6ZSWgkg+S8hgod2Q9vp6RwDAPE+ZHJ2sLxYcI6UuM8pNFhBakFi5TZ+886I0bOvh2ADuphkun/aITxg9BCSpBruHeOeDs0PgBBUf8PI6iymL5+hvsGr8rqA= X-Thread-Info: NDI1MC4xMi4xOTMwMDAwMDAxZWM3ZDkuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r2.h.in.socketlabs.com (r2.h.in.socketlabs.com [142.0.180.12]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 12 Jul 2018 17:12:37 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r2.h.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 12 Jul 2018 17:12:35 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fdit7-000I37-8i; Thu, 12 Jul 2018 21:12:33 +0000 Date: Thu, 12 Jul 2018 22:12:33 +0100 From: Steve O'Hara-Smith To: Valeri Galtsev Cc: freebsd@dreamchaser.org, FreeBSD Mailing List Subject: Re: 3d modeling recommendations? Message-Id: <20180712221233.cbd6012e5638d0207d35596b@sohara.org> In-Reply-To: <8c48216d-7899-e545-0837-3cad1e410a64@kicp.uchicago.edu> References: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> <20180712212311.57a9d9dcdb6e242cfd070713@sohara.org> <8c48216d-7899-e545-0837-3cad1e410a64@kicp.uchicago.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 21:12:46 -0000 On Thu, 12 Jul 2018 15:46:36 -0500 Valeri Galtsev wrote: > > > On 07/12/18 15:23, Steve O'Hara-Smith wrote: > > It's based around text files describing what is to be drawn, > > writing scad files is a lot like writing a program with extrusion and > > CSG as primitives. > > I used FreeCAD quite successfully to send models to 3D printing company > (and we printed them in house as well). There is FreeCAD package (as > well as port). I'm sure there is openscad package on FreeBSD as well Oh sure there's a package - I tried FreeCAD and a few others but I found it much easier to do precise models with text files than by drawing. I mostly do woodwork or building design with it so I have a library of components and with careful use of echo I can get a materials and cutting list on stdout while it renders an STL or image. -- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/ From owner-freebsd-questions@freebsd.org Thu Jul 12 21:17:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7778104794D for ; Thu, 12 Jul 2018 21:17:27 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0A280EFA for ; Thu, 12 Jul 2018 21:17:27 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 351F59F6B6 for ; Thu, 12 Jul 2018 21:17:26 +0000 (UTC) Received: from fledge.watson.org (doug@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.15.2/8.15.2) with ESMTP id w6CLHPv3030504 for ; Thu, 12 Jul 2018 17:17:25 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id w6CLHPpe030501 for ; Thu, 12 Jul 2018 17:17:25 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Thu, 12 Jul 2018 17:17:25 -0400 (EDT) From: doug Reply-To: doug@safeport.com To: freebsd-questions@FreeBSD.org Subject: ssh on 11.2 Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (fledge.watson.org [127.0.0.1]); Thu, 12 Jul 2018 17:17:25 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 21:17:27 -0000 After going to 11.2 from 11.1 authorized_keys2 MUST be renamed to authorized_keys. I spent a bit of time checking permissions and keys before comparing /etc/ssh/sshd_config. This might be implied in some of the Open-ssh errata but not so I got it. A note in UPDATING might be nice, or did I just miss this? From owner-freebsd-questions@freebsd.org Thu Jul 12 21:26:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53B83104883E for ; Thu, 12 Jul 2018 21:26:09 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id F39AF81639 for ; Thu, 12 Jul 2018 21:26:08 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 0C32A7180B5; Thu, 12 Jul 2018 16:26:08 -0500 (CDT) Subject: Re: 3d modeling recommendations? To: Steve O'Hara-Smith Cc: freebsd@dreamchaser.org, FreeBSD Mailing List References: <08a5e26d-18cb-9f42-9e63-6fd8f4dc953e@dreamchaser.org> <20180712212311.57a9d9dcdb6e242cfd070713@sohara.org> <8c48216d-7899-e545-0837-3cad1e410a64@kicp.uchicago.edu> <20180712221233.cbd6012e5638d0207d35596b@sohara.org> From: Valeri Galtsev Message-ID: <2443cc39-09f8-ba74-183d-77ac662e7cbb@kicp.uchicago.edu> Date: Thu, 12 Jul 2018 16:26:07 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180712221233.cbd6012e5638d0207d35596b@sohara.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 21:26:09 -0000 On 07/12/18 16:12, Steve O'Hara-Smith wrote: > On Thu, 12 Jul 2018 15:46:36 -0500 > Valeri Galtsev wrote: > >> >> >> On 07/12/18 15:23, Steve O'Hara-Smith wrote: > >>> It's based around text files describing what is to be drawn, >>> writing scad files is a lot like writing a program with extrusion and >>> CSG as primitives. >> >> I used FreeCAD quite successfully to send models to 3D printing company >> (and we printed them in house as well). There is FreeCAD package (as >> well as port). I'm sure there is openscad package on FreeBSD as well > > Oh sure there's a package - I tried FreeCAD and a few others but I > found it much easier to do precise models with text files than by drawing. > I mostly do woodwork or building design with it so I have a library of > components and with careful use of echo I can get a materials and cutting > list on stdout while it renders an STL or image. Oh, good, now we know the difference. Yes, FreeCAD is more GUI way drawing (I don't know if it can do script based drawing), and GUI is what I'm more used to with what I do (parts/fitting for ship model). Valeri > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jul 12 21:43:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 608F6104A65A for ; Thu, 12 Jul 2018 21:43:42 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (ns.umpquanet.com [209.216.177.146]) (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 DBC89823AA for ; Thu, 12 Jul 2018 21:43:41 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (localhost [127.0.0.1]) by g5.umpquanet.com (8.15.2/8.15.2) with ESMTPS id w6CLgoXH008787 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 Jul 2018 14:42:50 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by g5.umpquanet.com (8.15.2/8.15.2/Submit) id w6CLgmkQ008785; Thu, 12 Jul 2018 14:42:48 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: g5.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Thu, 12 Jul 2018 14:42:48 -0700 From: Jim Long To: Mike Tancsa Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE Message-ID: <20180712214248.GA98578@g5.umpquanet.com> References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 21:43:42 -0000 On Thu, Jul 12, 2018 at 02:49:53PM -0400, Mike Tancsa wrote: --snip-- > I would try and set a ceiling. On > RELENG_11 you dont need to reboot > > Try > sysctl -w vfs.zfs.arc_max=77946198016 > > which shaves off 20G from what ARC can gobble up. Not sure if thats your > issue, but it is an issue for some users. > > If you are still hurting for caching, an SSD drive or NVME and make it a > caching device for your pool. > > and what does > zpool status > show ? I set the limit to the value you suggested, and the next test ran less than three minutes before the machine rebooted, with no crash dump produced. I further reduced the limit to 50G and it's been running for about 50 minutes so far. Fingers crossed. I do have L2ARC I can add if need be. I'll keep you posted on how this run goes. Thank you, Jim # zpool list; echo; zpool status NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT mendeleev 21.6T 5.02T 16.6T - - 0% 23% 1.00x ONLINE - pool: mendeleev state: ONLINE scan: scrub repaired 0 in 3h39m with 0 errors on Wed Jun 6 18:24:08 2018 config: NAME STATE READ WRITE CKSUM mendeleev ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/zfs0 ONLINE 0 0 0 gpt/zfs1 ONLINE 0 0 0 gpt/zfs2 ONLINE 0 0 0 gpt/zfs3 ONLINE 0 0 0 gpt/zfs4 ONLINE 0 0 0 gpt/zfs5 ONLINE 0 0 0 errors: No known data errors Here's zfs-stats after about 50 min of activity. # zfs-stats -a ------------------------------------------------------------------------ ZFS Subsystem Report Thu Jul 12 14:38:04 2018 ------------------------------------------------------------------------ System Information: Kernel Version: 1102501 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 ZFS Storage pool Version: 5000 ZFS Filesystem Version: 5 FreeBSD 11.2-STABLE #0 r335674: Tue Jun 26 13:20:24 PDT 2018 root 2:38PM up 55 mins, 2 users, load averages: 3.44, 3.88, 3.83 ------------------------------------------------------------------------ System Memory: 0.02% 14.62 MiB Active, 0.02% 21.34 MiB Inact 62.00% 57.18 GiB Wired, 0.00% 0 Cache 37.96% 35.01 GiB Free, -0.00% -204800 Bytes Gap Real Installed: 96.00 GiB Real Available: 98.57% 94.63 GiB Real Managed: 97.45% 92.22 GiB Logical Total: 96.00 GiB Logical Used: 63.51% 60.97 GiB Logical Free: 36.49% 35.03 GiB Kernel Memory: 968.90 MiB Data: 96.26% 932.67 MiB Text: 3.74% 36.24 MiB Kernel Memory Map: 92.22 GiB Size: 1.70% 1.57 GiB Free: 98.30% 90.65 GiB ------------------------------------------------------------------------ ARC Summary: (HEALTHY) Memory Throttle Count: 0 ARC Misc: Deleted: 17.53m Recycle Misses: 0 Mutex Misses: 46.41k Evict Skips: 26.28k ARC Size: 100.02% 50.01 GiB Target Size: (Adaptive) 100.00% 50.00 GiB Min Size (Hard Limit): 22.80% 11.40 GiB Max Size (High Water): 4:1 50.00 GiB ARC Size Breakdown: Recently Used Cache Size: 99.19% 49.60 GiB Frequently Used Cache Size: 0.81% 416.12 MiB ARC Hash Breakdown: Elements Max: 3.96m Elements Current: 95.60% 3.79m Collisions: 3.22m Chain Max: 5 Chains: 367.37k ------------------------------------------------------------------------ ARC Efficiency: 63.22m Cache Hit Ratio: 43.75% 27.66m Cache Miss Ratio: 56.25% 35.56m Actual Hit Ratio: 39.39% 24.90m Data Demand Efficiency: 69.68% 26.96m Data Prefetch Efficiency: 0.00% 18.77m CACHE HITS BY CACHE LIST: Anonymously Used: 9.95% 2.75m Most Recently Used: 87.72% 24.26m Most Frequently Used: 2.32% 640.73k Most Recently Used Ghost: 0.00% 0 Most Frequently Used Ghost: 0.01% 2.43k CACHE HITS BY DATA TYPE: Demand Data: 67.92% 18.79m Prefetch Data: 0.00% 8 Demand Metadata: 22.12% 6.12m Prefetch Metadata: 9.96% 2.76m CACHE MISSES BY DATA TYPE: Demand Data: 22.99% 8.18m Prefetch Data: 52.77% 18.77m Demand Metadata: 17.07% 6.07m Prefetch Metadata: 7.17% 2.55m ------------------------------------------------------------------------ L2ARC is disabled ------------------------------------------------------------------------ File-Level Prefetch: (HEALTHY) DMU Efficiency: 137.36k Hit Ratio: 0.34% 470 Miss Ratio: 99.66% 136.89k Colinear: 0 Hit Ratio: 100.00% 0 Miss Ratio: 100.00% 0 Stride: 0 Hit Ratio: 100.00% 0 Miss Ratio: 100.00% 0 DMU Misc: Reclaim: 0 Successes: 100.00% 0 Failures: 100.00% 0 Streams: 0 +Resets: 100.00% 0 -Resets: 100.00% 0 Bogus: 0 ------------------------------------------------------------------------ VDEV cache is disabled ------------------------------------------------------------------------ ZFS Tunables (sysctl): kern.maxusers 6392 vm.kmem_size 99019939840 vm.kmem_size_scale 1 vm.kmem_size_min 0 vm.kmem_size_max 1319413950874 vfs.zfs.trim.max_interval 1 vfs.zfs.trim.timeout 30 vfs.zfs.trim.txg_delay 32 vfs.zfs.trim.enabled 1 vfs.zfs.vol.immediate_write_sz 32768 vfs.zfs.vol.unmap_sync_enabled 0 vfs.zfs.vol.unmap_enabled 1 vfs.zfs.vol.recursive 0 vfs.zfs.vol.mode 1 vfs.zfs.version.zpl 5 vfs.zfs.version.spa 5000 vfs.zfs.version.acl 1 vfs.zfs.version.ioctl 7 vfs.zfs.debug 0 vfs.zfs.super_owner 0 vfs.zfs.immediate_write_sz 32768 vfs.zfs.sync_pass_rewrite 2 vfs.zfs.sync_pass_dont_compress 5 vfs.zfs.sync_pass_deferred_free 2 vfs.zfs.zio.dva_throttle_enabled 1 vfs.zfs.zio.exclude_metadata 0 vfs.zfs.zio.use_uma 1 vfs.zfs.zil_slog_bulk 786432 vfs.zfs.cache_flush_disable 0 vfs.zfs.zil_replay_disable 0 vfs.zfs.standard_sm_blksz 131072 vfs.zfs.dtl_sm_blksz 4096 vfs.zfs.min_auto_ashift 12 vfs.zfs.max_auto_ashift 13 vfs.zfs.vdev.trim_max_pending 10000 vfs.zfs.vdev.bio_delete_disable 0 vfs.zfs.vdev.bio_flush_disable 0 vfs.zfs.vdev.queue_depth_pct 1000 vfs.zfs.vdev.write_gap_limit 4096 vfs.zfs.vdev.read_gap_limit 32768 vfs.zfs.vdev.aggregation_limit 131072 vfs.zfs.vdev.trim_max_active 64 vfs.zfs.vdev.trim_min_active 1 vfs.zfs.vdev.scrub_max_active 2 vfs.zfs.vdev.scrub_min_active 1 vfs.zfs.vdev.async_write_max_active 10 vfs.zfs.vdev.async_write_min_active 1 vfs.zfs.vdev.async_read_max_active 3 vfs.zfs.vdev.async_read_min_active 1 vfs.zfs.vdev.sync_write_max_active 10 vfs.zfs.vdev.sync_write_min_active 10 vfs.zfs.vdev.sync_read_max_active 10 vfs.zfs.vdev.sync_read_min_active 10 vfs.zfs.vdev.max_active 1000 vfs.zfs.vdev.async_write_active_max_dirty_percent60 vfs.zfs.vdev.async_write_active_min_dirty_percent30 vfs.zfs.vdev.mirror.non_rotating_seek_inc1 vfs.zfs.vdev.mirror.non_rotating_inc 0 vfs.zfs.vdev.mirror.rotating_seek_offset1048576 vfs.zfs.vdev.mirror.rotating_seek_inc 5 vfs.zfs.vdev.mirror.rotating_inc 0 vfs.zfs.vdev.trim_on_init 1 vfs.zfs.vdev.cache.bshift 16 vfs.zfs.vdev.cache.size 0 vfs.zfs.vdev.cache.max 16384 vfs.zfs.vdev.default_ms_shift 29 vfs.zfs.vdev.min_ms_count 16 vfs.zfs.vdev.max_ms_count 200 vfs.zfs.txg.timeout 5 vfs.zfs.spa_min_slop 134217728 vfs.zfs.spa_slop_shift 5 vfs.zfs.spa_asize_inflation 24 vfs.zfs.deadman_enabled 0 vfs.zfs.deadman_checktime_ms 5000 vfs.zfs.deadman_synctime_ms 1000000 vfs.zfs.debug_flags 0 vfs.zfs.debugflags 0 vfs.zfs.recover 0 vfs.zfs.spa_load_verify_data 1 vfs.zfs.spa_load_verify_metadata 1 vfs.zfs.spa_load_verify_maxinflight 10000 vfs.zfs.max_missing_tvds_scan 0 vfs.zfs.max_missing_tvds_cachefile 2 vfs.zfs.max_missing_tvds 0 vfs.zfs.spa_load_print_vdev_tree 0 vfs.zfs.ccw_retry_interval 300 vfs.zfs.check_hostid 1 vfs.zfs.mg_fragmentation_threshold 85 vfs.zfs.mg_noalloc_threshold 0 vfs.zfs.condense_pct 200 vfs.zfs.metaslab_sm_blksz 4096 vfs.zfs.metaslab.bias_enabled 1 vfs.zfs.metaslab.lba_weighting_enabled 1 vfs.zfs.metaslab.fragmentation_factor_enabled1 vfs.zfs.metaslab.preload_enabled 1 vfs.zfs.metaslab.preload_limit 3 vfs.zfs.metaslab.unload_delay 8 vfs.zfs.metaslab.load_pct 50 vfs.zfs.metaslab.min_alloc_size 33554432 vfs.zfs.metaslab.df_free_pct 4 vfs.zfs.metaslab.df_alloc_threshold 131072 vfs.zfs.metaslab.debug_unload 0 vfs.zfs.metaslab.debug_load 0 vfs.zfs.metaslab.fragmentation_threshold70 vfs.zfs.metaslab.force_ganging 16777217 vfs.zfs.free_bpobj_enabled 1 vfs.zfs.free_max_blocks -1 vfs.zfs.no_scrub_prefetch 0 vfs.zfs.no_scrub_io 0 vfs.zfs.resilver_min_time_ms 3000 vfs.zfs.free_min_time_ms 1000 vfs.zfs.scan_min_time_ms 1000 vfs.zfs.scan_idle 50 vfs.zfs.scrub_delay 4 vfs.zfs.resilver_delay 2 vfs.zfs.top_maxinflight 32 vfs.zfs.zfetch.array_rd_sz 1048576 vfs.zfs.zfetch.max_idistance 67108864 vfs.zfs.zfetch.max_distance 8388608 vfs.zfs.zfetch.min_sec_reap 2 vfs.zfs.zfetch.max_streams 8 vfs.zfs.prefetch_disable 0 vfs.zfs.delay_scale 500000 vfs.zfs.delay_min_dirty_percent 60 vfs.zfs.dirty_data_sync 67108864 vfs.zfs.dirty_data_max_percent 10 vfs.zfs.dirty_data_max_max 4294967296 vfs.zfs.dirty_data_max 4294967296 vfs.zfs.max_recordsize 1048576 vfs.zfs.default_ibs 17 vfs.zfs.default_bs 9 vfs.zfs.send_holes_without_birth_time 1 vfs.zfs.mdcomp_disable 0 vfs.zfs.per_txg_dirty_frees_percent 30 vfs.zfs.nopwrite_enabled 1 vfs.zfs.dedup.prefetch 1 vfs.zfs.dbuf_cache_lowater_pct 10 vfs.zfs.dbuf_cache_hiwater_pct 10 vfs.zfs.dbuf_cache_shift 5 vfs.zfs.dbuf_cache_max_bytes 3060818688 vfs.zfs.l2c_only_size 0 vfs.zfs.mfu_ghost_data_esize 44354878976 vfs.zfs.mfu_ghost_metadata_esize 8191800320 vfs.zfs.mfu_ghost_size 52546679296 vfs.zfs.mfu_data_esize 0 vfs.zfs.mfu_metadata_esize 84992 vfs.zfs.mfu_size 64779776 vfs.zfs.mru_ghost_data_esize 48840192 vfs.zfs.mru_ghost_metadata_esize 926682624 vfs.zfs.mru_ghost_size 975522816 vfs.zfs.mru_data_esize 47824171520 vfs.zfs.mru_metadata_esize 5086352896 vfs.zfs.mru_size 52926374400 vfs.zfs.anon_data_esize 0 vfs.zfs.anon_metadata_esize 0 vfs.zfs.anon_size 69500928 vfs.zfs.l2arc_norw 1 vfs.zfs.l2arc_feed_again 1 vfs.zfs.l2arc_noprefetch 1 vfs.zfs.l2arc_feed_min_ms 200 vfs.zfs.l2arc_feed_secs 1 vfs.zfs.l2arc_headroom 2 vfs.zfs.l2arc_write_boost 8388608 vfs.zfs.l2arc_write_max 8388608 vfs.zfs.arc_meta_limit 13421772800 vfs.zfs.arc_free_target 167651 vfs.zfs.compressed_arc_enabled 1 vfs.zfs.arc_grow_retry 60 vfs.zfs.arc_shrink_shift 7 vfs.zfs.arc_average_blocksize 8192 vfs.zfs.arc_no_grow_shift 5 vfs.zfs.arc_min 12243274752 vfs.zfs.arc_max 53687091200 vfs.zfs.abd_chunk_size 4096 ------------------------------------------------------------------------ A few iterations of 'zpool iostat -v': capacity operations bandwidth pool alloc free read write read write ------------ ----- ----- ----- ----- ----- ----- mendeleev 5.02T 16.6T 3.58K 0 389M 0 raidz2 5.02T 16.6T 3.58K 0 389M 0 gpt/zfs0 - - 783 0 45.9M 0 gpt/zfs1 - - 1.29K 0 100M 0 gpt/zfs2 - - 711 0 54.9M 0 gpt/zfs3 - - 729 0 54.3M 0 gpt/zfs4 - - 1.23K 0 99.7M 0 gpt/zfs5 - - 752 0 46.3M 0 ------------ ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ------------ ----- ----- ----- ----- ----- ----- mendeleev 5.02T 16.6T 8.71K 0 286M 0 raidz2 5.02T 16.6T 8.71K 0 286M 0 gpt/zfs0 - - 715 0 35.6M 0 gpt/zfs1 - - 2.15K 0 82.7M 0 gpt/zfs2 - - 791 0 34.4M 0 gpt/zfs3 - - 706 0 33.6M 0 gpt/zfs4 - - 2.29K 0 82.3M 0 gpt/zfs5 - - 693 0 37.0M 0 ------------ ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ------------ ----- ----- ----- ----- ----- ----- mendeleev 5.02T 16.6T 6.28K 0 775M 0 raidz2 5.02T 16.6T 6.28K 0 775M 0 gpt/zfs0 - - 1.37K 0 112M 0 gpt/zfs1 - - 1.57K 0 194M 0 gpt/zfs2 - - 802 0 87.0M 0 gpt/zfs3 - - 851 0 86.9M 0 gpt/zfs4 - - 2.03K 0 199M 0 gpt/zfs5 - - 1.09K 0 112M 0 ------------ ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool alloc free read write read write ------------ ----- ----- ----- ----- ----- ----- mendeleev 5.02T 16.6T 9.15K 0 272M 0 raidz2 5.02T 16.6T 9.15K 0 272M 0 gpt/zfs0 - - 507 0 23.1M 0 gpt/zfs1 - - 2.77K 0 80.7M 0 gpt/zfs2 - - 727 0 41.8M 0 gpt/zfs3 - - 707 0 41.2M 0 gpt/zfs4 - - 2.58K 0 76.1M 0 gpt/zfs5 - - 509 0 23.6M 0 ------------ ----- ----- ----- ----- ----- ----- From owner-freebsd-questions@freebsd.org Fri Jul 13 00:03:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62EC81034870 for ; Fri, 13 Jul 2018 00:03:55 +0000 (UTC) (envelope-from lists@fullard.ca) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 0117A8991B for ; Fri, 13 Jul 2018 00:03:54 +0000 (UTC) (envelope-from lists@fullard.ca) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id B557E2C1 for ; Thu, 12 Jul 2018 20:03:46 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute5.internal (MEProxy); Thu, 12 Jul 2018 20:03:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fullard.ca; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=yWN+E66Ta5A57zIaO32mTZz4Ye6NR DMyiTtVBpQ9+b8=; b=lYEzHPo8REUJgVQnfC1TLfHuMTGUXTI1tM1Y35410ApvI ofHpl3jm7kz89zUv1vgfRdzplGgHvR4svm2hEe60ZzH09Mo/1lNEmfC7itklZ+xi fhBnIBq8MuHzajMsRdHyFzYrMoCTXTrSz7yHuKR7aXvz0PP/Pcxv3wVDV77hX8m8 X3XIHU7VIp56DUq0KE12L706yj456NkJNt1/47SUn2L2Fv9h8KjSoeTxaHD1wE+/ vj1V0rTLl0QZSA7UPrjkojMMYzdRkXKM+od8tEJ8MN+iLBaqeDXrs7Lm0a2P4UmL viNsb/l0DsMgepcMBg81Xcw4BZ54jERyM1ioMBF6Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=yWN+E6 6Ta5A57zIaO32mTZz4Ye6NRDMyiTtVBpQ9+b8=; b=c9i8epeXl9+/c6pLHZzKdj 4iOzx6yUWIqbtrU34TnkEvVtY1biZF7jFp0QoGDOFpnSeYgUqezJROjlZLFewkEO HarXMZu7QuKjMYT9cyvvu9uupCRgY8pskXBCVyyCe0ULOXzF9Xak/dDwz49qkIjY 6EB2aXAPosaXu6x9KE3qTKlzYYlGx3QUG0WqfQeQ3SbB3uAP2Mo3Ed7poEAuVMDV h9jR/0qoSnSc86Qr3zIkrqUu/6gmGPTqMhG2LcRglZzr1UhsPaSzq+p/cYqLUMy0 JilAGk7fJdEGHBYTEf4zo271yUxU2Dwu1Y/XDSpoCWx/RxLd2FJ1+xRAI7vqn7RA == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id D6BF9BA50C; Thu, 12 Jul 2018 20:03:45 -0400 (EDT) Message-Id: <1531440225.583839.1439134704.47DD7B1D@webmail.messagingengine.com> From: David Fullard To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-957169fa Subject: Re: ssh on 11.2 References: Date: Thu, 12 Jul 2018 20:03:45 -0400 In-Reply-To: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 00:03:55 -0000 I think you missed it. When upgrading I remember being prompted that changes that needed to be applied to the /etc/sshd_config and it asking me if it looked okay. On Thu, Jul 12, 2018, at 5:17 PM, doug wrote: > After going to 11.2 from 11.1 authorized_keys2 MUST be renamed to > authorized_keys. I spent a bit of time checking permissions and keys > before > comparing /etc/ssh/sshd_config. This might be implied in some of the > Open-ssh > errata but not so I got it. A note in UPDATING might be nice, or did I > just miss > this? > > > _______________________________________________ > 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 Fri Jul 13 02:30:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF97510461BF for ; Fri, 13 Jul 2018 02:30:06 +0000 (UTC) (envelope-from va6bmj@gmail.com) Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::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 433568F1DC for ; Fri, 13 Jul 2018 02:30:06 +0000 (UTC) (envelope-from va6bmj@gmail.com) Received: by mail-ua0-x232.google.com with SMTP id q12-v6so19721406ual.2 for ; Thu, 12 Jul 2018 19:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ieIniz3ljYUXsR7Zy3LFnyZnfPthBYUlH1wfEJAi3qI=; b=mA55ucYoTl6U4p3KwVoQUxZYTXVhcnBtTzay07JARw04csRK4qPcIN+ZXclJU6ftiV klNYt+FypSWBWxBUkiA8euiRQsnUS3pOzQHAHreiSU2EGKMgAmCQNHit+0s0/RrAOqGK tyLq5ciQk0hRPLWy+5D6GNGST1C16jzn5jqlPUv3LsD3GzDK62OL9bofYL2r/wTP/Z/F 6UBfH+HxXEWeIcHGGwQJpqN0zCj79+9vS0hq1+g6XqqxtuXaASY+TbS2Fyx348ViFbNi Op7DAoexsPpQJ3R2EKkvhLW5rKlZAxmmipaMp3Gmza1+LKhTJme9jbQRFShLdkBkw29c IwFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ieIniz3ljYUXsR7Zy3LFnyZnfPthBYUlH1wfEJAi3qI=; b=IY3T4B8fsM9SFeN1Twov18/RIgng82l6PVQVtsTpuX79Lxc0Zzx3ljVDqxQe5rYU/D VBLoJcMzqUm8UpucxTGrXalxV2a24N3XzD1nOHpiKzO6ivNu5qQVVOB1hd7Ee5qJPD4+ 0XBMchd3c6oHWdOIV4I0r5EvFeU/pH6QTjY1I1l1QDV3MZ/RhTdpIv3uixm1J1N1xViQ iadIA47vVCr+sNA5CHV1YOCnF7ACsVwPRt2LbJccDSTqICuvdKEp2U0Cg+2d4NK0WAdw qB3G51wdboj8rfxC9FHHEz6IEHwjeRqRqx7J+CbKOYYQxNC0ZXu8lrIa9vyRPmF7p4Mb f1pA== X-Gm-Message-State: AOUpUlH0XwSGJw0Bt2IoA7ip976eZlErGgU9uFq8p75nKjrpWHeCSVEC Sca2NBHbx57YyF0F1jR6NF5xwFM2jZa88S4lM/g= X-Google-Smtp-Source: AAOMgpftx4GI5AFKwnoiFIFa8UCTXcFXEJ8rCARWwl8zxp8o2HB4kKSVKabRhLKp7Qs3LAwFzV4XjlXUjEKpRUdkWP4= X-Received: by 2002:a9f:25f2:: with SMTP id 105-v6mr2858007uaf.68.1531449005314; Thu, 12 Jul 2018 19:30:05 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:4c9a:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 19:30:04 -0700 (PDT) In-Reply-To: <20180621151647.2cdb8e6b.freebsd@edvax.de> References: <20180614093928.6f39434e.freebsd.ed.lists@sumeritec.com> <20180614161923.5246ae81.freebsd.ed.lists@sumeritec.com> <20180615102548.1c686d1b.freebsd.ed.lists@sumeritec.com> <20180619095828.26271eea.freebsd.ed.lists@sumeritec.com> <20180619115218.58b3983e.freebsd@edvax.de> <20180621151647.2cdb8e6b.freebsd@edvax.de> From: B J Date: Fri, 13 Jul 2018 02:30:04 +0000 Message-ID: Subject: Re: Problems Connecting Laptop To Modem To: Polytropon Cc: freebsd-questions , Erich Dollansky Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 02:30:07 -0000 During the past few weeks, I've tried all sorts of things in trying to solve the problem of connecting the laptop to the Internet. Late last month, I was at the house I inherited and I took the HD with me. I've got two machines there, as well as two different Internet services. I put that HD into one of the laptops and tried to connect to each modem. No joy. Whatever the problem is, it had to be something to do with drive. Earlier today, I installed FreeBSD on a spare HD that I connected to one of my tower machines. I put that drive into the original laptop and got the same results. The interface can't find a DHCP server and can't make a connection to the Internet. In addition, the laptop has a wireless interface, but the installer can't find it. Also, before the connection problems began, the machine had a number of sudden shutdowns, which, I suspect, might have been due to kernel panics. Considering the age of the machine, and the condition it was in when it was given to me, I'm inclined to think that the problem is on the motherboard. Maybe it's time to put the laptop up on blocks or, if it fails completely, cannibalize it for spare parts. BMJ From owner-freebsd-questions@freebsd.org Fri Jul 13 07:34:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9004B102CE45 for ; Fri, 13 Jul 2018 07:34:54 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [195.30.95.33]) (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 1D3C879448 for ; Fri, 13 Jul 2018 07:34:53 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (096-100-000-128.ip-addr.inexio.net [128.0.100.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id AB35212E28FA for ; Fri, 13 Jul 2018 09:34:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1531467285; bh=0BYR7nPPGjPD/+Owf4Q7IjhdPw1ztSM6mDXorigmZhc=; h=To:From:Subject:Date; b=rEztFBJgLTPNNI1DVp1unPtkJ9uRfls/Jt3UyPPuXlDm0P1UwvB0dUSrx1wSxxGqU Fr1OAR+2P6DDUh0VdxZWM8xyYQ/tccRe4k9SvVEOp/16dPxVa6d9+yY9PvaEjHRYGX iGSQKDp2T6L7dn2FB810AE1sOsmGo31IkFH+7x5k= Received: from [192.168.0.151] (096-100-000-128.ip-addr.inexio.net [128.0.100.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id DE9A0E8E9EC for ; Fri, 13 Jul 2018 09:34:44 +0200 (CEST) To: freebsd-questions@freebsd.org From: Matthias Fechner Subject: 11.2 cannot boot with root on ZFS Openpgp: preference=signencrypt Autocrypt: addr=idefix@fechner.net; prefer-encrypt=mutual; keydata= xsFNBFqca1YBEADM9mF2+ifk8HILTlf5wtAzV6SYVR4RvNOo/8Kucw4sCZT76zS1fjZe4Zy1 3C0IZ07Wi+3PnoGIgOCsXp3PrTc2nuHQWkwVBYXy8UaR9DHBWA/mIvRGG1ZscKQYA6oUdCvd K8Mu26zO60yTt+ONzFtK6G1myH4EHXZ8dpmdCFf+W3rzTU+aCQ5S3OfwCLGgYgOaVREGkdOc 5SVCpFb4n+2B8+CqeWsRHhnT+4h7/YhgDMGp4GiI3yrB2nBVSUUvcosD2nRtJQgGQHcAFtMq 3hJaKPOR/mHc6KVrp0xmGNmdtazvXloHmGIl9O1UpmMmrYu9Kugl0JkGi2fAcno02XgVlkyX 7xDLTteP5cNqRxor4yVDaRWUQnOfK9XgcrKGrAzb65BkCSkjT+Aw3S/A8Qd6NvjL9qy1d+Ct dzatOVF/Y7jaW28CMr3jvwPS13OxV7PnJzIZzdik20eVxfOXuYfxZD+PwBaGgFF0qj6zKACC aKLalE0ZpY0zNn/iPyQX/Cf9KoDyFpOHSsEswiJ5rCWwppVcsFyogHOemVmeaXlvyDPEipnV ZUkpGP/CCqPu3eD0uDzP7UJ0pt/l/JfW0Xw/4p9mjB024xiRlxLa6vSRfGl//EdtAIbKKa8x 5wsKTQEbYJDmXE3tH/A54DCqRXhcopTlu2iJlTdnIMltn9afVwARAQABzSVNYXR0aGlhcyBG ZWNobmVyIDxpZGVmaXhAZmVjaG5lci5uZXQ+wsGXBBMBCgBBAhsDBQkJZgGABQsJCAcDBRUK CQgLBRYDAgEAAh4BAheAFiEEaWB64mCp804YOtqutot13J/XR+EFAlqcc9gCGQEACgkQtot1 3J/XR+GQyhAAwDxUSg7X2aS1d6rrYUZdDk8rT5TCjayDAyOATdAUhJRZk8qXRNF27Mu6xiOT mIvEMKLagNsitffZs1g/mulRQiDVLloGav7xozSfYlaOYWpPb55wpsugQPLZz0OkU9tzw7j7 7sPPvnAxeqSofUJzQdZzp43aVwXVqsJ3rY0jGzYA5RLS6CBI1RRR8/hHLMxspDPl79IW3GhI HAXaVX1HVJA2oJEo9Y95DnJwX8NV+hvLlUVA2KDdNKFiVJKeV3ccqw+/5zW3Y8J6Rd8blW9n p68Z7lyxt6mvsDEdSxOyGSkPagzIDfHqmDfkaeum7gHMwweH2e2pZuhzMZkrKNoSkKiJ5uim 638ZhnzzmEWh2qtYPgHlZG1jO6n2DSzCqJkQYjYUtLj7ylIgZakG8M3idQRugHImMBq+HSMu WR8FI52gh1+4LbIArHB4YWTTr933ElwhS1jtomK9SeWezPfjunpxqXQl4QR0qXAuglsOMJ6y Togb6lc0qyEdOa5VCXQTLSD9yZpolSQOjOe1XEyM4g5v7FrPBGVni9AxlARvUDVbYQDv1+4A gchtgpLmAF8mDPq/tGeXuAO3m+ExQDXpJ4CneI9YHc+joU2cXQi5MP1NzgMOV43XEZCiTW0O BWM1+857gmDqGbybE7F3UFpvBs9/NRWnuxoKaYxYbqCOc3nOwU0EWpxrVgEQAN3uCLHZF+1V gcrzYjwL1wAJwjYb7UnHKvNYdaBKgW0n0NTfaTCLHxHYPO8NlV1+lNctSeXLeiWpmE1lCDHq /++53EJ34OsRd/n246PdtfIfltML73tsmq6S9zTye2zv7LsmE7jgUBaasbv0qSLSybOUvkRx j3xBuK9Ymg/ZXaENOhxwIQ6oQoNLg3ers9t5Xl4NVK6gzzZ2OdTGnuUVhQmi4rbP04R0GJFh AtGLAYUCxlXVZhdPAs4qZaoAEP5nW/u2MyzSaIouwcEIdttAiPZdrJr+a4OGKz88Sn6zqKSa uyUADgX+G8tKUONgZbfz4SSRvlinOgyU2RyyfNS977r/YfaHH+oAxg31yUWPtD/ryfVw69bG vK8RQrZ9+c1vyWBABoQOh5+JHW/AE9Xj5dQatEfWmGO3+/FRo2TIhqZQXXl8PW+jtEjkhgOH OUX5ERzSm6nCcPIw+LUkEINcLc9bw4fv1eOWIdBuCckGM4rWXkLYbqhdSzdWeCsC0tiQk8x7 O1zXRJOKF4rITJd/qX322EH29BR+T9V1Hw7LDSRe+3YxtoXhROZRXjF8QniEHeKVNRUComr6 rWGmuHjsNTQ7twtwnG8xSOfCkYAp9GrbzBkIYX+VFvFQLqVM+It3RAlge/bwpZPvkr3bFsJk 4JS+EAugBIrP0xd9BMOh6Ej5ABEBAAHCwXwEGAEKACYWIQRpYHriYKnzThg62q62i3Xcn9dH 4QUCWpxrVgIbDAUJCWYBgAAKCRC2i3Xcn9dH4ZZsEACoQI109htphVe2AQhJ7wuPo8pIrSFA 0Mb0pfibX/sYw8ZZz/x3ctTI3Ajq2baSaoebIuUyd6oPI7cAzgL4s2zHiZ3ChH2dDxJlOPfk OaiK124DJMPqWiWuxe39tgq23tsPhwcvF+DC+SkJoLWKCYNC06fS3bLktZ0s4lVE5tqfL5ww MvxgxB+6+sWHwZWSv1IwB/geov6zkEhVdkXqrGPE52LyLfU0ACMmihcl0/npsCMZSls0urge CsPMuHPQnmcM2ERbere8i9OdKQDzGBrTbWl9DxNRf4o+cAYirEJM3Kc+ZD2SE34bTSvg3kdQ QZQbj+o+BRcsR0LaGbORkNaMZlp5OuXteL6nG7sbAPn0bjUUlup8CJEXDXENG6LJG1/oVWFq m3OtPyr5UoMQAuhuGx0/Om6AXKr/mk+veuoKWMXkqll045/bYE7bX2A0gkyGE5DdjaiHPmS9 NsWuKDeExLlXZOL1GX+PKjWLADwlv07XHB8Hf6U0/lpf3/mggRtqHyKbHt0iRqYaMC95gVdM rbugxh61U/zxIaweU7VolD5cRrltxqPp5szOwDzw42JYwbpYsXFJXNkuCGCmK1LHcShfEggt fV3g/JKzvNRQn6p1f0frppl/eZ5UvWVKrNERJzcZgkOecxwiK/L/JoGpGfWOqWGsTxe/AnQc Xxj8Dw== Message-ID: Date: Fri, 13 Jul 2018 09:34:41 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Language: de-DE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 07:34:54 -0000 RGVhciBhbGwsDQoNCkkgY3VycmVudGx5IHdvcmsgd2l0aCBGcmVlQlNEIDExLjEgYm9vdGlu ZyBmcm9tIGEgWkZTIG1pcnJvciBhbmQgaGF2aW5nDQphbiBhZGRpdGlvbmFsIHJhaWR6LTEg cG9vbDoNCg0KwqAgcG9vbDogenJvb3QNCsKgc3RhdGU6IE9OTElORQ0KwqAgc2Nhbjogc2Ny dWIgY2FuY2VsZWQgb24gTW9uIEp1bMKgIDIgMjI6MTI6MzEgMjAxOA0KY29uZmlnOg0KDQrC oMKgwqDCoMKgwqDCoCBOQU1FwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBTVEFURcKgwqDCoMKg IFJFQUQgV1JJVEUgQ0tTVU0NCsKgwqDCoMKgwqDCoMKgIHpyb290wqDCoMKgwqDCoMKgwqDC oMKgwqAgT05MSU5FwqDCoMKgwqDCoMKgIDDCoMKgwqDCoCAwwqDCoMKgwqAgMA0KwqDCoMKg wqDCoMKgwqDCoMKgIG1pcnJvci0wwqDCoMKgwqDCoCBPTkxJTkXCoMKgwqDCoMKgwqAgMMKg wqDCoMKgIDDCoMKgwqDCoCAwDQrCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIGdwdC96cm9vdDDC oCBPTkxJTkXCoMKgwqDCoMKgwqAgMMKgwqDCoMKgIDDCoMKgwqDCoCAwDQrCoMKgwqDCoMKg wqDCoMKgwqDCoMKgIGdwdC96cm9vdDHCoCBPTkxJTkXCoMKgwqDCoMKgwqAgMMKgwqDCoMKg IDDCoMKgwqDCoCAwDQoNCmVycm9yczogTm8ga25vd24gZGF0YSBlcnJvcnMNCg0KwqAgcG9v bDogenN0b3JhZ2UNCsKgc3RhdGU6IE9OTElORQ0KwqAgc2Nhbjogc2NydWIgcmVwYWlyZWQg Ni41MEcgaW4gN2gzM20gd2l0aCAwIGVycm9ycyBvbiBUaHUgSmFuIDIxDQoyMjo1MToxMiAy MDE2DQpjb25maWc6DQoNCsKgwqDCoMKgwqDCoMKgIE5BTUXCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoCBTVEFURcKgwqDCoMKgIFJFQUQgV1JJVEUgQ0tTVU0NCsKgwqDCoMKgwqDCoMKg IHpzdG9yYWdlwqDCoMKgwqDCoMKgwqDCoMKgIE9OTElORcKgwqDCoMKgwqDCoCAwwqDCoMKg wqAgMMKgwqDCoMKgIDANCsKgwqDCoMKgwqDCoMKgwqDCoCByYWlkejEtMMKgwqDCoMKgwqDC oMKgIE9OTElORcKgwqDCoMKgwqDCoCAwwqDCoMKgwqAgMMKgwqDCoMKgIDANCsKgwqDCoMKg wqDCoMKgwqDCoMKgwqAgZ3B0L3N0b3JhZ2UwwqAgT05MSU5FwqDCoMKgwqDCoMKgIDDCoMKg wqDCoCAwwqDCoMKgwqAgMA0KwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBncHQvc3RvcmFnZTHC oCBPTkxJTkXCoMKgwqDCoMKgwqAgMMKgwqDCoMKgIDDCoMKgwqDCoCAwDQrCoMKgwqDCoMKg wqDCoMKgwqDCoMKgIGdwdC9zdG9yYWdlMsKgIE9OTElORcKgwqDCoMKgwqDCoCAwwqDCoMKg wqAgMMKgwqDCoMKgIDANCg0KZXJyb3JzOiBObyBrbm93biBkYXRhIGVycm9ycw0KDQpJIHRy aWVkIHRvIHVwZ3JhZGUgdG8gMTEuMiB1c2luZyBmcmVlYnNkLXVwZGF0ZToNCmZyZWVic2Qt dXBkYXRlIHVwZ3JhZGUgLXIgMTEuMi1SRUxFQVNFDQpmcmVlYnNkLXVwZGF0ZSBpbnN0YWxs DQpyZWJvb3QNCg0KQnV0IEZyZWVCU0QgMTEuMiBzZWVtcyBub3QgdG8gZmluZCB0aGUgemZz IHBvb2wgYW55bW9yZSB3aGlsZSBib290aW5nLg0KR2l2aW5nIHRoZSBwb29sIG1hbnVhbGx5 IHdoaWxlIGl0IGFza3MgZm9yIGRvZXMgbm90IGhlbHAgbmVpdGhlci4NCg0KSSBjaGVja2Vk IHRoZSBlcnJhdGEgaGVyZToNCmh0dHBzOi8vd3d3LmZyZWVic2Qub3JnL3JlbGVhc2VzLzEx LjJSL2VycmF0YS5odG1sDQphbmQgaXQgc2VlbXMgdGhhdCB0aGlzIGVycm9yIHdhcyBkaXNj b3ZlcmVkIFsyMDE3LTA3LTI1XS4NCg0KQXJlIHRoZXJlIGFueSBhY3Rpb25zIHBsYW5uZWQg dG8gZ2V0IHRoYXQgZml4ZWQ/DQpDdXJyZW50bHkgSSdtIGZpeGVkIHRvIHZlcnNpb24gMTEu MSB3aGljaCBydW5zIG91dCBvZiBzdXBwb3J0IHNvb24uDQpEb2VzIGFueW9uZSBoYXZlIGFu IGlkZWEgdG8gd29yay1hcm91bmQgdGhpcyBwcm9ibGVtPw0KDQpUaGFua3MgYSBsb3QuDQoN CkdydcOfDQpNYXR0aGlhcw0KDQotLSANCg0KIlByb2dyYW1taW5nIHRvZGF5IGlzIGEgcmFj ZSBiZXR3ZWVuIHNvZnR3YXJlIGVuZ2luZWVycyBzdHJpdmluZyB0bw0KYnVpbGQgYmlnZ2Vy IGFuZCBiZXR0ZXIgaWRpb3QtcHJvb2YgcHJvZ3JhbXMsIGFuZCB0aGUgdW5pdmVyc2UgdHJ5 aW5nIHRvDQpwcm9kdWNlIGJpZ2dlciBhbmQgYmV0dGVyIGlkaW90cy4gU28gZmFyLCB0aGUg dW5pdmVyc2UgaXMgd2lubmluZy4iIC0tDQpSaWNoIENvb2sNCg0K From owner-freebsd-questions@freebsd.org Fri Jul 13 13:58:02 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7FFD103D63D for ; Fri, 13 Jul 2018 13:58:02 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5498487121 for ; Fri, 13 Jul 2018 13:58:02 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 98A5211020B for ; Fri, 13 Jul 2018 08:57:54 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 7C01711020A; Fri, 13 Jul 2018 08:57:54 -0500 (CDT) Date: Fri, 13 Jul 2018 08:57:54 -0500 From: Doug McIntyre To: freebsd-questions@FreeBSD.org Subject: Re: ssh on 11.2 Message-ID: <20180713135754.GA74801@geeks.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 13:58:02 -0000 On Thu, Jul 12, 2018 at 05:17:25PM -0400, doug wrote: > After going to 11.2 from 11.1 authorized_keys2 MUST be renamed to > authorized_keys. I spent a bit of time checking permissions and keys before > comparing /etc/ssh/sshd_config. This might be implied in some of the Open-ssh > errata but not so I got it. A note in UPDATING might be nice, or did I just miss > this? Wow, you had an authorized_keys2 file? That was deprecated in OpenSSH 3.0 https://marc.info/?l=openssh-unix-dev&m=100508718416162&w=2 Your setup must have been copied along for quite some time. My guess is that OpenSSH finally removed support of it (although I'd have guessed the support would have been removed long ago), as part of the general cleanup. The changeover happened eons ago, so they probably figured nobody had that version any longer. From owner-freebsd-questions@freebsd.org Fri Jul 13 14:16:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34304103E117 for ; Fri, 13 Jul 2018 14:16:23 +0000 (UTC) (envelope-from patrick@davenulle.org) Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F08288718 for ; Fri, 13 Jul 2018 14:16:22 +0000 (UTC) (envelope-from patrick@davenulle.org) Received: from mr185083 (mr185083.univ-rennes1.fr [129.20.185.83]) by mx.zohomail.com with SMTPS id 1531491361323862.4820435580297; Fri, 13 Jul 2018 07:16:01 -0700 (PDT) Date: Fri, 13 Jul 2018 16:15:56 +0200 From: Patrick Lamaiziere To: freebsd-questions@freebsd.org Cc: tech-lists Subject: Re: vim color and copy/paste Message-ID: <20180713161556.70f8e525@mr185083> In-Reply-To: References: <20180712115452.48cee92d@mr185083> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-ZohoMailClient: External X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 14:16:23 -0000 Le Thu, 12 Jul 2018 11:02:10 +0100, tech-lists a =C3=A9crit : > On 12/07/2018 10:54, Patrick Lamaiziere wrote: > > Any idea why with Vim in a terminal xterm I cannot copy/paste text > > when the text is colored (syntax color by sample)? > >=20 > > vim-lite-8.0.0134 > > freebsd 11.2 =20 >=20 > Hi, >=20 > What's in your .vimrc ? >=20 > In a minimal config, I have just the following: >=20 > set mouse=3D >=20 > otherwise mouse commands get interpreted by vim and I don't want that. I've edited /usr/local/etc/vim/vimrc and /root/.vimrc to add set mouse-=3Da without vim uses a 'visual mode'. Thanks a lot, regards. From owner-freebsd-questions@freebsd.org Fri Jul 13 16:45:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20E411043977 for ; Fri, 13 Jul 2018 16:45:00 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by mx1.freebsd.org (Postfix) with ESMTP id C72308E68D for ; Fri, 13 Jul 2018 16:44:59 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 2278DBF353; Fri, 13 Jul 2018 16:44:53 +0000 (UTC) Received: from fledge.watson.org (doug@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.15.2/8.15.2) with ESMTP id w6DGiq4j023968; Fri, 13 Jul 2018 12:44:52 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id w6DGiqdK023965; Fri, 13 Jul 2018 12:44:52 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Fri, 13 Jul 2018 12:44:52 -0400 (EDT) From: doug Reply-To: doug@safeport.com To: Doug McIntyre cc: freebsd-questions@FreeBSD.org Subject: Re: ssh on 11.2 In-Reply-To: <20180713135754.GA74801@geeks.org> Message-ID: References: <20180713135754.GA74801@geeks.org> 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 (fledge.watson.org [127.0.0.1]); Fri, 13 Jul 2018 12:44:52 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 16:45:00 -0000 On Fri, 13 Jul 2018, Doug McIntyre wrote: > On Thu, Jul 12, 2018 at 05:17:25PM -0400, doug wrote: >> After going to 11.2 from 11.1 authorized_keys2 MUST be renamed to >> authorized_keys. I spent a bit of time checking permissions and keys before >> comparing /etc/ssh/sshd_config. This might be implied in some of the Open-ssh >> errata but not so I got it. A note in UPDATING might be nice, or did I just miss >> this? > > Wow, you had an authorized_keys2 file? That was deprecated in OpenSSH 3.0 > https://marc.info/?l=openssh-unix-dev&m=100508718416162&w=2 > > Your setup must have been copied along for quite some time. > > My guess is that OpenSSH finally removed support of it (although I'd > have guessed the support would have been removed long ago), as part > of the general cleanup. The changeover happened eons ago, so they > probably figured nobody had that version any longer. > Thanks for the info. Yea one of my keys is from the previous millennium. But my point remains. So you peaked my curiosity. FreeBSD takes no note of this as far as I can find. https://www.openssh.com/releasenotes.html covers OpenSSH 7.7/7.7p1 (2018-04-02) to openSSH 1.2.3p1 (2000-03-24). And indeed OpenSSH 5.9/5.9p1 (2011-09-06) notes authorized_keys2 is deprecated. That's not noted in UPDATING either. Without the comment in sshd_config it I would still be looking. One of the guys I work with has never used authorized_keys2 so I would have gotten it eventually from that. Back in the very eary ssh days I wanted to do a simple change that was eventually implemented. But from that I know I am not up to reading the ssh code. From owner-freebsd-questions@freebsd.org Fri Jul 13 19:11:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 829031048FC2 for ; Fri, 13 Jul 2018 19:11:41 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (ns.umpquanet.com [209.216.177.146]) (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 0D624742BE for ; Fri, 13 Jul 2018 19:11:40 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (localhost [127.0.0.1]) by g5.umpquanet.com (8.15.2/8.15.2) with ESMTPS id w6DJApQP002014 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Jul 2018 12:10:51 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by g5.umpquanet.com (8.15.2/8.15.2/Submit) id w6DJAog1002013; Fri, 13 Jul 2018 12:10:50 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: g5.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Fri, 13 Jul 2018 12:10:50 -0700 From: Jim Long To: Mike Tancsa Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] Message-ID: <20180713191050.GA98371@g5.umpquanet.com> References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> <20180712214248.GA98578@g5.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180712214248.GA98578@g5.umpquanet.com> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 19:11:41 -0000 On Thu, Jul 12, 2018 at 02:42:48PM -0700, Jim Long wrote: > On Thu, Jul 12, 2018 at 02:49:53PM -0400, Mike Tancsa wrote: > > --snip-- > > > I would try and set a ceiling. On > > RELENG_11 you dont need to reboot > > > > Try > > sysctl -w vfs.zfs.arc_max=77946198016 > > > > which shaves off 20G from what ARC can gobble up. Not sure if thats your > > issue, but it is an issue for some users. > > > > If you are still hurting for caching, an SSD drive or NVME and make it a > > caching device for your pool. > > > > and what does > > zpool status > > show ? > > I set the limit to the value you suggested, and the next test ran less > than three minutes before the machine rebooted, with no crash dump produced. > > I further reduced the limit to 50G and it's been running for about 50 minutes > so far. Fingers crossed. I do have L2ARC I can add if need be. > > I'll keep you posted on how this run goes. > > Thank you, > > Jim It appears that limiting the ARC size did it. The 'zfs send -R' was able to complete with ARC limited to 50G, and a second run with a 60G ARC limit also completed. That is a very handy tunable to know about. Being able to reduce cache size on a running system when needed, to free up RAM, or whatever. I was curious to find the answer to your query about the average size of files on the system, so I ran a 'zdb -b' on the pool. That process began to page out large amounts of RAM into swap, which was making the system rather sluggish, especially once I decided to kill the zdb process. By dropping the ARC size limit, I was able to temporarily free some RAM so that the process could succumb to the SIGKILL signal. Thank you very much for your advice in guiding me to this resolution! Jim From owner-freebsd-questions@freebsd.org Fri Jul 13 19:22:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C948D10496E1 for ; Fri, 13 Jul 2018 19:22:43 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost2.sentex.ca", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC85D748B2 for ; Fri, 13 Jul 2018 19:22:42 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5:0:0:0:11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w6DJMfqs046320 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Jul 2018 15:22:42 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w6DJMdJo098634; Fri, 13 Jul 2018 15:22:39 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] To: Jim Long Cc: freebsd-questions@freebsd.org References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> <20180712214248.GA98578@g5.umpquanet.com> <20180713191050.GA98371@g5.umpquanet.com> From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= xsBNBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAHNHG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT7CwHgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnnOwE0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAcLAXwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: Date: Fri, 13 Jul 2018 15:22:39 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180713191050.GA98371@g5.umpquanet.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.83 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 19:22:44 -0000 On 7/13/2018 3:10 PM, Jim Long wrote: > > It appears that limiting the ARC size did it. The 'zfs send -R' was > able to complete with ARC limited to 50G, and a second run with a 60G > ARC limit also completed. Great! I am glad that helped. Its helpful to me too as I have some systems I am upgrading to RELENG_11 from RELENG_10 soon. I was aware of this particular issue, but was worried perhaps your crashes were related to something else I might run into :) If you ever have a system with a LOT of small files and directories, a handy value to tune / keep an eye on is the mix allocated to metadata vs file data. vfs.zfs.arc_meta_limit. You can tell when doing things like "ls" in a directory takes a LONG time to list files. In my case, I had many directories with 50,000+ files. Also things like 'zfs list -t snapshot' start to take a long time. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-questions@freebsd.org Fri Jul 13 21:50:52 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30E511026CCE for ; Fri, 13 Jul 2018 21:50:52 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (ns.umpquanet.com [209.216.177.146]) (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 BC7B67A769 for ; Fri, 13 Jul 2018 21:50:51 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from g5.umpquanet.com (localhost [127.0.0.1]) by g5.umpquanet.com (8.15.2/8.15.2) with ESMTPS id w6DLnumw026402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Jul 2018 14:49:56 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by g5.umpquanet.com (8.15.2/8.15.2/Submit) id w6DLnuDU026401; Fri, 13 Jul 2018 14:49:56 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: g5.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Fri, 13 Jul 2018 14:49:56 -0700 From: Jim Long To: Mike Tancsa Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] Message-ID: <20180713214956.GA20628@g5.umpquanet.com> References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> <20180712214248.GA98578@g5.umpquanet.com> <20180713191050.GA98371@g5.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 21:50:52 -0000 On Fri, Jul 13, 2018 at 03:22:39PM -0400, Mike Tancsa wrote: > > If you ever have a system with a LOT of small files and directories, a > handy value to tune / keep an eye on is the mix allocated to metadata vs > file data. vfs.zfs.arc_meta_limit. You can tell when doing things like > "ls" in a directory takes a LONG time to list files. In my case, I had > many directories with 50,000+ files. > > Also things like 'zfs list -t snapshot' start to take a long time. I think I already have that symptom on another new server, a backup retention server. It's slow (CPU) and fat (disk). # time zfs list -Hrt snap | wc -l 27365 real 2m47.811s user 0m1.757s sys 0m20.828s Almost three minutes to list all snapshots found. So when that symptomatic slowness appears, is the tweak to *raise* arc_meta_limit ? I don't immediately see how to tell what the arc_meta usage is, and thus see how close it is to the limit. >From that storage server ("electron"): ARC Efficiency: 20.18m Cache Hit Ratio: 91.20% 18.40m Cache Miss Ratio: 8.80% 1.78m Actual Hit Ratio: 91.18% 18.40m Data Demand Efficiency: 87.10% 11.95k CACHE HITS BY CACHE LIST: Anonymously Used: 0.02% 3.15k Most Recently Used: 0.30% 55.95k Most Frequently Used: 99.68% 18.34m Most Recently Used Ghost: 0.00% 0 Most Frequently Used Ghost: 0.00% 0 CACHE HITS BY DATA TYPE: Demand Data: 0.06% 10.41k Prefetch Data: 0.00% 0 Demand Metadata: 99.93% 18.39m Prefetch Metadata: 0.02% 3.15k CACHE MISSES BY DATA TYPE: Demand Data: 0.09% 1.54k Prefetch Data: 0.00% 0 Demand Metadata: 99.73% 1.77m Prefetch Metadata: 0.19% 3.30k # sysctl -a | grep arc | grep ^vfs.zfs vfs.zfs.l2arc_norw: 1 vfs.zfs.l2arc_feed_again: 1 vfs.zfs.l2arc_noprefetch: 1 vfs.zfs.l2arc_feed_min_ms: 200 vfs.zfs.l2arc_feed_secs: 1 vfs.zfs.l2arc_headroom: 2 vfs.zfs.l2arc_write_boost: 8388608 vfs.zfs.l2arc_write_max: 8388608 vfs.zfs.arc_meta_limit: 16432737280 vfs.zfs.arc_free_target: 113124 vfs.zfs.compressed_arc_enabled: 1 vfs.zfs.arc_grow_retry: 60 vfs.zfs.arc_shrink_shift: 7 vfs.zfs.arc_average_blocksize: 8192 vfs.zfs.arc_no_grow_shift: 5 vfs.zfs.arc_min: 8216368640 vfs.zfs.arc_max: 65730949120 # top | head -8 last pid: 943; load averages: 0.14, 0.15, 0.10 up 0+00:30:43 14:42:26 22 processes: 1 running, 21 sleeping Mem: 16M Active, 13M Inact, 1063M Wired, 61G Free ARC: 374M Total, 214M MFU, 63M MRU, 32K Anon, 5614K Header, 91M Other 79M Compressed, 223M Uncompressed, 2.81:1 Ratio Swap: 8192M Total, 8192M Free Thanks again, Mike. Jim From owner-freebsd-questions@freebsd.org Sat Jul 14 04:42:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B71D103B9D8 for ; Sat, 14 Jul 2018 04:42:16 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 3ECD488C42 for ; Sat, 14 Jul 2018 04:42:14 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 124-169-217-176.dyn.iinet.net.au (HELO leader.local) ([124.169.217.176]) by ipmail06.adl6.internode.on.net with ESMTP; 14 Jul 2018 14:07:03 +0930 Subject: Re: ssh on 11.2 To: doug@safeport.com, Doug McIntyre Cc: freebsd-questions@FreeBSD.org References: <20180713135754.GA74801@geeks.org> From: Shane Ambler Message-ID: Date: Sat, 14 Jul 2018 14:07:01 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2018 04:42:16 -0000 On 14/07/2018 02:14, doug wrote: > > On Fri, 13 Jul 2018, Doug McIntyre wrote: > >> On Thu, Jul 12, 2018 at 05:17:25PM -0400, doug wrote: >>> After going to 11.2 from 11.1 authorized_keys2 MUST be renamed to >>> authorized_keys. I spent a bit of time checking permissions and keys >>> before >>> comparing /etc/ssh/sshd_config. This might be implied in some of the >>> Open-ssh >>> errata but not so I got it. A note in UPDATING might be nice, or did >>> I just miss >>> this? >> >> Wow, you had an authorized_keys2 file? That was deprecated in OpenSSH 3.0 >> https://marc.info/?l=openssh-unix-dev&m=100508718416162&w=2 >> >> Your setup must have been copied along for quite some time. >> >> My guess is that OpenSSH finally removed support of it (although I'd >> have guessed the support would have been removed long ago), as part >> of the general cleanup. The changeover happened eons ago, so they >> probably figured nobody had that version any longer. >> > Thanks for the info. Yea one of my keys is from the previous millennium. > But my point remains. So you peaked my curiosity. FreeBSD takes no note > of this as far as I can find. https://www.openssh.com/releasenotes.html > covers OpenSSH 7.7/7.7p1 (2018-04-02)  to openSSH 1.2.3p1 (2000-03-24). > And indeed OpenSSH 5.9/5.9p1 (2011-09-06) notes authorized_keys2 is > deprecated. That's not noted in UPDATING either. Without the comment in > sshd_config it I would still be looking. One of the guys I work with has > never used authorized_keys2 so I would have gotten it eventually from > that. Back in the very eary ssh days I wanted to do a simple change that > was eventually implemented. But from that I know I am not up to reading > the ssh code. This goes back a while, but the last time use of authorized_keys2 was removed in head was in Aug 2017 with the upgrade to OpenSSh 7.5p1 which got merged to stable/11 in Sept 2017 meaning 11.2 doesn't allow it this time, stable/10 still allows its use. Back in Mar 2013 (r248465) FreeBSD replaced the use of authorized_keys2 as the previous removal caught many off guard. So keeping support for this long was a FreeBSD adjustment. Support for the authorized_keys2 filename was and can be set in /etc/sshd_config - You will find releng/8.3 and releng/9.1 both removed authorized_keys2 with 8.4 and 9.2 replacing it. Also of note is that during these changes using authorized_keys was acceptable. AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2 So... our time for saying we weren't warned has long past. -- FreeBSD - the place to B...Securing Domains Shane Ambler From owner-freebsd-questions@freebsd.org Sat Jul 14 05:41:32 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A6B8103E369 for ; Sat, 14 Jul 2018 05:41:32 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by mx1.freebsd.org (Postfix) with ESMTP id B3A3A8A734 for ; Sat, 14 Jul 2018 05:41:31 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 124-169-217-176.dyn.iinet.net.au (HELO leader.local) ([124.169.217.176]) by ipmail07.adl2.internode.on.net with ESMTP; 14 Jul 2018 15:11:23 +0930 Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] To: Mike Tancsa , Jim Long Cc: freebsd-questions@freebsd.org References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> <20180712214248.GA98578@g5.umpquanet.com> <20180713191050.GA98371@g5.umpquanet.com> From: Shane Ambler Message-ID: <4d4726a7-66e0-4f7e-f230-b68e440ad8f6@ShaneWare.Biz> Date: Sat, 14 Jul 2018 15:11:21 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2018 05:41:32 -0000 On 14/07/2018 04:52, Mike Tancsa wrote: > On 7/13/2018 3:10 PM, Jim Long wrote: >> >> It appears that limiting the ARC size did it. The 'zfs send -R' was >> able to complete with ARC limited to 50G, and a second run with a 60G >> ARC limit also completed. > > Great! I am glad that helped. Its helpful to me too as I have some > systems I am upgrading to RELENG_11 from RELENG_10 soon. I was aware of > this particular issue, but was worried perhaps your crashes were related > to something else I might run into :) To add my 2c - I recently realised that the arc_max defaults allow all ram to be allocated as wired, which is bad. arc_max should not be set higher than physical ram - max_wired - buffer It is time I put this into a bug report - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229764 -- FreeBSD - the place to B...Storing Data Shane Ambler From owner-freebsd-questions@freebsd.org Sat Jul 14 13:29:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4131102AE8E for ; Sat, 14 Jul 2018 13:29:56 +0000 (UTC) (envelope-from darren.henderson@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEA279C4B for ; Sat, 14 Jul 2018 13:29:56 +0000 (UTC) (envelope-from darren.henderson@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id t79-v6so18536838qke.4 for ; Sat, 14 Jul 2018 06:29:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=8/3rgm0UekQppwAvzgbvnLK9fTZQ6PYir5p/zyk42xQ=; b=cuiP6Sf+HD2s4GEvhET31hOmD0AK5MKRFMB8wm42PScrG8QjzHBidHRpAfb3JcA7OL Hel82reviNvIRvsxqVdi+OuJS5HAi1VDnhfExp8LbBS9K9b/CSWG70WGDKKjaA0ufnoh w0UHUHuZxO8VizfxbQCcKheqE5cWHsCN/HnG/Qk1kKa5Eo/PmoQzvZ4TuHHkSiXt1W1w 8EPriCsDqLrFvseGBeBZWhGLPTvtyCY4Ust/itEgprIj0VWWz2uAz5+QcOP5iicIKgaj ygUTV6JltbLIVit6RaFkRN+szNi4b/y2cghGGnsgu0M34Vf/kE5g0RTviftxWPUNzYqk X7lQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=8/3rgm0UekQppwAvzgbvnLK9fTZQ6PYir5p/zyk42xQ=; b=ucLe1vSnfm6fTX+KjQNiVOOSf+zsMcIP1lsammR0t/ZZRTVWfFQIgS6hxiZ+6vxK5n IF6AurZru5O8hCM0J4i/q28HfrdqQi07Lmd1pIfVEStZQipUo4qX+ZGgOUcPkTlltYxe 12Ad36LkybRp7+Bxz3MetN27WLsWudfIa/s+m8dW7wZJHi7qXgZVh0vnOnTpUzkAgs4/ yOgJJP9aHpxADeL+yJa0En9UdMefRRDz4P6HdJ0WqdxlzJtb0zjBaGhKxBC8Tw/I1Lca Ta5wWit07PFKCWUmxgEsRQoq8N/UFc4AO3sNg3pe7N6qKo3rdm2nzbq6JY2iHJCO/RH2 7naA== X-Gm-Message-State: AOUpUlEpR30dJz/7XoewMto+EDcv5NKxvODqEDV9gIEr0aQ00kAIpclK EQgboSrvSOWP3KK9TIQerd2fGOSt X-Google-Smtp-Source: AAOMgpeaEJU/BGivjJc9ugDiwBHaxiTxjJb35iPakA11cb3q4KOmUQHzRgicesTjiiQlocytGYWfag== X-Received: by 2002:a37:5b83:: with SMTP id p125-v6mr8704212qkb.196.1531574995091; Sat, 14 Jul 2018 06:29:55 -0700 (PDT) Received: from olmec.nighttide.net ([68.238.56.219]) by smtp.gmail.com with ESMTPSA id f3-v6sm24408331qtf.61.2018.07.14.06.29.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Jul 2018 06:29:54 -0700 (PDT) Subject: Re: [commercial] sendmail setup request To: freebsd-questions@freebsd.org References: From: Darren Henderson Openpgp: preference=signencrypt Autocrypt: addr=darren.henderson@gmail.com; prefer-encrypt=mutual; keydata= xsFNBFiou5oBEACruBRieOQ4IDz0ybQeHm+GSA04ckSsHsFsC5fIEMJiRf5hW5XQ8aMU78VX Khp9MFB769a2K5oz45vlfnhRYZQ/jK5ABq7yC3IzzyLhknYXtAPnCBjvHMa811O0/ZHwVWSk JPOZxDTFJzFd+SNeHVXz03M6UfEJ963hj78oF3bcR8ou3+GScGcSGeHdf1UYsPDOus1uUIo4 8pjIp0P9mCy+OffUIGm06lQCeq/w0YTXJ1V4wBBm83J5Lbdrwzb1KUHJqCs/QovpduIgjav0 bwPQjqzNi20tVlZwwnQasJ06anWQGC/pQSxwC8/EjeM8xtun0pXmCcEaVZf5Cul26p9dMe5W WNzi+5edIirXvdnFscoROiT7QPU5IRj+Mvq2oOQ0tN4gnAnlhInS31yilcpP6RelA1de+1Wk JsIJ8dgG0pmEYyMNByrumulQ2zZ8yAvN8LYiVD5WVfrEsnrUvifMi0/kBAJmBvQNtNk62hP9 O0jIfnERtcnzAdNZbCIR8C42ZbJ50vZhUkWrvmYja6pDeFync4jd9c/RT8to6AgK4NbMN9K+ Rkp85v5PTeIdjfRTjFXOV0HDGi/SmyfgXSpfGsTkAzZvZO+3TacAc3yWnBVL7zXdgq3dIgII tShoKronNeFj9Qzygsvo0NF3l6nadS391eDP9SQK29Ry8OTZIwARAQABzS1EYXJyZW4gSGVu ZGVyc29uIDxkYXJyZW4uaGVuZGVyc29uQGdtYWlsLmNvbT7CwY4EEwEIADgWIQRRbTdstlJ2 L0k6UCPYhvzxDD9nTQUCWKi7mgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRDYhvzx DD9nTZXYD/4h/rE+qayd/3NHHDdhOt4IKb+a+/xrIdLoG+0S1fWslHYxdej9hBH9ISBEGxfQ 1Wo6FMnvTYufQHYfFdJKVXky7z4SsEsiO1pRP/v9BNHD264YHHd9zuG+j4SGWFJKnj76PX8o KoeIsgYXzvf/5qo+/vIX8Qrm73VTOQ9jCucXehIIjfTagis1PDn12jTKWlEV664ErUgG3KY2 Ljq0039HW1ThkY10VQtkWcQ9jqLipbYpnrL11eisC5FwMh0NHy/gi0dwlG1HikzUFkRfnYfT GbWhECGttYhgyBYjjZLyJc4YAYTynls5NfuYHQGGQKp05laUnYzf6WLHxPb8IsMrUzOLzXRd DOZmpk20q+4qz9ZLQsqs0LqfVer7bj9RldfqvfJJgcKsJ22hAdCF62K+bjykbXP1VC7KlYcP irNsPraHH5HPHeO3qm7vZ5JpXmqcrmsaCtpj2e8qNbt8GnbfkIf/ysGqcH0IOPtgO7AewLVd tO1BcXr5fPaznY5RXLJUerMBTaFma7nkAsAdvyi4yp2D5YZvZ7jvoNj/uP2597Lx+Lm8p/Hw L/D3m+BP79oBwUj+Eh3VRBAJn0DkBxuxHQzqdrBCslpRzQT7GkDML3KpEHN3PJR9r+1+0exD hES3YcgMrvnwMcXYgh5lCKXK7MvLFxS1EfmBkxMaBlmvZc7BTQRYqLuaARAA5Yjyml76KUkN iitvqPohdIOkFsYuT0cM6UTFSXGIPzlaBMs7LMYdCAZhtiKHSsuWlWrbdhuFZEyXMJYzBXOH hfs4nDa98UGfnsXJXsq5LVVr3E4Jjm0ZsAO7yHbzUcn/zLhZGIQTV8EgY2yXSOMQVp98y9gA AHT10gOemlVD/KW3xOAJFFWUYrYePeyu89D4LWWjrJjF4Xn0Pj+1gprT6mgiWDXTja526ify mgx0BSZo8dO37hacbRPHPIePU50+vfdBPkaAL3u7+sxf/44IfhLGoQrWfCD0+6YhwPmMzVGG q9oldrbXH8wKhRjfR4V3C+S7Eu6JCMsK90g46Oag3uYERGR01x5hiSlWdZefYgM0aGtOUQSQ 9AFrvoUTP7MpT60ETToO4cqC4VNeTYM+yGXlGS6FqfykrR/cOMVYbaKwF6jLOpsZiocqHP4f mKWeLhTVkvlb/8vSN5fFGn03eKEMY2AwFZp//wUrT0Jm/ftFSRySJQDOUphZtUTUtuEXfeXF R4r/bRJdRNTClpjVkCDQJQ7BHZqYJYyIpxPFC+ldO/QiqCEkKTzGswMUzfe7rT/NvFUy1bPF +bMfRi1sHzl5ZwYEI2HfdXElTPAgvoVrXGPeeYwqPb7OCgvp68tSwHvOaYWzjcYAq/+5NgAE VvJtqOnb2Ik5AIH5ji828asAEQEAAcLBdgQYAQgAIBYhBFFtN2y2UnYvSTpQI9iG/PEMP2dN BQJYqLuaAhsMAAoJENiG/PEMP2dNcTAP/i1x1jl3pOhoHnEI3gA5EXpF+e2AefL3KRPDgVwE C1LdLBNLHIZW/0HuL/tikbyzgQE8MA/GciwwMn35aM2tzWQbeYo587kN3HXi4mZ8t8+PnwwG gt1L21d0RRdxSABWcDQBYE+2/Cxa8MW5ifDRKJJc6hmLXGWQ/b3jQ20Z20PTgQsmRg1kJ7Sa rn+HZYGNQrAyTcwC3EDtNDTccJE4fX9jM18jU9DQPGlmutloP9HJXc8SHFcnjb82XZ4zPZ1X vGoOgs9pCyKRDIFkXEGsghbTN6LPEThQK+UTV+tJ/e/9PSTqFxDCTLGTiqkIbFHB3icmdnGp 4wRWa/pitHAcEiiYwUKnXHsdIosW9rmK/ZKUh0b6v+GmJQMga0tJsZxpcWS9FUZxhDs/0Hdz bVOe/e4ae4xpHA3wndUcDtzGywoSxEeAYx0eS+3+cVwM6JIXP6yy5d6hZ/K8ipr3adQ46/3r E3hQG4CxHTiR2Rd80A8gpyXL15fL+dNfd0On2QfNT8ztu2zYlbp1MbsGkYWKX+Kfa8c2XZ/h E0B1YVch2oSLiBm9FcBHkpxmUkmyY2XxElZiqXDmGi7KSiJtm7LONFePRoQhQKrAN8uZyFt7 NHOQiI3XcTLWXt6wqbzuKxIl+FW90JOE4FzJQiR9Hjj3gpVmobsdb3fTiAYGNByygDSK Message-ID: <4e88202e-9872-4f10-bf84-5904dc538668@gmail.com> Date: Sat, 14 Jul 2018 09:29:52 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2018 13:29:56 -0000 On 07/08/2018 04:52, Mayuresh Kathe wrote: > hi, > > i own a domain (kathe.in) for which email services are provided by the > domain registrar itself. email services include imap, smtp and webmail. > > the problem is that i lean more towards using mailx under bsd and at > the same time also wish to have my mails stored online (or rather > non-locally). This becomes much simpler if you are not stuck on mailx. Alpine and mutt are both text based email clients that will imap. You could even run those on a local windows machine (though it may require cygwin or the windows built in unix stuff) if you wanted. If you wanted remote access to the client via the internet you could set up a vps with someone like vultr who has a $2.50/month host (if you pick their NJ data center) and run them there. If you're using imap you cold do it in both places if you wanted. From owner-freebsd-questions@freebsd.org Sat Jul 14 14:46:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B62C1102DB99 for ; Sat, 14 Jul 2018 14:46:45 +0000 (UTC) (envelope-from johnl@iecc.com) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gal.iecc.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4400A7C53D for ; Sat, 14 Jul 2018 14:46:45 +0000 (UTC) (envelope-from johnl@iecc.com) Received: (qmail 44017 invoked from network); 14 Jul 2018 14:46:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=abec.5b4a0cd3.k1807; bh=5jPOLbH96yRbeIraqqUlITA4V/W3Fx3JBY+43gyR24U=; b=zQCqBFoRmF1W2UgLBTzUuWXm5u39WCtV6PIO/uTd3oxCjZchfU7BcfBNIWYYY0ybK3tpT/4q8138q32d30urID+X0bz4k1SF48oIH7fivWseveaCDPnTIC1BrGuCqaUq1xaY/QpBuZ2Po6+q04zM4fOQhZJVtFuUBRwsvu23cI3dWcnyQpvet8wsbxyuEcTmdK/KULQwLZkrBmpS3msEHOkOpqyhSyhxYx/d9RGsqXfDhXDBvss6pcdUw4l3S/4k Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 14 Jul 2018 14:46:43 -0000 Received: by ary.qy (Postfix, from userid 501) id 7456C20024BAA4; Sat, 14 Jul 2018 10:46:43 -0400 (EDT) Date: 14 Jul 2018 10:46:43 -0400 Message-Id: <20180714144643.7456C20024BAA4@ary.qy> From: "John Levine" To: freebsd-questions@freebsd.org Cc: darren.henderson@gmail.com Subject: Re: [commercial] sendmail setup request In-Reply-To: <4e88202e-9872-4f10-bf84-5904dc538668@gmail.com> Organization: Taughannock Networks X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2018 14:46:45 -0000 In article <4e88202e-9872-4f10-bf84-5904dc538668@gmail.com> you write: >This becomes much simpler if you are not stuck on mailx. Alpine and mutt >are both text based email clients that will imap. > >You could even run those on a local windows machine (though it may >require cygwin or the windows built in unix stuff) if you wanted. There's a Windows version of Alpine. It works pretty well. -- Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly From owner-freebsd-questions@freebsd.org Sat Jul 14 22:40:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A6681040F7E for ; Sat, 14 Jul 2018 22:40:37 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward102p.mail.yandex.net (forward102p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A106A8C21A for ; Sat, 14 Jul 2018 22:40:36 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from mxback11g.mail.yandex.net (mxback11g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:90]) by forward102p.mail.yandex.net (Yandex) with ESMTP id 59437430524F for ; Sun, 15 Jul 2018 01:40:33 +0300 (MSK) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [2a02:6b8:0:801::ab]) by mxback11g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id kreHr5lFQm-eXt0kXS7; Sun, 15 Jul 2018 01:40:33 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531608033; bh=WF1w2HGOTMMpjFU8jFhx7+gWnfl1O4oba0vDd4qXX3I=; h=Date:From:To:Subject:Message-ID; b=lsdlXdM48tlO6b/6B62JUQQGzLG+psVT5pHTFS/OHu8hvYU8WWNlEWjEXsc70k6rU NzHsA+EYyH41yKj5pOvvqPqJEKlVusZ5Hg52vzOSiTEOpolPIj7e7mTjEAG3w7dikh rIDAnaxktl7eGoxx+zzvY080R1LPPOxMvrrMYKGs= Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id HN6WOcQTaA-eW6ux15t; Sun, 15 Jul 2018 01:40:32 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531608032; bh=WF1w2HGOTMMpjFU8jFhx7+gWnfl1O4oba0vDd4qXX3I=; h=Date:From:To:Subject:Message-ID; b=gSua7xM7koaMu5G3ksyPcJ9fc0bP7EVcTaWgGPaEnrXLMn3k95iL+l2d9+P68bcqh A1uz0QpqbmZtCQXV5doXRPprSdidRABRnmA6Hgy6Y0uadME80c2u59Be1Eavay11Re c/1cppmPyDK9gk9RYM+6dZlxPygyGtQMS9iBQ7c4= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.com Date: Sat, 14 Jul 2018 18:40:29 -0400 From: Ajtim To: FreeBSD Questions Subject: webcamd Message-ID: <20180714184029.3231e83e@yandex.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2018 22:40:37 -0000 Hi! My system is FreeBSD 11.2-RELEASE (amd64) and it is installed on iMac 11,1 which has a built-in iSight video camera. It worked and it works after todays update too. After update I have video0 and video1 and both work the same. But my problem is sound in mpv player. I start with mpv tv://v42: device=/dev/video0 [tv] Selected driver: v4l2 [tv] name: Video 4 Linux 2 input [tv] your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead. [tv] Selected device: Built-in iSight: Built-in iSigh [tv] Capabilities: video capture read/write streaming [tv] supported norms: [tv] inputs: 0 = Camera 1; [tv] Current input: 0 [tv] Current format: YUYV [tv] tv.c: norm_from_string(pal): Bogus norm parameter, setting default. [tv] ioctl enum norm failed: Invalid argument [tv] Error: Cannot set norm! [tv] Selected input hasn't got a tuner! [tv] ioctl set mute failed: Invalid argument (+) Video --vid=1 (rawvideo 640x480 30.000fps) VO: [gpu] 640x480 yuv420p I had the same problem with sound on VLC player. But if I use: mencoder tv:// -tvdriver=v4l2:width=420:height=340:device=/dev/video0:forceaudio:adevice=/dev/dsp1 -ovc lavc -oac mp3lame -lameopts cbr:br=64:mode=3 -o webcam.avimencoder tv:// -tv driver=v4l2:width=420:height=340:device=/dev/video0:forceaudio:adevice=/dev/dsp1 -ovc lavc -oac mp3lame -lameopts cbr:br=64:mode=3 -o webcam2.avidevice=/dev/video0:forceaudio:adevice=/dev/dsp1 -ovc lavc -oac mp3lame -lameopts cbr:br=64:mode=3 -o webcam.avi It save webcam.avi with sound. Any idea how to get sound on mpv player, please? Thank you. SK