From owner-freebsd-stable@FreeBSD.ORG Thu Sep 11 03:23:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DCA406DF for ; Thu, 11 Sep 2014 03:23:19 +0000 (UTC) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id AAA7229C for ; Thu, 11 Sep 2014 03:23:18 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 351501F462 for ; Wed, 10 Sep 2014 23:23:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8CDsLyWHSRn for ; Wed, 10 Sep 2014 23:23:12 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <5411159F.6060608@egr.msu.edu> Date: Wed, 10 Sep 2014 23:23:11 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: ZFS on root booting broken somewhere after r270020 References: <51AD1F36-1089-481F-8784-8BD8E6EF020F@icloud.com> <71DEB316-3CDD-4403-A397-BCE684725ABD@icloud.com> <25886C53-39C1-47A8-95F7-494FA6E7ABA2@icloud.com> <20140819071045.GS2737@kib.kiev.ua> <99FB0662-1954-4ECB-939B-06D0AA49C1A1@icloud.com> <20140819074643.GU2737@kib.kiev.ua> <7F008C560B48412AB66A1EBD9382DDAE@multiplay.co.uk> <9315C209-701A-49EF-85D3-ACCCD1513EC3@icloud.com> <959C54D2C8EB4AC8983DC1DA3CE042E3@multiplay.co.uk> <9F24DD48FBEA46C39F98DF600D46DA1A@multiplay.co.uk> <4450778127F4407EB6566A0FE11CD651@multiplay.co.uk> <090135D4-8B1F-42B4-82FC-6FD2F1DBDDA8@icloud.com> In-Reply-To: <090135D4-8B1F-42B4-82FC-6FD2F1DBDDA8@icloud.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Sep 2014 03:23:19 -0000 On 09/10/2014 23:15, Kimmo Paasiala wrote: > >> On 11.9.2014, at 4.25, Steven Hartland wrote: >> >> ----- Original Message ----- From: "Kimmo Paasiala" >> >> snip... >> >>> Just a thought. Is my problem related to the use of GPT labeled partitions >>> in my pool configuration? Your testing shows just "raw" devices like ada0p3 etc. >> >> That "should" have no impact on anything, we disable gptids and diskid's as we >> don't like them adding an extra layer for lookups when admins are working with >> the machines. >> >> Regards >> Steve > > I recreated the pool on the second disk as another single disk pool, performed zfs send -R … | zfs receive -F … > > It works now just fine with the kernel that didn’t work with old pool so there must have been something seriously broken with the old pool. I also noticed the old pool kept repeatedly restarting the resilver operations when I tried to expand it into a mirror. > > Case closed for now. > > -Kimmo > > Were you running a newer kernel with an older format zpool? I heard ixsystems had customers doing that and ran into corruption when they tried to modify the zpool in some way (expand? I don't remember). http://www.bsdnow.tv/episodes/2014_07_09-zfs_war_stories