From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 13 20:38:39 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 995748F5; Fri, 13 Mar 2015 20:38:39 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9877211; Fri, 13 Mar 2015 20:38:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1426279092; l=2485; s=domk; d=fuckner.net; h=Content-Type:MIME-Version:Subject:References:In-Reply-To:Cc:To: Reply-To:From:Date; bh=/JrWJ2QROOgHOW12w+sjfZ+ks3ZKV70Ai7MCTsf1a9A=; b=QSKN86SssjVk1F8Rv9Sx1BmNXqLzuRCrB3gkC7tKQP/Kv6nWGq6yI+Ezj4dp0aWqmyz WGV4PR9ySC1fCPpH1Sw1ViyT4Pu7/y2pEDaiDu5M4eqTDdv5lMDsEqw5D/BZ86RsxkPT8 s+gqdCf/2cqLBXUDQaZvPVce/4lMm4Jp6+M= X-RZG-AUTH: :IWUHfUGtd9+6EujMWHx57N4dWae4bmTEGbkn8hussqFHiy/c+oYVPeezIVIZYA== X-RZG-CLASS-ID: mo00 Received: from ptangptang.store (com4.strato.de [81.169.145.237]) by smtp-ox.front (RZmta 37.4 AUTH) with ESMTPSA id x02882r2DKc1Ajs (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate); Fri, 13 Mar 2015 21:38:01 +0100 (CET) Date: Fri, 13 Mar 2015 21:38:01 +0100 (CET) From: Michael Fuckner Reply-To: Michael Fuckner To: Chris H , Adrian Chadd Message-ID: <1037310890.395652.1426279081703.JavaMail.open-xchange@ptangptang.store> In-Reply-To: <72adbbf534c673c111c0b8cec018318b@ultimatedns.net> References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <5503234A.4060103@fuckner.net> , <101866634.392324.1426276184167.JavaMail.open-xchange@ptangptang.store> <72adbbf534c673c111c0b8cec018318b@ultimatedns.net> Subject: Re: Server with 3TB Crashing at boot MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.6.0-Rev36 X-Originating-Client: com.openexchange.ox.gui.dhtml Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" , Oliver Pinter , freebsd-hardware@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 20:38:39 -0000 > Chris H hat am 13. M=C3=A4rz 2015 um 21:28 gesch= rieben: > > > On Fri, 13 Mar 2015 20:49:44 +0100 (CET) Michael Fuckner > wrote > > > > Adrian Chadd hat am 13. M=C3=A4rz 2015 um 19:02 > > > geschrieben: > > > > Hi! > > > > > boot_verbose=3DYES looks to be right. > > > > root@s4l:~ # grep verbose /boot/defaults/loader.conf > > verbose_loading=3D"NO" # Set to YES for verbose loader output > > > > OK, this confused me :-( > In case it's still not clear: > The values your copy of loader.conf located as /boot/loader.conf > overrides the values set in /boot/defaults/loader.conf >=20 that is clear to me, but I was confused by verbose_loading vs boot_verbose From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 13 20:42:08 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 976E4A67 for ; Fri, 13 Mar 2015 20:42:08 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::2]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 222982FE for ; Fri, 13 Mar 2015 20:42:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1426279324; l=2202; s=domk; d=fuckner.net; h=Content-Type:MIME-Version:Subject:References:In-Reply-To:Cc:To: Reply-To:From:Date; bh=vs6uouku9cC80mBHC+Uaqbx2U6xBAy7BrMckhA+mS38=; b=w+Xwc1xg+ZMG44IjLmj4qSIdih7VyGNw+dkkdNJPvX3eSuvCj6Gsi1XmhKhEVUfeuNC 8XTr09E1Sx7mtJgg0alT7Hg/Np00v7xe0fSsiekxAIPGaVcR6LEvacUySo51Dsgqp8qod aw9H+tZ2D39J4IQkjB71l4qjYH30iPAmm0U= X-RZG-AUTH: :IWUHfUGtd9+6EujMWHx57N4dWae4bmTEGbkn8hussqFHiy/c+oYVPeezIVIZYA== X-RZG-CLASS-ID: mo00 Received: from ptangptang.store (com4.strato.de [81.169.145.237]) by smtp-ox.front (RZmta 37.4 AUTH) with ESMTPSA id J0345cr2DKg48QW (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate); Fri, 13 Mar 2015 21:42:04 +0100 (CET) Date: Fri, 13 Mar 2015 21:42:04 +0100 (CET) From: Michael Fuckner Reply-To: Michael Fuckner To: Steven Hartland , Ryan Stone Message-ID: <275339388.395931.1426279324879.JavaMail.open-xchange@ptangptang.store> In-Reply-To: References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <5503234A.4060103@fuckner.net> <55032C1B.5030004@multiplay.co.uk> Subject: Re: Server with 3TB Crashing at boot MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.6.0-Rev36 X-Originating-Client: com.openexchange.ox.gui.dhtml Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 20:42:08 -0000 > Ryan Stone hat am 13. M=C3=A4rz 2015 um 20:40 geschri= eben: > > > On Fri, Mar 13, 2015 at 2:27 PM, Steven Hartland > wrote: > > > Looks like that's panicing when allocating the zfs dbuf hash table, whi= ch > > by my calculation should be requesting 8GB for a 4TB physmem? > > > > Interesting observation. Michael, can you try booting with this patch > applied? There is a bug in the kernel when we attempt to malloc() more > than 4GB. > > https://people.freebsd.org/~rstone/patches/vm_64bit_malloc.diff Now I can kldload zfs without exploding kernel. I'll do some more tests tomorrow, but this looks fine! From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 13 21:17:57 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22E088E3 for ; Fri, 13 Mar 2015 21:17:57 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D10278AB for ; Fri, 13 Mar 2015 21:17:56 +0000 (UTC) Received: by ieclw3 with SMTP id lw3so127475053iec.2 for ; Fri, 13 Mar 2015 14:17:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=82pvanoN/cmbHgq07gbdsXOz9eFkTuZu5zRhXwiIQcg=; b=C8X6lZ0fzQ6QR5NTkd0olUYL6TwtTZogoETyxGhcWZEOoOjIktglRyEMMKgU1DENQ+ o286PPgc4rA/SPz8HEzQ3J7Eia4AiBxPNEmxUL2irzuJnEeVfhGgsoG8zp6RYcr7gIAo 9CuMNEy90KnGO+ZuChbF7156JvNaCbA0XDXT5PTGJUNxEQCdjPuhh/C/LvI4xmg2CVaE OvnVW+GH/xLxZnCcAKuDEz4SaXsLi6FIw1z/7Q0QP+nVArsMTW3CFj6hXpwGCoeD6OHW Luqr/L8zmI2I91GXq5v4V38dNXoPUQ5dO9KVgS92+IuIpZZld9JDIcBGe07KfdHxAj6P 7XXw== MIME-Version: 1.0 X-Received: by 10.107.168.5 with SMTP id r5mr86591388ioe.87.1426281476045; Fri, 13 Mar 2015 14:17:56 -0700 (PDT) Received: by 10.107.156.75 with HTTP; Fri, 13 Mar 2015 14:17:55 -0700 (PDT) In-Reply-To: <275339388.395931.1426279324879.JavaMail.open-xchange@ptangptang.store> References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <5503234A.4060103@fuckner.net> <55032C1B.5030004@multiplay.co.uk> <275339388.395931.1426279324879.JavaMail.open-xchange@ptangptang.store> Date: Fri, 13 Mar 2015 17:17:55 -0400 Message-ID: Subject: Re: Server with 3TB Crashing at boot From: Ryan Stone To: Michael Fuckner Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" , Steven Hartland X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 21:17:57 -0000 On Fri, Mar 13, 2015 at 4:42 PM, Michael Fuckner wrote: > Now I can kldload zfs without exploding kernel. I'll do some more tests > tomorrow, but this looks fine! > Excellent news! I'd be interested to know whether this fixes the panics that you saw when zfs.ko was loaded by the bootloader. It's definitely possible, as the symptoms of this bug are likely to be random memory corruption after zfs initializes, but your crash happened pretty early on and I'm not sure whether zfs would have had a chance to do anything that early. Thanks for all of the work that you did to debug this.