From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 07:26:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF65D106564A for ; Sun, 26 Dec 2010 07:26:15 +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]) by mx1.freebsd.org (Postfix) with ESMTP id 9DED78FC16 for ; Sun, 26 Dec 2010 07:26:15 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1PWkzd-0006J0-OC for freebsd-stable@freebsd.org; Sun, 26 Dec 2010 09:26:13 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 2010 09:26:13 +0200 From: Daniel Braniss Message-ID: Subject: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 07:26:16 -0000 hi, this is still broken in 8.2-PRERELEASE, there seems to be a patch, but it's almost a year old. http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff danny From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 07:48:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97ADD1065670 for ; Sun, 26 Dec 2010 07:48:33 +0000 (UTC) (envelope-from dennylin93@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6A14B8FC14 for ; Sun, 26 Dec 2010 07:48:33 +0000 (UTC) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 1001) id B57D54B782A; Sun, 26 Dec 2010 15:31:56 +0800 (CST) Date: Sun, 26 Dec 2010 15:31:56 +0800 From: Denny Lin To: Daniel Braniss Message-ID: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 07:48:33 -0000 On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: > this is still broken in 8.2-PRERELEASE, there seems to be a patch, but > it's almost a year old. > http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff Setting snapdir to visible should fix this right away: # zfs set snapdir=visible tank/foo -- Denny Lin From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 09:05:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64419106564A for ; Sun, 26 Dec 2010 09:05:19 +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]) by mx1.freebsd.org (Postfix) with ESMTP id 163FA8FC12 for ; Sun, 26 Dec 2010 09:05:18 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1PWmXV-00085C-NK; Sun, 26 Dec 2010 11:05:17 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Denny Lin In-reply-to: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> Comments: In-reply-to Denny Lin message dated "Sun, 26 Dec 2010 15:31:56 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 2010 11:05:17 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 09:05:19 -0000 > On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: > > this is still broken in 8.2-PRERELEASE, there seems to be a patch, but > > it's almost a year old. > > http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff > > Setting snapdir to visible should fix this right away: > # zfs set snapdir=visible tank/foo > it did indeed! any reason why this should not be the default behaviour? thanks, danny From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 10:47:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9560106566C for ; Sun, 26 Dec 2010 10:47:49 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) by mx1.freebsd.org (Postfix) with ESMTP id 5F7E58FC12 for ; Sun, 26 Dec 2010 10:47:49 +0000 (UTC) Received: from [IPv6:2001:888:1029::226:bbff:fe1a:76b5] ([IPv6:2001:888:1029:0:226:bbff:fe1a:76b5]) (authenticated bits=0) by erg.verweg.com (8.14.4/8.14.4) with ESMTP id oBQAlgRk087122 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Sun, 26 Dec 2010 10:47:47 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host [IPv6:2001:888:1029:0:226:bbff:fe1a:76b5] claimed to be [IPv6:2001:888:1029::226:bbff:fe1a:76b5] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Ruben van Staveren In-Reply-To: Date: Sun, 26 Dec 2010 11:47:41 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <91EDEEE8-215F-438D-923E-12A75F7B2C88@verweg.com> References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> To: FreeBSD Stable X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]); Sun, 26 Dec 2010 10:47:47 +0000 (UTC) Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 10:47:49 -0000 On 26 Dec 2010, at 10:05, Daniel Braniss wrote: >> On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: >>> this is still broken in 8.2-PRERELEASE, there seems to be a patch, = but >>> it's almost a year old. >>> http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff >>=20 >> Setting snapdir to visible should fix this right away: >> # zfs set snapdir=3Dvisible tank/foo >>=20 > it did indeed! > any reason why this should not be the default behaviour? Personally, I want to have the snapshot, but not see the directory = otherwise so that it doesn't get scooped up by rsync et al inadvertently=20= >=20 > thanks, > danny Cheers, Ruben= From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 11:32:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32FBC1065693 for ; Sun, 26 Dec 2010 11:32:05 +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]) by mx1.freebsd.org (Postfix) with ESMTP id DE6818FC13 for ; Sun, 26 Dec 2010 11:32:04 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1PWopX-000A1z-5G; Sun, 26 Dec 2010 13:32:03 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Ruben van Staveren In-reply-to: <91EDEEE8-215F-438D-923E-12A75F7B2C88@verweg.com> References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> <91EDEEE8-215F-438D-923E-12A75F7B2C88@verweg.com> Comments: In-reply-to Ruben van Staveren message dated "Sun, 26 Dec 2010 11:47:41 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 26 Dec 2010 13:32:03 +0200 From: Daniel Braniss Message-ID: Cc: FreeBSD Stable Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 11:32:05 -0000 > > On 26 Dec 2010, at 10:05, Daniel Braniss wrote: > > >> On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: > >>> this is still broken in 8.2-PRERELEASE, there seems to be a patch, = =3Dbut > >>> it's almost a year old. > >>> http://people.freebsd.org/=7Ejh/patches/zfs-ctldir-vptocnp.diff > >>=20 > >> Setting snapdir to visible should fix this right away: > >> =23 zfs set snapdir=3Dvisible tank/foo > >>=20 > > it did indeed=21 > > any reason why this should not be the default behaviour? >=20 > Personally, I want to have the snapshot, but not see the directory othe= rwise so that > it doesn't get scooped up by rsync et al inadvertently I agree, so the point is that as usual, the solution fixes one problem by= =20 creating another one :-) so basically, the bug is still there, or is it a feature? ie: ls /h/.zfs/snapshot/20101225/ works cd /h/.zfs/snapshot/20101225/ works pwd pwd: .: No such file or directory btw, why use rsync if 'zfs send=7C zfs recv' work realy nice? cheers, danny From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 11:53:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 012071065673 for ; Sun, 26 Dec 2010 11:53:22 +0000 (UTC) (envelope-from dennylin93@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) by mx1.freebsd.org (Postfix) with ESMTP id C3D438FC0C for ; Sun, 26 Dec 2010 11:53:21 +0000 (UTC) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 1001) id 260754B782A; Sun, 26 Dec 2010 19:53:19 +0800 (CST) Date: Sun, 26 Dec 2010 19:53:19 +0800 From: Denny Lin To: Daniel Braniss Message-ID: <20101226115318.GB84868@mail.hs.ntnu.edu.tw> References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> <91EDEEE8-215F-438D-923E-12A75F7B2C88@verweg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Stable Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 11:53:22 -0000 On Sun, Dec 26, 2010 at 01:32:03PM +0200, Daniel Braniss wrote: > > > On 26 Dec 2010, at 10:05, Daniel Braniss wrote: > > > >> On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: > > >> Setting snapdir to visible should fix this right away: > > >> # zfs set snapdir=visible tank/foo > > >> > > > it did indeed! > > > any reason why this should not be the default behaviour? > > > > Personally, I want to have the snapshot, but not see the directory otherwise so that > > it doesn't get scooped up by rsync et al inadvertently > > btw, why use rsync if 'zfs send| zfs recv' work realy nice? If I wanted to rsync the contents of /path/to/foo/ to another computer, rsync would unintenionally pick up the contents of /path/to/foo/.zfs/, so it's best to have .zfs hidden most of the time. Other commands such as cp should also have this problem. -- Denny Lin From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 13:52:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45045106564A for ; Sun, 26 Dec 2010 13:52:32 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from eccles.ee.ryerson.ca (eccles.ee.ryerson.ca [141.117.1.2]) by mx1.freebsd.org (Postfix) with ESMTP id F3FCA8FC0C for ; Sun, 26 Dec 2010 13:52:31 +0000 (UTC) Received: from [10.0.1.3] (bas2-toronto09-1176132252.dsl.bell.ca [70.26.90.156]) (authenticated bits=0) by eccles.ee.ryerson.ca (8.14.4/8.14.4) with ESMTP id oBQDUcBL008350 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 26 Dec 2010 08:30:48 -0500 (EST) (envelope-from dmagda@ee.ryerson.ca) Message-Id: <9F1EF5B4-CC25-41C1-A389-F5102E48DBAD@ee.ryerson.ca> From: David Magda To: Daniel Braniss In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 26 Dec 2010 08:30:59 -0500 References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> <91EDEEE8-215F-438D-923E-12A75F7B2C88@verweg.com> X-Mailer: Apple Mail (2.936) Cc: FreeBSD Stable Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 13:52:32 -0000 On Dec 26, 2010, at 06:32, Daniel Braniss wrote: > btw, why use rsync if 'zfs send| zfs recv' work realy nice? You're assuming that both sides of the transmission are on ZFS, which is not always true. It may be that the FreeBSD/ZFS system is the "back up server" for a network of Linux machines, and so is the destination of the rsync job. It may be that the destination is Linux or AIX or HP-UX. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 26 23:23:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AF21106566B for ; Sun, 26 Dec 2010 23:23:39 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CCE088FC0A for ; Sun, 26 Dec 2010 23:23:38 +0000 (UTC) Received: by iwn39 with SMTP id 39so8340460iwn.13 for ; Sun, 26 Dec 2010 15:23:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=3zy3Wa2ew9dMNxPTtmAUY0jWc2InXG1LtcWFZ2FxoAo=; b=gusJ4JrcWwKQol13xbJYeIbF/9Su5WuSRAcS7RoIW8+l6PSBxATAuOfDT1UnzhYPre N0auwedcu+wMYfeIHvQrbQRVp25h5q1kzxEETPo18v3Dglk4Bz0L0bwNFA0zSir49ht1 +Lmkfzlf6xKHQQf6FTqXj4LK1da/cgc9soBz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Wvj+NKB9436vXVQVkYL5C3MEX8UbJyN3Fjd8Smn/7rw7Jtf8k6/MViexLo2TDIXP7o wEFXPb7Rda53oSNo1gpSR+ApquxpGmJ8GZ1KNS0OO4KUkXHA4v4P8POtin1nRMawew8v zET8MXVf7n7zpVtA0UpvEVE81+wetLUYJ9/rQ= MIME-Version: 1.0 Received: by 10.42.175.4 with SMTP id ay4mr11681108icb.394.1293404146465; Sun, 26 Dec 2010 14:55:46 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 14:55:46 -0800 (PST) Date: Mon, 27 Dec 2010 09:55:46 +1100 Message-ID: From: Jean-Yves Avenard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: New ZFSv28 patchset for 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2010 23:23:39 -0000 Hi there. I used stable-8-zfsv28-20101223-nopython.patch.xz from http://people.freebsd.org/~mm/patches/zfs/v28/ simply because it was the most recent at this location. Is this the one to use? Just asking cause the file server I installed it on has stopped responding this morning and doing a remote power cycle didn't work. So got to get to the office and see what went on :( Suspect a kernel panic of some kind Jean-Yves From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 00:15:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EDFF106564A for ; Mon, 27 Dec 2010 00:15:46 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5605E8FC12 for ; Mon, 27 Dec 2010 00:15:45 +0000 (UTC) Received: (qmail 87251 invoked by uid 0); 27 Dec 2010 00:15:45 -0000 Received: from smtp.bway.net (216.220.96.25) by xena.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Dec 2010 00:15:45 -0000 Received: (qmail 87241 invoked by uid 90); 27 Dec 2010 00:15:44 -0000 Received: from unknown (HELO ?10.3.2.41?) (spork@96.57.144.66) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Dec 2010 00:15:44 -0000 Date: Sun, 26 Dec 2010 19:15:42 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@hotlap.local To: Daniel Braniss In-Reply-To: Message-ID: References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> User-Agent: Alpine 2.00 (OSX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 00:15:46 -0000 On Sun, 26 Dec 2010, Daniel Braniss wrote: >> On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: >>> this is still broken in 8.2-PRERELEASE, there seems to be a patch, but >>> it's almost a year old. >>> http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff >> >> Setting snapdir to visible should fix this right away: >> # zfs set snapdir=visible tank/foo >> > it did indeed! > any reason why this should not be the default behaviour? Others mentioned "rsync" or "cp" (used recursively) might pick up these directories. These are good reasons, especially if you've got a few hundred snapshots, which would not be uncommon when using ZFS on a host that's doing disk-based backups. Other gotchas would be some of the periodic scripts - you don't want locate.updatedb traversing all that, or the setuid checks. Also I know I'm prone to sometimes doing a brute-force "find" which can also dip into those hundreds of snapshot dirs. In general, I think having the directories hidden is a good default. Wouldn't be opposed to having the "pwd" issue fixed though... Thanks, Charles > thanks, > 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" > From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 00:43:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 838A5106566B for ; Mon, 27 Dec 2010 00:43:19 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 509128FC19 for ; Mon, 27 Dec 2010 00:43:18 +0000 (UTC) Received: by iwn39 with SMTP id 39so8366232iwn.13 for ; Sun, 26 Dec 2010 16:43:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=plvQD9DNceaHK0ooSB2V8Ze51pZl3VuTMjYW8JCeuYA=; b=bDROX5/rwXj+hQ2kzJoD7WUTkb069ObBBQP8HMwtx8A/Kob/a/Mcgh9NuIt1xQCF5k dPkfFligG8SAJsbSPCGtqvZpXjJOeBF/ANAw+Y10KrY1WwtiSsJfeei8WOxkJtezoowT OSxFZCC8nuToHuPFBJKPEd3/R+yN+PhEt/JSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CFDwzEOnA5/GHVjUN9r3lVGgdk4FlxKncCmgeLXXzdnd6DOsVQKuZ3Gy4HVIEMzgPz zG0fIpmWhlN7+EA4l4rRwpel8o/n6NMr5/QG5ML/mUq6k1D8epBFsKJo47QAPMur1pgI 3maWxgo9RtzL0QX/pTlb6knrBzaRQsFcs1eko= MIME-Version: 1.0 Received: by 10.42.175.4 with SMTP id ay4mr11749898icb.394.1293410598044; Sun, 26 Dec 2010 16:43:18 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 16:43:18 -0800 (PST) Date: Mon, 27 Dec 2010 11:43:18 +1100 Message-ID: From: Jean-Yves Avenard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 00:43:19 -0000 On 27 December 2010 09:55, Jean-Yves Avenard wrote: > Hi there. > > I used stable-8-zfsv28-20101223-nopython.patch.xz from > http://people.freebsd.org/~mm/patches/zfs/v28/ I did the following: # zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good [root@server4 /pool/home/jeanyves_avenard]# zpool add pool log /dev/label/zil [root@server4 /pool/home/jeanyves_avenard]# zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 logs label/zil ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good: # zpool remove pool logs label/zil cannot remove logs: no such device in pool ^C Great... now nothing respond.. Rebooting the box, I can boot in single user mode. but doing zpool status give me: ZFS filesystem version 5 ZFS storage pool version 28 and it hangs there forever... What should I do :( ? From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 01:03:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74184106564A for ; Mon, 27 Dec 2010 01:03:25 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3E2BE8FC0A for ; Mon, 27 Dec 2010 01:03:24 +0000 (UTC) Received: by iwn39 with SMTP id 39so8372937iwn.13 for ; Sun, 26 Dec 2010 17:03:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=3KcE1Sc2LtbV3HeUf8Zw4owhJzSvhVLRxgcfBIGo8kk=; b=bfonZl6UZgaXbmUc3loD/AQ96QscIMP+uigROXhcS4ZzUqT/PGwbFQh454WoB6lyRB Ps5d0y2R3b3cODoZJeBM1wS5mpkmtAlvDq0jcRxATEyh/FY3VLJWYFFLHAIx0/r44cyA Pu0mwXagUlIHGY3Co5or4O+Qcmd/IjoDiwpnQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MfBCjns7mhqzTC2JjqHRcjXxIzYnJJp/Z89WtYCxX1/ybeYOmBXN/RT/KzYNqdNZzW rH7nZY+WUe311B6aIKX/Z3ejXqJPMbHjfWD8h0x04ps/kDaS5TE2PCl/k6VQ/uGzk32+ 0rTfafDZT+ir3YGYVxmp0rk0vNDOuKDQgqlFo= MIME-Version: 1.0 Received: by 10.42.229.8 with SMTP id jg8mr11769338icb.461.1293411804585; Sun, 26 Dec 2010 17:03:24 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 17:03:24 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Dec 2010 12:03:24 +1100 Message-ID: From: Jean-Yves Avenard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 01:03:25 -0000 Rebooting in single-user mode. zpool status pool or spool scrub pool hangs just the same ... and there's no disk activity either ... Will download a liveCD of OpenIndiana, hopefully it will show me what's wrong :( Jean-Yves From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 01:41:44 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E90D1065670 for ; Mon, 27 Dec 2010 01:41:44 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) by mx1.freebsd.org (Postfix) with ESMTP id B884C8FC0C for ; Mon, 27 Dec 2010 01:41:43 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.4/8.14.4) with ESMTP id oBR1ffgc070895; Sun, 26 Dec 2010 20:41:41 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.4/8.14.4/Submit) id oBR1ffno070894; Sun, 26 Dec 2010 20:41:41 -0500 (EST) (envelope-from wollman) Date: Sun, 26 Dec 2010 20:41:41 -0500 (EST) From: Garrett Wollman Message-Id: <201012270141.oBR1ffno070894@hergotha.csail.mit.edu> To: spork@bway.net In-Reply-To: References: <20101226073156.GA84868@mail.hs.ntnu.edu.tw> Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 26 Dec 2010 20:41:41 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hergotha.csail.mit.edu Cc: stable@freebsd.org Subject: Re: unable to pwd in ZFS snapshot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 01:41:44 -0000 In article , spork@bway.net writes: >Other gotchas would be some of the periodic scripts - you don't want >locate.updatedb traversing all that, or the setuid checks. locate.updatedb in 9-current doesn't do that, by default. Arguably you want the setuid checks to do it, so that you're aware of setuid executables that are buried in old snapshots -- particularly if you keep old snapshots of /usr around after a security update. >Also I know I'm prone to sometimes doing a brute-force "find" which >can also dip into those hundreds of snapshot dirs. In general, I >think having the directories hidden is a good default. I could see the logic in having find not descend into .zfs directories by default (if done in a sufficiently general way), although then you'd have to introduce a new flag "yes, really, look at everything!" for cases when that's not desirable. -GAWollman From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 02:28:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C914F106566C for ; Mon, 27 Dec 2010 02:28:11 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9654B8FC18 for ; Mon, 27 Dec 2010 02:28:11 +0000 (UTC) Received: by iyb26 with SMTP id 26so7390269iyb.13 for ; Sun, 26 Dec 2010 18:28:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=ksCqJfbp+nr3msDJbHkBkDM6WAFYVbVOCu4rjh3xSrI=; b=pgDQhkgLwM+Zo4pm1PgN18R9YOdODB0/Hq4CGOEQST3ZSXntuErNcvgrV9QKUm76/G LP4ISBc75HrRHWC0ij0QyPRkrLtyO62KbS+sBbJNFiHl0zaOwVWKyLJ1wNFRIH8iyLqP gcaVB2A9coRickQLFxZ9a1OecmD3ZWlxcBigE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=h+kvCzlOzdz2QV1T+CRgsUSlmxYPLxSibGCkf70ob2+wbrbl5dn9pC0ZFOWkAvZMZr wbQYymZUneoXLWPhaUalpSYuQ4wqaTo90gaazubnnWnGZeqILwOMP/pTBbYNTqHYPnMS olfrk8bgdHK/6gSgQSZcBJNoVS5Gr8HmqCJUU= MIME-Version: 1.0 Received: by 10.42.178.9 with SMTP id bk9mr11891789icb.126.1293416890956; Sun, 26 Dec 2010 18:28:10 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 18:28:10 -0800 (PST) Date: Mon, 27 Dec 2010 13:28:10 +1100 Message-ID: From: Jean-Yves Avenard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 02:28:11 -0000 tried to force a zpool import got a kernel panic: panic: solaris assert: weight >= space && weight <= 2 * space, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c, line: 793 cpuid = 5 KDB: stack backtrace #0: 0xffffffffff805f64be at kdb_backtrace #1 .. panic+0x187 #2 .. metaslab_weight+0xe1 #3: metaslab_sync_done+0x21e #4: vdev_sync_done #5: spa_sync+0x6a2 #6 txg_sync_thread+0x147 #7: fork_exit+0x118 #8: fork_trampoline+0xe uptime 2m25s.. sorry for not writing down all the RAM addressed in the backtrace ... Starting to smell very poorly :( From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 04:17:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03319106564A for ; Mon, 27 Dec 2010 04:17:53 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id BDADC8FC08 for ; Mon, 27 Dec 2010 04:17:52 +0000 (UTC) Received: by iwn39 with SMTP id 39so8445199iwn.13 for ; Sun, 26 Dec 2010 20:17:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=SGgP6tsNyF8cfAeEgMU2aV+MTDSETHnWgBsYxZVNYgE=; b=J4dMAh1Rv7rPLwI8LWXqoX5VaN1L5GA+wPItqYYbkw+lwQCZ1L1JRYpzzVmOdQvrzM WLeWG/UJpWmrm6Q7U+Aok2GjwgXL6Z3fm9lSCLRhi63iVzJ2F1bGlQyzp3pIP1S/f+Cg ObWvx5pGfd6R7qy4MXloxR5JU+ncSY3OMWSqQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=EBagB9O1nzzdFRhjNnDJP8CdUW9bcS4sKECq4TsPK4PP5bKgvlWk7yT0Tma8/80qrs piZekGiW8gg+/ujSf3MqyWtKuZidbWyVhLQANViG0lyhSCZUxuFoHYf2EPCMNPFJ5ESM hwTecbnEItau5cR1rcp6untAc/k+7iiXrG84M= MIME-Version: 1.0 Received: by 10.42.164.131 with SMTP id g3mr2235351icy.193.1293423471988; Sun, 26 Dec 2010 20:17:51 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 20:17:51 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Dec 2010 15:17:51 +1100 Message-ID: From: Jean-Yves Avenard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 04:17:53 -0000 Responding to myself again :P On 27 December 2010 13:28, Jean-Yves Avenard wrote: > tried to force a zpool import > > got a kernel panic: > panic: solaris assert: weight >=3D space && weight <=3D 2 * space, file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs= /metaslab.c, > line: 793 > > cpuid =3D 5 > KDB: stack backtrace > #0: 0xffffffffff805f64be at kdb_backtrace > #1 .. =A0panic+0x187 > #2 .. metaslab_weight+0xe1 > #3: metaslab_sync_done+0x21e > #4: vdev_sync_done > #5: spa_sync+0x6a2 > #6 txg_sync_thread+0x147 > #7: fork_exit+0x118 > #8: fork_trampoline+0xe > > uptime 2m25s.. > Command used to import in FreeBSD was: zpool import -fF -R / pool which told me that zil was missing, and to use -m I booted openindiana (which is the only distribution I could ifnd with a live CD supporting zpool v28) Doing a zpool import actually made it show that the pool had successfully been repaired by the command above. It did think that the pool was in use (and it was, as I didn't do a zpool export). So I run zpool import -f pool in openindiana, and luckily, all my files were there. Not sure if anything was lost... in openindiana, I then ran zpool export and rebooted into FreeBSD. I ran zpool import there, and got the same original behaviour of a zpool import hanging, I can't sigbreak it nothing. Only left with the option of rebooting. Back into openindiana, tried to remove the log drive, but no luck. Always end up with the message: cannot remove log: no such device in pool Googling that error seems to be a common issue when trying to remove a ZIL but while that message is displayed, the log drive is actually removed. Not in my case.. So I tried something brave: In Open Indiana zpool export pool rebooted the PC, disconnected the SSD drive I had use and rebooted into openindiana ran zpool import -fF -R / pool (complained that log device was missing) and again zpool import -fF -m -R / pool zfs status showed that logs device being unavailable this time. ran zpool remove pool log hex_number_showing_in_place It showed the error "cannot remove log: no such device in pool" but zpool status showed that everything was allright zpool export pool , then reboot into FreeBSD zpool import this time didn't hang and successfully imported my pool. All data seems to be there. Summary: v28 is still buggy when it comes to removing the log device... And once something is screwed, zpool utility becomes hopeless as it hangs. So better have a OpenIndiana live CD to repair things :( But I won't be trying to remove the log device for a long time ! at least the data can be recovered when it happens.. Could it be that this is related to the v28 patch I used (http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101223-nop= ython.patch.xz and should have stuck to the standard one). Jean-Yves Breezing again ! From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 05:04:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD7531065670 for ; Mon, 27 Dec 2010 05:04:24 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8ECE08FC15 for ; Mon, 27 Dec 2010 05:04:24 +0000 (UTC) Received: by gwj21 with SMTP id 21so4786504gwj.13 for ; Sun, 26 Dec 2010 21:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=qa7ZgBxSDo34/wgKOnQ0pWZ05x4kgWr4w/NLTvqY8Po=; b=SoxPdy4lhL1q/EEJIoNOaffV9Y2rU+8LI9rQq+KM6pU5q+ic+3a9mNFrhFm+/o6mWm GKL80sQe+9R4IQa0YWhzQiHJKbcXJEIIkvgFZl69aA1+5p33CpMqg4F9RdPyFWT6phrw Fd0dJ3IvyGPtDGRtAMYi4YIIbDPVzEyugZxOY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=vLMIT3o+5jzAeAna0smnmf+GWXlvbnIq6lIWxp9fPJOIHqwTNd2ROuf8BkCz5bGrU5 qohH/HAaRoqcKePoxsa6e9J2wO6uM4hZNCY37Os1DEHYmFQM639WIX9Q+s0YQaPDeEcY 6FFlkGfxiZ17kStn8qzLtEWEDgU6nZyPbsmQo= Received: by 10.100.5.3 with SMTP id 3mr6862724ane.67.1293426261942; Sun, 26 Dec 2010 21:04:21 -0800 (PST) Received: from centel.dataix.local ([99.181.145.144]) by mx.google.com with ESMTPS id 17sm1444581anx.33.2010.12.26.21.04.19 (version=SSLv3 cipher=RC4-MD5); Sun, 26 Dec 2010 21:04:20 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D181E51.30401@DataIX.net> Date: Mon, 27 Dec 2010 00:04:17 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Jean-Yves Avenard References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 05:04:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/26/2010 23:17, Jean-Yves Avenard wrote: > Responding to myself again :P > > On 27 December 2010 13:28, Jean-Yves Avenard wrote: >> tried to force a zpool import >> >> got a kernel panic: >> panic: solaris assert: weight >= space && weight <= 2 * space, file: >> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c, >> line: 793 >> >> cpuid = 5 >> KDB: stack backtrace >> #0: 0xffffffffff805f64be at kdb_backtrace >> #1 .. panic+0x187 >> #2 .. metaslab_weight+0xe1 >> #3: metaslab_sync_done+0x21e >> #4: vdev_sync_done >> #5: spa_sync+0x6a2 >> #6 txg_sync_thread+0x147 >> #7: fork_exit+0x118 >> #8: fork_trampoline+0xe >> >> uptime 2m25s.. >> > > Command used to import in FreeBSD was: > zpool import -fF -R / pool > which told me that zil was missing, and to use -m > > I booted openindiana (which is the only distribution I could ifnd with > a live CD supporting zpool v28) > > Doing a zpool import actually made it show that the pool had > successfully been repaired by the command above. > It did think that the pool was in use (and it was, as I didn't do a > zpool export). > > So I run zpool import -f pool in openindiana, and luckily, all my > files were there. Not sure if anything was lost... > > in openindiana, I then ran zpool export and rebooted into FreeBSD. > > I ran zpool import there, and got the same original behaviour of a > zpool import hanging, I can't sigbreak it nothing. Only left with the > option of rebooting. > > Back into openindiana, tried to remove the log drive, but no luck. > Always end up with the message: > cannot remove log: no such device in pool > > Googling that error seems to be a common issue when trying to remove a > ZIL but while that message is displayed, the log drive is actually > removed. > Not in my case.. > > So I tried something brave: > In Open Indiana > zpool export pool > > rebooted the PC, disconnected the SSD drive I had use and rebooted > into openindiana > ran zpool import -fF -R / pool (complained that log device was > missing) and again zpool import -fF -m -R / pool > > zfs status showed that logs device being unavailable this time. > > ran zpool remove pool log hex_number_showing_in_place > > It showed the error "cannot remove log: no such device in pool" > but zpool status showed that everything was allright > > zpool export pool , then reboot into FreeBSD > > zpool import this time didn't hang and successfully imported my pool. > All data seems to be there. > > > Summary: v28 is still buggy when it comes to removing the log > device... And once something is screwed, zpool utility becomes > hopeless as it hangs. > > So better have a OpenIndiana live CD to repair things :( > > But I won't be trying to remove the log device for a long time ! at > least the data can be recovered when it happens.. > > Could it be that this is related to the v28 patch I used > (http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20101223-nopython.patch.xz > and should have stuck to the standard one). > Before anything else can you: (in FreeBSD) 1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1) 2) Boot into single user mode without opensolaris.ko and zfs.ko loaded 3) ( mount -w / ) to make sure you can remove and also write new zpool.cache as needed. 3) Remove /boot/zfs/zpool.cache 4) kldload both zfs and opensolaris i.e. ( kldload zfs ) should do the trick 5) verify that vfs.zfs.recover=1 is set then ( zpool import pool ) 6) Give it a little bit monitor activity using Ctrl+T to see activity. You should have your pool back to a working condition after this. The reason why oi_127 can't work with your pool is because it cannot see FreeBSD generic labels. The only way to work around this for oi_127 would be to either point it directly at the replacing device or to use actual slices or partitions for your slogs and other such devices. Use adaNsN or gpt or gptid for working with your pool if you plan on using other OS's for recovery effects. Regards, - -- jhell,v -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJNGB5QAAoJEJBXh4mJ2FR+rUAH/1HhzfnDI1jTICrA2Oiwyk12 BLXac0HoTY+NVUrdieMUWPh781oiB0eOuzjnOprev1D2uTqrmKvivnWdzuT/5Kfi vWSSnIqWiNbtvA5ocgWs7IPtcaD5pZS06oToihvLlsEiRyYXTSh2XD7JOsLbQMNb uKTfAvGI/XnNX0OY3RNI+OOa031GfpdHEWon8oi5aFBYdsDsv3Wn8Z45qCp8yfI+ WZlI+P+uunrmfgZdSzDbpAxeByhTB+8ntnB6QC4d0GRXKwqTVrFmIw5yuuqRAIf8 oCJYDhH6AUi+cxAGDExhLz2e75mEZNHAqB2nkxTaWbwL/rGjBnVidNm1aj7WnWw= =FlmB -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 05:30:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3F371065672 for ; Mon, 27 Dec 2010 05:30:31 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8AF908FC1A for ; Mon, 27 Dec 2010 05:30:31 +0000 (UTC) Received: by iyb26 with SMTP id 26so7460336iyb.13 for ; Sun, 26 Dec 2010 21:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=FCxnxyxCxjtm3xyKSZ1mPYeum0kk/SIPlddAJsrWYzI=; b=D2cO69Knhu+6dBanATTu4lDl0/g8aMxjIm5nDj3a2bX2MtLpzRm/iGT9UXexyW5VCt yqFZwivkPbxGWnNSVyAlve+cSy6FXcTD64U15shtJ7qpXTmXnY/qod8emEiTBsPCQ6OA sNwt+gSqZYVDczSgQ9shbuS82U3qda+MJCcgY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C5hrcvJ/CpasMcvT11HCiPU+kSy8BHs6J+IAL/5jrPE1RsaNSewEqaXKBePVu3HsQB ApZ2mhg12kiB3DDTkVeiaDi90KeWN9hI72PYOAZtrneA52Opf5RV2KyD1YAr1fBN/I3N aKlZdk3N2nMvwR7+VxN35HXcjaAAVYM2kxGYk= MIME-Version: 1.0 Received: by 10.42.164.131 with SMTP id g3mr2288271icy.193.1293427830630; Sun, 26 Dec 2010 21:30:30 -0800 (PST) Received: by 10.42.220.70 with HTTP; Sun, 26 Dec 2010 21:30:30 -0800 (PST) In-Reply-To: <4D181E51.30401@DataIX.net> References: <4D181E51.30401@DataIX.net> Date: Mon, 27 Dec 2010 16:30:30 +1100 Message-ID: From: Jean-Yves Avenard To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 05:30:31 -0000 Hi On 27 December 2010 16:04, jhell wrote: > > Before anything else can you: (in FreeBSD) > > 1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1) > 2) Boot into single user mode without opensolaris.ko and zfs.ko loaded > 3) ( mount -w / ) to make sure you can remove and also write new > zpool.cache as needed. > 3) Remove /boot/zfs/zpool.cache > 4) kldload both zfs and opensolaris i.e. ( kldload zfs ) should do the trick > 5) verify that vfs.zfs.recover=1 is set then ( zpool import pool ) > 6) Give it a little bit monitor activity using Ctrl+T to see activity. > > You should have your pool back to a working condition after this. The > reason why oi_127 can't work with your pool is because it cannot see > FreeBSD generic labels. The only way to work around this for oi_127 > would be to either point it directly at the replacing device or to use > actual slices or partitions for your slogs and other such devices. > > Use adaNsN or gpt or gptid for working with your pool if you plan on > using other OS's for recovery effects. > Hi.. Thank you for your response, I will keep it safely should it ever occur again. Let me explain why I used labels.. It all started when I was trying to solve some serious performance issue when running with zfs http://forums.freebsd.org/showthread.php?t=20476 One of the step in trying to trouble shoot the latency problem, was to use AHCI ; I had always thought that activating AHCI in the bios was sufficient to get it going on FreeBSD, turned out that was the case and that I needed to load ahci.ko as well. After doing so, my system wouldn't boot anymore as it was trying to be /dev/ad0 which didn't exist anymore and was now names /dev/ata0. So I used a label to the boot disk to ensure that I will never encounter that problem ever again. In the same mindset, I used labels for the cache and log device I later added to the pool... I have to say however, that zfs had no issue using the labels until I tried to remove it. I had rebooted several times without having any problems. zpool status never hanged It all started to play up when I ran the command: zpool remove pool log label/zil zpool never ever came out from running that command (I let it run for a good 30 minutes, during which I was fearing the worse, and once I rebooted and nothing ever worked, suicide looked like an appealing alternative) It is very disappointing however that because the pool is in a non-working state, none of the command available to troubleshoot the problem would actually work (which I'm guessing is related to zpool looking for a device name that it can never find being a label) I also can't explain why FreeBSD would kernel panic when it was finally in a state of being able to do an import. I have to say unfortunately, that if I hadn't had OpenIndiana, I would probably still by crying underneath my desk right now... Thanks again for your email, I have no doubt that this would have worked but in my situation, I got your answer in just 2 hours, which is better than any paid support could provide ! Jean-Yves PS: saving my 5MB files over the network , went from 40-55s with v15 to a constant 16s with v28... I can't test with ZIL completely disabled , it seems that vfs.zfs.zil_disable has been removed, and so did vfs.zfs.write_limit_override From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 05:37:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47405106564A for ; Mon, 27 Dec 2010 05:37:12 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailA.acsu.buffalo.edu (localmailA.acsu.buffalo.edu [128.205.5.196]) by mx1.freebsd.org (Postfix) with ESMTP id E96918FC0A for ; Mon, 27 Dec 2010 05:37:11 +0000 (UTC) Received: from localmailA.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 80D20B3E8 for ; Mon, 27 Dec 2010 00:36:48 -0500 (EST) Received: from localmailA.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailA.acsu.buffalo.edu (Postfix) with ESMTP id 7851AB39E for ; Mon, 27 Dec 2010 00:36:44 -0500 (EST) Received: from mweb1.acsu.buffalo.edu (mweb1.acsu.buffalo.edu [128.205.5.238]) by localmailA.acsu.buffalo.edu (Prefixe) with ESMTP id 72DEFB22E for ; Mon, 27 Dec 2010 00:36:44 -0500 (EST) Received: from [192.168.1.101] (cpe-76-180-182-44.buffalo.res.rr.com [76.180.182.44]) by mweb1.acsu.buffalo.edu (Postfix) with ESMTP id 1A5A95B003A for ; Mon, 27 Dec 2010 00:36:44 -0500 (EST) From: Ken Smith To: freebsd-stable Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-UQa+958BlpL7iZ/yfFrM" Organization: U. Buffalo Date: Mon, 27 Dec 2010 00:36:32 -0500 Message-ID: <1293428192.80821.12.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 FreeBSD GNOME Team Port X-PM-EL-Spam-Prob: XX: 28% Subject: FreeBSD 7.4/8.2-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 05:37:12 -0000 --=-UQa+958BlpL7iZ/yfFrM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The first Release Candidate for the FreeBSD 7.4/8.2 release cycle is now available. For 7.4-RC1 the amd64, i386, pc98, and sparc64 architectures are available, for 8.2-RC1 those architectures plus ia64 and powerpc are available. Files suitable for creating installation media or doing FTP based installs through the network are available on the FreeBSD mirror sites. Checksums for the images are at the bottom of this message. For this Release Candidate no packages (except for the doc package set for 8.2-RC1) have been provided in any of the images. Packages will be provided with the RC2 builds. The target schedule for the releases is available here: http://www.freebsd.org/releases/8.2R/schedule.html http://www.freebsd.org/releases/7.4R/schedule.html and the wiki pages tracking the current status of the releases are: http://wiki.freebsd.org/Releng/8.2TODO http://wiki.freebsd.org/Releng/7.4TODO If you find problems you can report them through the normal Gnats based PR system or here on the mailing list. If you are updating an already running machine the CVS branch tag for 8.2-RC1 is RELENG_8_2, for 7.4-RC1 it is RELENG_7_4. If you prefer SVN use "releng/8.2" or "releng/7.4". The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 8.0-RELEASE, 8.1-RELEASE, or 8.2-BETA1 can upgrade as follows: # freebsd-update upgrade -r 8.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, and the system needs to be rebooted again: # freebsd-update install # shutdown -r now Users of earlier FreeBSD releases (FreeBSD 7.x) can also use freebsd-update to upgrade to FreeBSD 8.2-RC1, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 7.x and FreeBSD 8.x. Substitute "7.4-RC1" for "8.2-BETA1" in the above instructions if you are targeting 7.4-RC1 instead. Checksums: MD5 (FreeBSD-7.4-RC1-amd64-bootonly.iso) =3D 66ba849bc5cabf70c35884997648d2= ea MD5 (FreeBSD-7.4-RC1-amd64-disc1.iso) =3D 837e6111be636e88ca6f0e65ad233f61 MD5 (FreeBSD-7.4-RC1-amd64-docs.iso) =3D a7213fee78282beb2be68bb99ce56281 MD5 (FreeBSD-7.4-RC1-amd64-dvd1.iso) =3D 6c1259c130348851d3b50f082244345d MD5 (FreeBSD-7.4-RC1-amd64-livefs.iso) =3D fb8f64c4a8c5a099cd59f8a771b30a78 MD5 (FreeBSD-7.4-RC1-i386-bootonly.iso) =3D d5bda0643626284ef70346bf9323dc6= 2 MD5 (FreeBSD-7.4-RC1-i386-disc1.iso) =3D 39e97306df9edc93d745e31ef46de2a8 MD5 (FreeBSD-7.4-RC1-i386-docs.iso) =3D 14c61e0928d97a8779df16eac1f4f3f1 MD5 (FreeBSD-7.4-RC1-i386-dvd1.iso) =3D dae529bcf6706bfa0921b60b8486e3f3 MD5 (FreeBSD-7.4-RC1-i386-livefs.iso) =3D 619fd06612590d7112019d81b0888fe9 MD5 (FreeBSD-7.4-RC1-pc98-bootonly.iso) =3D eebcc73f5ac917db887c3ff275eacd0= 8 MD5 (FreeBSD-7.4-RC1-pc98-disc1.iso) =3D 33e2c33a2113579cb841e566f19eb449 MD5 (FreeBSD-7.4-RC1-pc98-livefs.iso) =3D 4983bc250a03f176bd95daee400f99c9 MD5 (FreeBSD-7.4-RC1-sparc64-bootonly.iso) =3D 06f9bd78fbe4340a5fc9c0024fcc= ec18 MD5 (FreeBSD-7.4-RC1-sparc64-disc1.iso) =3D 8cf5cf22e6e824565b0830177d02570= f MD5 (FreeBSD-7.4-RC1-sparc64-docs.iso) =3D a3f7a75f4387736313fd7037f7c43332 MD5 (FreeBSD-8.2-RC1-amd64-bootonly.iso) =3D d93f48d9944b7dd2d01eb9a50412fc= f2 MD5 (FreeBSD-8.2-RC1-amd64-disc1.iso) =3D f87e00d05be66d0e8ac996ee11214520 MD5 (FreeBSD-8.2-RC1-amd64-dvd1.iso) =3D e5427cf598341a06dce22f5cf48ecb43 MD5 (FreeBSD-8.2-RC1-amd64-livefs.iso) =3D cb687f9f3a69b450449be2ad849fce08 MD5 (FreeBSD-8.2-RC1-amd64-memstick.img) =3D e2f61ebbfd2f6c83a1c19af6be0af5= 5a MD5 (FreeBSD-8.2-RC1-i386-bootonly.iso) =3D c4a3e8001fe3786b9eff2b42df6d434= 7 MD5 (FreeBSD-8.2-RC1-i386-disc1.iso) =3D c8d9608dc611132bb6b785de1929fddc MD5 (FreeBSD-8.2-RC1-i386-dvd1.iso) =3D 870c038a1620338b95c2405dcc7de04e MD5 (FreeBSD-8.2-RC1-i386-livefs.iso) =3D c209b01ae838627fd52c365bd0461144 MD5 (FreeBSD-8.2-RC1-i386-memstick.img) =3D 57c02f0295f32b73d5bb52a567381d3= f MD5 (FreeBSD-8.2-RC1-ia64-bootonly.iso) =3D 1e92e3dccecfab6dce27d6f982456d5= 3 MD5 (FreeBSD-8.2-RC1-ia64-disc1.iso) =3D 245af0a6c1dbb40a865f71195f5387ee MD5 (FreeBSD-8.2-RC1-ia64-disc2.iso) =3D c1c12a47a24693a50e0fd3b138acd11b MD5 (FreeBSD-8.2-RC1-ia64-disc3.iso) =3D 3b2e109bdd320f10faad1886a632cf85 MD5 (FreeBSD-8.2-RC1-ia64-dvd1.iso) =3D fa321deb35d5a7ddb349a5d20ecdcebd MD5 (FreeBSD-8.2-RC1-ia64-livefs.iso) =3D 30cc67deb6f021e52bb2150bf786d73a MD5 (FreeBSD-8.2-RC1-pc98-bootonly.iso) =3D f23ce4becc76c7fdda96b2394652f75= d MD5 (FreeBSD-8.2-RC1-pc98-disc1.iso) =3D 4e9b77ebd30efe23b9478ab85f1d5dfa MD5 (FreeBSD-8.2-RC1-pc98-livefs.iso) =3D 09de03e3a5ae967f1b1cc47c04504656 MD5 (FreeBSD-8.2-RC1-powerpc-bootonly.iso) =3D 03755a9b9e54a2ab0c2e3ca049cb= a4f0 MD5 (FreeBSD-8.2-RC1-powerpc-disc1.iso) =3D 3ba2685cd8d3a884e8926f1d181e1cb= b MD5 (FreeBSD-8.2-RC1-powerpc-disc2.iso) =3D 946d8a5dfc01cedd8d48e42d0a5a613= 3 MD5 (FreeBSD-8.2-RC1-powerpc-disc3.iso) =3D 175f021c4ae2f929773448b647082dc= e MD5 (FreeBSD-8.2-RC1-powerpc-livefs.iso) =3D a60ac35a5c0094c60cac581aca5fa8= d8 MD5 (FreeBSD-8.2-RC1-sparc64-bootonly.iso) =3D d0eaae380dd7820de25bc9593d28= 6c3d MD5 (FreeBSD-8.2-RC1-sparc64-disc1.iso) =3D 37ce5fa8a391f5489e095d2a27b7de4= b MD5 (FreeBSD-8.2-RC1-sparc64-dvd1.iso) =3D b3ace4817fb9ec6808b711a0e8823b4f MD5 (FreeBSD-8.2-RC1-sparc64-livefs.iso) =3D fa26fb7175eeccf3361cdaa1f325aa= 7f SHA256 (FreeBSD-7.4-RC1-amd64-bootonly.iso) =3D f86c7b05f9cb3876b3ec2f1744d= 1726af52a06ed002ec77bd5a85f59821be1ed SHA256 (FreeBSD-7.4-RC1-amd64-disc1.iso) =3D ed05bfad54bd9105a09acdd193df58= be41a4de27a7579f5b284adfb6c366cc32 SHA256 (FreeBSD-7.4-RC1-amd64-docs.iso) =3D a353aee3c50d34395b858d70fe4ea23= f35a84f223e9696afe704a392f6b3b0b0 SHA256 (FreeBSD-7.4-RC1-amd64-dvd1.iso) =3D 529dd65ac03fe68eff80fd54e293065= fe3018e0d2437aec311f961512d4a5219 SHA256 (FreeBSD-7.4-RC1-amd64-livefs.iso) =3D 89e47d9d7af5ff8d84dad0efaf49f= 5c4feb06f329120c176389d826df359ddd4 SHA256 (FreeBSD-7.4-RC1-i386-bootonly.iso) =3D 314201e80f783c83ce6f7b542804= 7ec463a30ead706dbcb02aca6a9a9bd3e03e SHA256 (FreeBSD-7.4-RC1-i386-disc1.iso) =3D 302ecd98f63b10f2ed05aed0aed69b2= aca16fc1fb773ccc6365ab9b732cee3d1 SHA256 (FreeBSD-7.4-RC1-i386-docs.iso) =3D 82aa177ca824b70bd24a9569df050b59= 9453b324319a865ffca3681326939a01 SHA256 (FreeBSD-7.4-RC1-i386-dvd1.iso) =3D 8ddc0489f9a45d29b5d07d17ce00a934= a0dfd243cac7ca2c0cebaf4d0ece513d SHA256 (FreeBSD-7.4-RC1-i386-livefs.iso) =3D 5564abf2b8fc5dd199af7b7dea7fee= b9e1b721ebdda9c09d0cadb80e9bf69ff4 SHA256 (FreeBSD-7.4-RC1-pc98-bootonly.iso) =3D 7133e827c4f52670cd215f82d752= 567f673c3983a02d75e2904083d99c57b6a0 SHA256 (FreeBSD-7.4-RC1-pc98-disc1.iso) =3D 75e818bac59780b34346450b9bd3361= 857d2e7d8170584904af815af9dbc1aad SHA256 (FreeBSD-7.4-RC1-pc98-livefs.iso) =3D a26e2b0cb06a4382b894c132859b64= 2e1970897d9d28deef050b985d1b594345 SHA256 (FreeBSD-7.4-RC1-sparc64-bootonly.iso) =3D 791759778a5f92fdd2ecf93d4= e3eba2aaad55a0e87ffd117940f147d0b66c8e8 SHA256 (FreeBSD-7.4-RC1-sparc64-disc1.iso) =3D 54b658034f6517164a32e3d3eea2= 920d7cdf4b4105affa1e7a35138581b04b51 SHA256 (FreeBSD-7.4-RC1-sparc64-docs.iso) =3D 0363991b428cf744a8bc854532ffe= 6e17af433349d1ba410509f48b22c9d6ff5 SHA256 (FreeBSD-8.2-RC1-amd64-bootonly.iso) =3D 68d71e5f9dc4457f146be504437= 32f0705c34f80043198f3adb874aafbd28d42 SHA256 (FreeBSD-8.2-RC1-amd64-disc1.iso) =3D ac740c14fdc0ea9b92223b32f271b4= f8163f8163f17f3ac9433517e114eb8d10 SHA256 (FreeBSD-8.2-RC1-amd64-dvd1.iso) =3D a8a321ef5590e4e9fd69e1b6e82f606= 6a3ab9bf1df292d602fa10c148e026101 SHA256 (FreeBSD-8.2-RC1-amd64-livefs.iso) =3D e6f6e6ddd2d85e70c83a15a6dcaf5= bc9005adadbf24d3b4a4a231a1d036b0115 SHA256 (FreeBSD-8.2-RC1-amd64-memstick.img) =3D ef91f49e6ad6cf46bd8ffd3cc14= 957dfed62112cc54f9e7231dfedd2f467f770 SHA256 (FreeBSD-8.2-RC1-i386-bootonly.iso) =3D c22e6764c14b5832a3e77ed62284= ac5efce160179bcd2ef3741376276b42850f SHA256 (FreeBSD-8.2-RC1-i386-disc1.iso) =3D 557a921978b5a19b3bec793e219c5f2= 6cba5fdb3e24abac7dd11fc6d42c270a0 SHA256 (FreeBSD-8.2-RC1-i386-dvd1.iso) =3D 2fe461d1147c3fd97c55e3adc55d8f6e= e95b8fe4918448224aef5f08982b044d SHA256 (FreeBSD-8.2-RC1-i386-livefs.iso) =3D e93a451a99f7a57fb68f916f0e1d7d= 088b632e1e224426076ab6ec975fd393b7 SHA256 (FreeBSD-8.2-RC1-i386-memstick.img) =3D 3c77a63743e2cf6f1d5ffc7afd4f= 90daad8467ecaab75fde586f9cb6fb446eed SHA256 (FreeBSD-8.2-RC1-ia64-bootonly.iso) =3D eaff4e6ede2c53555d88dce50f58= c95f89323ba9c78c3da2fa96723a516ceb19 SHA256 (FreeBSD-8.2-RC1-ia64-disc1.iso) =3D 7445fc931578c2611118233f6a4a0fe= 32f17bdbcfaa4de8440c7832a4621fde8 SHA256 (FreeBSD-8.2-RC1-ia64-disc2.iso) =3D b33e3f2d61a358f2100284d882acd48= b199efc51ccefe6641e3b7ed20aaa48ad SHA256 (FreeBSD-8.2-RC1-ia64-disc3.iso) =3D 9409c46719b0a241248e4f297f01212= ddd34e524e2a52e8fe8a0481b1a2ba948 SHA256 (FreeBSD-8.2-RC1-ia64-dvd1.iso) =3D a957d89e068899a707dd4240a89bc097= 205628fa4d794a78e8a8314635132ade SHA256 (FreeBSD-8.2-RC1-ia64-livefs.iso) =3D 425a508e7a5abfd565019e6688e44b= 0903d207e464a053a119bd98c9b42a6a35 SHA256 (FreeBSD-8.2-RC1-pc98-bootonly.iso) =3D 760c23fca0aa0dba5e29a5ba2f75= d43a07b92a11c6e97abbcd9bb782df30582e SHA256 (FreeBSD-8.2-RC1-pc98-disc1.iso) =3D ec36b8797a268efde963a78d9c72e05= 04fa08bbd562a0912d809fb35d29484d6 SHA256 (FreeBSD-8.2-RC1-pc98-livefs.iso) =3D 4cb5a50bd3dba3a2e369d8dcad4d51= 2039e610beee4f1a3ea175a88314dcc905 SHA256 (FreeBSD-8.2-RC1-powerpc-bootonly.iso) =3D 1949925baa779533dfae9c044= 748492a80a406fd6ca34a43199293973a6960cb SHA256 (FreeBSD-8.2-RC1-powerpc-disc1.iso) =3D ad12cb6501e9cefc9cb9652b2e6b= 6f04ff37a2e23fd3d2a42f45ff208fb29bd3 SHA256 (FreeBSD-8.2-RC1-powerpc-disc2.iso) =3D b9e329673be062ede79461c462a2= b9ac8edadfd2ccfc458c5794c333f2c9af78 SHA256 (FreeBSD-8.2-RC1-powerpc-disc3.iso) =3D 01b7c070a0e7f51e69fc86242010= d7c6f083d32b4bc1d30f6238379202fef367 SHA256 (FreeBSD-8.2-RC1-powerpc-livefs.iso) =3D 7a14c364a8d34f2202e1138a762= 5ec1862021e5b811d9d1314247e7accab26ab SHA256 (FreeBSD-8.2-RC1-sparc64-bootonly.iso) =3D 39570a25201795589b85dec35= afbf79c2e5dfc157c588c569eebf15eda2fe26c SHA256 (FreeBSD-8.2-RC1-sparc64-disc1.iso) =3D dc086f83ae0478e86252130fe739= 042f8600cb9bccf92864621295e46853eac4 SHA256 (FreeBSD-8.2-RC1-sparc64-dvd1.iso) =3D b56703f4269927ff038e6bbaf1fed= 71d61482a1985b47189590bc1e6dd2c0b21 SHA256 (FreeBSD-8.2-RC1-sparc64-livefs.iso) =3D 3b1e39867bdf6b54ab7e0b67f9a= 00b745ebcc06126ec2bbbbab40fc64a3f0fbe --=20 Ken Smith - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-UQa+958BlpL7iZ/yfFrM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAk0YJdkACgkQ/G14VSmup/ZQxACeLX5JbLZnRzfOFEthg0qSP745 OIgAn1fkv4jQDFD76P39ul7wdR2zHSdc =D7ZI -----END PGP SIGNATURE----- --=-UQa+958BlpL7iZ/yfFrM-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 15:01:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C57910656CD for ; Mon, 27 Dec 2010 15:01:16 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 44C6E8FC14 for ; Mon, 27 Dec 2010 15:01:15 +0000 (UTC) Received: by qwj9 with SMTP id 9so8202933qwj.13 for ; Mon, 27 Dec 2010 07:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XIx0JN9SSG2Roi2XSjsT7DiElqI5eWVY2fC90w7/kTg=; b=QXu3oWdBKe8yLoBljUR/Hj1jav6H6qATpKdz6v06laVvF4qJSu11MWRMExB1QKwfR0 pl5NXXgtLsmPQ/8go5uyyTPjZND6esy5Qxpqf003RaeDVIdkEiBmhH0qQUT5o9bn35Y5 MaUiN0nvgIJ7jALgx/gdoqzVdcjOfAKB3FZh4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hEtYADr4LosO00mmMNRi4k9DUCqQbWDye6fqjAkbuyKPwn97ANAUPe8sCbds8cHuXp 8VunHHTozftM738/IrhtRDC3f/cMJpvveBuM6I5wCAz32f2+6Fsz1j01WZR5089S1tlD 2hRMHeG5K7VI7XWkWUNnENNeSoncwVMIaLejw= MIME-Version: 1.0 Received: by 10.229.95.8 with SMTP id b8mr10364299qcn.156.1293460511915; Mon, 27 Dec 2010 06:35:11 -0800 (PST) Received: by 10.229.90.211 with HTTP; Mon, 27 Dec 2010 06:35:11 -0800 (PST) In-Reply-To: <4BFBAEF6.1000809@infracaninophile.co.uk> References: <20100524121856.GA26479@icarus.home.lan> <224129E1-5E90-4E36-A553-2F37C0CF0780@lassitu.de> <20100524122944.GA26720@icarus.home.lan> <0CFCBFC9-F613-4D16-9359-334ECED3E913@lassitu.de> <20100524131346.GA27811@icarus.home.lan> <2142CA1C-C914-4ED0-A72D-0A0161C739E3@lassitu.de> <9C8A5AA9-4460-4629-97C4-6EDE50745797@lassitu.de> <20100524150738.GA30549@icarus.home.lan> <20100524162400.GA31162@icarus.home.lan> <20100524174933.GA33820@icarus.home.lan> <7FF8139E-2A30-4AC3-A60F-E3B0E723F491@lassitu.de> <4BFBAEF6.1000809@infracaninophile.co.uk> Date: Mon, 27 Dec 2010 15:35:11 +0100 Message-ID: From: Christer Solskogen To: Matthew Seaman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable , Stefan Bethke , Jeremy Chadwick Subject: Re: make world fails in usr.sbin/config? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 15:01:16 -0000 On Tue, May 25, 2010 at 1:05 PM, Matthew Seaman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 25/05/2010 11:40:23, Stefan Bethke wrote: >> For the record: I'm now running -stable as of last night, compiled >> without issue on ZFS filesystems throughout. =A0No idea what caused the >> issue in the first place, and what made it disappear though, but >> updating to the correctly built -stable made the build on ZFS work >> again. =A0(It also involved an accidential upgrade and downgrade via >> -current, since I checked out the wrong tag with csup. =A0Yikes.) > > I've a new machine that's been running 8-STABLE on ZFS for about a week > now. =A0Had no problems installing and then upgrading to recent 8-STABLE > although I did start with installing an 8-STABLE snapshot rather than > 8.0-RELEASE. (See: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror) > > Verb. Sap. =A0If you're booting from ZFS, beware of updating the zpool > version without due care and attention. =A08.0-RELEASE was on version 13, > 8-STABLE is now on version 14. =A0(Use 'zpool update' to see what the > status is on your machine -- this just gives you a report, and doesn't > update anything.) =A0Updating the zpool version is pretty smooth and > simple, but *remember to immediately rebuild and reinstall gptzfsboot or > zfsboot bootcode on your drives*. =A0If you don't do that, your system > won't be able to find the pool with the root filesystem and so won't be > able to reboot. > > Old thread, I know. But I encountered this error today and my solution was that /tmp was tmpfs and it was full. Cleaning that up fixed the error. --=20 chs, From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 20:43:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4075106567A for ; Mon, 27 Dec 2010 20:43:45 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6E65C8FC17 for ; Mon, 27 Dec 2010 20:43:45 +0000 (UTC) Received: by qwj9 with SMTP id 9so8455230qwj.13 for ; Mon, 27 Dec 2010 12:43:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=JpnpAVyeQutA/N4c03Bdu5jZEyaJflNug812hVbVpKI=; b=S5ZxDG5FHNo+PORcnWr7Kr6y3moLGIpt21Vfeuc7Hvluom/4ryuuUYWA0HaC7xeN/A phqJH9QsJnnTfHJ1FnYY9BH/Xv+qy1GiuZcPo/o0PLFd+tb7yzqgso3TKlwBVCEDgdoV R4quJMdCC0NrXjDeysO8zdXSzf+yS4hk/iowc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TgIlPOfJlSDhhsbclhXNVvlVULufr185o5Yi/Ab4mVOA7GI/Ps36/NWOrTfBOZbAd/ tuwBpuJO+QgBxYRTrJchScpSiKe7kZlgJPeb6FDHEPyncTz+yddnnijnBMAWBkyJlAUP 3+li80/LLLxyNM05auHyPTabrbjaicBR2xMYY= MIME-Version: 1.0 Received: by 10.224.38.26 with SMTP id z26mr11945046qad.375.1293481129377; Mon, 27 Dec 2010 12:18:49 -0800 (PST) Received: by 10.220.192.11 with HTTP; Mon, 27 Dec 2010 12:18:49 -0800 (PST) Date: Mon, 27 Dec 2010 23:18:49 +0300 Message-ID: From: Michael BlackHeart To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 20:43:45 -0000 Hello I've got trouble with FreeBSD 8 Stable First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to yesterday revision I don't remember exact number, but I've have this problem aobut week or two so it's not so important, also as it doesn't work on i386 too. After installing new kernel I've just build - indeed it always was GENERIC for both arch's on clean system - I've got an a kernel painc caused by disability to mount root partition because kernel couldn't see the drive. By pressing '?' I've sen only acd0 that represents CD-ROM. In debug messages I haven't found anything about ad0 - than hdd was identified before new kernel was installed. I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is working with diabled SATA native mode. I've not found any info 'bout this error in recent 8.Stable so I don't know how to handle this one. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 21:56:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F7E9106564A for ; Mon, 27 Dec 2010 21:56:25 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3C1FD8FC15 for ; Mon, 27 Dec 2010 21:56:24 +0000 (UTC) Received: by ywp6 with SMTP id 6so4128355ywp.13 for ; Mon, 27 Dec 2010 13:56:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oBAkqXiy06jDVpWVde3uIRX5+MCBVzdWkMTDke6Mf24=; b=JdxzDgTHMct/0Scl/pX/ORvJfoDHCPCcx5Qz+tbncpv+brpARP72k3jQrI/rD51cw0 v0nLfi2L6kt1CbEqFdRO+F9udjeMDQMK2SwRzLYf4AZsZaJBMfZCDNkAM1zRg8mAmvVA cABCMlY/C2+Gbi9vHH0CBe6OoTcVftMrB8+y4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bnJstTHDIUnSf1Zz5jesuI447XGZDN7vyZz48zJXuCuwEvYjFTa9gNsu55w72Qu1zC Jh3LE6xlS61lqWDCZkaiklSUmVf2iviNbj9h3vA4uhElAd3yHJo2SHpleLZu7srDRYim aeDEFOqDoPj/Job0CAaqaGMCDHdY2N9wEjGy4= MIME-Version: 1.0 Received: by 10.90.3.32 with SMTP id 32mr3570284agc.91.1293486984060; Mon, 27 Dec 2010 13:56:24 -0800 (PST) Received: by 10.90.153.20 with HTTP; Mon, 27 Dec 2010 13:56:23 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Dec 2010 13:56:23 -0800 Message-ID: From: Freddie Cash To: Jean-Yves Avenard Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 21:56:25 -0000 T24gU3VuLCBEZWMgMjYsIDIwMTAgYXQgNDo0MyBQTSwgSmVhbi1ZdmVzIEF2ZW5hcmQgPGp5YXZl bmFyZEBnbWFpbC5jb20+IHdyb3RlOgo+IE9uIDI3IERlY2VtYmVyIDIwMTAgMDk6NTUsIEplYW4t WXZlcyBBdmVuYXJkIDxqeWF2ZW5hcmRAZ21haWwuY29tPiB3cm90ZToKPj4gSGkgdGhlcmUuCj4+ Cj4+IEkgdXNlZCBzdGFibGUtOC16ZnN2MjgtMjAxMDEyMjMtbm9weXRob24ucGF0Y2gueHogZnJv bQo+PiBodHRwOi8vcGVvcGxlLmZyZWVic2Qub3JnL35tbS9wYXRjaGVzL3pmcy92MjgvCj4KPiBJ IGRpZCB0aGUgZm9sbG93aW5nOgo+Cj4gIyB6cG9vbCBzdGF0dXMKPiDCoHBvb2w6IHBvb2wKPiDC oHN0YXRlOiBPTkxJTkUKPiDCoHNjYW46IG5vbmUgcmVxdWVzdGVkCj4gY29uZmlnOgo+Cj4gwqAg wqAgwqAgwqBOQU1FIMKgIMKgIMKgIMKgIMKgIMKgU1RBVEUgwqAgwqAgUkVBRCBXUklURSBDS1NV TQo+IMKgIMKgIMKgIMKgcG9vbCDCoCDCoCDCoCDCoCDCoCDCoE9OTElORSDCoCDCoCDCoCAwIMKg IMKgIDAgwqAgwqAgMAo+IMKgIMKgIMKgIMKgIMKgcmFpZHoxLTAgwqAgwqAgwqBPTkxJTkUgwqAg wqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTIgwqAgwqAgwqAg wqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFk YTMgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDC oCDCoCDCoCDCoGFkYTQgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKg IDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTUgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDC oCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTYgwqAgwqAgwqAgwqBPTkxJTkUg wqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTcgwqAgwqAg wqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoGNhY2hl Cj4gwqAgwqAgwqAgwqAgwqBsYWJlbC96Y2FjaGUgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAw IMKgIMKgIDAKPgo+IGVycm9yczogTm8ga25vd24gZGF0YSBlcnJvcnMKPgo+IHNvIGZhciBzbyBn b29kCj4KPiBbcm9vdEBzZXJ2ZXI0IC9wb29sL2hvbWUvamVhbnl2ZXNfYXZlbmFyZF0jIHpwb29s IGFkZCBwb29sIGxvZwo+IC9kZXYvbGFiZWwvemlsIFtyb290QHNlcnZlcjQgL3Bvb2wvaG9tZS9q ZWFueXZlc19hdmVuYXJkXSMgenBvb2wKPiBzdGF0dXMKPiDCoHBvb2w6IHBvb2wKPiDCoHN0YXRl OiBPTkxJTkUKPiDCoHNjYW46IG5vbmUgcmVxdWVzdGVkCj4gY29uZmlnOgo+Cj4gwqAgwqAgwqAg wqBOQU1FIMKgIMKgIMKgIMKgIMKgIMKgU1RBVEUgwqAgwqAgUkVBRCBXUklURSBDS1NVTQo+IMKg IMKgIMKgIMKgcG9vbCDCoCDCoCDCoCDCoCDCoCDCoE9OTElORSDCoCDCoCDCoCAwIMKgIMKgIDAg wqAgwqAgMAo+IMKgIMKgIMKgIMKgIMKgcmFpZHoxLTAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAg MCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTIgwqAgwqAgwqAgwqBPTkxJ TkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTMgwqAg wqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDC oCDCoGFkYTQgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDC oCDCoCDCoCDCoCDCoCDCoGFkYTUgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAw IMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTYgwqAgwqAgwqAgwqBPTkxJTkUgwqAgwqAg wqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoCDCoCDCoGFkYTcgwqAgwqAgwqAgwqBP TkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPiDCoCDCoCDCoCDCoGxvZ3MKPiDCoCDC oCDCoCDCoCDCoGxhYmVsL3ppbCDCoCDCoCBPTkxJTkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKg IDAKPiDCoCDCoCDCoCDCoGNhY2hlCj4gwqAgwqAgwqAgwqAgwqBsYWJlbC96Y2FjaGUgwqBPTkxJ TkUgwqAgwqAgwqAgMCDCoCDCoCAwIMKgIMKgIDAKPgo+IGVycm9yczogTm8ga25vd24gZGF0YSBl cnJvcnMKPgo+IHNvIGZhciBzbyBnb29kOgo+Cj4gIyB6cG9vbCByZW1vdmUgcG9vbCBsb2dzIGxh YmVsL3ppbAo+IGNhbm5vdCByZW1vdmUgbG9nczogbm8gc3VjaCBkZXZpY2UgaW4gcG9vbAoKSXMg dGhhdCBhIHR5cG8sIG9yIHRoZSBhY3R1YWwgY29tbWFuZCB5b3UgdXNlZD8gIFlvdSBoYXZlIGFu IGV4dHJhICJzIgppbiB0aGVyZS4gIFNob3VsZCBiZSAibG9nIiBhbmQgbm90ICJsb2dzIi4gIEhv d2V2ZXIsIEkgZG9uJ3QgdGhpbmsKdGhhdCBjb21tYW5kIGlzIGNvcnJlY3QgZWl0aGVyLgoKSSBi ZWxpZXZlIHlvdSB3YW50IHRvIHVzZSB0aGUgImRldGFjaCIgY29tbWFuZCwgbm90ICJyZW1vdmUi LgoKIyB6cG9vbCBkZXRhY2ggcG9vbCBsYWJlbC96aWwKCi0tIApGcmVkZGllIENhc2gKZmp3Y2Fz aEBnbWFpbC5jb20K From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 22:44:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C349106566B for ; Mon, 27 Dec 2010 22:44:28 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (outgoing01.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id C22708FC12 for ; Mon, 27 Dec 2010 22:44:27 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 111E314E631 for ; Mon, 27 Dec 2010 12:44:26 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id A8AB8196E1C; Mon, 27 Dec 2010 12:44:26 -1000 (HST) Date: Mon, 27 Dec 2010 12:44:26 -1000 From: Clifton Royston To: FreeBSD Stable List Message-ID: <20101227224426.GA11955@lava.net> Mail-Followup-To: FreeBSD Stable List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 22:44:28 -0000 OK, so I'm a late adopter - up til now I've always upgraded FreeBSD machines from source or picking the update from a CD, but I decided to try freebsd-update to finally get my home machine from 6.4 to 7.1 (and thence hopefully to 8.1). Everything went well up through the merge steps, until I noticed a merge I had forgotten to resolve in /etc/hosts.allow, so at the "Does this look reasonable (y/n)?" prompt I answered 'n', thinking that would put me back into the editor. Instead it dumped me to the command line and aborted the update completely. How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) I just tried typing "sudo freebsd-update install" and "sudo freebsd-update install -r 7.1-RELEASE" but that gives me: "No updates are available to install." Is there some way to resume where I left off? -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 22:51:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DC21065670 for ; Mon, 27 Dec 2010 22:51:03 +0000 (UTC) (envelope-from jhelfman@experts-exchange.com) Received: from mail.experts-exchange.com (mail.experts-exchange.com [72.29.183.251]) by mx1.freebsd.org (Postfix) with ESMTP id 409498FC13 for ; Mon, 27 Dec 2010 22:51:03 +0000 (UTC) Received: from mail.experts-exchange.com (localhost [127.0.0.1]) by mail.experts-exchange.com (Postfix) with ESMTP id E3835CA570A; Mon, 27 Dec 2010 14:51:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=e-e.com; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received:received; s=ee; t= 1293490262; x=1295304662; bh=Mfii4srox6S17boec0Z9bafjbqE9oaq7uNr kapU6uRk=; b=CeTUFCRhDtYBv22QXXbH4FQzTGFk8DqWaJ7388lr/zTd113A0jo YmweB/gWft7D7gTPvfPKi3RuWlJHrLKEVYwaCaIbRfpi76PNMrMjSpGwr5F+YgCf 0aPTG9NbuHxahii3izc9FIBfZkDMb41VNuQrCVHL+dmlQ75lcign86G4= X-Virus-Scanned: amavisd-new at experts-exchange.com Received: from mail.experts-exchange.com ([127.0.0.1]) by mail.experts-exchange.com (mail.experts-exchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18Qeo5J0pEmc; Mon, 27 Dec 2010 14:51:02 -0800 (PST) Received: from experts-exchange.com (unknown [192.168.103.122]) by mail.experts-exchange.com (Postfix) with SMTP id 7819ECA5706; Mon, 27 Dec 2010 14:51:02 -0800 (PST) Received: (nullmailer pid 92329 invoked by uid 1001); Mon, 27 Dec 2010 22:47:53 -0000 Date: Mon, 27 Dec 2010 14:47:53 -0800 From: Jason Helfman To: Clifton Royston Message-ID: <20101227224752.GC1505@eggman.experts-exchange.com> References: <20101227224426.GA11955@lava.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20101227224426.GA11955@lava.net> X-Operating-System: FreeBSD 8.1-RELEASE X-Living-The-Dream: I love the SLO Life! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 22:51:03 -0000 On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: > OK, so I'm a late adopter - up til now I've always upgraded FreeBSD >machines from source or picking the update from a CD, but I decided to >try freebsd-update to finally get my home machine from 6.4 to 7.1 (and >thence hopefully to 8.1). > > Everything went well up through the merge steps, until I noticed a >merge I had forgotten to resolve in /etc/hosts.allow, so at the >"Does this look reasonable (y/n)?" prompt I answered 'n', thinking that >would put me back into the editor. > > Instead it dumped me to the command line and aborted the update >completely. > > How can I continue from here without downloading and applying 29000+ >patches all over again, not to mention having to manually resolve the >updated $FreeBSD lines in a ton of config files? (Or worse, having it >try to apply patches which have already been applied?) > > I just tried typing "sudo freebsd-update install" and >"sudo freebsd-update install -r 7.1-RELEASE" but that gives me: I've never run this command for a specific release. > > "No updates are available to install." What happens if you run "freebsd-update install" ? If you haven't installed anything, there is nothing to rollback. A feature that is part of freebsd-update. > > Is there some way to resume where I left off? I'm not aware of any method to do this, other than to remove everything under /var/db/freebsd-update and start from the beginning. > -- Clifton > >-- > Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net > President - I and I Computing * http://www.iandicomputing.com/ > Custom programming, network design, systems and network consulting services >_______________________________________________ >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" > -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 22:58:30 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A4321065673 for ; Mon, 27 Dec 2010 22:58:30 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing03.lava.net (outgoing03.lava.net [IPv6:2001:1888:0:1:202:b3ff:fe1d:6b98]) by mx1.freebsd.org (Postfix) with ESMTP id 28A098FC13 for ; Mon, 27 Dec 2010 22:58:30 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing03.lava.net (Postfix) with ESMTP id 2CA4110818; Mon, 27 Dec 2010 12:58:29 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 96700196E1C; Mon, 27 Dec 2010 12:58:28 -1000 (HST) Date: Mon, 27 Dec 2010 12:58:28 -1000 From: Clifton Royston To: Jason Helfman Message-ID: <20101227225828.GB11955@lava.net> Mail-Followup-To: Jason Helfman , freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101227224752.GC1505@eggman.experts-exchange.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 22:58:30 -0000 On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: Thanks for the prompt response! > On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: ... > > How can I continue from here without downloading and applying 29000+ > >patches all over again, not to mention having to manually resolve the > >updated $FreeBSD lines in a ton of config files? (Or worse, having it > >try to apply patches which have already been applied?) > > > > I just tried typing "sudo freebsd-update install" and > >"sudo freebsd-update install -r 7.1-RELEASE" but that gives me: > > I've never run this command for a specific release. > > > >"No updates are available to install." > > What happens if you run "freebsd-update install" ? Same message. > If you haven't installed anything, there is nothing to rollback. A > feature that is part of freebsd-update. I guess I should have realized that, at least. > > Is there some way to resume where I left off? > > I'm not aware of any method to do this, other than to remove everything > under /var/db/freebsd-update and start from the beginning. OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 22:59:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9FB106566B for ; Mon, 27 Dec 2010 22:59:57 +0000 (UTC) (envelope-from troy@twisted.net) Received: from oz.twisted.net (oz.twisted.net [69.211.34.241]) by mx1.freebsd.org (Postfix) with ESMTP id AD0EC8FC14 for ; Mon, 27 Dec 2010 22:59:56 +0000 (UTC) Received: from oz.twisted.net (localhost [127.0.0.1]) by oz.twisted.net (Postfix) with ESMTP id 4762EFF21FE for ; Mon, 27 Dec 2010 16:44:07 -0600 (CST) X-Virus-Scanned: amavisd-new at example.com Received: from oz.twisted.net ([127.0.0.1]) by oz.twisted.net (oz.twisted.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MytHLkYqCuDB for ; Mon, 27 Dec 2010 16:43:48 -0600 (CST) Received: from [172.16.0.5] (sindrome.twisted.net [172.16.0.5]) by oz.twisted.net (Postfix) with ESMTP id EC010FF21FC for ; Mon, 27 Dec 2010 16:43:42 -0600 (CST) Message-ID: <4D191642.4050908@twisted.net> Date: Mon, 27 Dec 2010 16:42:10 -0600 From: Troy User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: troy@twisted.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2010 22:59:57 -0000 I recently rebuilt the world and kernel and everything built just fine and when I went to boot into the new kernel, it hangs. I had to revert back to my previous kernel. Currently I'm running: FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server amd64 When it hangs upon boot-up it simply stops here. I don't know how I can figure out what is causing the root of the hang. I'd really like to get this machine upgraded. Ppc0 cannot reserve I/O port range PowerNow0 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow0 on cpu1 Device_attach: PowerNow0 attach return 6 PowerNow1 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow1 on cpu1 Device_attach: PowerNow0 attach return 6 Time Counters Tick every 1.000 msec <<>> Any help is greatly appreciated. -Troy From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 23:06:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF6F8106564A for ; Mon, 27 Dec 2010 23:06:05 +0000 (UTC) (envelope-from jhelfman@experts-exchange.com) Received: from mail.experts-exchange.com (mail.experts-exchange.com [72.29.183.251]) by mx1.freebsd.org (Postfix) with ESMTP id CB3EF8FC0C for ; Mon, 27 Dec 2010 23:06:05 +0000 (UTC) Received: from mail.experts-exchange.com (localhost [127.0.0.1]) by mail.experts-exchange.com (Postfix) with ESMTP id 6CBA1CA5710; Mon, 27 Dec 2010 15:06:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=e-e.com; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received:received; s=ee; t= 1293491165; x=1295305565; bh=36yOZvrI+QysIPRwHbU9p20eU5ERn2P+pBN A+mID7P8=; b=Dt19w3d9GDeUciIwaYBTpd75LVPDciMtBhvFI1dbVXVi/EXJgbe EpRPpxMTwJ2G1GJJLoHmXP75xbisA11w4XjdyoXPIHtR0uVQ50DFc9ShbeuNf1Bf O+zfmVFCBfaamzGx2zMiLDlB4lDkB/rFt9anVZG6F3xMUDBjw6ZENyyI= X-Virus-Scanned: amavisd-new at experts-exchange.com Received: from mail.experts-exchange.com ([127.0.0.1]) by mail.experts-exchange.com (mail.experts-exchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5Uu5hFhPY32; Mon, 27 Dec 2010 15:06:05 -0800 (PST) Received: from experts-exchange.com (unknown [192.168.103.122]) by mail.experts-exchange.com (Postfix) with SMTP id 1DA11CA570C; Mon, 27 Dec 2010 15:06:05 -0800 (PST) Received: (nullmailer pid 92420 invoked by uid 1001); Mon, 27 Dec 2010 23:02:56 -0000 Date: Mon, 27 Dec 2010 15:02:56 -0800 From: Jason Helfman To: freebsd-stable@freebsd.org Message-ID: <20101227230255.GD1505@eggman.experts-exchange.com> References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20101227225828.GB11955@lava.net> X-Operating-System: FreeBSD 8.1-RELEASE X-Living-The-Dream: I love the SLO Life! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: cliftonr@lava.net Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 23:06:06 -0000 On Mon, Dec 27, 2010 at 12:58:28PM -1000, Clifton Royston thus spake: >On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: > > Thanks for the prompt response! Your welcome :) > >> On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: >... >> > How can I continue from here without downloading and applying 29000+ >> >patches all over again, not to mention having to manually resolve the >> >updated $FreeBSD lines in a ton of config files? (Or worse, having it >> >try to apply patches which have already been applied?) >> > >> > I just tried typing "sudo freebsd-update install" and >> >"sudo freebsd-update install -r 7.1-RELEASE" but that gives me: >> >> I've never run this command for a specific release. >> > >> >"No updates are available to install." >> >> What happens if you run "freebsd-update install" ? > > Same message. You may want to just try and run the 'fetch' again. freebsd-update -r 7.1-RELEASE fetch > > >> If you haven't installed anything, there is nothing to rollback. A >> feature that is part of freebsd-update. > > I guess I should have realized that, at least. > >> > Is there some way to resume where I left off? >> >> I'm not aware of any method to do this, other than to remove everything >> under /var/db/freebsd-update and start from the beginning. > > OK, and oh well... I wish there were some way to automate the diffing >out of the $FreeBSD lines. I suppose those might be the artifact of >some previous upgrade, so that the file version present is not the one >expected for FreeBSD 6.1. I believe there is with a handcrafted mergemaster.rc file. I was told by Colin that this 'bug' was introduced at some point with freebsd-update, as branches at one point weren't tagged. When they started to get tagged, freebsd-update started to compare. -jgh > > -- Clifton > >-- > Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net > President - I and I Computing * http://www.iandicomputing.com/ > Custom programming, network design, systems and network consulting services > -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html From owner-freebsd-stable@FreeBSD.ORG Mon Dec 27 23:51:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DDD91065670 for ; Mon, 27 Dec 2010 23:51:09 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E764A8FC12 for ; Mon, 27 Dec 2010 23:51:08 +0000 (UTC) Received: by iyb26 with SMTP id 26so8069714iyb.13 for ; Mon, 27 Dec 2010 15:51:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rFYQQPg5u1l5SMg7UUsYgRTdur9sG3SjxVpomXoMb2U=; b=w+vdOMTZeI3aMByklD/wARWeVy3b4PX3DzZiYaUuIw5kd7OsZhzuJ87lHcSNELo2v6 gvdb3YeTClWoxYVSg14JJ+3J0KVUXPsXUngK4h/ohV/O/RBTXwaVeMJfoHigqG5jBZqd 6tz/WtpsesV7Q0u3IIYGTDWR58FSGjn3XC7gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rWKJZR7SXlTr99HRNPQxpWYNixHy9IIIxEVTgBCOzMHh7Js/U5hv/fWsRblllsyiCJ qY4QP2FL+EBEnVmzUAQVM0T2C9oOOdzMoJ/UO5RbIDSrIUmcbMNZD252qLUHSMVzf542 lLj5UtBATkjkNoCVjXQs4Ko3kO8oe1mRl7qYc= MIME-Version: 1.0 Received: by 10.42.167.131 with SMTP id s3mr12871002icy.260.1293493868308; Mon, 27 Dec 2010 15:51:08 -0800 (PST) Received: by 10.42.220.70 with HTTP; Mon, 27 Dec 2010 15:51:08 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Dec 2010 10:51:08 +1100 Message-ID: From: Jean-Yves Avenard To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-stable@freebsd.org" Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Dec 2010 23:51:09 -0000 Hi On Tuesday, 28 December 2010, Freddie Cash wrote: > On Sun, Dec 26, 2010 at 4:43 PM, Jean-Yves Avenard = wrote: >> On 27 December 2010 09:55, Jean-Yves Avenard wrote= : >>> Hi there. >>> >>> I used stable-8-zfsv28-20101223-nopython.patch.xz from >>> http://people.freebsd.org/~mm/patches/zfs/v28/ >> >> I did the following: >> >> # zpool status >> =A0pool: pool >> =A0state: ONLINE >> =A0scan: none requested >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSU= M >> =A0 =A0 =A0 =A0pool =A0 =A0 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0raidz1-0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada2 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada3 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada4 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada5 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada6 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada7 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0cache >> =A0 =A0 =A0 =A0 =A0label/zcache =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> >> errors: No known data errors >> >> so far so good >> >> [root@server4 /pool/home/jeanyves_avenard]# zpool add pool log >> /dev/label/zil [root@server4 /pool/home/jeanyves_avenard]# zpool >> status >> =A0pool: pool >> =A0state: ONLINE >> =A0scan: none requested >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSU= M >> =A0 =A0 =A0 =A0pool =A0 =A0 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0raidz1-0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada2 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada3 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada4 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada5 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada6 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ada7 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 = 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0logs >> =A0 =A0 =A0 =A0 =A0label/zil =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0cache >> =A0 =A0 =A0 =A0 =A0label/zcache =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> >> errors: No known data errors >> >> so far so good: >> >> # zpool remove pool logs label/zil >> cannot remove logs: no such device in pool > > Is that a typo, or the actual command you used? =A0You have an extra "s" > in there. =A0Should be "log" and not "logs". =A0However, I don't think > that command is correct either. > > I believe you want to use the "detach" command, not "remove". > # zpool detach pool label/zil > > -- > Freddie Cash > fjwcash@gmail.com > It was a typo, it should have been log (according to sun's doc). As it was showing "logs" in the status I typed this. According to sun, it zpool remove pool cache/log A typo should have never resulted in what happened, showing an error for sure; but zpool hanging and kernel panic? From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 00:10:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C40AA1065679 for ; Tue, 28 Dec 2010 00:10:01 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (outgoing01.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA6C8FC1D for ; Tue, 28 Dec 2010 00:10:01 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 8E7B714E62C; Mon, 27 Dec 2010 14:10:00 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id C108F196E1C; Mon, 27 Dec 2010 14:09:59 -1000 (HST) Date: Mon, 27 Dec 2010 14:09:59 -1000 From: Clifton Royston To: Jason Helfman Message-ID: <20101228000959.GC11955@lava.net> Mail-Followup-To: Jason Helfman , freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <20101227230255.GD1505@eggman.experts-exchange.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101227230255.GD1505@eggman.experts-exchange.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 00:10:01 -0000 On Mon, Dec 27, 2010 at 03:02:56PM -0800, Jason Helfman wrote: > On Mon, Dec 27, 2010 at 12:58:28PM -1000, Clifton Royston thus spake: > >On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: > >>On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: > >... > >>> How can I continue from here without downloading and applying 29000+ > >>>patches all over again, not to mention having to manually resolve the > >>>updated $FreeBSD lines in a ton of config files? (Or worse, having it > >>>try to apply patches which have already been applied?) ... > >>If you haven't installed anything, there is nothing to rollback. A > >>feature that is part of freebsd-update. > > > > I guess I should have realized that, at least. > > > >>> Is there some way to resume where I left off? > >> > >>I'm not aware of any method to do this, other than to remove everything > >>under /var/db/freebsd-update and start from the beginning. I started over but without removing the directory, and found that after redownloading all the metadata, it DTRT: nothing more got downloaded, and it apparently identified all the automatic merges as already patched. It seems to be starting over at the beginning of the ones to manually patch up. > > OK, and oh well... I wish there were some way to automate the diffing > >out of the $FreeBSD lines. I suppose those might be the artifact of > >some previous upgrade, so that the file version present is not the one > >expected for FreeBSD 6.1. > > I believe there is with a handcrafted mergemaster.rc file. I was told by > Colin that this 'bug' was introduced at some point with freebsd-update, > as branches at one point weren't tagged. > > When they started to get tagged, freebsd-update started to compare. Ah, I saw that discussion a while back on one of the lists for mergemaster, but I didn't realize it applied to freebsd-update as well. Next time around, I'll revisit the email thread and figure out which options I want to pull in to skip those lines. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 00:24:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86B1F106564A for ; Tue, 28 Dec 2010 00:24:57 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 271348FC27 for ; Tue, 28 Dec 2010 00:24:56 +0000 (UTC) Received: by wyf19 with SMTP id 19so8817846wyf.13 for ; Mon, 27 Dec 2010 16:24:55 -0800 (PST) Received: by 10.227.129.69 with SMTP id n5mr185391wbs.136.1293495884191; Mon, 27 Dec 2010 16:24:44 -0800 (PST) Received: from dfleuriot.local (paris.c-mal.com [88.170.200.60]) by mx.google.com with ESMTPS id m10sm8839466wbc.16.2010.12.27.16.24.43 (version=SSLv3 cipher=RC4-MD5); Mon, 27 Dec 2010 16:24:43 -0800 (PST) Message-ID: <4D192E4B.9020701@my.gd> Date: Tue, 28 Dec 2010 01:24:43 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D191642.4050908@twisted.net> In-Reply-To: <4D191642.4050908@twisted.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 00:24:57 -0000 Hey Troy, I can't speak for the rest of the list but I think we're missing a bit of information here. What are you trying to build and boot, 8.1, 8.2pre ? Are you building a GENERIC kernel ? I notice you're currently using a custom one. If you're not, I would suggest trying GENERIC first. You might want to post your whole boot message if it can be recovered. Also and in case you don't know, you may quickly test your kernel like so: nextboot -k yourkernelhere Next reboot, the host will try yourkernelhere, and on the reboot after that, revert to your regular kernel. Other than that, quick things to check: 1/ built world before kernel 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can do for the world) 3/ tracked the *correct* version in the cvsup file (I've had this case where I was running fbsd8 zfs boot, and was building a 7.x kernel by mistake cause I was tracking releng7 -.- ) 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or 8.2, whichever you're tracking On 12/27/10 11:42 PM, Troy wrote: > I recently rebuilt the world and kernel and everything built just fine > and when I went to boot into the new kernel, it hangs. I had to revert > back to my previous kernel. > > Currently I'm running: > FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 > 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server amd64 > > When it hangs upon boot-up it simply stops here. I don't know how I can > figure out what is causing the root of the hang. I'd really like to get > this machine upgraded. > > Ppc0 cannot reserve I/O port range > PowerNow0 on cpu0 > Device_attach: PowerNow0 attach return 6 > PowerNow0 on cpu1 > Device_attach: PowerNow0 attach return 6 > PowerNow1 on cpu0 > Device_attach: PowerNow0 attach return 6 > PowerNow1 on cpu1 > Device_attach: PowerNow0 attach return 6 > Time Counters Tick every 1.000 msec > <<>> > > Any help is greatly appreciated. > > -Troy > > _______________________________________________ > 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 Tue Dec 28 00:36:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18892106566C for ; Tue, 28 Dec 2010 00:36:05 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A9E4E8FC0C for ; Tue, 28 Dec 2010 00:36:04 +0000 (UTC) Received: by wwf26 with SMTP id 26so8667545wwf.31 for ; Mon, 27 Dec 2010 16:36:03 -0800 (PST) Received: by 10.216.18.194 with SMTP id l44mr17461864wel.87.1293496562055; Mon, 27 Dec 2010 16:36:02 -0800 (PST) Received: from dfleuriot.local (paris.c-mal.com [88.170.200.60]) by mx.google.com with ESMTPS id m13sm8849008wbz.3.2010.12.27.16.36.00 (version=SSLv3 cipher=RC4-MD5); Mon, 27 Dec 2010 16:36:01 -0800 (PST) Message-ID: <4D1930F1.9050902@my.gd> Date: Tue, 28 Dec 2010 01:36:01 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 00:36:05 -0000 Hey michael, First, I'd advise making use of FreeBSD's nextboot utility to test new kernels: http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?nextboot+8 Second, I would suggest reading the handbook's excellent section on upgrading your machine or rebuilding the kernel: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html Now, a likely cause of your problem is the installation of a custom kernel with removed support for whatever your hard disk drive or raid controller is recognized as. Did you reinstall your old, working kernel, or are you actually asking for help doing just that ? On 12/27/10 9:18 PM, Michael BlackHeart wrote: > Hello > > I've got trouble with FreeBSD 8 Stable > First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to > yesterday revision I don't remember exact number, but I've have this > problem aobut week or two so it's not so important, also as it doesn't > work on i386 too. > > After installing new kernel I've just build - indeed it always was > GENERIC for both arch's on clean system - I've got an a kernel painc > caused by disability to mount root partition because kernel couldn't > see the drive. By pressing '?' I've sen only acd0 that represents > CD-ROM. > > In debug messages I haven't found anything about ad0 - than hdd was > identified before new kernel was installed. > I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is > working with diabled SATA native mode. > > I've not found any info 'bout this error in recent 8.Stable so I don't > know how to handle this one. > _______________________________________________ > 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 Tue Dec 28 00:40:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C61F61065673 for ; Tue, 28 Dec 2010 00:40:28 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 65EBD8FC15 for ; Tue, 28 Dec 2010 00:40:28 +0000 (UTC) Received: by wyf19 with SMTP id 19so8824100wyf.13 for ; Mon, 27 Dec 2010 16:40:27 -0800 (PST) Received: by 10.227.157.73 with SMTP id a9mr5566706wbx.154.1293496827384; Mon, 27 Dec 2010 16:40:27 -0800 (PST) Received: from dfleuriot.local (paris.c-mal.com [88.170.200.60]) by mx.google.com with ESMTPS id q18sm8848505wbe.17.2010.12.27.16.40.26 (version=SSLv3 cipher=RC4-MD5); Mon, 27 Dec 2010 16:40:26 -0800 (PST) Message-ID: <4D1931FA.3070403@my.gd> Date: Tue, 28 Dec 2010 01:40:26 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> In-Reply-To: <20101227225828.GB11955@lava.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 00:40:28 -0000 On 12/27/10 11:58 PM, Clifton Royston wrote: > > OK, and oh well... I wish there were some way to automate the diffing > out of the $FreeBSD lines. I suppose those might be the artifact of > some previous upgrade, so that the file version present is not the one > expected for FreeBSD 6.1. > > -- Clifton > Wait, do you mean like, mergemaster -F ? Excerpt from the manual: -F If the files differ only by VCS Id ($FreeBSD) install the new file. I've discovered this rather recently, it's a *lifesaver* This comes from fbsd7's version though, I can not say for the one you're still running on fbsd6 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 00:52:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC945106564A for ; Tue, 28 Dec 2010 00:52:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 505A28FC1E for ; Tue, 28 Dec 2010 00:52:05 +0000 (UTC) Received: (qmail 4820 invoked by uid 399); 28 Dec 2010 00:52:04 -0000 Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 28 Dec 2010 00:52:04 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4D1934B3.8080102@FreeBSD.org> Date: Mon, 27 Dec 2010 16:52:03 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101210 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> In-Reply-To: <4D1931FA.3070403@my.gd> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 00:52:05 -0000 On 12/27/2010 16:40, Damien Fleuriot wrote: > > > On 12/27/10 11:58 PM, Clifton Royston wrote: >> >> OK, and oh well... I wish there were some way to automate the diffing >> out of the $FreeBSD lines. I suppose those might be the artifact of >> some previous upgrade, so that the file version present is not the one >> expected for FreeBSD 6.1. >> >> -- Clifton >> > > > Wait, do you mean like, mergemaster -F ? > > Excerpt from the manual: > -F If the files differ only by VCS Id ($FreeBSD) install > the new file. > > > I've discovered this rather recently, it's a *lifesaver* > > This comes from fbsd7's version though, I can not say for the one you're > still running on fbsd6 You always want to run mergemaster from the version you are upgrading _to_. It doesn't happen often (by design) but occasionally mergemaster has to grow "special knowledge" of specific files/directories/etc. in a new FreeBSD version. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 01:14:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 021F8106564A for ; Tue, 28 Dec 2010 01:14:57 +0000 (UTC) (envelope-from troy@twisted.net) Received: from oz.twisted.net (oz.twisted.net [69.211.34.241]) by mx1.freebsd.org (Postfix) with ESMTP id 7BF9E8FC0C for ; Tue, 28 Dec 2010 01:14:56 +0000 (UTC) Received: from oz.twisted.net (localhost [127.0.0.1]) by oz.twisted.net (Postfix) with ESMTP id 17622FF21FE; Mon, 27 Dec 2010 19:07:16 -0600 (CST) X-Virus-Scanned: amavisd-new at example.com Received: from oz.twisted.net ([127.0.0.1]) by oz.twisted.net (oz.twisted.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PnoZVs-DTcCr; Mon, 27 Dec 2010 19:07:00 -0600 (CST) Received: from [172.16.0.5] (sindrome.twisted.net [172.16.0.5]) by oz.twisted.net (Postfix) with ESMTP id AD3FCFF21B4; Mon, 27 Dec 2010 19:06:44 -0600 (CST) Message-ID: <4D1937C8.80609@twisted.net> Date: Mon, 27 Dec 2010 19:05:12 -0600 From: Troy User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Damien Fleuriot , freebsd-stable@freebsd.org References: <4D191642.4050908@twisted.net> <4D192E4B.9020701@my.gd> In-Reply-To: <4D192E4B.9020701@my.gd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: troy@twisted.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 01:14:57 -0000 Sorry. I am on the RELENG_8 tree and I believe it was building 8.2pre. I did the build about 4 days ago. I am building a custom kernel. Yes I definitely built the world before the kernel and it worked. I did not use -J anything. There is no boot message, it just hangs with what I wrote below. Below is the kernel config I'm using. machine amd64 cpu HAMMER ident servername-removed # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options NTFS # NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_43 # Needed by COMPAT_LINUX32 options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options COMPAT_LINUX32 # Compatible with i386 linux binaries options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache options INCLUDE_CONFIG_FILE # Include this file in kernel options IPSTEALTH options INVARIANTS options INVARIANT_SUPPORT # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # For SMBFS - mount_smbfs to work by users options SMBFS # SMB/CIFS filesystem options NETSMB # SMB/CIFS requester options LIBMCHAIN # MBUF management library options LIBICONV # Kernel side iconv library # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability # Linux 32-bit ABI support options LINPROCFS # Cannot be a module yet. # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. device ahd # AHA39320/29320 and onboard AIC79xx devices options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device mpt # LSI-Logic MPT-Fusion device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device twa # 3ware 9000 series PATA/SATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support options VGA_WIDTH90 options SC_PIXEL_MODE # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Serial (COM) ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device vlan # 802.1Q VLAN support device snp # Snoop support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet device udav # Davicom DM9601E USB On 12/27/2010 6:24 PM, Damien Fleuriot wrote: > Hey Troy, > > > I can't speak for the rest of the list but I think we're missing a bit > of information here. > > What are you trying to build and boot, 8.1, 8.2pre ? > > Are you building a GENERIC kernel ? I notice you're currently using a > custom one. > > If you're not, I would suggest trying GENERIC first. > > You might want to post your whole boot message if it can be recovered. > > > > Also and in case you don't know, you may quickly test your kernel like so: > nextboot -k yourkernelhere > > Next reboot, the host will try yourkernelhere, and on the reboot after > that, revert to your regular kernel. > > > Other than that, quick things to check: > > 1/ built world before kernel > > 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can > do for the world) > > 3/ tracked the *correct* version in the cvsup file (I've had this case > where I was running fbsd8 zfs boot, and was building a 7.x kernel by > mistake cause I was tracking releng7 -.- ) > > 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or 8.2, > whichever you're tracking > > > > On 12/27/10 11:42 PM, Troy wrote: >> I recently rebuilt the world and kernel and everything built just fine >> and when I went to boot into the new kernel, it hangs. I had to revert >> back to my previous kernel. >> >> Currently I'm running: >> FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 >> 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server amd64 >> >> When it hangs upon boot-up it simply stops here. I don't know how I can >> figure out what is causing the root of the hang. I'd really like to get >> this machine upgraded. >> >> Ppc0 cannot reserve I/O port range >> PowerNow0 on cpu0 >> Device_attach: PowerNow0 attach return 6 >> PowerNow0 on cpu1 >> Device_attach: PowerNow0 attach return 6 >> PowerNow1 on cpu0 >> Device_attach: PowerNow0 attach return 6 >> PowerNow1 on cpu1 >> Device_attach: PowerNow0 attach return 6 >> Time Counters Tick every 1.000 msec >> <<>> >> >> Any help is greatly appreciated. >> >> -Troy >> >> _______________________________________________ >> 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" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 04:23:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C950106566B for ; Tue, 28 Dec 2010 04:23:23 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing03.lava.net (outgoing03.lava.net [IPv6:2001:1888:0:1:202:b3ff:fe1d:6b98]) by mx1.freebsd.org (Postfix) with ESMTP id 096488FC1A for ; Tue, 28 Dec 2010 04:23:23 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing03.lava.net (Postfix) with ESMTP id 68789101E3; Mon, 27 Dec 2010 18:23:22 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 0E788196E1C; Mon, 27 Dec 2010 18:23:21 -1000 (HST) Date: Mon, 27 Dec 2010 18:23:20 -1000 From: Clifton Royston To: Damien Fleuriot Message-ID: <20101228042320.GA12184@lava.net> Mail-Followup-To: Damien Fleuriot , freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D1931FA.3070403@my.gd> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 04:23:23 -0000 On Tue, Dec 28, 2010 at 01:40:26AM +0100, Damien Fleuriot wrote: > > > On 12/27/10 11:58 PM, Clifton Royston wrote: > > > > OK, and oh well... I wish there were some way to automate the diffing > > out of the $FreeBSD lines. I suppose those might be the artifact of > > some previous upgrade, so that the file version present is not the one > > expected for FreeBSD 6.1. > > > > -- Clifton > > > > > Wait, do you mean like, mergemaster -F ? > > Excerpt from the manual: > -F If the files differ only by VCS Id ($FreeBSD) install > the new file. So *is* freebsd-update invoking mergemaster? There wasn't anything in its man page indicating that, or indicating how to pass flags to it if it is. My assumption was that it wasn't, because it doesn't show the usual mergemaster 4 options with each file (new, delete new, merge old/new, or defer to later.) -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 06:23:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E358106564A; Tue, 28 Dec 2010 06:23:38 +0000 (UTC) (envelope-from jhelfman@experts-exchange.com) Received: from mail.experts-exchange.com (mail.experts-exchange.com [72.29.183.251]) by mx1.freebsd.org (Postfix) with ESMTP id E9A628FC19; Tue, 28 Dec 2010 06:23:37 +0000 (UTC) Received: from mail.experts-exchange.com (localhost [127.0.0.1]) by mail.experts-exchange.com (Postfix) with ESMTP id 6D602CA5907; Mon, 27 Dec 2010 22:23:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=e-e.com; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received:received; s=ee; t= 1293517417; x=1295331817; bh=0JCy1AFLzC9cqZYTX2s7AtSEFPW7447NW5U LvsEfv28=; b=G2n3t3f14OIRl41AYWrQwSZWtduXdgUI34HwJzz77n4z596zcu0 UVcdT6Rp1owJSkVoQd0/TLP3buFFdevEaosMeuihaXWpJ/E6xDOjYl5rrCeZyPim /MotrmJ5ywHTZUhYIKM4Qi5oCwoe+YQI3hKlLJZzX8AcHsnVpJlSgqIg= X-Virus-Scanned: amavisd-new at experts-exchange.com Received: from mail.experts-exchange.com ([127.0.0.1]) by mail.experts-exchange.com (mail.experts-exchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NEd8ikkxiR5Q; Mon, 27 Dec 2010 22:23:37 -0800 (PST) Received: from experts-exchange.com (unknown [192.168.103.122]) by mail.experts-exchange.com (Postfix) with SMTP id 21252CA58E9; Mon, 27 Dec 2010 22:23:37 -0800 (PST) Received: (nullmailer pid 95917 invoked by uid 1001); Tue, 28 Dec 2010 06:20:28 -0000 Date: Mon, 27 Dec 2010 22:20:28 -0800 From: Jason Helfman To: Doug Barton Message-ID: <20101228062028.GA95888@eggman.experts-exchange.com> References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> <4D1934B3.8080102@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4D1934B3.8080102@FreeBSD.org> X-Operating-System: FreeBSD 8.1-RELEASE X-Living-The-Dream: I love the SLO Life! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 06:23:38 -0000 On Mon, Dec 27, 2010 at 04:52:03PM -0800, Doug Barton thus spake: >On 12/27/2010 16:40, Damien Fleuriot wrote: >> >> >> On 12/27/10 11:58 PM, Clifton Royston wrote: >>> >>> OK, and oh well... I wish there were some way to automate the diffing >>> out of the $FreeBSD lines. I suppose those might be the artifact of >>> some previous upgrade, so that the file version present is not the one >>> expected for FreeBSD 6.1. >>> >>> -- Clifton >>> >> >> >> Wait, do you mean like, mergemaster -F ? >> >> Excerpt from the manual: >> -F If the files differ only by VCS Id ($FreeBSD) install >> the new file. >> >> >> I've discovered this rather recently, it's a *lifesaver* >> >> This comes from fbsd7's version though, I can not say for the one you're >> still running on fbsd6 > >You always want to run mergemaster from the version you are upgrading >_to_. It doesn't happen often (by design) but occasionally mergemaster >has to grow "special knowledge" of specific files/directories/etc. in a >new FreeBSD version. As far as I can tell, freebsd-update doesn't use mergemaster. /usr/src/usr.sbin/freebsd-update/freebsd-update.sh Source installation does, however I don't believe a binary upgrade does. -jgh From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 10:13:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4C27106564A for ; Tue, 28 Dec 2010 10:13:35 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 454888FC19 for ; Tue, 28 Dec 2010 10:13:34 +0000 (UTC) Received: by wyf19 with SMTP id 19so9058153wyf.13 for ; Tue, 28 Dec 2010 02:13:33 -0800 (PST) Received: by 10.227.132.209 with SMTP id c17mr7927515wbt.135.1293531201001; Tue, 28 Dec 2010 02:13:21 -0800 (PST) Received: from dfleuriot.local ([83.167.62.196]) by mx.google.com with ESMTPS id m10sm9142440wbc.16.2010.12.28.02.13.19 (version=SSLv3 cipher=RC4-MD5); Tue, 28 Dec 2010 02:13:19 -0800 (PST) Message-ID: <4D19B83E.2090308@my.gd> Date: Tue, 28 Dec 2010 11:13:18 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: troy@twisted.net References: <4D191642.4050908@twisted.net> <4D192E4B.9020701@my.gd> <4D1937C8.80609@twisted.net> In-Reply-To: <4D1937C8.80609@twisted.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 10:13:35 -0000 Well, I would suggest you try this: cd /usr/src make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC cd /boot mv kernel test mv kernel.old kernel nextboot -k test Then, you can reboot. This will ensure you can boot a stock kernel just fine. If you can, obviously there is something wrong with your custom kernel and you should start from a fresh GENERIC kernel and remove devices and drivers little by little. On 12/28/10 2:05 AM, Troy wrote: > Sorry. > > I am on the RELENG_8 tree and I believe it was building 8.2pre. I did > the build about 4 days ago. I am building a custom kernel. Yes I > definitely built the world before the kernel and it worked. I did not > use -J anything. There is no boot message, it just hangs with what I > wrote below. Below is the kernel config I'm using. > > machine amd64 > cpu HAMMER > ident servername-removed > > # To statically compile in device wiring instead of /boot/device.hints > #hints "GENERIC.hints" # Default places to look for > devices. > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug > symbols > > options SCHED_ULE # ULE scheduler > options PREEMPTION # Enable kernel thread preemption > options INET # InterNETworking > options SCTP # Stream Control Transmission > Protocol > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big > directories > options UFS_GJOURNAL # Enable gjournal-based UFS > journaling > options MD_ROOT # MD is a potential root device > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFSLOCKD # Network Lock Manager > options NFS_ROOT # NFS usable as /, requires > NFSCLIENT > options NTFS # NT File System > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires > PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_PART_GPT # GUID Partition Tables. > options GEOM_LABEL # Provides labelization > options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) > options COMPAT_IA32 # Compatible with i386 binaries > options COMPAT_43 # Needed by COMPAT_LINUX32 > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options COMPAT_FREEBSD6 # Compatible with FreeBSD6 > options COMPAT_FREEBSD7 # Compatible with FreeBSD7 > options COMPAT_LINUX32 # Compatible with i386 linux > binaries > options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options STACK # stack(9) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options P1003_1B_SEMAPHORES # POSIX-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time > extensions > options PRINTF_BUFR_SIZE=128 # Prevent printf output being > interspersed. > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options HWPMC_HOOKS # Necessary kernel hooks for > hwpmc(4) > options AUDIT # Security event auditing > options MAC # TrustedBSD MAC Framework > options FLOWTABLE # per-cpu routing cache > options INCLUDE_CONFIG_FILE # Include this file in kernel > options IPSTEALTH > options INVARIANTS > options INVARIANT_SUPPORT > > # Make an SMP-capable kernel by default > options SMP # Symmetric MultiProcessor Kernel > > # CPU frequency control > device cpufreq > > # For SMBFS - mount_smbfs to work by users > options SMBFS # SMB/CIFS filesystem > options NETSMB # SMB/CIFS requester > options LIBMCHAIN # MBUF management library > options LIBICONV # Kernel side iconv library > > # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) > device atpic # 8259A compatability > > # Linux 32-bit ABI support > options LINPROCFS # Cannot be a module yet. > > # Bus support. > device acpi > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > options ATA_STATIC_ID # Static device numbering > > # SCSI Controllers > device ahc # AHA2940 and onboard AIC7xxx devices > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~128k to driver. > device ahd # AHA39320/29320 and onboard AIC79xx > devices > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~215k to driver. > device amd # AMD 53C974 (Tekram DC-390(T)) > device isp # Qlogic family > device mpt # LSI-Logic MPT-Fusion > device sym # NCR/Symbios Logic (newer chipsets + > those of `ncr') > device trm # Tekram DC395U/UW/F DC315U adapters > > device adv # Advansys SCSI adapters > device adw # Advansys wide SCSI adapters > device aic # Adaptec 15[012]x SCSI adapters, > AIC-6[23]60. > device bt # Buslogic/Mylex MultiMaster > SCSI adapters > > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device ch # SCSI media changers > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > device ses # SCSI Environmental Services (and SAF-TE) > > # RAID controllers interfaced to the SCSI subsystem > device twa # 3ware 9000 series PATA/SATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device kbdmux # keyboard multiplexer > device vga # VGA video card driver > device splash # Splash screen and screen saver support > options VGA_WIDTH90 > options SC_PIXEL_MODE > > # syscons is the default console driver, resembling an SCO console > device sc > device agp # support several AGP chipsets > > # Serial (COM) ports > device uart # Generic UART driver > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device ppi # Parallel port interface device > > > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these > NICs! > device miibus # MII bus support > device bge # Broadcom BCM570xx Gigabit Ethernet > > # Pseudo devices. > device loop # Network loopback > device random # Entropy device > device ether # Ethernet support > device vlan # 802.1Q VLAN support > device snp # Snoop support > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device firmware # firmware assist module > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device ehci # EHCI PCI->USB interface (USB 2.0) > device usb # USB Bus (required) > device uhid # "Human Interface Devices" > device ukbd # Keyboard > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus > and da > device ums # Mouse > > # USB Ethernet, requires miibus > device aue # ADMtek USB Ethernet > device axe # ASIX Electronics USB Ethernet > device cdce # Generic USB over Ethernet > device cue # CATC USB Ethernet > device kue # Kawasaki LSI USB Ethernet > device rue # RealTek RTL8150 USB Ethernet > device udav # Davicom DM9601E USB > > > > > On 12/27/2010 6:24 PM, Damien Fleuriot wrote: >> Hey Troy, >> >> >> I can't speak for the rest of the list but I think we're missing a bit >> of information here. >> >> What are you trying to build and boot, 8.1, 8.2pre ? >> >> Are you building a GENERIC kernel ? I notice you're currently using a >> custom one. >> >> If you're not, I would suggest trying GENERIC first. >> >> You might want to post your whole boot message if it can be recovered. >> >> >> >> Also and in case you don't know, you may quickly test your kernel like >> so: >> nextboot -k yourkernelhere >> >> Next reboot, the host will try yourkernelhere, and on the reboot after >> that, revert to your regular kernel. >> >> >> Other than that, quick things to check: >> >> 1/ built world before kernel >> >> 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can >> do for the world) >> >> 3/ tracked the *correct* version in the cvsup file (I've had this case >> where I was running fbsd8 zfs boot, and was building a 7.x kernel by >> mistake cause I was tracking releng7 -.- ) >> >> 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or 8.2, >> whichever you're tracking >> >> >> >> On 12/27/10 11:42 PM, Troy wrote: >>> I recently rebuilt the world and kernel and everything built just fine >>> and when I went to boot into the new kernel, it hangs. I had to revert >>> back to my previous kernel. >>> >>> Currently I'm running: >>> FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 >>> 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server >>> amd64 >>> >>> When it hangs upon boot-up it simply stops here. I don't know how I can >>> figure out what is causing the root of the hang. I'd really like to get >>> this machine upgraded. >>> >>> Ppc0 cannot reserve I/O port range >>> PowerNow0 on cpu0 >>> Device_attach: PowerNow0 attach return 6 >>> PowerNow0 on cpu1 >>> Device_attach: PowerNow0 attach return 6 >>> PowerNow1 on cpu0 >>> Device_attach: PowerNow0 attach return 6 >>> PowerNow1 on cpu1 >>> Device_attach: PowerNow0 attach return 6 >>> Time Counters Tick every 1.000 msec >>> <<>> >>> >>> Any help is greatly appreciated. >>> >>> -Troy >>> >>> _______________________________________________ >>> 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" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 10:15:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AD7D1065694 for ; Tue, 28 Dec 2010 10:15:15 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2641F8FC19 for ; Tue, 28 Dec 2010 10:15:15 +0000 (UTC) Received: by wyf19 with SMTP id 19so9059028wyf.13 for ; Tue, 28 Dec 2010 02:15:14 -0800 (PST) Received: by 10.227.157.207 with SMTP id c15mr7895206wbx.32.1293531314323; Tue, 28 Dec 2010 02:15:14 -0800 (PST) Received: from dfleuriot.local ([83.167.62.196]) by mx.google.com with ESMTPS id m13sm9144893wbz.15.2010.12.28.02.15.13 (version=SSLv3 cipher=RC4-MD5); Tue, 28 Dec 2010 02:15:13 -0800 (PST) Message-ID: <4D19B8B1.1060404@my.gd> Date: Tue, 28 Dec 2010 11:15:13 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> <4D1934B3.8080102@FreeBSD.org> <20101228062028.GA95888@eggman.experts-exchange.com> In-Reply-To: <20101228062028.GA95888@eggman.experts-exchange.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 10:15:15 -0000 On 12/28/10 7:20 AM, Jason Helfman wrote: > On Mon, Dec 27, 2010 at 04:52:03PM -0800, Doug Barton thus spake: >> On 12/27/2010 16:40, Damien Fleuriot wrote: >>> >>> >>> On 12/27/10 11:58 PM, Clifton Royston wrote: >>>> >>>> OK, and oh well... I wish there were some way to automate the >>>> diffing >>>> out of the $FreeBSD lines. I suppose those might be the artifact of >>>> some previous upgrade, so that the file version present is not the one >>>> expected for FreeBSD 6.1. >>>> >>>> -- Clifton >>>> >>> >>> >>> Wait, do you mean like, mergemaster -F ? >>> >>> Excerpt from the manual: >>> -F If the files differ only by VCS Id ($FreeBSD) install >>> the new file. >>> >>> >>> I've discovered this rather recently, it's a *lifesaver* >>> >>> This comes from fbsd7's version though, I can not say for the one you're >>> still running on fbsd6 >> >> You always want to run mergemaster from the version you are upgrading >> _to_. It doesn't happen often (by design) but occasionally mergemaster >> has to grow "special knowledge" of specific files/directories/etc. in a >> new FreeBSD version. > > As far as I can tell, freebsd-update doesn't use mergemaster. > > /usr/src/usr.sbin/freebsd-update/freebsd-update.sh > > Source installation does, however I don't believe a binary upgrade does. > Wouldn't it be possible for him to invoke mergemaster manually though, so that his configuration changes get merged much easier ? This implies having a current version of mergemaster and the new configuration files to compare though... From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 13:42:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2EE11065674 for ; Tue, 28 Dec 2010 13:42:07 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:2:2d29:0:1::]) by mx1.freebsd.org (Postfix) with ESMTP id 5CEEF8FC17 for ; Tue, 28 Dec 2010 13:42:07 +0000 (UTC) Received: from restart.be (avoriaz.tunnel.bel [IPv6:2001:41d0:2:2d29:1:ffff::]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 80808945A for ; Tue, 28 Dec 2010 14:42:04 +0100 (CET) Received: from morzine.restart.bel (morzine.restart.be [IPv6:2001:41d0:2:2d29:1:2::]) (authenticated bits=0) by restart.be (8.14.4/8.14.4) with ESMTP id oBSDg3rc043551 for ; Tue, 28 Dec 2010 14:42:04 +0100 (CET) (envelope-from hlh@restart.be) X-DKIM: Sendmail DKIM Filter v2.8.3 restart.be oBSDg3rc043551 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=restart.be; s=avoriaz; t=1293543724; bh=BDhyQJ/Xp9Ilzg5nrEl0reJbVbzaatIASp4Qclur8dk=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=CXBjyr6VhP7B8Zn3aJF0RiCO0v+MLVMiXjJ9NX95Yh8ipCC10XEr1tg2zFsjzhqY/ FgqVC8DDt8p2N/tM+tudw== X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 restart.be oBSDg3rc043551 DomainKey-Signature: a=rsa-sha1; s=avoriaz; d=restart.be; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:content-type:content-transfer-encoding; b=FweBJsBpxHPvbNoG4hBK/z9zuVFuPH7pOUmvsZNC9+Zn/E7Q5KdPPYS9ULN1+USki atnMO4PV8RYi5CgNepEyQ== Message-ID: <4D19E92B.7050306@restart.be> Date: Tue, 28 Dec 2010 14:42:03 +0100 From: Henri Hennebert Organization: RestartSoft User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101212 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: zfsboot from 8.2RC1 freeze at boot time X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 13:42:07 -0000 Hello and merry Xmas to everybody, I upgrade a remote server from 8.1-RELEASE to 8.2-RC1. This server have one disk: [root@tignes ~]# gpart show => 63 488397105 ada0 MBR (233G) 63 12583809 1 freebsd (6.0G) 12583872 475813296 2 freebsd [active] (227G) => 0 12583809 ada0s1 BSD (6.0G) 0 8388608 1 freebsd-ufs (4.0G) 8388608 4195201 2 freebsd-swap (2.0G) => 0 475813296 ada0s2 BSD (227G) 0 475813296 1 freebsd-zfs (227G) It boot with zfsboot from ada0s2 containing a zfs pool. After upgrading the zfsboot just to be able to upgrade the pool to v15, the server don't boot anymore. It is a remote server, so I reproduce this config under VirtualBox. The boot freeze after zfsboot displaying "-". I grab a old zfsboot from another server running 8.1-STABLE (r213582) which boot fine. I put the zfsboot from r213582 (zpool v15 aware) on ada0s2 and bingo, the server boot normally. Henri From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 15:40:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E80C5106566C for ; Tue, 28 Dec 2010 15:40:46 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id AFDDB8FC1B for ; Tue, 28 Dec 2010 15:40:46 +0000 (UTC) Received: by iyb26 with SMTP id 26so8552468iyb.13 for ; Tue, 28 Dec 2010 07:40:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=zXZQWvlFyqmapLtCN42dAlkEvfih2qNWLB9QDrRMzKk=; b=eqqwti8kyvyp94c2WOTghRVjfgv2WzvJf5SXkcdHXyUqIRE5zPhZiEOkg7PB7QA3un 9gA5dzH4295apg3HJxqjBRx3T6la4vC62NA3MJn9WuQLcNCxVbWtnPPeqi/q3pp/SP3M uNlr7R50XYp1uPMzRayUN30neM2K6YvZNec6Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wc3WRlbZKs8JDAThn4k+Dcx5nJkovvCKUAw8GM2l+RFTnI/ZlGaTTPGJNscpQh7QYB d0gO2a1x4SDZjdcJwN3FduB1PSD4Lby5mlkS028+JUmX9/+TIPX1kFJV9gc+dt53/gvZ rrfRgQ0huWKGlRYsMn7hV+WxFkQdyI41U5m7U= MIME-Version: 1.0 Received: by 10.42.175.4 with SMTP id ay4mr13575671icb.394.1293550845374; Tue, 28 Dec 2010 07:40:45 -0800 (PST) Received: by 10.42.220.70 with HTTP; Tue, 28 Dec 2010 07:40:45 -0800 (PST) In-Reply-To: References: Date: Wed, 29 Dec 2010 02:40:45 +1100 Message-ID: From: Jean-Yves Avenard To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 15:40:47 -0000 Well Today I added the log device: zpool add pool log /dev/ada1s1 (8GB slice on a SSD Intel X25 disk).. then added the cache (32GB) zpool add pool cache /dev/ada1s2 So far so good. zpool status -> all good. Reboot : it hangs booted in single user mode, zpool status: ZFS filesystem version 5 ZFS storage pool version 28 and that's it no more.. Just like before when I thought that removing the log disk had failed. This time no error nothing... just a nasty hang and unusable system again... :( From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:15:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FF62106566B for ; Tue, 28 Dec 2010 16:15:46 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id EB6728FC0C for ; Tue, 28 Dec 2010 16:15:45 +0000 (UTC) Received: by iyb26 with SMTP id 26so8577650iyb.13 for ; Tue, 28 Dec 2010 08:15:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=3VJ+QjofLYfDtQWq5yAwjWn2tuOhIzvJovErh8AKfV8=; b=vKUd5TvAPj8QA+iiLDnpwFK3TVmlu/HXRjssBTjq0kdyJX0T9T8TseVlmYtgkWN2sG Udufgxt5MU3O41JlgLsVA30YjUsTsYLe0GRsREnH1s83L0rNGOKfwgl08OxX2telGdyB 1SWwacBqv4QhewmaTsat80xz+wfyN6ZZswrtI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=CM5a+b0wHR220yhXhyFN/EXcwuzsCWNMnLiE6dk61my6A/xelMK/lIQaMuj15JwGV3 Uq5OSxaNEwFZJ+XDeIjchdtcfPyNYQXFOjAaU6UXHnMdLntxlZyjKqfc4Fr2CNGmBxJs i65/ZjFlbz+qOB4OPrlbyqGr/6/5cXrCxDk8k= MIME-Version: 1.0 Received: by 10.42.175.4 with SMTP id ay4mr13613114icb.394.1293552945207; Tue, 28 Dec 2010 08:15:45 -0800 (PST) Received: by 10.42.220.70 with HTTP; Tue, 28 Dec 2010 08:15:45 -0800 (PST) In-Reply-To: <4D181E51.30401@DataIX.net> References: <4D181E51.30401@DataIX.net> Date: Wed, 29 Dec 2010 03:15:45 +1100 Message-ID: From: Jean-Yves Avenard To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 16:15:46 -0000 Hi On 27 December 2010 16:04, jhell wrote: > 1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1) > 2) Boot into single user mode without opensolaris.ko and zfs.ko loaded > 3) ( mount -w / ) to make sure you can remove and also write new > zpool.cache as needed. > 3) Remove /boot/zfs/zpool.cache > 4) kldload both zfs and opensolaris i.e. ( kldload zfs ) should do the trick > 5) verify that vfs.zfs.recover=1 is set then ( zpool import pool ) > 6) Give it a little bit monitor activity using Ctrl+T to see activity. Ok.. I've got into the same situation again, no idea why this time. I've followed your instructions, and sure enough I could do an import of my pool again. However, wanted to find out what was going on.. So I did: zpool export pool followed by zpool import And guess what ... hanged zpool again.. can't Ctrl-C it, have to reboot.. So here we go again. Rebooted as above. zpool import pool -> ok this time, I decided that maybe that what was screwing things up was the cache. zpool remove pool ada1s2 -> ok zpool status: # zpool status pool: pool state: ONLINE scan: scrub repaired 0 in 18h20m with 0 errors on Tue Dec 28 10:28:05 2010 config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 logs ada1s1 ONLINE 0 0 0 errors: No known data errors # zpool export pool -> ok # zpool import pool -> ok # zpool add pool cache /dev/ada1s2 -> ok # zpool status pool: pool state: ONLINE scan: scrub repaired 0 in 18h20m with 0 errors on Tue Dec 28 10:28:05 2010 config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 logs ada1s1 ONLINE 0 0 0 cache ada1s2 ONLINE 0 0 0 errors: No known data errors # zpool export pool -> ok # zpool import load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.57r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.95r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 32.19r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 32.72r 0.00u 0.03s 0% 2556k load: 0.00 cmd: zpool 405 [spa_namespace_lock] 40.13r 0.00u 0.03s 0% 2556k ah ah ! it's not the separate log that make zpool crash, it's the cache ! Having the cache in prevent from importing the pool again.... rebooting: same deal... can't access the pool any longer ! Hopefully this is enough hint for someone to track done the bug ... From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:37:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FD261065695 for ; Tue, 28 Dec 2010 16:37:43 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id E8E168FC0C for ; Tue, 28 Dec 2010 16:37:42 +0000 (UTC) Received: from core.byshenk.net (localhost [127.0.0.1]) by core.byshenk.net (8.14.4/8.14.4) with ESMTP id oBSG9TPh032195; Tue, 28 Dec 2010 17:09:29 +0100 (CET) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.4/8.14.4/Submit) id oBSG9S9v032194; Tue, 28 Dec 2010 17:09:28 +0100 (CET) (envelope-from byshenknet) Date: Tue, 28 Dec 2010 17:09:28 +0100 From: Greg Byshenk To: freebsd-stable@freebsd.org Message-ID: <20101228160928.GC9465@core.byshenk.net> References: <4D1930F1.9050902@my.gd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D1930F1.9050902@my.gd> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on core.byshenk.net Cc: BlackHeart Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 16:37:43 -0000 On Tue, Dec 28, 2010 at 01:36:01AM +0100, Damien Fleuriot wrote: > On 12/27/10 9:18 PM, Michael BlackHeart wrote: > > I've got trouble with FreeBSD 8 Stable > > First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to > > yesterday revision I don't remember exact number, but I've have this > > problem aobut week or two so it's not so important, also as it doesn't > > work on i386 too. > > > > After installing new kernel I've just build - indeed it always was > > GENERIC for both arch's on clean system - I've got an a kernel painc > > caused by disability to mount root partition because kernel couldn't > > see the drive. By pressing '?' I've sen only acd0 that represents > > CD-ROM. > > > > In debug messages I haven't found anything about ad0 - than hdd was > > identified before new kernel was installed. > > I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is > > working with diabled SATA native mode. > > > > I've not found any info 'bout this error in recent 8.Stable so I don't > > know how to handle this one. > First, I'd advise making use of FreeBSD's nextboot utility to test new > kernels: > http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?nextboot+8 > > Second, I would suggest reading the handbook's excellent section on > upgrading your machine or rebuilding the kernel: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html > > Now, a likely cause of your problem is the installation of a custom > kernel with removed support for whatever your hard disk drive or raid > controller is recognized as. > > Did you reinstall your old, working kernel, or are you actually asking > for help doing just that ? What kind of laptop? For information, I had a similar problem when I updated my laptop (HP Compaq 6910p) to 8.2-PRERELEASE as of 14 December. For some reason, the system was no longer seeing the main hard drive. I solved the problem by setting 'SATA Native Mode' (or some such) in the BIOS, which then led my (SATA) drive to be seen at '/dev/ad8'. After booting from ad8 and modifying my 'fstab', everything works fine. So you might try the same thing. At least change the setting in your BIOS to see if you can see a drive. -greg -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:44:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7A16106566C for ; Tue, 28 Dec 2010 16:44:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B65838FC0A for ; Tue, 28 Dec 2010 16:44:18 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id EC8C846B1A; Tue, 28 Dec 2010 11:44:17 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A2B9D8A009; Tue, 28 Dec 2010 11:44:16 -0500 (EST) From: John Baldwin To: Miroslav Lachman <000.fbsd@quip.cz> Date: Tue, 28 Dec 2010 11:23:53 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20101102; KDE/4.4.5; amd64; ; ) References: <4BCE4D0F.2020807@quip.cz> <201012130824.33968.jhb@freebsd.org> <4D15D8DD.9010900@quip.cz> In-Reply-To: <4D15D8DD.9010900@quip.cz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012281123.53669.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 28 Dec 2010 11:44:16 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Garrett Cooper , freebsd-stable@freebsd.org Subject: Re: /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 16:44:19 -0000 On Saturday, December 25, 2010 6:43:25 am Miroslav Lachman wrote: > John Baldwin wrote: > > On Saturday, December 11, 2010 11:51:41 am Miroslav Lachman wrote: > >> Miroslav Lachman wrote: > >>> Garrett Cooper wrote: > >>>> 2010/4/20 Miroslav Lachman<000.fbsd@quip.cz>: > >>>>> I have large storage partition (/vol0) mounted as noexec and nosuid. > >>>>> Then > >>>>> one directory from this partition is mounted by nullfs as "exec and > >>>>> suid" so > >>>>> anything on it can be executed. > >>>>> > >>>>> The directory contains full installation of jail. Jail is running > >>>>> fine, but > >>>>> some ports (PHP for example) cannot be compiled inside the jail with > >>>>> message: > >>>>> > >>>>> /libexec/ld-elf.so.1: Cannot execute objects on / > >>>>> > >>>>> The same apply to executing of apxs > >>>>> > >>>>> root@rainnew ~/# /usr/local/sbin/apxs -q MPM_NAME > >>>>> /libexec/ld-elf.so.1: Cannot execute objects on / > >>>>> > >>>>> apxs:Error: Sorry, no shared object support for Apache. > >>>>> apxs:Error: available under your platform. Make sure. > >>>>> apxs:Error: the Apache module mod_so is compiled into. > >>>>> apxs:Error: your server binary '/usr/local/sbin/httpd'.. > >>>>> > >>>>> (it should return "prefork") > >>>>> > >>>>> So I think there is some bug in checking the mountpoint options, > >>>>> where the > >>>>> check is made on "parent" of the nullfs instead of the nullfs target > >>>>> mountpoint. > >>>>> > >>>>> It is on 6.4-RELEASE i386 GENERIC. I did not test it on another release. > >>>>> > >>>>> This is list of related mount points: > >>>>> > >>>>> /dev/mirror/gm0s2d on /vol0 (ufs, local, noexec, nosuid, soft-updates) > >>>>> /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local) > >>>>> /usr/ports on /vol0/jail/rain_new/usr/ports (nullfs, local) > >>>>> devfs on /vol0/jail/rain_new/dev (devfs, local) > >>>>> > >>>>> If I changed /vol0 options to (ufs, local, soft-updates) the above > >>>>> error is > >>>>> gone and apxs / compilation works fine. > >>>>> > >>>>> Can somebody look at this problem? > >>>> > >>>> Can you please provide output from ktrace / truss for the issue? > >>> > >>> I did > >>> # ktrace /usr/local/sbin/apxs -q MPM_NAME > >>> > >>> The output is here http://freebsd.quip.cz/ld-elf/ktrace.out > >>> > >>> Let me know if you need something else. > >>> > >>> Thank you for your interest! > >> > >> The problem is still there in FreeBSD 8.1-RELEASE amd64 GENERIC (and in > >> 7.x). > >> > >> Can somebody say if this is a bug or an expected "feature"? > > > > I think this is the expected behavior as nullfs is simply re-exposing /vol0 > > and it shouldn't be able to create a more privileged mount than the underlying > > mount I think (e.g. a read/write nullfs mount of a read-only filesystem would > > not make the underlying files read/write). It can be used to provide less > > privilege (e.g. a readonly nullfs mount of a read/write filesystem does not > > allow writes via the nullfs layer). > > > > That said, I'm not sure exactly where the permission check is failing. > > execve() only checks MNT_NOEXEC on the "upper" vnode's mountpoint (i.e. the > > nullfs mountpoint) and the VOP_ACCESS(.., V_EXEC) check does not look at > > MNT_NOEXEC either. > > > > I do think there might be bugs in that a nullfs mount that specifies noexec or > > nosuid might not enforce the noexec or nosuid bits if the underlying mount > > point does not have them set (from what I can see). > > Thank you for your explanation. Then it is strange, that there is bug, > that allows execution on originally non executable mountpoint. > It should be mentioned in the bugs section of the mount_nullfs man page. > > It would be useful, if 'mount' output shows inherited options for nullfs. > > If parent is: > /dev/mirror/gm0s2d on /vol0 (ufs, local, noexec, nosuid, soft-updates) > > Then nullfs line will be: > /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local, noexec, > nosuid) > > instead of just > /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local) > > > Then I can understand what is expected behavior, but our current state > is half working, if I can execute scripts and binaries, run jail on it, > but can't execute "apxs -q MPM_NAME" and few others. Hmm, so I was a bit mistaken. The kernel is not failing to exec the binary. Instead, rtld is reporting the error here: static Obj_Entry * do_load_object(int fd, const char *name, char *path, struct stat *sbp, int flags) { Obj_Entry *obj; struct statfs fs; /* * but first, make sure that environment variables haven't been * used to circumvent the noexec flag on a filesystem. */ if (dangerous_ld_env) { if (fstatfs(fd, &fs) != 0) { _rtld_error("Cannot fstatfs \"%s\"", path); return NULL; } if (fs.f_flags & MNT_NOEXEC) { _rtld_error("Cannot execute objects on %s\n", fs.f_mntonname); return NULL; } } I wonder if the fstatfs is falling down to the original mount rather than being caught by nullfs. Hmm, nullfs' statfs method returns the flags for the underlying mount, not the flags for the nullfs mount. This is possibly broken, but it is the behavior nullfs has always had and the behavior it still has on other BSDs. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:44:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06B8D1065714 for ; Tue, 28 Dec 2010 16:44:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CC66B8FC1B for ; Tue, 28 Dec 2010 16:44:22 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 85EC946B1A; Tue, 28 Dec 2010 11:44:22 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A25DC8A009; Tue, 28 Dec 2010 11:44:21 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 28 Dec 2010 11:42:32 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20101102; KDE/4.4.5; amd64; ; ) References: <4D11F1F5.7050902@quip.cz> <201012220957.26854.jhb@freebsd.org> <20101224084716.GM94020@over-yonder.net> In-Reply-To: <20101224084716.GM94020@over-yonder.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012281142.32654.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 28 Dec 2010 11:44:21 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Miroslav Lachman <000.fbsd@quip.cz>, "Matthew D. Fuller" Subject: Re: MCA messages after upgrade to 8.2-BEAT1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 16:44:23 -0000 On Friday, December 24, 2010 3:47:16 am Matthew D. Fuller wrote: > On Wed, Dec 22, 2010 at 09:57:26AM -0500 I heard the voice of > John Baldwin, and lo! it spake thus: > > > > You are getting corrected ECC errors in your RAM. > > Actually, don't > > > CPU 0 0 data cache > > ADDR 236493c0 > > Data cache ECC error (syndrome 1c) > > > CPU 0 1 instruction cache > > ADDR 2a1c9440 > > Instruction cache ECC error > > > CPU 0 2 bus unit > > L2 cache ECC error > > > CPU 1 0 data cache > > ADDR 23649640 > > Data cache ECC error (syndrome 1c) > > > CPU 1 1 instruction cache > > ADDR 2a1c9440 > > Instruction cache ECC error > > > CPU 1 2 bus unit > > L2 cache ECC error > > suggest CPU cache, not RAM? > > (that's actually a question; I don't know, but that's what a naive > reading suggests...) Hmm, I don't know for certain. My interpretation is that the CPU errors were just secondary errors from a memory error like this one that was in the middle of his reported errors. It was also only reported on CPU 0 and not CPU 1: STATUS d000400000000863 MCGSTATUS 0 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 67 HARDWARE ERROR. This is NOT a software problem! Please contact your hardware vendor CPU 0 4 northbridge MISC e00d0fff00000000 ADDR 2cac9678 Northbridge RAM ECC error ECC syndrome = 1c bit33 = err cpu1 bit46 = corrected ecc error bit59 = misc error valid bit62 = error overflow (multiple errors) bus error 'local node origin, request didn't time out generic read mem transaction memory access, level generic' On Intel systems (which I am much more familiar with as far as machine checks go), corrected ECC errors did not result in additional events in the CPU caches themselves, but I don't know if AMD is different in this regard. It could be that both CPUs and a DIMM are failing, but replacing a DIMM is cheaper and simpler and you can always replace the CPUs later if CPU errors continue. Of course, I can't tell you which DIMM to replace from these messages, but in this case since they are so easily reproducible, you could probably swap them out one at a time to test. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:50:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD38D1065670 for ; Tue, 28 Dec 2010 16:50:25 +0000 (UTC) (envelope-from troy@twisted.net) Received: from oz.twisted.net (oz.twisted.net [69.211.34.241]) by mx1.freebsd.org (Postfix) with ESMTP id 3B16C8FC08 for ; Tue, 28 Dec 2010 16:50:21 +0000 (UTC) Received: from oz.twisted.net (localhost [127.0.0.1]) by oz.twisted.net (Postfix) with ESMTP id 273FAFECC43; Tue, 28 Dec 2010 10:50:11 -0600 (CST) X-Virus-Scanned: amavisd-new at example.com Received: from oz.twisted.net ([127.0.0.1]) by oz.twisted.net (oz.twisted.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9z+YE0cvHBw; Tue, 28 Dec 2010 10:49:55 -0600 (CST) Received: from [172.16.0.5] (sindrome.twisted.net [172.16.0.5]) by oz.twisted.net (Postfix) with ESMTP id BB324FCFAB9; Tue, 28 Dec 2010 10:49:44 -0600 (CST) Message-ID: <4D1A14D6.5020303@twisted.net> Date: Tue, 28 Dec 2010 10:48:22 -0600 From: Troy User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Damien Fleuriot References: <4D191642.4050908@twisted.net> <4D192E4B.9020701@my.gd> <4D1937C8.80609@twisted.net> <4D19B83E.2090308@my.gd> In-Reply-To: <4D19B83E.2090308@my.gd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: troy@twisted.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 16:50:25 -0000 The generic kernel worked. What's the easiest way to try and figure out which line is causing the hang in my custom kernel? When it hangs it gives me nothing other than what I put in the initial email. I've been using this custom kernel config for years on this server. On 12/28/2010 4:13 AM, Damien Fleuriot wrote: > Well, I would suggest you try this: > > > cd /usr/src > > make buildkernel KERNCONF=GENERIC > make installkernel KERNCONF=GENERIC > > cd /boot > mv kernel test > mv kernel.old kernel > nextboot -k test > > > Then, you can reboot. > > This will ensure you can boot a stock kernel just fine. > > If you can, obviously there is something wrong with your custom kernel > and you should start from a fresh GENERIC kernel and remove devices and > drivers little by little. > > > On 12/28/10 2:05 AM, Troy wrote: >> Sorry. >> >> I am on the RELENG_8 tree and I believe it was building 8.2pre. I did >> the build about 4 days ago. I am building a custom kernel. Yes I >> definitely built the world before the kernel and it worked. I did not >> use -J anything. There is no boot message, it just hangs with what I >> wrote below. Below is the kernel config I'm using. >> >> machine amd64 >> cpu HAMMER >> ident servername-removed >> >> # To statically compile in device wiring instead of /boot/device.hints >> #hints "GENERIC.hints" # Default places to look for >> devices. >> >> makeoptions DEBUG=-g # Build kernel with gdb(1) debug >> symbols >> >> options SCHED_ULE # ULE scheduler >> options PREEMPTION # Enable kernel thread preemption >> options INET # InterNETworking >> options SCTP # Stream Control Transmission >> Protocol >> options FFS # Berkeley Fast Filesystem >> options SOFTUPDATES # Enable FFS soft updates support >> options UFS_ACL # Support for access control lists >> options UFS_DIRHASH # Improve performance on big >> directories >> options UFS_GJOURNAL # Enable gjournal-based UFS >> journaling >> options MD_ROOT # MD is a potential root device >> options NFSCLIENT # Network Filesystem Client >> options NFSSERVER # Network Filesystem Server >> options NFSLOCKD # Network Lock Manager >> options NFS_ROOT # NFS usable as /, requires >> NFSCLIENT >> options NTFS # NT File System >> options MSDOSFS # MSDOS Filesystem >> options CD9660 # ISO 9660 Filesystem >> options PROCFS # Process filesystem (requires >> PSEUDOFS) >> options PSEUDOFS # Pseudo-filesystem framework >> options GEOM_PART_GPT # GUID Partition Tables. >> options GEOM_LABEL # Provides labelization >> options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) >> options COMPAT_IA32 # Compatible with i386 binaries >> options COMPAT_43 # Needed by COMPAT_LINUX32 >> options COMPAT_FREEBSD4 # Compatible with FreeBSD4 >> options COMPAT_FREEBSD5 # Compatible with FreeBSD5 >> options COMPAT_FREEBSD6 # Compatible with FreeBSD6 >> options COMPAT_FREEBSD7 # Compatible with FreeBSD7 >> options COMPAT_LINUX32 # Compatible with i386 linux >> binaries >> options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI >> options KTRACE # ktrace(1) support >> options STACK # stack(9) support >> options SYSVSHM # SYSV-style shared memory >> options SYSVMSG # SYSV-style message queues >> options SYSVSEM # SYSV-style semaphores >> options P1003_1B_SEMAPHORES # POSIX-style semaphores >> options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time >> extensions >> options PRINTF_BUFR_SIZE=128 # Prevent printf output being >> interspersed. >> options KBD_INSTALL_CDEV # install a CDEV entry in /dev >> options HWPMC_HOOKS # Necessary kernel hooks for >> hwpmc(4) >> options AUDIT # Security event auditing >> options MAC # TrustedBSD MAC Framework >> options FLOWTABLE # per-cpu routing cache >> options INCLUDE_CONFIG_FILE # Include this file in kernel >> options IPSTEALTH >> options INVARIANTS >> options INVARIANT_SUPPORT >> >> # Make an SMP-capable kernel by default >> options SMP # Symmetric MultiProcessor Kernel >> >> # CPU frequency control >> device cpufreq >> >> # For SMBFS - mount_smbfs to work by users >> options SMBFS # SMB/CIFS filesystem >> options NETSMB # SMB/CIFS requester >> options LIBMCHAIN # MBUF management library >> options LIBICONV # Kernel side iconv library >> >> # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) >> device atpic # 8259A compatability >> >> # Linux 32-bit ABI support >> options LINPROCFS # Cannot be a module yet. >> >> # Bus support. >> device acpi >> device pci >> >> # Floppy drives >> device fdc >> >> # ATA and ATAPI devices >> device ata >> device atadisk # ATA disk drives >> device atapicd # ATAPI CDROM drives >> device atapifd # ATAPI floppy drives >> options ATA_STATIC_ID # Static device numbering >> >> # SCSI Controllers >> device ahc # AHA2940 and onboard AIC7xxx devices >> options AHC_REG_PRETTY_PRINT # Print register bitfields in debug >> # output. Adds ~128k to driver. >> device ahd # AHA39320/29320 and onboard AIC79xx >> devices >> options AHD_REG_PRETTY_PRINT # Print register bitfields in debug >> # output. Adds ~215k to driver. >> device amd # AMD 53C974 (Tekram DC-390(T)) >> device isp # Qlogic family >> device mpt # LSI-Logic MPT-Fusion >> device sym # NCR/Symbios Logic (newer chipsets + >> those of `ncr') >> device trm # Tekram DC395U/UW/F DC315U adapters >> >> device adv # Advansys SCSI adapters >> device adw # Advansys wide SCSI adapters >> device aic # Adaptec 15[012]x SCSI adapters, >> AIC-6[23]60. >> device bt # Buslogic/Mylex MultiMaster >> SCSI adapters >> >> >> # SCSI peripherals >> device scbus # SCSI bus (required for SCSI) >> device ch # SCSI media changers >> device da # Direct Access (disks) >> device sa # Sequential Access (tape etc) >> device cd # CD >> device pass # Passthrough device (direct SCSI access) >> device ses # SCSI Environmental Services (and SAF-TE) >> >> # RAID controllers interfaced to the SCSI subsystem >> device twa # 3ware 9000 series PATA/SATA RAID >> >> # atkbdc0 controls both the keyboard and the PS/2 mouse >> device atkbdc # AT keyboard controller >> device atkbd # AT keyboard >> device kbdmux # keyboard multiplexer >> device vga # VGA video card driver >> device splash # Splash screen and screen saver support >> options VGA_WIDTH90 >> options SC_PIXEL_MODE >> >> # syscons is the default console driver, resembling an SCO console >> device sc >> device agp # support several AGP chipsets >> >> # Serial (COM) ports >> device uart # Generic UART driver >> >> # Parallel port >> device ppc >> device ppbus # Parallel port bus (required) >> device lpt # Printer >> device ppi # Parallel port interface device >> >> >> # PCI Ethernet NICs that use the common MII bus controller code. >> # NOTE: Be sure to keep the 'device miibus' line in order to use these >> NICs! >> device miibus # MII bus support >> device bge # Broadcom BCM570xx Gigabit Ethernet >> >> # Pseudo devices. >> device loop # Network loopback >> device random # Entropy device >> device ether # Ethernet support >> device vlan # 802.1Q VLAN support >> device snp # Snoop support >> device tun # Packet tunnel. >> device pty # Pseudo-ttys (telnet etc) >> device md # Memory "disks" >> device firmware # firmware assist module >> >> # The `bpf' device enables the Berkeley Packet Filter. >> # Be aware of the administrative consequences of enabling this! >> # Note that 'bpf' is required for DHCP. >> device bpf # Berkeley packet filter >> >> # USB support >> device uhci # UHCI PCI->USB interface >> device ohci # OHCI PCI->USB interface >> device ehci # EHCI PCI->USB interface (USB 2.0) >> device usb # USB Bus (required) >> device uhid # "Human Interface Devices" >> device ukbd # Keyboard >> device ulpt # Printer >> device umass # Disks/Mass storage - Requires scbus >> and da >> device ums # Mouse >> >> # USB Ethernet, requires miibus >> device aue # ADMtek USB Ethernet >> device axe # ASIX Electronics USB Ethernet >> device cdce # Generic USB over Ethernet >> device cue # CATC USB Ethernet >> device kue # Kawasaki LSI USB Ethernet >> device rue # RealTek RTL8150 USB Ethernet >> device udav # Davicom DM9601E USB >> >> >> >> >> On 12/27/2010 6:24 PM, Damien Fleuriot wrote: >>> Hey Troy, >>> >>> >>> I can't speak for the rest of the list but I think we're missing a bit >>> of information here. >>> >>> What are you trying to build and boot, 8.1, 8.2pre ? >>> >>> Are you building a GENERIC kernel ? I notice you're currently using a >>> custom one. >>> >>> If you're not, I would suggest trying GENERIC first. >>> >>> You might want to post your whole boot message if it can be recovered. >>> >>> >>> >>> Also and in case you don't know, you may quickly test your kernel like >>> so: >>> nextboot -k yourkernelhere >>> >>> Next reboot, the host will try yourkernelhere, and on the reboot after >>> that, revert to your regular kernel. >>> >>> >>> Other than that, quick things to check: >>> >>> 1/ built world before kernel >>> >>> 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can >>> do for the world) >>> >>> 3/ tracked the *correct* version in the cvsup file (I've had this case >>> where I was running fbsd8 zfs boot, and was building a 7.x kernel by >>> mistake cause I was tracking releng7 -.- ) >>> >>> 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or 8.2, >>> whichever you're tracking >>> >>> >>> >>> On 12/27/10 11:42 PM, Troy wrote: >>>> I recently rebuilt the world and kernel and everything built just fine >>>> and when I went to boot into the new kernel, it hangs. I had to revert >>>> back to my previous kernel. >>>> >>>> Currently I'm running: >>>> FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 >>>> 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server >>>> amd64 >>>> >>>> When it hangs upon boot-up it simply stops here. I don't know how I can >>>> figure out what is causing the root of the hang. I'd really like to get >>>> this machine upgraded. >>>> >>>> Ppc0 cannot reserve I/O port range >>>> PowerNow0 on cpu0 >>>> Device_attach: PowerNow0 attach return 6 >>>> PowerNow0 on cpu1 >>>> Device_attach: PowerNow0 attach return 6 >>>> PowerNow1 on cpu0 >>>> Device_attach: PowerNow0 attach return 6 >>>> PowerNow1 on cpu1 >>>> Device_attach: PowerNow0 attach return 6 >>>> Time Counters Tick every 1.000 msec >>>> <<>> >>>> >>>> Any help is greatly appreciated. >>>> >>>> -Troy >>>> >>>> _______________________________________________ >>>> 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" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 16:58:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 314EC106566B for ; Tue, 28 Dec 2010 16:58:19 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id EB5BC8FC15 for ; Tue, 28 Dec 2010 16:58:18 +0000 (UTC) Received: by iyb26 with SMTP id 26so8607403iyb.13 for ; Tue, 28 Dec 2010 08:58:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3/H06PD5/dt6npuZA06Q0NKLZnddtd8uz1wtiBpY2sg=; b=XgMlIgDzH6RgIFy4Lfa65xaCf6KmAGmj9mDQ+HZJiJjIrHyWovxSgZ1ciU2LetclIa 4fI6YwWanr5qdaGw3IPx+Dx0w2s8gMLAVmGhwdump399XUg073i+74X6U3PpWeersqhm WnZh6v3DQ1D6hzROM4dA12dMPPsfsYdbRcG+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=K6dXXdZAD2SMIfldZXq6seepc/AtHmVDwBRRCqo5rRmaT6AwHayYm4XjzWNqT/B5st QZzl/2Jz2Vya/3kT64oYLN91/5L6V0SzJQNSIPOHUxB7RqcsfS15w4+Ts0EpHJuXtJtN KfIRUpYuAVw5/VVPYkXt2iSef6Ydjpi0a0Bf4= MIME-Version: 1.0 Received: by 10.42.221.71 with SMTP id ib7mr13648736icb.528.1293555498374; Tue, 28 Dec 2010 08:58:18 -0800 (PST) Received: by 10.42.220.70 with HTTP; Tue, 28 Dec 2010 08:58:18 -0800 (PST) In-Reply-To: References: Date: Wed, 29 Dec 2010 03:58:18 +1100 Message-ID: From: Jean-Yves Avenard To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 16:58:19 -0000 On 28 December 2010 08:56, Freddie Cash wrote: > Is that a typo, or the actual command you used? =A0You have an extra "s" > in there. =A0Should be "log" and not "logs". =A0However, I don't think > that command is correct either. > > I believe you want to use the "detach" command, not "remove". > > # zpool detach pool label/zil well, I tried the detach command: server4# zpool detach pool ada1s1 cannot detach ada1s1: only applicable to mirror and replacing vdevs server4# zpool remove pool ada1s1 server4# so you need to use remove, and adding log (or cache) makes no difference whatsoever.. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 17:39:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F27E3106564A for ; Tue, 28 Dec 2010 17:39:31 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B65918FC17 for ; Tue, 28 Dec 2010 17:39:31 +0000 (UTC) Received: by iwn39 with SMTP id 39so9653738iwn.13 for ; Tue, 28 Dec 2010 09:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=t8xpkEQq3SFV6CX4iH92enObGJ2IarUzLxf/qT956aM=; b=BX5liG5RpQPtoQjrXO/Y9r5lwtQRzNZd1Q/rlbEu1uvMPHoP2WNL/RwoaSHyWfICjt BGwsWuWeSBrUzMpxy7RCAHzq0qWd/mnbRdF3yPguR+7kojuRBh3XHnFwWCvtuabik4Hz v5HYKAkjA5yr61YqOGJFwAJSYjLateMUi1OvY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gzPhCFUajd6epQCi63KAFXZ3MtLzwMSmjRQZcPDhyH3wEFAWU/erJer7jUNXbnr8y7 JbmHin/1NN/W70IylKCB5rx3l5eCG7+lABTU8IKWN4Z223Lzu34GoByFxbPSyxNxvvvC heCdPH4TpkP/ZOQlp7xxSGG8nRT1Pzxh1LfRw= MIME-Version: 1.0 Received: by 10.42.178.9 with SMTP id bk9mr13764778icb.126.1293557971103; Tue, 28 Dec 2010 09:39:31 -0800 (PST) Received: by 10.42.220.70 with HTTP; Tue, 28 Dec 2010 09:39:31 -0800 (PST) In-Reply-To: References: <4D181E51.30401@DataIX.net> Date: Wed, 29 Dec 2010 04:39:31 +1100 Message-ID: From: Jean-Yves Avenard To: jhell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 17:39:32 -0000 On 29 December 2010 03:15, Jean-Yves Avenard wrote: > # zpool import > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 16.57r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 16.95r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 32.19r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 32.72r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 40.13r 0.00u 0.03s 0% 2= 556k > > ah ah ! > it's not the separate log that make zpool crash, it's the cache ! > > Having the cache in prevent from importing the pool again.... > > rebooting: same deal... can't access the pool any longer ! > > Hopefully this is enough hint for someone to track done the bug ... > More details as I was crazy enough to try various things. The problem of zpool being stuck in spa_namespace_lock, only occurs if you are using both the cache and the log at the same time. Use one or the other : then there's no issue But the instant you add both log and cache to the pool, it becomes unusable= . Now, I haven't tried using cache and log from a different disk. The motherboard on the server has 8 SATA ports, and I have no free port to add another disk. So my only option to have both a log and cache device in my zfs pool, is to use two slices on the same disk. Hope this helps.. Jean-Yves From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 17:58:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72B66106566B for ; Tue, 28 Dec 2010 17:58:42 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id F17F48FC12 for ; Tue, 28 Dec 2010 17:58:39 +0000 (UTC) Received: by wyf19 with SMTP id 19so9381493wyf.13 for ; Tue, 28 Dec 2010 09:58:39 -0800 (PST) Received: by 10.227.198.203 with SMTP id ep11mr8164845wbb.221.1293559118851; Tue, 28 Dec 2010 09:58:38 -0800 (PST) Received: from dfleuriot.local ([83.167.62.196]) by mx.google.com with ESMTPS id f35sm9469426wbf.20.2010.12.28.09.58.37 (version=SSLv3 cipher=RC4-MD5); Tue, 28 Dec 2010 09:58:38 -0800 (PST) Message-ID: <4D1A254C.5050100@my.gd> Date: Tue, 28 Dec 2010 18:58:36 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: troy@twisted.net References: <4D191642.4050908@twisted.net> <4D192E4B.9020701@my.gd> <4D1937C8.80609@twisted.net> <4D19B83E.2090308@my.gd> <4D1A14D6.5020303@twisted.net> In-Reply-To: <4D1A14D6.5020303@twisted.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 17:58:42 -0000 On 12/28/10 5:48 PM, Troy wrote: > The generic kernel worked. What's the easiest way to try and figure out > which line is causing the hang in my custom kernel? When it hangs it > gives me nothing other than what I put in the initial email. I've been > using this custom kernel config for years on this server. > > First, remove the device drivers which you aren't using (ISA NICs, NICs you don't use, SCSI if you use SATA, firewire...) Get this purified kernel working, then start adding your custom options little by little. I'm afraid there's no magic way of doing it that I know of :) By the way I am unsure what your whole bit about smbfs is about. Want users to be able to call mount_smbfs ? I would sooner give them sudo privileges for this very specific command, than bother hacking and patching the kernel in uncertain ways. I would also remove unnecessary SCSI support as well as mass storage USB, USB printer, USB NICs... Just get shot of everything you don't use to be honest ;) > > On 12/28/2010 4:13 AM, Damien Fleuriot wrote: >> Well, I would suggest you try this: >> >> >> cd /usr/src >> >> make buildkernel KERNCONF=GENERIC >> make installkernel KERNCONF=GENERIC >> >> cd /boot >> mv kernel test >> mv kernel.old kernel >> nextboot -k test >> >> >> Then, you can reboot. >> >> This will ensure you can boot a stock kernel just fine. >> >> If you can, obviously there is something wrong with your custom kernel >> and you should start from a fresh GENERIC kernel and remove devices and >> drivers little by little. >> >> >> On 12/28/10 2:05 AM, Troy wrote: >>> Sorry. >>> >>> I am on the RELENG_8 tree and I believe it was building 8.2pre. I did >>> the build about 4 days ago. I am building a custom kernel. Yes I >>> definitely built the world before the kernel and it worked. I did not >>> use -J anything. There is no boot message, it just hangs with what I >>> wrote below. Below is the kernel config I'm using. >>> >>> machine amd64 >>> cpu HAMMER >>> ident servername-removed >>> >>> # To statically compile in device wiring instead of /boot/device.hints >>> #hints "GENERIC.hints" # Default places to look for >>> devices. >>> >>> makeoptions DEBUG=-g # Build kernel with gdb(1) debug >>> symbols >>> >>> options SCHED_ULE # ULE scheduler >>> options PREEMPTION # Enable kernel thread >>> preemption >>> options INET # InterNETworking >>> options SCTP # Stream Control Transmission >>> Protocol >>> options FFS # Berkeley Fast Filesystem >>> options SOFTUPDATES # Enable FFS soft updates >>> support >>> options UFS_ACL # Support for access control >>> lists >>> options UFS_DIRHASH # Improve performance on big >>> directories >>> options UFS_GJOURNAL # Enable gjournal-based UFS >>> journaling >>> options MD_ROOT # MD is a potential root device >>> options NFSCLIENT # Network Filesystem Client >>> options NFSSERVER # Network Filesystem Server >>> options NFSLOCKD # Network Lock Manager >>> options NFS_ROOT # NFS usable as /, requires >>> NFSCLIENT >>> options NTFS # NT File System >>> options MSDOSFS # MSDOS Filesystem >>> options CD9660 # ISO 9660 Filesystem >>> options PROCFS # Process filesystem (requires >>> PSEUDOFS) >>> options PSEUDOFS # Pseudo-filesystem framework >>> options GEOM_PART_GPT # GUID Partition Tables. >>> options GEOM_LABEL # Provides labelization >>> options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) >>> options COMPAT_IA32 # Compatible with i386 binaries >>> options COMPAT_43 # Needed by COMPAT_LINUX32 >>> options COMPAT_FREEBSD4 # Compatible with FreeBSD4 >>> options COMPAT_FREEBSD5 # Compatible with FreeBSD5 >>> options COMPAT_FREEBSD6 # Compatible with FreeBSD6 >>> options COMPAT_FREEBSD7 # Compatible with FreeBSD7 >>> options COMPAT_LINUX32 # Compatible with i386 linux >>> binaries >>> options SCSI_DELAY=5000 # Delay (in ms) before >>> probing SCSI >>> options KTRACE # ktrace(1) support >>> options STACK # stack(9) support >>> options SYSVSHM # SYSV-style shared memory >>> options SYSVMSG # SYSV-style message queues >>> options SYSVSEM # SYSV-style semaphores >>> options P1003_1B_SEMAPHORES # POSIX-style semaphores >>> options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time >>> extensions >>> options PRINTF_BUFR_SIZE=128 # Prevent printf output being >>> interspersed. >>> options KBD_INSTALL_CDEV # install a CDEV entry in /dev >>> options HWPMC_HOOKS # Necessary kernel hooks for >>> hwpmc(4) >>> options AUDIT # Security event auditing >>> options MAC # TrustedBSD MAC Framework >>> options FLOWTABLE # per-cpu routing cache >>> options INCLUDE_CONFIG_FILE # Include this file in kernel >>> options IPSTEALTH >>> options INVARIANTS >>> options INVARIANT_SUPPORT >>> >>> # Make an SMP-capable kernel by default >>> options SMP # Symmetric MultiProcessor >>> Kernel >>> >>> # CPU frequency control >>> device cpufreq >>> >>> # For SMBFS - mount_smbfs to work by users >>> options SMBFS # SMB/CIFS filesystem >>> options NETSMB # SMB/CIFS requester >>> options LIBMCHAIN # MBUF management library >>> options LIBICONV # Kernel side iconv library >>> >>> # Workarounds for some known-to-be-broken chipsets (nVidia >>> nForce3-Pro150) >>> device atpic # 8259A compatability >>> >>> # Linux 32-bit ABI support >>> options LINPROCFS # Cannot be a module yet. >>> >>> # Bus support. >>> device acpi >>> device pci >>> >>> # Floppy drives >>> device fdc >>> >>> # ATA and ATAPI devices >>> device ata >>> device atadisk # ATA disk drives >>> device atapicd # ATAPI CDROM drives >>> device atapifd # ATAPI floppy drives >>> options ATA_STATIC_ID # Static device numbering >>> >>> # SCSI Controllers >>> device ahc # AHA2940 and onboard AIC7xxx devices >>> options AHC_REG_PRETTY_PRINT # Print register bitfields in >>> debug >>> # output. Adds ~128k to >>> driver. >>> device ahd # AHA39320/29320 and onboard AIC79xx >>> devices >>> options AHD_REG_PRETTY_PRINT # Print register bitfields in >>> debug >>> # output. Adds ~215k to >>> driver. >>> device amd # AMD 53C974 (Tekram DC-390(T)) >>> device isp # Qlogic family >>> device mpt # LSI-Logic MPT-Fusion >>> device sym # NCR/Symbios Logic (newer chipsets + >>> those of `ncr') >>> device trm # Tekram DC395U/UW/F DC315U adapters >>> >>> device adv # Advansys SCSI adapters >>> device adw # Advansys wide SCSI adapters >>> device aic # Adaptec 15[012]x SCSI adapters, >>> AIC-6[23]60. >>> device bt # Buslogic/Mylex MultiMaster >>> SCSI adapters >>> >>> >>> # SCSI peripherals >>> device scbus # SCSI bus (required for SCSI) >>> device ch # SCSI media changers >>> device da # Direct Access (disks) >>> device sa # Sequential Access (tape etc) >>> device cd # CD >>> device pass # Passthrough device (direct SCSI >>> access) >>> device ses # SCSI Environmental Services (and >>> SAF-TE) >>> >>> # RAID controllers interfaced to the SCSI subsystem >>> device twa # 3ware 9000 series PATA/SATA RAID >>> >>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>> device atkbdc # AT keyboard controller >>> device atkbd # AT keyboard >>> device kbdmux # keyboard multiplexer >>> device vga # VGA video card driver >>> device splash # Splash screen and screen saver support >>> options VGA_WIDTH90 >>> options SC_PIXEL_MODE >>> >>> # syscons is the default console driver, resembling an SCO console >>> device sc >>> device agp # support several AGP chipsets >>> >>> # Serial (COM) ports >>> device uart # Generic UART driver >>> >>> # Parallel port >>> device ppc >>> device ppbus # Parallel port bus (required) >>> device lpt # Printer >>> device ppi # Parallel port interface device >>> >>> >>> # PCI Ethernet NICs that use the common MII bus controller code. >>> # NOTE: Be sure to keep the 'device miibus' line in order to use these >>> NICs! >>> device miibus # MII bus support >>> device bge # Broadcom BCM570xx Gigabit Ethernet >>> >>> # Pseudo devices. >>> device loop # Network loopback >>> device random # Entropy device >>> device ether # Ethernet support >>> device vlan # 802.1Q VLAN support >>> device snp # Snoop support >>> device tun # Packet tunnel. >>> device pty # Pseudo-ttys (telnet etc) >>> device md # Memory "disks" >>> device firmware # firmware assist module >>> >>> # The `bpf' device enables the Berkeley Packet Filter. >>> # Be aware of the administrative consequences of enabling this! >>> # Note that 'bpf' is required for DHCP. >>> device bpf # Berkeley packet filter >>> >>> # USB support >>> device uhci # UHCI PCI->USB interface >>> device ohci # OHCI PCI->USB interface >>> device ehci # EHCI PCI->USB interface (USB 2.0) >>> device usb # USB Bus (required) >>> device uhid # "Human Interface Devices" >>> device ukbd # Keyboard >>> device ulpt # Printer >>> device umass # Disks/Mass storage - Requires scbus >>> and da >>> device ums # Mouse >>> >>> # USB Ethernet, requires miibus >>> device aue # ADMtek USB Ethernet >>> device axe # ASIX Electronics USB Ethernet >>> device cdce # Generic USB over Ethernet >>> device cue # CATC USB Ethernet >>> device kue # Kawasaki LSI USB Ethernet >>> device rue # RealTek RTL8150 USB Ethernet >>> device udav # Davicom DM9601E USB >>> >>> >>> >>> >>> On 12/27/2010 6:24 PM, Damien Fleuriot wrote: >>>> Hey Troy, >>>> >>>> >>>> I can't speak for the rest of the list but I think we're missing a bit >>>> of information here. >>>> >>>> What are you trying to build and boot, 8.1, 8.2pre ? >>>> >>>> Are you building a GENERIC kernel ? I notice you're currently using a >>>> custom one. >>>> >>>> If you're not, I would suggest trying GENERIC first. >>>> >>>> You might want to post your whole boot message if it can be recovered. >>>> >>>> >>>> >>>> Also and in case you don't know, you may quickly test your kernel like >>>> so: >>>> nextboot -k yourkernelhere >>>> >>>> Next reboot, the host will try yourkernelhere, and on the reboot after >>>> that, revert to your regular kernel. >>>> >>>> >>>> Other than that, quick things to check: >>>> >>>> 1/ built world before kernel >>>> >>>> 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can >>>> do for the world) >>>> >>>> 3/ tracked the *correct* version in the cvsup file (I've had this case >>>> where I was running fbsd8 zfs boot, and was building a 7.x kernel by >>>> mistake cause I was tracking releng7 -.- ) >>>> >>>> 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or >>>> 8.2, >>>> whichever you're tracking >>>> >>>> >>>> >>>> On 12/27/10 11:42 PM, Troy wrote: >>>>> I recently rebuilt the world and kernel and everything built just fine >>>>> and when I went to boot into the new kernel, it hangs. I had to revert >>>>> back to my previous kernel. >>>>> >>>>> Currently I'm running: >>>>> FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 >>>>> 20:44:06 CST 2010 root@server.domain.net:/usr/obj/usr/src/sys/server >>>>> amd64 >>>>> >>>>> When it hangs upon boot-up it simply stops here. I don't know how I >>>>> can >>>>> figure out what is causing the root of the hang. I'd really like to >>>>> get >>>>> this machine upgraded. >>>>> >>>>> Ppc0 cannot reserve I/O port range >>>>> PowerNow0 on cpu0 >>>>> Device_attach: PowerNow0 attach return 6 >>>>> PowerNow0 on cpu1 >>>>> Device_attach: PowerNow0 attach return 6 >>>>> PowerNow1 on cpu0 >>>>> Device_attach: PowerNow0 attach return 6 >>>>> PowerNow1 on cpu1 >>>>> Device_attach: PowerNow0 attach return 6 >>>>> Time Counters Tick every 1.000 msec >>>>> <<>> >>>>> >>>>> Any help is greatly appreciated. >>>>> >>>>> -Troy >>>>> >>>>> _______________________________________________ >>>>> 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" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 19:00:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38113106566B for ; Tue, 28 Dec 2010 19:00:35 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (outgoing01.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id D48048FC21 for ; Tue, 28 Dec 2010 19:00:34 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 2926014E63A; Tue, 28 Dec 2010 09:00:33 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 67148196E1C; Tue, 28 Dec 2010 09:00:33 -1000 (HST) Date: Tue, 28 Dec 2010 09:00:33 -1000 From: Clifton Royston To: Jason Helfman Message-ID: <20101228190032.GA3031@lava.net> Mail-Followup-To: Jason Helfman , freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> <4D1934B3.8080102@FreeBSD.org> <20101228062028.GA95888@eggman.experts-exchange.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101228062028.GA95888@eggman.experts-exchange.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 19:00:35 -0000 On Mon, Dec 27, 2010 at 10:20:28PM -0800, Jason Helfman wrote: > On Mon, Dec 27, 2010 at 04:52:03PM -0800, Doug Barton thus spake: > >On 12/27/2010 16:40, Damien Fleuriot wrote: > >>On 12/27/10 11:58 PM, Clifton Royston wrote: > >>> OK, and oh well... I wish there were some way to automate the diffing > >>>out of the $FreeBSD lines. I suppose those might be the artifact of > >>>some previous upgrade, so that the file version present is not the one > >>>expected for FreeBSD 6.1. > >> > >>Wait, do you mean like, mergemaster -F ? > >> > >>Excerpt from the manual: > >> -F If the files differ only by VCS Id ($FreeBSD) install > >>the new file. > >> > >> > >>I've discovered this rather recently, it's a *lifesaver* > >> > >>This comes from fbsd7's version though, I can not say for the one you're > >>still running on fbsd6 > > > >You always want to run mergemaster from the version you are upgrading > >_to_. It doesn't happen often (by design) but occasionally mergemaster > >has to grow "special knowledge" of specific files/directories/etc. in a > >new FreeBSD version. > > As far as I can tell, freebsd-update doesn't use mergemaster. > > /usr/src/usr.sbin/freebsd-update/freebsd-update.sh > > Source installation does, however I don't believe a binary upgrade does. It might be an interesting project to work on enhancing freebsd-update to use mergemaster - shared code, DRY, and all that. ... A brief update for the curious: this turned into the "sharks circling" kind of upgrade though not through any fault of freebsd-update. It turned out after I had done the initial install steps at the console that 7.1 doesn't detect the built-in re0 GbE interface on this motherboard, which threw a major monkeywrench in the way of rebuilding all the ports. I should have recalled that there were some ongoing re problems which Pyun was fixing around the time of 7.1. As I didn't want to downgrade - and couldn't safely after having installed userland prematurely - I had a backup plan of booting from the CD drive, which then turned out to have failed mechanically. Fortunately this is my home server and isn't running anything critical. I stole a CD drive from my usual desktop computer and could boot the loader/kernel on a 7.3 CD, which detects everything. Following that, rebooting via the hard drive got the interface running again. (Why, I don't know - I suspect it might be somehow picking up either the 7.3 loader or hints due to having the CD set as the BIOS boot drive.) I got the old ports removed and essential ports rebuilt with portsnap and portmaster (thank you, Doug Barton) and I'm pressing ahead with an upgrade to 7.3 since it appears that kernel will work fine with this motherboard. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 20:08:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12DF1106564A for ; Tue, 28 Dec 2010 20:08:46 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id C2F5F8FC16 for ; Tue, 28 Dec 2010 20:08:45 +0000 (UTC) Received: by qwj9 with SMTP id 9so9266652qwj.13 for ; Tue, 28 Dec 2010 12:08:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KVnF8Mwl8h4ZSbCGzN3D1qS+e2AHlm/fZJh2OrwcCrc=; b=n2SZyFq5j+tkEQZYv9uZu1IvaqKQu+ErqwvX+LJGOQj2bJWQKHeWgBeBeZDERbGTLM U5IyxiDhF6TrNbcX7rnKtgdmT5aYPAVO/NS/0U2vG6iv7HJpb+liDbQWwlGoOsVKqxRp Z19rBtPuQFk/m0fRd1IYQdTKUjOl7nNjamVBY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=oEfXbsM4GRsc8d1WoDIlgPvmUOw+18Ys1kClt/qFmcYICaJZzeu765w/IR1ttQTJ8o +ZcD1nkgbx6Vw+Z7HamUU9ip+BFzpY0zC/wFh+SVdauJC1NcYwOfKC0/8vfUrfwjEuYv +Rgjn3ZtTvklRx1qzZvkIUN3Sfhz9ZoaWepg4= MIME-Version: 1.0 Received: by 10.229.79.12 with SMTP id n12mr12175670qck.129.1293566924972; Tue, 28 Dec 2010 12:08:44 -0800 (PST) Received: by 10.220.192.11 with HTTP; Tue, 28 Dec 2010 12:08:44 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Dec 2010 23:08:44 +0300 Message-ID: From: Michael BlackHeart To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 20:08:46 -0000 I'm no looking for help neither instructions how to build kernel. I'm just installing 8.1 RELEASE and svn it up to last week 8-stable. And going step-by-step of handbook installing kernel I'm having a trouble - it seems than new kenel doesn't recognize my HDD. I'm not doing something special, in that case I'm for shure mentioned it. I'm just building GENERIC kernel without any configuration of system after installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel and it can't find my HDD but 8.1 i386/amd64 releases works well and as I remember something about month ago stable too. >Now, a likely cause of your problem is the installation of a custom >kernel with removed support for whatever your hard disk drive or raid >controller is recognized as. When it works it's just and ad0 hdd, no raid or special driver I'm jsut trying to say than recent changes in kernel or kernel-modules broke up my HDD support and I'd like to notice developres to check where the problem is. And of couse I've tried to switch SATA native mode and it doesn't change anything. Loader on it's own stage easily detects HDD and root partition so I can just select old kernel and boot up, but I'm not shure how he gain access to HDD to mfke any conclusion, probably through BIOS interrupts but it's out of piont. And for my pity I don't know how to dump demsg without having any serial connection or usable disk drive, maybe to flash drive, but I don't know how. And anyway there's no real kernel painc, it just asks for root mountpoint. And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD If you need any aditional info I'll give it all, just ask. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 20:49:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24ACA106566B for ; Tue, 28 Dec 2010 20:49:06 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id D94698FC20 for ; Tue, 28 Dec 2010 20:49:05 +0000 (UTC) Received: by qyk36 with SMTP id 36so9233271qyk.13 for ; Tue, 28 Dec 2010 12:49:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.80.198 with SMTP id u6mr13321935qak.113.1293569344918; Tue, 28 Dec 2010 12:49:04 -0800 (PST) Received: by 10.220.59.69 with HTTP; Tue, 28 Dec 2010 12:49:04 -0800 (PST) X-Originating-IP: [71.1.133.114] In-Reply-To: <4D1937C8.80609@twisted.net> References: <4D191642.4050908@twisted.net> <4D192E4B.9020701@my.gd> <4D1937C8.80609@twisted.net> Date: Tue, 28 Dec 2010 12:49:04 -0800 Message-ID: From: Rob Farmer To: troy@twisted.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Kernel/World Upgrade causes Hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 20:49:06 -0000 On Mon, Dec 27, 2010 at 17:05, Troy wrote: > # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150= ) > device =A0 =A0 =A0 =A0 =A0atpic =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # 825= 9A compatability > What is this? Do you actually need it? nforce 3 is pretty old - maybe it got broken somewhere along the way? It is, IMHO, the strangest thing in your kernel vs. GENERIC, which you said works. --=20 Rob Farmer From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 21:08:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21833106564A for ; Tue, 28 Dec 2010 21:08:31 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 914B48FC12 for ; Tue, 28 Dec 2010 21:08:30 +0000 (UTC) Received: from core.byshenk.net (localhost [127.0.0.1]) by core.byshenk.net (8.14.4/8.14.4) with ESMTP id oBSL9FPq036068; Tue, 28 Dec 2010 22:09:15 +0100 (CET) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.4/8.14.4/Submit) id oBSL9F3u036067; Tue, 28 Dec 2010 22:09:15 +0100 (CET) (envelope-from byshenknet) Date: Tue, 28 Dec 2010 22:09:15 +0100 From: Greg Byshenk To: Michael BlackHeart Message-ID: <20101228210915.GE9465@core.byshenk.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on core.byshenk.net Cc: freebsd-stable@freebsd.org Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 21:08:31 -0000 On Tue, Dec 28, 2010 at 11:08:44PM +0300, Michael BlackHeart wrote: > I'm no looking for help neither instructions how to build kernel. I'm > just installing 8.1 RELEASE and svn it up to last week 8-stable. And > going step-by-step of handbook installing kernel I'm having a trouble > - it seems than new kenel doesn't recognize my HDD. I'm not doing > something special, in that case I'm for shure mentioned it. I'm just > building GENERIC kernel without any configuration of system after > installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel > and it can't find my HDD but 8.1 i386/amd64 releases works well and as > I remember something about month ago stable too. > >Now, a likely cause of your problem is the installation of a custom > >kernel with removed support for whatever your hard disk drive or raid > >controller is recognized as. > When it works it's just and ad0 hdd, no raid or special driver > I'm jsut trying to say than recent changes in kernel or kernel-modules > broke up my HDD support and I'd like to notice developres to check > where the problem is. > And of couse I've tried to switch SATA native mode and it doesn't > change anything. > Loader on it's own stage easily detects HDD and root partition so I > can just select old kernel and boot up, but I'm not shure how he gain > access to HDD to mfke any conclusion, probably through BIOS interrupts > but it's out of piont. > And for my pity I don't know how to dump demsg without having any > serial connection or usable disk drive, maybe to flash drive, but I > don't know how. And anyway there's no real kernel painc, it just asks > for root mountpoint. > > And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD > > If you need any aditional info I'll give it all, just ask. If you change to SATA native mode, then your HD may show up at a different device (mine moved to ad8). If you go to native mode and issue a '?' when it fails to find the kernel, does it show any HD devices? -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 22:40:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11451106564A for ; Tue, 28 Dec 2010 22:40:46 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id BD7C38FC17 for ; Tue, 28 Dec 2010 22:40:45 +0000 (UTC) Received: by yxh35 with SMTP id 35so4446513yxh.13 for ; Tue, 28 Dec 2010 14:40:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zefN1kNuBw0XK8FjYlcxhyDCJo1soEz3Pc/KBkV9iaA=; b=dP88skYlUQzO3rQY/sPNw3XeuR/00mVH8fKyFx1uRK1HZA/aaGYBNTMPBSeeVYcpje D9Xt3ZISc1ryp3nJeHO/WUvHqwPW42Nb4UG+ktPklpz4aDZEfqbe1eTEbC8ZokWk15Ow LKuHCnc1eGGrd/L8418VXxBsY5I6qjsuLnZlA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Rxw3oH0Je+qkrGJQkleqYcgXaN+GS01PS1GfPj8IyKMkmxHeO3zD1+Wf8pFcdyqm5O MNC0vsyAgWn2MWrNwX3XyBrUki7uIdRW53eEdmsoi8Dj2rfDVga2LF/7vFbOsnZUW1rj m95lNdtNDCLGy0daxCPPVORRNSh53g/YVYWaE= MIME-Version: 1.0 Received: by 10.90.72.20 with SMTP id u20mr4743033aga.145.1293576044957; Tue, 28 Dec 2010 14:40:44 -0800 (PST) Received: by 10.90.153.20 with HTTP; Tue, 28 Dec 2010 14:40:44 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Dec 2010 14:40:44 -0800 Message-ID: From: Freddie Cash To: Jean-Yves Avenard Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 22:40:46 -0000 On Tue, Dec 28, 2010 at 8:58 AM, Jean-Yves Avenard wr= ote: > On 28 December 2010 08:56, Freddie Cash wrote: > >> Is that a typo, or the actual command you used? =C2=A0You have an extra = "s" >> in there. =C2=A0Should be "log" and not "logs". =C2=A0However, I don't t= hink >> that command is correct either. >> >> I believe you want to use the "detach" command, not "remove". >> >> # zpool detach pool label/zil > > well, I tried the detach command: > > server4# zpool detach pool ada1s1 > cannot detach ada1s1: only applicable to mirror and replacing vdevs > > server4# zpool remove pool ada1s1 > server4# > > so you need to use remove, and adding log (or cache) makes no > difference whatsoever.. > Interesting, thanks for the confirmation. I don't have any ZFS systems using log devices, so can only go by what's in the docs. May want to make a note that the man page (at least for ZFSv15 in FreeBSD 8.1) includes several sections that use "zpool detach" when talking about log devices. If that's still in the man page for ZFSv28, it'll need to be cleaned up. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 22:43:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34F42106566B for ; Tue, 28 Dec 2010 22:43:32 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id E0A498FC12 for ; Tue, 28 Dec 2010 22:43:31 +0000 (UTC) Received: by gyf3 with SMTP id 3so4342542gyf.13 for ; Tue, 28 Dec 2010 14:43:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=r6kc2J7XN0eUXT8YYTb9/a6nekB8jfWAKBih+hQND+4=; b=cFEVbkABeT1F93G48KOPXwkEWXOCPbikwVD9OZUh8oAnvHJrSlFyeVkJeAcr7R9ay2 bYAlBiuPqCq65hAPkVT68AFle+RbbnFR6eojt4/YxDHe3s0uX7jOVGOUQn7j80rJgAUj 6ajjIItV0mBtbvtrshDzq8nek/b29FmfhrTB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YiBwRIr5i+Mdw/L3VRXFMqL4wuBHCP/XTR69P0P2vihq87b/URGChRYSigtu+cs4Yl USvajtWXtU5lLAreBXeOJ9ijvnsGhze+sjAuh8+JUxzvPdj4vJ+hcRh4cXV7I+1GYris SPFxZCc1fCjtlsTCdqYjoLqpBeDl8FTesnXBc= MIME-Version: 1.0 Received: by 10.91.153.10 with SMTP id f10mr4909569ago.172.1293576211109; Tue, 28 Dec 2010 14:43:31 -0800 (PST) Received: by 10.90.153.20 with HTTP; Tue, 28 Dec 2010 14:43:30 -0800 (PST) In-Reply-To: References: <4D181E51.30401@DataIX.net> Date: Tue, 28 Dec 2010 14:43:30 -0800 Message-ID: From: Freddie Cash To: Jean-Yves Avenard Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 22:43:32 -0000 On Tue, Dec 28, 2010 at 9:39 AM, Jean-Yves Avenard > Now, I haven't tried using cache and log from a different disk. The > motherboard on the server has 8 SATA ports, and I have no free port to > add another disk. So my only option to have both a log and cache > device in my zfs pool, is to use two slices on the same disk. For testing, you can always just connect a USB stick, and use that for the cache. I've done this on large ZFS systems (24-drives) and on my home server (5-drives). Works nicely. That should narrow it down to either "can't use cache/log on same device" or "can't use cache and log at the same time". -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 22:50:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60856106566C; Tue, 28 Dec 2010 22:50:28 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 2DEA28FC0C; Tue, 28 Dec 2010 22:50:28 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oBSMoQ6D075260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Dec 2010 14:50:26 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oBSMoQR6075259; Tue, 28 Dec 2010 14:50:26 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA20705; Tue, 28 Dec 10 14:31:39 PST Date: Tue, 28 Dec 2010 14:31:39 -0800 From: perryh@pluto.rain.com To: avg@freebsd.org Message-Id: <4d1a654b.9/lZDQOjHY0hJCjq%perryh@pluto.rain.com> References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> In-Reply-To: <4CFD0633.9060509@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_4d1a654b.wI8NqF1oq/fXqFb0P3dTZcQHcnPbwnEUR2uSBDl9zIYjK+nz" Cc: freebsd-stable@freebsd.org Subject: Re: Could MSGBUF_SIZE be made a loader tunable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 22:50:28 -0000 This is a multi-part message in MIME format. --=_4d1a654b.wI8NqF1oq/fXqFb0P3dTZcQHcnPbwnEUR2uSBDl9zIYjK+nz Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Andriy Gapon wrote: > on 06/12/2010 07:20 perryh@pluto.rain.com said the following: > > Would there be some fundamental problem in changing MSGBUF_SIZE > > from a compiled-in constant to a tunable that could be set at the > > loader prompt? > > I didn't see any obvious downside from examining the 8.1-RELEASE > > code ... > I also don't immediately see why that wouldn't work. > Can you try to come up with a patch? I got it working. The first attachment contains the changes to generic and i386-specific files, tested against 8.1-RELEASE. The second attachment contains (untested) corresponding changes to files for other arches. --=_4d1a654b.wI8NqF1oq/fXqFb0P3dTZcQHcnPbwnEUR2uSBDl9zIYjK+nz Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="MsgBufSiz.patch-81R-working" --- boot/common/loader.8-81R Sun Jun 13 19:09:06 2010 +++ boot/common/loader.8 Mon Dec 13 21:34:49 2010 @@ -615,6 +615,14 @@ the NBUF parameter will override this limit. Modifies .Dv VM_BCACHE_SIZE_MAX . +.It Va kern.msgbufsize +Sets the size of the kernel message buffer. +The default of 64KB is usually sufficient unless +large amounts of trace data need to be collected +between opportunities to examine the buffer or +dump it to a file. +Modifies kernel option +.Dv MSGBUF_SIZE .It Va machdep.disable_mtrrs Disable the use of i686 MTRRs (x86 only). .It Va net.inet.tcp.tcbhashsize --- boot/forth/loader.conf-81R Sun Jun 13 19:09:06 2010 +++ boot/forth/loader.conf Mon Dec 13 21:50:16 2010 @@ -99,6 +99,7 @@ #kern.maxswzone="" # Set the max swmeta KVA storage #kern.maxtsiz="" # Set the max text size #kern.maxusers="32" # Set size of various static tables +#kern.msgbufsize="" # Set size of kernel message buffer #kern.nbuf="" # Set the number of buffer headers #kern.ncallout="" # Set the maximum # of timer events #kern.ngroups="1023" # Set the maximum # of supplemental groups --- kern/subr_param.c-81R Sun Jun 13 19:09:06 2010 +++ kern/subr_param.c Mon Dec 27 00:21:26 2010 @@ -38,6 +38,7 @@ __FBSDID("$FreeBSD: src/sys/kern/subr_param.c,v 1.90.2.4.2.1 2010/06/14 02:09:06 kensmith Exp $"); #include "opt_param.h" +#include "opt_msgbuf.h" #include "opt_maxusers.h" #include @@ -45,6 +46,7 @@ #include #include #include +#include #include @@ -89,6 +91,7 @@ int nswbuf; long maxswzone; /* max swmeta KVA storage */ long maxbcache; /* max buffer cache KVA storage */ +long msgbufsize; /* size of kernel message buffer */ long maxpipekva; /* Limit on pipe KVA */ int vm_guest; /* Running as virtual machine guest? */ u_long maxtsiz; /* max text size */ @@ -110,6 +113,8 @@ "Maximum memory for swap metadata"); SYSCTL_LONG(_kern, OID_AUTO, maxbcache, CTLFLAG_RDTUN, &maxbcache, 0, "Maximum value of vfs.maxbufspace"); +SYSCTL_LONG(_kern, OID_AUTO, msgbufsize, CTLFLAG_RDTUN, &msgbufsize, 0, + "Size of the kernel message buffer"); SYSCTL_ULONG(_kern, OID_AUTO, maxtsiz, CTLFLAG_RDTUN, &maxtsiz, 0, "Maximum text size"); SYSCTL_ULONG(_kern, OID_AUTO, dfldsiz, CTLFLAG_RDTUN, &dfldsiz, 0, @@ -217,6 +222,10 @@ maxbcache = VM_BCACHE_SIZE_MAX; #endif TUNABLE_LONG_FETCH("kern.maxbcache", &maxbcache); +#ifdef MSGBUF_SIZE + msgbufsize = MSGBUF_SIZE; +#endif + TUNABLE_LONG_FETCH("kern.msgbufsize", &msgbufsize); maxtsiz = MAXTSIZ; TUNABLE_ULONG_FETCH("kern.maxtsiz", &maxtsiz); --- i386/i386/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ i386/i386/machdep.c Mon Dec 27 00:25:40 2010 @@ -50,7 +50,6 @@ #include "opt_isa.h" #include "opt_kstack_pages.h" #include "opt_maxmem.h" -#include "opt_msgbuf.h" #include "opt_npx.h" #include "opt_perfmon.h" #include "opt_xbox.h" @@ -2059,7 +2058,7 @@ physmem = Maxmem; basemem = 0; physmap[0] = init_first << PAGE_SHIFT; - physmap[1] = ptoa(Maxmem) - round_page(MSGBUF_SIZE); + physmap[1] = ptoa(Maxmem) - round_page(msgbufsize); physmap_idx = 0; goto physmap_done; #endif @@ -2445,7 +2444,7 @@ * calculation, etc.). */ while (phys_avail[pa_indx - 1] + PAGE_SIZE + - round_page(MSGBUF_SIZE) >= phys_avail[pa_indx]) { + round_page(msgbufsize) >= phys_avail[pa_indx]) { physmem -= atop(phys_avail[pa_indx] - phys_avail[pa_indx - 1]); phys_avail[pa_indx--] = 0; phys_avail[pa_indx--] = 0; @@ -2454,10 +2453,10 @@ Maxmem = atop(phys_avail[pa_indx]); /* Trim off space for the message buffer. */ - phys_avail[pa_indx] -= round_page(MSGBUF_SIZE); + phys_avail[pa_indx] -= round_page(msgbufsize); /* Map the message buffer. */ - for (off = 0; off < round_page(MSGBUF_SIZE); off += PAGE_SIZE) + for (off = 0; off < round_page(msgbufsize); off += PAGE_SIZE) pmap_kenter((vm_offset_t)msgbufp + off, phys_avail[pa_indx] + off); @@ -2666,7 +2665,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* transfer to user mode */ _ucodesel = GSEL(GUCODE_SEL, SEL_UPL); @@ -2921,7 +2920,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* make a call gate to reenter kernel with */ gdp = &ldt[LSYS5CALLS_SEL].gd; --- i386/i386/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ i386/i386/pmap.c Mon Dec 27 00:23:49 2010 @@ -105,7 +105,6 @@ #include "opt_cpu.h" #include "opt_pmap.h" -#include "opt_msgbuf.h" #include "opt_smp.h" #include "opt_xbox.h" @@ -448,7 +447,7 @@ /* * msgbufp is used to map the system message buffer. */ - SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(MSGBUF_SIZE))) + SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(msgbufsize))) /* * KPTmap is used by pmap_kextract(). --- sys/msgbuf.h-81R Sun Jun 13 19:09:06 2010 +++ sys/msgbuf.h Mon Dec 27 00:17:41 2010 @@ -54,6 +54,7 @@ #ifdef _KERNEL extern int msgbuftrigger; extern struct msgbuf *msgbufp; +extern long msgbufsize; void msgbufinit(void *ptr, int size); void msgbuf_addchar(struct msgbuf *mbp, int c); --=_4d1a654b.wI8NqF1oq/fXqFb0P3dTZcQHcnPbwnEUR2uSBDl9zIYjK+nz Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="MsgBufSiz.patch-81R-otherArch" --- amd64/amd64/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ amd64/amd64/machdep.c Mon Dec 27 22:33:15 2010 @@ -51,7 +51,6 @@ #include "opt_isa.h" #include "opt_kstack_pages.h" #include "opt_maxmem.h" -#include "opt_msgbuf.h" #include "opt_perfmon.h" #include "opt_sched.h" @@ -1499,7 +1498,7 @@ * calculation, etc.). */ while (phys_avail[pa_indx - 1] + PAGE_SIZE + - round_page(MSGBUF_SIZE) >= phys_avail[pa_indx]) { + round_page(msgbufsize) >= phys_avail[pa_indx]) { physmem -= atop(phys_avail[pa_indx] - phys_avail[pa_indx - 1]); phys_avail[pa_indx--] = 0; phys_avail[pa_indx--] = 0; @@ -1508,10 +1507,10 @@ Maxmem = atop(phys_avail[pa_indx]); /* Trim off space for the message buffer. */ - phys_avail[pa_indx] -= round_page(MSGBUF_SIZE); + phys_avail[pa_indx] -= round_page(msgbufsize); /* Map the message buffer. */ - for (off = 0; off < round_page(MSGBUF_SIZE); off += PAGE_SIZE) + for (off = 0; off < round_page(msgbufsize); off += PAGE_SIZE) pmap_kenter((vm_offset_t)msgbufp + off, phys_avail[pa_indx] + off); } @@ -1708,7 +1707,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); fpuinit(); /* transfer to user mode */ --- arm/at91/at91_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/at91/at91_machdep.c Mon Dec 27 22:33:28 2010 @@ -43,8 +43,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" - #include __FBSDID("$FreeBSD: src/sys/arm/at91/at91_machdep.c,v 1.6.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $"); @@ -274,7 +272,7 @@ valloc_pages(abtstack, ABT_STACK_SIZE); valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); /* * Now we start construction of the L1 page table @@ -319,7 +317,7 @@ pmap_map_chunk(l1pagetable, kernel_l1pt.pv_va, kernel_l1pt.pv_pa, L1_TABLE_SIZE, VM_PROT_READ|VM_PROT_WRITE, PTE_PAGETABLE); pmap_map_chunk(l1pagetable, msgbufpv.pv_va, msgbufpv.pv_pa, - MSGBUF_SIZE, VM_PROT_READ|VM_PROT_WRITE, PTE_CACHE); + msgbufsize, VM_PROT_READ|VM_PROT_WRITE, PTE_CACHE); for (loop = 0; loop < NUM_KERNEL_PTS; ++loop) { pmap_map_chunk(l1pagetable, kernel_pt_table[loop].pv_va, @@ -396,7 +394,7 @@ KERNVIRTADDR + 3 * memsize, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- arm/mv/mv_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/mv/mv_machdep.c Mon Dec 27 22:33:35 2010 @@ -35,7 +35,6 @@ * from: FreeBSD: //depot/projects/arm/src/sys/arm/at91/kb920x_machdep.c, rev 45 */ -#include "opt_msgbuf.h" #include "opt_ddb.h" #include @@ -491,7 +490,7 @@ valloc_pages(abtstack, ABT_STACK_SIZE); valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); /* * Now we start construction of the L1 page table @@ -620,7 +619,7 @@ pmap_bootstrap(freemempos, pmap_bootstrap_lastaddr, &kernel_l1pt); msgbufp = (void *)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); /* --- arm/xscale/i80321/ep80219_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/xscale/i80321/ep80219_machdep.c Mon Dec 27 22:33:43 2010 @@ -45,8 +45,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" - #include __FBSDID("$FreeBSD: src/sys/arm/xscale/i80321/ep80219_machdep.c,v 1.13.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $"); @@ -247,7 +245,7 @@ valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); alloc_pages(minidataclean.pv_pa, 1); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); #ifdef ARM_USE_SMALL_ALLOC freemempos -= PAGE_SIZE; freemem_pt = trunc_page(freemem_pt); @@ -397,7 +395,7 @@ pmap_bootstrap(pmap_curmaxkvaddr, 0xd0000000, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- arm/xscale/i80321/iq31244_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/xscale/i80321/iq31244_machdep.c Mon Dec 27 22:33:51 2010 @@ -45,8 +45,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" - #include __FBSDID("$FreeBSD: src/sys/arm/xscale/i80321/iq31244_machdep.c,v 1.34.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $"); @@ -247,7 +245,7 @@ valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); alloc_pages(minidataclean.pv_pa, 1); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); #ifdef ARM_USE_SMALL_ALLOC freemempos -= PAGE_SIZE; freemem_pt = trunc_page(freemem_pt); @@ -403,7 +401,7 @@ pmap_bootstrap(pmap_curmaxkvaddr, 0xd0000000, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- arm/xscale/i8134x/crb_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/xscale/i8134x/crb_machdep.c Mon Dec 27 22:33:58 2010 @@ -45,8 +45,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" - #include __FBSDID("$FreeBSD: src/sys/arm/xscale/i8134x/crb_machdep.c,v 1.10.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $"); @@ -242,7 +240,7 @@ valloc_pages(abtstack, ABT_STACK_SIZE); valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); #ifdef ARM_USE_SMALL_ALLOC freemempos -= PAGE_SIZE; freemem_pt = trunc_page(freemem_pt); @@ -375,7 +373,7 @@ pmap_bootstrap(pmap_curmaxkvaddr, 0xd0000000, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- arm/xscale/ixp425/avila_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/xscale/ixp425/avila_machdep.c Mon Dec 27 22:34:04 2010 @@ -45,8 +45,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" - #include __FBSDID("$FreeBSD: src/sys/arm/xscale/ixp425/avila_machdep.c,v 1.20.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $"); @@ -314,7 +312,7 @@ valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); alloc_pages(minidataclean.pv_pa, 1); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); #ifdef ARM_USE_SMALL_ALLOC freemempos -= PAGE_SIZE; freemem_pt = trunc_page(freemem_pt); @@ -460,7 +458,7 @@ pmap_bootstrap(pmap_curmaxkvaddr, 0xd0000000, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- arm/xscale/pxa/pxa_machdep.c-81R Sun Jun 13 19:09:06 2010 +++ arm/xscale/pxa/pxa_machdep.c Mon Dec 27 22:34:11 2010 @@ -45,7 +45,6 @@ * Created : 17/09/94 */ -#include "opt_msgbuf.h" #include "opt_ddb.h" #include @@ -229,7 +228,7 @@ valloc_pages(undstack, UND_STACK_SIZE); valloc_pages(kernelstack, KSTACK_PAGES); alloc_pages(minidataclean.pv_pa, 1); - valloc_pages(msgbufpv, round_page(MSGBUF_SIZE) / PAGE_SIZE); + valloc_pages(msgbufpv, round_page(msgbufsize) / PAGE_SIZE); #ifdef ARM_USE_SMALL_ALLOC freemempos -= PAGE_SIZE; freemem_pt = trunc_page(freemem_pt); @@ -393,7 +392,7 @@ dump_avail[i] = 0; pmap_bootstrap(pmap_curmaxkvaddr, 0xd0000000, &kernel_l1pt); msgbufp = (void*)msgbufpv.pv_va; - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); mutex_init(); i = 0; --- i386/xen/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ i386/xen/pmap.c Mon Dec 27 22:14:40 2010 @@ -107,7 +107,6 @@ #include "opt_cpu.h" #include "opt_pmap.h" -#include "opt_msgbuf.h" #include "opt_smp.h" #include "opt_xbox.h" @@ -465,7 +464,7 @@ /* * msgbufp is used to map the system message buffer. */ - SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(MSGBUF_SIZE))) + SYSMAP(struct msgbuf *, unused, msgbufp, atop(round_page(msgbufsize))) /* * ptemap is used for pmap_pte_quick --- ia64/ia64/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ ia64/ia64/machdep.c Mon Dec 27 22:34:21 2010 @@ -31,7 +31,6 @@ #include "opt_compat.h" #include "opt_ddb.h" #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include "opt_sched.h" #include @@ -882,8 +881,8 @@ /* * Initialize error message buffer (at end of core). */ - msgbufp = (struct msgbuf *)pmap_steal_memory(MSGBUF_SIZE); - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufp = (struct msgbuf *)pmap_steal_memory(msgbufsize); + msgbufinit(msgbufp, msgbufsize); proc_linkup0(&proc0, &thread0); /* --- mips/mips/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ mips/mips/pmap.c Mon Dec 27 22:34:28 2010 @@ -69,7 +69,6 @@ __FBSDID("$FreeBSD: src/sys/mips/mips/pmap.c,v 1.21.2.2.2.1 2010/06/14 02:09:06 kensmith Exp $"); #include "opt_ddb.h" -#include "opt_msgbuf.h" #include #include #include @@ -328,8 +327,8 @@ /* * Steal the message buffer from the beginning of memory. */ - msgbufp = (struct msgbuf *)pmap_steal_memory(MSGBUF_SIZE); - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufp = (struct msgbuf *)pmap_steal_memory(msgbufsize); + msgbufinit(msgbufp, msgbufsize); /* Steal memory for the dynamic per-cpu area. */ dpcpu_init((void *)pmap_steal_memory(DPCPU_SIZE), 0); --- pc98/pc98/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ pc98/pc98/machdep.c Mon Dec 27 22:34:37 2010 @@ -49,7 +49,6 @@ #include "opt_isa.h" #include "opt_kstack_pages.h" #include "opt_maxmem.h" -#include "opt_msgbuf.h" #include "opt_npx.h" #include "opt_perfmon.h" @@ -1915,7 +1914,7 @@ * calculation, etc.). */ while (phys_avail[pa_indx - 1] + PAGE_SIZE + - round_page(MSGBUF_SIZE) >= phys_avail[pa_indx]) { + round_page(msgbufsize) >= phys_avail[pa_indx]) { physmem -= atop(phys_avail[pa_indx] - phys_avail[pa_indx - 1]); phys_avail[pa_indx--] = 0; phys_avail[pa_indx--] = 0; @@ -1924,10 +1923,10 @@ Maxmem = atop(phys_avail[pa_indx]); /* Trim off space for the message buffer. */ - phys_avail[pa_indx] -= round_page(MSGBUF_SIZE); + phys_avail[pa_indx] -= round_page(msgbufsize); /* Map the message buffer. */ - for (off = 0; off < round_page(MSGBUF_SIZE); off += PAGE_SIZE) + for (off = 0; off < round_page(msgbufsize); off += PAGE_SIZE) pmap_kenter((vm_offset_t)msgbufp + off, phys_avail[pa_indx] + off); } @@ -2144,7 +2143,7 @@ /* now running on new page tables, configured,and u/iom is accessible */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* make a call gate to reenter kernel with */ gdp = &ldt[LSYS5CALLS_SEL].gd; --- powerpc/aim/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ powerpc/aim/machdep.c Mon Dec 27 22:34:44 2010 @@ -60,7 +60,6 @@ #include "opt_compat.h" #include "opt_ddb.h" #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include #include @@ -530,7 +529,7 @@ pc->pc_curpcb = thread0.td_pcb; /* Initialise the message buffer. */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); #ifdef KDB if (boothowto & RB_KDB) --- powerpc/aim/mmu_oea.c-81R Wed Jun 23 06:47:27 2010 +++ powerpc/aim/mmu_oea.c Mon Dec 27 22:34:51 2010 @@ -935,10 +935,10 @@ /* * Allocate virtual address space for the message buffer. */ - pa = msgbuf_phys = moea_bootstrap_alloc(MSGBUF_SIZE, PAGE_SIZE); + pa = msgbuf_phys = moea_bootstrap_alloc(msgbufsize, PAGE_SIZE); msgbufp = (struct msgbuf *)virtual_avail; va = virtual_avail; - virtual_avail += round_page(MSGBUF_SIZE); + virtual_avail += round_page(msgbufsize); while (va < virtual_avail) { moea_kenter(mmup, va, pa); pa += PAGE_SIZE; --- powerpc/aim/mmu_oea64.c-81R Sun Jun 13 19:09:06 2010 +++ powerpc/aim/mmu_oea64.c Mon Dec 27 22:34:58 2010 @@ -1016,10 +1016,10 @@ /* * Allocate virtual address space for the message buffer. */ - pa = msgbuf_phys = moea64_bootstrap_alloc(MSGBUF_SIZE, PAGE_SIZE); + pa = msgbuf_phys = moea64_bootstrap_alloc(msgbufsize, PAGE_SIZE); msgbufp = (struct msgbuf *)virtual_avail; va = virtual_avail; - virtual_avail += round_page(MSGBUF_SIZE); + virtual_avail += round_page(msgbufsize); while (va < virtual_avail) { moea64_kenter(mmup, va, pa); pa += PAGE_SIZE; --- powerpc/booke/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ powerpc/booke/machdep.c Mon Dec 27 22:35:06 2010 @@ -84,7 +84,6 @@ #include "opt_compat.h" #include "opt_ddb.h" #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include #include @@ -450,7 +449,7 @@ pc->pc_curpcb = thread0.td_pcb; /* Initialise the message buffer. */ - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* Enable Machine Check interrupt. */ mtmsr(mfmsr() | PSL_ME); --- powerpc/booke/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ powerpc/booke/pmap.c Mon Dec 27 22:35:12 2010 @@ -984,7 +984,7 @@ /* Allocate space for the message buffer. */ msgbufp = (struct msgbuf *)data_end; - data_end += MSGBUF_SIZE; + data_end += msgbufsize; debugf(" msgbufp at 0x%08x end = 0x%08x\n", (uint32_t)msgbufp, data_end); --- sparc64/sparc64/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ sparc64/sparc64/machdep.c Mon Dec 27 22:35:18 2010 @@ -41,7 +41,6 @@ #include "opt_compat.h" #include "opt_ddb.h" #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include #include @@ -574,7 +573,7 @@ * buffer (after setting the trap table). */ dpcpu_init(dpcpu0, 0); - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); /* * Initialize mutexes. --- sparc64/sparc64/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ sparc64/sparc64/pmap.c Mon Dec 27 22:35:23 2010 @@ -66,7 +66,6 @@ */ #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include "opt_pmap.h" #include @@ -396,7 +395,7 @@ /* * Allocate and map the message buffer. */ - pa = pmap_bootstrap_alloc(MSGBUF_SIZE); + pa = pmap_bootstrap_alloc(msgbufsize); msgbufp = (struct msgbuf *)TLB_PHYS_TO_DIRECT(pa); /* --- sun4v/sun4v/machdep.c-81R Sun Jun 13 19:09:06 2010 +++ sun4v/sun4v/machdep.c Mon Dec 27 22:35:29 2010 @@ -41,7 +41,6 @@ #include "opt_compat.h" #include "opt_ddb.h" #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include #include @@ -502,7 +501,7 @@ */ BVPRINTF("initialize msgbuf\n"); dpcpu_init(dpcpu0, 0); - msgbufinit(msgbufp, MSGBUF_SIZE); + msgbufinit(msgbufp, msgbufsize); BVPRINTF("initialize mutexes\n"); mutex_init(); --- sun4v/sun4v/pmap.c-81R Sun Jun 13 19:09:06 2010 +++ sun4v/sun4v/pmap.c Mon Dec 27 22:35:55 2010 @@ -29,7 +29,6 @@ __FBSDID("$FreeBSD: src/sys/sun4v/sun4v/pmap.c,v 1.47.2.2.2.1 2010/06/14 02:09:06 kensmith Exp $"); #include "opt_kstack_pages.h" -#include "opt_msgbuf.h" #include "opt_pmap.h" #include "opt_trap_trace.h" @@ -779,7 +778,7 @@ /* * Allocate and map the message buffer. */ - msgbuf_phys = pmap_bootstrap_alloc(MSGBUF_SIZE); + msgbuf_phys = pmap_bootstrap_alloc(msgbufsize); msgbufp = (struct msgbuf *)TLB_PHYS_TO_DIRECT(msgbuf_phys); /* --=_4d1a654b.wI8NqF1oq/fXqFb0P3dTZcQHcnPbwnEUR2uSBDl9zIYjK+nz-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 23:20:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31CCE106567A for ; Tue, 28 Dec 2010 23:20:28 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id B342C8FC15 for ; Tue, 28 Dec 2010 23:20:27 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id B0E48133223; Wed, 29 Dec 2010 00:20:26 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id n2tXlC3usGBd; Wed, 29 Dec 2010 00:20:24 +0100 (CET) Received: from [10.9.8.1] (188-167-78-139.dynamic.chello.sk [188.167.78.139]) by mail.vx.sk (Postfix) with ESMTPSA id 481E2133217; Wed, 29 Dec 2010 00:20:24 +0100 (CET) Message-ID: <4D1A70B7.6090809@FreeBSD.org> Date: Wed, 29 Dec 2010 00:20:23 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Jean-Yves Avenard References: <4D181E51.30401@DataIX.net> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2010 23:20:28 -0000 Please don't consider these patches as production-ready. What we want to do is find and resolve as many bugs as possible. To help us fix these bugs, a way to reproduce the bug from a clean start (e.g. in virtualbox) would be great and speed up finding the cause for the problem. Your problem looks like some sort of deadlock. In your case, when you experiene the hang, try running "procstat -k -k PID" in another shell (console). That will give us valuable information. Cheers, mm Dňa 28.12.2010 18:39, Jean-Yves Avenard wrote / napísal(a): > On 29 December 2010 03:15, Jean-Yves Avenard wrote: > >> # zpool import >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.57r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.95r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 32.19r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 32.72r 0.00u 0.03s 0% 2556k >> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 40.13r 0.00u 0.03s 0% 2556k >> >> ah ah ! >> it's not the separate log that make zpool crash, it's the cache ! >> >> Having the cache in prevent from importing the pool again.... >> >> rebooting: same deal... can't access the pool any longer ! >> >> Hopefully this is enough hint for someone to track done the bug ... >> > > More details as I was crazy enough to try various things. > > The problem of zpool being stuck in spa_namespace_lock, only occurs if > you are using both the cache and the log at the same time. > Use one or the other : then there's no issue > > But the instant you add both log and cache to the pool, it becomes unusable. > > Now, I haven't tried using cache and log from a different disk. The > motherboard on the server has 8 SATA ports, and I have no free port to > add another disk. So my only option to have both a log and cache > device in my zfs pool, is to use two slices on the same disk. > > Hope this helps.. > Jean-Yves > _______________________________________________ > 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 Wed Dec 29 00:22:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67A18106566C for ; Wed, 29 Dec 2010 00:22:57 +0000 (UTC) (envelope-from fvhemert@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2546C8FC08 for ; Wed, 29 Dec 2010 00:22:56 +0000 (UTC) Received: by gwj21 with SMTP id 21so5354588gwj.13 for ; Tue, 28 Dec 2010 16:22:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=el0yTk7ocaNiM9thDWyX82kbd0tuuDrXDFJkhomrFhU=; b=Tx8NWtw41nYlJBWooqFiRSp0qUD/OoJT48rgpuOMqUXLkE3990B2sQTFV0/l6MbI4q RKqGUWC0ISCDKxPDIltn/BaW2hDBY4yFmucIzuSNExQ3mXE2BNIpv58DGM6Yf6IiBvzn erMWsGLt2bU0wzWiVXddRS5viYn+/AUSqwTQQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=g/tm8NeD8Bi0BPTb6MfpGLNn4dQibxnRyC0bA5bhhLTQmOWwcgkK5Fg5JHzasFsI/l H0bEmFDOXOESsa/V8Lp7cbP4CQHQKG1BSDF1Vx/MxfyWMW4uLpawuW5+w3qvZTOwsQQA z36Zt4/YJukU53BM4aCdlP+mj2e5mGIUI/V2I= MIME-Version: 1.0 Received: by 10.100.173.20 with SMTP id v20mr5765825ane.133.1293580617793; Tue, 28 Dec 2010 15:56:57 -0800 (PST) Received: by 10.101.5.31 with HTTP; Tue, 28 Dec 2010 15:56:57 -0800 (PST) Date: Wed, 29 Dec 2010 00:56:57 +0100 Message-ID: From: Freek van Hemert To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 00:22:57 -0000 Hello everyone, This is my first mail on the mailinglist and I very much appreciate this option of getting some help. I have a question regarding zfs on freebsd. (I'm making a home server) This afternoon I did a "zpool create data mirror ad4 ad6" Now I'm copying things from my ufs2 disk into the 2TB zpool, it is very slow. I'm on freebsd 8.1 amd64 on an atom n330 with 2 sata disks, gstat tells me I'm going at around 2 mbps at near 100 %busy while the ufs2 drives are near 0. Also, ufs2 to ufs2 was much faster (I estimate about 10 times faster). How do I tune? The wiki is not helpful for amd64 users stating that the defaults should be optimal. I'm using the 8.1-stable version which has just been installed this afternoon from a minimal install iso. I'm copying from a single ufs2 pata drive into a sata zpool mirror. I have 2GB of ram. Top tells me: 761 MB Active, 790 Inactive and there is hardly any cpu usage (96-98% idle). vfs.numvnodes: around 12500 now (after several hours of copying) and stil slowly rising. Hope you can help me. Freek (from the Netherlands) From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 00:27:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 379A8106564A for ; Wed, 29 Dec 2010 00:27:47 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 230088FC0A for ; Wed, 29 Dec 2010 00:27:47 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id oBT0ReW8009218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Dec 2010 16:27:41 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 6F55D1CC16; Tue, 28 Dec 2010 16:27:40 -0800 (PST) To: Greg Byshenk In-reply-to: Your message of "Tue, 28 Dec 2010 22:09:15 +0100." <20101228210915.GE9465@core.byshenk.net> Date: Tue, 28 Dec 2010 16:27:40 -0800 From: "Kevin Oberman" Message-Id: <20101229002740.6F55D1CC16@ptavv.es.net> Cc: freebsd-stable@freebsd.org, Michael BlackHeart Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 00:27:47 -0000 > Date: Tue, 28 Dec 2010 22:09:15 +0100 > From: Greg Byshenk > Sender: owner-freebsd-stable@freebsd.org > > On Tue, Dec 28, 2010 at 11:08:44PM +0300, Michael BlackHeart wrote: > > I'm no looking for help neither instructions how to build kernel. I'm > > just installing 8.1 RELEASE and svn it up to last week 8-stable. And > > going step-by-step of handbook installing kernel I'm having a trouble > > - it seems than new kenel doesn't recognize my HDD. I'm not doing > > something special, in that case I'm for shure mentioned it. I'm just > > building GENERIC kernel without any configuration of system after > > installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel > > and it can't find my HDD but 8.1 i386/amd64 releases works well and as > > I remember something about month ago stable too. > > >Now, a likely cause of your problem is the installation of a custom > > >kernel with removed support for whatever your hard disk drive or raid > > >controller is recognized as. > > When it works it's just and ad0 hdd, no raid or special driver > > I'm jsut trying to say than recent changes in kernel or kernel-modules > > broke up my HDD support and I'd like to notice developres to check > > where the problem is. > > And of couse I've tried to switch SATA native mode and it doesn't > > change anything. > > Loader on it's own stage easily detects HDD and root partition so I > > can just select old kernel and boot up, but I'm not shure how he gain > > access to HDD to mfke any conclusion, probably through BIOS interrupts > > but it's out of piont. > > And for my pity I don't know how to dump demsg without having any > > serial connection or usable disk drive, maybe to flash drive, but I > > don't know how. And anyway there's no real kernel painc, it just asks > > for root mountpoint. > > > > And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD > > > > If you need any aditional info I'll give it all, just ask. > > If you change to SATA native mode, then your HD may show up at a > different device (mine moved to ad8). If you go to native mode and > issue a '?' when it fails to find the kernel, does it show any HD > devices? I would strongly urge that you start using labels instead of device names for your disks. Labels don't change unless you explicitly change them while drive names do. Labels may be used in the fstab. E.G.: # Device Mountpoint FStype Options Dump Pass# /dev/ufs/root / ufs rw 1 1 /dev/ufs/tmp /tmp ufs rw 2 2 /dev/ufs/var /usr ufs rw 2 2 /dev/ufs/var /var ufs rw 2 2 See 19.6 "Labeling Disk Devices" in the handbook for more information. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 00:40:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03DD61065670 for ; Wed, 29 Dec 2010 00:40:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 9E27D8FC18 for ; Wed, 29 Dec 2010 00:40:37 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta06.emeryville.ca.mail.comcast.net with comcast id oj5j1f0051Y3wxoA6ogcu8; Wed, 29 Dec 2010 00:40:36 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta15.emeryville.ca.mail.comcast.net with comcast id ooga1f00U2tehsa8bogb8y; Wed, 29 Dec 2010 00:40:35 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 912279B427; Tue, 28 Dec 2010 16:40:34 -0800 (PST) Date: Tue, 28 Dec 2010 16:40:34 -0800 From: Jeremy Chadwick To: Freek van Hemert Message-ID: <20101229004034.GA18233@icarus.home.lan> 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 Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 00:40:38 -0000 On Wed, Dec 29, 2010 at 12:56:57AM +0100, Freek van Hemert wrote: > Hello everyone, > > This is my first mail on the mailinglist and I very much appreciate this > option of getting some help. > > I have a question regarding zfs on freebsd. > (I'm making a home server) > This afternoon I did a "zpool create data mirror ad4 ad6" Now I'm copying > things from my ufs2 disk into the 2TB zpool, it is very slow. I'm on freebsd > 8.1 amd64 on an atom n330 with 2 sata disks, gstat tells me I'm going at > around 2 mbps at near 100 %busy while the ufs2 drives are near 0. Also, > ufs2 to ufs2 was much faster (I estimate about 10 times faster). How do I > tune? The wiki is not helpful for amd64 users stating that the defaults > should be optimal. I'm using the 8.1-stable version which has just been > installed this afternoon from a minimal install iso. > > I'm copying from a single ufs2 pata drive into a sata zpool mirror. I have > 2GB of ram. > > Top tells me: 761 MB Active, 790 Inactive and there is hardly any cpu usage > (96-98% idle). vfs.numvnodes: around 12500 now (after several hours of > copying) and stil slowly rising. For your system. /boot/loader.conf: # Increase vm.kmem_size to allow for ZFS ARC to utilise more memory. vm.kmem_size="2048M" vfs.zfs.arc_max="1024M" # Disable ZFS prefetching # http://southbrain.com/south/2008/04/the-nightmare-comes-slowly-zfs.html # Increases overall speed of ZFS, but when disk flushing/writes occur, # system is less responsive (due to extreme disk I/O). # NOTE: Systems with 8GB of RAM or more have prefetch enabled by # default. vfs.zfs.prefetch_disable="1" # Decrease ZFS txg timeout value from 30 (default) to 5 seconds. This # should increase throughput and decrease the "bursty" stalls that # happen during immense I/O with ZFS. # http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007343.html # http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007355.html vfs.zfs.txg.timeout="5" /etc/sysctl.conf: # Increase number of vnodes; we've seen vfs.numvnodes reach 115,000 # at times. Default max is a little over 200,000. Playing it safe... kern.maxvnodes=250000 # Set TXG write limit to a lower threshold. This helps "level out" # the throughput rate (see "zpool iostat"). A value of 256MB works well # for systems with 4GB of RAM, while 1GB works well for us w/ 8GB. # We're using 1GB here because of the ada3 disk which can really handle # a massive amount of write speed. vfs.zfs.txg.write_limit_override=1073741824 Note that the last entry in sysctl.conf may need to be adjusted, or commented out entirely. It's up to you. You can mess with this in real-time using sysctl. Google for vfs.zfs.txg.write_limit_override to get an idea of how to adjust it, if you want to. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 01:05:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6E211065670 for ; Wed, 29 Dec 2010 01:05:41 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 782E48FC14 for ; Wed, 29 Dec 2010 01:05:41 +0000 (UTC) Received: by fxm16 with SMTP id 16so9921333fxm.13 for ; Tue, 28 Dec 2010 17:05:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ypIf4lvvowxitZzOJqzqztoirDoOEFEb97rHiAZ8Su0=; b=eNhhO/rOUyBVqB6N20sPCr8AxO+xlZByqhpf/oC3KgotvApJPpBb5KJSR9kvCUUHP7 hrO4HxV6y0GJ1puZz8YWpvxLkJkiE3K9yqo1SPjdynH3ZYTtMGVYAE5LtMLAfFd79wQB VyOwA/C2cuOzZNSISS53XiBHTr1sPrUrLAYXA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=diwGez3gQWZdEyMAlC1Ie4heK8RTMlcsoCuP06VsHEs4s9vh6iGlplJW9Ir0D87mFX 1cCLYubKiIjtlnsd1MxSFT219A7Mnubf0HgAKS8cahcT49MLLVHmcAIs2v4rFuB+6G/e DnsfvKfLSI1rIOtHKiki8BNOvojKRZQwDXfKc= MIME-Version: 1.0 Received: by 10.223.106.129 with SMTP id x1mr1259454fao.13.1293584739490; Tue, 28 Dec 2010 17:05:39 -0800 (PST) Received: by 10.223.114.4 with HTTP; Tue, 28 Dec 2010 17:05:39 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Dec 2010 19:05:39 -0600 Message-ID: From: Adam Vande More To: Freek van Hemert Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 01:05:42 -0000 On Tue, Dec 28, 2010 at 5:56 PM, Freek van Hemert wrote: > Top tells me: 761 MB Active, 790 Inactive and there is hardly any cpu usage > (96-98% idle). vfs.numvnodes: around 12500 now (after several hours of > copying) and stil slowly rising. > > Hope you can help me. > I believe there were some zfs bugs/performance issues in 8.1 that were made more visible by having other file system types mounted simultaneously. Stuff like this: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/146410 This has been MFC'd so not sure why it's still open. -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 01:42:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19E5F106566B for ; Wed, 29 Dec 2010 01:42:29 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id C42928FC0C for ; Wed, 29 Dec 2010 01:42:28 +0000 (UTC) Received: by iyb26 with SMTP id 26so8900912iyb.13 for ; Tue, 28 Dec 2010 17:42:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=NiWgdEDvxFmwf1j2UCobATCqTkfvIWtu6XPZa+Rp5OI=; b=KftKWXBSlhnSxMxhZWA6qA4tkMGB1SZ9KcNSigH87o+iffhoS+pLw4Q8KyIsOrldVb SkxwiRGOQaOPWGWeA7TtALV6n5N0Dg+Z5YWaD1uzdOwj7yHjrzI4bO/ZdeuvMM9jbJU0 HnUdZlEyka+hAAM5GjoB7K6E0tMYz1+7vllKU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OKB32muWioZxyVDpgT2avlhozT125DmGtAK7ETmRGPhV2Mwf+bueSfT7nO1BHPNGwJ F7mQd9SDiIRbdmrM0BnXPoBUfiWIOx3wxW49nH0yf0ioq+0b+RRdrmo272U5TiOfkBQ9 4TX9F91sUdsx/4ilVHoDW49ilseRcoagLgGPQ= MIME-Version: 1.0 Received: by 10.42.218.3 with SMTP id ho3mr14280433icb.437.1293586947420; Tue, 28 Dec 2010 17:42:27 -0800 (PST) Received: by 10.42.101.209 with HTTP; Tue, 28 Dec 2010 17:42:27 -0800 (PST) In-Reply-To: <4D1A70B7.6090809@FreeBSD.org> References: <4D181E51.30401@DataIX.net> <4D1A70B7.6090809@FreeBSD.org> Date: Wed, 29 Dec 2010 12:42:27 +1100 Message-ID: From: Jean-Yves Avenard To: Martin Matuska Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-stable@freebsd.org" Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 01:42:29 -0000 Hi On Wednesday, 29 December 2010, Martin Matuska wrote: > Please don't consider these patches as production-ready. > What we want to do is find and resolve as many bugs as possible. > > To help us fix these bugs, a way to reproduce the bug from a clean start > (e.g. in virtualbox) would be great and speed up finding the cause for > the problem. > > Your problem looks like some sort of deadlock. In your case, when you > experiene the hang, try running "procstat -k -k PID" in another shell > (console). That will give us valuable information. > I am away until next week now (hopefully no problem will occur until then) I will try reproduce the issue then. I have to say that v28 massively increased write performance over samba, over 3 times than when v14 or v15. How do you disable ZIL with v28? I wanted to test performance in the case I'm trying to qtroubleshoot. Writing our file over samba, V14-v15: 55s V14-v15 zip disabled: 6s V28: 16s.. (with or without separate log drive: SSD Intel X25-m 40GB). Playing with the only zil parameter showing in sysctl, made no difference whatsoever. UFS boot drive: 14s sequential read shows over 280MB/s from that raidz array, similar with writes I started a thread in the freebsd forum: http://forums.freebsd.org/showthread.php?t=20476 And finally, which patch should I try on your site? Thanks From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 01:59:20 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 531F4106566B for ; Wed, 29 Dec 2010 01:59:20 +0000 (UTC) (envelope-from ca+envelope@esmtp.org) Received: from zardoc.esmtp.org (zardoc.esmtp.org [70.36.157.240]) by mx1.freebsd.org (Postfix) with ESMTP id 2EDD48FC17 for ; Wed, 29 Dec 2010 01:59:19 +0000 (UTC) Received: from quiet.esmtp.org (localhost. [127.0.0.1]) by zardoc.esmtp.org (MeTA1-1.0.PreAlpha41.0) with ESMTPS (TLS=TLSv1/SSLv3, cipher=AES256-SHA, bits=256, verify=OK) id S0000000000027FBB00; Tue, 28 Dec 2010 17:49:18 -0800 Received: (from ca@localhost) by quiet.esmtp.org (8.14.3/8.12.10.Beta0/Submit) id oBT1nIbF014434 for freebsd-stable@freebsd.org; Tue, 28 Dec 2010 17:49:18 -0800 (PST) Date: Tue, 28 Dec 2010 17:49:18 -0800 From: Claus Assmann To: freebsd-stable@freebsd.org Message-ID: <20101229014918.GA8274@quiet.esmtp.org> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-08-27) Subject: 8.2-RC1: installer does not recognize some disks properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2010 01:59:20 -0000 I just tried to install 8.2-RC1 (amd64) on one of my machines. It has two disks: WDC WD1001FALS-4 and SAMSUNG HD103SJ, both 1TB SATA disks. The installer shows them as ad10 and ad8. Both disks are already in use and have been "formatted" via fdisk, e.g., the Samsung (ad10) has 3 partitions (BF, A9, A8)) and the WDC has 4 (A6, BF, A5, A9). However, the installer only shows the existing partitions for the Samsung, but not for the WDC. The WDC is the boot disk and has a Grub loader installed. What could be the reason that the existing partitioning is not recognized by the installer? Here is some data from the system after I installed it on the second disk: fdisk ad8 ******* Working on device /dev/ad8 ******* parameters extracted from in-core disklabel are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 166 (0xa6),(OpenBSD) start 64, size 530161001 (258867 Meg), flag 0 beg: cyl 0/ head 1/ sector 2; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 191 (0xbf),(Solaris x86 (new)) start 530161065, size 626535000 (305925 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 1156696065, size 449820000 (219638 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 255/ sector 63 The data for partition 4 is: sysid 169 (0xa9),(NetBSD) start 1606516065, size 347004000 (169435 Meg), flag 0 beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 This shows that FreeBSD recognizes the partitions properly. I ran sysinstall from the command lines (under script) and got this (after removing all the screen layout sequences): ---------------------------------------------------------------------- Disk name: ad8 FDISK Partition Editor DISK Geometry: 1938021 cyls/16 heads/63 sectors = 1953525168 sectors (953869MB) Offset Size(ST) End Name PType Desc Subtype Flags 0 1953525168 1953525167 - 12 unused 0 The following commands are supported (in upper or lower case): ---------------------------------------------------------------------- As you see, sysinstall shows something else than fdisk. The outpuf of dmesg is below. Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RC1 #0: Wed Dec 22 17:34:20 UTC 2010 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) II X6 1055T Processor (2812.48-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100fa0 Family = 10 Model = a Stepping = 0 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8243384320 (7861 MB) ACPI APIC Table: <032510 APIC1318> FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <032510 XSDT1318> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee00000, 1000 (3) failed acpi0: reservation of ffb80000, 80000 (3) failed acpi0: reservation of fec10000, 20 (3) failed acpi0: reservation of fed40000, 5000 (3) failed acpi0: reservation of fed80000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cfe00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 18 at device 2.0 on pci0 pci1: on pcib1 vgapci0: mem 0xfd000000-0xfdffffff,0xd0000000-0xdfffffff,0xfc000000-0xfcffffff irq 18 at device 0.0 on pci1 pcib2: irq 18 at device 6.0 on pci0 pci2: on pcib2 em0: port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff irq 18 at device 0.0 on pci2 em0: Using MSIX interrupts with 3 vectors em0: [ITHREAD] em0: [ITHREAD] em0: [ITHREAD] em0: Ethernet address: 00:1b:21:78:d3:36 pcib3: irq 17 at device 9.0 on pci0 pci3: on pcib3 atapci0: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f irq 17 at device 0.0 on pci3 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] pcib4: irq 18 at device 10.0 on pci0 pci4: on pcib4 re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaffffff,0xfaff8000-0xfaffbfff irq 18 at device 0.0 on pci4 re0: Using 1 MSI messages re0: Chip rev. 0x2c000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: e0:cb:4e:cf:4a:00 re0: [FILTER] atapci1: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfbfffc00-0xfbffffff irq 19 at device 17.0 on pci0 atapci1: [ITHREAD] atapci1: AHCI v1.20 controller with 6 6Gbps ports, PM supported ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] ata9: on atapci1 ata9: [ITHREAD] ohci0: mem 0xfbffe000-0xfbffefff irq 18 at device 18.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 ehci0: mem 0xfbfff800-0xfbfff8ff irq 17 at device 18.2 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 ohci1: mem 0xfbffd000-0xfbffdfff irq 18 at device 19.0 on pci0 ohci1: [ITHREAD] usbus2: on ohci1 ehci1: mem 0xfbfff400-0xfbfff4ff irq 17 at device 19.2 on pci0 ehci1: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci1 pci0: at device 20.0 (no driver attached) pci0: at device 20.2 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib5: at device 20.4 on pci0 pci5: on pcib5 ohci2: mem 0xfbffc000-0xfbffcfff irq 18 at device 20.5 on pci0 ohci2: [ITHREAD] usbus4: on ohci2 ohci3: mem 0xfbff3000-0xfbff3fff irq 18 at device 22.0 on pci0 ohci3: [ITHREAD] usbus5: on ohci3 ehci2: mem 0xfbfff000-0xfbfff0ff irq 17 at device 22.2 on pci0 ehci2: [ITHREAD] usbus6: EHCI version 1.0 usbus6: on ehci2 acpi_button0: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 ppc1: port 0x378-0x37f irq 5 on acpi0 ppc1: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppc1: [ITHREAD] ppbus0: on ppc1 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 acpi_hpet1: iomem 0xfed00000-0xfed003ff on acpi0 device_attach: acpi_hpet1 attach returned 12 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] orm0: at iomem 0xd1800-0xd27ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: cannot reserve I/O port range acpi_throttle0: on cpu0 hwpstate0: on cpu0 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 acd0: DVDR at ata2-master UDMA33 ad8: 953869MB at ata4-master UDMA100 SATA 3Gb/s ad10: 953869MB at ata5-master UDMA100 SATA 3Gb/s SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #4 Launched! uhub4: 2 ports with 2 removable, self powered uhub5: 4 ports with 4 removable, self powered uhub0: 5 ports with 5 removable, self powered uhub2: 5 ports with 5 removable, self powered Root mount waiting for: usbus6 usbus3 usbus1 uhub6: 4 ports with 4 removable, self powered Root mount waiting for: usbus3 usbus1 uhub1: 5 ports with 5 removable, self powered uhub3: 5 ports with 5 removable, self powered Root mount waiting for: usbus1 ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 uhub_reattach_port: port 3 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 3 Trying to mount root from ufs:/dev/ad10s2a ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 uhub_reattach_port: port 4 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 4 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 04:22:58 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9420106566B for ; Wed, 29 Dec 2010 04:22:58 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9D5EE8FC12 for ; Wed, 29 Dec 2010 04:22:58 +0000 (UTC) Received: by iyb26 with SMTP id 26so8972362iyb.13 for ; Tue, 28 Dec 2010 20:22:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yGSfrwIiCAEHLMyCfP72Ao6OYshDF68kqtaMKuW10GU=; b=Qml+ZYeEmhR/9yzCHp3y/qj57sCWBdxmipIxQ/qdiTV+pLjdPOu1JJgX1rw/eXw7lM TJP0+Jg553c+0JG4ZjqcQ5RfWPJ378dvvm7l2Kl1tjVSbdBlXynMXU9zJmvtPaZp0ClS Vfif8dFOzyHCDzvweNS0ErjY33+T3CFJcGaBE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Sn1uBF3xt3j4hRy7JmshYLx2krt3B6sLdgHMIPF0ok8USL5sjey9iypVbkdtMIIr/7 zxfzRveyG6U4P9+UakZW1ScliYBuPA5H30NTKqUgg9JiOj+vTRZCEFlA9VkbbjPNfmYy Am+FwcOgmfIprpmXB0oytbZ3dzmcjZtF16In4= MIME-Version: 1.0 Received: by 10.231.169.74 with SMTP id x10mr14045627iby.26.1293595228111; Tue, 28 Dec 2010 20:00:28 -0800 (PST) Received: by 10.231.172.69 with HTTP; Tue, 28 Dec 2010 20:00:28 -0800 (PST) In-Reply-To: <201012281123.53669.jhb@freebsd.org> References: <4BCE4D0F.2020807@quip.cz> <201012130824.33968.jhb@freebsd.org> <4D15D8DD.9010900@quip.cz> <201012281123.53669.jhb@freebsd.org> Date: Tue, 28 Dec 2010 20:00:28 -0800 Message-ID: From: Matthew Fleming To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 04:22:58 -0000 On Tue, Dec 28, 2010 at 8:23 AM, John Baldwin wrote: > On Saturday, December 25, 2010 6:43:25 am Miroslav Lachman wrote: >> John Baldwin wrote: >> > On Saturday, December 11, 2010 11:51:41 am Miroslav Lachman wrote: >> >> Miroslav Lachman wrote: >> >>> Garrett Cooper wrote: >> >>>> 2010/4/20 Miroslav Lachman<000.fbsd@quip.cz>: >> >>>>> I have large storage partition (/vol0) mounted as noexec and nosui= d. >> >>>>> Then >> >>>>> one directory from this partition is mounted by nullfs as "exec an= d >> >>>>> suid" so >> >>>>> anything on it can be executed. >> >>>>> >> >>>>> The directory contains full installation of jail. Jail is running >> >>>>> fine, but >> >>>>> some ports (PHP for example) cannot be compiled inside the jail wi= th >> >>>>> message: >> >>>>> >> >>>>> /libexec/ld-elf.so.1: Cannot execute objects on / >> >>>>> >> >>>>> The same apply to executing of apxs >> >>>>> >> >>>>> root@rainnew ~/# /usr/local/sbin/apxs -q MPM_NAME >> >>>>> /libexec/ld-elf.so.1: Cannot execute objects on / >> >>>>> >> >>>>> apxs:Error: Sorry, no shared object support for Apache. >> >>>>> apxs:Error: available under your platform. Make sure. >> >>>>> apxs:Error: the Apache module mod_so is compiled into. >> >>>>> apxs:Error: your server binary '/usr/local/sbin/httpd'.. >> >>>>> >> >>>>> (it should return "prefork") >> >>>>> >> >>>>> So I think there is some bug in checking the mountpoint options, >> >>>>> where the >> >>>>> check is made on "parent" of the nullfs instead of the nullfs targ= et >> >>>>> mountpoint. >> >>>>> >> >>>>> It is on 6.4-RELEASE i386 GENERIC. I did not test it on another re= lease. >> >>>>> >> >>>>> This is list of related mount points: >> >>>>> >> >>>>> /dev/mirror/gm0s2d on /vol0 (ufs, local, noexec, nosuid, soft-upda= tes) >> >>>>> /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local) >> >>>>> /usr/ports on /vol0/jail/rain_new/usr/ports (nullfs, local) >> >>>>> devfs on /vol0/jail/rain_new/dev (devfs, local) >> >>>>> >> >>>>> If I changed /vol0 options to (ufs, local, soft-updates) the above >> >>>>> error is >> >>>>> gone and apxs / compilation works fine. >> >>>>> >> >>>>> Can somebody look at this problem? >> >>>> >> >>>> Can you please provide output from ktrace / truss for the issue? >> >>> >> >>> I did >> >>> # ktrace /usr/local/sbin/apxs -q MPM_NAME >> >>> >> >>> The output is here http://freebsd.quip.cz/ld-elf/ktrace.out >> >>> >> >>> Let me know if you need something else. >> >>> >> >>> Thank you for your interest! >> >> >> >> The problem is still there in FreeBSD 8.1-RELEASE amd64 GENERIC (and = in >> >> 7.x). >> >> >> >> Can somebody say if this is a bug or an expected "feature"? >> > >> > I think this is the expected behavior as nullfs is simply re-exposing = /vol0 >> > and it shouldn't be able to create a more privileged mount than the un= derlying >> > mount I think (e.g. a read/write nullfs mount of a read-only filesyste= m would >> > not make the underlying files read/write). =A0It can be used to provid= e less >> > privilege (e.g. a readonly nullfs mount of a read/write filesystem doe= s not >> > allow writes via the nullfs layer). >> > >> > That said, I'm not sure exactly where the permission check is failing. >> > execve() only checks MNT_NOEXEC on the "upper" vnode's mountpoint (i.e= . the >> > nullfs mountpoint) and the VOP_ACCESS(.., V_EXEC) check does not look = at >> > MNT_NOEXEC either. >> > >> > I do think there might be bugs in that a nullfs mount that specifies n= oexec or >> > nosuid might not enforce the noexec or nosuid bits if the underlying m= ount >> > point does not have them set (from what I can see). >> >> Thank you for your explanation. Then it is strange, that there is bug, >> that allows execution on originally non executable mountpoint. >> It should be mentioned in the bugs section of the mount_nullfs man page. >> >> It would be useful, if 'mount' output shows inherited options for nullfs= . >> >> If parent is: >> /dev/mirror/gm0s2d on /vol0 (ufs, local, noexec, nosuid, soft-updates) >> >> Then nullfs line will be: >> /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local, noexec, >> nosuid) >> >> instead of just >> /vol0/jail/.nullfs/rain on /vol0/jail/rain_new (nullfs, local) >> >> >> Then I can understand what is expected behavior, but our current state >> is half working, if I can execute scripts and binaries, run jail on it, >> but can't execute "apxs -q MPM_NAME" and few others. > > Hmm, so I was a bit mistaken. =A0The kernel is not failing to exec the bi= nary. > Instead, rtld is reporting the error here: > > static Obj_Entry * > do_load_object(int fd, const char *name, char *path, struct stat *sbp, > =A0int flags) > { > =A0 =A0Obj_Entry *obj; > =A0 =A0struct statfs fs; > > =A0 =A0/* > =A0 =A0 * but first, make sure that environment variables haven't been > =A0 =A0 * used to circumvent the noexec flag on a filesystem. > =A0 =A0 */ > =A0 =A0if (dangerous_ld_env) { > =A0 =A0 =A0 =A0if (fstatfs(fd, &fs) !=3D 0) { > =A0 =A0 =A0 =A0 =A0 =A0_rtld_error("Cannot fstatfs \"%s\"", path); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return NULL; > =A0 =A0 =A0 =A0} > =A0 =A0 =A0 =A0if (fs.f_flags & MNT_NOEXEC) { > =A0 =A0 =A0 =A0 =A0 =A0_rtld_error("Cannot execute objects on %s\n", fs.f= _mntonname); > =A0 =A0 =A0 =A0 =A0 =A0return NULL; > =A0 =A0 =A0 =A0} > =A0 =A0} > > I wonder if the fstatfs is falling down to the original mount rather than > being caught by nullfs. > > Hmm, nullfs' statfs method returns the flags for the underlying mount, no= t > the flags for the nullfs mount. =A0This is possibly broken, but it is the > behavior nullfs has always had and the behavior it still has on other BSD= s. Not sure if it's relevant here but we fixed a bug locally that I still need to upstream, where NFS is putting another flags word here and incorrectly reporting MNT_NOEXEC. Unfortunately I'm on vacation so I can't easily look it up but there are very few lines in NFS that set f_flags. Thanks, matthew From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 05:02:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C72781065693; Wed, 29 Dec 2010 05:02:08 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 641F78FC14; Wed, 29 Dec 2010 05:02:08 +0000 (UTC) Received: by gxk8 with SMTP id 8so4386102gxk.13 for ; Tue, 28 Dec 2010 21:02:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=HupFettBsOtHWIfUAG6ZPG3TIZ06WQ6BQT9m0b347aI=; b=n3IwVIwbi1CXjsJzzUyyW5D5OsLqMx3yJvvF29+uDGyOKlQo8EqSzxM8hpDOxqVf71 JWR58iy1mzK4ZtWtzImziRw+8MjA7iILCkO8/qjxKvPnqaaDE5TJHEcWrZAbk0QhSqD0 YkZfvnRiDyRBfGBXPpjQf3Gb7appwqTaG8KKc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=Ynj/q2VERyeIqZa4EdtUY58twwpoAu049MJfK0Dmm0YByDw8ayXvj41+sWqfpXdEhW 7+8gCg+EXunotTuFTLOxlreHe3z/HkDSV1b7WDmM3pII5ZByIBaQNy5pRzB265KEoMcs RAC7/TuLdGyfISLIr/oG/S81nPR6jYjlBww8c= Received: by 10.236.105.205 with SMTP id k53mr1379103yhg.58.1293598927386; Tue, 28 Dec 2010 21:02:07 -0800 (PST) Received: from centel.dataix.local (adsl-99-181-145-144.dsl.klmzmi.sbcglobal.net [99.181.145.144]) by mx.google.com with ESMTPS id v8sm7781900yhg.40.2010.12.28.21.02.05 (version=SSLv3 cipher=RC4-MD5); Tue, 28 Dec 2010 21:02:06 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D1AC0CC.7020907@DataIX.net> Date: Wed, 29 Dec 2010 00:02:04 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Martin Matuska References: <4D181E51.30401@DataIX.net> <4D1A70B7.6090809@FreeBSD.org> In-Reply-To: <4D1A70B7.6090809@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jean-Yves Avenard Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 05:02:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/28/2010 18:20, Martin Matuska wrote: > Please don't consider these patches as production-ready. > What we want to do is find and resolve as many bugs as possible. I completely agree with Martin here. If your running it then your willing to loose what you have if you have not taken precaution to save your data somewhere else. Even though with that said ZFS does a pretty fine job of ensuring that nothing happens to it, it is still best practice to have a copy somewhere other than "IN THAT BOX" ;) Another note too, I think I read that you mentioned using the L2ARC and slog device on the same disk.... You simply shouldn't do this it could be contributing to the real cause and there is absolutely no gain in either sanity or performance and you will end up bottle-necking your system. > > To help us fix these bugs, a way to reproduce the bug from a clean start > (e.g. in virtualbox) would be great and speed up finding the cause for > the problem. > > Your problem looks like some sort of deadlock. In your case, when you > experiene the hang, try running "procstat -k -k PID" in another shell > (console). That will give us valuable information. > Martin, I agree with the above that it may be some sort of live or dead lock problem in this case. It would be awesome to know if some of the following sysctl(8)'s values are and how this reacts when set to the opposite of their current values. vfs.zfs.l2arc_noprefetch: vfs.zfs.dedup.prefetch: vfs.zfs.prefetch_disable The reason why I say this is on one of my personal systems that I toy with the box cannot make it very long with prefetch enabled on either v15 or v28 after some 'unknown' commit to world on stable/8. Now this may actually be just a contributing factor that makes it happen sooner than it normally would but probably also directly relates to the exact problem. I would love to see this go away as I had been using the L2ARC with prefetch enabled for a long time and now all of a sudden just plainly does not work correctly. I also have about 19 core.txt.NN files from when this started happening with various stack traces. If you would like these just let me know and Ill privately mail them to you. Regards, - -- jhell,v - JJH48-ARIN -----BEGIN PGP SIGNATURE----- iQEbBAEBAgAGBQJNGsDLAAoJEJBXh4mJ2FR+TqkH8wVFQKiU/C6L+F4Y3/ClScQD b4s0IkC1B+bHl9eD6Hhxif/1iKj1w9clYvuLt8ageDF98KTB9GCRjuh48VswdtPQ FQtDRTj1pGzWPxmOn2Nrf7qrFnymqZk+qoTBX8A1nDvrSe41Mqp82ue9E7nZ1ipg Dz9k5F8J+WxUAZYLHxtxLvYEa19/hvG1K5LOpRKIU0iycsqaywezFflTGDcR5lT8 A50ic9sZ21jr87CK45TLv1Wmu+kDgpy2j1x77bYTDGoAzQMlPcOENO8st8EobcWB eIwwXIjtRwOKF4rSxoqwwYxOM4ek+tK4p6ZnO1uLipNXMB+zJTjs//GV6Xp3TA== =Io4+ -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 08:38:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 340501065672 for ; Wed, 29 Dec 2010 08:38:43 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0D28FC08 for ; Wed, 29 Dec 2010 08:38:42 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id oBT8cdAt017095 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 29 Dec 2010 08:38:40 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 smtp.infracaninophile.co.uk oBT8cdAt017095 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1293611920; bh=L/1UmTlN7ZzbyJaWTyR+YfDGdNr4J7CIAgwXo9AdQj0=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Cc:Content-Type:Date:From:In-Reply-To: Message-ID:Mime-Version:References:To; z=Message-ID:=20<4D1AF388.3080107@infracaninophile.co.uk>|Date:=20W ed,=2029=20Dec=202010=2008:38:32=20+0000|From:=20Matthew=20Seaman= 20|User-Agent:=20Mozilla/5.0=20(M acintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20en-US=3B=20r v:1.9.2.13)=20Gecko/20101207=20Thunderbird/3.1.7|MIME-Version:=201 .0|To:=20freebsd-stable@freebsd.org|Subject:=20Re:=20slow=20ZFS=20 on=20FreeBSD=208.1|References:=20|In-Reply-To:=20|X-Enigmail-Version:=201. 1.1|OpenPGP:=20id=3D60AE908C|Content-Type:=20multipart/signed=3B=2 0micalg=3Dpgp-sha1=3B=0D=0A=20protocol=3D"application/pgp-signatur e"=3B=0D=0A=20boundary=3D"------------enig09AC943CBD333172A390312A "; b=veMh6Fg8wc6ELtqgRmAzx0zGqLNQKQesgM2k2P4UmNqYVOBrRMOTwumOIy9rg2lYf CSYN3A8Gq6HMpkNnWwtD/aDSMsUKZ8VWrjzdZXVnxLV7XX8s87L8WTcfTkpgscAef3 p12Rn1/3jFg0m51rBhoNDyXzv6X0sMYwWMZKFCV4= Message-ID: <4D1AF388.3080107@infracaninophile.co.uk> Date: Wed, 29 Dec 2010 08:38:32 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig09AC943CBD333172A390312A" X-Virus-Scanned: clamav-milter 0.96.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 08:38:43 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig09AC943CBD333172A390312A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 28/12/2010 23:56, Freek van Hemert wrote: > I have a question regarding zfs on freebsd. > (I'm making a home server) > This afternoon I did a "zpool create data mirror ad4 ad6" Now I'm copyi= ng > things from my ufs2 disk into the 2TB zpool, it is very slow. I'm on fr= eebsd > 8.1 amd64 on an atom n330 with 2 sata disks, gstat tells me I'm going a= t > around 2 mbps at near 100 %busy while the ufs2 drives are near 0. Also= , > ufs2 to ufs2 was much faster (I estimate about 10 times faster). How do= I > tune? The wiki is not helpful for amd64 users stating that the defaults= > should be optimal. I'm using the 8.1-stable version which has just been= > installed this afternoon from a minimal install iso. Upgrade to one of the 8.2 release candidates or to a recent RELENG_8 / stable/8 -- there has been serious work done on ZFS since 8.1-RELEASE including the import of ZFS v15, and it is a lot more performant. Or wait a few weeks and then upgrade to 8.2-RELEASE. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig09AC943CBD333172A390312A 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 Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0a848ACgkQ8Mjk52CukIwd5gCfbVjGc+6ayr0vW10I01rPIUW7 uOAAnivSlVXSJgCbCy6++ZI1ozrQK6NU =ndoa -----END PGP SIGNATURE----- --------------enig09AC943CBD333172A390312A-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 08:57:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0CB51065670 for ; Wed, 29 Dec 2010 08:57:41 +0000 (UTC) (envelope-from fvhemert@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 695DC8FC13 for ; Wed, 29 Dec 2010 08:57:41 +0000 (UTC) Received: by yie19 with SMTP id 19so2212620yie.13 for ; Wed, 29 Dec 2010 00:57:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=jm9L+7HO+O+CwJecrWSpQK4s7pPUy4/eIrAw47cO/HA=; b=i4GCtthq2winPi8R0FPdykM8ZnqSzewEVB5UQX7jV7u1oLs0WNkz/q9JeIZcG/UUPK tvwJnJEaH7FLE/BHkfvC0xscnLmFeKBkpeTP33DzjoZAuJLjdZeFfjRPnj7Tl829raZR dO1tL/L05w+1hm6+F01+9EDt7OEk/Nc0mIFJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YHfohafReScfpP6M5qioRoNUR5m7jDr6VhWxQUDIJQZA6/6EdGdNeQI1LmMCIyzfhl x44Z3qSc+rH5YtmODABLDaasA3ZkBfp+YnfDoX6HviBrdwVzwleoLvMNBdmhxhSI09Kj aN1jqU+YoJVTdW77WHYh8Jz+n/r38LaHSnUKQ= MIME-Version: 1.0 Received: by 10.100.164.1 with SMTP id m1mr8393198ane.269.1293613060631; Wed, 29 Dec 2010 00:57:40 -0800 (PST) Received: by 10.101.5.31 with HTTP; Wed, 29 Dec 2010 00:57:40 -0800 (PST) In-Reply-To: <4D1AF388.3080107@infracaninophile.co.uk> References: <4D1AF388.3080107@infracaninophile.co.uk> Date: Wed, 29 Dec 2010 09:57:40 +0100 Message-ID: From: Freek van Hemert To: Matthew Seaman Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 08:57:41 -0000 Thanx for all the replies. The hacks sounds good until 8.2 is released however, regarding this upgrade, is the on-disk format the same? Can I just add the pool to a new install (of 8.2-RC) and expect higher performance? Or do I need to recreate the pool with the newer versions of the utilities? On 29 December 2010 09:38, Matthew Seaman wrote: > On 28/12/2010 23:56, Freek van Hemert wrote: > > I have a question regarding zfs on freebsd. > > (I'm making a home server) > > This afternoon I did a "zpool create data mirror ad4 ad6" Now I'm copying > > things from my ufs2 disk into the 2TB zpool, it is very slow. I'm on > freebsd > > 8.1 amd64 on an atom n330 with 2 sata disks, gstat tells me I'm going at > > around 2 mbps at near 100 %busy while the ufs2 drives are near 0. Also, > > ufs2 to ufs2 was much faster (I estimate about 10 times faster). How do I > > tune? The wiki is not helpful for amd64 users stating that the defaults > > should be optimal. I'm using the 8.1-stable version which has just been > > installed this afternoon from a minimal install iso. > > Upgrade to one of the 8.2 release candidates or to a recent RELENG_8 / > stable/8 -- there has been serious work done on ZFS since 8.1-RELEASE > including the import of ZFS v15, and it is a lot more performant. > > Or wait a few weeks and then upgrade to 8.2-RELEASE. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW > > From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 09:27:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB752106566B; Wed, 29 Dec 2010 09:27:56 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 81AA98FC08; Wed, 29 Dec 2010 09:27:56 +0000 (UTC) Received: by iwn39 with SMTP id 39so10132772iwn.13 for ; Wed, 29 Dec 2010 01:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=bpY3IlSTs6ZA6lsypdvYaSR6MA3d+UsZOrlANU3UEUY=; b=OmIS4J/JYbtPg/j8JoutoLk9iW8sA7VqcnDoTtElCwFs8XQ4juPubr6HiFsgznL5+H ZKgMAJ4wunrj3pHgdt94Ii8M+wJHil1TAiMWWjTgqPxWn6YDMYZ3nVFWiaXrT/WQg4hK ih7gJwmDlakRiBUbNi3ZpEkb080rGq5ZFnPiE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=P3KVeuIwmE03x67q/9PDwp0NMnpfEBakuF/cL5XcI21xOZAfkYSuVR6qIJTwv914/F 6v8WswwB00BnqdPU52yqHJxZCcI2s9DlYNue7AiV3JtE6I0RHclnpaCv+Maq491It8yJ dCrmBKzdS/aufj6JM6StDz4JBSefUx0z2XdyE= MIME-Version: 1.0 Received: by 10.42.167.66 with SMTP id r2mr14667874icy.303.1293614875865; Wed, 29 Dec 2010 01:27:55 -0800 (PST) Received: by 10.42.101.209 with HTTP; Wed, 29 Dec 2010 01:27:55 -0800 (PST) In-Reply-To: <4D1AC0CC.7020907@DataIX.net> References: <4D181E51.30401@DataIX.net> <4D1A70B7.6090809@FreeBSD.org> <4D1AC0CC.7020907@DataIX.net> Date: Wed, 29 Dec 2010 20:27:55 +1100 Message-ID: From: Jean-Yves Avenard To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-stable@freebsd.org" , Martin Matuska Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 09:27:57 -0000 On Wednesday, 29 December 2010, jhell wrote: > > Another note too, I think I read that you mentioned using the L2ARC and > slog device on the same disk.... You simply shouldn't do this it could > be contributing to the real cause and there is absolutely no gain in > either sanity or performance and you will end up bottle-necking your system. > >> And why would that be? I've read so many conflictinginformation on the matter over the past few days that I'm starting to wonder if there's an actual definitive answer on the matter or if anyone has a clue regarding what they're talking about. It ranges from, should only use raw disk to freebsd isn't solaris so slices are fine. Don't use slice because they can't be read by another OS use partitions.. It doesn't apply to SSD and so on.. The way I look at it, the only thing that would bottleneck access to that SSD drive, is the SATA interface itself. So using two drives, or two partitions on the same drive, I can't see how it would make much difference if any other than the traditional "I think I know" argument. Surely latency as with know it with hard drive do not apply to SSDs. Even within sun's official documentation, they are contradicting information, starting from the commands on how to add remove/cache of log device. It seems to me that tuning ZFS is very much like black magic, everyone has their own idea about what to do, and not once did I get to read conclusive evidence about what is best or find an information people actually agree on. As for using unofficial code, sure I accept that risk now. I made a conscious decision on using it, there's now no way to go back and I accept that. At the end of the day, it's the only thing that will make that code suitable for real world condition: testing. If that particular code isn't put under any actual stress how else are you going to know if its good or not. I don't really like reading between the lines of your post that I shouldn't be surprised should anything break or that it doesn't matter if it crashes. there's a deadlock occurring somewhere : it needs to be found. I know nothing about the ZFS code, and I could only do what I'm capable of under those circumstances: find a way to reproduce the problem consistently, report as much information as I have so someone more clueey will know what to do with it. Hope that makes sense Jean-Yves From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 11:15:14 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 946C5106566B for ; Wed, 29 Dec 2010 11:15:14 +0000 (UTC) (envelope-from maulwurf@guckux.de) Received: from artif-webmail.de (artif-webmail.de [188.40.35.67]) by mx1.freebsd.org (Postfix) with ESMTP id 566A08FC0C for ; Wed, 29 Dec 2010 11:15:14 +0000 (UTC) Received: from artif-webmail.de (localhost [127.0.0.1]) by artif-webmail.de (Postfix) with ESMTP id 88AE9228E07A; Wed, 29 Dec 2010 11:55:57 +0100 (CET) Received: from 195.185.213.162 (SquirrelMail authenticated user huerter) by artif-webmail.de with HTTP; Wed, 29 Dec 2010 11:55:57 +0100 Message-ID: <6435f8322a5d1045d20c7a782d85f846.squirrel@artif-webmail.de> In-Reply-To: References: <4D1AF388.3080107@infracaninophile.co.uk> Date: Wed, 29 Dec 2010 11:55:57 +0100 From: "Stefan Huerter" To: "Freek van Hemert" User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 11:15:14 -0000 Guckux Freek > The hacks sounds good until 8.2 is released however, regarding this > upgrade, > is the on-disk format the same? Can I just add the pool to a new install > (of > 8.2-RC) and expect higher performance? Or do I need to recreate the pool > with the newer versions of the utilities? just do an upgrade of zfs... "zpool upgrade" Bye Stefan From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 13:06:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F683106564A for ; Wed, 29 Dec 2010 13:06:41 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id C61258FC1B for ; Wed, 29 Dec 2010 13:06:40 +0000 (UTC) Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 578901495; Wed, 29 Dec 2010 14:06:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received; s=mail; t=1293627991; x= 1295442391; bh=aaIxLHGx1sx5+gBlS5t1Y/odkcSsnY0O1plNwjxKAzw=; b=e HX3spI+5OG6jzpW0PbEoW+wqvblog35Oc39ZT/D5k5FvPHsv0i4wvgRcY+aq3H+E +3q0jOZHTqXhXaRaQWlKy0XFhyzjfwx3yNLptSLKqo3KFtskrj2qd+M0iQDLY1b2 sS95/oW2rzW0zetuQkv3AnAAOyqz/wWopDQHop6iCo= X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by megatron.madpilot.net (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RKliAwbhHyIn; Wed, 29 Dec 2010 14:06:31 +0100 (CET) Received: by megatron.madpilot.net (Postfix, from userid 1000) id B2FB31489; Wed, 29 Dec 2010 14:06:31 +0100 (CET) Date: Wed, 29 Dec 2010 14:06:31 +0100 From: Guido Falsi To: Stefan Huerter Message-ID: <20101229130631.GB41011@megatron.madpilot.net> References: <4D1AF388.3080107@infracaninophile.co.uk> <6435f8322a5d1045d20c7a782d85f846.squirrel@artif-webmail.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6435f8322a5d1045d20c7a782d85f846.squirrel@artif-webmail.de> X-Operating-System: FreeBSD 8.1-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Freek van Hemert , freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 13:06:41 -0000 On Wed, Dec 29, 2010 at 11:55:57AM +0100, Stefan Huerter wrote: > Guckux Freek > > > The hacks sounds good until 8.2 is released however, regarding this > > upgrade, > > is the on-disk format the same? Can I just add the pool to a new install > > (of > > 8.2-RC) and expect higher performance? Or do I need to recreate the pool > > with the newer versions of the utilities? > > just do an upgrade of zfs... > "zpool upgrade" He'll need a "zfs upgrade" too. -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 16:00:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DA841065675 for ; Wed, 29 Dec 2010 16:00:18 +0000 (UTC) (envelope-from xaero@xaerolimit.net) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id D84AF8FC14 for ; Wed, 29 Dec 2010 16:00:17 +0000 (UTC) Received: by ewy24 with SMTP id 24so4997180ewy.13 for ; Wed, 29 Dec 2010 08:00:16 -0800 (PST) Received: by 10.213.106.11 with SMTP id v11mr5660292ebo.38.1293636710713; Wed, 29 Dec 2010 07:31:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.28.148 with HTTP; Wed, 29 Dec 2010 07:31:30 -0800 (PST) In-Reply-To: <20101229014918.GA8274@quiet.esmtp.org> References: <20101229014918.GA8274@quiet.esmtp.org> From: Chris Brennan Date: Wed, 29 Dec 2010 10:31:30 -0500 Message-ID: To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 8.2-RC1: installer does not recognize some disks properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 16:00:18 -0000 On Tue, Dec 28, 2010 at 8:49 PM, Claus Assmann > wrote: > I just tried to install 8.2-RC1 (amd64) on one of my machines. It > has two disks: WDC WD1001FALS-4 and SAMSUNG HD103SJ, both 1TB SATA > disks. The installer shows them as ad10 and ad8. Both disks are > already in use and have been "formatted" via fdisk, e.g., the Samsung > (ad10) has 3 partitions (BF, A9, A8)) and the WDC has 4 (A6, BF, > A5, A9). However, the installer only shows the existing partitions > for the Samsung, but not for the WDC. The WDC is the boot disk and > has a Grub loader installed. What could be the reason that the > existing partitioning is not recognized by the installer? > I've got a similar issue via the thread about a 2y/o laptop and a new hard drive. Linux sees the drive fine and can use it but freebsd cannot for some reason. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 17:47:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 680781065698 for ; Wed, 29 Dec 2010 17:47:41 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id C01308FC14 for ; Wed, 29 Dec 2010 17:47:40 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id oBTHlb7D020629 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 29 Dec 2010 17:47:37 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 smtp.infracaninophile.co.uk oBTHlb7D020629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1293644857; bh=YJ0F72no+QN9mYUG4e4CFKPflKFTXBvH/QQ7nKRv5Nw=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Cc:Content-Type:Date:From:In-Reply-To: Message-ID:Mime-Version:References:To; z=Message-ID:=20<4D1B7431.7070808@infracaninophile.co.uk>|Date:=20W ed,=2029=20Dec=202010=2017:47:29=20+0000|From:=20Matthew=20Seaman= 20|User-Agent:=20Mozilla/5.0=20(M acintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20en-US=3B=20r v:1.9.2.13)=20Gecko/20101207=20Thunderbird/3.1.7|MIME-Version:=201 .0|To:=20Freek=20van=20Hemert=20|CC:=20freebsd -stable@freebsd.org|Subject:=20Re:=20slow=20ZFS=20on=20FreeBSD=208 .1|References:=20=09<4D1AF388.3080107@infracaninophile.co.uk>=20|In-Reply- To:=20|X-Enigmail-Version:=201.1.1|OpenPGP:=20id=3D60AE908C|Content-Ty pe:=20multipart/signed=3B=20micalg=3Dpgp-sha1=3B=0D=0A=20protocol= 3D"application/pgp-signature"=3B=0D=0A=20boundary=3D"------------e nigFAC1BC1AAF7B4B3CF657DCFE"; b=jMrxMSDciy69vL1ib3qDSxzf7eyUSWw1bgw7ncOdmVY4mNudMMdMPZfJGgk8rZCJr tP3BYIJCfP2JAJJnbOI3ulBpl2KaMGg0DtL6BZO1h0zSK1dtZeOtA3VZ9+/q5FpJcN zsZ77+0bT3a5/TuqLihXVvzWo/HYlBfA+TSur6cc= Message-ID: <4D1B7431.7070808@infracaninophile.co.uk> Date: Wed, 29 Dec 2010 17:47:29 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Freek van Hemert References: <4D1AF388.3080107@infracaninophile.co.uk> In-Reply-To: X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFAC1BC1AAF7B4B3CF657DCFE" X-Virus-Scanned: clamav-milter 0.96.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 17:47:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFAC1BC1AAF7B4B3CF657DCFE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 29/12/2010 08:57, Freek van Hemert wrote: > The hacks sounds good until 8.2 is released however, regarding this upg= rade, > is the on-disk format the same? Can I just add the pool to a new instal= l (of > 8.2-RC) and expect higher performance? Or do I need to recreate the poo= l > with the newer versions of the utilities? No -- the on-disk format is different. ZFS will run fine with the older on-disk formats, but you won't get the full benefits without updating them. You'll need to run both 'zpool update -a' and 'zfs update -a' -- this is a non-reversible step, so be certain you will never need to downgrade before doing it. Also, you *will* need to update gptzfsboot on your drives, or you will come to a sticky end if you try and reboot. Something like this: # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigFAC1BC1AAF7B4B3CF657DCFE 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 Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0bdDkACgkQ8Mjk52CukIzYtgCgiqmzK5kMMqiqC3Hxg7pgLoqN QTAAniZ8vAAJplHbPEwqdhn85oSGpCeX =4wVD -----END PGP SIGNATURE----- --------------enigFAC1BC1AAF7B4B3CF657DCFE-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 20:25:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D74D106564A for ; Wed, 29 Dec 2010 20:25:57 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id E60CD8FC08 for ; Wed, 29 Dec 2010 20:25:56 +0000 (UTC) Received: by iwn39 with SMTP id 39so10611772iwn.13 for ; Wed, 29 Dec 2010 12:25:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KlJKoel2wKufhcNfuvbuyr0b1eSZbgf705uzkPeQYFg=; b=U/S0umi5TA93PEDJGSHuBmYyt5AK6+xmO9+5Pg/nU/LgwsvMbtcDAUoktMp7STdwdC bKg9/sq/BYsU82lHjdJ9yMr8yqzaqD15fK72oeCQ5mSHEEcy1YNStEoQ5G2eA+6AexH1 41D30MaxtdrZAS9+phe34mbwpeBhUdFUiQatI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FgWQxCPQVPhZOOfdG/TL7MYW9RPAw1YJW34EIBiFenCOcyXEif3Mh98uiADaNyUt8W ukrIx7XjwN0LkWQCF4KL1VaRcD1dcAsX1fg7a6i/k/76iMxv9aSaxop/OBv1Vm8yygUT shkDN9leFhyO87BsucuYYEhxsy7C+No/EjeYo= MIME-Version: 1.0 Received: by 10.42.170.1 with SMTP id d1mr15551996icz.169.1293654356293; Wed, 29 Dec 2010 12:25:56 -0800 (PST) Received: by 10.42.101.209 with HTTP; Wed, 29 Dec 2010 12:25:56 -0800 (PST) In-Reply-To: <4D1B7431.7070808@infracaninophile.co.uk> References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> Date: Thu, 30 Dec 2010 07:25:56 +1100 Message-ID: From: Jean-Yves Avenard To: Matthew Seaman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Freek van Hemert , "freebsd-stable@freebsd.org" Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 20:25:57 -0000 On Thursday, 30 December 2010, Matthew Seaman wrote: > No -- the on-disk format is different. =A0ZFS will run fine with the olde= r > on-disk formats, but you won't get the full benefits without updating > them. =A0 You'll need to run both 'zpool update -a' and 'zfs update -a' -= - I believe it's "upgrade" you want to use, not update. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 21:26:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2DA21065670 for ; Wed, 29 Dec 2010 21:26:33 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.freebsd.org (Postfix) with ESMTP id 4547A8FC13 for ; Wed, 29 Dec 2010 21:26:32 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail17.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id oBTLO0nm010059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Dec 2010 08:25:33 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id oBTLNpLe011264 for ; Thu, 30 Dec 2010 08:23:51 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id oBTLMv0Y011250; Thu, 30 Dec 2010 08:22:57 +1100 (EST) (envelope-from peter) Date: Thu, 30 Dec 2010 08:22:57 +1100 From: Peter Jeremy To: Michael BlackHeart Message-ID: <20101229212257.GA34530@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Dec 2010 21:26:34 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Dec-28 23:08:44 +0300, Michael BlackHeart wrote: >I'm jsut trying to say than recent changes in kernel or kernel-modules >broke up my HDD support and I'd like to notice developres to check >where the problem is. It doesn't work that way. The developers don't have a problem or it would have been fixed. You are going to need to provide more details and do some investigations yourself to help identify the problem. >Loader on it's own stage easily detects HDD and root partition so I >can just select old kernel and boot up, but I'm not shure how he gain >access to HDD to mfke any conclusion, probably through BIOS interrupts >but it's out of piont. Yes. Until the kernel starts, all I/O is via BIOS. >And for my pity I don't know how to dump demsg without having any >serial connection or usable disk drive, maybe to flash drive, but I >don't know how. And anyway there's no real kernel painc, it just asks >for root mountpoint. Best suggestion I can offer is to take photographs of the boot messages (you can use scroll-lock to let you scroll back) and post them somewhere. >If you need any aditional info I'll give it all, just ask. What is the SVN revision of a kernel that works? What is the SVN revision of a kernel that fails? Can you please post a verbose dmesg of a successful boot. Can you please post a dmesg of an unsuccessful boot (see above). --=20 Peter Jeremy --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAk0bprEACgkQ/opHv/APuIf5oQCgq24USL9WmdnrSFwDZO+ztRTb 8wMAn1e/aaHTMKlRgHpCRfIUtKh/SnWH =Gc9+ -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 00:56:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55535106566C for ; Thu, 30 Dec 2010 00:56:49 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 234158FC14 for ; Thu, 30 Dec 2010 00:56:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 41698508AA for ; Thu, 30 Dec 2010 00:56:48 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oGzpey4WQkq for ; Thu, 30 Dec 2010 00:56:48 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id E7010508AC for ; Thu, 30 Dec 2010 00:56:47 +0000 (GMT) Message-ID: <4D1BD8D0.5010402@langille.org> Date: Wed, 29 Dec 2010 19:56:48 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> In-Reply-To: <4D1B7431.7070808@infracaninophile.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 00:56:49 -0000 On 12/29/2010 12:47 PM, Matthew Seaman wrote: > On 29/12/2010 08:57, Freek van Hemert wrote: >> The hacks sounds good until 8.2 is released however, regarding this upgrade, >> is the on-disk format the same? Can I just add the pool to a new install (of >> 8.2-RC) and expect higher performance? Or do I need to recreate the pool >> with the newer versions of the utilities? > > No -- the on-disk format is different. ZFS will run fine with the older > on-disk formats, but you won't get the full benefits without updating > them. You'll need to run both 'zpool update -a' and 'zfs update -a' -- > this is a non-reversible step, so be certain you will never need to > downgrade before doing it. Also, you *will* need to update gptzfsboot > on your drives, or you will come to a sticky end if you try and reboot. > Something like this: > > # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 > > Cheers, > > Matthew This part applies only if you're booting from ZFS drives? -- Dan Langille - http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 08:00:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29C341065673 for ; Thu, 30 Dec 2010 08:00:18 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id BEB428FC13 for ; Thu, 30 Dec 2010 08:00:17 +0000 (UTC) Received: by qyk8 with SMTP id 8so11090553qyk.13 for ; Thu, 30 Dec 2010 00:00:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=Q+o4u0ZJnv31xnhw5op/XevjYo/1/eoa21+0azkoDFc=; b=Uc1Qb05pg1DY+LJFt2Z5aoYRvVEJaoj2lz566Li9FiwOkODAgihQv9tWitwgg7muwQ ZVoTqWDY7YR3sb8uPkiV1NZV+Tj3Yq5zSpH2vQMzcUl8F6kJ/1Bw2TaLRH3PKKzjWA0u e8TpzYTXNhNrrshVKmASQtBCFbLj30I6Zhktk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=ARfFU5YKnYiPbuudR2a7z8rGCDIMdAXCAduUlIagTapduM3yi0rdP/SGiYUywcwBpn 8n23VMFIPfBfpTGNRYyM7uBu/A5fw6YH3PFlBzyVzhyqNlXR4yNINFqLMRDQgM6W0oQ0 u4f1E7orCH4+lwoTravflpn1lWFoMSMMsU/uY= Received: by 10.224.2.138 with SMTP id 10mr15043065qaj.133.1293694314258; Wed, 29 Dec 2010 23:31:54 -0800 (PST) Received: from zephyr.adamsnet ([72.49.234.31]) by mx.google.com with ESMTPS id s10sm7584602qco.47.2010.12.29.23.31.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 29 Dec 2010 23:31:52 -0800 (PST) Date: Thu, 30 Dec 2010 02:31:30 -0500 From: Adam Stylinski To: freebsd-stable@freebsd.org Message-ID: <20101230073130.GA55431@zephyr.adamsnet> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 08:00:18 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I can tell you what the problem is right now, actually. ZFS performs very = poorly on low performance CPUs (i.e. your Atom N330). Try the same system = with a different CPU and you'll get a different result. It's not a lack of= bandwidth on your bus, memory, or disks, and it's not exactly the checksum= ming either (although that certainly contributes to the bottleneck), the gr= ouping of transaction groups to be flushed to the disks is what your bottle= neck is. I had an issue with some fairly poor performance with a Sempron 2= 800+ 45W TDP CPU and replacing it with an Athlon X2 did wonders. =20 --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJNHDVRAAoJED6sRHE6Tvmn66YP/ih/lpS86FVnFaTC3GxBRGa4 y7jiv9pFI1EafWcOxulxxkTAVGH6hBCodOsZbQi+aKqJH0wVfPzRXp/TFSf4CxRH EWfIAbZsouD2bRVc3/hfsCcE7nC96DB/qArY/A9lGexW6HDpzkLd5JvBwyQLbjrr qGCcnElNH8n4AMfa5zIYW2+LoD475v5dmUff21yLNFqvdJcbZN2DivF1OAxtCsbe OjZUfIrOIifdTp0YaU33zYjM74kY/lR2oa532YJiYlExELGyMY+6P4IMsBKFj/SN 2X4JKhO5uQzLU+jWYo+WyGoL4YkAWsIz1GKIMOgteD7YpEELJ82yN3qgHxRLTsKc JG6tHsIdNwbqkyccnx2sqaHkCEeM+wpub6Xvmy5r279Z8iF9bosUSKvNeZV93fEA tv2V2VmhPqhI/DZ3v4smcomqgNgFvjjpg7jlY0boaKAK7AugAGMWZpzPzKR+mEij Ltyu6uTLyWiCE4jqdIiAQphddjyhLA4/Zl8h/bkSHqXrCqmOGRcbvRlzzoIPtqts k8yY5OkOQUSNyAAE8ygnqwUT8RzkC4f7ceIAvFuORwyg7ZBNREOgqYYXW7XO21fb 9Xq9LVc1glv/jbFw7NQqZuDVtmaRUNqA17au7ouKaJtA5uX/G4hCVX4qZGEbutaY LlRNNXnFDLM+mYxW0Cdo =0WY5 -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 09:00:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B2C106566B for ; Thu, 30 Dec 2010 09:00:42 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id B1ED08FC1A for ; Thu, 30 Dec 2010 09:00:41 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id oBU90aQV028124 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 30 Dec 2010 09:00:37 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 smtp.infracaninophile.co.uk oBU90aQV028124 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1293699637; bh=LSrIdWqd+2whPtCBwWwDBuLDFw2c66Uzq6x7rekeJzw=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Cc:Content-Type:Date:From:In-Reply-To: Message-ID:Mime-Version:References:To; z=Message-ID:=20<4D1C4A2D.4020206@infracaninophile.co.uk>|Date:=20T hu,=2030=20Dec=202010=2009:00:29=20+0000|From:=20Matthew=20Seaman= 20|User-Agent:=20Mozilla/5.0=20(M acintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20en-US=3B=20r v:1.9.2.13)=20Gecko/20101207=20Thunderbird/3.1.7|MIME-Version:=201 .0|To:=20freebsd-stable@freebsd.org|Subject:=20Re:=20slow=20ZFS=20 on=20FreeBSD=208.1|References:=20=09<4D1AF388.3080107@infracaninophile .co.uk>=09=09<4D1B7431.7070808@infracaninophile.co.uk>=20<4D1BD8D0.501 0402@langille.org>|In-Reply-To:=20<4D1BD8D0.5010402@langille.org>| X-Enigmail-Version:=201.1.1|OpenPGP:=20id=3D60AE908C|Content-Type: =20multipart/signed=3B=20micalg=3Dpgp-sha1=3B=0D=0A=20protocol=3D" application/pgp-signature"=3B=0D=0A=20boundary=3D"------------enig C4B7A6CD7171D4147FE4469A"; b=cxhmkTb9ZJVpVZJpOkFDN6MRIVMWulYv0vXW5eLzVk1nAOAxVh+G+/GKXmrtRP3TX J4i1JD2+P+qzTUao1/cHpWwLe0xHp77JVJrWDhOi2CbB5aj5m7pbyylvBUwLkD923b XyDmx9oJKFSDKRg0VADM0Vu/868U4VMZS6hqbvEM= Message-ID: <4D1C4A2D.4020206@infracaninophile.co.uk> Date: Thu, 30 Dec 2010 09:00:29 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> <4D1BD8D0.5010402@langille.org> In-Reply-To: <4D1BD8D0.5010402@langille.org> X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC4B7A6CD7171D4147FE4469A" X-Virus-Scanned: clamav-milter 0.96.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 09:00:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC4B7A6CD7171D4147FE4469A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 30/12/2010 00:56, Dan Langille wrote: >> them. You'll need to run both 'zpool update -a' and 'zfs update -a' = -- As Jean-Yves pointed out: upgrade not update. Some word beginning with 'up' anyhow. >> # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 > This part applies only if you're booting from ZFS drives? Yes, if you're booting from ZFS and you're using gpt to partition the disks, as described at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ et seq. That's probably the most common way of installing FreeBSD+ZFS in use today. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigC4B7A6CD7171D4147FE4469A 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 Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0cSjQACgkQ8Mjk52CukIyjtACgiDrMYWtCeJvQ67yECAXUadQH 1XkAnj8iE7lnb4HE8eLw/5yhBgPHTk0A =nAQS -----END PGP SIGNATURE----- --------------enigC4B7A6CD7171D4147FE4469A-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 11:40:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE1F8106566C for ; Thu, 30 Dec 2010 11:40:05 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 587F08FC0C for ; Thu, 30 Dec 2010 11:40:02 +0000 (UTC) Received: by wwf26 with SMTP id 26so10650495wwf.31 for ; Thu, 30 Dec 2010 03:40:02 -0800 (PST) Received: by 10.227.162.194 with SMTP id w2mr9579514wbx.203.1293709202222; Thu, 30 Dec 2010 03:40:02 -0800 (PST) Received: from dfleuriot.local ([83.167.62.196]) by mx.google.com with ESMTPS id m10sm10886306wbc.22.2010.12.30.03.40.00 (version=SSLv3 cipher=RC4-MD5); Thu, 30 Dec 2010 03:40:01 -0800 (PST) Message-ID: <4D1C6F90.3080206@my.gd> Date: Thu, 30 Dec 2010 12:40:00 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 11:40:05 -0000 Hello list, I currently have a ZFS zraid1 with 4x 1.5TB drives. The system is a zfs-only FreeBSD 8.1 with zfs version 14. I am concerned that in the event a drive fails, I won't be able to repair the disks in time before another actually fails. I wish to reinstall the OS on a dedicated drive (possibly SSD, doesn't matter, likely UFS) and dedicate the 1.5tb disks to storage only. I have ordered 5x new drives and would like to create a new zraid2 mirrored pool. Then I plan on moving data from pool1 to pool2, removing drives from pool1 and adding them to pool2. My questions are as follows: With a total of 9x 1.5TB drives, should I be using zraid3 instead of zraid2 ? I will not be able to add any more drives so unnecessary parity drives = less storage room. What are the steps for properly removing my drives from the zraid1 pool and inserting them in the zraid2 pool ? Regards, dfl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 12:20:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0480106564A for ; Thu, 30 Dec 2010 12:20:59 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id AECDC8FC17 for ; Thu, 30 Dec 2010 12:20:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id AEA45508AA; Thu, 30 Dec 2010 12:20:58 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsgzItGRuuBw; Thu, 30 Dec 2010 12:20:58 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 6EEF150852 ; Thu, 30 Dec 2010 12:20:58 +0000 (GMT) Message-ID: <4D1C7929.3040809@langille.org> Date: Thu, 30 Dec 2010 07:20:57 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Matthew Seaman References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> <4D1BD8D0.5010402@langille.org> <4D1C4A2D.4020206@infracaninophile.co.uk> In-Reply-To: <4D1C4A2D.4020206@infracaninophile.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 12:21:00 -0000 On 12/30/2010 4:00 AM, Matthew Seaman wrote: > On 30/12/2010 00:56, Dan Langille wrote: >>> them. You'll need to run both 'zpool update -a' and 'zfs update -a' -- > > As Jean-Yves pointed out: upgrade not update. Some word beginning with > 'up' anyhow. > >>> # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 > >> This part applies only if you're booting from ZFS drives? > > Yes, if you're booting from ZFS and you're using gpt to partition the > disks, as described at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ > et seq. That's probably the most common way of installing FreeBSD+ZFS in > use today. The reason I've not installed ZFS on root is because of the added complications. I run the OS on ufs (with gmirror) and my data is on ZFS. We must be hanging out with different groups. Most of the people I know don't have ZFS on root. -- Dan Langille - http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 12:33:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A6271065679 for ; Thu, 30 Dec 2010 12:33:26 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id DC7978FC14 for ; Thu, 30 Dec 2010 12:33:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=antiszoc.hu; s=default; h=Subject:To:From:Date; bh=/+4KYIHoQeSXIm1E7ZN0McAeRu/GCAFrO4xv9aLgT9c=; b=XVwIqH1RvGxVTl6+fGAlEuppjP0g+Gesoy7mrn0Yq+Xo0M7V9T8ESlOnMhgF87C4bQv6ycYgcNKjVXIZV1i2aRir29DW34cOJbC/3cZUs5w9ZzkEoCTWeHAn6221Z8dv; Received: from localhost ([127.0.0.1]:35906 helo=mail.deployis.eu) by mail.deployis.eu with esmtp (Exim 4.71 #1 (Debian)) id 1PYHSI-00038Q-11 from ; Thu, 30 Dec 2010 13:18:06 +0100 MIME-Version: 1.0 Date: Thu, 30 Dec 2010 13:18:06 +0100 From: =?UTF-8?Q?G=C3=B3t_Andr=C3=A1s?= To: Damien Fleuriot In-Reply-To: <4D1C6F90.3080206@my.gd> References: <4D1C6F90.3080206@my.gd> Message-ID: X-Sender: andrej@antiszoc.hu User-Agent: RoundCube Webmail/0.2.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" X-DKIM-Status: None (from 127.0.0.1) X-Mail-Status-postahivatal: trustedmail (from 127.0.0.1) X-Spam-Score-postahivatal: -43 Cc: freebsd-stable@freebsd.org Subject: Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 12:33:26 -0000 Hi, I think it's enough to have 2 parity drives with raidz2. If a drive fails another two has to fail for data loss. However, keep in mind that raid (in any form) is not instead of backups. I have a setup where a 8TB RAID5 is the main backup and serves as file server for not important things AND there's a 3TB RAID5 in a different machine for secondary backups. Regards, Andras On Thu, 30 Dec 2010 12:40:00 +0100, Damien Fleuriot wrote: > Hello list, > > > > I currently have a ZFS zraid1 with 4x 1.5TB drives. > The system is a zfs-only FreeBSD 8.1 with zfs version 14. > > I am concerned that in the event a drive fails, I won't be able to > repair the disks in time before another actually fails. > > > > > I wish to reinstall the OS on a dedicated drive (possibly SSD, doesn't > matter, likely UFS) and dedicate the 1.5tb disks to storage only. > > I have ordered 5x new drives and would like to create a new zraid2 > mirrored pool. > > Then I plan on moving data from pool1 to pool2, removing drives from > pool1 and adding them to pool2. > > > > My questions are as follows: > > With a total of 9x 1.5TB drives, should I be using zraid3 instead of > zraid2 ? I will not be able to add any more drives so unnecessary parity > drives = less storage room. > > What are the steps for properly removing my drives from the zraid1 pool > and inserting them in the zraid2 pool ? > > > Regards, > > > dfl > > _______________________________________________ > 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 Dec 30 14:07:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C7FA1065670 for ; Thu, 30 Dec 2010 14:07:46 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id F22DF8FC12 for ; Thu, 30 Dec 2010 14:07:45 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id oBUE7eid030151 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 30 Dec 2010 14:07:41 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 smtp.infracaninophile.co.uk oBUE7eid030151 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1293718061; bh=/6W6jjYdUqwrkssohou3NWlgKsx7BJ08hlEAO3jNMZk=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Cc:Content-Type:Date:From:In-Reply-To: Message-ID:Mime-Version:References:To; z=Message-ID:=20<4D1C9224.1010909@infracaninophile.co.uk>|Date:=20T hu,=2030=20Dec=202010=2014:07:32=20+0000|From:=20Matthew=20Seaman= 20|User-Agent:=20Mozilla/5.0=20(M acintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20en-US=3B=20r v:1.9.2.13)=20Gecko/20101207=20Thunderbird/3.1.7|MIME-Version:=201 .0|To:=20Dan=20Langille=20|CC:=20freebsd-stable@ freebsd.org|Subject:=20Re:=20slow=20ZFS=20on=20FreeBSD=208.1|Refer ences:=20=09<4D1AF388.3080107@infracaninophile.co.uk>=09=09<4D1B7431.70708 08@infracaninophile.co.uk>=09<4D1BD8D0.5010402@langille.org>=20<4D 1C4A2D.4020206@infracaninophile.co.uk>=20<4D1C7929.3040809@langill e.org>|In-Reply-To:=20<4D1C7929.3040809@langille.org>|X-Enigmail-V ersion:=201.1.1|OpenPGP:=20id=3D60AE908C|Content-Type:=20multipart /signed=3B=20micalg=3Dpgp-sha1=3B=0D=0A=20protocol=3D"application/ pgp-signature"=3B=0D=0A=20boundary=3D"------------enigE1EC705E6F6A 55CEFBB40C35"; b=qCmRCImocrL9EGyoN+WaRypumDUj8kQEC3Y8VVqXqjcrP5MWvX5vH1Tho+t0jWQm8 mj5KdK8z936/csVNuQrK5h4SCPp+/JrEgcBedmMv7vQJ43JztW74Yixy0iOySUS22g q74tG6nSqzygfxPKiEqgwVsAj3a8LaCRgQ/8pRO8= Message-ID: <4D1C9224.1010909@infracaninophile.co.uk> Date: Thu, 30 Dec 2010 14:07:32 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Dan Langille References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> <4D1BD8D0.5010402@langille.org> <4D1C4A2D.4020206@infracaninophile.co.uk> <4D1C7929.3040809@langille.org> In-Reply-To: <4D1C7929.3040809@langille.org> X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE1EC705E6F6A55CEFBB40C35" X-Virus-Scanned: clamav-milter 0.96.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 14:07:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE1EC705E6F6A55CEFBB40C35 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 30/12/2010 12:20, Dan Langille wrote: > On 12/30/2010 4:00 AM, Matthew Seaman wrote: >> On 30/12/2010 00:56, Dan Langille wrote: >> Yes, if you're booting from ZFS and you're using gpt to partition the >> disks, as described at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ >> et seq. That's probably the most common way of installing FreeBSD+ZFS = in >> use today. > The reason I've not installed ZFS on root is because of the added > complications. I run the OS on ufs (with gmirror) and my data is on > ZFS. We must be hanging out with different groups. Most of the peopl= e > I know don't have ZFS on root. Hmmm... well, complication is in the eye of the beholder. Installing root on ZFS is more work, certainly. Mostly because sysinstall doesn't support it (but the PC-BSD installer does). Once it is set up, it's no more bother than root on UFS during normal use, and personally I'd say a pure ZFS system is simpler and cleaner than a hybrid UFS/ZFS setup[*]. The whole deal with updating gptzfsloader is a thing you only need to worry about on rare occasions; typically only during version upgrades. Unless you're tracking a dev branch or running experimental code. 8.1-RELEASE has v13. 8.2-RELEASE will have v15. 9.0 and 8.3 will probably have v28 -- it's anybodies' guess after that, given Oracle's actions over OpenSolaris. Cheers, Matthew [*] There's a good argument for a system with root on ZFS and data on UFS, as a DB server -- ZFS is not the best performing filesystem for the sort of small randomly located IOs that RDBMSes generate. --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigE1EC705E6F6A55CEFBB40C35 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 Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0ckiwACgkQ8Mjk52CukIwusACdG2027WDtEeP110Ct1Pq390+t aqwAn1GC86Y5lxTLWOyHuAOR1E01QsUg =oxsR -----END PGP SIGNATURE----- --------------enigE1EC705E6F6A55CEFBB40C35-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 17:01:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89406106564A for ; Thu, 30 Dec 2010 17:01:11 +0000 (UTC) (envelope-from luke@digital-crocus.com) Received: from mail.digital-crocus.com (node2.digital-crocus.com [91.209.244.128]) by mx1.freebsd.org (Postfix) with ESMTP id 435C18FC15 for ; Thu, 30 Dec 2010 17:01:11 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dkselector; d=hybrid-logic.co.uk; h=Received:Received:Subject:From:Reply-To:To:Content-Type:Organization:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-Spam-Score:X-Digital-Crocus-Maillimit:X-Authenticated-Sender:X-Complaints:X-Admin:X-Abuse; b=xhdKlJMP4aFNOZbLb2IJI4iMDQfhTJnl52bYG1l0LtnbLILcvzTxuH2HyMWgiXhQ8M5eSlcP/i5LUrotheBkMAF0aRMZxMXjK8XzYXhAgNSyHMge8tSWrIQ9W5zLc//z; Received: from luke by mail.digital-crocus.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1PYLLx-0009xo-OW for freebsd-stable@freebsd.org; Thu, 30 Dec 2010 16:27:49 +0000 Received: from 127cr.net ([78.105.122.99] helo=[192.168.1.22]) by mail.digital-crocus.com with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1PYLLx-0009ws-5R; Thu, 30 Dec 2010 16:27:49 +0000 From: Luke Marsden To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Organization: Hybrid Web Cluster Date: Thu, 30 Dec 2010 16:32:52 +0000 Message-ID: <1293726772.5853.1348.camel@pow> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.0 X-Digital-Crocus-Maillimit: done X-Authenticated-Sender: luke X-Complaints: abuse@digital-crocus.com X-Admin: admin@digital-crocus.com X-Abuse: abuse@digital-crocus.com (Please include full headers in abuse reports) Cc: Subject: Virtio drivers for FreeBSD on KVM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: luke@hybrid-logic.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2010 17:01:11 -0000 Hi everyone, With more cloud infrastructure providers using KVM than ever before, the importance of having FreeBSD performant as a guest on these infrastructures [1], [2], [3] is increasing. It seems that using Virtio drivers give a pretty significant performance boost [4], [5]. There was a NetBSD driver, and there seems to (have been) some work happening to port this to DragonFly BSD at [6] and [7] -- does anyone know if this code is stable, or if it has stalled, or if anyone's working on it? It may be possible to use the work done on the Xen paravirtualised network and disk drivers, combined with the NetBSD code, as starting point for an implementation? My company might soon be in a position to sponsor the work to get this completed and available at some point in FreeBSD 8. I'd be very interested to hear from anyone who's involved, or who might like to be. -- Best Regards, Luke Marsden CTO, Hybrid Logic Ltd. Web: http://www.hybrid-cluster.com/ Hybrid Web Cluster - cloud web hosting Mobile: +447791750420 [1] http://www.elastichosts.com/ [2] http://www.cloudsigma.com/ [3] http://beta.brightbox.com/ [4] http://arstechnica.com/civs/viewtopic.php?f=16&t=34039 [5] blog.loftninjas.org/2008/10/22/kvm-virtio-network-performance/ [6] kerneltrap.org/mailarchive/dragonflybsd-kernel/2010/10/23/6884356 [7] http://gitorious.org/virtio-drivers From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 18:07:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 572321065694 for ; Thu, 30 Dec 2010 18:07:31 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out2.tiscali.nl (smtp-out2.tiscali.nl [195.241.79.177]) by mx1.freebsd.org (Postfix) with ESMTP id 182388FC12 for ; Thu, 30 Dec 2010 18:07:30 +0000 (UTC) Received: from [212.123.145.58] (helo=sjakie.klop.ws) by smtp-out2.tiscali.nl with esmtp (Exim) (envelope-from ) id 1PYMct-0005x9-V6 for freebsd-stable@freebsd.org; Thu, 30 Dec 2010 18:49:24 +0100 Received: from 212-123-145-58.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id 309CB10122 for ; Thu, 30 Dec 2010 18:49:21 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org References: <4D1C6F90.3080206@my.gd> Date: Thu, 30 Dec 2010 18:49:20 +0100 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: <4D1C6F90.3080206@my.gd> User-Agent: Opera Mail/11.00 (FreeBSD) Content-Transfer-Encoding: quoted-printable Subject: Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 18:07:31 -0000 On Thu, 30 Dec 2010 12:40:00 +0100, Damien Fleuriot wrote: > Hello list, > > > > I currently have a ZFS zraid1 with 4x 1.5TB drives. > The system is a zfs-only FreeBSD 8.1 with zfs version 14. > > I am concerned that in the event a drive fails, I won't be able to > repair the disks in time before another actually fails. > > > > > I wish to reinstall the OS on a dedicated drive (possibly SSD, doesn't > matter, likely UFS) and dedicate the 1.5tb disks to storage only. > > I have ordered 5x new drives and would like to create a new zraid2 > mirrored pool. > > Then I plan on moving data from pool1 to pool2, removing drives from > pool1 and adding them to pool2. > > > > My questions are as follows: > > With a total of 9x 1.5TB drives, should I be using zraid3 instead of > zraid2 ? I will not be able to add any more drives so unnecessary parit= y > drives =3D less storage room. > > What are the steps for properly removing my drives from the zraid1 pool > and inserting them in the zraid2 pool ? > > > Regards, > > > dfl Make sure you have spare drives so you can swap in a new one quickly and = =20 have off-line backups in case disaster strikes. Extra backups are always = =20 nice. Disks are not the only parts which can break and damage your data. Ronald. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 19:13:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5727106566C for ; Thu, 30 Dec 2010 19:13:37 +0000 (UTC) (envelope-from pj@smo.de) Received: from smtp-out30.ilk.net (smtp-out30.ilk.net [212.86.193.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2C5248FC12 for ; Thu, 30 Dec 2010 19:13:36 +0000 (UTC) Received: from bologna.intern.smo.de (pool39.tdsl.ilk.net [212.86.201.39]) by smtp.ilk.net (Postfix) with ESMTP id 4C7DE360C6; Thu, 30 Dec 2010 20:13:34 +0100 (CET) Received: from herdubreid.intern.smo.de (herdubreid.intern.smo.de [192.168.153.208]) by bologna.intern.smo.de (8.13.8+Sun/8.13.8) with ESMTP id oBUJDUPK029254; Thu, 30 Dec 2010 20:13:31 +0100 (CET) Message-ID: <4D1CDA22.8070905@smo.de> Date: Thu, 30 Dec 2010 20:14:42 +0100 From: Philipp Ost User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.16) Gecko/20101218 SeaMonkey/2.0.11 MIME-Version: 1.0 To: Zoran References: <20101224170809.GA28772@feodosiia.fooboo.org> <4D14EA2C.8060401@smo.de> <20101225051708.GA853@feodosiia.fooboo.org> In-Reply-To: <20101225051708.GA853@feodosiia.fooboo.org> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070205040409010603030009" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: happy hacker lite 2 keyboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 19:13:37 -0000 This is a cryptographically signed message in MIME format. --------------ms070205040409010603030009 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Zoran wrote: > Thaks for reply. > >> I have one in use since ~5 years. The typing feel is a lot better comp= ared >> to the Logitech keyboard I had before. >> The only problem I have with mine is that it's not usable with the boo= t >> loader menu. It seems to be hardware related as it works fine with oth= er >> computers (using different chipsets). > > There is always chance to use it with ps2 converter. All new keyboards > are usb in fact, but I add that little plastic in between. I'm aware of that, but didn't try it. On the other hand, the BIOS seems=20 to be a little bit too stupid to handle this correctly. As I'm switching this computer on only once per day and not updating my=20 system every other day, I don't really care about it any longer ;-) Besides, the HHKB Lite 2 has two USB ports integrated which are quite=20 handy sometimes. [...] > I still have something to ponder. To have more than one screen in fvwm,= > actually four of them, I ought to turn off numpad first. Then I use com= - > bination of Alt-Fx to jump here and there. In bios I removed numpad and= > it is not working on the kb, to my wish. Any thought how it goes on HH?= The Happy Hacking keyboard doesn't have a numpad. I didn't have any=20 problems because of this, regardless of having it enabled/disabled in=20 the BIOS. Happy Hacking ;-) Philipp --------------ms070205040409010603030009-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 20:43:44 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80CC5106564A for ; Thu, 30 Dec 2010 20:43:44 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 1D0D88FC21 for ; Thu, 30 Dec 2010 20:43:43 +0000 (UTC) Received: by qyk8 with SMTP id 8so11643779qyk.13 for ; Thu, 30 Dec 2010 12:43:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=t9Vvm81ctRAQGzDFyEe9lhCKfW0GfRdr5E/OycgKIA0=; b=UkmvFbWUFE/TSf2bwLDl+D0FhqfhZcZLyZ2jRLxdAH2dgtIr/FMbjtpl2j3ejTaqWN lxRcr+3JaRCpzfWT2ZWhAl3rLyLl2EsCEMdg9DJux6iV+sWATgbe2fgmEzO9iLj4psaT AEglah3FFGc2AeuW1LU6W1seW5A68GexMYTxk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YiDKBpsTJiByEfTj6R7NofFbVuNmomJqlOTrO663CKkN1/51D94hqlCCGVB37s5Lqh SBhOuEl+VGHrHRNcXkri6fBuxk97dDUxrl/O/h+1gUQakvE9Ss1FY8KPcN2e33/7O8B+ WqqO7gqDDVmi+oTkUYX18KOyqnIl6vktXcWME= MIME-Version: 1.0 Received: by 10.229.182.11 with SMTP id ca11mr7091807qcb.15.1293741823190; Thu, 30 Dec 2010 12:43:43 -0800 (PST) Received: by 10.220.192.11 with HTTP; Thu, 30 Dec 2010 12:43:43 -0800 (PST) In-Reply-To: References: Date: Thu, 30 Dec 2010 23:43:43 +0300 Message-ID: From: Michael BlackHeart To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 20:43:44 -0000 You were right about SATA mode, I should miss something when I try switch it first time or may be there're some other reasons, like previously I tried i386. Anyway there's HDD. But it's all doesn't find HDD with SATA native disabled, but I'd like to have this working old way for some reasons. I've not tried to enble labeling, but i think that it wouldn't work because with disabled native mode there's no any entry about HDD like with native mode enabled. And when I get promted to enter new boot point and pressing '?' there's only acd drive with enabled native mode, but with enabled native mode there's acd, hdd and also automaticaly created labels. I'm still thinking that the some of the drivers or one of them is broken or maybe some modules are no longer included. Now I've got two kernels, is there a way to find out where's the problem, 'cos I think I can just put old driver source code and recompile kernel to get things working back in old way? And as you ask me - dmesg logs. With SATA native enabled there's a slightly different controller strings and I think there's the problem ------------------------------------------------------------ ------------------------------------------------------------ Working good at all points - 8.1 RELEASE kernel, dunno REVISION Default configuration working with SATA native disabled: ------------------------------------------------------------ Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU T2410 @ 2.00GHz (1995.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Family = 6 Model = f Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2047451136 (1952 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7f700000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x4000-0x4007 mem 0xe4400000-0xe44fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M vgapci1: mem 0xe4500000-0xe45fffff at device 2.1 on pci0 em0: port 0x4020-0x403f mem 0xe4600000-0xe461ffff,0xe4620000-0xe4620fff irq 22 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1f:29:9c:7a:12 uhci0: port 0x4040-0x405f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: on uhci0 ehci0: mem 0xe4621000-0xe46213ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci8: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci16: on pcib2 siba_bwn0: mem 0xe4000000-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci40: on pcib3 uhci1: port 0x4060-0x407f irq 20 at device 29.0 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus2: on uhci1 uhci2: port 0x4080-0x409f irq 21 at device 29.1 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus3: on uhci2 uhci3: port 0x40a0-0x40bf irq 18 at device 29.2 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x2f00 usbus4: on uhci3 ehci1: mem 0xe4628000-0xe46283ff irq 20 at device 29.7 on pci0 ehci1: [ITHREAD] usbus5: EHCI version 1.0 usbus5: on ehci1 pcib4: at device 30.0 on pci0 pci2: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x40c0-0x40cf,0x40d0-0x40df irq 17 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] battery0: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 acpi_tz3: on acpi0 acpi_tz3: _CRT value is absurd, ignored (256.0C) acpi_tz4: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ad0: 152627MB at ata0-master UDMA100 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 acd0: DVDR at ata1-master PIO4 SMP: AP CPU #1 Launched! uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered Root mount waiting for: usbus5 usbus1 Root mount waiting for: usbus5 usbus1 uhub1: 4 ports with 4 removable, self powered uhub5: 6 ports with 6 removable, self powered Root mount waiting for: usbus5 Trying to mount root from ufs:/dev/ad0s3a ugen2.2: at usbus2 ukbd0: on usbus2 kbd2 at ukbd0 ums0: on usbus2 ums0: 5 buttons and [XYZT] coordinates ID=26 ums0: 0 buttons and [T] coordinates ID=0 uhid0: on usbus2 ----------------------------------------------------------------- ----------------------------------------------------------------- Newly compiled trouble kernel - REVISION 216724 Working good with SATA native enabled ----------------------------------------------------------------- Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-PRERELEASE #0: Mon Dec 27 16:15:01 MSK 2010 root@:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU T2410 @ 2.00GHz (1995.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Family = 6 Model = f Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2044231680 (1949 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7f700000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x4000-0x4007 mem 0xe4400000-0xe44fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M vgapci1: mem 0xe4500000-0xe45fffff at device 2.1 on pci0 em0: port 0x4020-0x403f mem 0xe4600000-0xe461ffff,0xe4620000-0xe4620fff irq 22 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1f:29:9c:7a:12 uhci0: port 0x4040-0x405f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: on uhci0 ehci0: mem 0xe4621000-0xe46213ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci8: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci16: on pcib2 siba_bwn0: mem 0xe4000000-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci40: on pcib3 uhci1: port 0x4060-0x407f irq 20 at device 29.0 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus2: on uhci1 uhci2: port 0x4080-0x409f irq 21 at device 29.1 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus3: on uhci2 uhci3: port 0x40a0-0x40bf irq 18 at device 29.2 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x2f00 usbus4: on uhci3 ehci1: mem 0xe4628000-0xe46283ff irq 20 at device 29.7 on pci0 ehci1: [ITHREAD] usbus5: EHCI version 1.0 usbus5: on ehci1 pcib4: at device 30.0 on pci0 pci2: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x40c0-0x40cf irq 16 at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] atapci1: port 0x13f0-0x13f7,0x15f4-0x15f7,0x1370-0x1377,0x1574-0x1577,0x4100-0x411f mem 0xe4629000-0xe46297ff irq 17 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI v1.10 controller with 3 3Gbps ports, PM not supported ata2: on atapci1 ata2: [ITHREAD] battery0: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 acpi_tz3: on acpi0 acpi_tz3: _CRT value is absurd, ignored (256.0C) acpi_tz4: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 acd0: DVDR at ata0-master PIO4 ad4: 152627MB at ata2-master UDMA100 SATA 3Gb/s SMP: AP CPU #1 Launched! Root mount waiting for: usbus5 usbus4 usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered Root mount waiting for: usbus5 usbus1 uhub1: 4 ports with 4 removable, self powered uhub5: 6 ports with 6 removable, self powered Root mount waiting for: usbus5 Trying to mount root from ufs:/dev/ad4s3a ugen2.2: at usbus2 ukbd0: on usbus2 kbd2 at ukbd0 ums0: on usbus2 ums0: 5 buttons and [XYZT] coordinates ID=26 ums0: 0 buttons and [T] coordinates ID=0 uhid0: on usbus2 ------------------------------------------------------------ ------------------------------------------------------------ And troubles with SATA Native disabled: REVISION 216724 (Log was reprodused by photos) ------------------------------------------------------------ Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-PRERELEASE #0: Mon Dec 27 16:15:01 MSK 2010 root@:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU T2410 @ 2.00GHz (1995.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Family = 6 Model = f Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2044231680 (1949 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7f700000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x4000-0x4007 mem 0xe4400000-0xe44fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M vgapci1: mem 0xe4500000-0xe45fffff at device 2.1 on pci0 em0: port 0x4020-0x403f mem 0xe4600000-0xe461ffff,0xe4620000-0xe4620fff irq 22 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1f:29:9c:7a:12 uhci0: port 0x4040-0x405f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: on uhci0 ehci0: mem 0xe4621000-0xe46213ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci8: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci16: on pcib2 siba_bwn0: mem 0xe4000000-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci40: on pcib3 uhci1: port 0x4060-0x407f irq 20 at device 29.0 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus2: on uhci1 uhci2: port 0x4080-0x409f irq 21 at device 29.1 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus3: on uhci2 uhci3: port 0x40a0-0x40bf irq 18 at device 29.2 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x2f00 usbus4: on uhci3 ehci1: mem 0xe4628000-0xe46283ff irq 20 at device 29.7 on pci0 ehci1: [ITHREAD] usbus5: EHCI version 1.0 usbus5: on ehci1 pcib4: at device 30.0 on pci0 pci2: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x40c0-0x40cf irq 17 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] battery0: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 acpi_tz3: on acpi0 acpi_tz3: _CRT value is absurd, ignored (256.0C) acpi_tz4: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 acd0: DVDR at ata0-master PIO4 SMP: AP CPU #1 Launched! Root mount waiting for: usbus5 usbus4 usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered Root mount waiting for: usbus5 usbus1 uhub1: 4 ports with 4 removable, self powered uhub5: 6 ports with 6 removable, self powered Root mount waiting for: usbus5 Trying to mount root from ufs:/dev/ad4s3a ROOT MOUNT ERROR From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 23:33:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1497106566B for ; Thu, 30 Dec 2010 23:33:57 +0000 (UTC) (envelope-from mikes@siralan.org) Received: from mail.suso.org (mail.suso.org [66.244.94.5]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3708FC17 for ; Thu, 30 Dec 2010 23:33:57 +0000 (UTC) Received: from c-71-194-154-137.hsd1.in.comcast.net (c-71-194-154-137.hsd1.in.comcast.net [71.194.154.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.suso.org (Postfix) with ESMTP id 9360F1B08C; Thu, 30 Dec 2010 23:33:57 +0000 (GMT) Date: Thu, 30 Dec 2010 18:28:47 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: Pyun YongHyeon In-Reply-To: <20101222135420.C47756@familysquires.net> Message-ID: <20101230181239.N2744@familysquires.net> References: <20101127184952.E90087@familysquires.net> <20101128160043.W11452@familysquires.net> <20101129023531.GB1380@michelle.cdnetworks.com> <20101220181005.P32987@familysquires.net> <20101221180543.GB5236@michelle.cdnetworks.com> <20101222135420.C47756@familysquires.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: bge driver regression in 7.4-PRERELEASE, Tyan S4881 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 23:33:57 -0000 I'm having watchdod timeout problems with the bge driver in 7.4-PRERELEASE on a Tyan S4881 motherboard (the S4881 has 4 Opteron sockets, 2 PCI-E slots, and 3 PCI-X slots, plus VGA and dual Broadcom "bge" GigE ports.) I don't know if this problem also affects the similar Tyan S4882 motherboard, which appears to be much more common. I have a S4882 and can swap it for the S4881 and test this, if anyone is interested (there are a lot things to unplug and unscrew, so I'd rather not if there's no reason for it). I've been able to isolate the problem to the following patches Edit src/sys/dev/bge/if_bge.c Add delta 1.198.2.48 2010.10.08.18.46.02 yongari Add delta 1.198.2.49 2010.10.08.18.51.28 yongari Edit src/sys/dev/bge/if_bgereg.h Add delta 1.73.2.22 2010.10.08.18.46.02 yongari Edit src/sys/dev/et/if_et.c Add delta 1.1.2.9 2010.10.08.19.25.46 yongari Edit src/sys/dev/mii/brgphy.c Add delta 1.70.2.14 2010.10.08.19.00.36 yongari Edit src/sys/dev/mii/brgphyreg.h Add delta 1.10.2.3 2010.10.08.19.00.36 yongari Add delta 1.7.2.6 2010.10.08.20.13.42 yongari Add delta 1.7.2.7 2010.10.08.20.27.51 yongari Add delta 1.7.2.8 2010.10.08.20.31.35 yongari Add delta 1.7.2.9 2010.10.08.20.37.13 yongari Add delta 1.7.2.10 2010.10.08.20.41.15 yongari Add delta 1.7.2.11 2010.10.08.20.44.35 yongari Add delta 1.7.2.12 2010.10.08.20.49.44 yongari Add delta 1.7.2.13 2010.10.08.20.52.47 yongari Add delta 1.7.2.14 2010.10.08.23.14.21 yongari Add delta 1.7.2.15 2010.10.08.23.29.45 yongari Add delta 1.7.2.16 2010.10.08.23.34.45 yongari Reverting if_bge.c, if_bgerec.h, brgphy.c, and brgphyreg.h to the version that existed on 10/7/2010 allows me to do a 7.4-PRERELEASE buildworld/ buildkernel/installkernel cycle and the resulting kernel does not exhibit the watchdog timeout problem. The problem appears only on samba shares exported to a Windows XP Pro client (I've been copying a directory with 17GB of "Ghost" images as a test). The dmesg for a kernel that failed (containing the patches above) is as follows: bge0: mem 0xd0110000-0xd011ffff,0xd0100000-0xd010ffff irq 26 at device 2.0 on pci17 miibus0: on bge0 bge0: Ethernet address: 00:e0:81:58:2d:e3 bge0: [ITHREAD] bge1: mem 0xd0130000-0xd013ffff,0xd0120000-0xd012ffff irq 27 at device 2.1 on pci17 miibus1: on bge1 bge1: Ethernet address: 00:e0:81:58:2d:e4 bge1: [ITHREAD] bge1: link state changed to UP bge1: watchdog timeout -- resetting bge1: link state changed to DOWN bge1: link state changed to UP bge1: watchdog timeout -- resetting bge1: link state changed to DOWN bge1: link state changed to UP bge1: watchdog timeout -- resetting bge1: link state changed to DOWN bge1: link state changed to UP bge1: watchdog timeout -- resetting bge1: link state changed to DOWN bge1: link state changed to UP Mike Squires mikes@siralan.org From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 23:50:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C45B106566C for ; Thu, 30 Dec 2010 23:50:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 7FDCA8FC08 for ; Thu, 30 Dec 2010 23:50:24 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta05.emeryville.ca.mail.comcast.net with comcast id pbCN1f0011u4NiLA5bqP8c; Thu, 30 Dec 2010 23:50:23 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta21.emeryville.ca.mail.comcast.net with comcast id pbqN1f00A2tehsa8hbqPmD; Thu, 30 Dec 2010 23:50:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 700AF9B427; Thu, 30 Dec 2010 15:50:22 -0800 (PST) Date: Thu, 30 Dec 2010 15:50:22 -0800 From: Jeremy Chadwick To: "Michael L. Squires" Message-ID: <20101230235022.GA78602@icarus.home.lan> References: <20101127184952.E90087@familysquires.net> <20101128160043.W11452@familysquires.net> <20101129023531.GB1380@michelle.cdnetworks.com> <20101220181005.P32987@familysquires.net> <20101221180543.GB5236@michelle.cdnetworks.com> <20101222135420.C47756@familysquires.net> <20101230181239.N2744@familysquires.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101230181239.N2744@familysquires.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Pyun YongHyeon , freebsd-stable@freebsd.org Subject: Re: bge driver regression in 7.4-PRERELEASE, Tyan S4881 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Dec 2010 23:50:24 -0000 On Thu, Dec 30, 2010 at 06:28:47PM -0500, Michael L. Squires wrote: > I'm having watchdod timeout problems with the bge driver in > 7.4-PRERELEASE on a Tyan S4881 motherboard (the S4881 has 4 Opteron > sockets, 2 PCI-E slots, and 3 PCI-X slots, plus VGA and dual > Broadcom "bge" GigE ports.) > > I don't know if this problem also affects the similar Tyan S4882 motherboard, > which appears to be much more common. I have a S4882 and can swap it for > the S4881 and test this, if anyone is interested (there are a lot things > to unplug and unscrew, so I'd rather not if there's no reason for it). > > I've been able to isolate the problem to the following patches > > Edit src/sys/dev/bge/if_bge.c > Add delta 1.198.2.48 2010.10.08.18.46.02 yongari > Add delta 1.198.2.49 2010.10.08.18.51.28 yongari > Edit src/sys/dev/bge/if_bgereg.h > Add delta 1.73.2.22 2010.10.08.18.46.02 yongari > Edit src/sys/dev/et/if_et.c > Add delta 1.1.2.9 2010.10.08.19.25.46 yongari > Edit src/sys/dev/mii/brgphy.c > Add delta 1.70.2.14 2010.10.08.19.00.36 yongari > Edit src/sys/dev/mii/brgphyreg.h > Add delta 1.10.2.3 2010.10.08.19.00.36 yongari > Add delta 1.7.2.6 2010.10.08.20.13.42 yongari > Add delta 1.7.2.7 2010.10.08.20.27.51 yongari > Add delta 1.7.2.8 2010.10.08.20.31.35 yongari > Add delta 1.7.2.9 2010.10.08.20.37.13 yongari > Add delta 1.7.2.10 2010.10.08.20.41.15 yongari > Add delta 1.7.2.11 2010.10.08.20.44.35 yongari > Add delta 1.7.2.12 2010.10.08.20.49.44 yongari > Add delta 1.7.2.13 2010.10.08.20.52.47 yongari > Add delta 1.7.2.14 2010.10.08.23.14.21 yongari > Add delta 1.7.2.15 2010.10.08.23.29.45 yongari > Add delta 1.7.2.16 2010.10.08.23.34.45 yongari > > Reverting if_bge.c, if_bgerec.h, brgphy.c, and brgphyreg.h to the > version that existed on 10/7/2010 allows me to do a 7.4-PRERELEASE > buildworld/ > buildkernel/installkernel cycle and the resulting kernel does not exhibit > the watchdog timeout problem. > > The problem appears only on samba shares exported to a Windows XP Pro client > (I've been copying a directory with 17GB of "Ghost" images as a test). > > The dmesg for a kernel that failed (containing the patches above) is > as follows: > > bge0: mem 0xd0110000-0xd011ffff,0xd0100000-0xd010ffff irq 26 at device 2.0 on pci17 > miibus0: on bge0 > bge0: Ethernet address: 00:e0:81:58:2d:e3 > bge0: [ITHREAD] > bge1: mem 0xd0130000-0xd013ffff,0xd0120000-0xd012ffff irq 27 at device 2.1 on pci17 > miibus1: on bge1 > bge1: Ethernet address: 00:e0:81:58:2d:e4 > bge1: [ITHREAD] > bge1: link state changed to UP > bge1: watchdog timeout -- resetting > bge1: link state changed to DOWN > bge1: link state changed to UP > bge1: watchdog timeout -- resetting > bge1: link state changed to DOWN > bge1: link state changed to UP > bge1: watchdog timeout -- resetting > bge1: link state changed to DOWN > bge1: link state changed to UP > bge1: watchdog timeout -- resetting > bge1: link state changed to DOWN > bge1: link state changed to UP Please provide output from the following command, as root: pciconf -lbvc And only include the bge1 and bge0 devices in your output. Thanks. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 00:31:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 122861065696 for ; Fri, 31 Dec 2010 00:31:45 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (mail.1command.com [168.103.150.6]) by mx1.freebsd.org (Postfix) with ESMTP id D299D8FC18 for ; Fri, 31 Dec 2010 00:31:44 +0000 (UTC) Received: from webmail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id oBV06a7a020937 for ; Thu, 30 Dec 2010 16:06:42 -0800 (PST) (envelope-from chris#@1command.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (Local authenticated user inf0s) by webmail.1command.com with HTTP; Thu, 30 Dec 2010 16:06:42 -0800 (PST) Message-ID: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> Date: Thu, 30 Dec 2010 16:06:42 -0800 (PST) From: "Chris H" To: freebsd-stable@freebsd.org User-Agent: HRC Internet Messaging/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit Subject: installworld: check your date/time - Installworld NOT possible... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 00:31:45 -0000 Greetings, I've spent the morning grooming a fresh kernel on a freshly installed 8.1 amd64, from the DVD. I cvsup'd src && ports last night. Build world && kernel && installkernel went as anticipated. HOWEVER, a reboot to single user, followed by a mergemaster -p, followed by cd /usr/src && make installworld, returned: "/usr/src/Makefile", line 177: check your date/time: WTF? Should I simply comment lines 174-178? Why does make(1) refuse to installworld? My date and time are correct (in sync). Any insight into this error would be GREATLY appreciated. --Chris -- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 00:38:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6907B1065670 for ; Fri, 31 Dec 2010 00:38:48 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 0CE038FC0A for ; Fri, 31 Dec 2010 00:38:47 +0000 (UTC) Received: by wwf26 with SMTP id 26so11205353wwf.31 for ; Thu, 30 Dec 2010 16:38:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.183.145 with SMTP id q17mr15932154wem.5.1293755925434; Thu, 30 Dec 2010 16:38:45 -0800 (PST) Received: by 10.216.241.11 with HTTP; Thu, 30 Dec 2010 16:38:45 -0800 (PST) X-Originating-IP: [71.1.133.114] In-Reply-To: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> References: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> Date: Thu, 30 Dec 2010 16:38:45 -0800 Message-ID: From: Rob Farmer To: Chris H Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: installworld: check your date/time - Installworld NOT possible... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 00:38:48 -0000 On Thu, Dec 30, 2010 at 16:06, Chris H wrote: > Greetings, > =A0I've spent the morning grooming a fresh kernel on a freshly installed > 8.1 amd64, from the DVD. I cvsup'd src && ports last night. > Build world && kernel && installkernel went as anticipated. > HOWEVER, a reboot to single user, followed by a mergemaster -p, followed = by > cd /usr/src && make installworld, returned: > "/usr/src/Makefile", line 177: check your date/time: > > WTF? Should I simply comment lines 174-178? > Why does make(1) refuse to installworld? My date and time are correct (in= sync). > Any insight into this error would be GREATLY appreciated. > Did you run "adjkerntz -i" to set your timezone in single user? It starts up with the assumption that your hardware clock is UTC - depending on where you are (east/west of that), this can lead to files created in the "future," which confuses make. --=20 Rob Farmer From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 00:39:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8618010657C1 for ; Fri, 31 Dec 2010 00:39:24 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id DB6538FC15 for ; Fri, 31 Dec 2010 00:39:21 +0000 (UTC) Received: from ur.dons.net.au (ppp203-122-198-179.lns6.adl6.internode.on.net [203.122.198.179]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id oBV0cnxR057056 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Dec 2010 11:08:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/signed; boundary=Apple-Mail-11--231367491; protocol="application/pkcs7-signature"; micalg=sha1 From: "Daniel O'Connor" In-Reply-To: <4D1CDA22.8070905@smo.de> Date: Fri, 31 Dec 2010 11:08:48 +1030 Message-Id: <23B8A0C5-F90B-4ADA-8597-5D3930079887@gsoft.com.au> References: <20101224170809.GA28772@feodosiia.fooboo.org> <4D14EA2C.8060401@smo.de> <20101225051708.GA853@feodosiia.fooboo.org> <4D1CDA22.8070905@smo.de> To: Philipp Ost X-Mailer: Apple Mail (2.1082) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Zoran Subject: Re: happy hacker lite 2 keyboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 00:39:24 -0000 --Apple-Mail-11--231367491 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 31/12/2010, at 5:44, Philipp Ost wrote: >> I still have something to ponder. To have more than one screen in = fvwm, >> actually four of them, I ought to turn off numpad first. Then I use = com- >> bination of Alt-Fx to jump here and there. In bios I removed numpad = and >> it is not working on the kb, to my wish. Any thought how it goes on = HH? >=20 > The Happy Hacking keyboard doesn't have a numpad. I didn't have any = problems because of this, regardless of having it enabled/disabled in = the BIOS. I suspect that only applies to keyboards the BIOS sees, so in your case = a PS/2 one. You can set numlock in X with the x11/numlockx port (I've never used it = though). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --Apple-Mail-11--231367491-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 00:47:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C42CB1065670 for ; Fri, 31 Dec 2010 00:47:00 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8EF8FC1E for ; Fri, 31 Dec 2010 00:46:59 +0000 (UTC) Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta02.westchester.pa.mail.comcast.net with comcast id pcXw1f0021GhbT852cn0oM; Fri, 31 Dec 2010 00:47:00 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta07.westchester.pa.mail.comcast.net with comcast id pcml1f00Q2tehsa3TcmpGw; Fri, 31 Dec 2010 00:46:58 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 044D99B427; Thu, 30 Dec 2010 16:46:41 -0800 (PST) Date: Thu, 30 Dec 2010 16:46:41 -0800 From: Jeremy Chadwick To: Chris H Message-ID: <20101231004640.GA79549@icarus.home.lan> References: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: installworld: check your date/time - Installworld NOT possible... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 00:47:00 -0000 On Thu, Dec 30, 2010 at 04:06:42PM -0800, Chris H wrote: > Greetings, > I've spent the morning grooming a fresh kernel on a freshly installed > 8.1 amd64, from the DVD. I cvsup'd src && ports last night. > Build world && kernel && installkernel went as anticipated. > HOWEVER, a reboot to single user, followed by a mergemaster -p, followed by > cd /usr/src && make installworld, returned: > "/usr/src/Makefile", line 177: check your date/time: > > WTF? Should I simply comment lines 174-178? > Why does make(1) refuse to installworld? My date and time are correct (in sync). > Any insight into this error would be GREATLY appreciated. Usually this error indicates that your clock is skewing excessively (meaning going backwards or forwards too much). How/why this is a problem has to do with how make works, and is for a separate discussion some other time. Are you running ntpd on the machine? How is your clock being kept in sync? What timecounter is being used? sysctl kern.timecounter If you're using ntpd, please provide output from: ntpq -c peers ntpdc -c peers If the problem turns out to be a faulty timecounter, the easiest way to solve the problem is to replace the motherboard. If you're not using ntpd, you should be, and will need to wait ~48 hours (this is not an exaggeration) for the clock skew calculation to determine a median value. If you're using something like ntpdate via a cron job, this is almost certainly the cause of your problems. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 00:53:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D73E1065673 for ; Fri, 31 Dec 2010 00:53:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id E65458FC0C for ; Fri, 31 Dec 2010 00:53:28 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta13.emeryville.ca.mail.comcast.net with comcast id pcDb1f0020QkzPwADctUhD; Fri, 31 Dec 2010 00:53:28 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta02.emeryville.ca.mail.comcast.net with comcast id pctN1f00E2tehsa8NctQij; Fri, 31 Dec 2010 00:53:26 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 065A49B427; Thu, 30 Dec 2010 16:53:20 -0800 (PST) Date: Thu, 30 Dec 2010 16:53:20 -0800 From: Jeremy Chadwick To: Zoran Message-ID: <20101231005319.GA79837@icarus.home.lan> References: <20101224170809.GA28772@feodosiia.fooboo.org> <4D14EA2C.8060401@smo.de> <20101225051708.GA853@feodosiia.fooboo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101225051708.GA853@feodosiia.fooboo.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: happy hacker lite 2 keyboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 00:53:29 -0000 On Sat, Dec 25, 2010 at 06:17:08AM +0100, Zoran wrote: > Thaks for reply. > > > I have one in use since ~5 years. The typing feel is a lot better compared > > to the Logitech keyboard I had before. > > The only problem I have with mine is that it's not usable with the boot > > loader menu. It seems to be hardware related as it works fine with other > > computers (using different chipsets). > > There is always chance to use it with ps2 converter. All new keyboards > are usb in fact, but I add that little plastic in between. I should note that the feature needed in your BIOS to make a USB keyboard work in operating systems that lack USB drivers (ex. MS-DOS, FreeBSD bootloader, GRUB, etc.) is often called "USB Legacy" or "USB Keyboard/Mouse Emulation". If your BIOS does not offer this capability, you need to contact your system manufacturer and discuss this fact. Don't bother to mention FreeBSD or GRUB. Simply tell them that when you boot into MS-DOS via a floppy or CD-ROM, you cannot type anything at the C:\> prompt on your keyboard. Otherwise, try upgrading the system BIOS + reset the settings to factory defaults and see if you find any improvement. If not, continue communicating with your system manufacturer. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 04:34:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EAD71065674 for ; Fri, 31 Dec 2010 04:34:35 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (mail.1command.com [168.103.150.6]) by mx1.freebsd.org (Postfix) with ESMTP id DBD4C8FC0C for ; Fri, 31 Dec 2010 04:34:34 +0000 (UTC) Received: from webmail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id oBV4YQKU021673; Thu, 30 Dec 2010 20:34:33 -0800 (PST) (envelope-from chris#@1command.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (Local authenticated user inf0s) by webmail.1command.com with HTTP; Thu, 30 Dec 2010 20:34:33 -0800 (PST) Message-ID: <2d15f072160e43456a2b10cd973545cb.HRCIM@webmail.1command.com> In-Reply-To: References: <5c0c13e4d33949daafa2a25687db460c.HRCIM@webmail.1command.com> Date: Thu, 30 Dec 2010 20:34:33 -0800 (PST) From: "Chris H" To: freebsd-stable@freebsd.org User-Agent: HRC Internet Messaging/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Rob Farmer Subject: Re: installworld: check your date/time - Installworld NOT possible... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 04:34:35 -0000 Greetings, and thank you for your reply. On Thu, December 30, 2010 4:38 pm, Rob Farmer wrote: > On Thu, Dec 30, 2010 at 16:06, Chris H wrote: > >> Greetings, >>  I've spent the morning grooming a fresh kernel on a freshly installed >> 8.1 amd64, from the DVD. I cvsup'd src && ports last night. >> Build world && kernel && installkernel went as anticipated. >> HOWEVER, a reboot to single user, followed by a mergemaster -p, followed by >> cd /usr/src && make installworld, returned: "/usr/src/Makefile", line 177: >> check your date/time: >> >> WTF? Should I simply comment lines 174-178? >> Why does make(1) refuse to installworld? My date and time are correct (in >> sync). Any insight into this error would be GREATLY appreciated. >> >> > > Did you run "adjkerntz -i" to set your timezone in single user? It > starts up with the assumption that your hardware clock is UTC - depending on > where you are (east/west of that), this can lead to files created in the > "future," which confuses make. Well, turns out that was the answer. I've got to tell you; I've performed _well_ over 1200 build/install world/kernel's over the last 30 years, and this was the _first_ time I've ever been required to do this extra step. In fact, I just finished 4 last week on the same ARCH. The only difference was that I used the 8.0 DVD for the initial install. Everything else was the same. Cvsupping src && ports brought them to 8.1-CURRENT, prior to the build/install world/kern. If I had to guess, I'd say that something changed on the 8.1 DVD, or _very_ recently on src. I didn't see anything in NOTES || README || UPDATING. Well, I _greatly_ appreciate your response, and wish you a _very_ happy new year! :) --Chris > > > -- > Rob Farmer > _______________________________________________ > 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 Fri Dec 31 16:06:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A216106564A for ; Fri, 31 Dec 2010 16:06:24 +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 E21068FC12 for ; Fri, 31 Dec 2010 16:06:23 +0000 (UTC) Received: from mycenae (cable-94-189-178-17.dynamic.sbb.rs [94.189.178.17]) by smtp9.sbb.rs (8.14.0/8.14.0) with ESMTP id oBVFfdSW011421 for ; Fri, 31 Dec 2010 16:41:39 +0100 Received: by mycenae (Postfix, from userid 1001) id 91D455C2B; Fri, 31 Dec 2010 16:41:31 +0100 (CET) Date: Fri, 31 Dec 2010 16:41:31 +0100 From: Zoran Kolic To: freebsd-stable@freebsd.org Message-ID: <20101231154131.GA1073@mycenae.sbb.rs> References: <20101231120040.71AEC10657DF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101231120040.71AEC10657DF@hub.freebsd.org> X-SMTP-Vilter-Version: 1.3.2 X-SBB-Virus-Status: clean X-SBB-Spam-Score: -1.8 Subject: Re: happy hacker lite 2 keyboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 16:06:24 -0000 > The Happy Hacking keyboard doesn't have a numpad. I didn't have any > problems because of this, regardless of having it enabled/disabled in > the BIOS. Sorry for late reply. My old keyboard has numpad part. Since hh lite 2 has it not, I simply ask for behaveor of kb with options I set. I turn off numpad support in bios first. It removes numpad and let me jump from one part of the big screen in fvwm2 to the other one. If I turn numpad on, I cannot do that. Since I never used usb keyboard, cannot comment on the other concern, hh lite 2 and booting process. Best regards all Zoran From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 19:14:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 707721065679 for ; Fri, 31 Dec 2010 19:14:10 +0000 (UTC) (envelope-from noreplyB-NET@ymail.com) Received: from [174.212.186.154] (h-96-14-54-125.ip.alltel.net [96.14.54.125]) by mx1.freebsd.org (Postfix) with SMTP id E2B7F8FC24 for ; Fri, 31 Dec 2010 19:14:08 +0000 (UTC) Received: from [174.212.186.154][127.0.0.1] by [174.212.186.154][127.0.0.1] (SMTPD32); Fri, 31 Dec 2010 12:14:04 -0700 Message-ID: <3407037a3efc7a6bb8dd9c54001a25a0@ymail.com> From: "Business Network" To: Date: Fri, 31 Dec 2010 12:14:01 -0700 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Succeed in a Tough Economy! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 19:14:10 -0000 Succeed in a Tough Economy! A small business can turn=20 a bad economy into a great opportunity. According to a = recent=20 study, more business owners and managers are turning to E-mail=20 Marketing then = ever=20 before. Every other type of advertising has declined in sales = -=20 except E-mail Marketing. This=20 proves that it works! When you launch your E-mail = Marketing=20 program with [1]our=20 company you have access to powerful tools that can help = you grow=20 revenue, find new customers and achieve your online marketing=20 goals. We Have Access To 45=20 Million Businesses & 200=20 Million Consumers. Drive traffic directly to your = website=20 with ease using our [2]turnkey e-mail = marketing=20 programs! [3]Click=20 Here to get our FREE Information Packet! OUR OFFER: Our Graphics Team Designs Your AD You Pick Your Ideal = Target=20 Audience We = Provide=20 OPT-IN Customer List We Scrub Do not E-mail Database Send E-mails Using = our=20 Servers Track=20 Click-Thru's & Open Rates Direct Traffic To = Your Web=20 site Customer = Contacts=20 You Interested Blast Can=20 Broken Up As You Need 1 (800) = 330-4022 [4]Click=20 Here to get our FREE Information Packet! The Decision To Grow Is = Yours.=20 Are You Ready? <= /td> [5][ljoq3"] References Visible links 1. 3D"mailto:getsalesinstantly@gmx.com?cc=3Dfreebsd-stable@freebsd.org&am= 2. 3D"http://tiny.cc/96w2p" 3. 3D"mailto:getsalesinstantly@gmx.com?cc=3Dfreebsd-stable@freebsd.org&am= 4. 3D"mailto:getsalesinstantly@gmx.com?cc=3Dfreebsd-stable@freebsd.org&am= 5. 3D"mailto:stopthisstuff@gmx.com" Hidden links: 6. 3D"http://tiny.cc/96w2p" From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 22:30:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EA1B106566C for ; Fri, 31 Dec 2010 22:30:38 +0000 (UTC) (envelope-from cforgeron@acsi.ca) Received: from mta02.eastlink.ca (mta02.eastlink.ca [24.224.136.13]) by mx1.freebsd.org (Postfix) with ESMTP id DC89D8FC0C for ; Fri, 31 Dec 2010 22:30:37 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ip04.eastlink.ca ([unknown] [24.222.39.52]) by mta02.eastlink.ca (Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)) with ESMTP id <0LEB00DZRBT0RYB2@mta02.eastlink.ca> for freebsd-stable@freebsd.org; Fri, 31 Dec 2010 18:00:36 -0400 (AST) X-CMAE-Score: 0 X-CMAE-Analysis: v=1.1 cv=zW4qkwwpA+AM09VaNOLkucDBqffYZTwBSaEYifkV/P4= c=1 sm=1 a=kj9zAlcOel0A:10 a=6I5d2MoRAAAA:8 a=CaSQRWpuhzfPvHMvIKAA:9 a=zz4y56aexYhWLkgD6osA:7 a=HmRrJTQEN8vC8F_CZwn515ix8TcA:4 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=ZjIqTmGINkQKjhCx/60B3Q==:117 Received: from blk-222-10-85.eastlink.ca (HELO server7.acsi.ca) ([24.222.10.85]) by ip04.eastlink.ca with ESMTP; Fri, 31 Dec 2010 18:00:36 -0400 Received: from server7.acsi.ca ([192.168.9.7]) by server7.acsi.ca ([192.168.9.7]) with mapi; Fri, 31 Dec 2010 18:00:36 -0400 From: Chris Forgeron To: "freebsd-stable@freebsd.org" Date: Fri, 31 Dec 2010 18:00:36 -0400 Thread-topic: ZFS v28 and zil_disable Thread-index: AcupNZahBcx36wFoRi2rwBWUj768Gg== Message-id: Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Subject: ZFS v28 and zil_disable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 22:30:38 -0000 BTW, I'm noticing the removal of vfs.zfs.zil_disable as well - It's not listed as a sysctl when I check vfs.zfs, but I see it's still in the source code; In usr/src/sys/cddl/ : # grep -r zil_disable * cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zil.h.orig:extern int zil_disable; cddl/contrib/opensolaris/uts/common/fs/zfs/zil.c.orig:int zil_disable = 0; /* disable intent logging */ cddl/contrib/opensolaris/uts/common/fs/zfs/zil.c.orig:TUNABLE_INT("vfs.zfs.zil_disable", &zil_disable); cddl/contrib/opensolaris/uts/common/fs/zfs/zil.c.orig:SYSCTL_INT(_vfs_zfs, OID_AUTO, zil_disable, CTLFLAG_RW, &zil_disable, 0, cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c.orig: if (zil_disable) { cddl/contrib/opensolaris/uts/common/fs/zfs/zvol.c.orig: if (bp->bio_cmd == BIO_FLUSH && !zil_disable) I know Sun was trying to move away from allowing people to disable the ZIL, but was this by design in the FreeBSD port, or are we just missing some code to link the sysctl up with the code to easily disable the ZIL? I'll try setting zil_disable=1 in the source tomorrow and recompile to see if it works. It's such a huge speed increase for some operations (80MB/sec with ZIL, 450 MB/sec without ZIL) that I still use zil_disable. I'll also have to check my 9.0-CUR v28 patch, although I assume it's the same. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Jean-Yves Avenard Sent: December-27-10 1:31 AM To: jhell Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic Jean-Yves PS: saving my 5MB files over the network , went from 40-55s with v15 to a constant 16s with v28... I can't test with ZIL completely disabled , it seems that vfs.zfs.zil_disable has been removed, and so did vfs.zfs.write_limit_override _______________________________________________ From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 23:33:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4782A106564A for ; Fri, 31 Dec 2010 23:33:54 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id CC3088FC12 for ; Fri, 31 Dec 2010 23:33:53 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id oBVNXkT7006117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Jan 2011 10:33:48 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id oBVNXjni042610; Sat, 1 Jan 2011 10:33:45 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id oBVNXhqQ042607; Sat, 1 Jan 2011 10:33:43 +1100 (EST) (envelope-from peter) Date: Sat, 1 Jan 2011 10:33:43 +1100 From: Peter Jeremy To: Dan Langille Message-ID: <20101231233343.GB48579@server.vk2pj.dyndns.org> References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> <4D1BD8D0.5010402@langille.org> <4D1C4A2D.4020206@infracaninophile.co.uk> <4D1C7929.3040809@langille.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <4D1C7929.3040809@langille.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 23:33:54 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Dec-30 07:20:57 -0500, Dan Langille wrote: >The reason I've not installed ZFS on root is because of the added=20 >complications. I run the OS on ufs (with gmirror) and my data is on=20 >ZFS. We must be hanging out with different groups. Most of the people= =20 >I know don't have ZFS on root. My primary system at home is setup this way - primarily because at the time I built it (Nov 2008), I felt ZFS was a bit immature and wanted to have src and obj on UFS so I could do a rebuild if I lost access to ZFS for some reason. My experience has been that the UFS root has caused me far more headaches than the ZFS parts. I've since done some reconfiguration and plan to switch to ZFS root soon. Based on my experiences at home, I converted my desktop at work to pure ZFS. The only issues I've run into have been programs that extensively use mmap(2) - which is a known issue with ZFS. --=20 Peter Jeremy --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAk0eaFcACgkQ/opHv/APuIfZVACghX22o9VApA1p7JXQjp9wo2hV FRQAnA8MIfY2HaPawlVqdpeXb3ebTcYw =+olt -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 31 23:47:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B98781065670 for ; Fri, 31 Dec 2010 23:47:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6195A8FC08 for ; Fri, 31 Dec 2010 23:47:49 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta01.westchester.pa.mail.comcast.net with comcast id pzfk1f0021vXlb851znpPJ; Fri, 31 Dec 2010 23:47:49 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta17.westchester.pa.mail.comcast.net with comcast id pzno1f0082tehsa3dznojD; Fri, 31 Dec 2010 23:47:49 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 21FE59B427; Fri, 31 Dec 2010 15:47:47 -0800 (PST) Date: Fri, 31 Dec 2010 15:47:47 -0800 From: Jeremy Chadwick To: Peter Jeremy Message-ID: <20101231234747.GA8171@icarus.home.lan> References: <4D1AF388.3080107@infracaninophile.co.uk> <4D1B7431.7070808@infracaninophile.co.uk> <4D1BD8D0.5010402@langille.org> <4D1C4A2D.4020206@infracaninophile.co.uk> <4D1C7929.3040809@langille.org> <20101231233343.GB48579@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101231233343.GB48579@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Dan Langille Subject: Re: slow ZFS on FreeBSD 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Dec 2010 23:47:49 -0000 On Sat, Jan 01, 2011 at 10:33:43AM +1100, Peter Jeremy wrote: > On 2010-Dec-30 07:20:57 -0500, Dan Langille wrote: > >The reason I've not installed ZFS on root is because of the added > >complications. I run the OS on ufs (with gmirror) and my data is on > >ZFS. We must be hanging out with different groups. Most of the people > >I know don't have ZFS on root. > > My primary system at home is setup this way - primarily because at the > time I built it (Nov 2008), I felt ZFS was a bit immature and wanted > to have src and obj on UFS so I could do a rebuild if I lost access to > ZFS for some reason. My experience has been that the UFS root has > caused me far more headaches than the ZFS parts. I've since done some > reconfiguration and plan to switch to ZFS root soon. > > Based on my experiences at home, I converted my desktop at work to > pure ZFS. The only issues I've run into have been programs that > extensively use mmap(2) - which is a known issue with ZFS. Is your ZFS root filesystem associated with a pool that's mirrored or using raidzX? What about mismatched /boot content (ZFS vs. UFS)? What about booting into single-user mode? http://wiki.freebsd.org/ZFSOnRoot indirectly hints at these problems but doesn't outright admit them (yet should), so I'm curious to know how people have solved them. Remembering manual "one-offs" for a system configured this way is not acceptable (read: highly prone to error/mistake). Is it worth the risk? Most administrators don't have the tolerance for stuff like that in the middle of a system upgrade or what not; they should be able to follow exactly what's in the handbook, to a tee. There's a link to www.dan.me.uk at the bottom of the above Wiki page that outlines "the madness" that's required to configure the setup, all of which has to be done by hand. I don't know many administrators who are going to tolerate this when deploying numerous machines, especially when compounded by the complexities mentioned above. The mmap(2) and sendfile(2) complexities will bite an junior or mid-level SA in the butt too -- they won't know why software starts failing or behaving oddly (FreeBSD ftpd is a good example). It just so happens that Apache, out-of-the-box, comes with mmap and sendfile use disabled. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |