From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 05:27:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AFBB49BC for ; Sun, 4 Aug 2013 05:27:29 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6B5942D6E for ; Sun, 4 Aug 2013 05:27:29 +0000 (UTC) Received: by mail-vb0-f46.google.com with SMTP id p13so1891743vbe.33 for ; Sat, 03 Aug 2013 22:27:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=TJjKc7dhiFKEwe5aM+LbsrNIgjgGeXcE/wbqKlyjkog=; b=vqUMzPzLzCoGPJQGfWbAvVmhbGbfirK0e46XeVPpiRSZ408HWFe1XncqLsiFvt67e2 FVdTN6Evd+dUN9hM2h079EpaBlfHflZk74v+GQiZfuOelpCRMJ105mP8MlvcTsgrb+of sDF/ttqNhUD+5BQOcG/GhquatJM8cUREQqtvBu7XLZr8OkyEKn/j0K7RBx9hwGF5gXMV zg05z4sedYfIeCbUu5/+wVqu1Uaf1HflnCFKgWHWqSYR4Z4tMaI3g9tPsCmaAX10dqEu 5EA2VuFRjjm2Qdp8x3fSh/dYpgkVYcAPqMqwBYTXuJ9hO9Uo2/QBCB5LrwW7kpvsZXs+ H9Uw== MIME-Version: 1.0 X-Received: by 10.52.36.236 with SMTP id t12mr3511697vdj.95.1375594047781; Sat, 03 Aug 2013 22:27:27 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Sat, 3 Aug 2013 22:27:27 -0700 (PDT) In-Reply-To: References: <20130802102100.GA11138@eris.bzerk.org> Date: Sun, 4 Aug 2013 09:27:27 +0400 Message-ID: Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 From: Pavel Timofeev Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 05:27:29 -0000 Same thing on RELENG/9.2 2013/8/3 Pavel Timofeev : > 2013/8/2 Ruben de Groot : >> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>> We don't use IPv6 in our company. >>> >>> 2013/7/31 Pavel Timofeev : >>> > I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>> > server, but not A (IPv4). >>> > Any ideas? >>> > >>> > 2013/7/31 Pavel Timofeev : >>> >> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>> >> ip address. >>> >> >>> >> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>> >> 53417+ AAAA? xxx.ru. (24) >>> >> [13/98] >>> >> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>> >> 53417* 0/1/0 (75) >>> >> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>> >> 53418+ A? xxx.ru. (24) >> >> Here it is definately asking an A record. > > And? It's not A record of mx server. > >>> >> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>> >> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>> >> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>> >> (136) >> >> And here is the reply. The quetion is more why is it repeating the same >> query (below) over and over. > > Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru > >> >> Ruben >> >>> >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>> >> 53419+ MX? xxx.ru. (24) >>> >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>> >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>> >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>> >> 53420+ AAAA? kalmar.xxx.ru. (31) >>> >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>> >> 53420* 0/1/0 (82) >>> >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>> >> 53421+ AAAA? kalmar.xxx.ru. (31) >>> >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>> >> 53421* 0/1/0 (82) >>> >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>> >> 53422+ AAAA? kalmar. (24) >>> >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>> >> 53422 ServFail 0/0/0 (24) >>> >> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>> >> 53422+ AAAA? kalmar. (24) >>> >> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>> >> 53422 ServFail 0/0/0 (24) >>> >> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>> >> 53423+ AAAA? kalmar.xxx.ru. (31) >>> >> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>> >> 53423* 0/1/0 (82) >>> >> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>> >> 53424+ AAAA? kalmar. (24) >>> >> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>> >> 53424 ServFail 0/0/0 (24) >>> >> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>> >> 53424+ AAAA? kalmar. (24) >>> >> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>> >> 53424 ServFail 0/0/0 (24) >>> >> >>> >> How to force it to use IPv4? >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 06:34:46 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CFF073DE for ; Sun, 4 Aug 2013 06:34:46 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by mx1.freebsd.org (Postfix) with ESMTP id A5830202F for ; Sun, 4 Aug 2013 06:34:46 +0000 (UTC) Received: from fed1rmimpo109 ([68.230.241.158]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130804063016.GZPO3892.fed1rmfepo101.cox.net@fed1rmimpo109> for ; Sun, 4 Aug 2013 02:30:16 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo109 with cox id 8WWF1m00B2oShb201WWFYk; Sun, 04 Aug 2013 02:30:15 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.51FDF4F7.00A4,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=Z5Yy6gtA c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=FsoGBpxP2c0A:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=F-_XmPgKG-cA:10 a=bxBBvLhrdZszU3Xi2tgA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r73NJ4T3064075 for ; Sat, 3 Aug 2013 23:19:04 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51FDF5E5.4070606@reynoldsnet.org> Date: Sat, 03 Aug 2013 23:34:13 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: stable@freebsd.org Subject: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- Firefox SQLite locking issue Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 06:34:47 -0000 Hello all, I've been recently building up a new Haswell box and after overcoming several problems have gotten things to mostly work. But I got stuck when trying to use Firefox 22. The bookmarks editor/container was always coming up empty and I was not able to import bookmarks I had from a saved profile. Additionally, the back/forward arrow buttons would not work. They were always grayed out making navigation impossible and thus rendering the browser fairly useless. I tried linux-firefox and the SAME problems existed. This led me to believe it wasn't a port problem. I saw mention after searching and searching for an answer of somebody who moved their account's $HOME dir from an NFS mounted volume to a local disk and some other problem they had went away. I thought "oh, this has got to be a locking problem." So, I tried this and Firefox 22 works perfectly on local disk! It's got to be the SQLite that FF22 uses for the "places.sqlite" and other SQL databases (bookmarks, etc.) and a locking issue since I have my $HOME directory mounted over NFS. My setup: NFS server: FreeBSD 8.3-STABLE as of Jan 2013 nfs_server_enable="YES" nfs_server_flags="-u -t -n 4" nfsv4_server_enable="NO" rpc_lockd_enable="YES" rpc_statd_enable="YES" I am not knowingly running any other version of NFS server/client other than what any user would get by "default" (supposing NFSv3). NFS client: FreeBSD 9.2-BETA2 (I've been tracking sources and updating through buildworld, etc.) Just using normal "nfs" options when mounting the homedir directory on the client. So, questions: - I haven't upgraded the server to 9.x. I plan to do that along with new faster hardware, but since I have multiple "users" in the house, I have to have some dedicated time to work, research, plan, and pray things don't go wrong before I black-out the gateway/firewall/nat/etc box for all these "users" :). When I upgrade so that server is relatively equal to client (at least same 9.x version) should I see locking problems like the above? i.e. somebody else on this list HAS to be using NFS to serve up home directories. Do you see locking problems like that mentioned above? - I saw many posts talking about moving things to NFSv4 to resolve locking problems. If I was to upgrade the server to the latest 8.x-STABLE kernel/world should this interact with a 9.x world properly using NFSv4? Is the NFSv4 server in 8.x-STABLE "good enough" in this regard? - Without having to upgrade either my server or change to NFSv4 across the board, what other options might there be? The older hardware for this machine was running relatively the same kernel as my server--8.3-STABLE and I DID NOT SEE this behavior--which l leads me to believe that it is an 8.x <-> 9.x issue. Is there anybody out there besides me mixing these versions or am I the only person the planet that hasn't upgraded to 9-stable? :) - I see bits and pieces of documentation talking about how to use NFSv4, but I didn't see anything in the Handbook or out there in the wild that was a guide on how to migrate one's setup/config files. If there are good howto's or other articles on this please share! Thanks in advance for all answers. I appreciate the dedication that you all have! -Jr From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 10:32:30 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3DC5CD65 for ; Sun, 4 Aug 2013 10:32:30 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0183D2494 for ; Sun, 4 Aug 2013 10:32:29 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqMEAPgs/lGDaFve/2dsb2JhbABSCIM7UIMQvAWBMHSCJAEBAQMBAQEBIAQnIAsFFhgCAg0EFQIpAQkmBggHBAEcBIdpBgylUpBagSiNHxYEDXc0BwqCXIEnA5UZg3GQJYFegVUgMnwHFyI X-IronPort-AV: E=Sophos;i="4.89,812,1367985600"; d="scan'208";a="43475159" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 04 Aug 2013 06:32:22 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id C969AB3F43; Sun, 4 Aug 2013 06:32:22 -0400 (EDT) Date: Sun, 4 Aug 2013 06:32:22 -0400 (EDT) From: Rick Macklem To: John Reynolds Message-ID: <1072840488.5640439.1375612342793.JavaMail.root@uoguelph.ca> In-Reply-To: <51FDF5E5.4070606@reynoldsnet.org> Subject: Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- Firefox SQLite locking issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 10:32:30 -0000 John Reynolds wrote: > Hello all, > > I've been recently building up a new Haswell box and after overcoming > several problems have gotten things to mostly work. But I got stuck > when > trying to use Firefox 22. The bookmarks editor/container was always > coming up empty and I was not able to import bookmarks I had from a > saved profile. Additionally, the back/forward arrow buttons would not > work. They were always grayed out making navigation impossible and > thus > rendering the browser fairly useless. > > I tried linux-firefox and the SAME problems existed. This led me to > believe it wasn't a port problem. I saw mention after searching and > searching for an answer of somebody who moved their account's $HOME > dir > from an NFS mounted volume to a local disk and some other problem > they > had went away. I thought "oh, this has got to be a locking problem." > So, > I tried this and Firefox 22 works perfectly on local disk! It's got > to > be the SQLite that FF22 uses for the "places.sqlite" and other SQL > databases (bookmarks, etc.) and a locking issue since I have my $HOME > directory mounted over NFS. > > My setup: > > NFS server: FreeBSD 8.3-STABLE as of Jan 2013 > nfs_server_enable="YES" > nfs_server_flags="-u -t -n 4" > nfsv4_server_enable="NO" > rpc_lockd_enable="YES" > rpc_statd_enable="YES" > > I am not knowingly running any other version of NFS server/client > other > than what any user would get by "default" (supposing NFSv3). > > NFS client: FreeBSD 9.2-BETA2 (I've been tracking sources and > updating > through buildworld, etc.) > Just using normal "nfs" options when mounting the homedir directory > on > the client. > > So, questions: > - I haven't upgraded the server to 9.x. I plan to do that along > with > new faster hardware, but since I have multiple "users" in the house, > I > have to have some dedicated time to work, research, plan, and pray > things don't go wrong before I black-out the gateway/firewall/nat/etc > box for all these "users" :). When I upgrade so that server is > relatively equal to client (at least same 9.x version) should I see > locking problems like the above? i.e. somebody else on this list HAS > to > be using NFS to serve up home directories. Do you see locking > problems > like that mentioned above? > - I saw many posts talking about moving things to NFSv4 to resolve > locking problems. If I was to upgrade the server to the latest > 8.x-STABLE kernel/world should this interact with a 9.x world > properly > using NFSv4? Is the NFSv4 server in 8.x-STABLE "good enough" in this > regard? Yes, I believe that a current stable/8.x NFSv4 server will work ok. > - Without having to upgrade either my server or change to NFSv4 > across > the board, what other options might there be? Unless multiple clients share the same files concurrently that must be locked (not likely for home dir stuff), the "nolockd" mount option on the client will avoid having to use rpc.lockd and rpc.statd. (With this mount option, the locks are visible to all processes in the client, but not to other clients accessing the same file.) > The older hardware for > this machine was running relatively the same kernel as my > server--8.3-STABLE and I DID NOT SEE this behavior--which l leads me > to > believe that it is an 8.x <-> 9.x issue. Is there anybody out there > besides me mixing these versions or am I the only person the planet > that > hasn't upgraded to 9-stable? :) > - I see bits and pieces of documentation talking about how to use > NFSv4, but I didn't see anything in the Handbook or out there in the > wild that was a guide on how to migrate one's setup/config files. If > there are good howto's or other articles on this please share! > About all you need to do is add a "V4: ..." line to your /etc/exports and then set nfsv4_server_enable="YES" in /etc/rc.conf and reboot. On the client mount, you need to add "nfsv4" as a mount option. > Thanks in advance for all answers. I appreciate the dedication that > you > all have! > > -Jr > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 15:57:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B45599B4 for ; Sun, 4 Aug 2013 15:57:09 +0000 (UTC) (envelope-from zkolic@sbb.rs) Received: from smtp9.sbb.rs (smtp9.sbb.rs [89.216.2.41]) by mx1.freebsd.org (Postfix) with ESMTP id 273DF2D68 for ; Sun, 4 Aug 2013 15:57:08 +0000 (UTC) Received: from knossos (cable-178-148-104-205.dynamic.sbb.rs [178.148.104.205]) by smtp9.sbb.rs (8.14.0/8.14.0) with ESMTP id r74Fb2TR008429 for ; Sun, 4 Aug 2013 17:37:07 +0200 Received: from localhost (1000@localhost [local]); by knossos (OpenSMTPD) with ESMTPA id a993a8ae; for ; Sun, 4 Aug 2013 17:36:34 +0200 (CEST) User-Agent: OpenSMTPD enqueuer (Demoosh) Date: Sun, 4 Aug 2013 17:36:34 +0200 From: Zoran Kolic To: freebsd-stable@freebsd.org Subject: binary upgrade from 9.1 to 9.2 Message-ID: <20130804153634.GA12761@knossos> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 15:57:09 -0000 I assume freebsd-update, mergemaster and pkgng would do the job. Is there any change for upcoming release? Especially for kms nodes, which needed to be compiled separately to have x working. Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 16:54:08 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F0BD6C24 for ; Sun, 4 Aug 2013 16:54:07 +0000 (UTC) (envelope-from kdunn@acm.org) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8F7A52F8E for ; Sun, 4 Aug 2013 16:54:07 +0000 (UTC) Received: from fly.hiwaay.net (localhost.localdomain [127.0.0.1]) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id r74Gk2jh011883 for ; Sun, 4 Aug 2013 11:46:02 -0500 Received: from localhost (kldunn@localhost) by fly.hiwaay.net (8.13.8/8.13.8/fly-submit) with ESMTP id r74Gk2ZB011880 for ; Sun, 4 Aug 2013 11:46:02 -0500 X-Authentication-Warning: fly.hiwaay.net: kldunn owned process doing -bs Date: Sun, 4 Aug 2013 11:46:02 -0500 (CDT) From: Karl Dunn X-X-Sender: kldunn@fly.hiwaay.net To: freebsd-stable@freebsd.org Subject: root umask and building ports In-Reply-To: Message-ID: References: User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Karl Dunn List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 16:54:08 -0000 I discovered the hard way, when building ImageMagick-6.7.9.4 on 9.1-RELEASE, that having root's umask set to 077 is a mistake. Lots of directories and some files, in ImageMagick itself and some of the dependent ports, had other and group perms set to ---. No good. Hard to fix after the fact: I tracked down all the problems with four-liner command that used find, ls, and grep; then I fixed them "by hand", more or less. Made a lot of work for myself, just to get mogrify to run in a script that generates per-user web activity bar graphs once a week. This is probably not a new discovery to most. I have been using FreeBSD for a long time (about 15 years), but I still regard myself as a newbie. Lesson learned. Leave root umask set to 022. (Maybe ports should be written to not depend on root's umask?) Karl Dunn kdunn@acm.org On Sun, 4 Aug 2013, freebsd-stable-request@freebsd.org wrote: > Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-request@freebsd.org > > You can reach the person managing the list at > freebsd-stable-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." > > > Today's Topics: > > 1. Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 > (Pavel Timofeev) > 2. Re: ZFS: can't read MOS of pool (Andriy Gapon) > 3. Re: /usr/bin/ld: warning: creating a DT_TEXTREL in a shared > object after freebsd-update (Fabian Wenk) > 4. Re: Problem with zfsloader on 9.2-BETA2 (Andriy Gapon) > 5. Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 > (Pavel Timofeev) > 6. NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- > Firefox SQLite locking issue (John Reynolds) > 7. Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 > -- Firefox SQLite locking issue (Rick Macklem) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 3 Aug 2013 17:41:58 +0400 > From: Pavel Timofeev > To: Ruben de Groot > Cc: freebsd-stable@freebsd.org > Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > 2013/8/2 Ruben de Groot : >> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>> We don't use IPv6 in our company. >>> >>> 2013/7/31 Pavel Timofeev : >>>> I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>> server, but not A (IPv4). >>>> Any ideas? >>>> >>>> 2013/7/31 Pavel Timofeev : >>>>> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>>> ip address. >>>>> >>>>> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>>> 53417+ AAAA? xxx.ru. (24) >>>>> [13/98] >>>>> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>>> 53417* 0/1/0 (75) >>>>> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>>> 53418+ A? xxx.ru. (24) >> >> Here it is definately asking an A record. > > And? It's not A record of mx server. > >>>>> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>>> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>>> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>>> (136) >> >> And here is the reply. The quetion is more why is it repeating the same >> query (below) over and over. > > Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru > >> >> Ruben >> >>>>> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>>> 53419+ MX? xxx.ru. (24) >>>>> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>>> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>>> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>>> 53420+ AAAA? kalmar.xxx.ru. (31) >>>>> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>>> 53420* 0/1/0 (82) >>>>> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>>> 53421+ AAAA? kalmar.xxx.ru. (31) >>>>> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>>> 53421* 0/1/0 (82) >>>>> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>>> 53422+ AAAA? kalmar. (24) >>>>> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>>> 53422 ServFail 0/0/0 (24) >>>>> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>>> 53422+ AAAA? kalmar. (24) >>>>> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>>> 53422 ServFail 0/0/0 (24) >>>>> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>>> 53423+ AAAA? kalmar.xxx.ru. (31) >>>>> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>>> 53423* 0/1/0 (82) >>>>> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>>> 53424+ AAAA? kalmar. (24) >>>>> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>>> 53424 ServFail 0/0/0 (24) >>>>> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>>> 53424+ AAAA? kalmar. (24) >>>>> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>>> 53424 ServFail 0/0/0 (24) >>>>> >>>>> How to force it to use IPv4? >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > ------------------------------ > > Message: 2 > Date: Sat, 03 Aug 2013 21:59:15 +0300 > From: Andriy Gapon > To: ?ukasz W?sikowski > Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org > Subject: Re: ZFS: can't read MOS of pool > Message-ID: <51FD5303.30507@FreeBSD.org> > Content-Type: text/plain; charset=UTF-8 > > on 02/08/2013 17:56 ?ukasz W?sikowski said the following: >> This tools doesn't compile on 9.2-BETA2 r253884 > > There are fixes for this in head that haven't been MFC-ed yet: > http://svnweb.freebsd.org/base/head/tools/tools/zfsboottest/zfsboottest.c?view=patch&r1=253067&r2=253066&pathrev=253067 > http://svnweb.freebsd.org/base/head/tools/tools/zfsboottest/zfsboottest.sh?view=patch&r1=253068&r2=253067&pathrev=253068 > http://svnweb.freebsd.org/base/head/tools/tools/zfsboottest/Makefile?view=patch&r1=253605&r2=253604&pathrev=253605 > > It would be very interesting to see what zfsboottest says about the pool. > Especially interesting it would be to see the error in a debugger. > > -- > Andriy Gapon > > > ------------------------------ > > Message: 3 > Date: Sat, 03 Aug 2013 21:12:03 +0200 > From: Fabian Wenk > To: freebsd-stable@freebsd.org > Subject: Re: /usr/bin/ld: warning: creating a DT_TEXTREL in a shared > object after freebsd-update > Message-ID: <51FD5603.7040408@wenks.ch> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello Alex > > On 31.07.2013 10:45, Alex Povolotsky wrote: >> Hello >> >> I've updated (with freebsd-update) an old 7.3 to 9.1-RELEASE and now I >> cannot build at least one port. > >> ===> Compilation failed unexpectedly. >> >> Googling did not yield anything useful. What should I check and fix? > > Did you install the compat7x package for 9.1? If not, then > download it from [1] (for an amd64 system) and use the following > command to install: > > pkg_add compat7x-amd64-7.3.703000.201008_1.tbz > > [1] > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/misc/compat7x-amd64-7.3.703000.201008_1.tbz > > Then you should also rebuild all installed Ports, as it is noted > in the documentation. > > > bye > Fabian > > > ------------------------------ > > Message: 4 > Date: Sat, 03 Aug 2013 22:16:25 +0300 > From: Andriy Gapon > To: J David > Cc: freebsd-stable@FreeBSD.org > Subject: Re: Problem with zfsloader on 9.2-BETA2 > Message-ID: <51FD5709.7050306@FreeBSD.org> > Content-Type: text/plain; charset=windows-1252 > > on 31/07/2013 10:49 J David said the following: >> But the system still wouldn't boot, moving on to: >> >> ZFS: can't find pool by guid >> ZFS: can't find pool by guid >> >> We got around this by interrupting the stage1 loader and invoking >> data/root:/boot/zfsloader.old instead. Then we moved the 9.2 >> zfsloader out of the way and restored the 8.4 loader. >> >> So this system only boots with the 9.2 gptzfsboot and the 8.4 zfsloader. > > Very unusual. Would you be able to try 9.2 zfsloader again? > I would like to see values of loaddev, currdev and vfs.zfs.boot.primary_pool > loader variables (if any are set). These can be obtained using 'show' command > at loader prompt. Also, output of lsdev -v. > > Also, if you are able to build custom 9.2 zfsloader, then it would be useful to > modify the printf statement (in zfs_fmtdev(), sys/boot/zfs/zfs.c) to print > dev->pool_guid. > > -- > Andriy Gapon > > > ------------------------------ > > Message: 5 > Date: Sun, 4 Aug 2013 09:27:27 +0400 > From: Pavel Timofeev > Cc: freebsd-stable@freebsd.org > Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Same thing on RELENG/9.2 > > 2013/8/3 Pavel Timofeev : >> 2013/8/2 Ruben de Groot : >>> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>>> We don't use IPv6 in our company. >>>> >>>> 2013/7/31 Pavel Timofeev : >>>>> I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>>> server, but not A (IPv4). >>>>> Any ideas? >>>>> >>>>> 2013/7/31 Pavel Timofeev : >>>>>> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>>>> ip address. >>>>>> >>>>>> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>>>> 53417+ AAAA? xxx.ru. (24) >>>>>> [13/98] >>>>>> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>>>> 53417* 0/1/0 (75) >>>>>> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>>>> 53418+ A? xxx.ru. (24) >>> >>> Here it is definately asking an A record. >> >> And? It's not A record of mx server. >> >>>>>> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>>>> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>>>> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>>>> (136) >>> >>> And here is the reply. The quetion is more why is it repeating the same >>> query (below) over and over. >> >> Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru >> >>> >>> Ruben >>> >>>>>> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>>>> 53419+ MX? xxx.ru. (24) >>>>>> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>>>> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>>>> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>>>> 53420+ AAAA? kalmar.xxx.ru. (31) >>>>>> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>>>> 53420* 0/1/0 (82) >>>>>> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>>>> 53421+ AAAA? kalmar.xxx.ru. (31) >>>>>> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>>>> 53421* 0/1/0 (82) >>>>>> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>>>> 53422+ AAAA? kalmar. (24) >>>>>> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>>>> 53422 ServFail 0/0/0 (24) >>>>>> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>>>> 53422+ AAAA? kalmar. (24) >>>>>> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>>>> 53422 ServFail 0/0/0 (24) >>>>>> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>>>> 53423+ AAAA? kalmar.xxx.ru. (31) >>>>>> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>>>> 53423* 0/1/0 (82) >>>>>> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>>>> 53424+ AAAA? kalmar. (24) >>>>>> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>>>> 53424 ServFail 0/0/0 (24) >>>>>> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>>>> 53424+ AAAA? kalmar. (24) >>>>>> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>>>> 53424 ServFail 0/0/0 (24) >>>>>> >>>>>> How to force it to use IPv4? >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > ------------------------------ > > Message: 6 > Date: Sat, 03 Aug 2013 23:34:13 -0700 > From: John Reynolds > To: stable@freebsd.org > Subject: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- > Firefox SQLite locking issue > Message-ID: <51FDF5E5.4070606@reynoldsnet.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello all, > > I've been recently building up a new Haswell box and after overcoming > several problems have gotten things to mostly work. But I got stuck when > trying to use Firefox 22. The bookmarks editor/container was always > coming up empty and I was not able to import bookmarks I had from a > saved profile. Additionally, the back/forward arrow buttons would not > work. They were always grayed out making navigation impossible and thus > rendering the browser fairly useless. > > I tried linux-firefox and the SAME problems existed. This led me to > believe it wasn't a port problem. I saw mention after searching and > searching for an answer of somebody who moved their account's $HOME dir > from an NFS mounted volume to a local disk and some other problem they > had went away. I thought "oh, this has got to be a locking problem." So, > I tried this and Firefox 22 works perfectly on local disk! It's got to > be the SQLite that FF22 uses for the "places.sqlite" and other SQL > databases (bookmarks, etc.) and a locking issue since I have my $HOME > directory mounted over NFS. > > My setup: > > NFS server: FreeBSD 8.3-STABLE as of Jan 2013 > nfs_server_enable="YES" > nfs_server_flags="-u -t -n 4" > nfsv4_server_enable="NO" > rpc_lockd_enable="YES" > rpc_statd_enable="YES" > > I am not knowingly running any other version of NFS server/client other > than what any user would get by "default" (supposing NFSv3). > > NFS client: FreeBSD 9.2-BETA2 (I've been tracking sources and updating > through buildworld, etc.) > Just using normal "nfs" options when mounting the homedir directory on > the client. > > So, questions: > - I haven't upgraded the server to 9.x. I plan to do that along with > new faster hardware, but since I have multiple "users" in the house, I > have to have some dedicated time to work, research, plan, and pray > things don't go wrong before I black-out the gateway/firewall/nat/etc > box for all these "users" :). When I upgrade so that server is > relatively equal to client (at least same 9.x version) should I see > locking problems like the above? i.e. somebody else on this list HAS to > be using NFS to serve up home directories. Do you see locking problems > like that mentioned above? > - I saw many posts talking about moving things to NFSv4 to resolve > locking problems. If I was to upgrade the server to the latest > 8.x-STABLE kernel/world should this interact with a 9.x world properly > using NFSv4? Is the NFSv4 server in 8.x-STABLE "good enough" in this regard? > - Without having to upgrade either my server or change to NFSv4 across > the board, what other options might there be? The older hardware for > this machine was running relatively the same kernel as my > server--8.3-STABLE and I DID NOT SEE this behavior--which l leads me to > believe that it is an 8.x <-> 9.x issue. Is there anybody out there > besides me mixing these versions or am I the only person the planet that > hasn't upgraded to 9-stable? :) > - I see bits and pieces of documentation talking about how to use > NFSv4, but I didn't see anything in the Handbook or out there in the > wild that was a guide on how to migrate one's setup/config files. If > there are good howto's or other articles on this please share! > > Thanks in advance for all answers. I appreciate the dedication that you > all have! > > -Jr > > > > ------------------------------ > > Message: 7 > Date: Sun, 4 Aug 2013 06:32:22 -0400 (EDT) > From: Rick Macklem > To: John Reynolds > Cc: stable@freebsd.org > Subject: Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 > -- Firefox SQLite locking issue > Message-ID: > <1072840488.5640439.1375612342793.JavaMail.root@uoguelph.ca> > Content-Type: text/plain; charset=utf-8 > > John Reynolds wrote: >> Hello all, >> >> I've been recently building up a new Haswell box and after overcoming >> several problems have gotten things to mostly work. But I got stuck >> when >> trying to use Firefox 22. The bookmarks editor/container was always >> coming up empty and I was not able to import bookmarks I had from a >> saved profile. Additionally, the back/forward arrow buttons would not >> work. They were always grayed out making navigation impossible and >> thus >> rendering the browser fairly useless. >> >> I tried linux-firefox and the SAME problems existed. This led me to >> believe it wasn't a port problem. I saw mention after searching and >> searching for an answer of somebody who moved their account's $HOME >> dir >> from an NFS mounted volume to a local disk and some other problem >> they >> had went away. I thought "oh, this has got to be a locking problem." >> So, >> I tried this and Firefox 22 works perfectly on local disk! It's got >> to >> be the SQLite that FF22 uses for the "places.sqlite" and other SQL >> databases (bookmarks, etc.) and a locking issue since I have my $HOME >> directory mounted over NFS. >> >> My setup: >> >> NFS server: FreeBSD 8.3-STABLE as of Jan 2013 >> nfs_server_enable="YES" >> nfs_server_flags="-u -t -n 4" >> nfsv4_server_enable="NO" >> rpc_lockd_enable="YES" >> rpc_statd_enable="YES" >> >> I am not knowingly running any other version of NFS server/client >> other >> than what any user would get by "default" (supposing NFSv3). >> >> NFS client: FreeBSD 9.2-BETA2 (I've been tracking sources and >> updating >> through buildworld, etc.) >> Just using normal "nfs" options when mounting the homedir directory >> on >> the client. >> >> So, questions: >> - I haven't upgraded the server to 9.x. I plan to do that along >> with >> new faster hardware, but since I have multiple "users" in the house, >> I >> have to have some dedicated time to work, research, plan, and pray >> things don't go wrong before I black-out the gateway/firewall/nat/etc >> box for all these "users" :). When I upgrade so that server is >> relatively equal to client (at least same 9.x version) should I see >> locking problems like the above? i.e. somebody else on this list HAS >> to >> be using NFS to serve up home directories. Do you see locking >> problems >> like that mentioned above? >> - I saw many posts talking about moving things to NFSv4 to resolve >> locking problems. If I was to upgrade the server to the latest >> 8.x-STABLE kernel/world should this interact with a 9.x world >> properly >> using NFSv4? Is the NFSv4 server in 8.x-STABLE "good enough" in this >> regard? > Yes, I believe that a current stable/8.x NFSv4 server will work ok. > >> - Without having to upgrade either my server or change to NFSv4 >> across >> the board, what other options might there be? > Unless multiple clients share the same files concurrently that must be > locked (not likely for home dir stuff), the "nolockd" mount option on > the client will avoid having to use rpc.lockd and rpc.statd. (With this > mount option, the locks are visible to all processes in the client, > but not to other clients accessing the same file.) > >> The older hardware for >> this machine was running relatively the same kernel as my >> server--8.3-STABLE and I DID NOT SEE this behavior--which l leads me >> to >> believe that it is an 8.x <-> 9.x issue. Is there anybody out there >> besides me mixing these versions or am I the only person the planet >> that >> hasn't upgraded to 9-stable? :) >> - I see bits and pieces of documentation talking about how to use >> NFSv4, but I didn't see anything in the Handbook or out there in the >> wild that was a guide on how to migrate one's setup/config files. If >> there are good howto's or other articles on this please share! >> > About all you need to do is add a "V4: ..." line to your /etc/exports > and then set nfsv4_server_enable="YES" in /etc/rc.conf and reboot. > On the client mount, you need to add "nfsv4" as a mount option. > >> Thanks in advance for all answers. I appreciate the dedication that >> you >> all have! >> >> -Jr >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" >> > > > ------------------------------ > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > End of freebsd-stable Digest, Vol 524, Issue 9 > ********************************************** > From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 19:28:07 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 186105BA for ; Sun, 4 Aug 2013 19:28:07 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE3092575 for ; Sun, 4 Aug 2013 19:28:06 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r74JRxda068759 for ; Sun, 4 Aug 2013 15:28:04 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <51FEAB3F.3010008@m5p.com> Date: Sun, 04 Aug 2013 15:27:59 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130716 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: boot2 FreeBSD 9.2-RC1 r253913M Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 04 Aug 2013 15:28:05 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 19:28:07 -0000 boot2 gives me a "boot: " prompt but will not accept input from the keyboard on an HP CQ61-420US notebook. Fortunately, it times out after a few seconds and boots normally after that. But it's still a bit annoying. -- George From owner-freebsd-stable@FreeBSD.ORG Sun Aug 4 19:30:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2DEB768 for ; Sun, 4 Aug 2013 19:30:41 +0000 (UTC) (envelope-from george@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7DA0E25B9 for ; Sun, 4 Aug 2013 19:30:41 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r74JUZQo068773 for ; Sun, 4 Aug 2013 15:30:40 -0400 (EDT) (envelope-from george@m5p.com) Message-ID: <51FEABDB.7030804@m5p.com> Date: Sun, 04 Aug 2013 15:30:35 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130716 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: boot2 FreeBSD 9.2-RC1 r253913M References: <51FEAB3F.3010008@m5p.com> In-Reply-To: <51FEAB3F.3010008@m5p.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 04 Aug 2013 15:30:40 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 19:30:41 -0000 On 08/04/13 15:27, George Mitchell wrote: > boot2 gives me a "boot: " prompt but will not accept input from the > keyboard on an HP CQ61-420US notebook. Fortunately, it times out > after a few seconds and boots normally after that. But it's still > a bit annoying. -- George The "M" is because I rolled back r250907 due to the reports of NFS deadlocks. -- George From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 11:11:51 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89A2596F; Mon, 5 Aug 2013 11:11:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 43B002766; Mon, 5 Aug 2013 11:11:51 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 4A0EF832A; Mon, 5 Aug 2013 11:11:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 4A0EF832A Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 5 Aug 2013 07:11:47 -0400 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: FreeBSD 9.2-RC1 now available Message-ID: <20130805111147.GR2352@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zu8lIfFVzXMVnfzp" Content-Disposition: inline X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 11:11:51 -0000 --zu8lIfFVzXMVnfzp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The first release candidate builds of the 9.2-RELEASE release cycle are now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64, and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.2/ (or any of the FreeBSD mirror sites). If you notice problems you can report them through the normal GNATS PR system or here on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system use "releng/9.2". Please be aware that cvsup and CVS are both deprecated, and are not supported methods of updating the src/ tree. Changes between -BETA2 and -RC1 include: - Expand the list of devices claimed by cxgbe(4). - Fix a panic in the racct code when munlock(2) is called with incorrect values. - Remove ctl(4) from GENERIC. ctladm(8) now automatically loads the corresponding module as necessary. This reduces the default memory footprint and allows FreeBSD to work on i386 machines with 128 MB of RAM out of the box. - Fix zfs send -D hang after processing requiring a CTRL+C to interrupt. The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 9.2-RC1 During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 8.x. Alternatively, the user can install misc/compat8x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install Checksums: amd64: SHA256 (FreeBSD-9.2-RC1-amd64-bootonly.iso) = 57312363a8ce588c22c21b849af802ca2616e105da2e29b4ae6f549d41e9a32d SHA256 (FreeBSD-9.2-RC1-amd64-disc1.iso) = bc30f5661304c65d14612d39e19f9651502fbdc467d9ad02402c58a99d6fe2da SHA256 (FreeBSD-9.2-RC1-amd64-memstick.img) = 57af7a47604d2c138e4887a717526f7a48d90ba0e0f5e23425845a7b1a2ff131 MD5 (FreeBSD-9.2-RC1-amd64-bootonly.iso) = c36b97aec501a49f3a49b38303b53f0d MD5 (FreeBSD-9.2-RC1-amd64-disc1.iso) = 5124086f31bf5efc40b770dd2439ce7a MD5 (FreeBSD-9.2-RC1-amd64-memstick.img) = 2f2ea636cfc5fe74ea15a4c1cbd2f8cb i386: SHA256 (FreeBSD-9.2-RC1-i386-bootonly.iso) = 7926b57fdc9ce536bdf51722a524d9ae385a82bf02c42b3315604542672b0906 SHA256 (FreeBSD-9.2-RC1-i386-disc1.iso) = d33ec96a39e2b5a53b143397daac4d3778c30b3ec0592fccd5e8b84def69d03c SHA256 (FreeBSD-9.2-RC1-i386-memstick.img) = 523899af78effdf7760791d91c3d56620a484b73c74bbfa82e9f21178979ddb8 MD5 (FreeBSD-9.2-RC1-i386-bootonly.iso) = 3500e3b375a955d91f194b8ab3a58c2f MD5 (FreeBSD-9.2-RC1-i386-disc1.iso) = 4534a3675a5a38d475a7eff6651f4289 MD5 (FreeBSD-9.2-RC1-i386-memstick.img) = c4cbb5478c557dd9e2200da027da799c ia64: SHA256 (FreeBSD-9.2-RC1-ia64-bootonly.iso) = bd95b2480edd547fff06587a04f65ceceeaa312ac08e0fceccbced47f3df47ac SHA256 (FreeBSD-9.2-RC1-ia64-disc1.iso) = 93795e3e9df2e3ea6163efadf0f25a70d8574f75868826a403721fbc8abec43e SHA256 (FreeBSD-9.2-RC1-ia64-memstick.img) = d027d2965906c96798855adadf60ea622d87e19e28de15efe889086962d73774 MD5 (FreeBSD-9.2-RC1-ia64-bootonly.iso) = 3be3ec429b03facf5f6f29ac409dd2f6 MD5 (FreeBSD-9.2-RC1-ia64-disc1.iso) = 24f6a2c3749799337065ebc7bb8f7d92 MD5 (FreeBSD-9.2-RC1-ia64-memstick.img) = 8fa6c1736ea74bc440137079bf3c9fa1 powerpc: SHA256 (FreeBSD-9.2-RC1-powerpc-bootonly.iso) = 0d0f2048ffe81ac7bc36a687ccd8dcd4368460c4dd7055cdabde5f70824062d0 SHA256 (FreeBSD-9.2-RC1-powerpc-disc1.iso) = 31544e513992da8c1df4ca043d22952b102ed2c1b9c184db6ddc3a2fd4aecedc SHA256 (FreeBSD-9.2-RC1-powerpc-memstick.img) = 48306dd6f718d820ca2464eedfafe761b2fb5f211d1f23545e3cb1f6dfdbf0a8 MD5 (FreeBSD-9.2-RC1-powerpc-bootonly.iso) = 20d43ffe51a6d374fc358dd7e5c65a2a MD5 (FreeBSD-9.2-RC1-powerpc-disc1.iso) = 8deb66e7d557734fd64aaaa709c8512a MD5 (FreeBSD-9.2-RC1-powerpc-memstick.img) = 324373d1a647722f6b925038b00a9004 powerpc64: SHA256 (FreeBSD-9.2-RC1-powerpc-powerpc64-bootonly.iso) = 27f4f23093067d20a92f85d7fb611c6576e7ceb4fdf2481154ca05ba1ddbf282 SHA256 (FreeBSD-9.2-RC1-powerpc-powerpc64-disc1.iso) = 008f42feb9c6378976d20cec227fbd5ab811f36be1519db9f90e0edd07df961c SHA256 (FreeBSD-9.2-RC1-powerpc-powerpc64-memstick.img) = 49602d2f1cbd70e09fe8a52dd524b5c2199eab62c12a3f5a01b7da556f6fb631 MD5 (FreeBSD-9.2-RC1-powerpc-powerpc64-bootonly.iso) = 5f9e70ef5e219cddf7efd7d8b781be75 MD5 (FreeBSD-9.2-RC1-powerpc-powerpc64-disc1.iso) = 4e86808cfe5fc9ad2bea65de65f7c39a MD5 (FreeBSD-9.2-RC1-powerpc-powerpc64-memstick.img) = f848312980656b313306fd0cef29a87c sparc64: SHA256 (FreeBSD-9.2-RC1-sparc64-bootonly.iso) = 6ba72bc66c0d18fcb4fe9cd1a67289fbf4d2aacb85d21920b4e1d2f46e21a0cc SHA256 (FreeBSD-9.2-RC1-sparc64-disc1.iso) = 089b9792b4e3af9cc1a341b06757c852e57ed19ec8ef81b4c99dba047dbb9c8d MD5 (FreeBSD-9.2-RC1-sparc64-bootonly.iso) = 08b69371ea4222c42058083e364da1a0 MD5 (FreeBSD-9.2-RC1-sparc64-disc1.iso) = 2d041fb59229dcf5bc46337679d32ab0 Glen --zu8lIfFVzXMVnfzp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR/4hzAAoJEFJPDDeguUaj94MH/2zGxRkK0l4y0l3mkBmpYT/Z z0OKeYWcegJDn70Mq97izndz6CYraveOJubhPbNRgzdIvx1W9bWHquO6EPl/Xrwm ytH099wkOGN3w8aW2C+LJTdSxVSSf8+Q+gr2iTcy68WgnZD+9v9SLtgJpjtBXtwz hfenvOB7Iv38s8ZPBRwRnayv9DGoh72kXJyY4cDPbbuxPsRDOIQxqu/Wdnwcmxd+ S0pUT5sdLhVNFNuqZcvl15hw9MtqdkeDDUil8KEHq2t1+qmphBaQ2jDIOWj+vJXT uRXoRSN+eVYKnPcfCEXytjIQnwfOAbXLZvlBGmSYe6JQe4EExVoAdild1tv9Gwg= =Pe+S -----END PGP SIGNATURE----- --zu8lIfFVzXMVnfzp-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 12:02:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB73BB6D for ; Mon, 5 Aug 2013 12:02:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87C1229CF for ; Mon, 5 Aug 2013 12:02:41 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id pb11so2919487veb.39 for ; Mon, 05 Aug 2013 05:02:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=VVxLvZg+g1IMBerT9I9BvJ0YdtkRp/7b6QXHNepRFsI=; b=SukQ3d3Qn0Q4xJIWq1vWy3d7QiAJ+tMYSE6XyaV8jXTOhFdLUHKo425k0e4AdJqkXH 1gVzigpQuyDN0ayMgbzORdZcRv4HMT+UrfYQ/HI/WXmwl6QvYUsDpAAwbcMFHPycijv6 5YM3xtqcXhlTftnBXwBdxlCjKyodpK3CyTR+YlQo1it/fj0kCHh1Iy0aDJCU/79VLrNy rB5fkilBzEkhDYKJF9xaVzboVocH3cw0ooPRQBXv+5dMAtvVY6Rxm+0AGKDqj8vXRW+F AY3paZ5yGrLjQE2GnmTbVQFAQlNklwH8C3qdU8Mq+MMPLO+6ceWxZspS8vIrAj2rve1L NspQ== MIME-Version: 1.0 X-Received: by 10.58.76.130 with SMTP id k2mr5584383vew.24.1375704160705; Mon, 05 Aug 2013 05:02:40 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Mon, 5 Aug 2013 05:02:40 -0700 (PDT) In-Reply-To: References: <20130802102100.GA11138@eris.bzerk.org> Date: Mon, 5 Aug 2013 16:02:40 +0400 Message-ID: Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 From: Pavel Timofeev Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 12:02:41 -0000 Got some new info. I read this https://lists.isc.org/pipermail/bind-users/2006-August/063528.html Perhaps, the problem because our MS DNS server returns SERVFAIL on AAAA query. It happens in case of often AAAA queries. It's 9.2-RC1: .... 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: 53419+ MX? xxx.ru. (24) 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: 53420+ AAAA? kalmar.xxx.ru. (31) 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: 53420* 0/1/0 (82) 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: 53421+ AAAA? kalmar.xxx.ru. (31) 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: 53421* 0/1/0 (82) 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: 53422+ AAAA? kalmar. (24) 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: 53422 ServFail 0/0/0 (24) .... At third time MS DNS returned SERVFAIL. Why sendmail asks AAAA for 3 times? Something wrong with bind libraries? I think if there was no SERVFAIL on AAAA it would ask for A record then. The opposite situation on 9.1-RELEASE. Here sendmail asks AAAA only for 1 time. Then it asks A. ... 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ MX? xxx.ru. (24) 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* 1/0/1 MX kalmar.xxx.ru. 10 (63) 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ AAAA? kalmar.xxx.ru. (31) 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? kalmar.xxx.ru. (31) 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* 1/0/0 A 192.168.31.190 (47) ... I will continue investigation. 2013/8/4 Pavel Timofeev : > Same thing on RELENG/9.2 > > 2013/8/3 Pavel Timofeev : >> 2013/8/2 Ruben de Groot : >>> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>>> We don't use IPv6 in our company. >>>> >>>> 2013/7/31 Pavel Timofeev : >>>> > I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>> > server, but not A (IPv4). >>>> > Any ideas? >>>> > >>>> > 2013/7/31 Pavel Timofeev : >>>> >> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>> >> ip address. >>>> >> >>>> >> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>> >> 53417+ AAAA? xxx.ru. (24) >>>> >> [13/98] >>>> >> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>> >> 53417* 0/1/0 (75) >>>> >> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>> >> 53418+ A? xxx.ru. (24) >>> >>> Here it is definately asking an A record. >> >> And? It's not A record of mx server. >> >>>> >> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>> >> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>> >> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>> >> (136) >>> >>> And here is the reply. The quetion is more why is it repeating the same >>> query (below) over and over. >> >> Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru >> >>> >>> Ruben >>> >>>> >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>> >> 53419+ MX? xxx.ru. (24) >>>> >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>> >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>> >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>> >> 53420+ AAAA? kalmar.xxx.ru. (31) >>>> >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>> >> 53420* 0/1/0 (82) >>>> >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>> >> 53421+ AAAA? kalmar.xxx.ru. (31) >>>> >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>> >> 53421* 0/1/0 (82) >>>> >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>> >> 53422+ AAAA? kalmar. (24) >>>> >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>> >> 53422 ServFail 0/0/0 (24) >>>> >> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>> >> 53422+ AAAA? kalmar. (24) >>>> >> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>> >> 53422 ServFail 0/0/0 (24) >>>> >> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>> >> 53423+ AAAA? kalmar.xxx.ru. (31) >>>> >> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>> >> 53423* 0/1/0 (82) >>>> >> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>> >> 53424+ AAAA? kalmar. (24) >>>> >> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>> >> 53424 ServFail 0/0/0 (24) >>>> >> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>> >> 53424+ AAAA? kalmar. (24) >>>> >> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>> >> 53424 ServFail 0/0/0 (24) >>>> >> >>>> >> How to force it to use IPv4? >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 12:15:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B69FC9B for ; Mon, 5 Aug 2013 12:15:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 724BB2A56 for ; Mon, 5 Aug 2013 12:15:41 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id q14so2722177vbe.27 for ; Mon, 05 Aug 2013 05:15:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=a20tizCePbtpKpcluhy/GD82ksrOuZfZoq3CyKe1JVA=; b=mlWj687J8eeY1e50SBGaDq8RVmMSaYpRQiDBQBrqC+NFqn+zvnXkLem4nNvzoBTYRa dUS3H9G06jKrp7+VJALvs1Dot1ytEF3VLhjP2SNLj+A+hAQqWQyJ8DOpwI6QZKjAJG+5 eiRU7v3aWCWHadXOG552QwxzuzAuOfT36DCxvk/fNCTjaJTaU+VTV3v12nMOJxhH0PUy gKE0R01ykWwhZM+gIeuCJrLG6gBMLP2cpCVDxBPXY9BqVF0qxxlK3UspVO83C3nOijFq jgRgT8eUeMg7tMJyVpqdzg6WRQxOYfxbML90Mi6ic16Hm5kO25xm6dhCjaIohoA9ii3q Xk9Q== MIME-Version: 1.0 X-Received: by 10.220.111.142 with SMTP id s14mr3059261vcp.55.1375704940613; Mon, 05 Aug 2013 05:15:40 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Mon, 5 Aug 2013 05:15:40 -0700 (PDT) In-Reply-To: References: <20130802102100.GA11138@eris.bzerk.org> Date: Mon, 5 Aug 2013 16:15:40 +0400 Message-ID: Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 From: Pavel Timofeev To: Pavel Timofeev Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 12:15:41 -0000 Hmm. SERVFAIL comes because of not full dns name. Kalmar. instead of kalmar.ocs.ru. 2013/8/5 Pavel Timofeev : > Got some new info. I read this > https://lists.isc.org/pipermail/bind-users/2006-August/063528.html > Perhaps, the problem because our MS DNS server returns SERVFAIL on AAAA query. > It happens in case of often AAAA queries. It's 9.2-RC1: > .... > 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: > 53419+ MX? xxx.ru. (24) > 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: > 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) > 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: > 53420+ AAAA? kalmar.xxx.ru. (31) > 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: > 53420* 0/1/0 (82) > 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: > 53421+ AAAA? kalmar.xxx.ru. (31) > 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: > 53421* 0/1/0 (82) > 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: > 53422+ AAAA? kalmar. (24) > 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: > 53422 ServFail 0/0/0 (24) > .... > At third time MS DNS returned SERVFAIL. Why sendmail asks AAAA for 3 times? > Something wrong with bind libraries? I think if there was no SERVFAIL > on AAAA it would ask for A record then. > > The opposite situation on 9.1-RELEASE. Here sendmail asks AAAA only > for 1 time. Then it asks A. > ... > 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ > MX? xxx.ru. (24) > 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* > 1/0/1 MX kalmar.xxx.ru. 10 (63) > 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ > AAAA? kalmar.xxx.ru. (31) > 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) > 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? > kalmar.xxx.ru. (31) > 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* > 1/0/0 A 192.168.31.190 (47) > ... > > I will continue investigation. > > > > 2013/8/4 Pavel Timofeev : >> Same thing on RELENG/9.2 >> >> 2013/8/3 Pavel Timofeev : >>> 2013/8/2 Ruben de Groot : >>>> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>>>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>>>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>>>> We don't use IPv6 in our company. >>>>> >>>>> 2013/7/31 Pavel Timofeev : >>>>> > I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>>> > server, but not A (IPv4). >>>>> > Any ideas? >>>>> > >>>>> > 2013/7/31 Pavel Timofeev : >>>>> >> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>>> >> ip address. >>>>> >> >>>>> >> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>>> >> 53417+ AAAA? xxx.ru. (24) >>>>> >> [13/98] >>>>> >> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>>> >> 53417* 0/1/0 (75) >>>>> >> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>>> >> 53418+ A? xxx.ru. (24) >>>> >>>> Here it is definately asking an A record. >>> >>> And? It's not A record of mx server. >>> >>>>> >> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>>> >> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>>> >> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>>> >> (136) >>>> >>>> And here is the reply. The quetion is more why is it repeating the same >>>> query (below) over and over. >>> >>> Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru >>> >>>> >>>> Ruben >>>> >>>>> >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>>> >> 53419+ MX? xxx.ru. (24) >>>>> >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>>> >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>>> >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>>> >> 53420+ AAAA? kalmar.xxx.ru. (31) >>>>> >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>>> >> 53420* 0/1/0 (82) >>>>> >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>>> >> 53421+ AAAA? kalmar.xxx.ru. (31) >>>>> >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>>> >> 53421* 0/1/0 (82) >>>>> >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>>> >> 53422+ AAAA? kalmar. (24) >>>>> >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>>> >> 53422 ServFail 0/0/0 (24) >>>>> >> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>>> >> 53422+ AAAA? kalmar. (24) >>>>> >> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>>> >> 53422 ServFail 0/0/0 (24) >>>>> >> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>>> >> 53423+ AAAA? kalmar.xxx.ru. (31) >>>>> >> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>>> >> 53423* 0/1/0 (82) >>>>> >> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>>> >> 53424+ AAAA? kalmar. (24) >>>>> >> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>>> >> 53424 ServFail 0/0/0 (24) >>>>> >> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>>> >> 53424+ AAAA? kalmar. (24) >>>>> >> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>>> >> 53424 ServFail 0/0/0 (24) >>>>> >> >>>>> >> How to force it to use IPv4? >>>>> _______________________________________________ >>>>> freebsd-stable@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 12:21:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 93EBB4C9 for ; Mon, 5 Aug 2013 12:21:45 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4EC262AA3 for ; Mon, 5 Aug 2013 12:21:45 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id cy12so2973877veb.32 for ; Mon, 05 Aug 2013 05:21:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8UVw7ZHY21Mc0bCCekUip4FEf4TZyU7Hpeh3jXRTYhU=; b=sm3KnNelJzUkRmaAwKSRe6DyNxtUnrAaD6vI7DFsuLddiH9b9LHwML14KuVxC63nQV gDQ+HGHW1gU4jPiZY4FUIs/noA4H6RJ7h9vngwJsVDSU9xckqHNceiWY7saWMW04j1Va sYABia4ERDeDPDIHCbtOK5Iox+gALE8KCAiclAgQkI5BJwyCWQsAslbMFC19ezvDe15c Tn7muGQsxXbK7XVURshr3dOKHa9zzLty8KDj6L4upBoGutKpHMjgCpwOBx44yXWw2jcW vzjAwMQQjHyYyFY9S1UZuracLfnKduInmiXoRxp3tp0o/8d7lz3MuRKXkdTUFpHwTbFe PCSA== MIME-Version: 1.0 X-Received: by 10.58.118.8 with SMTP id ki8mr5617526veb.84.1375705304284; Mon, 05 Aug 2013 05:21:44 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Mon, 5 Aug 2013 05:21:44 -0700 (PDT) In-Reply-To: References: <20130802102100.GA11138@eris.bzerk.org> Date: Mon, 5 Aug 2013 16:21:44 +0400 Message-ID: Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 From: Pavel Timofeev To: Pavel Timofeev Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 12:21:45 -0000 So, sendmail is broken? Or libraries which sendmail uses to resolv names? 2013/8/5 Pavel Timofeev : > Hmm. SERVFAIL comes because of not full dns name. Kalmar. instead of > kalmar.ocs.ru. > > 2013/8/5 Pavel Timofeev : >> Got some new info. I read this >> https://lists.isc.org/pipermail/bind-users/2006-August/063528.html >> Perhaps, the problem because our MS DNS server returns SERVFAIL on AAAA query. >> It happens in case of often AAAA queries. It's 9.2-RC1: >> .... >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >> 53419+ MX? xxx.ru. (24) >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >> 53420+ AAAA? kalmar.xxx.ru. (31) >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >> 53420* 0/1/0 (82) >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >> 53421+ AAAA? kalmar.xxx.ru. (31) >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >> 53421* 0/1/0 (82) >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >> 53422+ AAAA? kalmar. (24) >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >> 53422 ServFail 0/0/0 (24) >> .... >> At third time MS DNS returned SERVFAIL. Why sendmail asks AAAA for 3 times? >> Something wrong with bind libraries? I think if there was no SERVFAIL >> on AAAA it would ask for A record then. >> >> The opposite situation on 9.1-RELEASE. Here sendmail asks AAAA only >> for 1 time. Then it asks A. >> ... >> 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ >> MX? xxx.ru. (24) >> 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* >> 1/0/1 MX kalmar.xxx.ru. 10 (63) >> 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ >> AAAA? kalmar.xxx.ru. (31) >> 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) >> 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? >> kalmar.xxx.ru. (31) >> 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* >> 1/0/0 A 192.168.31.190 (47) >> ... >> >> I will continue investigation. >> >> >> >> 2013/8/4 Pavel Timofeev : >>> Same thing on RELENG/9.2 >>> >>> 2013/8/3 Pavel Timofeev : >>>> 2013/8/2 Ruben de Groot : >>>>> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>>>>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>>>>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>>>>> We don't use IPv6 in our company. >>>>>> >>>>>> 2013/7/31 Pavel Timofeev : >>>>>> > I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>>>> > server, but not A (IPv4). >>>>>> > Any ideas? >>>>>> > >>>>>> > 2013/7/31 Pavel Timofeev : >>>>>> >> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>>>> >> ip address. >>>>>> >> >>>>>> >> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>>>> >> 53417+ AAAA? xxx.ru. (24) >>>>>> >> [13/98] >>>>>> >> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>>>> >> 53417* 0/1/0 (75) >>>>>> >> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>>>> >> 53418+ A? xxx.ru. (24) >>>>> >>>>> Here it is definately asking an A record. >>>> >>>> And? It's not A record of mx server. >>>> >>>>>> >> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>>>> >> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>>>> >> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>>>> >> (136) >>>>> >>>>> And here is the reply. The quetion is more why is it repeating the same >>>>> query (below) over and over. >>>> >>>> Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru >>>> >>>>> >>>>> Ruben >>>>> >>>>>> >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>>>> >> 53419+ MX? xxx.ru. (24) >>>>>> >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>>>> >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>>>> >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>>>> >> 53420+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>>>> >> 53420* 0/1/0 (82) >>>>>> >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>>>> >> 53421+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>>>> >> 53421* 0/1/0 (82) >>>>>> >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>>>> >> 53422+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>>>> >> 53422 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>>>> >> 53422+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>>>> >> 53422 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>>>> >> 53423+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>>>> >> 53423* 0/1/0 (82) >>>>>> >> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>>>> >> 53424+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>>>> >> 53424 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>>>> >> 53424+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>>>> >> 53424 ServFail 0/0/0 (24) >>>>>> >> >>>>>> >> How to force it to use IPv4? >>>>>> _______________________________________________ >>>>>> freebsd-stable@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 12:59:31 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 704E5D53 for ; Mon, 5 Aug 2013 12:59:31 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A8FC2C18 for ; Mon, 5 Aug 2013 12:59:31 +0000 (UTC) Received: by mail-ve0-f178.google.com with SMTP id ox1so2993620veb.37 for ; Mon, 05 Aug 2013 05:59:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=HqoUwsSEKGB7C4dJ7e2SIjXFC3Kt0JW4yeL4O5w4gXo=; b=a8LGvAL7BpbD3mx4VC1WRnnBqxQCt2acUy+LrWIzhACWxO+kIhLO3uTPTVznoNCDud 8M/aGHcX93ZoMMq4L+I+rTU9jrmXfaDZn0EB9H5Id8Bxy42CfFQ30EG0h5kqMvPcw5yi hs3IgYUdKz3EhQhvQ9sxGz503fm/15xn7r1f9vwHRvEQhGm0KnC8pSAfAJ1LXFoFlI+M 4c/RCqHNuxeboVkr7UXZpKzXerk5W8VpI9PiQwZWL/ZA+HN5HwlviWWOn8CfpyakQtRM 6BkcR6/2l1RBqDj3juiSlfSVYoA0zJs5xvoOyx2tte4OREX3uyPlYlhm4huxyRMBGREQ +mCA== MIME-Version: 1.0 X-Received: by 10.220.205.67 with SMTP id fp3mr5878721vcb.43.1375707569973; Mon, 05 Aug 2013 05:59:29 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Mon, 5 Aug 2013 05:59:29 -0700 (PDT) In-Reply-To: References: <20130802102100.GA11138@eris.bzerk.org> Date: Mon, 5 Aug 2013 16:59:29 +0400 Message-ID: Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 From: Pavel Timofeev Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 12:59:31 -0000 Another DNS (not MS) server answers NXDomain instead of SERVFAIL on 'AAAA? kalmar.' query. And then sendmail asks for A. Email works There are two ways obviously: 1. Change sendmail behaviour, i.e. make it ask for A record just after first query for AAAA. Like in 9.1-RELEASE. 2. Make MS DNS answer NXDomain instead of SERVFAIL on AAAA of kalmar. Is it possible at all? =) 2013/8/5 Pavel Timofeev : > Hmm. SERVFAIL comes because of not full dns name. Kalmar. instead of > kalmar.ocs.ru. > > 2013/8/5 Pavel Timofeev : >> Got some new info. I read this >> https://lists.isc.org/pipermail/bind-users/2006-August/063528.html >> Perhaps, the problem because our MS DNS server returns SERVFAIL on AAAA query. >> It happens in case of often AAAA queries. It's 9.2-RC1: >> .... >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >> 53419+ MX? xxx.ru. (24) >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >> 53420+ AAAA? kalmar.xxx.ru. (31) >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >> 53420* 0/1/0 (82) >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >> 53421+ AAAA? kalmar.xxx.ru. (31) >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >> 53421* 0/1/0 (82) >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >> 53422+ AAAA? kalmar. (24) >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >> 53422 ServFail 0/0/0 (24) >> .... >> At third time MS DNS returned SERVFAIL. Why sendmail asks AAAA for 3 times? >> Something wrong with bind libraries? I think if there was no SERVFAIL >> on AAAA it would ask for A record then. >> >> The opposite situation on 9.1-RELEASE. Here sendmail asks AAAA only >> for 1 time. Then it asks A. >> ... >> 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ >> MX? xxx.ru. (24) >> 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* >> 1/0/1 MX kalmar.xxx.ru. 10 (63) >> 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ >> AAAA? kalmar.xxx.ru. (31) >> 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) >> 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? >> kalmar.xxx.ru. (31) >> 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* >> 1/0/0 A 192.168.31.190 (47) >> ... >> >> I will continue investigation. >> >> >> >> 2013/8/4 Pavel Timofeev : >>> Same thing on RELENG/9.2 >>> >>> 2013/8/3 Pavel Timofeev : >>>> 2013/8/2 Ruben de Groot : >>>>> On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: >>>>>> I've just installed new fresh 9.2-BETA2 amd64 on another machine. >>>>>> Same behaviour - Sendmail asks DNS only for AAAA record of mx server. >>>>>> We don't use IPv6 in our company. >>>>>> >>>>>> 2013/7/31 Pavel Timofeev : >>>>>> > I wanted to say that sendmail asks only AAAA (IPv6) record of mx >>>>>> > server, but not A (IPv4). >>>>>> > Any ideas? >>>>>> > >>>>>> > 2013/7/31 Pavel Timofeev : >>>>>> >> Looks like my sendmail uses only IPv6 to resolve mx server dns name to >>>>>> >> ip address. >>>>>> >> >>>>>> >> 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: >>>>>> >> 53417+ AAAA? xxx.ru. (24) >>>>>> >> [13/98] >>>>>> >> 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: >>>>>> >> 53417* 0/1/0 (75) >>>>>> >> 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: >>>>>> >> 53418+ A? xxx.ru. (24) >>>>> >>>>> Here it is definately asking an A record. >>>> >>>> And? It's not A record of mx server. >>>> >>>>>> >> 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: >>>>>> >> 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A >>>>>> >> 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 >>>>>> >> (136) >>>>> >>>>> And here is the reply. The quetion is more why is it repeating the same >>>>> query (below) over and over. >>>> >>>> Yes, reply about xxx.ru, not about mx server's IP which is kalmar.xxx.ru >>>> >>>>> >>>>> Ruben >>>>> >>>>>> >> 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: >>>>>> >> 53419+ MX? xxx.ru. (24) >>>>>> >> 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: >>>>>> >> 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) >>>>>> >> 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: >>>>>> >> 53420+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: >>>>>> >> 53420* 0/1/0 (82) >>>>>> >> 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: >>>>>> >> 53421+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: >>>>>> >> 53421* 0/1/0 (82) >>>>>> >> 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: >>>>>> >> 53422+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: >>>>>> >> 53422 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: >>>>>> >> 53422+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: >>>>>> >> 53422 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: >>>>>> >> 53423+ AAAA? kalmar.xxx.ru. (31) >>>>>> >> 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: >>>>>> >> 53423* 0/1/0 (82) >>>>>> >> 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: >>>>>> >> 53424+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: >>>>>> >> 53424 ServFail 0/0/0 (24) >>>>>> >> 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: >>>>>> >> 53424+ AAAA? kalmar. (24) >>>>>> >> 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: >>>>>> >> 53424 ServFail 0/0/0 (24) >>>>>> >> >>>>>> >> How to force it to use IPv4? >>>>>> _______________________________________________ >>>>>> freebsd-stable@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 17:10:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B03914FB for ; Mon, 5 Aug 2013 17:10:03 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C4F228B9 for ; Mon, 5 Aug 2013 17:10:02 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id hu16so1093641qab.3 for ; Mon, 05 Aug 2013 10:09:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=wl3ZMXEms6EloxvganyflLxI6K7T2//QAOy8ItVzUgc=; b=DDmg29ZZ9diVwGnrqC+Bkk2nygeGd4xy7RHDxvkBKLn6hP0DzFdyN5TRgtyznVIkrA G/Xe31MCV5r9zl+VA3ajcuS7UuLbxsEaVOXtBWO6NBTDae7yEf52PRmHSMpV4vAujP7N GKQJHD1ax1NQQEGJnJhFRtDtwQO2je1ARKrvzlZdOKGh/bCIdAQUD6TiaksydM2LeQkd RjUWhjT+dfpFDC1GCBZ5Hb4LN8Su8URlygcccv1Tb6Sri2c1Ii5/emZ50u65bUo+sdWW u+49k59UQkYmQA5fiLfvtz3wWekiFWzBnxPma0l7Gl3Fb1uXeAQmkGCR8Zbn+sUmDzW+ Vw3Q== X-Received: by 10.224.24.134 with SMTP id v6mr29330726qab.58.1375718820787; Mon, 05 Aug 2013 09:07:00 -0700 (PDT) Received: from [192.168.11.213] (ool-4a58bf32.dyn.optonline.net. [74.88.191.50]) by mx.google.com with ESMTPSA id nh4sm5136198qeb.6.2013.08.05.09.06.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 09:06:59 -0700 (PDT) References: <1710471570.3603170.1375141032147.JavaMail.root@uoguelph.ca> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <4166503B-C2FA-4FF4-9E2A-54874CA9EBF2@longcount.org> X-Mailer: iPhone Mail (10B329) From: Mark Saad Subject: Re: NFS deadlock on 9.2-Beta1 Date: Mon, 5 Aug 2013 12:06:58 -0400 To: J David X-Gm-Message-State: ALoCoQldbDL4IoxgNdHt5jo655pKm4QwJ2Lq7W8bxd8HeUBkoMQVeaFOBRnSv+C2E/D0wiu+HJmC Cc: Rick Macklem , "freebsd-stable@freebsd.org" , Michael Tratz , Steven Hartland , Konstantin Belousov , re X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 17:10:03 -0000 On Jul 29, 2013, at 10:48 PM, J David wrote: > If it is helpful, we have 25 nodes testing the 9.2-BETA1 build and > without especially trying to exercise this bug, we found > sendfile()-using processes deadlocked in WCHAN newnfs on 5 of the 25 > nodes. The ones with highest uptime (about 3 days) seem most > affected, so it does seem like a "sooner or later" type of thing. > Hopefully the fix is easy and it won't be an issue, but it definitely > does seem like a problem 9.2-RELEASE would be better off without. >=20 > Unfortunately we are not in a position to capture the requested > debugging information at this time; none of those nodes are running a > debug version of the kernel. If Michael is unable to get the > information as he hopes, we can try to do that, possibly over the > weekend. For the time being, we will convert half the machines to > rollback r250907 to try to confirm that resolves the issue. >=20 > Thanks all! If one has to encounter a problem like this, it is nice > to come to the list and find the research already so well underway! > ______________________________ All Is there any updates on this issue ? Has anyone tested it or see it happen= on the release candidate ?=20 --- Mark saad | mark.saad@longcount.org From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 17:30:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2246F10; Mon, 5 Aug 2013 17:30:50 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7FF942A57; Mon, 5 Aug 2013 17:30:50 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id f8so6141372obp.36 for ; Mon, 05 Aug 2013 10:30:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZqVcvnjX/d85SNM0Qew89T/43M3LEdJwuOxJlHHWk00=; b=PvfI56KK2gdMzF8D/H0KjFvyR9NM2Y/+ut5UTdyc3G9aHPW85yLASk212yqMrqbh53 Q3yIbMdvHQckIXxB5S6IujK02j8bVVhkVF1VtWZlLdkEdWo2MKXahme1eI+3pZBOsuds vXaIEjJJJBLfgWt2j1r7pCf5r5rBC0J0bLHrJD1mBCoWhZ+6lzZSrH7ckAui8bqXk7bP IHF3F3JTMN+XeeNW/fa5zTHzQ1tEYWWoSpSu6lA63v1asZzCvTOIy/9teYcNzTvaDH4o kpUb2ZI0vsiCdWSarYQJxDxQejQlI1zRAuUKP4LUz1aivHLFZGOEWMqqGlYizUMZT4O7 DoXQ== MIME-Version: 1.0 X-Received: by 10.50.178.133 with SMTP id cy5mr1182798igc.26.1375723848831; Mon, 05 Aug 2013 10:30:48 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Mon, 5 Aug 2013 10:30:48 -0700 (PDT) In-Reply-To: <4166503B-C2FA-4FF4-9E2A-54874CA9EBF2@longcount.org> References: <1710471570.3603170.1375141032147.JavaMail.root@uoguelph.ca> <4166503B-C2FA-4FF4-9E2A-54874CA9EBF2@longcount.org> Date: Mon, 5 Aug 2013 13:30:48 -0400 X-Google-Sender-Auth: y4d3fPHAi9N9aSbW0uoHK1Xuxsc Message-ID: Subject: Re: NFS deadlock on 9.2-Beta1 From: J David To: Mark Saad Content-Type: text/plain; charset=ISO-8859-1 Cc: Rick Macklem , "freebsd-stable@freebsd.org" , Michael Tratz , Steven Hartland , Konstantin Belousov , re X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 17:30:50 -0000 On Mon, Aug 5, 2013 at 12:06 PM, Mark Saad wrote: > Is there any updates on this issue ? Has anyone tested it or see it happen on the release candidate ? It's a bit premature for that; the RC has been out for a few hours. We put BETA2 on 25 nodes and only saw the problem on five after 24 hours. At that point we switched to a build that reverts the patch that causes the deadlock and no node on which that was done (at this point, all of them) has had the problem since. We'll get some machines on releng/9.2 today, but I didn't see anything in the release candidate announcement to indicate that relevant changes had been made. Is there anything in the release candidate that is believe to address this issue? If so, let us know with svn revision it's in and we'll try to accelerate test deployment. Thanks! From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 17:36:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0A12B645 for ; Mon, 5 Aug 2013 17:36:43 +0000 (UTC) (envelope-from boland37@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id 9EE912ABA for ; Mon, 5 Aug 2013 17:36:42 +0000 (UTC) Received: from charlemagne.boland.org (37-251-73-96.FTTH.ispfabriek.nl [37.251.73.96]) (authenticated bits=0) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id r75HaeQ9075445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Aug 2013 19:36:41 +0200 (CEST) (envelope-from boland37@xs4all.nl) Message-ID: <51FFE2A8.3040504@xs4all.nl> Date: Mon, 05 Aug 2013 19:36:40 +0200 From: Michiel Boland User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130705 Thunderbird/17.0.7 MIME-Version: 1.0 To: FreeBSD Stable Subject: 9.2-RC1 sparc install via network problems Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 17:36:43 -0000 Hi. I have some problems installing 9.2-RC1 on sparc64 via the network I have a dhcp server, and an NFS server that exports the disc1 ISO. Relevant portions of dhcpd.conf: filename "boot/loader"; option root-path ":/cdrom"; The boot/loader was copied from the install image. The tftpboot directory is otherwise empty. (So no loader.conf etc.) First I tried booting an Ultra10. That paniced immediately isp0: port 0x1000-0x10ff mem 0x2808000-0x2808fff at device 4.0 on pci3 isp0: invalid NVRAM header isp1: port 0x2000-0x20ff mem 0x2900000-0x2900fff at device 2.0 on pci2 panic: trap: data access error (kernel) cpuid = 0 KDB: stack backtrace: #0 0xc08588b4 at trap+0x554 Uptime: 1s This may be a hardware thing so I did not pursue this further. Maybe Ultra10 is no longer supported, I don't know. (Ultra10s are crap anyway :) Next I tried netbooting a V-120. That at least did not panic, but instead of starting the installer it produced this message on the console cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ... Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19. Trying to mount root from nfs: []... At which point all I get is a single-user shell. Is installing via the network supported at all with the new bsd installer? Any magic loader options I need to get this to work? Cheers Michiel From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 21:26:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5F95368 for ; Mon, 5 Aug 2013 21:26:12 +0000 (UTC) (envelope-from dave@mischler.com) Received: from teaspoon.mischlersflorist.com (rrcs-72-45-221-198.nys.biz.rr.com [72.45.221.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7663F2926 for ; Mon, 5 Aug 2013 21:26:12 +0000 (UTC) Received: from [192.168.163.29] ([192.168.163.29]) by teaspoon.mischlersflorist.com (8.14.7/8.14.5) with ESMTP id r75LFGPN020101 for ; Mon, 5 Aug 2013 17:15:16 -0400 (EDT) (envelope-from dave@mischler.com) Subject: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 From: Dave Mischler To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" Date: Mon, 05 Aug 2013 17:15:16 -0400 Message-ID: <1375737316.96778.10.camel@firkin.mischler.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dave@mischler.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 21:26:12 -0000 I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the GENERIC kernel. Today, while still running 9.2-BETA2, I updated my source tree and started building world with idprio 31 and I looked back a while later and all the CPU cores and disk were essentially idle, and hardly any progress had been made on the build. I stopped and restarted the build without the idle priority setting and it ran fine. Anybody else seen any of this? Anybody know about any fairly recent changes that might account for it? I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before going to RC1. I still see odd behavior at RC1. Sometimes it works just like it should (i.e. compute bound processes use most/all of the available CPU time), but a lot of the time both the CPU and disk are idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I ever saw this behavior before while running "make buildworld -j4". Can anyone else confirm/rebut my findings? Thanks. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 5 23:54:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8D44241E; Mon, 5 Aug 2013 23:54:53 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D3A92E7D; Mon, 5 Aug 2013 23:54:53 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id o6so7673135oag.41 for ; Mon, 05 Aug 2013 16:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GWruLmnZJnmdL7kC6kOWjB516G6nir/DsaLTNt9pwGA=; b=xsh/LhSdlpobXwUzCsi/VAeQm1TLfCQq/U/WUPlr7NymWiOoo9s9E6YgWemeg3X9Dd wMgOe1IhXC24jU0GiF0PhOdF/Lhhine3hqLCaCPoXPSl5JQMWFS8vM4CQBN7+syKxz2l GBfzJN83v4uyRwrB0VMtzo8GhtS3Rn1ZW9V9u3yxhAHiqrgoS89dFUXc9bN8H+puad48 sP3aD1fTypOT+hauJ6y4jvfhf2FNE5uWbMC+ey7fjF6yDAE/7iL5SXlfKk9tR8VqLQZO +ejUN77g8yOgtrzY+X/ngmutTpND0cF59FKv60rFH0/HkBRY3fuXrtKs3FosDbqFZWvw moTw== MIME-Version: 1.0 X-Received: by 10.50.12.5 with SMTP id u5mr1224igb.58.1375746892480; Mon, 05 Aug 2013 16:54:52 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Mon, 5 Aug 2013 16:54:52 -0700 (PDT) In-Reply-To: <51FD5709.7050306@FreeBSD.org> References: <51FD5709.7050306@FreeBSD.org> Date: Mon, 5 Aug 2013 19:54:52 -0400 X-Google-Sender-Auth: WNKHATG8h1-waoYgi6UuxYApwCg Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 23:54:53 -0000 On Sat, Aug 3, 2013 at 3:16 PM, Andriy Gapon wrote: > Very unusual. Would you be able to try 9.2 zfsloader again? Surely. > I would like to see values of loaddev, currdev and vfs.zfs.boot.primary_pool > loader variables (if any are set). These can be obtained using 'show' command > at loader prompt. OK show loaddev OK show currdev OK show vfs.zfs.boot.primary_pool 2022708996989799150 > Also, output of lsdev -v. OK lsdev -v cd devices: disk devices: disk0: BIOS drive C: disk0p1: FreeBSD boot 64KB disk0p2: FreeBSD swap 2048MB disk0p3: FreeBSD ZFS 28GB disk1: BIOS drive D: disk1p1: FreeBSD boot 64KB disk1p2: FreeBSD swap 2048MB disk1p3: FreeBSD ZFS 27GB disk2: BIOS drive E: disk3: BIOS drive F: disk4: BIOS drive G: disk5: BIOS drive H: disk6: BIOS drive I: disk7: BIOS drive J: pxe devices: zfs devices: OK > Also, if you are able to build custom 9.2 zfsloader, then it would be useful to > modify the printf statement (in zfs_fmtdev(), sys/boot/zfs/zfs.c) to print > dev->pool_guid. This didn't produce the expected result. Slipped it into the 9.2-RC1 build, rebuilt, installed it, but nothing changed. In order to get it to load, we removed zfsloader, storing the 8.4 version as zfsloader-8.4 and installing the 9.2-RC1 zfsloader as zfsloader-9.2. Then, when the gptzfsboot can't find /boot/zfsloader, I entered zfsloader-9.2 at the prompt. It does the same thing, with the same message: ZFS: can't find pool by guid Even though I changed the source as you suggested: Index: zfs.c =================================================================== --- zfs.c (revision 253967) +++ zfs.c (working copy) @@ -645,7 +645,7 @@ } else spa = spa_find_by_guid(dev->pool_guid); if (spa == NULL) { - printf("ZFS: can't find pool by guid\n"); + printf("ZFS: can't find pool by guid: %llX\n", dev->pool_guid); return (buf); } if (dev->root_guid == 0 && zfs_get_root(spa, &dev->root_guid)) { So I can't figure out why the message didn't change. Doing a full buildworld buildkernel right now in case the problem is just that I don't know how to selectively build this. Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 00:01:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5D06058F; Tue, 6 Aug 2013 00:01:04 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1C2282EBD; Tue, 6 Aug 2013 00:01:04 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id m1so7799129oag.32 for ; Mon, 05 Aug 2013 17:01:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=b+P4xQCKgSYbHPMuU88guTtZesHt6M1092/mcNccl/w=; b=TcLghgeTRhgBH9MwyVLsI0NOSJIBtCseRbkQ8T1+GsrAlK5W27bu5GsmQ3ryHzpi+9 2FE2KP5jSAWyLRKzvjdT333pumeb8xQCyTjicmVMj8jETuikc+0+/u9L92qMq305Wcl7 TLcPP+QUl4FYJNS3JTPO/4E7i+9ZliS33E7NPmmOG3u7mgWygB1q3iRz/Jv45Cmh3LUh J6yvoo9Dpmu2CC6oB+uJYNZpbf1RIwoy4BvEn4N87147Qf12V9ZOWV+WfSGLpPBCQG1L GkLmjsCGuCyVZm5DKOPiiFRX/Lu+cgiRjnDtbA1NUoIm64Zsxhkli9u13BsXSgosdbYR x3iQ== MIME-Version: 1.0 X-Received: by 10.50.153.109 with SMTP id vf13mr2808igb.58.1375747263413; Mon, 05 Aug 2013 17:01:03 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Mon, 5 Aug 2013 17:01:03 -0700 (PDT) In-Reply-To: References: <51FD5709.7050306@FreeBSD.org> Date: Mon, 5 Aug 2013 20:01:03 -0400 X-Google-Sender-Auth: GoN9T4vRBIJjUF6pxgBVpEkB9M0 Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 00:01:04 -0000 On Mon, Aug 5, 2013 at 7:54 PM, J David wrote: > OK show vfs.zfs.boot.primary_pool > 2022708996989799150 I should add that this is indeed the correct guid for the pool: $ zpool get guid NAME PROPERTY VALUE SOURCE data guid 2022708996989799150 default Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 01:53:47 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9105B6B5 for ; Tue, 6 Aug 2013 01:53:47 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 119422213 for ; Tue, 6 Aug 2013 01:53:46 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.7/8.14.7/ALCHEMY.FRANKEN.DE) with ESMTP id r761rilD063169; Tue, 6 Aug 2013 03:53:44 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.7/8.14.7/Submit) id r761ric6063168; Tue, 6 Aug 2013 03:53:44 +0200 (CEST) (envelope-from marius) Date: Tue, 6 Aug 2013 03:53:44 +0200 From: Marius Strobl To: Michiel Boland Subject: Re: 9.2-RC1 sparc install via network problems Message-ID: <20130806015344.GA62529@alchemy.franken.de> References: <51FFE2A8.3040504@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FFE2A8.3040504@xs4all.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 01:53:47 -0000 On Mon, Aug 05, 2013 at 07:36:40PM +0200, Michiel Boland wrote: > Hi. I have some problems installing 9.2-RC1 on sparc64 via the network > > I have a dhcp server, and an NFS server that exports the disc1 ISO. > > Relevant portions of dhcpd.conf: > > filename "boot/loader"; > option root-path ":/cdrom"; > > The boot/loader was copied from the install image. The tftpboot directory is > otherwise empty. (So no loader.conf etc.) Do you also have 'next-server' in there? I'm buffled how TFTPing the loader could work without one ... > > First I tried booting an Ultra10. That paniced immediately > > isp0: port 0x1000-0x10ff mem > 0x2808000-0x2808fff at device 4.0 on pci3 > isp0: invalid NVRAM header > isp1: port 0x2000-0x20ff mem > 0x2900000-0x2900fff at device 2.0 on pci2 > panic: trap: data access error (kernel) > cpuid = 0 > KDB: stack backtrace: > #0 0xc08588b4 at trap+0x554 > Uptime: 1s > > This may be a hardware thing so I did not pursue this further. Maybe Ultra10 is > no longer supported, I don't know. (Ultra10s are crap anyway :) U10 are still supported, why should they have been dropped? :) In fact, the 9.2 images have been tested on a U10 before they were published. I also found an ISP 1040 card, which works just fine here. So this indeed could be a hardware problem causing a PCI access to fail, which typically causes very strange backtraces like the incomplete one above. > > Next I tried netbooting a V-120. That at least did not panic, but instead of > starting the installer it produced this message on the console > > cd0: Attempt to query device size failed: NOT READY, Medium not present > Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... > mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ... > Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19. So far, that's expected as you seem to also have copied over the /etc/fstab from disc1. > Trying to mount root from nfs: []... > > At which point all I get is a single-user shell. > > Is installing via the network supported at all with the new bsd installer? Any > magic loader options I need to get this to work? > According to the /etc/rc.local that ends up on the ISO 9660 file system of the release images, netbooted installing indeed was thought of when these were switched to bsdinstall(8). Given that just copying over that one file to a NFS root properly fires up bsdinstall(8) after booting here and given that your netboot environment apparently also works just fine - except you refer to the mountroot prompt as single-user shell -, I've no idea what could be going wrong in your case ... Marius From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 03:24:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD6178E2; Tue, 6 Aug 2013 03:24:41 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 89B882515; Tue, 6 Aug 2013 03:24:41 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id ef5so7114912obb.23 for ; Mon, 05 Aug 2013 20:24:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=RnUx8oJEtwIpOSWGLQCgqlCfaUp6wtyylZLYdHBb9oE=; b=BtrnZwIJUbaHO/8omomTZvg+0wP5St3tb8G/ow0OfQVxiWjXXIHm13YUdIe4I8+3YC ZSJeZ4+b1fr+m368e/CAie8VAFZyxS+Stu+uwiPkVeyaYbyikSuDXxaTe91a9KH+0KeG s/9pMTKuyUatbK2MgNEoG7JxK1jE5MlP0W4+Y+/1T2uRMKtFdM9HP1l3DN1lfsLFmVFA xKXh3VelXodN/I8lX32HB56HRL47wzO4O01WAnOs14yvwMTyLB0/qTj0FV45tCcRGcRV 2U6KRPLtqqdMAgsZptv/fBC+o5WAbdTdzmi7+sJbYwzIkkrRxskuFu8L9IEi8tRY+WIl pwXA== MIME-Version: 1.0 X-Received: by 10.50.178.234 with SMTP id db10mr71485igc.35.1375759480867; Mon, 05 Aug 2013 20:24:40 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Mon, 5 Aug 2013 20:24:40 -0700 (PDT) In-Reply-To: References: <51FD5709.7050306@FreeBSD.org> Date: Mon, 5 Aug 2013 23:24:40 -0400 X-Google-Sender-Auth: c_0LBy26PId4Mv0NkAe3P48kBGE Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 03:24:41 -0000 On Mon, Aug 5, 2013 at 8:01 PM, J David wrote: > I should add that this is indeed the correct guid for the pool: > > $ zpool get guid > NAME PROPERTY VALUE SOURCE > data guid 2022708996989799150 default After a full make buildworld installworld, I finally got the revised output: ZFS: can't find pool by guid: 1C121B1DB1904AEE ZFS: can't find pool by guid: 1C121B1DB1904AEE (0x1C121B1DB1904AEE == 2022708996989799150) Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 05:58:51 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 47101A4E for ; Tue, 6 Aug 2013 05:58:51 +0000 (UTC) (envelope-from boland37@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.freebsd.org (Postfix) with ESMTP id DD7572988 for ; Tue, 6 Aug 2013 05:58:50 +0000 (UTC) Received: from charlemagne.boland.org (37-251-73-96.FTTH.ispfabriek.nl [37.251.73.96]) (authenticated bits=0) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id r765wgk4066100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 07:58:43 +0200 (CEST) (envelope-from boland37@xs4all.nl) Message-ID: <52009092.8000806@xs4all.nl> Date: Tue, 06 Aug 2013 07:58:42 +0200 From: Michiel Boland User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130705 Thunderbird/17.0.7 MIME-Version: 1.0 To: Marius Strobl Subject: Re: 9.2-RC1 sparc install via network problems References: <51FFE2A8.3040504@xs4all.nl> <20130806015344.GA62529@alchemy.franken.de> In-Reply-To: <20130806015344.GA62529@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 05:58:51 -0000 On 08/06/2013 03:53, Marius Strobl wrote: > On Mon, Aug 05, 2013 at 07:36:40PM +0200, Michiel Boland wrote: >> Hi. I have some problems installing 9.2-RC1 on sparc64 via the network >> >> I have a dhcp server, and an NFS server that exports the disc1 ISO. >> >> Relevant portions of dhcpd.conf: >> >> filename "boot/loader"; >> option root-path ":/cdrom"; >> >> The boot/loader was copied from the install image. The tftpboot directory is >> otherwise empty. (So no loader.conf etc.) > > Do you also have 'next-server' in there? I'm buffled how TFTPing > the loader could work without one ... There is a next-server line; it was in another location in the dhcpd.conf, so I did not think to copy that, sorry. [...] > U10 are still supported, why should they have been dropped? :) > In fact, the 9.2 images have been tested on a U10 before they were > published. I also found an ISP 1040 card, which works just fine > here. > So this indeed could be a hardware problem causing a PCI access to > fail, which typically causes very strange backtraces like the > incomplete one above. Ok. I'll take out the pci cards - let's see if I can get it to boot then. > So far, that's expected as you seem to also have copied over the > /etc/fstab from disc1. Right. I thought I could take a shortcut by just mdconfig-ing the install image and mounting and exporting that. Cheers Michiel From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 09:57:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9B543FB0; Tue, 6 Aug 2013 09:57:13 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward1l.mail.yandex.net (forward1l.mail.yandex.net [IPv6:2a02:6b8:0:1819::1]) by mx1.freebsd.org (Postfix) with ESMTP id 580822433; Tue, 6 Aug 2013 09:57:12 +0000 (UTC) Received: from smtp19.mail.yandex.net (smtp19.mail.yandex.net [95.108.252.19]) by forward1l.mail.yandex.net (Yandex) with ESMTP id 3D9B41520FA5; Tue, 6 Aug 2013 13:57:10 +0400 (MSK) Received: from smtp19.mail.yandex.net (localhost [127.0.0.1]) by smtp19.mail.yandex.net (Yandex) with ESMTP id CF495BE05EC; Tue, 6 Aug 2013 13:57:09 +0400 (MSK) Received: from v10-164-213.yandex.net (v10-164-213.yandex.net [84.201.164.213]) by smtp19.mail.yandex.net (nwsmtp/Yandex) with ESMTP id qykWYSAXhD-v98C8ig3; Tue, 6 Aug 2013 13:57:09 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1375783029; bh=5gZJpgAsIy3v6QJs0TnECgWEiTfsnn7dPV3C/UfID1Y=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=bXngw2JH+f7gjbRWScPE9T/W3T6jX7ocWOXsbXynPD9MBdDXBcdLbeJsG4Cy9F1BK VXVCBTnwC8pGGQtXJkhnelKSIsplwRKM0y3DewyLf7XIYDdr+QjnbKcze7Z6XPqZ13 B5ePswo4JRGTXKsDPPqZu9nho1plogVGbR2tQgPA= Authentication-Results: smtp19.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5200C7A3.3070403@yandex.ru> Date: Tue, 06 Aug 2013 13:53:39 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: J David Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 09:57:13 -0000 On 06.08.2013 03:54, J David wrote: > OK lsdev -v > cd devices: > disk devices: > disk0: BIOS drive C: > disk0p1: FreeBSD boot 64KB > disk0p2: FreeBSD swap 2048MB > disk0p3: FreeBSD ZFS 28GB > disk1: BIOS drive D: > disk1p1: FreeBSD boot 64KB > disk1p2: FreeBSD swap 2048MB > disk1p3: FreeBSD ZFS 27GB > disk2: BIOS drive E: > disk3: BIOS drive F: > disk4: BIOS drive G: > disk5: BIOS drive H: > disk6: BIOS drive I: > disk7: BIOS drive J: Hi, looking to your `zfs status` output and this, we can see, that GPT wasn't detected on most of disks. Can you try to boot with this loader: http://people.freebsd.org/~ae/zfsloader It's from 10-CURRENT and was build with -DPART_DEBUG, so you will see some additional debug messages while booting. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 10:29:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 05033552; Tue, 6 Aug 2013 10:29:22 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4l.mail.yandex.net (forward4l.mail.yandex.net [IPv6:2a02:6b8:0:1819::4]) by mx1.freebsd.org (Postfix) with ESMTP id B3D3F2585; Tue, 6 Aug 2013 10:29:21 +0000 (UTC) Received: from smtp16.mail.yandex.net (smtp16.mail.yandex.net [95.108.252.16]) by forward4l.mail.yandex.net (Yandex) with ESMTP id 0CE5B14415A6; Tue, 6 Aug 2013 14:29:17 +0400 (MSK) Received: from smtp16.mail.yandex.net (localhost [127.0.0.1]) by smtp16.mail.yandex.net (Yandex) with ESMTP id A34076A06F2; Tue, 6 Aug 2013 14:29:17 +0400 (MSK) Received: from v10-164-213.yandex.net (v10-164-213.yandex.net [84.201.164.213]) by smtp16.mail.yandex.net (nwsmtp/Yandex) with ESMTP id WuNTeCEygr-THOKCrXN; Tue, 6 Aug 2013 14:29:17 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1375784957; bh=6yR/tvzuIx6cvr70B0tBAqHXqYaIIgxoTGBmNfGRX9M=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=nShZf5HJY/xKw8cob+wvlQdYj9tk91MRpLlBEq9a5zHoQHCqOFUGfO09apuzIUMou 0zz46d2FrI0bTS4itK7BjZHHZj5HIpZyIoxHyPOIdZ1d5qn+fCSTiQXx8oElgwZ57F nBhc21LrQ1ap32WPx0WOitQ5xhoGQ7SD7QNy09U0= Authentication-Results: smtp16.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5200CF2B.6060602@yandex.ru> Date: Tue, 06 Aug 2013 14:25:47 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: J David Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> In-Reply-To: <5200C7A3.3070403@yandex.ru> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 10:29:22 -0000 On 06.08.2013 13:53, Andrey V. Elsukov wrote: >> disk5: BIOS drive H: >> disk6: BIOS drive I: >> disk7: BIOS drive J: > > Hi, > > looking to your `zfs status` output and this, we can see, that GPT > wasn't detected on most of disks. Can you try to boot with this loader: > http://people.freebsd.org/~ae/zfsloader > It's from 10-CURRENT and was build with -DPART_DEBUG, so you will see > some additional debug messages while booting. Also, you can build src/tools/tools/bootparttest utility and try to read each disk to be sure that there aren't any errors in the metadata. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 11:10:07 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 40C4252F; Tue, 6 Aug 2013 11:10:07 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E662727AF; Tue, 6 Aug 2013 11:10:06 +0000 (UTC) Received: by mail-vb0-f43.google.com with SMTP id h11so214301vbh.16 for ; Tue, 06 Aug 2013 04:10:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=hDnJcToR480QyfQmFdWsH6LKxUMTEO+ewIKSN2aPCAI=; b=fMsfGJsvyKIH6NKuwLa0iiIDGMQknlCiQ60K0JzpZsoQz6x1HakyP8wuq7i0rbyBFo USx3Bx4yowlgRXyDWm1mTx1c2JCDNvRhkmWg1n+3mAsiyHSuByAEuK7m6As2AyKtnhvW 16PTX9f69xsu3213QStfb+4MEpKskzoiPWH9/LZHUY5e89e+U9cqV9JIm3BHoXNzzEF6 gCZGmnHXYMhPuu4p/Ma5mauYP5f3NRUd9DsmqKoCCHFqtHmKuF7Hwl76+aLn2CncymyN 08EAKfinkj+poW9tjAg07+92mLCqtTUI4Uuzf4gKX/LrEvt/WhjrvkkoG+Cjpcb9VNv9 K9Zg== MIME-Version: 1.0 X-Received: by 10.58.85.161 with SMTP id i1mr177338vez.97.1375787405656; Tue, 06 Aug 2013 04:10:05 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Tue, 6 Aug 2013 04:10:05 -0700 (PDT) Date: Tue, 6 Aug 2013 15:10:05 +0400 Message-ID: Subject: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: gshapiro@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 11:10:07 -0000 Hello! I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS you won't receive it. But in same time email passes from FreeBSD 9.1-RELEASE which uses Sendmail-8.14.5. It's because of two things. First thing: Sendmail behaviour changed between these two releases when it tries to resolve mx server name. For example, I did `echo foo | mail timp@xxx.ru`. Sendmail-8.14.5's tcpdump output: 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ MX? xxx.ru. (24) 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* 1/0/1 MX kalmar.xxx.ru. 10 (63) 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ AAAA? kalmar.xxx.ru. (31) 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? kalmar.xxx.ru. (31) 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* 1/0/0 A 192.168.31.190 (47) 14:30:45.066014 IP 10.0.2.15.42197 > hercules.xxx.ru.domain: 62687+ A? kalmar.xxx.ru. (31) 14:30:45.066810 IP hercules.xxx.ru.domain > 10.0.2.15.42197: 62687* 1/0/0 A 192.168.31.190 (47) 14:30:45.071833 IP 10.0.2.15.23534 > hercules.xxx.ru.domain: 62688+ PTR? 15.2.0.10.in-addr.arpa. (40) Sendmail-8.14.7's tcpdump output: 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: 53417+ AAAA? xxx.ru. (24) [13/98] 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: 53417* 0/1/0 (75) 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: 53418+ A? xxx.ru. (24) 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 (136) 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: 53419+ MX? xxx.ru. (24) 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: 53420+ AAAA? kalmar.xxx.ru. (31) 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: 53420* 0/1/0 (82) 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: 53421+ AAAA? kalmar.xxx.ru. (31) 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: 53421* 0/1/0 (82) 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: 53422+ AAAA? kalmar. (24) 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: 53422 ServFail 0/0/0 (24) 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: 53422+ AAAA? kalmar. (24) 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: 53422 ServFail 0/0/0 (24) 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: 53423+ AAAA? kalmar.xxx.ru. (31) 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: 53423* 0/1/0 (82) 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: 53424+ AAAA? kalmar. (24) 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: 53424 ServFail 0/0/0 (24) 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: 53424+ AAAA? kalmar. (24) 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: 53424 ServFail 0/0/0 (24) All of them asked MX and got it - kalmar.xxx.ru. Then they went to resolve kalmar.xxx.ru. Sendmail-8.14.5 asked one time for 'AAAA kalmar.xxx.ru.' and then went to ask 'A kalmar.xxx.ru.'. But Sendmail-8.15.7 asked several times for 'AAAA kalmar.xxx.ru.' and then went to ask 'AAAA kalmar.' Without xxx.ru at then end, just servername. What for? I don't know. This is change. And yes, sendmail ignored ADDITIONAL SECTION from MX record and tried to resolve mx server name independently. Second thing: Sendmail-8.15.7 doesn't work with MS DNS in IPv4 network. MS DNS answers SERVFAIL on 'AAAA kalmar.' But BIND answers NXDOMAIN on same query. In case of SERVFAIL answer Sendmail never goes to ask for any A records. It tries to resolve 'AAAA kalmar.' again and again. In case of NXDOMAIN answer Sendmail goes to ask for A record and no problem. I checked it, set BIND server as DNS server for this test host. In my network there are only MS DNS servers. I tried to install sendmail-8.14.5 on FreeBSD 9.2-RC1 and got no problem with email. I tried to use ip6addrctl. No effect. So what we gonna do? There will be so many crying persons in mailinglist after 9.2-RELEASE I think) P.S. here is russian version small discussion http://ru-freebsd.livejournal.com/226451.html From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 12:47:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1221ABB2; Tue, 6 Aug 2013 12:47:45 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B43932CB5; Tue, 6 Aug 2013 12:47:44 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id cz11so331525veb.22 for ; Tue, 06 Aug 2013 05:47:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xliOoLy+eP+VgKhItLTgppqFtTUU9xyIbz6eFvdIzf8=; b=sEXmk6WN4qIZUiuOLcITBs6HOmipKM/Fyld72rxF20bs2XFr0/An0S57IMy/T0JsRj dibsxLN4BdFx2A00zOQ1DIWLIH4Vm35UI1s7Fd4X2nfvwsa6uOrvUWvHmXjTzz3vE6dR foq3/Mru5beXgj145QZu5Uar0Lr0sfIFPNndVftrCUfBcBEkjzuk6ReAYZqgvssYkHM4 04RLjW2anrgl1HFK65M2/uhC0EHBK7psf7i/IVgihhgjhBgeCVgNlIPR/hAMvqPwPhmO FPFqjycwrVWNpFwk6cxGHPl1ySo+VmyDC1rFNpb/DOkJn0Yr5Hh7kN767NBK8XIfAQIX aaxQ== MIME-Version: 1.0 X-Received: by 10.52.115.102 with SMTP id jn6mr286513vdb.18.1375793263690; Tue, 06 Aug 2013 05:47:43 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Tue, 6 Aug 2013 05:47:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Aug 2013 16:47:43 +0400 Message-ID: Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: gshapiro@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 12:47:45 -0000 I know about WorkAroundBrokenAAAA. I used default system configuration of sendmail so WorkAroundBrokenAAAA was set by default. 2013/8/6 Pavel Timofeev : > Hello! > > I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. > If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS > you won't receive it. > But in same time email passes from FreeBSD 9.1-RELEASE which uses > Sendmail-8.14.5. > > It's because of two things. > > First thing: Sendmail behaviour changed between these two releases > when it tries to resolve mx server name. For example, I did `echo foo > | mail timp@xxx.ru`. > > Sendmail-8.14.5's tcpdump output: > 14:30:45.061950 IP 10.0.2.15.30979 > hercules.xxx.ru.domain: 62684+ > MX? xxx.ru. (24) > 14:30:45.063064 IP hercules.xxx.ru.domain > 10.0.2.15.30979: 62684* > 1/0/1 MX kalmar.xxx.ru. 10 (63) > 14:30:45.063624 IP 10.0.2.15.39212 > hercules.xxx.ru.domain: 62685+ > AAAA? kalmar.xxx.ru. (31) > 14:30:45.064460 IP hercules.xxx.ru.domain > 10.0.2.15.39212: 62685* 0/1/0 (82) > 14:30:45.064766 IP 10.0.2.15.44381 > hercules.xxx.ru.domain: 62686+ A? > kalmar.xxx.ru. (31) > 14:30:45.065530 IP hercules.xxx.ru.domain > 10.0.2.15.44381: 62686* > 1/0/0 A 192.168.31.190 (47) > 14:30:45.066014 IP 10.0.2.15.42197 > hercules.xxx.ru.domain: 62687+ A? > kalmar.xxx.ru. (31) > 14:30:45.066810 IP hercules.xxx.ru.domain > 10.0.2.15.42197: 62687* > 1/0/0 A 192.168.31.190 (47) > 14:30:45.071833 IP 10.0.2.15.23534 > hercules.xxx.ru.domain: 62688+ > PTR? 15.2.0.10.in-addr.arpa. (40) > > > Sendmail-8.14.7's tcpdump output: > 14:59:50.793338 IP reticulum.xxx.ru.19032 > hercules.xxx.ru.domain: > 53417+ AAAA? xxx.ru. (24) [13/98] > 14:59:50.793662 IP hercules.xxx.ru.domain > reticulum.xxx.ru.19032: > 53417* 0/1/0 (75) > 14:59:50.793696 IP reticulum.xxx.ru.55299 > hercules.xxx.ru.domain: > 53418+ A? xxx.ru. (24) > 14:59:50.794087 IP hercules.xxx.ru.domain > reticulum.xxx.ru.55299: > 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A > 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 (136) > 14:59:50.973445 IP reticulum.xxx.ru.29244 > hercules.xxx.ru.domain: > 53419+ MX? xxx.ru. (24) > 14:59:50.973754 IP hercules.xxx.ru.domain > reticulum.xxx.ru.29244: > 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) > 14:59:50.974061 IP reticulum.xxx.ru.56461 > hercules.xxx.ru.domain: > 53420+ AAAA? kalmar.xxx.ru. (31) > 14:59:50.974340 IP hercules.xxx.ru.domain > reticulum.xxx.ru.56461: > 53420* 0/1/0 (82) > 14:59:50.974570 IP reticulum.xxx.ru.28332 > hercules.xxx.ru.domain: > 53421+ AAAA? kalmar.xxx.ru. (31) > 14:59:50.974887 IP hercules.xxx.ru.domain > reticulum.xxx.ru.28332: > 53421* 0/1/0 (82) > 14:59:50.974919 IP reticulum.xxx.ru.21453 > hercules.xxx.ru.domain: > 53422+ AAAA? kalmar. (24) > 14:59:50.975290 IP hercules.xxx.ru.domain > reticulum.xxx.ru.21453: > 53422 ServFail 0/0/0 (24) > 14:59:50.975314 IP reticulum.xxx.ru.63038 > hercules.xxx.ru.domain: > 53422+ AAAA? kalmar. (24) > 14:59:50.975674 IP hercules.xxx.ru.domain > reticulum.xxx.ru.63038: > 53422 ServFail 0/0/0 (24) > 14:59:50.975749 IP reticulum.xxx.ru.38393 > hercules.xxx.ru.domain: > 53423+ AAAA? kalmar.xxx.ru. (31) > 14:59:50.976105 IP hercules.xxx.ru.domain > reticulum.xxx.ru.38393: > 53423* 0/1/0 (82) > 14:59:50.976176 IP reticulum.xxx.ru.45558 > hercules.xxx.ru.domain: > 53424+ AAAA? kalmar. (24) > 14:59:50.976483 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45558: > 53424 ServFail 0/0/0 (24) > 14:59:50.976512 IP reticulum.xxx.ru.45297 > hercules.xxx.ru.domain: > 53424+ AAAA? kalmar. (24) > 14:59:50.976864 IP hercules.xxx.ru.domain > reticulum.xxx.ru.45297: > 53424 ServFail 0/0/0 (24) > > > All of them asked MX and got it - kalmar.xxx.ru. Then they went to > resolve kalmar.xxx.ru. > Sendmail-8.14.5 asked one time for 'AAAA kalmar.xxx.ru.' and then went > to ask 'A kalmar.xxx.ru.'. > But Sendmail-8.15.7 asked several times for 'AAAA kalmar.xxx.ru.' and > then went to ask 'AAAA kalmar.' Without xxx.ru at then end, just > servername. What for? I don't know. This is change. > And yes, sendmail ignored ADDITIONAL SECTION from MX record and tried > to resolve mx server name independently. > > > > Second thing: Sendmail-8.15.7 doesn't work with MS DNS in IPv4 network. > MS DNS answers SERVFAIL on 'AAAA kalmar.' > But BIND answers NXDOMAIN on same query. > In case of SERVFAIL answer Sendmail never goes to ask for any A > records. It tries to resolve 'AAAA kalmar.' again and again. > In case of NXDOMAIN answer Sendmail goes to ask for A record and no problem. > I checked it, set BIND server as DNS server for this test host. > > In my network there are only MS DNS servers. > I tried to install sendmail-8.14.5 on FreeBSD 9.2-RC1 and got no > problem with email. > I tried to use ip6addrctl. No effect. > > So what we gonna do? There will be so many crying persons in > mailinglist after 9.2-RELEASE I think) > > P.S. here is russian version small discussion > http://ru-freebsd.livejournal.com/226451.html From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 13:45:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6158C78 for ; Tue, 6 Aug 2013 13:45:57 +0000 (UTC) (envelope-from lausts@acm.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3362F3B for ; Tue, 6 Aug 2013 13:45:57 +0000 (UTC) X-Authority-Analysis: v=2.0 cv=KJ7Y/S5o c=1 sm=0 a=xRdgvQXv5AerPAHtJUV3Bw==:17 a=i3v0hNX2wH8A:10 a=kWQ6D_09QQAA:10 a=kHc8Q_KJ-KsA:10 a=N54-gffFAAAA:8 a=KGjhK52YXX0A:10 a=SK-8MZRCJncA:10 a=IcfkkVo58H4NOCgLXB4A:9 a=xRdgvQXv5AerPAHtJUV3Bw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 184.58.98.36 Received: from [184.58.98.36] ([184.58.98.36:60505] helo=mail.laus.org) by hrndva-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 18/D9-02415-F0EF0025; Tue, 06 Aug 2013 13:45:51 +0000 Received: from [192.168.1.100] (laust2 [192.168.1.100]) by mail.laus.org (8.14.7/8.14.7) with ESMTP id r76DjoJT001549 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Aug 2013 09:45:51 -0400 (EDT) (envelope-from lausts@acm.org) From: "Thomas Laus" Organization: ABB To: freebsd-stable@freebsd.org Date: Tue, 06 Aug 2013 09:45:50 -0400 Subject: FreeBSD-Update + Sendmail Message-ID: <5200FE0E.8506.5CB69E@lausts.acm.org> Priority: normal X-mailer: Pegasus Mail for Windows (4.63) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lausts@acm.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 13:45:57 -0000 I have been updating my FreeBSD systems for many years by updating and building from source. For the FreeBSD 9.2 cycle, I decided to use freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL and the freebsd-update process only installed a 'bare bones' binary. How do I compile just Sendmail from source so that it uses my /etc/make.conf for the smtp_auth components? Is there a freebsd-update.conf flag to perform this task? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 13:50:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CF0E7DF0; Tue, 6 Aug 2013 13:50:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A5D222F72; Tue, 6 Aug 2013 13:50:10 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id F11E5AE52; Tue, 6 Aug 2013 13:50:08 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us F11E5AE52 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 6 Aug 2013 09:50:07 -0400 From: Glen Barber To: Thomas Laus Subject: Re: FreeBSD-Update + Sendmail Message-ID: <20130806135007.GA2190@glenbarber.us> References: <5200FE0E.8506.5CB69E@lausts.acm.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <5200FE0E.8506.5CB69E@lausts.acm.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 13:50:10 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 06, 2013 at 09:45:50AM -0400, Thomas Laus wrote: > I have been updating my FreeBSD systems for many years by updating and=20 > building from source. For the FreeBSD 9.2 cycle, I decided to use=20 > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL an= d=20 > the freebsd-update process only installed a 'bare bones' binary. How do = I=20 > compile just Sendmail from source so that it uses my /etc/make.conf for t= he=20 > smtp_auth components? Is there a freebsd-update.conf flag to perform thi= s=20 > task? >=20 No. When you use freebsd-update(8), you get the binary bits that are available on the release images. There is no way to have freebsd-update(8) know of local changes/patches/etc. Glen --azLHFNyN32YCQGCU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSAP8PAAoJEFJPDDeguUajIpEIAJs52Zm4mzB4yrQQVCQHsq8+ AHzXRTfgJ85DXBWzZk18eK2rypYm+hFiB5IpgslDSN4FdWeysmGncNMGU7GU3H6n sH54R2XvbdLeiq/pOrf0LsRI0uSfreZPPBEFkT/EGZpOe07pnmnj3CmgP1zozg+Q ZonNwZoc2dG+buRCCSTf4ldd4+G4hSxcfDt6cheS/Iy6rfwzeA2R6uHZNPpsO6zT KC9LFWWWDaNm9L1D4fyxbH47DliOlZdQUjJoHHM1+4u0tVHih8699QPzdoQu6Ehk dJPqX7BnQ5hVYzAT1giWLnkkPkvshwQsJaH/h7P4XdGniR92ZU7AESlaaj0DbJs= =i7ZG -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 13:51:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CE6EFEFB for ; Tue, 6 Aug 2013 13:51:12 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 67F322F8E for ; Tue, 6 Aug 2013 13:51:12 +0000 (UTC) Received: from rufus.webfusion.com (mail.heartinternet.co.uk [79.170.40.31]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id r76Doqcc029951 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 6 Aug 2013 14:51:07 +0100 (BST) (envelope-from matthew@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk r76Doqcc029951 Authentication-Results: smtp.infracaninophile.co.uk/r76Doqcc029951; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy) X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host mail.heartinternet.co.uk [79.170.40.31] claimed to be rufus.webfusion.com Message-ID: <5200FF3C.1020300@freebsd.org> Date: Tue, 06 Aug 2013 14:50:52 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130715 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-Update + Sendmail References: <5200FE0E.8506.5CB69E@lausts.acm.org> In-Reply-To: <5200FE0E.8506.5CB69E@lausts.acm.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.8 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 13:51:12 -0000 On 06/08/2013 14:45, Thomas Laus wrote: > I have been updating my FreeBSD systems for many years by updating and > building from source. For the FreeBSD 9.2 cycle, I decided to use > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL and > the freebsd-update process only installed a 'bare bones' binary. How do I > compile just Sendmail from source so that it uses my /etc/make.conf for the > smtp_auth components? Is there a freebsd-update.conf flag to perform this > task? Use the version of sendmail from ports? Cheers, Matthew From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 14:56:32 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 85F4B8C6; Tue, 6 Aug 2013 14:56:32 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 29B2A22D1; Tue, 6 Aug 2013 14:56:29 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id up14so1053652obb.39 for ; Tue, 06 Aug 2013 07:56:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=yU0fGDPPLy0tXl9dYBvITDie3N/tmZ7tRPSrJEM60H4=; b=eoaXcZFAPbuUq36Wh/j+Yt8IMhI8wHQF/IyQAnvWQ6Hj6eGWbdOrLg1j3XMJ5Sp9dv Y+liSG7ncAlzQUwQOYCfDl4J73drdDp6ihHYG16Vif+sXYCKX+XTnPaed073gj9X3q4p irQXL9nWoj/Xw6cAkEQ1exg22UnLLNSs5/nKRPmz56OZPFe4BymEDjSPi4Xh53hoWf4Z eTvj3YIoLCANT/uP9ZrTGDGqHhclw7Uu1L+Q0co2clcIjee7D3kYYzG+qTysmrai6owA xLiypQz/OGJ1la0V3Byqpx113K8JwNbVWFMKV8sVn5le0W4sZtXZTm0qInSP7l4TWgvF lT5w== MIME-Version: 1.0 X-Received: by 10.60.131.232 with SMTP id op8mr1290188oeb.75.1375800988263; Tue, 06 Aug 2013 07:56:28 -0700 (PDT) Received: by 10.182.128.36 with HTTP; Tue, 6 Aug 2013 07:56:28 -0700 (PDT) Date: Tue, 6 Aug 2013 16:56:28 +0200 Message-ID: Subject: wireless networking probelm with WEP From: Oliver Pinter To: freebsd-wireless@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: adrien@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 14:56:32 -0000 Hi All! I run in to problem, what described in some more place: http://149.20.54.209/showthread.php?t=39724 . The concrete problem is: when I use FreeBSD with WEP, there are no RX traffic received. So, when I probed a DHCP request, then here are no response from DHCP server. The OS is: FreeBSD 9.2-BETA2 (freebsd-stable). From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 15:33:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 21D18F06 for ; Tue, 6 Aug 2013 15:33:35 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF55A2472 for ; Tue, 6 Aug 2013 15:33:34 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,827,1367989200"; d="scan'208";a="37601175" Message-ID: <520116DE.8030305@vangyzen.net> Date: Tue, 6 Aug 2013 10:31:42 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: dave@mischler.com Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> In-Reply-To: <1375737316.96778.10.camel@firkin.mischler.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 15:33:35 -0000 On 08/05/2013 16:15, Dave Mischler wrote: > I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the > GENERIC kernel. Today, while still running 9.2-BETA2, I updated my > source tree and started building world with idprio 31 and I looked back > a while later and all the CPU cores and disk were essentially idle, and > hardly any progress had been made on the build. I stopped and restarted > the build without the idle priority setting and it ran fine. Anybody > else seen any of this? Anybody know about any fairly recent changes that > might account for it? > > I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before > going to RC1. I still see odd behavior at RC1. Sometimes it works just > like it should (i.e. compute bound processes use most/all of the > available CPU time), but a lot of the time both the CPU and disk are > idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I > ever saw this behavior before while running "make buildworld -j4". Can > anyone else confirm/rebut my findings? Thanks. I can confirm your findings, on 9.1-RELEASE-p5 amd64 GENERIC. I ran $ idprio 31 make buildworld buildkernel > /tmp/build.log 2>&1 < /dev/null & on an otherwise idle amd64 system with 4 CPUs. The first command in the build.log file: rm -rf /usr/obj/home/freebsd/tmp took over three minutes. It should have taken about three /seconds/. "uptime" reported a load average of around 1.00. "top" showed no threads (user or kernel) using CPU. "iostat" showed an average of less than 20 tps on ada0. "rm" was usually in the RUN state. /home/freebsd (src) is UFS+SUJ. /usr/obj is UFS+SU. /tmp/build.log is tmpfs. Both UFS file systems are on ada0: ada0 at ata2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 2.x device ata2: at channel 0 on atapci0 atapci0: CPU: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz (2394.04-MHz K8-class CPU) real memory = 8589934592 (8192 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) FreeBSD 9.1-RELEASE-p5 #0 r+94f2ad5: Tue Aug 6 09:40:22 CDT 2013 root@srv5:/usr/obj/home/freebsd/sys/GENERIC amd64 /boot/loader.conf contains: console="comconsole vidconsole" comconsole_speed="115200" comconsole_port="0x2f8" /etc/sysctl.conf is empty. I'll update to releng/9.2 and try again. Eric From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 15:43:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 26CE0360 for ; Tue, 6 Aug 2013 15:43:56 +0000 (UTC) (envelope-from jim@jimking.net) Received: from quartz.jimking.net (dsl-katy-207-70-162-186.consolidated.net [207.70.162.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC37524E2 for ; Tue, 6 Aug 2013 15:43:55 +0000 (UTC) Received: from [134.132.77.10] ([34.254.247.1]) (authenticated bits=0) by quartz.jimking.net (8.14.5/8.14.5) with ESMTP id r76FW2AT099881 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 10:32:04 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <520116F1.5040704@jimking.net> Date: Tue, 06 Aug 2013 10:32:01 -0500 From: Jim King User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: lausts@acm.org Subject: Re: FreeBSD-Update + Sendmail References: <5200FE0E.8506.5CB69E@lausts.acm.org> In-Reply-To: <5200FE0E.8506.5CB69E@lausts.acm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 15:43:56 -0000 On 8/6/2013 8:45 AM, Thomas Laus wrote: > I have been updating my FreeBSD systems for many years by updating and > building from source. For the FreeBSD 9.2 cycle, I decided to use > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL and > the freebsd-update process only installed a 'bare bones' binary. How do I > compile just Sendmail from source so that it uses my /etc/make.conf for the > smtp_auth components? Is there a freebsd-update.conf flag to perform this > task? > > Tom > Use the sendmail-sasl port instead. Jim From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 16:36:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB7616FB for ; Tue, 6 Aug 2013 16:36:03 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B63727BE for ; Tue, 6 Aug 2013 16:36:03 +0000 (UTC) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.14.7/8.14.7) with ESMTP id r76GINNo028596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Aug 2013 11:18:23 -0500 (CDT) (envelope-from ted@io-tx.com) Date: Tue, 6 Aug 2013 11:18:23 -0500 (CDT) From: Ted Hatfield To: Thomas Laus Subject: Re: FreeBSD-Update + Sendmail In-Reply-To: <5200FE0E.8506.5CB69E@lausts.acm.org> Message-ID: References: <5200FE0E.8506.5CB69E@lausts.acm.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.97.8 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-3.1 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 user=root X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on io-tx.com Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 16:36:03 -0000 On Tue, 6 Aug 2013, Thomas Laus wrote: > I have been updating my FreeBSD systems for many years by updating and > building from source. For the FreeBSD 9.2 cycle, I decided to use > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL and > the freebsd-update process only installed a 'bare bones' binary. How do I > compile just Sendmail from source so that it uses my /etc/make.conf for the > smtp_auth components? Is there a freebsd-update.conf flag to perform this > task? > > Tom > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > I too have been updating my systems by updating and building from source. To recompile and install sendmail from the /usr/src tree you can run these commands. cd /usr/src/lib/libsm; make clean; make obj; make depend; make cd /usr/src/lib/libsmutil; make clean; make obj; make depend; make cd /usr/src/usr.sbin/sendmail; make clean; make obj; make depend; make; make install This procedure will follow all the /etc/make.conf arguments. I hope this helps. Ted Hatfield PrismNet Ltd. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 17:06:51 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DD8665BC for ; Tue, 6 Aug 2013 17:06:50 +0000 (UTC) (envelope-from boland37@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.freebsd.org (Postfix) with ESMTP id 88C702994 for ; Tue, 6 Aug 2013 17:06:50 +0000 (UTC) Received: from charlemagne.boland.org (37-251-73-96.FTTH.ispfabriek.nl [37.251.73.96]) (authenticated bits=0) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id r76H6h5t075280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 19:06:43 +0200 (CEST) (envelope-from boland37@xs4all.nl) Message-ID: <52012D23.5010106@xs4all.nl> Date: Tue, 06 Aug 2013 19:06:43 +0200 From: Michiel Boland User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130705 Thunderbird/17.0.7 MIME-Version: 1.0 To: Marius Strobl Subject: Re: 9.2-RC1 sparc install via network problems References: <51FFE2A8.3040504@xs4all.nl> <20130806015344.GA62529@alchemy.franken.de> In-Reply-To: <20130806015344.GA62529@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 17:06:51 -0000 On 08/06/2013 03:53, Marius Strobl wrote: [...] > U10 are still supported, why should they have been dropped? :) Turns out the panic is caused by a Performance Technologies SCSI PCI card. I didn't check the exact model, but has a Qlogic 1040B chip on it. (vendor=0x1077, dev=0x1020, revid=0x05) Sometimes it crashes, sometimes not. (But more often than not.) If I remove the card booting proceeds without problems. Difference betweeen normal boot (with -v) and crash: --- boot.ok 2013-08-06 18:50:40.484988096 +0200 +++ boot.notok 2013-08-06 18:59:04.801005172 +0200 @@ -175,7 +175,7 @@ eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) -eeprom0: current time: 1375793620.000000000 +eeprom0: current time: 1375794253.000000000 ebus0: addr 0x1000000000-0x10000fffff (no driver attached) pcm0: addr 0x1400200000-0x14002000ff,0x1400702000-0x140070200f,0x1400704000-0x140070400f,0x1400722000-0x1400722003 irq 35,36 on ebus0 pcm0: @@ -205,49 +205,11 @@ isp0: port 0x400-0x4ff mem 0x2000-0x2fff at device 1.0 on pci2 isp0: using Memory space register mapping isp0: loaded firmware isp_1040 -isp0: Ultra Mode Capable -isp0: Board Type 1040B, Chip Revision 0x5, loaded F/W Revision 4.66.0 -isp0: 512 max I/O command limit set -isp0: Chan 0 Initiator ID is 7 -syscons0: on nexus0 -syscons0: Unknown <16 virtual consoles, flags=0x100> -syscons0: fb0, kbd0, terminal emulator: scteken (teken terminal) -procfs registered -Timecounter "tick" frequency 440000000 Hz quality 1000 -Event timer "tick" frequency 440000000 Hz quality 1000 -Timecounters tick every 1.000 msec -vlan: initialized, using hash tables with chaining -lo0: bpf attached -ata2: reset tp1 mask=03 ostat0=50 ostat1=00 -ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 -ata2: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 -ata2: reset tp2 stat0=50 stat1=00 devices=0x1 -ata3: reset tp1 mask=03 ostat0=00 ostat1=00 -ata3: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb -ata3: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 -ata3: reset tp2 stat0=00 stat1=00 devices=0x10000 -isp0: driver initiated bus reset of bus 0 -(noperiph:isp0:0:-1:-1): reset bus on channel 0 -ada0 at ata2 bus 0 scbus0 target 0 lun 0 -GEOM: new disk ada0 -ada0: ATA-4 device -ada0: Serial Number 3CM0NK7P -ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes) -ada0: 8693MB (17803297 512 byte sectors: 16H 63S/T 17662C) -ada0: Previously was known as ad0 -pass0 at ata2 bus 0 scbus0 target 0 lun 0 -pass0: ATA-4 device -pass0: Serial Number 3CM0NK7P -pass0: 16.700MB/s transfers (WDMA2, PIO 8192bytes) -pass1 at ata3 bus 0 scbus1 target 0 lun 0 -pass1: Removable CD-ROM SCSI-0 device -pass1: Serial Number 1998/09/24 -pass1: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) -cd0 at ata3 bus 0 scbus1 target 0 lun 0 -cd0: Removable CD-ROM SCSI-0 device -cd0: Serial Number 1998/09/24 -cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) -cd0: cd present [323350 x 2048 byte records] -nfs_diskless: no NFS handle -GEOM: new disk cd0 - +panic: trap: data access error (kernel) +cpuid = 0 +KDB: stack backtrace: +#0 0xc08588b4 at trap+0x554 +Uptime: 1s +Automatic reboot in 15 seconds - press a key on the console to abort +Rebooting... +Resetting ... From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 17:59:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3504D4F3 for ; Tue, 6 Aug 2013 17:59:49 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D584D2C97 for ; Tue, 6 Aug 2013 17:59:48 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,827,1367989200"; d="scan'208";a="39157659" Message-ID: <52013992.4050101@vangyzen.net> Date: Tue, 6 Aug 2013 12:59:46 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: dave@mischler.com Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> <520116DE.8030305@vangyzen.net> In-Reply-To: <520116DE.8030305@vangyzen.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 17:59:49 -0000 On 08/06/2013 10:31, Eric van Gyzen wrote: > On 08/05/2013 16:15, Dave Mischler wrote: >> I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the >> GENERIC kernel. Today, while still running 9.2-BETA2, I updated my >> source tree and started building world with idprio 31 and I looked back >> a while later and all the CPU cores and disk were essentially idle, and >> hardly any progress had been made on the build. I stopped and restarted >> the build without the idle priority setting and it ran fine. Anybody >> else seen any of this? Anybody know about any fairly recent changes that >> might account for it? >> >> I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before >> going to RC1. I still see odd behavior at RC1. Sometimes it works just >> like it should (i.e. compute bound processes use most/all of the >> available CPU time), but a lot of the time both the CPU and disk are >> idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I >> ever saw this behavior before while running "make buildworld -j4". Can >> anyone else confirm/rebut my findings? Thanks. > I can confirm your findings, on 9.1-RELEASE-p5 amd64 GENERIC. > > I ran > > $ idprio 31 make buildworld buildkernel > /tmp/build.log 2>&1 < > /dev/null & > > on an otherwise idle amd64 system with 4 CPUs. The first command in the > build.log file: > > rm -rf /usr/obj/home/freebsd/tmp > > took over three minutes. It should have taken about three /seconds/. > > "uptime" reported a load average of around 1.00. > "top" showed no threads (user or kernel) using CPU. > "iostat" showed an average of less than 20 tps on ada0. > "rm" was usually in the RUN state. > > /home/freebsd (src) is UFS+SUJ. > /usr/obj is UFS+SU. > /tmp/build.log is tmpfs. > > Both UFS file systems are on ada0: > > ada0 at ata2 bus 0 scbus2 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ata2: at channel 0 on atapci0 > atapci0: > > CPU: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz (2394.04-MHz > K8-class CPU) > real memory = 8589934592 (8192 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > > FreeBSD 9.1-RELEASE-p5 #0 r+94f2ad5: Tue Aug 6 09:40:22 CDT 2013 > root@srv5:/usr/obj/home/freebsd/sys/GENERIC amd64 > > /boot/loader.conf contains: > > console="comconsole vidconsole" > comconsole_speed="115200" > comconsole_port="0x2f8" > > /etc/sysctl.conf is empty. > > I'll update to releng/9.2 and try again. I see more-or-less the same behavior on 9.2-RC1 (r253912). It seems to be faster than 9.1, but it's still much slower than I would expect. idprio 30 is much, much faster than 31. It's about as fast as I would expect (for this idle machine). So, the problem seems to affect only idprio 31. (Off-by-one / fencepost problem?) CPU-bound processes, such as c++, seem to run at the normal speeds, so the problem seems to affect system- or I/O-bound work. Can anyone try this on a 9.0-RELEASE system? Eric From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 19:23:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4523BD1 for ; Tue, 6 Aug 2013 19:23:56 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A06C32120 for ; Tue, 6 Aug 2013 19:23:56 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wo10so1806952obc.27 for ; Tue, 06 Aug 2013 12:23:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PESSWMg+xHQDA4zEEDQkkKTfpQWFI1Ii4NJf6LmZZkg=; b=cRH6f9zAhzToyjj0zhAEwh0OMDgn8ynssdLWqx75dq7ibxyb+jVoHdu1vhuy6eR4B0 J61sxHXLswdbPd32VuXDBhNnnbb9/Qi1cjjzucGM2Mrt1CQ2t68SEMwzPmeIgn0veF8d XvhNlCESH76y4BuzySoFdZ0OI6gp2mYj7xoagikVjbO0QhK0mYK/ut0SstNu05qqv1Ef hoB7Mmy9EcWcSGWqxOQkWBpDKoS28Msn3yu7lA+VKIxtdGO9H6D1zHQBFfdAQynCL2Dw 75lOF4ybGCK3r8SHkgntuRIRRH2P2bWm8AOKLU8yZdEY85C2W2CPVUaEX86Gs+6UYJaX J5HQ== MIME-Version: 1.0 X-Received: by 10.43.152.210 with SMTP id kx18mr32994icc.39.1375817035961; Tue, 06 Aug 2013 12:23:55 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Tue, 6 Aug 2013 12:23:55 -0700 (PDT) In-Reply-To: <52013992.4050101@vangyzen.net> References: <1375737316.96778.10.camel@firkin.mischler.com> <520116DE.8030305@vangyzen.net> <52013992.4050101@vangyzen.net> Date: Tue, 6 Aug 2013 15:23:55 -0400 X-Google-Sender-Auth: oBE17esH5bml9qF7rPgnx5-Nz2s Message-ID: Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 From: J David To: Eric van Gyzen Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, dave@mischler.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 19:23:56 -0000 On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen wrote: >> on an otherwise idle amd64 system with 4 CPUs. The first command in the >> build.log file: >> >> rm -rf /usr/obj/home/freebsd/tmp >> >> took over three minutes. It should have taken about three /seconds/. >> >> "uptime" reported a load average of around 1.00. >> "top" showed no threads (user or kernel) using CPU. >> "iostat" showed an average of less than 20 tps on ada0. >> "rm" was usually in the RUN state. We are looking at something similar. Would you be able to try to reproduce it using a kernel with: nooptions SCHED_ULE options SCHED_4BSD to see if it makes a difference? It seems to, but the problem is inconsistent enough that I can't be sure. Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 21:26:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 62A698E3; Tue, 6 Aug 2013 21:26:56 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 205412613; Tue, 6 Aug 2013 21:26:56 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id er7so2076727obc.17 for ; Tue, 06 Aug 2013 14:26:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=I2bgZJkgdNj8rpd2Hh6QYdu9JxeHyvtEuTQlu995JN8=; b=oc1aFA5mygs25udofzufCWCWpVfN26SqAqd9upiFL9RK6wdjjIRmZDP1wUeuJDF/gK bxCFThtnHhtFTM72E16zvd+y/Yih8sXG0Qc7Cr01xbxTnICZccSD49QV/B34UhfLWcKS ECOnQkKuI6TDn3ipc6TZ3wYqPuBVhYBAlX9lHXIPfFHzAEVjyD03uYximlKFK1Sdlmrq pPDEYFogGZhZ/oNseUhnzIZGK7eEMEeYcJs6CMnhSKjXeDs1RgwXIVo9cQcpqrfw0Ixh 0dDnawvkqy6nVwtR4vHXESXemCadlcQDad89a4nEAKDz3A4T4rmaHnRPfIAZWNFq5Pan 3/4A== MIME-Version: 1.0 X-Received: by 10.42.215.11 with SMTP id hc11mr19344icb.9.1375824415339; Tue, 06 Aug 2013 14:26:55 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Tue, 6 Aug 2013 14:26:55 -0700 (PDT) In-Reply-To: <5200C7A3.3070403@yandex.ru> References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> Date: Tue, 6 Aug 2013 17:26:55 -0400 X-Google-Sender-Auth: FSwO69iFRn4eX84cjays_onulsk Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: "Andrey V. Elsukov" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 21:26:56 -0000 On Tue, Aug 6, 2013 at 5:53 AM, Andrey V. Elsukov wrote= : > looking to your `zfs status` output and this, we can see, that GPT > wasn't detected on most of disks. Can you try to boot with this loader: > http://people.freebsd.org/~ae/zfsloader > It's from 10-CURRENT and was build with -DPART_DEBUG, so you will see > some additional debug messages while booting. OK, some of the output scrolls too fast=85 since it can't load the filesystem it doesn't know to copy to serial console. But looking at the tail end, it's a lot of this: gpt_checkhdr: invalid entry size or number of entries gpt_checkhdr: invalid entry size or number of entries ptable_open: PMBR detected At least five sets of those, so I assume they are for at least disk2 - disk 7. Unfortunately I can't catch the output for disks 1 and 2, which are the only two bootable disks. :( Here's the bootparttest output: $ sudo ./bootparttest da0 GEOM provider "da0" opened Mediasize: 32296140800 Bytes (63078400 sectors) Sectorsize: 512 Bytes da0: read 1 blocks from the offset 0 [+0] da0: read 1 blocks from the offset 1 [+0] ptable_open: PMBR detected da0: read 1 blocks from the offset 1 [+0] da0: read 32 blocks from the offset 2 [+0] da0: read 1 blocks from the offset 63078399 [+0] ptable_gptread: new GPT partition added ptable_gptread: new GPT partition added ptable_gptread: new GPT partition added Partition table detected: GPT da0p1: FreeBSD boot 64k da0p2: FreeBSD swap 2048M da0p3: FreeBSD ZFS 28G GEOM provider "da1" opened Mediasize: 32000000000 Bytes (62500000 sectors) Sectorsize: 512 Bytes da1: read 1 blocks from the offset 0 [+0] da1: read 1 blocks from the offset 1 [+0] ptable_open: PMBR detected da1: read 1 blocks from the offset 1 [+0] da1: read 32 blocks from the offset 2 [+0] da1: read 1 blocks from the offset 62499999 [+0] ptable_gptread: new GPT partition added ptable_gptread: new GPT partition added ptable_gptread: new GPT partition added Partition table detected: GPT da1p1: FreeBSD boot 64k da1p2: FreeBSD swap 2048M da1p3: FreeBSD ZFS 27G $ sudo ./bootparttest da2 GEOM provider "da2" opened Mediasize: 1000204886016 Bytes (1953525168 sectors) Sectorsize: 512 Bytes da2: read 1 blocks from the offset 0 [+0] da2: read 1 blocks from the offset 1 [+0] ptable_open: PMBR detected da2: read 1 blocks from the offset 1 [+0] gpt_checkhdr: invalid entry size or number of entries da2: read 1 blocks from the offset 1953525167 [+0] gpt_checkhdr: invalid entry size or number of entries Partition table detected: None (Output for da3 - da7 are identical to da2.) So I'm guessing something doesn't like the metadata on the data drives. This is a raidz2, so I can certainly offline the disks one by one to rebuild the partition tables, though that'll take ages; the I/O performance of this system is awful. But I do wonder why the zfsloader from 8.4 can handle whatever's going on in there and 9.2 can't. Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 21:28:46 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D440A9FF for ; Tue, 6 Aug 2013 21:28:46 +0000 (UTC) (envelope-from lausts@acm.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 976E8264D for ; Tue, 6 Aug 2013 21:28:46 +0000 (UTC) X-Authority-Analysis: v=2.0 cv=e9yEuNV/ c=1 sm=0 a=xRdgvQXv5AerPAHtJUV3Bw==:17 a=i3v0hNX2wH8A:10 a=kWQ6D_09QQAA:10 a=kHc8Q_KJ-KsA:10 a=N54-gffFAAAA:8 a=KGjhK52YXX0A:10 a=M43duC95k9sA:10 a=bJzdTrdgvzwysgaonzgA:9 a=xRdgvQXv5AerPAHtJUV3Bw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 184.58.98.36 Received: from [184.58.98.36] ([184.58.98.36:63352] helo=mail.laus.org) by hrndva-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id B4/0D-18705-D8A61025; Tue, 06 Aug 2013 21:28:45 +0000 Received: from [192.168.1.100] (laust2 [192.168.1.100]) by mail.laus.org (8.14.7/8.14.7) with ESMTP id r76LSi4B001420 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Tue, 6 Aug 2013 17:28:44 -0400 (EDT) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host laust2 [192.168.1.100] claimed to be [192.168.1.100] From: "Thomas Laus" Organization: ABB To: Ted Hatfield , freebsd-stable@freebsd.org Date: Tue, 06 Aug 2013 17:28:45 -0400 Subject: Re: FreeBSD-Update + Sendmail Message-ID: <52016A8D.14552.95D18@lausts.acm.org> Priority: normal In-reply-to: References: <5200FE0E.8506.5CB69E@lausts.acm.org>, X-mailer: Pegasus Mail for Windows (4.63) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lausts@acm.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 21:28:46 -0000 > > I have been updating my FreeBSD systems for many years by updating and > > building from source. For the FreeBSD 9.2 cycle, I decided to use > > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL and > > the freebsd-update process only installed a 'bare bones' binary. How do I > > compile just Sendmail from source so that it uses my /etc/make.conf for the > > smtp_auth components? Is there a freebsd-update.conf flag to perform this > > task? > > I too have been updating my systems by updating and building from source. To > recompile and install sendmail from the /usr/src tree you can run these > commands. > > cd /usr/src/lib/libsm; make clean; make obj; make depend; make > cd /usr/src/lib/libsmutil; make clean; make obj; make depend; make > cd /usr/src/usr.sbin/sendmail; make clean; make obj; make depend; make; make > install > > This procedure will follow all the /etc/make.conf arguments. > I like the 'sendmail from ports' suggestion a little better. Going this route, I only need to make configuration changes to /etc/mail/mailer.conf once. All subsequent freebsd-update operations won't require rebuilding sendmail and it's tools. Any updates to the port version are covered by the normal port update system. Future updates to the port version only require a 'make restart' in the /etc/mail directory after reviewing my .mc file for any affected changes. Thanks for the alternate procedure. I'll save it for future reference and it may prove useful someday. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-stable@FreeBSD.ORG Tue Aug 6 21:44:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CF70215B for ; Tue, 6 Aug 2013 21:44:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3922126F1 for ; Tue, 6 Aug 2013 21:44:02 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.2.117.99]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id r76LhubH037211 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 6 Aug 2013 22:43:57 +0100 (BST) (envelope-from matthew@FreeBSD.org) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk r76LhubH037211 Authentication-Results: smtp.infracaninophile.co.uk/r76LhubH037211; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy) Message-ID: <52016E15.1020507@FreeBSD.org> Date: Tue, 06 Aug 2013 22:43:49 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-Update + Sendmail References: <5200FE0E.8506.5CB69E@lausts.acm.org>, <52016A8D.14552.95D18@lausts.acm.org> In-Reply-To: <52016A8D.14552.95D18@lausts.acm.org> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r3rfcvDxHireJS2tQow74HGdG7aHWxlOs" X-Virus-Scanned: clamav-milter 0.97.8 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 21:44:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --r3rfcvDxHireJS2tQow74HGdG7aHWxlOs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 06/08/2013 22:28, Thomas Laus wrote: > I like the 'sendmail from ports' suggestion a little better. Going thi= s=20 > route, I only need to make configuration changes to /etc/mail/mailer.co= nf=20 > once. All subsequent freebsd-update operations won't require rebuildin= g=20 > sendmail and it's tools. Any updates to the port version are covered b= y the=20 > normal port update system. Future updates to the port version only req= uire a=20 > 'make restart' in the /etc/mail directory after reviewing my .mc file f= or any=20 > affected changes. If you're using the ports version of sendmail, a handy tip is to add this to /etc/make.conf: SENDMAIL_CF_DIR=3D /usr/local/share/sendmail/cf MAKEMAP=3D /usr/local/sbin/makemap so you use a version of the sendmail M4 config bits that matches the sendmail binary you're running, and you can use /etc/mail/Makefile to generate and install the configs exactly as if you were using the base system sendmail. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --r3rfcvDxHireJS2tQow74HGdG7aHWxlOs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIBbhwACgkQ8Mjk52CukIwSpACfb2KbVk79v8YXNPw1E0zW7YJO 6kwAnjWeuZ46zcSyty6Rz9wXkXWGS7+n =OdLc -----END PGP SIGNATURE----- --r3rfcvDxHireJS2tQow74HGdG7aHWxlOs-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 08:09:13 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9426ABAD for ; Wed, 7 Aug 2013 08:09:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E23A82237 for ; Wed, 7 Aug 2013 08:09:12 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA20877; Wed, 07 Aug 2013 11:09:07 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V6ynr-000O5l-1v; Wed, 07 Aug 2013 11:09:07 +0300 Message-ID: <5202006B.5060708@FreeBSD.org> Date: Wed, 07 Aug 2013 11:08:11 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: J David Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "Andrey V. Elsukov" , freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 08:09:13 -0000 on 07/08/2013 00:26 J David said the following: > $ sudo ./bootparttest da2 > GEOM provider "da2" opened > Mediasize: 1000204886016 Bytes (1953525168 sectors) > Sectorsize: 512 Bytes > da2: read 1 blocks from the offset 0 [+0] > da2: read 1 blocks from the offset 1 [+0] > ptable_open: PMBR detected > da2: read 1 blocks from the offset 1 [+0] > gpt_checkhdr: invalid entry size or number of entries > da2: read 1 blocks from the offset 1953525167 [+0] > gpt_checkhdr: invalid entry size or number of entries > Partition table detected: None > > (Output for da3 - da7 are identical to da2.) Could you please hack gpt_checkhdr() in sys/boot/common/part.c to print all the relevant values for this check and try bootparttest again? -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 08:20:05 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 17E8DE8F for ; Wed, 7 Aug 2013 08:20:05 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 699AA236F for ; Wed, 7 Aug 2013 08:20:03 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA20977; Wed, 07 Aug 2013 11:19:41 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V6yy5-000O6c-AD; Wed, 07 Aug 2013 11:19:41 +0300 Message-ID: <520202E5.30300@FreeBSD.org> Date: Wed, 07 Aug 2013 11:18:45 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: hartzell@alerce.com Subject: Re: Help with filing a [maybe] ZFS/mmap bug. References: <20967.760.95825.310085@gargle.gargle.HOWL> <51E80B30.1090004@FreeBSD.org> <20968.10645.880772.30501@gargle.gargle.HOWL> In-Reply-To: <20968.10645.880772.30501@gargle.gargle.HOWL> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 08:20:05 -0000 on 18/07/2013 20:44 George Hartzell said the following: > Andriy Gapon writes: > > on 17/07/2013 23:47 George Hartzell said the following: > > > How should I move forward with this? > > > > Could you please try to reproduce this problem using a kernel built with > > INVARIANTS options? > > I added INVARIANT_SUPPORT and INVARIANTS options to the GENERIC > kernel, rebuilt it, installed it and running through my "test case" > generated a lot of invalid flac files. I"m not sure what the options > are/were supposed to do though, it looks like they generally lead to > KASSERTS, which lead to abort()'s. Nothing in /var/log/messages or on > the console. George, do you have anything new on this issue? Could you please try the following patch? http://people.freebsd.org/~avg/zfs-putpages.diff I expect it to not really fix the issue, but it may help to narrow it down. Please keep INVARIANTS. Thank you. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 08:32:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 04703885 for ; Wed, 7 Aug 2013 08:32:24 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E28642562; Wed, 7 Aug 2013 08:32:23 +0000 (UTC) Received: from xyf.my.dom (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r778WMsp022143; Wed, 7 Aug 2013 08:32:23 GMT (envelope-from davidxu@freebsd.org) Message-ID: <5202063F.9070706@freebsd.org> Date: Wed, 07 Aug 2013 16:33:03 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130416 Thunderbird/17.0.5 MIME-Version: 1.0 To: dave@mischler.com Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> In-Reply-To: <1375737316.96778.10.camel@firkin.mischler.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 08:32:24 -0000 On 2013/08/06 05:15, Dave Mischler wrote: > I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the > GENERIC kernel. Today, while still running 9.2-BETA2, I updated my > source tree and started building world with idprio 31 and I looked back > a while later and all the CPU cores and disk were essentially idle, and > hardly any progress had been made on the build. I stopped and restarted > the build without the idle priority setting and it ran fine. Anybody > else seen any of this? Anybody know about any fairly recent changes that > might account for it? > > I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before > going to RC1. I still see odd behavior at RC1. Sometimes it works just > like it should (i.e. compute bound processes use most/all of the > available CPU time), but a lot of the time both the CPU and disk are > idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I > ever saw this behavior before while running "make buildworld -j4". Can > anyone else confirm/rebut my findings? Thanks. > > idle should never be used, it can cause long term priority inversion in kernel, make the system slower. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 09:09:47 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 211A433E for ; Wed, 7 Aug 2013 09:09:47 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6C77E2773 for ; Wed, 7 Aug 2013 09:09:46 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA21955; Wed, 07 Aug 2013 12:09:39 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V6zkR-000OB8-C0; Wed, 07 Aug 2013 12:09:39 +0300 Message-ID: <52020EAF.6000301@FreeBSD.org> Date: Wed, 07 Aug 2013 12:09:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: dave@mischler.com Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> In-Reply-To: <1375737316.96778.10.camel@firkin.mischler.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 09:09:47 -0000 on 06/08/2013 00:15 Dave Mischler said the following: > I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the > GENERIC kernel. Today, while still running 9.2-BETA2, I updated my > source tree and started building world with idprio 31 and I looked back > a while later and all the CPU cores and disk were essentially idle, and > hardly any progress had been made on the build. I stopped and restarted > the build without the idle priority setting and it ran fine. Anybody > else seen any of this? Anybody know about any fairly recent changes that > might account for it? > > I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before > going to RC1. I still see odd behavior at RC1. Sometimes it works just > like it should (i.e. compute bound processes use most/all of the > available CPU time), but a lot of the time both the CPU and disk are > idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I > ever saw this behavior before while running "make buildworld -j4". Can > anyone else confirm/rebut my findings? Thanks. Are you sure that you really want to use idprio for a goal you want to achieve? If yes, are you sure that you want to use idprio 31 specifically? With sched_ule idprio 31 is equivalent to priority of a completely idle system. So the scheduler is in its right to run the idle ("do nothing") thread instead of your thread(s). P.S. https://wiki.freebsd.org/AvgThreadPriorityRanges -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 10:52:41 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1A49F5CF; Wed, 7 Aug 2013 10:52:41 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id D65982050; Wed, 7 Aug 2013 10:52:40 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id 02C4BA81; Wed, 7 Aug 2013 12:52:38 +0200 (CEST) From: "Cedric GROSS" To: "'Oliver Pinter'" References: In-Reply-To: Subject: RE: wireless networking probelm with WEP Date: Wed, 7 Aug 2013 12:52:34 +0200 Message-ID: <002701ce935c$3b087f50$b1197df0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6StTLWKY9fxSKDTIaIjE4H5xptrwApmpZA Content-Language: fr Cc: stable@freebsd.org, freebsd-wireless@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 10:52:41 -0000 > De=A0: owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd- > wireless@freebsd.org] De la part de Oliver Pinter > Envoy=E9=A0: mardi 6 ao=FBt 2013 16:56 > =C0=A0: freebsd-wireless@freebsd.org; stable@freebsd.org > Cc=A0: adrien@freebsd.org > Objet=A0: wireless networking probelm with WEP >=20 > Hi All! Hello Oliver, >=20 > I run in to problem, what described in some more place: > http://149.20.54.209/showthread.php?t=3D39724 . >=20 > The concrete problem is: when I use FreeBSD with WEP, there are no RX > traffic received. Why using WEP ? It's a security hole. How is the network configured ? At boot time or by hand ? > So, when I probed a DHCP request, then here are no response from DHCP > server. >=20 > The OS is: FreeBSD 9.2-BETA2 (freebsd-stable). > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless- > unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 10:52:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:1900:2254:206a::19:2]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BE6C76D0; Wed, 7 Aug 2013 10:52:57 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) by mx2.freebsd.org (Postfix) with ESMTP id 8D7A04D24; Wed, 7 Aug 2013 10:52:56 +0000 (UTC) Message-ID: <52022633.4000507@FreeBSD.org> Date: Wed, 07 Aug 2013 14:49:23 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: J David Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 10:52:57 -0000 On 07.08.2013 01:26, J David wrote: > On Tue, Aug 6, 2013 at 5:53 AM, Andrey V. Elsukov wrote: >> looking to your `zfs status` output and this, we can see, that GPT >> wasn't detected on most of disks. Can you try to boot with this loader: >> http://people.freebsd.org/~ae/zfsloader >> It's from 10-CURRENT and was build with -DPART_DEBUG, so you will see >> some additional debug messages while booting. > > OK, some of the output scrolls too fast… since it can't load the > filesystem it doesn't know to copy to serial console. > > But looking at the tail end, it's a lot of this: > > gpt_checkhdr: invalid entry size or number of entries > gpt_checkhdr: invalid entry size or number of entries > ptable_open: PMBR detected > > At least five sets of those, so I assume they are for at least disk2 - > disk 7. Unfortunately I can't catch the output for disks 1 and 2, > which are the only two bootable disks. :( > > Here's the bootparttest output: > > $ sudo ./bootparttest da0 > GEOM provider "da0" opened > Mediasize: 32296140800 Bytes (63078400 sectors) > Sectorsize: 512 Bytes > da0: read 1 blocks from the offset 0 [+0] > da0: read 1 blocks from the offset 1 [+0] > ptable_open: PMBR detected > da0: read 1 blocks from the offset 1 [+0] > da0: read 32 blocks from the offset 2 [+0] > da0: read 1 blocks from the offset 63078399 [+0] > ptable_gptread: new GPT partition added > ptable_gptread: new GPT partition added > ptable_gptread: new GPT partition added > Partition table detected: GPT > da0p1: FreeBSD boot 64k > da0p2: FreeBSD swap 2048M > da0p3: FreeBSD ZFS 28G > GEOM provider "da1" opened > Mediasize: 32000000000 Bytes (62500000 sectors) > Sectorsize: 512 Bytes > da1: read 1 blocks from the offset 0 [+0] > da1: read 1 blocks from the offset 1 [+0] > ptable_open: PMBR detected > da1: read 1 blocks from the offset 1 [+0] > da1: read 32 blocks from the offset 2 [+0] > da1: read 1 blocks from the offset 62499999 [+0] > ptable_gptread: new GPT partition added > ptable_gptread: new GPT partition added > ptable_gptread: new GPT partition added > Partition table detected: GPT > da1p1: FreeBSD boot 64k > da1p2: FreeBSD swap 2048M > da1p3: FreeBSD ZFS 27G > $ sudo ./bootparttest da2 > GEOM provider "da2" opened > Mediasize: 1000204886016 Bytes (1953525168 sectors) > Sectorsize: 512 Bytes > da2: read 1 blocks from the offset 0 [+0] > da2: read 1 blocks from the offset 1 [+0] > ptable_open: PMBR detected > da2: read 1 blocks from the offset 1 [+0] > gpt_checkhdr: invalid entry size or number of entries > da2: read 1 blocks from the offset 1953525167 [+0] > gpt_checkhdr: invalid entry size or number of entries > Partition table detected: None > > (Output for da3 - da7 are identical to da2.) > > So I'm guessing something doesn't like the metadata on the data drives. Hi, can you please dump first 34 blocks from da2 and send to me? i.e., # dd if=/dev/da2 of=./gpt count=34 Also, it is interesting, what tool did you use for partitioning? -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 12:45:05 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 449C262E; Wed, 7 Aug 2013 12:45:05 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 047CC2912; Wed, 7 Aug 2013 12:45:04 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id ta17so3526616obb.4 for ; Wed, 07 Aug 2013 05:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=T5CKuxLOjbXYvJ0wwLrzNMQXt8dPPWtq514B4SJHkT8=; b=xw7m4qxu2JmTLNpBSxpCLJwaXra/jBXRXQzc3pt2VUU911eCykQiagg9SmKXfkKZAZ 00lfF0N0UKfbqqZHFaoyNWnCbFB2BwCwfCiIdp7pLAWWK39xfUbCPDBErlAi204Y48pR 7FxeS3inf5owua8u9OonvFNiuLzrjdtHEALCiA9VvEQPIfBg0NEK+lwKbR4uwRQNXIB6 GUtkkSRyRD9gLWT7ZNNbZS/lYGz6rAi1pCcN6FvBrKEjy8sPvcWzUAo5uPKaAWM9eQBr K3E+Dj862OlsF4rwvnqV4cKdAavBkVVm+CgTk6zk0myw2uvuYh6SFVLlfkfCGAPqvuYJ Oeew== MIME-Version: 1.0 X-Received: by 10.60.52.244 with SMTP id w20mr347037oeo.30.1375879504093; Wed, 07 Aug 2013 05:45:04 -0700 (PDT) Received: by 10.182.128.36 with HTTP; Wed, 7 Aug 2013 05:45:04 -0700 (PDT) In-Reply-To: <002701ce935c$3b087f50$b1197df0$@info> References: <002701ce935c$3b087f50$b1197df0$@info> Date: Wed, 7 Aug 2013 14:45:04 +0200 Message-ID: Subject: Re: wireless networking probelm with WEP From: Oliver Pinter To: Cedric GROSS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, freebsd-wireless@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 12:45:05 -0000 On 8/7/13, Cedric GROSS wrote: >> De : owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd- >> wireless@freebsd.org] De la part de Oliver Pinter >> Envoy=E9 : mardi 6 ao=FBt 2013 16:56 >> =C0 : freebsd-wireless@freebsd.org; stable@freebsd.org >> Cc : adrien@freebsd.org >> Objet : wireless networking probelm with WEP >> >> Hi All! > > > Hello Oliver, > >> >> I run in to problem, what described in some more place: >> http://149.20.54.209/showthread.php?t=3D39724 . >> >> The concrete problem is: when I use FreeBSD with WEP, there are no RX >> traffic received. > > Why using WEP ? It's a security hole. Because there is no other. > > How is the network configured ? At boot time or by hand ? Both. And now I try to debug, why not work... So I'm now deep in the kernel source. > > >> So, when I probed a DHCP request, then here are no response from DHCP >> server. >> >> The OS is: FreeBSD 9.2-BETA2 (freebsd-stable). >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless- >> unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 13:09:10 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4A4CCEA7; Wed, 7 Aug 2013 13:09:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DCA012A81; Wed, 7 Aug 2013 13:09:09 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r77D989W050698; Wed, 7 Aug 2013 13:09:08 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r77D98lf050688; Wed, 7 Aug 2013 13:09:08 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 7 Aug 2013 13:09:08 GMT Message-Id: <201308071309.r77D98lf050688@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 13:09:10 -0000 TB --- 2013-08-07 08:55:22 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-08-07 08:55:22 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-08-07 08:55:22 - starting RELENG_9 tinderbox run for amd64/amd64 TB --- 2013-08-07 08:55:22 - cleaning the object tree TB --- 2013-08-07 08:55:22 - /usr/local/bin/svn stat /src TB --- 2013-08-07 08:55:27 - At svn revision 254052 TB --- 2013-08-07 08:55:28 - building world TB --- 2013-08-07 08:55:28 - CROSS_BUILD_TESTING=YES TB --- 2013-08-07 08:55:28 - MAKEOBJDIRPREFIX=/obj TB --- 2013-08-07 08:55:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-08-07 08:55:28 - SRCCONF=/dev/null TB --- 2013-08-07 08:55:28 - TARGET=amd64 TB --- 2013-08-07 08:55:28 - TARGET_ARCH=amd64 TB --- 2013-08-07 08:55:28 - TZ=UTC TB --- 2013-08-07 08:55:28 - __MAKE_CONF=/dev/null TB --- 2013-08-07 08:55:28 - cd /src TB --- 2013-08-07 08:55:28 - /usr/bin/make -B buildworld >>> World build started on Wed Aug 7 08:55:29 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Wed Aug 7 12:48:01 UTC 2013 TB --- 2013-08-07 12:48:01 - generating LINT kernel config TB --- 2013-08-07 12:48:01 - cd /src/sys/amd64/conf TB --- 2013-08-07 12:48:01 - /usr/bin/make -B LINT TB --- 2013-08-07 12:48:01 - cd /src/sys/amd64/conf TB --- 2013-08-07 12:48:01 - /usr/sbin/config -m LINT TB --- 2013-08-07 12:48:01 - building LINT kernel TB --- 2013-08-07 12:48:01 - CROSS_BUILD_TESTING=YES TB --- 2013-08-07 12:48:01 - MAKEOBJDIRPREFIX=/obj TB --- 2013-08-07 12:48:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-08-07 12:48:01 - SRCCONF=/dev/null TB --- 2013-08-07 12:48:01 - TARGET=amd64 TB --- 2013-08-07 12:48:01 - TARGET_ARCH=amd64 TB --- 2013-08-07 12:48:01 - TZ=UTC TB --- 2013-08-07 12:48:01 - __MAKE_CONF=/dev/null TB --- 2013-08-07 12:48:01 - cd /src TB --- 2013-08-07 12:48:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Aug 7 12:48:01 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/initcpu.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/io.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/legacy.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/machdep.c /src/sys/amd64/amd64/machdep.c: In function 'db_show_sysregs': /src/sys/amd64/amd64/machdep.c:1226: error: 'MSR_IA32_FEATURE_CONTROL' undeclared (first use in this function) /src/sys/amd64/amd64/machdep.c:1226: error: (Each undeclared identifier is reported only once /src/sys/amd64/amd64/machdep.c:1226: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-08-07 13:09:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-08-07 13:09:08 - ERROR: failed to build LINT kernel TB --- 2013-08-07 13:09:08 - 11554.16 user 1307.35 system 15225.98 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 14:18:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C562487B for ; Wed, 7 Aug 2013 14:18:42 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 897302EDA for ; Wed, 7 Aug 2013 14:18:42 +0000 (UTC) Received: by mail-qe0-f48.google.com with SMTP id 9so1011446qea.35 for ; Wed, 07 Aug 2013 07:18:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=5m6iPAYq0hSQm5zixfmWAHBRp9r/5+z2p/PgjCe/Xro=; b=Z/i6q2HndWruZHITvPE1hyePdkt7u7F8VAnlrSCGVwjM1sxXnjlmZJVGQK+lSqGhGS 2bC/eZL7mpO6ExWrgtiBF4G5sE32z89VisGaxsIbmJepITBGJTqbRh667shxD7tEmLs7 ZmV0s9wQjC5am8nL1RlI3tfMnJe+DuFe5uWv6ZIuQPpR4+dj620KOFDDzD620+t9TRDL i89sWM+hfsnKTqZ36a/WZPOF273+MpnJC+hdtlMlEX07HccipN8kJjmPfHMkfqxsf08R 4tU7f8pvZBzljKjcI4eUCCsENJSkS3GOl4J5C3kUwy8QqEqFpAAIUEzuKa4yGIGN3g9K UAsg== MIME-Version: 1.0 X-Received: by 10.49.42.103 with SMTP id n7mr821003qel.75.1375885121411; Wed, 07 Aug 2013 07:18:41 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.70.225 with HTTP; Wed, 7 Aug 2013 07:18:41 -0700 (PDT) Date: Wed, 7 Aug 2013 16:18:41 +0200 X-Google-Sender-Auth: J1YLVsyTb8YUGTyS7GU1-lYBtFQ Message-ID: Subject: FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases) From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 14:18:42 -0000 Hello :-) I am installing the 9.2-RC1 bootonly iso which wants to download stuff from snapshots while it is in releases directory: Installer wants to get 9.2-RC1 stuff from here (where it is missing): ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/ While the stuff is at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RC1/ Please fix :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 14:19:51 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5295E98B for ; Wed, 7 Aug 2013 14:19:51 +0000 (UTC) (envelope-from p.christias@noc.ntua.gr) Received: from diomedes.noc.ntua.gr (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]) by mx1.freebsd.org (Postfix) with ESMTP id A71F82EF5 for ; Wed, 7 Aug 2013 14:19:50 +0000 (UTC) Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1]) by diomedes.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id r77EJmRX070413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 7 Aug 2013 17:19:48 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: from ajax.noc.ntua.gr (localhost [127.0.0.1]) by ajax.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id r77EJm7U078812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 7 Aug 2013 17:19:48 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: (from christia@localhost) by ajax.noc.ntua.gr (8.14.5/8.14.4/Submit) id r77EJm1x078811 for freebsd-stable@freebsd.org; Wed, 7 Aug 2013 17:19:48 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to p.christias@noc.ntua.gr using -f Date: Wed, 7 Aug 2013 17:19:48 +0300 From: Panagiotis Christias To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-Update + Sendmail Message-ID: <20130807141948.GA78527@noc.ntua.gr> References: <5200FE0E.8506.5CB69E@lausts.acm.org> <52016A8D.14552.95D18@lausts.acm.org> <52016E15.1020507@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52016E15.1020507@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.5 at diomedes.noc.ntua.gr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]); Wed, 07 Aug 2013 17:19:48 +0300 (EEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 14:19:51 -0000 On Tue, Aug 06, 2013 at 10:43:49PM +0100, Matthew Seaman wrote: > On 06/08/2013 22:28, Thomas Laus wrote: > > I like the 'sendmail from ports' suggestion a little better. Going this > > route, I only need to make configuration changes to /etc/mail/mailer.conf > > once. All subsequent freebsd-update operations won't require rebuilding > > sendmail and it's tools. Any updates to the port version are covered by the > > normal port update system. Future updates to the port version only require a > > 'make restart' in the /etc/mail directory after reviewing my .mc file for any > > affected changes. > > If you're using the ports version of sendmail, a handy tip is to add > this to /etc/make.conf: > > SENDMAIL_CF_DIR= /usr/local/share/sendmail/cf > MAKEMAP= /usr/local/sbin/makemap > > so you use a version of the sendmail M4 config bits that matches the > sendmail binary you're running, and you can use /etc/mail/Makefile to > generate and install the configs exactly as if you were using the base > system sendmail. Indeed, plus: SENDMAIL=/usr/local/sbin/sendmail And in /etc/rc.conf: sendmail_program="/usr/local/sbin/sendmail" Regards, Panagiotis -- Panagiotis J. Christias Network Management Center P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 14:32:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9BB21D89; Wed, 7 Aug 2013 14:32:03 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6F8332FDB; Wed, 7 Aug 2013 14:32:02 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id B36B3A4EE; Wed, 7 Aug 2013 14:31:59 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us B36B3A4EE Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Wed, 7 Aug 2013 10:31:57 -0400 From: Glen Barber To: CeDeROM Subject: Re: FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases) Message-ID: <20130807143157.GA2236@glenbarber.us> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 14:32:03 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 07, 2013 at 04:18:41PM +0200, CeDeROM wrote: > Hello :-) >=20 > I am installing the 9.2-RC1 bootonly iso which wants to download stuff fr= om > snapshots while it is in releases directory: >=20 > Installer wants to get 9.2-RC1 stuff from here (where it is missing): >=20 > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/ >=20 > While the stuff is at: >=20 > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RC1/ >=20 > Please fix :-) >=20 Ugh. I'll get this fixed as soon as possible. Thank you for the report. Glen --17pEHd4RhPHOinZp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSAlpdAAoJEFJPDDeguUajgLkH/11a/xNwIoQTk40JO1NqIPB2 N7iD2F6rE5ofWY7zzd0x5yIJXePOpKex0EHTBiK1+0SOZp/OAuyBVIUTmI+Qi/JO XgfCarvm1+BkoKjl3FPg/lM5jOxyaezRqGsbZccHWKQ7prx4nlDZehVfnTvhAT4s 9txL20yOszxCx0EZ0WfES2WJO0UtWaQdxcvT/8eE2mY/EPk1K1GW7qH32nQhsHsr /ABvpfJGrq+R/PwSxrfxa9bpZy24g2tvmfdaowjXm9N/l5zvpryrU8fMABpvy5EW DoSBXHOG057EYgYvzhipVf1/wYq1Qggcj25jR4Pa//npIhVFI5tE0JY7Yb6CVWU= =BOVT -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 14:48:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4586A149; Wed, 7 Aug 2013 14:48:59 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-x229.google.com (mail-qe0-x229.google.com [IPv6:2607:f8b0:400d:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB4FC20D0; Wed, 7 Aug 2013 14:48:58 +0000 (UTC) Received: by mail-qe0-f41.google.com with SMTP id a11so1048136qen.28 for ; Wed, 07 Aug 2013 07:48:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HCllYFQYh5A6IVf/D7R0gOr9K54D1Btag1ZhfH/ndoU=; b=Su5xQZ0GSZY4nDNIVN4MJCE3cOvYQ8GmW/SSTepoQv9auUKkQ9mG1GhGO8IxhP0q0c zXwEGVCk4n4evAXDdxKs/OATOY1bO/wdu2GKpj7KSWy8oI5VTD8pmnCz9Z8WSNVJpk4J nMoJWtFU4Aers3TyySS5Lc2VEP0HSwGR66etWpqwMH0SodddzYosKvGqda5qFG2qq5bf 0o9svUQkKhNcydXBUo8HnAAAKcC1D/SzoQgW5v8zFLtS9M5EE68yfrShkawSju5S48Wa TJd3+giD3VsN9KHLB8XLCfRDZ1fZ63taijMv4s+aTBSTyoaisXg/4ILp5j95CCVsUI5y uGlg== MIME-Version: 1.0 X-Received: by 10.49.105.36 with SMTP id gj4mr1005694qeb.56.1375886938117; Wed, 07 Aug 2013 07:48:58 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.70.225 with HTTP; Wed, 7 Aug 2013 07:48:58 -0700 (PDT) In-Reply-To: <20130807143157.GA2236@glenbarber.us> References: <20130807143157.GA2236@glenbarber.us> Date: Wed, 7 Aug 2013 16:48:58 +0200 X-Google-Sender-Auth: n3QpcehwGrSKYMiBlK1-RPWma7c Message-ID: Subject: Re: FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases) From: CeDeROM To: Glen Barber Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 14:48:59 -0000 On Wed, Aug 7, 2013 at 4:31 PM, Glen Barber wrote: > On Wed, Aug 07, 2013 at 04:18:41PM +0200, CeDeROM wrote: >> I am installing the 9.2-RC1 bootonly iso which wants to download stuff from >> snapshots while it is in releases directory: > > Ugh. I'll get this fixed as soon as possible. > Thank you for the report. > Glen Sure thing! No problem! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:02:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 195293C1 for ; Wed, 7 Aug 2013 15:02:28 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A59F2198 for ; Wed, 7 Aug 2013 15:02:27 +0000 (UTC) Received: from rufus.webfusion.com (mail.heartinternet.co.uk [79.170.40.31]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id r77F2Fvd063274 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 16:02:22 +0100 (BST) (envelope-from matthew@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk r77F2Fvd063274 Authentication-Results: smtp.infracaninophile.co.uk/r77F2Fvd063274; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy) X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host mail.heartinternet.co.uk [79.170.40.31] claimed to be rufus.webfusion.com Message-ID: <52026176.40807@freebsd.org> Date: Wed, 07 Aug 2013 16:02:14 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130801 Thunderbird/17.0.7 MIME-Version: 1.0 To: Panagiotis Christias Subject: Re: FreeBSD-Update + Sendmail References: <5200FE0E.8506.5CB69E@lausts.acm.org> <52016A8D.14552.95D18@lausts.acm.org> <52016E15.1020507@FreeBSD.org> <20130807141948.GA78527@noc.ntua.gr> In-Reply-To: <20130807141948.GA78527@noc.ntua.gr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.8 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:02:28 -0000 On 07/08/2013 15:19, Panagiotis Christias wrote: > On Tue, Aug 06, 2013 at 10:43:49PM +0100, Matthew Seaman wrote: >> On 06/08/2013 22:28, Thomas Laus wrote: >>> I like the 'sendmail from ports' suggestion a little better. Going this >>> route, I only need to make configuration changes to /etc/mail/mailer.conf >>> once. All subsequent freebsd-update operations won't require rebuilding >>> sendmail and it's tools. Any updates to the port version are covered by the >>> normal port update system. Future updates to the port version only require a >>> 'make restart' in the /etc/mail directory after reviewing my .mc file for any >>> affected changes. >> >> If you're using the ports version of sendmail, a handy tip is to add >> this to /etc/make.conf: >> >> SENDMAIL_CF_DIR= /usr/local/share/sendmail/cf >> MAKEMAP= /usr/local/sbin/makemap >> >> so you use a version of the sendmail M4 config bits that matches the >> sendmail binary you're running, and you can use /etc/mail/Makefile to >> generate and install the configs exactly as if you were using the base >> system sendmail. > > > Indeed, plus: > > SENDMAIL=/usr/local/sbin/sendmail > > And in /etc/rc.conf: > > sendmail_program="/usr/local/sbin/sendmail" /etc/mail/mailer.conf does that bit for you. Cheers, Matthew From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:05:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B16CA4CF; Wed, 7 Aug 2013 15:05:01 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87F1921B3; Wed, 7 Aug 2013 15:05:01 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 2E4F3A836; Wed, 7 Aug 2013 15:05:00 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 2E4F3A836 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Wed, 7 Aug 2013 11:04:58 -0400 From: Glen Barber To: CeDeROM Subject: Re: FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases) Message-ID: <20130807150458.GB2236@glenbarber.us> References: <20130807143157.GA2236@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:05:01 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 07, 2013 at 04:48:58PM +0200, CeDeROM wrote: > On Wed, Aug 7, 2013 at 4:31 PM, Glen Barber wrote: > > On Wed, Aug 07, 2013 at 04:18:41PM +0200, CeDeROM wrote: > >> I am installing the 9.2-RC1 bootonly iso which wants to download stuff= from > >> snapshots while it is in releases directory: > > > > Ugh. I'll get this fixed as soon as possible. > > Thank you for the report. > > Glen >=20 > Sure thing! No problem! :-) >=20 Some mirrors have already begun to pick up the change. Sorry for the inconvenience. It was my fault. :( Glen --K8nIJk4ghYZn606h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSAmIaAAoJEFJPDDeguUajqmMH/R8UR5sKfnarBNpD8GammLCb UIyDJB48CHGTGTwnAHFsATZrAH3nhNL6Umn3MEhtkL8Y/zmsb5Xof0DNmQ2ZZuqI oWOrRYykE1+3eFpjbyb9WloILShi+SCa6ngGS7LZk+EPrdEdvX97sgUtv3CSBNc3 CP6kOCCebeLsPzUsm7O5gVlppDE+3q/4zqH8yBmdag9H6YiMf65zmo5B7Si+3Rjy 8OtlB8xYnaEoCfwSc07fIP3vWV1ual302CwYn0kIaA+sdXM9KGqlIznKSRus68A4 KRYOCR51XYV1LKH5x6Dyysq0rRZJQLtIR7t3W8/jKs83kAebFbRrWmOMClM0Mts= =HDlC -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:07:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C8F0601; Wed, 7 Aug 2013 15:07:01 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F26ED21DF; Wed, 7 Aug 2013 15:07:00 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id d10so961232qcz.1 for ; Wed, 07 Aug 2013 08:06:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2/Ul7y+NAmsxYQ6bcaCopJ0V5zt8Gy0IFwPKwOzFNjQ=; b=SMoxJZ37xTWiFXkPKC+fbbq6lOy2QL7cpuAxIDPv167ihrILtP71M0rRrlWuVXnEH6 0XqUwieRkPYEQoGsZQ24HxN5b2EYe93mT6D45vQz44epHJCKskjE9dtgq0JN/gv+y24L MDcpChUKG8D0HlnHY1Q56NTklkuSi1m4um3oVui+6X9zL+5kM1AS12Deqxk6YgsndODS 1mO7drXpBZdhzwjSK6SmdjaIHMkrzDa50/U4XJlWkkxW89nvCIEdv7M3pv8IWGNJfjsa 4FR8J41e+lf3nnlk0DSrD83BencMrB0cynYWjfLlnR0IZt+ynpaq7g92g3HccUo2urPZ nRDg== MIME-Version: 1.0 X-Received: by 10.224.45.138 with SMTP id e10mr1171065qaf.47.1375888019404; Wed, 07 Aug 2013 08:06:59 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.70.225 with HTTP; Wed, 7 Aug 2013 08:06:59 -0700 (PDT) In-Reply-To: <20130807150458.GB2236@glenbarber.us> References: <20130807143157.GA2236@glenbarber.us> <20130807150458.GB2236@glenbarber.us> Date: Wed, 7 Aug 2013 17:06:59 +0200 X-Google-Sender-Auth: AwmjK27-H13Y_TlxY2jMSAJA1K4 Message-ID: Subject: Re: FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases) From: CeDeROM To: Glen Barber Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:07:01 -0000 On Wed, Aug 7, 2013 at 5:04 PM, Glen Barber wrote: > Some mirrors have already begun to pick up the change. > Sorry for the inconvenience. It was my fault. :( > Glen Naah, this is still 9.2-RC1 for testing, important that 9.2-RELEASE gets fine :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:10:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3218EAD6; Wed, 7 Aug 2013 15:10:02 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D7B7F220D; Wed, 7 Aug 2013 15:10:01 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,833,1367989200"; d="scan'208,217";a="37736128" Message-ID: <52026347.9030005@vangyzen.net> Date: Wed, 7 Aug 2013 10:09:59 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> <52020EAF.6000301@FreeBSD.org> In-Reply-To: <52020EAF.6000301@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@FreeBSD.org, dave@mischler.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:10:02 -0000 On 08/07/2013 04:09, Andriy Gapon wrote: > on 06/08/2013 00:15 Dave Mischler said the following: >> I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the >> GENERIC kernel. Today, while still running 9.2-BETA2, I updated my >> source tree and started building world with idprio 31 and I looked back >> a while later and all the CPU cores and disk were essentially idle, and >> hardly any progress had been made on the build. I stopped and restarted >> the build without the idle priority setting and it ran fine. Anybody >> else seen any of this? Anybody know about any fairly recent changes that >> might account for it? >> >> I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before >> going to RC1. I still see odd behavior at RC1. Sometimes it works just >> like it should (i.e. compute bound processes use most/all of the >> available CPU time), but a lot of the time both the CPU and disk are >> idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I >> ever saw this behavior before while running "make buildworld -j4". Can >> anyone else confirm/rebut my findings? Thanks. > Are you sure that you really want to use idprio for a goal you want to achieve? > If yes, are you sure that you want to use idprio 31 specifically? > With sched_ule idprio 31 is equivalent to priority of a completely idle system. > So the scheduler is in its right to run the idle ("do nothing") thread instead > of your thread(s). That sounds like a bug to me, or a POLA violation at least. A user thread should never have the same priority as the idle threads, because a user thread, by definition, has work to do. >From the rtprio(1) examples: To make depend while not disturbing other machine usage: idprio 31 make depend > P.S. > https://wiki.freebsd.org/AvgThreadPriorityRanges Nice! Thank you for writing it and sending the link. Eric From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:52:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C9C72491 for ; Wed, 7 Aug 2013 15:52:49 +0000 (UTC) (envelope-from p.christias@noc.ntua.gr) Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [IPv6:2001:648:2000:de::230]) by mx1.freebsd.org (Postfix) with ESMTP id 2F737249C for ; Wed, 7 Aug 2013 15:52:48 +0000 (UTC) Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1]) by ulysses.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id r77FqlZm048937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 7 Aug 2013 18:52:47 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: from ajax.noc.ntua.gr (localhost [127.0.0.1]) by ajax.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id r77FqllS083494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 7 Aug 2013 18:52:47 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) Received: (from christia@localhost) by ajax.noc.ntua.gr (8.14.5/8.14.4/Submit) id r77Fqlsg083493 for freebsd-stable@freebsd.org; Wed, 7 Aug 2013 18:52:47 +0300 (EEST) (envelope-from p.christias@noc.ntua.gr) X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to p.christias@noc.ntua.gr using -f Date: Wed, 7 Aug 2013 18:52:47 +0300 From: Panagiotis Christias To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-Update + Sendmail Message-ID: <20130807155247.GB78527@noc.ntua.gr> References: <5200FE0E.8506.5CB69E@lausts.acm.org> <52016A8D.14552.95D18@lausts.acm.org> <52016E15.1020507@FreeBSD.org> <20130807141948.GA78527@noc.ntua.gr> <52026176.40807@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52026176.40807@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.5 at ulysses.noc.ntua.gr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (ulysses.noc.ntua.gr [IPv6:2001:648:2000:de::230]); Wed, 07 Aug 2013 18:52:47 +0300 (EEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:52:49 -0000 On Wed, Aug 07, 2013 at 04:02:14PM +0100, Matthew Seaman wrote: > On 07/08/2013 15:19, Panagiotis Christias wrote: > > On Tue, Aug 06, 2013 at 10:43:49PM +0100, Matthew Seaman wrote: > >> On 06/08/2013 22:28, Thomas Laus wrote: > >>> I like the 'sendmail from ports' suggestion a little better. Going this > >>> route, I only need to make configuration changes to /etc/mail/mailer.conf > >>> once. All subsequent freebsd-update operations won't require rebuilding > >>> sendmail and it's tools. Any updates to the port version are covered by the > >>> normal port update system. Future updates to the port version only require a > >>> 'make restart' in the /etc/mail directory after reviewing my .mc file for any > >>> affected changes. > >> > >> If you're using the ports version of sendmail, a handy tip is to add > >> this to /etc/make.conf: > >> > >> SENDMAIL_CF_DIR= /usr/local/share/sendmail/cf > >> MAKEMAP= /usr/local/sbin/makemap > >> > >> so you use a version of the sendmail M4 config bits that matches the > >> sendmail binary you're running, and you can use /etc/mail/Makefile to > >> generate and install the configs exactly as if you were using the base > >> system sendmail. > > > > > > Indeed, plus: > > > > SENDMAIL=/usr/local/sbin/sendmail > > > > And in /etc/rc.conf: > > > > sendmail_program="/usr/local/sbin/sendmail" > > /etc/mail/mailer.conf does that bit for you. Hm, you are right. -- Panagiotis J. Christias Network Management Center P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 15:59:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7651B75A for ; Wed, 7 Aug 2013 15:59:44 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 33CAA24FB for ; Wed, 7 Aug 2013 15:59:43 +0000 (UTC) Received: from dagger.cc.vt.edu (dagger.cc.vt.edu [198.82.163.114]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id r77FrcNu014860 for ; Wed, 7 Aug 2013 11:59:06 -0400 Received: from auth3.smtp.vt.edu (auth3.smtp.vt.edu [198.82.161.152]) by dagger.cc.vt.edu (MOS 4.3.3-GA) with ESMTP id CNC06022; Wed, 7 Aug 2013 11:59:05 -0400 X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu 0 none Received: from pmather.tower.lib.vt.edu (pmather.tower.lib.vt.edu [128.173.51.28]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id r77Fx5k6021686 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 7 Aug 2013 11:59:05 -0400 From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Enabling pf in 9-STABLE guest on KVM triggers abrt crash report Message-Id: <44D51B45-3584-415B-85F9-42A5BAB348B6@gromit.dlib.vt.edu> Date: Wed, 7 Aug 2013 11:59:05 -0400 To: freebsd-stable List Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:59:44 -0000 I have been using 9-STABLE as a guest under KVM on RHEL 6 for several = months now without incident. I am using the virtio drivers and using = bridged networking on the host to attach my guests. Recently, I enabled pf in one of my 9-STABLE (r253579) guests and = subsequently started to receive intermittent crash reports from abrt on = the KVM host. Has anyone else encountered problems using pf under KVM = virtualisation? A typical crash report from the host goes like this: =3D=3D=3D=3D=3D abrt_version: 2.0.8 cmdline: ro root=3D/dev/mapper/chumby-root rd_LVM_LV=3Dchumby/root = rd_NO_LUKS LANG=3Den_US.UTF-8 rd_LVM_LV=3Dchumby/swap = SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3D137M@0M = rd_MD_UUID=3Db7338ac5:b08fdc1b:34d0fcf1:cf28da17 KEYBOARDTYPE=3Dpc = KEYTABLE=3Dus rd_NO_DM rhgb quiet console=3Dtty0 console=3DttyS1,115200 kernel: 2.6.32-358.14.1.el6.x86_64 not-reportable: A kernel problem occurred, but your kernel has been = tainted (flags:G W ). Kernel maintainers are unable to diagnose = tainted reports. time: Wed 07 Aug 2013 11:41:22 AM EDT sosreport.tar.xz: Binary file, 2114408 bytes backtrace: :WARNING: at net/core/dev.c:1759 skb_gso_segment+0x1df/0x2b0() (Tainted: = G W --------------- ) :Hardware name: AX1204-819-R700UB :igb: caps=3D(0x12114bb3, 0x0) len=3D2084 data_len=3D0 ip_summed=3D0 :Modules linked in: iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 = iptable_filter ip_tables ebtable_nat ebtables xt_CHECKSUM = cpufreq_ondemand powernow_k8 freq_table mperf bridge stp llc ipt_REJECT = ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack = ip6table_filter ip6_tables ipv6 ext2 vhost_net macvtap macvlan tun = kvm_amd kvm igb dca ptp pps_core microcode sg serio_raw fam15h_power = k10temp amd64_edac_mod edac_core edac_mce_amd i2c_piix4 i2c_core shpchp = ext4 mbcache jbd2 raid1 sr_mod cdrom sd_mod crc_t10dif pata_acpi = ata_generic pata_atiixp ahci dm_mirror dm_region_hash dm_log dm_mod = [last unloaded: nf_defrag_ipv4] :Pid: 3262, comm: vhost-3242 Tainted: G W --------------- = 2.6.32-358.14.1.el6.x86_64 #1 :Call Trace: : [] ? warn_slowpath_common+0x87/0xc0 :[] ? warn_slowpath_fmt+0x46/0x50 :[] ? igb_get_drvinfo+0x82/0xe0 [igb] :[] ? skb_gso_segment+0x1df/0x2b0 :[] ? dev_hard_start_xmit+0x1b0/0x530 :[] ? sch_direct_xmit+0x15a/0x1c0 :[] ? dev_queue_xmit+0x3b0/0x550 :[] ? br_dev_queue_push_xmit+0x6c/0xa0 [bridge] :[] ? br_forward_finish+0x58/0x60 [bridge] :[] ? __br_forward+0xaa/0xd0 [bridge] :[] ? nf_hook_slow+0x74/0x110 :[] ? br_forward+0x5d/0x70 [bridge] :[] ? br_handle_frame_finish+0x179/0x2a0 [bridge] :[] ? rebalance_domains+0x1a6/0x5a0 :[] ? br_handle_frame+0x1aa/0x250 [bridge] :[] ? __netif_receive_skb+0x529/0x750 :[] ? process_backlog+0x9a/0x100 :[] ? net_rx_action+0x103/0x2f0 :[] ? __do_softirq+0xc1/0x1e0 :[] ? call_softirq+0x1c/0x30 :[] ? call_softirq+0x1c/0x30 : [] ? do_softirq+0x65/0xa0 :[] ? netif_rx_ni+0x28/0x30 :[] ? tun_sendmsg+0x229/0x4ec [tun] :[] ? handle_tx+0x275/0x5e0 [vhost_net] :[] ? handle_tx_kick+0x15/0x20 [vhost_net] :[] ? vhost_worker+0xbc/0x140 [vhost_net] :[] ? vhost_worker+0x0/0x140 [vhost_net] :[] ? kthread+0x96/0xa0 :[] ? child_rip+0xa/0x20 :[] ? kthread+0x0/0xa0 :[] ? child_rip+0x0/0x20 =3D=3D=3D=3D=3D I get these crash reports even with a simple firewall rule set like = this: =3D=3D=3D=3D=3D # $FreeBSD: stable/9/share/examples/pf/pf.conf 218854 2011-02-19 = 14:57:00Z brucec $ # $OpenBSD: pf.conf,v 1.34 2007/02/24 19:30:59 millert Exp $ # # See pf.conf(5) and /usr/share/examples/pf for syntax and examples. # Remember to set net.inet.ip.forwarding=3D1 and/or = net.inet6.ip6.forwarding=3D1 # in /etc/sysctl.conf if packets are to be forwarded between interfaces. ext_if=3D"vtnet0" set skip on lo scrub in block in pass out pass in on $ext_if proto tcp to ($ext_if) port ssh pass in on $ext_if inet proto icmp from any to ($ext_if) icmp-type { = unreach, redir, timex } =3D=3D=3D=3D=3D Does anyone know of any problems using pf with the virtio vtnet driver, = or indeed in using pf at all under KVM virtualisation? For now, I've = turned off pf, but I would like to be able to enable it in future to do = firewalling on the virtual guest. I have no problems using iptables for = firewalling on my Linux KVM guests. Cheers, Paul.= From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 16:04:26 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09B8C9E4 for ; Wed, 7 Aug 2013 16:04:26 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2A4A2558 for ; Wed, 7 Aug 2013 16:04:25 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id c11so976063qcv.41 for ; Wed, 07 Aug 2013 09:04:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=284/UEMrEjQei3Wb614B5hbopcm6jcmNysWx0RwovQQ=; b=Ei3PCmr77tKmxThJDZKZtowTZ61Rx//o4w+MXkq8iDatYkRpCVReGNdfsAdZzpoSRe hdDH5X0tVH25gLiNyyPszhHKd0pDUacG70cwp0MovvN0yfXfy+PpJvBbbAD2eJh1WO/R ygI9XZivFiUm0j5IjmPkGJG71sieIJlJx+WW2gMZZO9rHu+oHOMhbKEBBiKD2/zwuW5X eMwuoIzgAxxJqFrfzsDal0XKPNselX5fuFeDm5zW8MLBQtmcPudBYIhR2hLD29VEyQNO Y2yqDTDpIEvXGcIMfMbBP1ByFYtB3VyOexv3ZUuHOeChYdn6UrnG0aW0zZdINND2mtmZ UzTQ== MIME-Version: 1.0 X-Received: by 10.49.105.36 with SMTP id gj4mr1386853qeb.56.1375891464665; Wed, 07 Aug 2013 09:04:24 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.70.225 with HTTP; Wed, 7 Aug 2013 09:04:24 -0700 (PDT) Date: Wed, 7 Aug 2013 18:04:24 +0200 X-Google-Sender-Auth: SaIhzCNPiRHdhfk8by4lbr1e1Mo Message-ID: Subject: FreeBSD 9.2-RC1 i386 frozen to death From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 16:04:26 -0000 Hey :-) I have just installed FreeBSD 9.2-RC1 on Dell Latitude D620 i386 laptop. After first run and installation of some packets with pkg(ng) then some xorg configuration when I was in console it hung badly with totally no response. This looks bad :-( http://www.youtube.com/watch?v=7Tngr7YpP_I Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 16:05:31 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BF2D2AF2 for ; Wed, 7 Aug 2013 16:05:31 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A9793256F for ; Wed, 7 Aug 2013 16:05:31 +0000 (UTC) Received: from minime.local (natted.sendmail.com [63.211.143.38]) (authenticated bits=0) by zim.gshapiro.net (8.14.7/8.14.7) with ESMTP id r77G5R1a034052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 09:05:30 -0700 (PDT) (envelope-from gshapiro@freebsd.org) Date: Wed, 7 Aug 2013 09:05:29 -0700 From: Gregory Shapiro To: Pavel Timofeev Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network Message-ID: <20130807160528.GC13555@minime.local> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 16:05:31 -0000 > I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. > If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS > you won't receive it. > But in same time email passes from FreeBSD 9.1-RELEASE which uses > Sendmail-8.14.5. The recent release made the following change: --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 @@ -4726,7 +4726,12 @@ #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ int nmaps; # if NETINET6 - int flags = AI_DEFAULT|AI_ALL; +# ifndef SM_IPNODEBYNAME_FLAGS + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG +# endif /* SM_IPNODEBYNAME_FLAGS */ + + int flags = SM_IPNODEBYNAME_FLAGS; int err; # endif /* NETINET6 */ char *maptype[MAXMAPSTACK]; Which is described in this release note: Drop support for IPv4-mapped IPv6 addresses to prevent the MTA from using a mapped address over a legitimate IPv6 address and to enforce the proper semantics over the IPv6 connection. Problem noted by Ulrich Sporlein. It looks like that SERVFAIL from Microsoft's DNS server is getting in the way of that. I can look at adding this exception to WorkAroundBrokenAAAA as a possibility for a future release. I'd also like to hear feedback on whether the above change (changing getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went too far and what the accepted norm is for getipnodebyname(). From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 16:10:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AA9F0F1C for ; Wed, 7 Aug 2013 16:10:09 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6E7CB25C6 for ; Wed, 7 Aug 2013 16:10:09 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id e11so977190qcx.8 for ; Wed, 07 Aug 2013 09:10:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=9Jc8hQS+ALXeVZ1o6+7JjThdAh9bWCGDhfaYRR2pJes=; b=V7vC5S/6Q0YE5dGKsN2HL01i8F4h8s5MHjZ13QBORFYL6BoeV9FHCDUnH8ar/6uOsL KPuZc3JevicThwmDzyejl3J/xre72GZx+iLs73bzrr+hjLDCsWtignY1FB8EYlu9xpHS P4jTs7jdIWoV10Z2rOdUmEENeNjs82p62EVPTHc4EZXM/CV+ynmtUA4u4YipmhrKVa0u 34IkppouqvF0MlKjfH3vnHmGWdrZEOv4JcyY5mu0b/iPoIpUv/pYIs48taYs/BN5RO0t RzzkDLFvQNubxGcfFM4CqVntNwj+LbnWAifYKA/rsz6Q25y70BfVBY62hrSEzGCYX4R5 i+Gg== MIME-Version: 1.0 X-Received: by 10.229.139.196 with SMTP id f4mr349208qcu.34.1375891808113; Wed, 07 Aug 2013 09:10:08 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.70.225 with HTTP; Wed, 7 Aug 2013 09:10:08 -0700 (PDT) In-Reply-To: References: Date: Wed, 7 Aug 2013 18:10:08 +0200 X-Google-Sender-Auth: ns4BXTBN-T-j0OwJvga2FoymZRo Message-ID: Subject: Re: FreeBSD 9.2-RC1 i386 frozen to death From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 16:10:09 -0000 No crashdump was made, I was on second console so I dont know what happened exactly, no backtrace, nothing, sorry :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 16:26:11 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 30E8B445 for ; Wed, 7 Aug 2013 16:26:11 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E08426C6 for ; Wed, 7 Aug 2013 16:26:11 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id lj1so2195799pab.1 for ; Wed, 07 Aug 2013 09:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=4A3mZ9s933XE4TwbkploKKcXbC3tPrBAmhsg0azvDvk=; b=FlJDceA0CVf5izAnlyqQYj8BywOplyQasYpo2G8ZOcMu8QrMnxon2kmj6ef7kcgDLD tz56oKzql66u+ysgklQFoKxGExS0zVYHF2CGIl9tj/ocsstNUanAYgr1XoHvCV5RVhEg etQva9kdyHCrNGjYZCshbYF9v0UNlQ9tuwr42y1WSpQCewYqmobavY8pDnLPwsfxPO9t pB0BkjwM80TLqd4ev9f2hbTiJ2FAS9lvFfw0YO8eOf0bcbdKKcMGPvKEgOWPJPDiPgAa ReHJ3s76gTwaHsdEanihNL3QeqorUx6F+yV0E71PGD8mctbuecOLHz3SUDcq9g0tYjen 7qGQ== MIME-Version: 1.0 X-Received: by 10.66.147.9 with SMTP id tg9mr1612244pab.5.1375892770553; Wed, 07 Aug 2013 09:26:10 -0700 (PDT) Received: by 10.68.211.106 with HTTP; Wed, 7 Aug 2013 09:26:10 -0700 (PDT) Date: Wed, 7 Aug 2013 19:26:10 +0300 Message-ID: Subject: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 16:26:11 -0000 Hi list, With a 9.1 system and the following: /etc/sysctl.conf: security.jail.mount_allowed=1 security.jail.mount_zfs_allowed=1 security.jail.enforce_statfs=1 zfs set jailed=on Pool zfs jail 1 Pool jexec 1 tcsh jail1# zfs create Pool/test1 jail1# zfs list NAME USED AVAIL REFER MOUNTPOINT Pool 223K 19.6G 31K /Pool Pool/test1 31K 19.6G 31K /Pool/test After upgrading to 9.2-RC1 the same operation results in: jail1# zfs create Pool/test2 cannot create 'Pool/test2': permission denied What am I missing? Thanks -- George Kontostanos --- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 17:09:06 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23515305; Wed, 7 Aug 2013 17:09:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB5FB291D; Wed, 7 Aug 2013 17:09:04 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r77H90PC006738; Wed, 7 Aug 2013 20:09:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r77H90PC006738 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r77H90CA006737; Wed, 7 Aug 2013 20:09:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 7 Aug 2013 20:09:00 +0300 From: Konstantin Belousov To: FreeBSD Tinderbox Subject: Re: [releng_9 tinderbox] failure on amd64/amd64 Message-ID: <20130807170900.GI4972@kib.kiev.ua> References: <201308071309.r77D98lf050688@freebsd-stable.sentex.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u6pNtzRgvO9A6gR8" Content-Disposition: inline In-Reply-To: <201308071309.r77D98lf050688@freebsd-stable.sentex.ca> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: amd64@freebsd.org, stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 17:09:06 -0000 --u6pNtzRgvO9A6gR8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Aug 07, 2013 at 01:09:08PM +0000, FreeBSD Tinderbox wrote: > /src/sys/amd64/amd64/machdep.c: In function 'db_show_sysregs': > /src/sys/amd64/amd64/machdep.c:1226: error: 'MSR_IA32_FEATURE_CONTROL' undeclared (first use in this function) Should be fixed with the r254066, sorry for the breakage. --u6pNtzRgvO9A6gR8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJSAn8rAAoJEJDCuSvBvK1BFAEQAI02rSfVpYWmTjO8A4wneChF MgAW/rIfTDpr8gkis6o6vuhFrGFlHtGIYD0y7Rb1ri5Cioi90n42va9rly1kAqqT sgzbLOe1DPVb7gEJqOAJhflZgMJ2PdrENXx5SF+iaflIJ1/HfO9mqI1F3acgxOx9 y6WeQCOjmSWEp7RsOhUOE/wq2iV5ixLH1tv3yG+VNXaewro/NbUSPACYujTcG0V7 j2OReJJlCC7Q59ep0xZoK7r6FlA04tlgqicBFvbaDTVmP8BiBAYiMG0FINV13Wnf N/bh6Ef1b+GPu858B/vZCb9jS3ik96HAYJ2eMNul3miFafUOp9BetvYjL3TsWSIm e1DdV3y46nkDZ9NpH46uMEt5l+4d+a3BM2ZwN2co1+AEpQaTn3sLJSubr3l83WVQ XWV6FE3ptZxFtUYNctnIhhyX801qm/VmLZV0sfTgocTihH6qv7o7PqT28omOIcRl Mt7+EiR5wIuRQOU5wHZ3mEEOXExK7glDcmuePQRoAu2vlRn2kypVBcT93JtJYiv2 H/MteglZrBBQdBU660lWOfqbuHh71tbdrpr/aIRF0o5msH156zLgYiHTbChkXXba VjqPf8TBptAwxzQRZZ3X0DW55z/TIn8O4H5ij6vn8x4JtAHG+nm4iHTJERfemXJs ZpxgTxtHWfCaSZDJEtf+ =Q2N1 -----END PGP SIGNATURE----- --u6pNtzRgvO9A6gR8-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 17:30:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 64155B0A for ; Wed, 7 Aug 2013 17:30:42 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD2752ADB for ; Wed, 7 Aug 2013 17:30:41 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r77HS1EP080320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 19:28:01 +0200 (CEST) (envelope-from freebsd@omnilan.de) Message-ID: <520283A1.1070404@omnilan.de> Date: Wed, 07 Aug 2013 19:28:01 +0200 From: "freebsd@omnilan.de" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable Subject: Some missong patches in 9.2-RC2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 17:30:42 -0000 Hello, I went through my local patches against base/releng/, 9.2 in that case. There are some fixes which are noct in 9.2-RC1: - Regarding kerberized builds: http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043902.html - Regarding mfi and >2TB corruption, seems MFC reminder failed http://www.freebsd.org/cgi/query-pr.cgi?pr=173291 - Regarding mount failok (seems r230226 got lost?) http://www.freebsd.org/cgi/query-pr.cgi?pr=163668&cat=conf I guess it's far too late to get anything i n9.2 but maby 9.3? Sorry, I couldn't find time to chekc this earlier :-( Thanks, -Harry From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 18:22:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5B8EBB90; Wed, 7 Aug 2013 18:22:29 +0000 (UTC) (envelope-from lee@dilkie.com) Received: from data.snhdns.com (data.snhdns.com [208.76.82.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 250DC2E70; Wed, 7 Aug 2013 18:22:28 +0000 (UTC) Received: from [216.191.234.70] (port=56034 helo=[10.39.164.100]) by data.snhdns.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1V77df-00036g-QQ; Wed, 07 Aug 2013 13:35:11 -0400 Message-ID: <52028551.2040305@dilkie.com> Date: Wed, 07 Aug 2013 13:35:13 -0400 From: Lee Dilkie User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Gregory Shapiro Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network References: <20130807160528.GC13555@minime.local> In-Reply-To: <20130807160528.GC13555@minime.local> X-Enigmail-Version: 1.5.2 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - data.snhdns.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - dilkie.com X-Get-Message-Sender-Via: data.snhdns.com: authenticated_id: lee@dilkie.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Pavel Timofeev , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 18:22:29 -0000 On 8/7/2013 12:05 PM, Gregory Shapiro wrote: >> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. >> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS >> you won't receive it. >> But in same time email passes from FreeBSD 9.1-RELEASE which uses >> Sendmail-8.14.5. > The recent release made the following change: > > --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 > +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 > @@ -4726,7 +4726,12 @@ > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > int nmaps; > # if NETINET6 > - int flags = AI_DEFAULT|AI_ALL; > +# ifndef SM_IPNODEBYNAME_FLAGS > + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > +# endif /* SM_IPNODEBYNAME_FLAGS */ > + > + int flags = SM_IPNODEBYNAME_FLAGS; > int err; > # endif /* NETINET6 */ > char *maptype[MAXMAPSTACK]; > > Which is described in this release note: > > Drop support for IPv4-mapped IPv6 addresses to prevent the MTA > from using a mapped address over a legitimate IPv6 address > and to enforce the proper semantics over the IPv6 > connection. Problem noted by Ulrich Sporlein. > > It looks like that SERVFAIL from Microsoft's DNS server is getting > in the way of that. I can look at adding this exception to > WorkAroundBrokenAAAA as a possibility for a future release. > > I'd also like to hear feedback on whether the above change (changing > getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went > too far and what the accepted norm is for getipnodebyname(). > getipnodebyname() is deprecated... getaddrinfo() should be used in this ipv6 world instead. -lee From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 18:59:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 59615E27; Wed, 7 Aug 2013 18:59:30 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20BD120C6; Wed, 7 Aug 2013 18:59:30 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id f4so126004iea.37 for ; Wed, 07 Aug 2013 11:59:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XLrH2o1AXYSPAexZkB/7WiyZPDupTj4MNk3PubfLQrw=; b=VrLZk9GSFsN/cmIOdLpGLncigWBnXzJ6/S2XGBSUDATjS/4z9czL3IhTT2Cfqh6q8g rcJtENPS44qJgz7Wnrpn7WisBWDFSqW8q1Ae/DCqSiafMZjnrDaVxJ9y16QGhd/UShS1 ismZwV1XS1MMUWq0leIxERh2xSZ8ifsGYYhUT5xLZnO4rH0So9TWg+XAU19/9NP4vEmi sOekWVkVxDUuOKBYlgbPS5HhvMycq3jbHPH5sonZRuEU1pRp6rF9x/4ZP5JPQbT+anKq t2yuV7Bo4CtfvYAasW8WLnvR/Nf5JtaElbSVqC2L13xa6sSZD3rCxSDy47spj3qmDXoG Gfdg== MIME-Version: 1.0 X-Received: by 10.43.137.9 with SMTP id im9mr275985icc.39.1375901969677; Wed, 07 Aug 2013 11:59:29 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Wed, 7 Aug 2013 11:59:29 -0700 (PDT) In-Reply-To: <5202006B.5060708@FreeBSD.org> References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> <5202006B.5060708@FreeBSD.org> Date: Wed, 7 Aug 2013 14:59:29 -0400 X-Google-Sender-Auth: JiOISNTuhLpT7_yH1pRWg6dVJzo Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: "Andrey V. Elsukov" , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 18:59:30 -0000 On Wed, Aug 7, 2013 at 4:08 AM, Andriy Gapon wrote: > Could you please hack gpt_checkhdr() in sys/boot/common/part.c to print all the > relevant values for this check and try bootparttest again? Your wish is my command: --- common/part.c.orig 2013-08-05 19:00:49.536868414 +0000 +++ common/part.c 2013-08-07 18:34:09.277972724 +0000 @@ -184,7 +184,7 @@ if (hdr->hdr_entries < 128 || hdr->hdr_entsz < sizeof(struct gpt_ent) || sectorsize % hdr->hdr_entsz != 0) { - DEBUG("invalid entry size or number of entries"); + DEBUG("invalid entry size (%u/%lu) or number of entries (%u)", hdr->hdr_entsz, sizeof(struct gpt_ent), hdr->hdr_entries); return (NULL); } hdr->hdr_lba_start = le64toh(hdr->hdr_lba_start); $ sudo ./bootparttest da2 GEOM provider "da2" opened Mediasize: 1000204886016 Bytes (1953525168 sectors) Sectorsize: 512 Bytes da2: read 1 blocks from the offset 0 [+0] da2: read 1 blocks from the offset 1 [+0] ptable_open: PMBR detected da2: read 1 blocks from the offset 1 [+0] gpt_checkhdr: invalid entry size (128/128) or number of entries (9) da2: read 1 blocks from the offset 1953525167 [+0] gpt_checkhdr: invalid entry size (128/128) or number of entries (9) Partition table detected: None So it looks like this check is tripping because of hdr->hdr_entries (9 < 128). If I change the minimum to 9 instead of 128, I get the following: $ sudo ./bootparttest da2 GEOM provider "da2" opened Mediasize: 1000204886016 Bytes (1953525168 sectors) Sectorsize: 512 Bytes da2: read 1 blocks from the offset 0 [+0] da2: read 1 blocks from the offset 1 [+0] ptable_open: PMBR detected da2: read 1 blocks from the offset 1 [+0] da2: read 2 blocks from the offset 2 [+0] da2: read 1 blocks from the offset 1953525167 [+0] ptable_gptread: new GPT partition added Partition table detected: GPT da2p1: FreeBSD ZFS 931G That looks like it's reading it. So is "128 partitions is the minimum" more of a guideline than an actual rule? Maybe "be restrictive with what you generate but permissive in what you accept" would apply here. Unfortunately since I am currently resilvering one of the drives with a fresh gpart-built table, I won't be in a position to reboot this machine for awhile to see if a zfsloader built with this change would boot the pool. But it seems like it might. Thanks! From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 19:06:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 04F9830A; Wed, 7 Aug 2013 19:06:13 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B567B216C; Wed, 7 Aug 2013 19:06:12 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id a11so143093iee.36 for ; Wed, 07 Aug 2013 12:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cG9oRbZtN0ltqK8rrXzJnK2eBPZFUZRoCy2gKjkMjPM=; b=NZ2Y/R7JZ/xJhWJjzNDpjBsgaBNDAEuRc5LzB+JfKYbSO3MFQ5oe8i68ASP0QDbWEw DHnWuJ/6/RUhyM02M3Kiezmfjy+n3ZvUikM75sD06Jt7y8ZderiuwvP5HluYwMSCxKGm MBME/CemSFPGNx15ToJWkHWv+ngQ/JO1Rx0M3ddp1VtDV1nTen4V/3PDeByXvUe5AaCc TwBaaF2jFyI6+r1xde63PBqs0dDA0zckdSrtMm3e7cxbtP/We6SSgHpO8WeARcgS5gNX TsQmw2FGPhE9tmzI1+9y2mLOn0fRSZG/IHM9plO4LN9ZFwZJwmlm1ceVBDBV9GlBLc1l Sw4g== MIME-Version: 1.0 X-Received: by 10.43.137.9 with SMTP id im9mr290036icc.39.1375902372264; Wed, 07 Aug 2013 12:06:12 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.150.196 with HTTP; Wed, 7 Aug 2013 12:06:12 -0700 (PDT) In-Reply-To: <52022633.4000507@FreeBSD.org> References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> <52022633.4000507@FreeBSD.org> Date: Wed, 7 Aug 2013 15:06:12 -0400 X-Google-Sender-Auth: n1Fdf6F9TydOiEiaTkr9WzGofC0 Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: "Andrey V. Elsukov" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 19:06:13 -0000 On Wed, Aug 7, 2013 at 6:49 AM, Andrey V. Elsukov wrote: > can you please dump first 34 blocks from da2 and send to me? Will send off-list. > Also, it is interesting, what tool did you use for partitioning? Unfortunately I'm not sure. This pool may have been created on Solaris. Seems like maybe the Gnu parted folks hit this as well: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=ce85c5145ed5e267e http://thread.gmane.org/gmane.comp.gnu.parted.bugs/10173 Thanks! From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 21:46:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 65063C1A for ; Wed, 7 Aug 2013 21:46:19 +0000 (UTC) (envelope-from peter@wemm.org) Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1E3122C1E for ; Wed, 7 Aug 2013 21:46:18 +0000 (UTC) Received: by mail-ve0-f169.google.com with SMTP id db10so2432057veb.28 for ; Wed, 07 Aug 2013 14:46:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pgdkHNLw2h9wOo5IB0WkuJokx+GuQYGwuit6hTxupFw=; b=2oGKuMBBfmV1Yg2GvFWf1pJtrbBTfDakyKxdO6C37g28wOEaqK1tFZC1mBwYb2v1TX fyY57oW8fpub0WeDgnZ4CDEnIDGZ2J4HPlBeN2MpQaR1ddMTmzXx/dznGnjqmgCJ6jUB N1YJfxaJFVXOVtdzzj+paGn3dGV/XQv6HRMEQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pgdkHNLw2h9wOo5IB0WkuJokx+GuQYGwuit6hTxupFw=; b=NDeWBbCKXvWdCYrLq9pFqMWFKoRB+dx2+8Br1q2JRcce/8zKI6HxZQonybMsrVbQVF v00VZ+DF2RPlG5kjq/jm1xOsOH8/KvnxWDL/omwcjOYAk29uL8LHL/gympZEEvG66RRY YtdPe/Wac5HDog+xPIhZfu2wE+mJT3+EYmGAI1wVF9afw/g7LSukgCmKNqJ9wRHZ0maq A2pt4w77Yn/0UALGXhOA8nJmiJOuRVASZPoseEWKAveMnzUZEerTd5x4T68BE6DR5Muo YZ0J/IfpCBx/3SgLnXZHGdW1LGe0Kf0Y6qJtTbRiXvDhOcFctr/dH2Ft7O6gAgbsPT6T PpDA== X-Gm-Message-State: ALoCoQmv45ypKFTe2v+cxQAr82eJY2GfHqjzyxRBKjD462llxkb9xh0/PLFRIGl61V2kOMTqGg98 MIME-Version: 1.0 X-Received: by 10.220.50.10 with SMTP id x10mr609475vcf.86.1375911977457; Wed, 07 Aug 2013 14:46:17 -0700 (PDT) Received: by 10.220.167.74 with HTTP; Wed, 7 Aug 2013 14:46:17 -0700 (PDT) In-Reply-To: References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> <5202006B.5060708@FreeBSD.org> Date: Wed, 7 Aug 2013 14:46:17 -0700 Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: Peter Wemm To: J David Content-Type: text/plain; charset=ISO-8859-1 Cc: "Andrey V. Elsukov" , freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 21:46:19 -0000 On Wed, Aug 7, 2013 at 11:59 AM, J David wrote: > On Wed, Aug 7, 2013 at 4:08 AM, Andriy Gapon wrote: >> Could you please hack gpt_checkhdr() in sys/boot/common/part.c to print all the >> relevant values for this check and try bootparttest again? [..] > So it looks like this check is tripping because of hdr->hdr_entries (9 < 128). I've run into this before. Our loader and kernel are excessively pedantic about this. gpart create -s gpt -n ... leads to bootblocks or loader or kernel rejecting it if it is < 128, and some of the bootblocks reject it if it is > 128. As things stand, the -n option is basically "make my system unusable". -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV UTF-8: for when a ' just won\342\200\231t do. ZFS must be the bacon of file systems. "everything's better with ZFS" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 7 23:44:16 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 042828A2; Wed, 7 Aug 2013 23:44:16 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7676A236E; Wed, 7 Aug 2013 23:44:15 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 6A9022842A; Wed, 7 Aug 2013 16:38:18 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id 30F7128424; Wed, 7 Aug 2013 16:38:18 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id 272AF15A70BA; Wed, 7 Aug 2013 16:38:17 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20994.55913.93606.436124@gargle.gargle.HOWL> Date: Wed, 7 Aug 2013 16:38:17 -0700 To: Andriy Gapon Subject: Re: Help with filing a [maybe] ZFS/mmap bug. In-Reply-To: <520202E5.30300@FreeBSD.org> References: <20967.760.95825.310085@gargle.gargle.HOWL> <51E80B30.1090004@FreeBSD.org> <20968.10645.880772.30501@gargle.gargle.HOWL> <520202E5.30300@FreeBSD.org> X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@FreeBSD.org, hartzell@alerce.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 23:44:16 -0000 Andriy Gapon writes: > on 18/07/2013 20:44 George Hartzell said the following: > > Andriy Gapon writes: > > > on 17/07/2013 23:47 George Hartzell said the following: > > > > How should I move forward with this? > > > > > > Could you please try to reproduce this problem using a kernel built with > > > INVARIANTS options? > > > > I added INVARIANT_SUPPORT and INVARIANTS options to the GENERIC > > kernel, rebuilt it, installed it and running through my "test case" > > generated a lot of invalid flac files. I"m not sure what the options > > are/were supposed to do though, it looks like they generally lead to > > KASSERTS, which lead to abort()'s. Nothing in /var/log/messages or on > > the console. > > George, > > do you have anything new on this issue? Since the message that you quoted I narrowed down my "test case" somewhat but I have not yet produced a stand-alone tool that reproduces it (you still have to go through picard et al.). > Could you please try the following patch? > http://people.freebsd.org/~avg/zfs-putpages.diff > > I expect it to not really fix the issue, but it may help to narrow it down. > Please keep INVARIANTS. Absolutely. Probably not until the weekend, but I'll give it a go. Thanks for following up. g. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 03:56:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BFD9616A for ; Thu, 8 Aug 2013 03:56:23 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 429232157 for ; Thu, 8 Aug 2013 03:56:23 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id e12so2132259wgh.21 for ; Wed, 07 Aug 2013 20:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=65Nvp1iB4MKFiTAMgOl0qqYc+6jxc0S450UM/XsE2OI=; b=MmyoAWtm/jZQAPMlbPgWB1s5W/Djfq6Fzd6VhNxEQWDOzP4ny0m7a+D5h3EuJBKgfR pJftjJ004CdTWNH05pHsskZCilx/O17XlCSENo32bw30llcum1rR1YhoAAckcEm5/Mkw BRfPoCeyBGz8GDXUHI6M6rno78tGEkpt5mfXQmkZCbxksSr/9Tgb3BKPYc3ApW6iJkrx T0CsmMNemLxX08AF14yAxjvEjFAPvNhJLbH+M3tTuxtwNlhDc7v9bqM/63Z/U5g6sytp dhSi82jOP3LNtSNEwSg4+4HpbhyNGytk3m/so5zxqXgxbItE7y9zfhlMsQM7s/fN7wFb f7TQ== MIME-Version: 1.0 X-Received: by 10.180.24.130 with SMTP id u2mr3921155wif.40.1375934181584; Wed, 07 Aug 2013 20:56:21 -0700 (PDT) Received: by 10.194.135.84 with HTTP; Wed, 7 Aug 2013 20:56:21 -0700 (PDT) Date: Thu, 8 Aug 2013 05:56:21 +0200 Message-ID: Subject: how to remove usb-storage devices without CAM errors From: Michael Schuh To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 03:56:23 -0000 H i@list, i have a simple wuestion caused by a "device loss". is there a special routine for unplugging usb-storage devices? in the meaning: may be settle some commends before unplugging the device other than umount. according to the handbook there ist no special routine. unmounting should be enough and pull the USB-Devie out of the bus. i could not find anything related by the help of the big oracle. i have some usb-sticks that i need to write with prepared disk-images by using dd. two or more drives are already plugged in and da0 is already finished, da1 or da2 still at writing. unplugging da0 causes a CAM error and interrupts the ongoing write. i am not sure if all writes to each different device gets stopped. this is a reproduceable behaviour thats new to me. see the listing below. let me know if i can and what to do to help to further identify and investigate this error. iirc this happens for the first time this way. my last upgrade before this was feb./march. time of svn checkout was 2013-07-22 so its may be already fixed? many thanks in advance regards michael =============== ugen3.2: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:8:0:-1: Attached to scbus8 da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 da0: Removable Direct Access SCSI-6 device da0: 40.000MB/s transfers da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) da0: quirks=0x2 ugen7.2: at usbus7 umass1: on usbus7 umass1: SCSI over Bulk-Only; quirks = 0x0100 umass1:9:1:-1: Attached to scbus9 da1 at umass-sim1 bus 1 scbus9 target 0 lun 0 da1: Removable Direct Access SCSI-6 device da1: 40.000MB/s transfers da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) da1: quirks=0x2 (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 ugen3.2: at usbus3 (disconnected) (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error umass0: (da0:at uhub3, port 3, addr 2 (disconnected) umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Error 5, Retries exhausted (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Error 5, Retries exhausted (da0:umass-sim0:0:0:0): got CAM status 0x44 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs (da0:umass-sim0:0:0:0): removing device entry From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 05:58:00 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E244C9C5 for ; Thu, 8 Aug 2013 05:58:00 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo102.cox.net (fed1rmfepo102.cox.net [68.230.241.144]) by mx1.freebsd.org (Postfix) with ESMTP id B6A082792 for ; Thu, 8 Aug 2013 05:58:00 +0000 (UTC) Received: from fed1rmimpo210 ([68.230.241.161]) by fed1rmfepo102.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130808055754.JVGL3896.fed1rmfepo102.cox.net@fed1rmimpo210> for ; Thu, 8 Aug 2013 01:57:54 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo210 with cox id A5xt1m00G2oShb2015xtaW; Thu, 08 Aug 2013 01:57:53 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020206.52033362.000E,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=drIF/Sc4 c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=iCVRR6hNiGIA:10 a=ktNfuVtv0skA:10 a=IkcTkHD0fZMA:10 a=05pWP5ZVAAAA:8 a=uyszvKpkjiMA:10 a=0Qu1Tt9fp2NXtEhOVVEA:9 a=QEXdDO2ut3YA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.7/8.14.7) with ESMTP id r77MjtcD034810; Wed, 7 Aug 2013 22:45:55 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <52033444.9060703@reynoldsnet.org> Date: Wed, 07 Aug 2013 23:01:40 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Rick Macklem Subject: SOLVED: Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- Firefox SQLite locking issue References: <1072840488.5640439.1375612342793.JavaMail.root@uoguelph.ca> In-Reply-To: <1072840488.5640439.1375612342793.JavaMail.root@uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 05:58:00 -0000 > About all you need to do is add a "V4: ..." line to your /etc/exports > and then set nfsv4_server_enable="YES" in /etc/rc.conf and reboot. > On the client mount, you need to add "nfsv4" as a mount option. I had to enable the proper daemons and mount on the client from the actual server mount point (previously in NFSv3 I could mount a symbolic link which pointed to the actual disk--now with NFSv4 I couldn't do that, but it's OK) but it worked! After I got my home dir to mount under NFSv4 I went into Xorg and fired up Firefox (with a brand new profile just to be on the safe side) and BOOM! Everything works that Firefox relies on SQLite for (bookmarks, and link history). Bookmark editor as well as the <- and -> arrows show up and work now as expected. I am running 8.4-STABLE as of Aug 6th on my server (it will be upgraded to 9.2-STABLE once I can find the time) and the client is 9.2-BETA2 just for the record. So it seems that 8.x and 9.x talk to each other just fine. I have not noticed anything odd performancewise--just that when I "umount" the directory it seems to "think about it" for 10-15 seconds before doing it. I don't know if that's just the "way it is" or if I can configure something more fine-tuned. However, I'm just happy--actually ecstatic--that it's working. That was my last missing link (no pun intended) to letting the "users" in the house on this new machine as their new desktop. Can't have FF broken! :) Thanks all for your responses and help. -jr From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 08:35:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EAAD3AE9; Thu, 8 Aug 2013 08:35:20 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A5C42F40; Thu, 8 Aug 2013 08:35:20 +0000 (UTC) Received: by mail-ve0-f169.google.com with SMTP id db10so2802299veb.14 for ; Thu, 08 Aug 2013 01:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PHmKcvO7jxWzzU+ha/4984/b7AhGKGXACDWZ3jIs/Ho=; b=snItP5TCwRyQcx2woHeIwTACJGxIWPpkLik8blWO6kUHDb0IkcbR7IO3/ZB6nki2yt DtMHxwHNMvjuXjNXwfuy8zM3uUIy7ewKLcihYqbnzt0VRsTHBKhcr9i7mUyYtvnjfXjn JArUGknXvQXNWwPypd6T5+cvmdxKXeOjlyxZiJXp43UaPKSw76HpYnjTStKCvmioexbZ CyRy85hKh6gJSq+QgHf6EqD9w1uM+fKDDwAx7rgtBYILKKLpecmbv6trNU2tmTvwUVvQ vAgCBNnHRQKfiL66mXzGJS19kx24OCnxsqoImn/fZF4gX5zlmNlXtTVb/U4sAYi0yvwL 821Q== MIME-Version: 1.0 X-Received: by 10.52.243.201 with SMTP id xa9mr1968536vdc.106.1375950919783; Thu, 08 Aug 2013 01:35:19 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Thu, 8 Aug 2013 01:35:19 -0700 (PDT) In-Reply-To: <20130807160528.GC13555@minime.local> References: <20130807160528.GC13555@minime.local> Date: Thu, 8 Aug 2013 12:35:19 +0400 Message-ID: Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: Gregory Shapiro Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 08:35:21 -0000 I'm sorry. What I have to do? I'm ready) 2013/8/7 Gregory Shapiro : >> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. >> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS >> you won't receive it. >> But in same time email passes from FreeBSD 9.1-RELEASE which uses >> Sendmail-8.14.5. > > The recent release made the following change: > > --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 > +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 > @@ -4726,7 +4726,12 @@ > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > int nmaps; > # if NETINET6 > - int flags = AI_DEFAULT|AI_ALL; > +# ifndef SM_IPNODEBYNAME_FLAGS > + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > +# endif /* SM_IPNODEBYNAME_FLAGS */ > + > + int flags = SM_IPNODEBYNAME_FLAGS; > int err; > # endif /* NETINET6 */ > char *maptype[MAXMAPSTACK]; > > Which is described in this release note: > > Drop support for IPv4-mapped IPv6 addresses to prevent the MTA > from using a mapped address over a legitimate IPv6 address > and to enforce the proper semantics over the IPv6 > connection. Problem noted by Ulrich Sporlein. > > It looks like that SERVFAIL from Microsoft's DNS server is getting > in the way of that. I can look at adding this exception to > WorkAroundBrokenAAAA as a possibility for a future release. > > I'd also like to hear feedback on whether the above change (changing > getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went > too far and what the accepted norm is for getipnodebyname(). > From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 09:35:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F0F4AD06; Thu, 8 Aug 2013 09:35:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A00C02346; Thu, 8 Aug 2013 09:35:41 +0000 (UTC) Received: by mail-vb0-f49.google.com with SMTP id w16so2946845vbb.8 for ; Thu, 08 Aug 2013 02:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=STQv6zXYlebc+MJb+fEygoLyeo1mQaoOMtuQMjl40gA=; b=yKqRQVrXB6NjZlhndGUQGKOId1iPKoyAIGUKkLWzoca+unIQP5VaH9/2SGPHeACg+z GackxsU7SJYZcFT3CtxzRbl5mgLBGsNd6m6qIa9D4AIaAIx50b65VNKZtcq/Phd5L1r1 xJyQ8f1BMkxgGZ82q5xWwdwfKfrttQ7t69Xm4N4BuZpkW2w0oY/QBvlT1Kn3Ksf38W8G 3ABk8zUm2vs+7DeRQblPdWn4HHcU8OOSmUvveTwL3NSZK8dkfQNiicwrNhvrTRMQvtoC v7mOBE/M3WKsWtnc7HwSUnussyCOw7NnfywmXKlUak2n8bvPQL8MJB/4XDH/HzPOU8uC 1GZw== MIME-Version: 1.0 X-Received: by 10.58.85.161 with SMTP id i1mr2485381vez.97.1375954540726; Thu, 08 Aug 2013 02:35:40 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Thu, 8 Aug 2013 02:35:40 -0700 (PDT) In-Reply-To: <20130807160528.GC13555@minime.local> References: <20130807160528.GC13555@minime.local> Date: Thu, 8 Aug 2013 13:35:40 +0400 Message-ID: Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: Gregory Shapiro Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 09:35:42 -0000 I tried to revert mentioned patch, i.e. applied this --- sendmail/conf.c.orig 2013-08-08 12:28:40.000000000 +0400 +++ sendmail/conf.c 2013-08-08 12:31:17.000000000 +0400 @@ -4294,12 +4294,7 @@ #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ int nmaps; # if NETINET6 -# ifndef SM_IPNODEBYNAME_FLAGS - /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ -# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG -# endif /* SM_IPNODEBYNAME_FLAGS */ - - int flags = SM_IPNODEBYNAME_FLAGS; + int flags = AI_DEFAULT|AI_ALL; int err; # endif /* NETINET6 */ char *maptype[MAXMAPSTACK]; Sendmail started to work 2013/8/7 Gregory Shapiro : >> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. >> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS >> you won't receive it. >> But in same time email passes from FreeBSD 9.1-RELEASE which uses >> Sendmail-8.14.5. > > The recent release made the following change: > > --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 > +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 > @@ -4726,7 +4726,12 @@ > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > int nmaps; > # if NETINET6 > - int flags = AI_DEFAULT|AI_ALL; > +# ifndef SM_IPNODEBYNAME_FLAGS > + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > +# endif /* SM_IPNODEBYNAME_FLAGS */ > + > + int flags = SM_IPNODEBYNAME_FLAGS; > int err; > # endif /* NETINET6 */ > char *maptype[MAXMAPSTACK]; > > Which is described in this release note: > > Drop support for IPv4-mapped IPv6 addresses to prevent the MTA > from using a mapped address over a legitimate IPv6 address > and to enforce the proper semantics over the IPv6 > connection. Problem noted by Ulrich Sporlein. > > It looks like that SERVFAIL from Microsoft's DNS server is getting > in the way of that. I can look at adding this exception to > WorkAroundBrokenAAAA as a possibility for a future release. > > I'd also like to hear feedback on whether the above change (changing > getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went > too far and what the accepted norm is for getipnodebyname(). > From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 11:39:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9A228F1A for ; Thu, 8 Aug 2013 11:39:19 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C72B2A73 for ; Thu, 8 Aug 2013 11:39:19 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A315920E90 for ; Thu, 8 Aug 2013 07:39:12 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Thu, 08 Aug 2013 07:39:12 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=/SAys8xajPfEjgGajqdVmGZe0rc=; b=Abs7H cKTcACH6qBnTIJPto1ATcWj8VXx9VhFRF3+VHbVdxRtpENeAATtK1nT7VZs2r+3i fjVjT66a8yeRRCN6ioFP480JGQuFrWTbMkhx/UyGWjHzPoSlck8n0+tNyNByll8b c2E9Dg6AHLTBvefj6ylgmYy1Gzd9cD97W+xoFQ= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 873B8B022D3; Thu, 8 Aug 2013 07:39:12 -0400 (EDT) Message-Id: <1375961952.24413.7481975.02B045E3@webmail.messagingengine.com> X-Sasl-Enc: EVR/8C2wEhok7UiwcCQdIJ34rr9qMbuP3yk7iTwwklFh 1375961952 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d9f253bf Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network Date: Thu, 08 Aug 2013 06:39:12 -0500 In-Reply-To: References: <20130807160528.GC13555@minime.local> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 11:39:19 -0000 On Thu, Aug 8, 2013, at 4:35, Pavel Timofeev wrote: > I tried to revert mentioned patch, i.e. applied this > > --- sendmail/conf.c.orig 2013-08-08 12:28:40.000000000 +0400 > +++ sendmail/conf.c 2013-08-08 12:31:17.000000000 +0400 > @@ -4294,12 +4294,7 @@ > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && > SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > int nmaps; > # if NETINET6 > -# ifndef SM_IPNODEBYNAME_FLAGS > - /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > -# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > -# endif /* SM_IPNODEBYNAME_FLAGS */ > - > - int flags = SM_IPNODEBYNAME_FLAGS; > + int flags = AI_DEFAULT|AI_ALL; > int err; > # endif /* NETINET6 */ > char *maptype[MAXMAPSTACK]; > > Sendmail started to work > Is this patch going to be applied to revert this behavior before 9.2-RELEASE? It seems to me that 8.14.7 violates our POLA... From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 11:53:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19B1D5FD for ; Thu, 8 Aug 2013 11:53:35 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E90D92B8E for ; Thu, 8 Aug 2013 11:53:34 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id up15so3050497pbc.40 for ; Thu, 08 Aug 2013 04:53:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jkm7z4mwZxMooMmVM1vgsUD9/4yxjCm1hEI/yMUIv84=; b=pkYBUdkgPOFakgiabCG1hQcl1+ngKhoxWCs6tUPpaTV6+RfFrHRkAMMXRF5PVxRuYQ Gh5326lqePn2an9rXC2p78kAyl0sGRZ+Csl16hGb6l1vkBs3BuYtp1zbgj1mmJ3vvOEY S9Lj33eIDXocYrWnFv1cx685219f1uM/mTnnTCPQwRQzPAT6UT8Nf7ZdHG3OVa9LT427 DHSPIARtrb88+3q1Gyzd8V3O9BjnogAT0/08cGcOESWfCZ1CnkEIR3d3nAqQ4tyh3GNW zkumOS5n97UVXyuBNu/Unk4bKn4Ehx8YYHPexvpwF5DZM84XUCBt862OGIHm/5MXf1+J /ykg== MIME-Version: 1.0 X-Received: by 10.66.144.104 with SMTP id sl8mr5833434pab.9.1375962814265; Thu, 08 Aug 2013 04:53:34 -0700 (PDT) Received: by 10.68.211.106 with HTTP; Thu, 8 Aug 2013 04:53:34 -0700 (PDT) In-Reply-To: References: Date: Thu, 8 Aug 2013 14:53:34 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 11:53:35 -0000 On Wed, Aug 7, 2013 at 7:26 PM, George Kontostanos wrote: > Hi list, > > With a 9.1 system and the following: > > /etc/sysctl.conf: > > security.jail.mount_allowed=1 > security.jail.mount_zfs_allowed=1 > security.jail.enforce_statfs=1 > > zfs set jailed=on Pool > zfs jail 1 Pool > > jexec 1 tcsh > > jail1# zfs create Pool/test1 > jail1# zfs list > > NAME USED AVAIL REFER MOUNTPOINT > Pool 223K 19.6G 31K /Pool > Pool/test1 31K 19.6G 31K /Pool/test > > After upgrading to 9.2-RC1 the same operation results in: > > jail1# zfs create Pool/test2 > > cannot create 'Pool/test2': permission denied > > What am I missing? > > Thanks > > > -- > George Kontostanos > --- > > Anybody? From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 11:58:48 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 201AD98E for ; Thu, 8 Aug 2013 11:58:48 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id D9E502BE5 for ; Thu, 8 Aug 2013 11:58:47 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqMEAKuGA1KDaFve/2dsb2JhbABbgztQgxS7NYEwdIIkAQEBAwEBAQEgBCcgCwUWGAICDRIHAikBCSYGCAcEARwEh2kGDKYhgRCRMYEojT0NdTQHgmeBJwOVGoNxkCWBX4FVIDJ8Bxci X-IronPort-AV: E=Sophos;i="4.89,838,1367985600"; d="scan'208";a="44056190" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 08 Aug 2013 07:58:41 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 3B7B5B3F1B; Thu, 8 Aug 2013 07:58:41 -0400 (EDT) Date: Thu, 8 Aug 2013 07:58:41 -0400 (EDT) From: Rick Macklem To: John Reynolds Message-ID: <1897895443.7142339.1375963121233.JavaMail.root@uoguelph.ca> In-Reply-To: <52033444.9060703@reynoldsnet.org> Subject: Re: SOLVED: Re: NFS locking between 8.3-STABLE (jan 2013) and 9.2-BETA2 -- Firefox SQLite locking issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 11:58:48 -0000 John Reynolds wrote: > > About all you need to do is add a "V4: ..." line to your > > /etc/exports > > and then set nfsv4_server_enable="YES" in /etc/rc.conf and reboot. > > On the client mount, you need to add "nfsv4" as a mount option. > I had to enable the proper daemons and mount on the client from the > actual server mount point (previously in NFSv3 I could mount a > symbolic > link which pointed to the actual disk--now with NFSv4 I couldn't do > that, but it's OK) but it worked! > > After I got my home dir to mount under NFSv4 I went into Xorg and > fired > up Firefox (with a brand new profile just to be on the safe side) and > BOOM! Everything works that Firefox relies on SQLite for (bookmarks, > and > link history). Bookmark editor as well as the <- and -> arrows show > up > and work now as expected. > > I am running 8.4-STABLE as of Aug 6th on my server (it will be > upgraded > to 9.2-STABLE once I can find the time) and the client is 9.2-BETA2 > just > for the record. So it seems that 8.x and 9.x talk to each other just > fine. I have not noticed anything odd performancewise--just that when > I > "umount" the directory it seems to "think about it" for 10-15 seconds > before doing it. I don't know if that's just the "way it is" or if I > can > configure something more fine-tuned. > It is "just the way it is", I think. It has to close all outstanding opens (and return delegations, if they are enabled) during the umount. I'm a bit surprised it takes 10-15sec, but not that amazed.;-) Have fun with it, rick ps: I realized I forgot to mention enabling the nfsuserd daemon on both client and server in the last post. > However, I'm just happy--actually ecstatic--that it's working. That > was > my last missing link (no pun intended) to letting the "users" in the > house on this new machine as their new desktop. Can't have FF broken! > :) > > Thanks all for your responses and help. > > -jr > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 11:59:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3160BA91 for ; Thu, 8 Aug 2013 11:59:23 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 057B52BF5 for ; Thu, 8 Aug 2013 11:59:22 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CE9A821225 for ; Thu, 8 Aug 2013 07:59:20 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Thu, 08 Aug 2013 07:59:21 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=4G5OT9YeLIBtVEZi21Pg40YhX0E=; b=K/6 W5n1zuLwac+Tz5QY5oMWxajazZco1Ia2mvyLRQNzWI8TmBNyymeNtZgmqFQcZwTs UUsw5zyFeiPyiG1Ae6FuwEwzZHEuhj4EeSjc/e8KRMmznfiQ4sZJuYZN/NtMCox/ sf/pEUUwDjUaOptxemqz1elpxvz4Ii46QaT3pImw= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id AECA6B022D3; Thu, 8 Aug 2013 07:59:20 -0400 (EDT) Message-Id: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> X-Sasl-Enc: +uyl1T3D8jbv2QZ30p4FiGK0bi2B/NdFSG+r+/6ePCR2 1375963160 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d9f253bf In-Reply-To: References: Subject: Re: ZFS in jails 9.2-RC1 permission denied Date: Thu, 08 Aug 2013 06:59:20 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 11:59:23 -0000 On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > Anybody? > Can you provide your jail configuration? I think 9.2 introduces the new /etc/jail.conf functionality and perhaps it somehow it broke the way you were doing it previously? If so, the old method is supposed to be work as well... From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 12:00:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B467BD15 for ; Thu, 8 Aug 2013 12:00:04 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A38B2C0F for ; Thu, 8 Aug 2013 12:00:03 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r78BxxDs069887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 13:59:59 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r78Bxxle069884; Thu, 8 Aug 2013 13:59:59 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Thu, 8 Aug 2013 13:59:58 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: George Kontostanos Subject: Re: ZFS in jails 9.2-RC1 permission denied In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-494027019-1375963199=:90799" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 12:00:04 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-494027019-1375963199=:90799 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Thu, 8 Aug 2013 14:53+0300, George Kontostanos wrote: > On Wed, Aug 7, 2013 at 7:26 PM, George Kontostanos wrote: > > > Hi list, > > > > With a 9.1 system and the following: > > > > /etc/sysctl.conf: > > > > security.jail.mount_allowed=1 > > security.jail.mount_zfs_allowed=1 > > security.jail.enforce_statfs=1 > > > > zfs set jailed=on Pool > > zfs jail 1 Pool > > > > jexec 1 tcsh > > > > jail1# zfs create Pool/test1 > > jail1# zfs list > > > > NAME USED AVAIL REFER MOUNTPOINT > > Pool 223K 19.6G 31K /Pool > > Pool/test1 31K 19.6G 31K /Pool/test > > > > After upgrading to 9.2-RC1 the same operation results in: > > > > jail1# zfs create Pool/test2 > > > > cannot create 'Pool/test2': permission denied > > > > What am I missing? > > > > Thanks > > > > -- > > George Kontostanos > > --- > > > > > Anybody? I'm just guessing, but I doubt a jail would be able to create new ZFS filesystems outside its own structure, if at all able. A jail would however be allowed to (un)mount already existing filesystems within its own structure, i.e. Pool/test1. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-494027019-1375963199=:90799-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 12:05:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 553B2F23 for ; Thu, 8 Aug 2013 12:05:27 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 287E72CB7 for ; Thu, 8 Aug 2013 12:05:26 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5E72B20AEF for ; Thu, 8 Aug 2013 08:05:26 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Thu, 08 Aug 2013 08:05:26 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=qWib/sMQx5/oc+bajHgvsLln92s=; b=SqX 8ovREcskavV1olP0tWYzkh9Sq69Dj8pUBJ2Fo8zHZmL5oFogQxfsaCCif0AlDRnZ au28AubDkI5ozZpgy1n+NuS9GROq7Nzyee3O/doTF2piBJTnMHs3OyrlYC1LsiZW Oe3+QpnEbmDHNChWfTmtLvkvMK2g6E6loTY1wyHc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 44860B022D3; Thu, 8 Aug 2013 08:05:26 -0400 (EDT) Message-Id: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> X-Sasl-Enc: F/E4bY51pUDUhVcV7V2HnqvuVs9XAWsru48hBZwPX8NJ 1375963526 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: MessagingEngine.com Webmail Interface - ajax-d9f253bf In-Reply-To: References: Subject: Re: ZFS in jails 9.2-RC1 permission denied Date: Thu, 08 Aug 2013 07:05:26 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 12:05:27 -0000 On Thu, Aug 8, 2013, at 6:59, Trond Endrest=F8l wrote: >=20 > I'm just guessing, but I doubt a jail would be able to create new ZFS=20 > filesystems outside its own structure, if at all able. A jail would=20 > however be allowed to (un)mount already existing filesystems within=20 > its own structure, i.e. Pool/test1. >=20 When I first reviewed his post I clearly confused "mounting" with "creating a new zfs filesystem". Is that even supposed to be permitted in a jail? I almost feel a sysctl disabling that by default would be nice... DoS by zfs filesystem creation/deletion, anyone? From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 12:20:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0E9FB506; Thu, 8 Aug 2013 12:20:41 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 768362DEF; Thu, 8 Aug 2013 12:20:40 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r78CKan3070049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 14:20:36 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r78CKakW070046; Thu, 8 Aug 2013 14:20:36 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Thu, 8 Aug 2013 14:20:36 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Mark Felder Subject: Re: ZFS in jails 9.2-RC1 permission denied In-Reply-To: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> Message-ID: References: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-1860324778-1375964436=:90799" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 12:20:41 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-1860324778-1375964436=:90799 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Thu, 8 Aug 2013 07:05-0500, Mark Felder wrote: > On Thu, Aug 8, 2013, at 6:59, Trond Endrestøl wrote: > > > > I'm just guessing, but I doubt a jail would be able to create new ZFS > > filesystems outside its own structure, if at all able. A jail would > > however be allowed to (un)mount already existing filesystems within > > its own structure, i.e. Pool/test1. > > > > When I first reviewed his post I clearly confused "mounting" with > "creating a new zfs filesystem". Is that even supposed to be permitted > in a jail? I almost feel a sysctl disabling that by default would be > nice... DoS by zfs filesystem creation/deletion, anyone? I started experimenting with jails last Sunday. There is certainly more to explore and learn. Just a few more hours and I'm heading home to do some lab work. ;-) -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-1860324778-1375964436=:90799-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 13:06:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 594CD5F5 for ; Thu, 8 Aug 2013 13:06:50 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA43720E6 for ; Thu, 8 Aug 2013 13:06:49 +0000 (UTC) Received: from rufus.webfusion.com (mail.heartinternet.co.uk [79.170.40.31]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id r78D6e5v093091 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 8 Aug 2013 14:06:41 +0100 (BST) (envelope-from matthew@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk r78D6e5v093091 Authentication-Results: smtp.infracaninophile.co.uk/r78D6e5v093091; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy) X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host mail.heartinternet.co.uk [79.170.40.31] claimed to be rufus.webfusion.com Message-ID: <520397E0.1090209@freebsd.org> Date: Thu, 08 Aug 2013 14:06:40 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130801 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: ZFS in jails 9.2-RC1 permission denied References: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> In-Reply-To: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.97.8 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 13:06:50 -0000 On 08/08/2013 13:05, Mark Felder wrote: > On Thu, Aug 8, 2013, at 6:59, Trond Endrestøl wrote: >> >> I'm just guessing, but I doubt a jail would be able to create new ZFS >> filesystems outside its own structure, if at all able. A jail would >> however be allowed to (un)mount already existing filesystems within >> its own structure, i.e. Pool/test1. >> > > When I first reviewed his post I clearly confused "mounting" with > "creating a new zfs filesystem". Is that even supposed to be permitted > in a jail? I almost feel a sysctl disabling that by default would be > nice... DoS by zfs filesystem creation/deletion, anyone? There's a 'zfs jail' command and a 'jailed' property you can set on a ZFS which I believes allow you to manage that ZFS from within the jail. I think that extends to creating other ZFSes beneath that one (which would inherit the 'jailed' property), BICBW. Mostly I find it easier to just manage the ZFSes from the host system but then again, I'm not really making very extensive use of jails. Cheers, Matthew From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 13:35:25 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0C4A9EC8 for ; Thu, 8 Aug 2013 13:35:25 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from cpsmtpb-ews02.kpnxchange.com (cpsmtpb-ews02.kpnxchange.com [213.75.39.5]) by mx1.freebsd.org (Postfix) with ESMTP id 779652316 for ; Thu, 8 Aug 2013 13:35:24 +0000 (UTC) Received: from cpsps-ews11.kpnxchange.com ([10.94.84.178]) by cpsmtpb-ews02.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Thu, 8 Aug 2013 15:35:15 +0200 Received: from CPSMTPM-TLF103.kpnxchange.com ([195.121.3.6]) by cpsps-ews11.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Thu, 8 Aug 2013 15:35:14 +0200 Received: from sjakie.klop.ws ([212.182.167.131]) by CPSMTPM-TLF103.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Thu, 8 Aug 2013 15:35:14 +0200 Received: from 212-182-167-131.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id 5E2D51458F for ; Thu, 8 Aug 2013 15:35:14 +0200 (CEST) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: how to remove usb-storage devices without CAM errors References: Date: Thu, 08 Aug 2013 15:35:13 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-OriginalArrivalTime: 08 Aug 2013 13:35:14.0594 (UTC) FILETIME=[1D01F820:01CE943C] X-RcptDomain: freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 13:35:25 -0000 On Thu, 08 Aug 2013 05:56:21 +0200, Michael Schuh wrote: > H i@list, > > i have a simple wuestion caused by a "device loss". > > is there a special routine for unplugging usb-storage devices? > in the meaning: > may be settle some commends before unplugging the device > other than umount. > according to the handbook there ist no special routine. > unmounting should be enough and pull the USB-Devie out of the bus. > > i could not find anything related by the help of the big oracle. > > > i have some usb-sticks that i need to write with prepared disk-images by > using dd. > two or more drives are already plugged in > and da0 is already finished, da1 or da2 still at writing. > unplugging da0 causes a CAM error and interrupts the ongoing write. > i am not sure if all writes to each different device gets stopped. > this is a reproduceable behaviour thats new to me. > see the listing below. > > let me know if i can and what to do to help to further identify > and investigate this error. > > iirc this happens for the first time this way. > my last upgrade before this was feb./march. > time of svn checkout was 2013-07-22 so its may be already fixed? > > many thanks in advance > > regards > > michael Does 'camcontrol eject ' help? It tells CAM to eject the device. This is usefull for CD's, but maybe to for preventing errors for USB-storage. Ronald. > > =============== > > ugen3.2: at usbus3 > umass0: on usbus3 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:8:0:-1: Attached to scbus8 > da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 > da0: Removable Direct Access SCSI-6 device > da0: 40.000MB/s transfers > da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da0: quirks=0x2 > ugen7.2: at usbus7 > umass1: on usbus7 > umass1: SCSI over Bulk-Only; quirks = 0x0100 > umass1:9:1:-1: Attached to scbus9 > da1 at umass-sim1 bus 1 scbus9 target 0 lun 0 > da1: Removable Direct Access SCSI-6 device > da1: 40.000MB/s transfers > da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da1: quirks=0x2 > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > ugen3.2: at usbus3 (disconnected) > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > umass0: (da0:at uhub3, port 3, addr 2 (disconnected) > umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Error 5, Retries exhausted > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 > 00 > 00 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 > 00 > 00 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Error 5, Retries exhausted > (da0:umass-sim0:0:0:0): got CAM status 0x44 > (da0:umass-sim0:0:0:0): fatal error, failed to attach to device > (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs > (da0:umass-sim0:0:0:0): removing device entry > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 14:20:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 720EED6F for ; Thu, 8 Aug 2013 14:20:05 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1A812263A for ; Thu, 8 Aug 2013 14:20:04 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,839,1367989200"; d="scan'208,217";a="39384111" Message-ID: <5203A90D.6020008@vangyzen.net> Date: Thu, 8 Aug 2013 09:19:57 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: J David Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> <520116DE.8030305@vangyzen.net> <52013992.4050101@vangyzen.net> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org, dave@mischler.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 14:20:05 -0000 On 08/06/2013 14:23, J David wrote: > On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen wrote: >>> on an otherwise idle amd64 system with 4 CPUs. The first command in the >>> build.log file: >>> >>> rm -rf /usr/obj/home/freebsd/tmp >>> >>> took over three minutes. It should have taken about three /seconds/. >>> >>> "uptime" reported a load average of around 1.00. >>> "top" showed no threads (user or kernel) using CPU. >>> "iostat" showed an average of less than 20 tps on ada0. >>> "rm" was usually in the RUN state. > We are looking at something similar. Would you be able to try to > reproduce it using a kernel with: > > nooptions SCHED_ULE > options SCHED_4BSD > > to see if it makes a difference? It seems to, but the problem is > inconsistent enough that I can't be sure. The 4BSD scheduler does //not// exhibit this problem. I tested with the latest releng/9.2 (r254054) and an otherwise GENERIC config. Eric From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 14:20:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 54544E7A for ; Thu, 8 Aug 2013 14:20:53 +0000 (UTC) (envelope-from haramrae@gmail.com) Received: from mail-vb0-x234.google.com (mail-vb0-x234.google.com [IPv6:2607:f8b0:400c:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13150266E for ; Thu, 8 Aug 2013 14:20:53 +0000 (UTC) Received: by mail-vb0-f52.google.com with SMTP id f12so3244112vbg.11 for ; Thu, 08 Aug 2013 07:20:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xaMHKi1mfMoxTXyCLJp7FzDZsTfCRCj6SFnwFEsLhYw=; b=QgBpU+BWp3p0SNXVGAUsspeAwY2JedJpHgwEIRAxnCVbu094rDlnOT45xovyrTxuQT TDULb8eqImcgvwHzp475xlxpiPXBSwcGsyJBowz1pIWJ7crEFv0d7BXtOm+FPgWxA+8h uRYhSTsNb4pU+GRvPbaf8+2JuBijr5QrxRuw+AZVmUYvBK7emV0+pQd2OtH9v2bTvF/0 5H9z7Vhy1wtPLT8a3yZcngS0pFtt1zeUMDT018Eb3r9pu8hI5KNvfreQ30xQv4TqFeE0 KhZ9AolLayCkt3dUXMiKTNsUw7H2vFkeLLue24g19p+B5zRaSFA/oYBpKgTgJEnU/fGX Z49Q== MIME-Version: 1.0 X-Received: by 10.52.164.227 with SMTP id yt3mr2696886vdb.107.1375971652189; Thu, 08 Aug 2013 07:20:52 -0700 (PDT) Received: by 10.220.5.194 with HTTP; Thu, 8 Aug 2013 07:20:52 -0700 (PDT) In-Reply-To: References: Date: Thu, 8 Aug 2013 16:20:52 +0200 Message-ID: Subject: Re: how to remove usb-storage devices without CAM errors From: Alban Hertroys To: Michael Schuh Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 14:20:53 -0000 On 8 August 2013 05:56, Michael Schuh wrote: > ugen3.2: at usbus3 > umass0: on usbus3 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:8:0:-1: Attached to scbus8 > da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 > da0: Removable Direct Access SCSI-6 device > da0: 40.000MB/s transfers > da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da0: quirks=0x2 > > ugen7.2: at usbus7 > umass1: on usbus7 > umass1: SCSI over Bulk-Only; quirks = 0x0100 > umass1:9:1:-1: Attached to scbus9 > da1 at umass-sim1 bus 1 scbus9 target 0 lun 0 > da1: Removable Direct Access SCSI-6 device > da1: 40.000MB/s transfers > da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da1: quirks=0x2 > > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > ugen3.2: at usbus3 (disconnected) > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > umass0: (da0:at uhub3, port 3, addr 2 (disconnected) > umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command > I'm mostly guessing, but what I suspect that happens is that after you successfully remove da0, the former da1 becomes da0 and any operations on da1 (or da2 that now became da1) get aborted. That you just happen to have exactly identical USB sticks in this case does not help diagnosing whether that's the case though. I'm really hoping this isn't actually what happens here, but it would explain what you're seeing. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 14:41:14 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8E6334E3 for ; Thu, 8 Aug 2013 14:41:14 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 521C427B8 for ; Thu, 8 Aug 2013 14:41:13 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,839,1367989200"; d="scan'208";a="39387580" Message-ID: <5203AE08.30504@vangyzen.net> Date: Thu, 8 Aug 2013 09:41:12 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: J David Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1 References: <1375737316.96778.10.camel@firkin.mischler.com> <520116DE.8030305@vangyzen.net> <52013992.4050101@vangyzen.net> <5203A90D.6020008@vangyzen.net> In-Reply-To: <5203A90D.6020008@vangyzen.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, dave@mischler.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 14:41:14 -0000 On 08/08/2013 09:19, Eric van Gyzen wrote: > On 08/06/2013 14:23, J David wrote: >> On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen wrote: >>>> on an otherwise idle amd64 system with 4 CPUs. The first command in the >>>> build.log file: >>>> >>>> rm -rf /usr/obj/home/freebsd/tmp >>>> >>>> took over three minutes. It should have taken about three /seconds/. >>>> >>>> "uptime" reported a load average of around 1.00. >>>> "top" showed no threads (user or kernel) using CPU. >>>> "iostat" showed an average of less than 20 tps on ada0. >>>> "rm" was usually in the RUN state. >> We are looking at something similar. Would you be able to try to >> reproduce it using a kernel with: >> >> nooptions SCHED_ULE >> options SCHED_4BSD >> >> to see if it makes a difference? It seems to, but the problem is >> inconsistent enough that I can't be sure. > The 4BSD scheduler does //not// exhibit this problem. I tested with the > latest releng/9.2 (r254054) and an otherwise GENERIC config. To be thorough, I built a GENERIC kernel at the same rev, and it still exhibits the problem. Eric From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 14:50:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 254E98DE; Thu, 8 Aug 2013 14:50:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F00B1286D; Thu, 8 Aug 2013 14:50:48 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id BBC30AAFE; Thu, 8 Aug 2013 14:50:47 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us BBC30AAFE Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 8 Aug 2013 10:50:45 -0400 From: Glen Barber To: "freebsd@omnilan.de" Subject: Re: Some missong patches in 9.2-RC2 Message-ID: <20130808145045.GA17282@glenbarber.us> References: <520283A1.1070404@omnilan.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <520283A1.1070404@omnilan.de> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 14:50:49 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 07, 2013 at 07:28:01PM +0200, freebsd@omnilan.de wrote: > Hello, >=20 > I went through my local patches against base/releng/, 9.2 in that case. > There are some fixes which are noct in 9.2-RC1: >=20 > - Regarding kerberized builds: > http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043902.html >=20 I'll take a look at this, but I do not see this change even committed to head/ yet. > - Regarding mfi and >2TB corruption, seems MFC reminder failed > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D173291 >=20 Closed: Mon Dec 10 06:34:48 UTC 2012 > - Regarding mount failok (seems r230226 got lost?) > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D163668&cat=3Dconf >=20 Closed-Date: Mon Jun 11 18:25:59 UTC 2012 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D163668&cat=3Dconf#reply6 Glen --DocE+STaALJfprDB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSA7BFAAoJEFJPDDeguUajIdkIAJnjiS6V47L7wSmJFF7K4p0I rMmZXUz3K9IKM4kQOdD2wxweqJ342yQGrmLvQoRR4/c/q+BqS/Mg3I+F+aYUL3Nr 6qpgTMsSgbGe0S6nclltR8B6LtGduS6dsXb8uQ1C58LgjuJ3DClonk5R0Dj6w+IL +cPNHfBP/aBVJ1EBnYTt8lmBYx9BQO7Ol8GFEiuaPvTiEBJQA6RfHoQzyroE3UMI dHD/gi59EFCXTNqcvsVPTDBoMf0nct1ngkPAr+qoc/98Pl4VcQC+c64sUK8FDrau 4BhfYuWy4U0t+k1qFkeE6VwejtiAiaO/JmphvmjKqVH+1SYijopNvsBGWfd2ogA= =bL8O -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 15:21:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE209903; Thu, 8 Aug 2013 15:21:32 +0000 (UTC) (envelope-from nicolas.roosen@gmail.com) Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 594262AD9; Thu, 8 Aug 2013 15:21:32 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id c11so2722306wgh.20 for ; Thu, 08 Aug 2013 08:21:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=Zs0SHZILj6Zcae5ZHueP+jgE6kQXSonaIa07Mhjb088=; b=cAcG5og+LYrJFaGadLp/Ai38TeOD4GsI4gJ1AHGM2MtaTJOUm9vRHpsIZhawLZ/zrS hAG8t4G36ayQm+bbnSlAeUrB+HEFXVvXgmOiqIC6SyDkC3d29mAXJQEvtF70DTtrq37P L86CYx7kE51TbpKMeGj3piCV7YL8IyYZ+4VYjj6hpNHir6oz72jyvC7Xw5Jf+FpfNhS6 a2k2cWKdph7ajBueooSYNNxxV8UTkDne5GcMmZqW89Sr7bIzgTuTntRZkXw1NwQdggha /YGQnEteNCVyjjBuI03kJJF5T0SoDjzK0rnvLZQO+0cDwT7JJvR8SXpAqEuEfbtExaCz chQA== X-Received: by 10.180.39.212 with SMTP id r20mr5446366wik.13.1375975290613; Thu, 08 Aug 2013 08:21:30 -0700 (PDT) Received: from [192.168.100.100] (205.39.201.77.rev.sfr.net. [77.201.39.205]) by mx.google.com with ESMTPSA id fz8sm18552557wic.0.2013.08.08.08.21.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 08:21:29 -0700 (PDT) From: Nicolas Roosen Content-Type: multipart/signed; boundary="Apple-Mail=_2F9CDD00-E66F-4C8A-8BB7-AC2542F26D75"; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: URTW driver and AHDEMO mode Date: Thu, 8 Aug 2013 17:21:27 +0200 Message-Id: <49CE2BF3-612B-42AA-9A59-83E8FB5F99F9@gmail.com> To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: weongyo@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 15:21:33 -0000 --Apple-Mail=_2F9CDD00-E66F-4C8A-8BB7-AC2542F26D75 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi, I'm (successfully) using an ALFA AWUS036H usb wireless network adapter = on FreeBSD 9.1, with the urtw driver. I can monitor networks (using Kismet or airodump-ng), but there is = something I can't do: inject packets to the device. And for one simple = reason: this seems not to be supported by the driver (the AHDEMO mode = isn't available). Any idea how to add this capability in the source code? Thanks! Nicolas Vos conversations sont priv=E9es, s=E9curisez-les. Your conversations are private, secure them. https://gpgtools.org or http://gpg4win.org --Apple-Mail=_2F9CDD00-E66F-4C8A-8BB7-AC2542F26D75 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJSA7d3AAoJEIylYwQV0UQc1ZEH/0vglbENf41FR4F5fKoPYLk7 WUqxhKVqhLOy1asS6UwbhSPZgM8ZsSgPJTyVDK1mOC671tl4/tsm6qaHzb4bQJq7 KrpZPWocSkwo8qWna7OFMLbwefIVmod6pdAGyBJlsJ9FLZux0rvQG5QRr+R85sJB kzt+zyiKYG/0wfGKP0Oduon+ABcENaotRcy31kSZk6Mq9jYnIYqJ4ghr/dfo4Key nvj9inukEHWZC/Ek3qX9xwSnkcX3kdasrohogFX1kuleLMOY+DK2NkwknkejpveN GdlIsiaDLkyg3Af7Cu4mLrsicN5kVncrZAlfUE8h4LFsp/XKfrG5nxpKguSD+z0= =xP5m -----END PGP SIGNATURE----- --Apple-Mail=_2F9CDD00-E66F-4C8A-8BB7-AC2542F26D75-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 15:46:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5997C6BD for ; Thu, 8 Aug 2013 15:46:57 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 23F6F2DA0 for ; Thu, 8 Aug 2013 15:46:57 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id n12so5443471oag.39 for ; Thu, 08 Aug 2013 08:46:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Whi7abrTCaa/oClVFD6HHABCbdshrCHNwZT64Lw7DRc=; b=eNC/GdtCdAifmNe7VvwjifjolmuqAe+aIcIGmcEDJ7mI78j3dys7ygvGEL4dPBCdxI 79oRv2VqP3W3yJ84hzir84yrejHzUik4YhX99S8GWyAYVDbNmoUojUb16uw2jo0Cm1D8 4oTxtnTs3rJAD1UcPmYUfaNXXmk6EuWkH9Fe/P4Pyc/4wB8jRQPkHiMUF4HjlpAjb3Xi WS4OOWxJCGweEZnuFGbdUK0GafZ02ZuZi0TlxWuc8FzZRpZsJmXJ4HBcXnRNRRoriQ1J ySPkOSoxQc/kMIXR9TwMrXg58YEIQWdKJpWRdneMdSr0qUo0xXstTBpi91NCJJc4GnJi JrSA== MIME-Version: 1.0 X-Received: by 10.60.124.14 with SMTP id me14mr4795085oeb.4.1375976816367; Thu, 08 Aug 2013 08:46:56 -0700 (PDT) Received: by 10.60.172.40 with HTTP; Thu, 8 Aug 2013 08:46:56 -0700 (PDT) In-Reply-To: References: Date: Thu, 8 Aug 2013 17:46:56 +0200 Message-ID: Subject: Re: how to remove usb-storage devices without CAM errors From: Michael Schuh To: Alban Hertroys Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 15:46:57 -0000 2013/8/8 Alban Hertroys > On 8 August 2013 05:56, Michael Schuh wrote: > >> ugen3.2: at usbus3 >> umass0: on usbus3 >> umass0: SCSI over Bulk-Only; quirks = 0x0100 >> umass0:8:0:-1: Attached to scbus8 >> da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 >> da0: Removable Direct Access SCSI-6 device >> da0: 40.000MB/s transfers >> da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) >> da0: quirks=0x2 >> > > >> ugen7.2: at usbus7 >> umass1: on usbus7 >> umass1: SCSI over Bulk-Only; quirks = 0x0100 >> umass1:9:1:-1: Attached to scbus9 >> da1 at umass-sim1 bus 1 scbus9 target 0 lun 0 >> da1: Removable Direct Access SCSI-6 device >> da1: 40.000MB/s transfers >> da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) >> da1: quirks=0x2 >> > > >> (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 >> ugen3.2: at usbus3 (disconnected) >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> umass0: (da0:at uhub3, port 3, addr 2 (disconnected) >> umass-sim0:0:0:0): Retrying command >> (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Retrying command >> > > I'm mostly guessing, but what I suspect that happens is that after you > successfully remove da0, the former da1 becomes da0 and any operations on > da1 (or da2 that now became da1) get aborted. > > That you just happen to have exactly identical USB sticks in this case > does not help diagnosing whether that's the case though. > > I'm really hoping this isn't actually what happens here, but it would > explain what you're seeing. > > No. That is not a valid explanation. This happens too if i change the order of the USB-Sticks and pull da2 or da1 instead of da0. The log snippet is exactly from the try and error of your thought. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 16:04:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D2713374; Thu, 8 Aug 2013 16:04:57 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA472F66; Thu, 8 Aug 2013 16:04:57 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id k18so5645651oag.12 for ; Thu, 08 Aug 2013 09:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T7+JTUVSmReACVqhEDaDMRR8pexU04tlDDmKnjir7kU=; b=VAOgRKs1MyViYmA2vfMVqJjAKmnuPaqz5uKHQGC31Oi0aacAMJQMxbW733GziyQ4Zm +5kEfxh2T9zCYwuyubUUOoQcVsQSza8lurw7015nWBfrqUL9/86E0x13meCNPMn9guso D4ekvSBOuaTIhDZM3hQF7TOwve3Fu1fv+bcrhmUgolQrb5mfc5NCYoE3ZC+9EFiRFmEu VzVogsSp62cAT6YC8sw2mkkk+ijvLDh2CcDMRtUWFAy7mKu8fy/THvz0URaN6tqmWEyM qAXodnKAh1MVAfj8XstRuiFl29ScVekqByML29w6C4VdrMT7kUXKdKttJ0GHQ7S+5c9K ojJg== MIME-Version: 1.0 X-Received: by 10.182.204.72 with SMTP id kw8mr5655317obc.54.1375977896878; Thu, 08 Aug 2013 09:04:56 -0700 (PDT) Received: by 10.76.35.67 with HTTP; Thu, 8 Aug 2013 09:04:56 -0700 (PDT) In-Reply-To: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> Date: Thu, 8 Aug 2013 19:04:56 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 16:04:58 -0000 On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder wrote: > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > Anybody? > > > > Can you provide your jail configuration? I think 9.2 introduces the new > /etc/jail.conf functionality and perhaps it somehow it broke the way you > were doing it previously? If so, the old method is supposed to be work > as well... > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > jail_enable="YES" jail_list="jail1" jail_jail1_rootdir="/tank/jails/jail1" jail_jail1_hostname="jail1" jail_jail1_interface="em0" jail_jail1_ip="172.16.154.32" jail_jail1_devfs_enable="YES" Do you see anything wrong here? Thanks -- George Kontostanos --- http://www.aisecure.net From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 16:11:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D96D7E0; Thu, 8 Aug 2013 16:11:54 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE2FD2070; Thu, 8 Aug 2013 16:11:53 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id up14so5366365obb.11 for ; Thu, 08 Aug 2013 09:11:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pn/IZNIoInHbvaexkxgkRskp0aMA69ze414qE/K7Cbk=; b=JYE7YMGS4ocE/Mdk6OCywLNOKzuxH+8V4ct67hRD+Cv0G1S2jLqCkYUx5YJRNV1XzK YeXgttl4xixHR8+FOuJ2iB0BiCwqM1f/UfG5GkOzH6OGcamgB/boeA4jXNIMz6qQoWNh mma4V9eWwY7vQE3ZWT5y7k1tTOo11VuWfLCEvDAQm5FLd2YwLyf/BWwxBYbwN+Pkvf0S 41+GMpRtXZgt8kf1/FMAUHoyKdMJv4nyC7hPDPM1Lyt9kd08D7O0jTJzi17qFFRYwEIj fzpErZEeX86yU00OaTucRoH/U9AW7bQjo2B2ZOSGpGIFtgORmyLiV7mMJC1EDJeg0i11 eg6Q== MIME-Version: 1.0 X-Received: by 10.182.215.133 with SMTP id oi5mr6819865obc.83.1375978313088; Thu, 08 Aug 2013 09:11:53 -0700 (PDT) Received: by 10.76.35.67 with HTTP; Thu, 8 Aug 2013 09:11:53 -0700 (PDT) In-Reply-To: <520397E0.1090209@freebsd.org> References: <1375963526.32115.7488635.39B9BAB2@webmail.messagingengine.com> <520397E0.1090209@freebsd.org> Date: Thu, 8 Aug 2013 19:11:53 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: Matthew Seaman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 16:11:54 -0000 On Thu, Aug 8, 2013 at 4:06 PM, Matthew Seaman wrote: > On 08/08/2013 13:05, Mark Felder wrote: > > On Thu, Aug 8, 2013, at 6:59, Trond Endrest=F8l wrote: > >> > >> I'm just guessing, but I doubt a jail would be able to create new ZFS > >> filesystems outside its own structure, if at all able. A jail would > >> however be allowed to (un)mount already existing filesystems within > >> its own structure, i.e. Pool/test1. > >> > > > > When I first reviewed his post I clearly confused "mounting" with > > "creating a new zfs filesystem". Is that even supposed to be permitted > > in a jail? I almost feel a sysctl disabling that by default would be > > nice... DoS by zfs filesystem creation/deletion, anyone? > > There's a 'zfs jail' command and a 'jailed' property you can set on a > ZFS which I believes allow you to manage that ZFS from within the jail. > I think that extends to creating other ZFSes beneath that one (which > would inherit the 'jailed' property), BICBW. > > Mostly I find it easier to just manage the ZFSes from the host system > but then again, I'm not really making very extensive use of jails. > > Cheers, > > Matthew > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Yes, it is easier to manage ZFS datasets from the host system but in this case we are assigning a different jail to each customer. That jail should be able to receive snapshots. It was working fine so far with 9.1. --=20 George Kontostanos --- http://www.aisecure.net From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 16:14:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B9CDEA26; Thu, 8 Aug 2013 16:14:02 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F43720C3; Thu, 8 Aug 2013 16:14:02 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id r78GE1FX003356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 8 Aug 2013 11:14:01 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.135]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Thu, 8 Aug 2013 11:14:00 -0500 From: "Teske, Devin" To: George Kontostanos Subject: Re: ZFS in jails 9.2-RC1 permission denied Thread-Topic: ZFS in jails 9.2-RC1 permission denied Thread-Index: AQHOk4rbXkfWuZRtskmo4tPc7BjGoZmLiI0AgAABnACAAESfAIAAAoeA Date: Thu, 8 Aug 2013 16:14:00 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720200B052@ltcfiswmsgmb21> References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="us-ascii" Content-ID: <21700F7E88675D408FC580A83CA04802@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-08_06:2013-08-08,2013-08-08,1970-01-01 signatures=0 Cc: Devin Teske , freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 16:14:02 -0000 On Aug 8, 2013, at 9:04 AM, George Kontostanos wrote: > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder wrote: >=20 >> On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: >>>=20 >>> Anybody? >>>=20 >>=20 >> Can you provide your jail configuration? I think 9.2 introduces the new >> /etc/jail.conf functionality and perhaps it somehow it broke the way you >> were doing it previously? If so, the old method is supposed to be work >> as well... >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>=20 >=20 > jail_enable=3D"YES" > jail_list=3D"jail1" > jail_jail1_rootdir=3D"/tank/jails/jail1" > jail_jail1_hostname=3D"jail1" > jail_jail1_interface=3D"em0" > jail_jail1_ip=3D"172.16.154.32" > jail_jail1_devfs_enable=3D"YES" >=20 > Do you see anything wrong here? >=20 Nope... though possible optimization... jail_jail1_ip=3D"em0|172.16.154.32" # no need for jail_jail1_interface --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 16:45:12 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CED84A58; Thu, 8 Aug 2013 16:45:12 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5CF6E239F; Thu, 8 Aug 2013 16:45:12 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r78Gj8G9002026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 18:45:08 +0200 (CEST) (envelope-from freebsd@omnilan.de) Message-ID: <5203CB14.5070306@omnilan.de> Date: Thu, 08 Aug 2013 18:45:08 +0200 From: "freebsd@omnilan.de" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Glen Barber Subject: Re: Some missing patches in 9.2-RC1 [Was: Re: Some missong patches in 9.2-RC2] References: <520283A1.1070404@omnilan.de> <20130808145045.GA17282@glenbarber.us> In-Reply-To: <20130808145045.GA17282@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 16:45:12 -0000 Bezüglich Glen Barber's Nachricht vom 08.08.2013 16:50 (localtime): ... >> - Regarding kerberized builds: >> http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043902.html > I'll take a look at this, but I do not see this change even committed to > head/ yet. Thank you for your attention! >> - Regarding mfi and >2TB corruption, seems MFC reminder failed >> http://www.freebsd.org/cgi/query-pr.cgi?pr=173291 > Closed: Mon Dec 10 06:34:48 UTC 2012 I saw that, but couldn't find the code... Because r**** 242681 changed it again... So the fix for the problem was changed and the original patch is outdated! Sorry for the noise... >> - Regarding mount failok (seems r230226 got lost?) >> http://www.freebsd.org/cgi/query-pr.cgi?pr=163668&cat=conf > Closed-Date: Mon Jun 11 18:25:59 UTC 2012 > http://www.freebsd.org/cgi/query-pr.cgi?pr=163668&cat=conf#reply6 Please see for example mount.c from head: http://svnweb.freebsd.org/base/head/sbin/mount/mount.c?revision=253372&view=markup In line 552 you find new code from r230226, the first patch in PR163668, commited on 2012/01/16 Now when I look into RELENG_9_2: http://svnweb.freebsd.org/base/releng/9.2/sbin/mount/mount.c?revision=253912&view=markup There's no sign of the above mentioned patch. Just the later followups from that PR got MFCd. Can't imagine that the first patch is only needed in head and not in stable. But maybe I'm missing something? Thanks, -Harry From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 17:12:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9424D4FD; Thu, 8 Aug 2013 17:12:20 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F4F225CC; Thu, 8 Aug 2013 17:12:19 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r78HCG4M002383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 19:12:16 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <5203D16A.3030308@omnilan.de> Date: Thu, 08 Aug 2013 19:12:10 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Glen Barber Subject: MFC vm_page.c and vm_phys.c missing [Was: Re: Some missing patches in 9.2-RC1] References: <520283A1.1070404@omnilan.de> <20130808145045.GA17282@glenbarber.us> <5203CB14.5070306@omnilan.de> In-Reply-To: <5203CB14.5070306@omnilan.de> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD61FCCAEF0B98B1AD46C74F9" Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 17:12:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD61FCCAEF0B98B1AD46C74F9 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable ... Can someone please have a look why this wasn't MFCd? http://svnweb.freebsd.org/base?view=3Drevision&revision=3D252653 Thanks, -Harry --------------enigD61FCCAEF0B98B1AD46C74F9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlID0XAACgkQLDqVQ9VXb8h9YQCg0A2qCSt5MUmdwepK4CaVm3Q9 eYMAniRvLCTTdEZy/nUjrK1BDaFjvWta =UYVH -----END PGP SIGNATURE----- --------------enigD61FCCAEF0B98B1AD46C74F9-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 18:23:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 505F3EE1; Thu, 8 Aug 2013 18:23:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3l.mail.yandex.net (forward3l.mail.yandex.net [IPv6:2a02:6b8:0:1819::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0AF782A33; Thu, 8 Aug 2013 18:23:42 +0000 (UTC) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17]) by forward3l.mail.yandex.net (Yandex) with ESMTP id 708561501492; Thu, 8 Aug 2013 22:23:39 +0400 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id ED59919000ED; Thu, 8 Aug 2013 22:23:38 +0400 (MSK) Received: from v10-164-213.yandex.net (v10-164-213.yandex.net [84.201.164.213]) by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTP id hpQPP4jqv6-NcUidYpV; Thu, 8 Aug 2013 22:23:38 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1375986218; bh=o7kzUyqXjgqRJY0vFhErc3QdGr5xbiTBJdsrG3hq6i8=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=Unlx1srno7clgmm+WaaoJmkjh/q0XreNhEvPCYFrazzVPidfQGEyI75y777sQIP4H JMAuQzx14x+a/eqgRa0mXIyLRLuSYE4tqUim5FDj4T3tuF8wf7tbKRwSa4F2SpuK+y +IbBsDYnGw2eNH2+R002fnH8qJFixOzVC2AKmMwE= Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5203E153.4070605@yandex.ru> Date: Thu, 08 Aug 2013 22:20:03 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Peter Wemm Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> <5202006B.5060708@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: J David , freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 18:23:42 -0000 On 08.08.2013 01:46, Peter Wemm wrote: > I've run into this before. Our loader and kernel are excessively > pedantic about this. > > gpart create -s gpt -n ... > > leads to bootblocks or loader or kernel rejecting it if it is < 128, > and some of the bootblocks reject it if it is > 128. > > As things stand, the -n option is basically "make my system unusable". The minimum number of GPT partitions that gpart(8) can create is 128. It seems it's not fully correct now. The spec only requires that at least 16k must be reserved for GPT table, but this doesn't mean that all 16kbytes should be used, also gpt table entry can be greater than 128 bytes in future. gptboot uses static buffer to load GPT, and its size is 16k. So, if you create GPT with more than 128 entries, it won't boot. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 05:55:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2DD9754D; Fri, 9 Aug 2013 05:55:28 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A9C582F25; Fri, 9 Aug 2013 05:55:27 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r795tNo0063861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 07:55:23 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r795tM9x063858; Fri, 9 Aug 2013 07:55:23 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 9 Aug 2013 07:55:22 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: George Kontostanos Subject: Re: ZFS in jails 9.2-RC1 permission denied In-Reply-To: Message-ID: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-1952888083-1376027723=:90799" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 05:55:28 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-1952888083-1376027723=:90799 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder wrote: > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > Anybody? > > > > > > > Can you provide your jail configuration? I think 9.2 introduces the new > > /etc/jail.conf functionality and perhaps it somehow it broke the way you > > were doing it previously? If so, the old method is supposed to be work > > as well... > > jail_enable="YES" > jail_list="jail1" > jail_jail1_rootdir="/tank/jails/jail1" > jail_jail1_hostname="jail1" > jail_jail1_interface="em0" > jail_jail1_ip="172.16.154.32" > jail_jail1_devfs_enable="YES" During my experimentation yesterday, I had to add: jail_jail1_parameters="enforce_statfs=1 allow.mount=1 allow.mount.zfs=1" I wish there was a way of executing a command in the host environment _after_ the jail is created, but _before_ exec.start is run from within the jail environment, exec.prestart is run in the host environment before the jail is created and is of no use for attaching a ZFS dataset to a particular jail with the zfs jail command. Until this issue is resolved, I see no other way than manually attaching a ZFS dataset to a jail, and manually running the mount command from within the jail environment. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-1952888083-1376027723=:90799-- From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 06:34:15 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B1BB3E1D; Fri, 9 Aug 2013 06:34:15 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 611852109; Fri, 9 Aug 2013 06:34:15 +0000 (UTC) Received: by mail-vc0-f176.google.com with SMTP id ha11so786462vcb.35 for ; Thu, 08 Aug 2013 23:34:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=viNuCqkky/3mgOfOKU1h5cJlxEYP/NIaITacG8HXZ7A=; b=oUoQvTTFjztaTQ7/J3Sj7qsdYHl/jgWtzsWs6tG8caXsFoDxHdVW2miB01Exufp5re aKe0NnxbLHoG4Lj6I92OOWpo5fq7v2HbJu5QmEq4lycS166xu3wDXBin8y+9ReR5C5z6 95064cnossjNpWI3dkZG/nQS+Mbk3KaV8mjuI14gzPCvpTzc+nQKxFb18IlPduR8eg9W HZQPh4kxkzFiYb5D2sXp2FtazWXQeoUKJLCqBLpsJx/whaPv9kec5SXMV9NH2E8zuYpJ c+o4HaElHAYNVnZLcFw2U2P2x3k+SA5wURsob9zVSBA0nYcrU9RGAP5nOfnXrVdwTCuR VSqw== MIME-Version: 1.0 X-Received: by 10.220.76.69 with SMTP id b5mr5833805vck.85.1376030054494; Thu, 08 Aug 2013 23:34:14 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Thu, 8 Aug 2013 23:34:14 -0700 (PDT) In-Reply-To: References: <20130807160528.GC13555@minime.local> Date: Fri, 9 Aug 2013 10:34:14 +0400 Message-ID: Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: Gregory Shapiro Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 06:34:15 -0000 I agree with Mark Felder. 2013/8/8 Pavel Timofeev : > I tried to revert mentioned patch, i.e. applied this > > --- sendmail/conf.c.orig 2013-08-08 12:28:40.000000000 +0400 > +++ sendmail/conf.c 2013-08-08 12:31:17.000000000 +0400 > @@ -4294,12 +4294,7 @@ > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && > SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > int nmaps; > # if NETINET6 > -# ifndef SM_IPNODEBYNAME_FLAGS > - /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > -# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > -# endif /* SM_IPNODEBYNAME_FLAGS */ > - > - int flags = SM_IPNODEBYNAME_FLAGS; > + int flags = AI_DEFAULT|AI_ALL; > int err; > # endif /* NETINET6 */ > char *maptype[MAXMAPSTACK]; > > Sendmail started to work > > 2013/8/7 Gregory Shapiro : >>> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. >>> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS >>> you won't receive it. >>> But in same time email passes from FreeBSD 9.1-RELEASE which uses >>> Sendmail-8.14.5. >> >> The recent release made the following change: >> >> --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 >> +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 >> @@ -4726,7 +4726,12 @@ >> #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ >> int nmaps; >> # if NETINET6 >> - int flags = AI_DEFAULT|AI_ALL; >> +# ifndef SM_IPNODEBYNAME_FLAGS >> + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ >> +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG >> +# endif /* SM_IPNODEBYNAME_FLAGS */ >> + >> + int flags = SM_IPNODEBYNAME_FLAGS; >> int err; >> # endif /* NETINET6 */ >> char *maptype[MAXMAPSTACK]; >> >> Which is described in this release note: >> >> Drop support for IPv4-mapped IPv6 addresses to prevent the MTA >> from using a mapped address over a legitimate IPv6 address >> and to enforce the proper semantics over the IPv6 >> connection. Problem noted by Ulrich Sporlein. >> >> It looks like that SERVFAIL from Microsoft's DNS server is getting >> in the way of that. I can look at adding this exception to >> WorkAroundBrokenAAAA as a possibility for a future release. >> >> I'd also like to hear feedback on whether the above change (changing >> getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went >> too far and what the accepted norm is for getipnodebyname(). >> From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 08:34:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 958C0322 for ; Fri, 9 Aug 2013 08:34:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4BB892786 for ; Fri, 9 Aug 2013 08:34:21 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1V7i3Q-0009aG-NU for freebsd-stable@freebsd.org; Fri, 09 Aug 2013 11:28:12 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-stable@freebsd.org Subject: missing /boot/menusets.4th Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Aug 2013 11:28:12 +0300 From: Daniel Braniss Message-ID: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 08:34:21 -0000 as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th is not being installed, so boot failes! danny From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 09:56:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2CD58958 for ; Fri, 9 Aug 2013 09:56:57 +0000 (UTC) (envelope-from freebsd@lidstrom.eu) Received: from ch-smtp05.sth.basefarm.net (ch-smtp05.sth.basefarm.net [80.76.153.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AA9EE2B7E for ; Fri, 9 Aug 2013 09:56:56 +0000 (UTC) Received: from c83-251-34-31.bredband.comhem.se ([83.251.34.31]:61379 helo=zimbra01.henriklidstrom.se) by ch-smtp05.sth.basefarm.net with esmtp (Exim 4.80.1) (envelope-from ) id 1V7jPo-0007RC-Gc; Fri, 09 Aug 2013 11:55:26 +0200 Received: from localhost (localhost [127.0.0.1]) by zimbra01.henriklidstrom.se (Postfix) with ESMTP id DDABD122CFF; Fri, 9 Aug 2013 11:55:01 +0200 (CEST) Received: from zimbra01.henriklidstrom.se ([127.0.0.1]) by localhost (zimbra01.henriklidstrom.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id e4v34tNdbWiw; Fri, 9 Aug 2013 11:55:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra01.henriklidstrom.se (Postfix) with ESMTP id 66C70122D05; Fri, 9 Aug 2013 11:55:01 +0200 (CEST) X-Virus-Scanned: amavisd-new at zimbra01.henriklidstrom.se Received: from zimbra01.henriklidstrom.se ([127.0.0.1]) by localhost (zimbra01.henriklidstrom.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id m-nDvqyN7kAh; Fri, 9 Aug 2013 11:55:01 +0200 (CEST) Received: from [10.102.2.153] (mgt01.telecomputing.se [84.17.194.80]) by zimbra01.henriklidstrom.se (Postfix) with ESMTPSA id 3B785122CFF; Fri, 9 Aug 2013 11:55:01 +0200 (CEST) Message-ID: <5204BC75.9090705@lidstrom.eu> Date: Fri, 09 Aug 2013 11:55:01 +0200 From: =?ISO-8859-1?Q?Henrik_Lidstr=F6m?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 MIME-Version: 1.0 To: Daniel Braniss Subject: Re: missing /boot/menusets.4th References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 83.251.34.31 X-Scan-Result: No virus found in message 1V7jPo-0007RC-Gc. X-Scan-Signature: ch-smtp05.sth.basefarm.net 1V7jPo-0007RC-Gc 52410177e75347e037ce3b741488184c Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd@lidstrom.eu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 09:56:57 -0000 On 08/09/13 10:28, Daniel Braniss wrote: > as of now (sorry have no rev#) the file > sys/boot/forth/menusets.4th > is not being installed, so boot failes! > > danny > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Yep, I just recovered from it using fixit and copying the file from src to /boot. FreeBSD 149999HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22 CEST 2013 root@149999HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 /Henrik From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 10:35:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A55426A; Fri, 9 Aug 2013 10:35:04 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0B5732D57; Fri, 9 Aug 2013 10:35:04 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id lf1so1964807pab.10 for ; Fri, 09 Aug 2013 03:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4X1OFaR28OvkOHlIMyGdMb93Wpsqk/k3UhVv7KCSIwQ=; b=MtpjhVdRQMHSUwzFMnjlYg+PVOloTW6MmRDF/m7SD6UtUBxK14n+qLHaBhrIp86HSh H4pwGpPXbNliNFPqwy+R653RBuRFA4LROqGBIH1BCgUrGKw6kOx9vH5tbyY2LgOC5pcQ MtdTF1yBYphPpyfpcinTwMuq2XLbztgj8OzkT7pUghw8vznUwnjsRPzZl6s6995V94NL FVtdhwJDkXiaS7YOprd7tnGugt0H5u8ZKOm+lSkTAyWiNu4kUmRdnrKI5jrJc4HXIYnK 2p/5dDDioOovpREc9L35edoc69DhD3rBNrYa0T8awkL4JF0pwnxs0NWyUNeJkM+VAkg1 cQPA== MIME-Version: 1.0 X-Received: by 10.68.189.195 with SMTP id gk3mr10364065pbc.193.1376044503476; Fri, 09 Aug 2013 03:35:03 -0700 (PDT) Received: by 10.68.211.106 with HTTP; Fri, 9 Aug 2013 03:35:03 -0700 (PDT) In-Reply-To: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> Date: Fri, 9 Aug 2013 13:35:03 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 10:35:04 -0000 On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrest=F8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > > > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder wrote: > > > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > > > Anybody? > > > > > > > > > > Can you provide your jail configuration? I think 9.2 introduces the n= ew > > > /etc/jail.conf functionality and perhaps it somehow it broke the way > you > > > were doing it previously? If so, the old method is supposed to be wor= k > > > as well... > > > > jail_enable=3D"YES" > > jail_list=3D"jail1" > > jail_jail1_rootdir=3D"/tank/jails/jail1" > > jail_jail1_hostname=3D"jail1" > > jail_jail1_interface=3D"em0" > > jail_jail1_ip=3D"172.16.154.32" > > jail_jail1_devfs_enable=3D"YES" > > During my experimentation yesterday, I had to add: > > jail_jail1_parameters=3D"enforce_statfs=3D1 allow.mount=3D1 allow.mount.z= fs=3D1" > > I wish there was a way of executing a command in the host environment > _after_ the jail is created, but _before_ exec.start is run from > within the jail environment, exec.prestart is run in the host > environment before the jail is created and is of no use for attaching > a ZFS dataset to a particular jail with the zfs jail command. > > Until this issue is resolved, I see no other way than manually > attaching a ZFS dataset to a jail, and manually running the mount > command from within the jail environment. > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=F8l, | Trond Endrest=F8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=F8vik Technical College, Norway, | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > Excellent, this worked like a charm! Does this means that the sysctl parameters are not honored or they have to be also passed in the jail parameters? Thanks! --=20 George Kontostanos --- http://www.aisecure.net From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 10:57:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 126BAA0A; Fri, 9 Aug 2013 10:57:45 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A62312FB1; Fri, 9 Aug 2013 10:57:44 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r79AvdST065941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 12:57:39 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r79AvdDU065938; Fri, 9 Aug 2013 12:57:39 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 9 Aug 2013 12:57:38 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: George Kontostanos Subject: Re: ZFS in jails 9.2-RC1 permission denied In-Reply-To: Message-ID: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-2124911918-1376045859=:90799" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 10:57:45 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-2124911918-1376045859=:90799 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: > On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl < > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > > > > > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder wrote: > > > > > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > > > > > Anybody? > > > > > > > > > > > > > Can you provide your jail configuration? I think 9.2 introduces the new > > > > /etc/jail.conf functionality and perhaps it somehow it broke the way > > you > > > > were doing it previously? If so, the old method is supposed to be work > > > > as well... > > > > > > jail_enable="YES" > > > jail_list="jail1" > > > jail_jail1_rootdir="/tank/jails/jail1" > > > jail_jail1_hostname="jail1" > > > jail_jail1_interface="em0" > > > jail_jail1_ip="172.16.154.32" > > > jail_jail1_devfs_enable="YES" > > > > During my experimentation yesterday, I had to add: > > > > jail_jail1_parameters="enforce_statfs=1 allow.mount=1 allow.mount.zfs=1" > > > > I wish there was a way of executing a command in the host environment > > _after_ the jail is created, but _before_ exec.start is run from > > within the jail environment, exec.prestart is run in the host > > environment before the jail is created and is of no use for attaching > > a ZFS dataset to a particular jail with the zfs jail command. > > > > Until this issue is resolved, I see no other way than manually > > attaching a ZFS dataset to a jail, and manually running the mount > > command from within the jail environment. > > Excellent, this worked like a charm! > > Does this means that the sysctl parameters are not honored or they have to > be also passed in the jail parameters? I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to propagate to the jail environments at all in 9.2-BETA2. > Thanks! You're welcome, and thanks for pushing me to explore jails and ZFS even further. ;-) Maybe the jail people should erect exec.afterprestart, enabling us to attach ZFS datasets to our jails prior to launching the jails. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-2124911918-1376045859=:90799-- From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 11:07:25 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F088DDD4; Fri, 9 Aug 2013 11:07:25 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C0D3D20D0; Fri, 9 Aug 2013 11:07:25 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id x10so420064pdj.29 for ; Fri, 09 Aug 2013 04:07:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VZuYbM1fe2YFByBog524ajrRLSrvP0xkDz4O0esvQHE=; b=XEEbNpb6OxpybQjrb89v/9w5mUlaOhXLZ/pflw8/3cObjf5slPE07Md5B+3IB4ExuX +BvgCBbT2qA8G2+ELbPibAzQ1dwbG0QPiY8xnh3FsStB6GmTQw7SII59ZdwM1Q4stfgY JfX/t6pomDOsxccKjxE5avuKQauZ6G32sd9tXgnPuU83h+5aA5wmkubWTIFXPIjy3ZvA igAbSgL7mqzaTM8XrQ7g/FaWbm/aa7DLI0aJUWD1/ttgH7EaAjo4a8ZkwgZhUZ8ssaLQ Y3U8IHb6/z+xLLvXdu8d7KC6xHjS25L9xijByIvO0xu1LEPU8CWhYDI4YPC0v8h8BYDp VF6Q== MIME-Version: 1.0 X-Received: by 10.68.189.195 with SMTP id gk3mr10482686pbc.193.1376046445156; Fri, 09 Aug 2013 04:07:25 -0700 (PDT) Received: by 10.68.211.106 with HTTP; Fri, 9 Aug 2013 04:07:25 -0700 (PDT) In-Reply-To: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> Date: Fri, 9 Aug 2013 14:07:25 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 11:07:26 -0000 On Fri, Aug 9, 2013 at 1:57 PM, Trond Endrest=F8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: > > > On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrest=F8l < > > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > > > On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > > > > > > > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder > wrote: > > > > > > > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > > > > > > > Anybody? > > > > > > > > > > > > > > > > Can you provide your jail configuration? I think 9.2 introduces > the new > > > > > /etc/jail.conf functionality and perhaps it somehow it broke the > way > > > you > > > > > were doing it previously? If so, the old method is supposed to be > work > > > > > as well... > > > > > > > > jail_enable=3D"YES" > > > > jail_list=3D"jail1" > > > > jail_jail1_rootdir=3D"/tank/jails/jail1" > > > > jail_jail1_hostname=3D"jail1" > > > > jail_jail1_interface=3D"em0" > > > > jail_jail1_ip=3D"172.16.154.32" > > > > jail_jail1_devfs_enable=3D"YES" > > > > > > During my experimentation yesterday, I had to add: > > > > > > jail_jail1_parameters=3D"enforce_statfs=3D1 allow.mount=3D1 > allow.mount.zfs=3D1" > > > > > > I wish there was a way of executing a command in the host environment > > > _after_ the jail is created, but _before_ exec.start is run from > > > within the jail environment, exec.prestart is run in the host > > > environment before the jail is created and is of no use for attaching > > > a ZFS dataset to a particular jail with the zfs jail command. > > > > > > Until this issue is resolved, I see no other way than manually > > > attaching a ZFS dataset to a jail, and manually running the mount > > > command from within the jail environment. > > > > Excellent, this worked like a charm! > > > > Does this means that the sysctl parameters are not honored or they have > to > > be also passed in the jail parameters? > > I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to > propagate to the jail environments at all in 9.2-BETA2. > > > Thanks! > > You're welcome, and thanks for pushing me to explore jails and ZFS > even further. ;-) > > Maybe the jail people should erect exec.afterprestart, enabling us to > attach ZFS datasets to our jails prior to launching the jails. > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=F8l, | Trond Endrest=F8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=F8vik Technical College, Norway, | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > I think that the process of attaching a dataset or a pool to a jail has to be done after the JID has been created. The way I attach them is from the host system: #zfs jail pool/dataset Best --=20 George Kontostanos --- http://www.aisecure.net From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 11:22:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5E2D71B2; Fri, 9 Aug 2013 11:22:38 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9498E219A; Fri, 9 Aug 2013 11:22:37 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r79BMWXO066121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 13:22:32 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r79BMWhE066118; Fri, 9 Aug 2013 13:22:32 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 9 Aug 2013 13:22:32 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: George Kontostanos Subject: Re: ZFS in jails 9.2-RC1 permission denied In-Reply-To: Message-ID: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-628144725-1376047352=:90799" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 11:22:38 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-628144725-1376047352=:90799 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Fri, 9 Aug 2013 14:07+0300, George Kontostanos wrote: > On Fri, Aug 9, 2013 at 1:57 PM, Trond Endrestøl < > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: > > > > > On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl < > > > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > > > > > On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > > > > > > > > > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder > > wrote: > > > > > > > > > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > > > > > > > > > Anybody? > > > > > > > > > > > > > > > > > > > Can you provide your jail configuration? I think 9.2 introduces > > the new > > > > > > /etc/jail.conf functionality and perhaps it somehow it broke the > > way > > > > you > > > > > > were doing it previously? If so, the old method is supposed to be > > work > > > > > > as well... > > > > > > > > > > jail_enable="YES" > > > > > jail_list="jail1" > > > > > jail_jail1_rootdir="/tank/jails/jail1" > > > > > jail_jail1_hostname="jail1" > > > > > jail_jail1_interface="em0" > > > > > jail_jail1_ip="172.16.154.32" > > > > > jail_jail1_devfs_enable="YES" > > > > > > > > During my experimentation yesterday, I had to add: > > > > > > > > jail_jail1_parameters="enforce_statfs=1 allow.mount=1 > > allow.mount.zfs=1" > > > > > > > > I wish there was a way of executing a command in the host environment > > > > _after_ the jail is created, but _before_ exec.start is run from > > > > within the jail environment, exec.prestart is run in the host > > > > environment before the jail is created and is of no use for attaching > > > > a ZFS dataset to a particular jail with the zfs jail command. > > > > > > > > Until this issue is resolved, I see no other way than manually > > > > attaching a ZFS dataset to a jail, and manually running the mount > > > > command from within the jail environment. > > > > > > Excellent, this worked like a charm! > > > > > > Does this means that the sysctl parameters are not honored or they have > > to > > > be also passed in the jail parameters? > > > > I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to > > propagate to the jail environments at all in 9.2-BETA2. > > > > > Thanks! > > > > You're welcome, and thanks for pushing me to explore jails and ZFS > > even further. ;-) > > > > Maybe the jail people should erect exec.afterprestart, enabling us to > > attach ZFS datasets to our jails prior to launching the jails. > > I think that the process of attaching a dataset or a pool to a jail has to > be done after the JID has been created. The way I attach them is from the > host system: > > #zfs jail pool/dataset That's why I propose the exec.afterprestart. This is how I imagine it should work: 1. The operator attempts to create a jail: jail -c somejail 2. The exec.prestart is run within the _host_ environment. It is of no concern regarding attaching ZFS datasets to our jail. 3. The jail is actually created, say, with /jails/somejail (zjails/jails/somejail) as it root. 4. The exec.afterprestart is run within the _host_ environment, and in our case is configured to attach some ZFS datasets, say: zfs jail somejail zjails/jaildata/somejail 5. The exec.start is run within the _jail_ environment, typically running /etc/rc. 6. /etc/fstab within the _jail_ environment contains the necessary information to mount zjails/jaildata/somejail as /jaildata. 7. Everything else remains unchanged. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-628144725-1376047352=:90799-- From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 12:13:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9A4EB389 for ; Fri, 9 Aug 2013 12:13:20 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 62A732429 for ; Fri, 9 Aug 2013 12:13:19 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r79C3xsb045568 for ; Fri, 9 Aug 2013 05:03:59 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r79C3x92045567 for freebsd-stable@freebsd.org; Fri, 9 Aug 2013 05:03:59 -0700 (PDT) (envelope-from david) Date: Fri, 9 Aug 2013 05:03:59 -0700 From: David Wolfskill To: freebsd-stable@freebsd.org Subject: Re: missing /boot/menusets.4th Message-ID: <20130809120359.GM1746@albert.catwhisker.org> References: <5204BC75.9090705@lidstrom.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Mqntr8YLmpnm4ZyH" Content-Disposition: inline In-Reply-To: <5204BC75.9090705@lidstrom.eu> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 12:13:20 -0000 --Mqntr8YLmpnm4ZyH Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 09, 2013 at 11:55:01AM +0200, Henrik Lidstr=F6m wrote: > On 08/09/13 10:28, Daniel Braniss wrote: > > as of now (sorry have no rev#) the file > > sys/boot/forth/menusets.4th > > is not being installed, so boot failes! > ... > Yep, I just recovered from it using fixit and copying the file from src= =20 > to /boot. >=20 > FreeBSD 149999HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22=20 > CEST 2013 root@149999HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 > ... I hit it as well; recovered by booting from one of my alternate boot slices & copying as above. Yesterday's stable/9: FreeBSD 9.2-BETA2 #521 r254090M/254091:902501: Thu Aug 8 04:34:52 PDT 201= 3 root@localhost:/usr/obj/usr/src/sys/CANARY i386 was OK. This morning's -- where I encountered the problem -- was: FreeBSD 9.2-BETA2 #522 r254136M/254137:902501: Fri Aug 9 04:34:36 PDT 201= 3 root@localhost:/usr/obj/usr/src/sys/CANARY i386 Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Mqntr8YLmpnm4ZyH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlIE2q4ACgkQmprOCmdXAD2P3wCbBnWE6+L1ZfS4uGfLz/Z10t9i FBwAnisjxW5Vmb6B8i47FJISpOTWVbdU =kEi7 -----END PGP SIGNATURE----- --Mqntr8YLmpnm4ZyH-- From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 14:12:14 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9DF8EED1; Fri, 9 Aug 2013 14:12:14 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6865A2A82; Fri, 9 Aug 2013 14:12:14 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa02.fnfis.com (8.14.5/8.14.5) with ESMTP id r79EBwZ4015626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 9 Aug 2013 09:11:58 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.135]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Fri, 9 Aug 2013 09:11:57 -0500 From: "Teske, Devin" To: "" Subject: [SOLVED] Re: missing /boot/menusets.4th Thread-Topic: [SOLVED] Re: missing /boot/menusets.4th Thread-Index: AQHOlNtIxSBVVLVSR0OrUtYsurGrUpmM9yKAgABHyYA= Date: Fri, 9 Aug 2013 14:11:57 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720200D19F@ltcfiswmsgmb21> References: <5204BC75.9090705@lidstrom.eu> In-Reply-To: <5204BC75.9090705@lidstrom.eu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <4A40EBCFE5DA654B8065A979A7EF8EBA@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-09_06:2013-08-09,2013-08-09,1970-01-01 signatures=0 Cc: Devin Teske , freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 14:12:14 -0000 On Aug 9, 2013, at 2:55 AM, Henrik Lidstr=F6m wrote: > On 08/09/13 10:28, Daniel Braniss wrote: >> as of now (sorry have no rev#) the file >> sys/boot/forth/menusets.4th >> is not being installed, so boot failes! >>=20 >> danny >>=20 >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >=20 > Yep, I just recovered from it using fixit and copying the file from src t= o /boot. >=20 > FreeBSD 149999HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22 CE= ST 2013 root@149999HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 >=20 (raises hand) My fault! I committed SVN r254109/r254113. ... and forgot to merge r242688. And I know why I missed it... Learned a valuable lessen today... *** I did my "mergeinfo --show-revs=3Deligible" in sys/boot/forth *** NOTE: Despite the fact that I did "svn merge" in the proper location, the "= show-revs" was influenced by the fact that I was in a sub-directory ... thu= s I never caught r242688 because at that sub-directory level, the revision = didn't apply (show-revs=3Deligible didn't list it; and that's the list I wa= s processing). It's not that I wasn't paying close attention to... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subver= sion-primer.html It's that I didn't know that the rule of getting the list of eligible revs = was quite as important as the actual act of merging. I'm very aware now tha= t when you go to synchronize branches... it's imperative that even the show= -revs step be done at the right level (but to be fair... I wasn't expecting= something like r242688 ... and it had been a _long_ time since I had last = broke the build [albeit with the same problem in HEAD]). Much apologies. Merging r242688 immediately to stable/9 to fix the missing file issue. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 14:19:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D9D234AE; Fri, 9 Aug 2013 14:19:43 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A47E32AEB; Fri, 9 Aug 2013 14:19:43 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r79EJUIN000750 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 9 Aug 2013 09:19:30 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.135]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Fri, 9 Aug 2013 09:19:29 -0500 From: "Teske, Devin" To: Devin Teske Subject: Re: [SOLVED] Re: missing /boot/menusets.4th Thread-Topic: [SOLVED] Re: missing /boot/menusets.4th Thread-Index: AQHOlNtIxSBVVLVSR0OrUtYsurGrUpmM9yKAgABHyYCAAAIaAA== Date: Fri, 9 Aug 2013 14:19:28 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720200D1EC@ltcfiswmsgmb21> References: <5204BC75.9090705@lidstrom.eu> <13CA24D6AB415D428143D44749F57D720200D19F@ltcfiswmsgmb21> In-Reply-To: <13CA24D6AB415D428143D44749F57D720200D19F@ltcfiswmsgmb21> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-09_06:2013-08-09,2013-08-09,1970-01-01 signatures=0 Cc: freebsd-stable stable , "freebsd@lidstrom.eu" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 14:19:43 -0000 On Aug 9, 2013, at 7:11 AM, Teske, Devin wrote: >=20 > On Aug 9, 2013, at 2:55 AM, Henrik Lidstr=F6m wrote: >=20 >> On 08/09/13 10:28, Daniel Braniss wrote: >>> as of now (sorry have no rev#) the file >>> sys/boot/forth/menusets.4th Again, apologies... Patched stable/9 with forgotten MFC of r242688 (see recent SVN r254146). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 17:29:11 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 53000ADE for ; Fri, 9 Aug 2013 17:29:11 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3BDE325A4 for ; Fri, 9 Aug 2013 17:29:11 +0000 (UTC) Received: from minime.local (natted.sendmail.com [63.211.143.38]) (authenticated bits=0) by zim.gshapiro.net (8.14.7/8.14.7) with ESMTP id r79HT7vh001954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 10:29:10 -0700 (PDT) (envelope-from gshapiro@freebsd.org) Date: Fri, 9 Aug 2013 10:29:15 -0700 From: Gregory Shapiro To: Pavel Timofeev Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network Message-ID: <20130809172915.GC17837@minime.local> References: <20130807160528.GC13555@minime.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 17:29:11 -0000 Can you put back the original sendmail/conf.c file and try this patch instead to verify it works? If so, I can plan to commit it to HEAD and MFC to the various branches (with re permission to the 9.2 branch). This would be a short term fix until the next sendmail release where we will revisit this section of code. --- contrib/sendmail/include/sm/os/sm_os_freebsd.h 2008-08-27 22:53:56.000000000 -0700 +++ contrib/sendmail/include/sm/os/sm_os_freebsd.h 2013-08-09 10:21:12.000000000 -0700 @@ -39,3 +39,7 @@ #ifndef SM_CONF_MSG # define SM_CONF_MSG 1 #endif /* SM_CONF_MSG */ + +#ifndef SM_IPNODEBYNAME_FLAGS +# define SM_IPNODEBYNAME_FLAGS AI_DEFAULT|AI_ALL +#endif /* SM_IPNODEBYNAME_FLAGS */ On Fri, Aug 09, 2013 at 10:34:14AM +0400, Pavel Timofeev wrote: > I agree with Mark Felder. > > 2013/8/8 Pavel Timofeev : > > I tried to revert mentioned patch, i.e. applied this > > > > --- sendmail/conf.c.orig 2013-08-08 12:28:40.000000000 +0400 > > +++ sendmail/conf.c 2013-08-08 12:31:17.000000000 +0400 > > @@ -4294,12 +4294,7 @@ > > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && > > SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > > int nmaps; > > # if NETINET6 > > -# ifndef SM_IPNODEBYNAME_FLAGS > > - /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > > -# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > > -# endif /* SM_IPNODEBYNAME_FLAGS */ > > - > > - int flags = SM_IPNODEBYNAME_FLAGS; > > + int flags = AI_DEFAULT|AI_ALL; > > int err; > > # endif /* NETINET6 */ > > char *maptype[MAXMAPSTACK]; > > > > Sendmail started to work > > > > 2013/8/7 Gregory Shapiro : > >>> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7. > >>> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS > >>> you won't receive it. > >>> But in same time email passes from FreeBSD 9.1-RELEASE which uses > >>> Sendmail-8.14.5. > >> > >> The recent release made the following change: > >> > >> --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 > >> +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 > >> @@ -4726,7 +4726,12 @@ > >> #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ > >> int nmaps; > >> # if NETINET6 > >> - int flags = AI_DEFAULT|AI_ALL; > >> +# ifndef SM_IPNODEBYNAME_FLAGS > >> + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ > >> +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG > >> +# endif /* SM_IPNODEBYNAME_FLAGS */ > >> + > >> + int flags = SM_IPNODEBYNAME_FLAGS; > >> int err; > >> # endif /* NETINET6 */ > >> char *maptype[MAXMAPSTACK]; > >> > >> Which is described in this release note: > >> > >> Drop support for IPv4-mapped IPv6 addresses to prevent the MTA > >> from using a mapped address over a legitimate IPv6 address > >> and to enforce the proper semantics over the IPv6 > >> connection. Problem noted by Ulrich Sporlein. > >> > >> It looks like that SERVFAIL from Microsoft's DNS server is getting > >> in the way of that. I can look at adding this exception to > >> WorkAroundBrokenAAAA as a possibility for a future release. > >> > >> I'd also like to hear feedback on whether the above change (changing > >> getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went > >> too far and what the accepted norm is for getipnodebyname(). > >> > From owner-freebsd-stable@FreeBSD.ORG Fri Aug 9 22:53:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8FC11143 for ; Fri, 9 Aug 2013 22:53:19 +0000 (UTC) (envelope-from SRS0=+P5fYwD8=RW=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from vulcan.beatsnet.com (vulcan.beatsnet.com [IPv6:2001:470:1f0b:102::bea1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20B98278E for ; Fri, 9 Aug 2013 22:53:18 +0000 (UTC) Received: from mbp-wl.beatsnet.com ([IPv6:2001:1620:f14:0:a54c:e4f6:bb76:dc19]) (authenticated bits=0) by vulcan.beatsnet.com (8.14.5/8.14.5) with ESMTP id r79Mr2Qb001953 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for ; Sat, 10 Aug 2013 00:53:12 +0200 (CEST) (envelope-from beat.siegenthaler@beatsnet.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=beatsnet.com; s=VULCAN_DKIM; t=1376088795; bh=lkxjzu+m6ZXBA18bOtG2y5waNfP3iTHWxrY5RByeJzc=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type; b=iXO6y4NnpeSQlWCNXmV0vb5+L5gMl5DPWoq6ZuU43QYgWtiL57611dDPZsic9dYZe AQ9BDT9i7Mmwi/Xu5SPvsbs8uWRgvpV0j/Q5nuy8JRp4J1nJ8mFQQtBHc88/T6lp/j NJPDWz9Kv/9vwJ1NjMytt5/ftsefkZU2/aH4Zh1g= Message-ID: <520572CD.5070501@beatsnet.com> Date: Sat, 10 Aug 2013 00:53:01 +0200 From: Beat Siegenthaler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: [SOLVED] Re: missing /boot/menusets.4th References: <5204BC75.9090705@lidstrom.eu> <13CA24D6AB415D428143D44749F57D720200D19F@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D720200D1EC@ltcfiswmsgmb21> In-Reply-To: <13CA24D6AB415D428143D44749F57D720200D1EC@ltcfiswmsgmb21> X-Enigmail-Version: 1.5.2 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (vulcan.beatsnet.com [IPv6:2001:470:1f0b:102::bea1]); Sat, 10 Aug 2013 00:53:12 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.97.7 at vulcan.beatsnet.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 22:53:19 -0000 On 09.08.13 16:19, Teske, Devin wrote: > Again, apologies... > > Patched stable/9 with forgotten MFC of r242688 (see recent SVN r254146). Accepted! that was the worst outage that hit me since a decade or more. It was really STABLE for longtime ;-) But In that stage of boot i was a bit helpless. Tried half a day to recover. Found some issues with "fixit" and mounting zfs on root in /mnt could not find menusets.4th on any place in the system. At the end I simply copied the file from http://svnweb.freebsd.org/base/head/sys/boot/forth/menusets.4th?revision=242667&view=co&pathrev=242667 on a usb-drive and copied to /mnt/boot Hope to help others. Now i have to figure out, why |Fixit# zpool import -R /mnt -f poolname| |Fixit# mount -t zfs poolname /mnt| did not worked as expected, and the 9.2-RC1 image was not installable... good night, Beat From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 06:33:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E999B73E; Sat, 10 Aug 2013 06:33:10 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A7432AED; Sat, 10 Aug 2013 06:33:10 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1V82jZ-000LjP-Ot; Sat, 10 Aug 2013 09:33:06 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: Devin Teske Subject: Re: [SOLVED] Re: missing /boot/menusets.4th In-reply-to: <13CA24D6AB415D428143D44749F57D720200D1EC@ltcfiswmsgmb21> References: <5204BC75.9090705@lidstrom.eu> <13CA24D6AB415D428143D44749F57D720200D19F@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D720200D1EC@ltcfiswmsgmb21> Comments: In-reply-to "Teske, Devin" message dated "Fri, 09 Aug 2013 14:19:28 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 10 Aug 2013 09:33:05 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-stable stable , "freebsd@lidstrom.eu" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 06:33:11 -0000 > > On Aug 9, 2013, at 7:11 AM, Teske, Devin wrote: > > > > > On Aug 9, 2013, at 2:55 AM, Henrik Lidstr=F6m wrote: > > > >> On 08/09/13 10:28, Daniel Braniss wrote: > >>> as of now (sorry have no rev=23) the file > >>> sys/boot/forth/menusets.4th > > Again, apologies... > > Patched stable/9 with forgotten MFC of r242688 (see recent SVN r25414= 6). > -- > Devin thanks, and not only for fixing it, but for the time you invest in the pr= oject=21 danny From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 12:31:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 10F2A74C for ; Sat, 10 Aug 2013 12:31:19 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A43D02977 for ; Sat, 10 Aug 2013 12:31:18 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so4222473wgh.31 for ; Sat, 10 Aug 2013 05:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LCpswCnPRU1TLbiksd7j5ujkK7UzfNncrzWV77Iwh94=; b=PpIENLMbbSUPf+kcXWedjkhNK1CjWgewLC5OGbjmbxBXF1UKOw0stEoEIOd/XcelSB wwhA2wxTtvV+w0+ev9YBhLg1Zytz7BcKPauOlgyHdigL87/ERARPQAVBtLHw0uOYlZf/ TRRyPtTzQquoNJH1VY3gCVZ3O7pIPRBUjjngn2a7mrX3O/MxLL5+MKUGFhDOaUheZEmQ QtSHaf1KkquzSM5FUwhdzYSFGuXFP5L+twh5ivHgSF+FFLB2tI2W0F46EVeEBccHBuGz 35D+2xKmz9vJik4VHG7pASRFzMiXwyqt5bNCd7jhKZEq79Pnpeu8PHWmpWwixgPHmdFK aypw== MIME-Version: 1.0 X-Received: by 10.180.188.132 with SMTP id ga4mr2460350wic.53.1376137877167; Sat, 10 Aug 2013 05:31:17 -0700 (PDT) Received: by 10.216.67.193 with HTTP; Sat, 10 Aug 2013 05:31:17 -0700 (PDT) Date: Sat, 10 Aug 2013 13:31:17 +0100 Message-ID: Subject: VTNET + pf + TSO performance From: krad To: freebsd-stable@freebsd.org, bane.ivosev@pmf.uns.ac.rs Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 12:31:19 -0000 Hi Was there any progress on the thread below? I have a freebsd guest ontop of solaris 11 exhibiting this problem. I'm on a pretty upto date stable kernel. The TSO fix works fine but i guess im taking a performance hit with it disabled FreeBSD carrera.snaffler.net 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254177: Sat Aug 10 11:08:17 BST 2013 root@carrera.snaffler.net:/usr/obj/usr/src/sys/me amd6 http://lists.freebsd.org/pipermail/freebsd-stable/2012-November/070413.html http://forums.freebsd.org/showthread.php?t=37814 From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 16:20:26 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7A8202B5; Sat, 10 Aug 2013 16:20:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 22D9F2429; Sat, 10 Aug 2013 16:20:26 +0000 (UTC) Received: by mail-ve0-f178.google.com with SMTP id ox1so4637858veb.23 for ; Sat, 10 Aug 2013 09:20:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=FYpKoXghmzNQYm2GMe6h8AhrBhoqpulWqt2ywo9rHzQ=; b=kWv7kU80H+lDjt0ADnMAX322E2jq9kfkQqDcJYMWQ5j0mKfEvpOHvkcTTfYVswRFDp p2LGxhx3D4grPVVuMxoZCKmh994v4HdKk+Y1RHUIEPqHY80n+Nhe1vFmmomIPO0Msu5s kr7aE15t9zPjwKvMAFnXZMRHcW0Qz7BYaHwLg8uHlS7XTGciGLJdgecuo0idvyU5r/ao IZhBQJ8iFNb9o6wFM5tcDkVLzTr6XvACPkgRq3cncP8edB/FpFMxHW5VtMIaxsMRnSHV YDn8GpXd7RWLCry5qwjRZ5qGoVX45WoA61QluP9rtL8PElCbLuBQxcF1645Y4YQ+wC06 ClnA== MIME-Version: 1.0 X-Received: by 10.58.118.8 with SMTP id ki8mr2937882veb.84.1376151625226; Sat, 10 Aug 2013 09:20:25 -0700 (PDT) Received: by 10.52.38.134 with HTTP; Sat, 10 Aug 2013 09:20:25 -0700 (PDT) In-Reply-To: <20130809172915.GC17837@minime.local> References: <20130807160528.GC13555@minime.local> <20130809172915.GC17837@minime.local> Date: Sat, 10 Aug 2013 20:20:25 +0400 Message-ID: Subject: Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network From: Pavel Timofeev To: Gregory Shapiro Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 16:20:26 -0000 Gregory's new patch for sm_os_freebsd.h worked. 2013/8/9 Gregory Shapiro : > Can you put back the original sendmail/conf.c file and try this patch ins= tead to verify it works? If so, I can plan to commit it to HEAD and MFC to= the various branches (with re permission to the 9.2 branch). This would b= e a short term fix until the next sendmail release where we will revisit th= is section of code. > > --- contrib/sendmail/include/sm/os/sm_os_freebsd.h 2008-08-27 22:53:= 56.000000000 -0700 > +++ contrib/sendmail/include/sm/os/sm_os_freebsd.h 2013-08-09 10:21:= 12.000000000 -0700 > @@ -39,3 +39,7 @@ > #ifndef SM_CONF_MSG > # define SM_CONF_MSG 1 > #endif /* SM_CONF_MSG */ > + > +#ifndef SM_IPNODEBYNAME_FLAGS > +# define SM_IPNODEBYNAME_FLAGS AI_DEFAULT|AI_ALL > +#endif /* SM_IPNODEBYNAME_FLAGS */ > > > > On Fri, Aug 09, 2013 at 10:34:14AM +0400, Pavel Timofeev wrote: >> I agree with Mark Felder. >> >> 2013/8/8 Pavel Timofeev : >> > I tried to revert mentioned patch, i.e. applied this >> > >> > --- sendmail/conf.c.orig 2013-08-08 12:28:40.000000000 +0400 >> > +++ sendmail/conf.c 2013-08-08 12:31:17.000000000 +0400 >> > @@ -4294,12 +4294,7 @@ >> > #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) && >> > SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ >> > int nmaps; >> > # if NETINET6 >> > -# ifndef SM_IPNODEBYNAME_FLAGS >> > - /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ >> > -# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG >> > -# endif /* SM_IPNODEBYNAME_FLAGS */ >> > - >> > - int flags =3D SM_IPNODEBYNAME_FLAGS; >> > + int flags =3D AI_DEFAULT|AI_ALL; >> > int err; >> > # endif /* NETINET6 */ >> > char *maptype[MAXMAPSTACK]; >> > >> > Sendmail started to work >> > >> > 2013/8/7 Gregory Shapiro : >> >>> I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail= -8.14.7. >> >>> If you try to send email from FreeBSD 9.2 in IPv4 network with MS DN= S >> >>> you won't receive it. >> >>> But in same time email passes from FreeBSD 9.1-RELEASE which uses >> >>> Sendmail-8.14.5. >> >> >> >> The recent release made the following change: >> >> >> >> --- sendmail/conf.c 25 Jan 2011 18:31:30 -0000 8.1168 >> >> +++ sendmail/conf.c 5 Apr 2013 17:39:09 -0000 8.1182 >> >> @@ -4726,7 +4726,12 @@ >> >> #else /* (SOLARIS > 10000 && SOLARIS < 20400) || (defined(SOLARIS) &= & SOLARIS < 204) || (defined(sony_news) && defined(__svr4)) */ >> >> int nmaps; >> >> # if NETINET6 >> >> - int flags =3D AI_DEFAULT|AI_ALL; >> >> +# ifndef SM_IPNODEBYNAME_FLAGS >> >> + /* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */ >> >> +# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG >> >> +# endif /* SM_IPNODEBYNAME_FLAGS */ >> >> + >> >> + int flags =3D SM_IPNODEBYNAME_FLAGS; >> >> int err; >> >> # endif /* NETINET6 */ >> >> char *maptype[MAXMAPSTACK]; >> >> >> >> Which is described in this release note: >> >> >> >> Drop support for IPv4-mapped IPv6 addresses to prevent the MT= A >> >> from using a mapped address over a legitimate IPv6 ad= dress >> >> and to enforce the proper semantics over the IPv6 >> >> connection. Problem noted by Ulrich Sporlein. >> >> >> >> It looks like that SERVFAIL from Microsoft's DNS server is getting >> >> in the way of that. I can look at adding this exception to >> >> WorkAroundBrokenAAAA as a possibility for a future release. >> >> >> >> I'd also like to hear feedback on whether the above change (changing >> >> getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG'= went >> >> too far and what the accepted norm is for getipnodebyname(). >> >> >> From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 17:18:28 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0EE65B0E for ; Sat, 10 Aug 2013 17:18:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E764C2682 for ; Sat, 10 Aug 2013 17:18:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7AHIRO4051036 for ; Sat, 10 Aug 2013 17:18:27 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7AHIRtx051034 for stable@FreeBSD.org; Sat, 10 Aug 2013 17:18:27 GMT (envelope-from bdrewery) Received: (qmail 84696 invoked from network); 10 Aug 2013 12:18:25 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 10 Aug 2013 12:18:25 -0500 Message-ID: <520675D3.8020801@FreeBSD.org> Date: Sat, 10 Aug 2013 12:18:11 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Failure to build stable/9 (r253683) from head - WCHAR_MIN redefined X-Enigmail-Version: 1.5.2 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TwNNbtvV23k8BxjCwtSTx7CpaLSFBBtnH" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 17:18:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TwNNbtvV23k8BxjCwtSTx7CpaLSFBBtnH Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anyone else seeing this? > cc -O2 -pipe -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/includ= e -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include -I/zpou= driere/jails/exp-bdrewery/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_P= RIVATE -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contrib/gd= toa -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contrib/libc-= vis -DINET6 -I/usr/obj/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc -I/= zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPO= SIX_MISTAKE -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contr= ib/tzcode/stdtime -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/stdti= me -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/locale -DBROKEN_DES= -DPORTMAP -DDES_BUILTIN -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/lib= c/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=3Dgnu99 -fstack-protecto= r -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-= pointer-sign -c /zpoudriere/jails/exp-bdrewery/usr /src/lib/libc/gen/fnmatch.c -o fnmatch.o > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/g= en/fnmatch.c:66: > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/collate.h:41: > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/xlocale_private.h:38: > /usr/include/stdint.h:75:9: error: 'WCHAR_MIN' macro redefined [-Werror= ] > #define WCHAR_MIN __WCHAR_MIN > ^ > /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include/wchar.h:9= 2:9: note: previous definition is here > #define WCHAR_MIN __INT_MIN > ^ > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/g= en/fnmatch.c:66: > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/collate.h:41: > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/xlocale_private.h:38: > /usr/include/stdint.h:76:9: error: 'WCHAR_MAX' macro redefined [-Werror= ] > #define WCHAR_MAX __WCHAR_MAX > ^ > /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include/wchar.h:9= 3:9: note: previous definition is here > #define WCHAR_MAX __INT_MAX > ^ > 2 errors generated. > *** [fnmatch.o] Error code 1 > 1 error > *** [lib/libc__L] Error code 2 > 1 error > *** [libraries] Error code 2 > 1 error > *** [_libraries] Error code 2 > 1 error > *** [buildworld] Error code 2 > 1 error --=20 Regards, Bryan Drewery --TwNNbtvV23k8BxjCwtSTx7CpaLSFBBtnH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSBnXTAAoJEG54KsA8mwz5ECYP/3HHPxO16X8tkERoJHSMOt8D O0iag2FEQiqn+xVz0BFOy+TWYB35mXIizTCiDGrcby8uHELBFrbEhXnY5G+3sFfd aBBGL1+Dj7XsJhuJjiGW4/HFT68x5a5+LOuKSqaYBa52+Mv35YE7R7bQqAcoIYL3 YkHalpvs/1o/87kUoVflM32Lf4uZ5ldDRe1Mw8phbCApQh/K/Cbv1GAIiXaMrzfu D5rS//6L+lodViOoJ9uhW6Zh6CsJLlQXWwDolb3VseRQ9FxflEWLigYdPGOMybP4 SfJQHhuQd8oNG1j1QAQ35iQ/M8tOk6JxZ4xSczOTmUOnNZLecnIYJsrBzBTqNTtN 4IfyoYTkcEXat+6HkIEB89CSxxFjKyi+dqgdLkIIhBNdNmejtvVoN8/6ltvtjqb3 dFIqesCl6LQ22I9lKuV2hWTAkVTSVnUjPKc5nsJNSxZHAyu7CQ7mynKrfcxnxRbr t/f6IO1ld6dfFCUZPVvdyABYKCmPY79aHTP8sKNVAhnmk2DQeEfDjFqJRaMz5fSF k0/s9Plr9udIB84/Pwc1M6rLFYjec5CFl8TaPR2PwfORcNFvP41VtJP1QQj5zA2+ stLtb9wXAPCAOu3kAe2elM1zRZo33y1ES46t4WADYvnE2fparhmvhHXNwcrkkVQV bKbAFJ/cnFq7V9qcoOPx =pK6H -----END PGP SIGNATURE----- --TwNNbtvV23k8BxjCwtSTx7CpaLSFBBtnH-- From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 17:28:35 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 63E7FCF3; Sat, 10 Aug 2013 17:28:35 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 317A726F8; Sat, 10 Aug 2013 17:28:34 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r7AHSRN0056683; Sat, 10 Aug 2013 10:28:27 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r7AHSREX056682; Sat, 10 Aug 2013 10:28:27 -0700 (PDT) (envelope-from david) Date: Sat, 10 Aug 2013 10:28:27 -0700 From: David Wolfskill To: Bryan Drewery Subject: Re: Failure to build stable/9 (r253683) from head - WCHAR_MIN redefined Message-ID: <20130810172827.GD1746@albert.catwhisker.org> References: <520675D3.8020801@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vUOrpVjU9N5sOsWB" Content-Disposition: inline In-Reply-To: <520675D3.8020801@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 17:28:35 -0000 --vUOrpVjU9N5sOsWB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 10, 2013 at 12:18:11PM -0500, Bryan Drewery wrote: > Anyone else seeing this? >=20 > > cc -O2 -pipe -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/includ= e -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include -I/zpoudr= iere/jails/exp-bdrewery/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVA= TE -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contrib/gdtoa -I= /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contrib/libc-vis -DIN= ET6 -I/usr/obj/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc -I/zpoudriere= /jails/exp-bdrewery/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE = -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../contrib/tzcode/stdt= ime -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/stdtime -I/zpoudrier= e/jails/exp-bdrewery/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_B= UILTIN -I/zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/rpc -DYP -DNS_CACH= ING -DSYMBOL_VERSIONING -std=3Dgnu99 -fstack-protector -Wsystem-headers -We= rror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /zpoudri= ere/jails/exp-bdrewery/usr > /src/lib/libc/gen/fnmatch.c -o fnmatch.o > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/g= en/fnmatch.c:66: > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/collate.h:41: > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/xlocale_private.h:38: > > /usr/include/stdint.h:75:9: error: 'WCHAR_MIN' macro redefined [-Werror] > > #define WCHAR_MIN __WCHAR_MIN > > ^ > > /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include/wchar.h:9= 2:9: note: previous definition is here > > #define WCHAR_MIN __INT_MIN > > ^ > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/g= en/fnmatch.c:66: > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/collate.h:41: > > In file included from /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/l= ocale/xlocale_private.h:38: > > /usr/include/stdint.h:76:9: error: 'WCHAR_MAX' macro redefined [-Werror] > > #define WCHAR_MAX __WCHAR_MAX > > ^ > > /zpoudriere/jails/exp-bdrewery/usr/src/lib/libc/../../include/wchar.h:9= 3:9: note: previous definition is here > > #define WCHAR_MAX __INT_MAX > > ^ > > 2 errors generated. > > *** [fnmatch.o] Error code 1 > ... I am not; my recent stable/9 history may be seen at -- but I build using clang (in case that is significant). Most recent was: FreeBSD localhost 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #523 r254170M/2541= 77:902501: Sat Aug 10 05:06:34 PDT 2013 root@localhost:/usr/obj/usr/src= /sys/CANARY i386 Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --vUOrpVjU9N5sOsWB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlIGeDIACgkQmprOCmdXAD1RegCfSPgm32cOkbVk3cV8alft03JY bQcAnR7GD6FexiNvra4NBEBN9kKziNiU =h99c -----END PGP SIGNATURE----- --vUOrpVjU9N5sOsWB-- From owner-freebsd-stable@FreeBSD.ORG Sat Aug 10 20:07:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 51548833; Sat, 10 Aug 2013 20:07:34 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1D2F12E0F; Sat, 10 Aug 2013 20:07:34 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id q10so1831843pdj.7 for ; Sat, 10 Aug 2013 13:07:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FGnGDQ6eAYe5pq+817FTrgKGpYC3c4cVbpgS0UpWdHo=; b=r/dWlpE47BBFQf7NHPlosaF+hiEPGKbBDWbT1SL5W51KS1+fR3uFYRZ3dCi3C16BaD TslRXvKbENc4G/9KBzJXasQQxCdaAbsk2sIftG6Ub1BBfIcsCJxBzw9shYkaqGm54qul 0XrAMz65oXGmaHajhBAhE2E8656FPoJBZaq4gfVXcID6PTyVu9KSlof/scaePu2WA1hB ncY/Ls64LFSFGHZ1BWbRR1rzrVt9owc9Bq/Pl8XOBlL1ZPqrj8FgaQmy/BL9Q9LLuyOH CfLtwFGQCKLM5IBr+0urymmDXMXYSYyVwHHmZ+THUKllYdA75Vr+qxZ1AQD8rlGVmoXy dyKg== MIME-Version: 1.0 X-Received: by 10.66.246.225 with SMTP id xz1mr6604531pac.110.1376165253603; Sat, 10 Aug 2013 13:07:33 -0700 (PDT) Received: by 10.68.211.106 with HTTP; Sat, 10 Aug 2013 13:07:33 -0700 (PDT) In-Reply-To: References: <1375963160.29686.7487435.7323F707@webmail.messagingengine.com> Date: Sat, 10 Aug 2013 23:07:33 +0300 Message-ID: Subject: Re: ZFS in jails 9.2-RC1 permission denied From: George Kontostanos To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 20:07:34 -0000 On Fri, Aug 9, 2013 at 2:22 PM, Trond Endrest=F8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Fri, 9 Aug 2013 14:07+0300, George Kontostanos wrote: > > > On Fri, Aug 9, 2013 at 1:57 PM, Trond Endrest=F8l < > > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > > > On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: > > > > > > > On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrest=F8l < > > > > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > > > > > > > On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: > > > > > > > > > > > On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder > > > wrote: > > > > > > > > > > > > > On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: > > > > > > > > > > > > > > > > Anybody? > > > > > > > > > > > > > > > > > > > > > > Can you provide your jail configuration? I think 9.2 introduc= es > > > the new > > > > > > > /etc/jail.conf functionality and perhaps it somehow it broke > the > > > way > > > > > you > > > > > > > were doing it previously? If so, the old method is supposed t= o > be > > > work > > > > > > > as well... > > > > > > > > > > > > jail_enable=3D"YES" > > > > > > jail_list=3D"jail1" > > > > > > jail_jail1_rootdir=3D"/tank/jails/jail1" > > > > > > jail_jail1_hostname=3D"jail1" > > > > > > jail_jail1_interface=3D"em0" > > > > > > jail_jail1_ip=3D"172.16.154.32" > > > > > > jail_jail1_devfs_enable=3D"YES" > > > > > > > > > > During my experimentation yesterday, I had to add: > > > > > > > > > > jail_jail1_parameters=3D"enforce_statfs=3D1 allow.mount=3D1 > > > allow.mount.zfs=3D1" > > > > > > > > > > I wish there was a way of executing a command in the host > environment > > > > > _after_ the jail is created, but _before_ exec.start is run from > > > > > within the jail environment, exec.prestart is run in the host > > > > > environment before the jail is created and is of no use for > attaching > > > > > a ZFS dataset to a particular jail with the zfs jail command. > > > > > > > > > > Until this issue is resolved, I see no other way than manually > > > > > attaching a ZFS dataset to a jail, and manually running the mount > > > > > command from within the jail environment. > > > > > > > > Excellent, this worked like a charm! > > > > > > > > Does this means that the sysctl parameters are not honored or they > have > > > to > > > > be also passed in the jail parameters? > > > > > > I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to > > > propagate to the jail environments at all in 9.2-BETA2. > > > > > > > Thanks! > > > > > > You're welcome, and thanks for pushing me to explore jails and ZFS > > > even further. ;-) > > > > > > Maybe the jail people should erect exec.afterprestart, enabling us to > > > attach ZFS datasets to our jails prior to launching the jails. > > > > I think that the process of attaching a dataset or a pool to a jail has > to > > be done after the JID has been created. The way I attach them is from t= he > > host system: > > > > #zfs jail pool/dataset > > That's why I propose the exec.afterprestart. This is how I imagine it > should work: > > 1. The operator attempts to create a jail: jail -c somejail > > 2. The exec.prestart is run within the _host_ environment. It is of no > concern regarding attaching ZFS datasets to our jail. > > 3. The jail is actually created, say, with /jails/somejail > (zjails/jails/somejail) as it root. > > 4. The exec.afterprestart is run within the _host_ environment, and in > our case is configured to attach some ZFS datasets, say: > > zfs jail somejail zjails/jaildata/somejail > > 5. The exec.start is run within the _jail_ environment, typically > running /etc/rc. > > 6. /etc/fstab within the _jail_ environment contains the necessary > information to mount zjails/jaildata/somejail as /jaildata. > > 7. Everything else remains unchanged. > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=F8l, | Trond Endrest=F8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=F8vik Technical College, Norway, | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > Sounds very good! As a side note. I noticed that if I log into the jail and issue: zail1> zfs mount -a All datasets are available. --=20 George Kontostanos --- http://www.aisecure.net