From owner-freebsd-fs@FreeBSD.ORG Thu May 13 06:44:30 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAE41106566C for ; Thu, 13 May 2010 06:44:30 +0000 (UTC) (envelope-from c.kworr@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 76CEE8FC16 for ; Thu, 13 May 2010 06:44:30 +0000 (UTC) Received: by fxm1 with SMTP id 1so1045523fxm.13 for ; Wed, 12 May 2010 23:44:29 -0700 (PDT) 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=3U1vlDIwkm4TAVQCK1i7l2KjTzJaOIrDZAEsQ3Qa0xc=; b=EQWSvkh3bIh+b0pfBbpkVkw6xP9jARklQREvKlSSRKCOlQCE840EyGXoWWhZb3ssRl JIEdqkcEPdzliQ7teKxeNIl3VfLpyEUURP7wTHxVuhrdDqvyWqVoUSWPw/5rRh70py9U qyT2Wduo4bjrZEZ4HcOwmIkK78KGM+qBnFALs= 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=d+2Z2Nlhry1bGCZ3D7x/YozwS8TBqkmHGXL60dF8ebCBRUXTeau4uIAvzKaPtdwgd7 YlXC8otHAdkkGT3TCyxvry8h0DguRJC1ADGkjEyb/IgkR7iKP8xIhQ4ZDZeDs1AUBgxz ITzxI62op1j2U9JsuAjYcSUgQW0RZ+pXL+fGk= MIME-Version: 1.0 Received: by 10.103.4.13 with SMTP id g13mr5312470mui.12.1273733069129; Wed, 12 May 2010 23:44:29 -0700 (PDT) Received: by 10.102.244.10 with HTTP; Wed, 12 May 2010 23:44:29 -0700 (PDT) In-Reply-To: <4BEB9327.6040405@icyb.net.ua> References: <201004291220.o3TCK3Bo029643@freefall.freebsd.org> <4BE09F5D.2080100@gmail.com> <4BEB9327.6040405@icyb.net.ua> Date: Thu, 13 May 2010 09:44:29 +0300 Message-ID: From: Volodymyr Kostyrko To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs Subject: Re: bin/144214: zfsboot fails on gang block after upgrade to zfs v14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2010 06:44:31 -0000 2010/5/13 Andriy Gapon : > This is what I am confused about. > What do you mean by the same 'boot code'? > I originally asked if you have the *latest* bootcode installed, but you s= eem to > be giving contradicting answers... > > You detailed your magic workaround of re-writing data, but you haven't me= ntioned > how you updated your boot code. > Could you please report the actual commands that you use to update the bo= ot > blocks? =C2=A0Just so we are sure that the problem is indeed present in t= he latest code. 1. I have updated bootcode just in month or so before the failure. dd if=3D/boot/zfsboot of=3D/dev/slice count=3D1 bs=3D512 dd if=3D/boot/zfsboot of=3D/dev/slice skip=3D1 seek=3D1024 bs=3D512 Yes, this means revision 206815 was not there. 2. After the computer fails this time I haven't touched bootcode. I see your point and I'll try to retest on recent STABLE. This changes nothing though. http://svn.freebsd.org/viewvc/base/stable/8/sys/boot/zfs/zfs.c?r1=3D199634&= r2=3D206815&pathrev=3D206815 I'll try to retest writing on recent STABLE on i386. Maybe not the bootcode is culprit here. --=20 Sphinx of black quartz judge my vow.