From owner-freebsd-current@freebsd.org Tue May 16 18:53:30 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 299FED70F06; Tue, 16 May 2017 18:53:30 +0000 (UTC) (envelope-from srs0=fzxa=4w=sigsegv.be=kristof@codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD6A8E39; Tue, 16 May 2017 18:53:29 +0000 (UTC) (envelope-from srs0=fzxa=4w=sigsegv.be=kristof@codepro.be) Received: from [172.16.32.137] (unknown [103.210.33.250]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id C68059033; Tue, 16 May 2017 20:53:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigsegv.be; s=mail; t=1494960807; bh=r5MlwkYi2hUMbdIHRH6Bn+5pm2QMc6BxZZ8lhLDGe8M=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=2vGoSeqc6IyFSqD4jU15sIi+gwDwpnTeBuCpOjW31soQpZUCd4E9YXbluGk6Id3bZ vk5FVdQAexje7if2PcSyw+3+XZZF10fDvWmrxEZPh9JfKmpf3HodGmmXuGFfM6hZsg mkiDC2g/x6vcVZSgr7ZUpPEIYSBDCJt5JdeHaSzg= From: "Kristof Provost" To: "Andriy Gapon" Cc: "Freebsd current" , freebsd-fs@FreeBSD.org Subject: Re: zfs recv panic Date: Wed, 17 May 2017 00:23:24 +0530 Message-ID: <96BF657D-34A8-4044-BC73-E0BCD1E98E52@sigsegv.be> In-Reply-To: <51bbf691-a8e2-2d16-6a95-c37a474c1dfe@FreeBSD.org> References: <18A74EE1-3358-4276-88EA-C13E28D8563A@sigsegv.be> <98df7d70-4ecb-34f2-7db2-d11a4b0c854a@FreeBSD.org> <51bbf691-a8e2-2d16-6a95-c37a474c1dfe@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit X-Mailer: MailMate (2.0BETAr6082) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2017 18:53:30 -0000 On 16 May 2017, at 19:58, Andriy Gapon wrote: > On 16/05/2017 16:49, Kristof Provost wrote: >> On 16 May 2017, at 15:41, Andriy Gapon wrote: >>> On 10/05/2017 12:37, Kristof Provost wrote: >>>> I have a reproducible panic on CURRENT (r318136) doing >>>> (jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc >>>> dual 1234 >>>> (dual) # nc -l 1234 | zfs recv -v -F tank/jupiter/var >>>> >>>> For clarity, the receiving machine is CURRENT r318136, the sending >>>> machine is >>>> running a somewhat older CURRENT version. >>>> >>>> The receiving machine panics a few seconds in: >>>> >>>> receiving full stream of zroot/var@before-kernel-2017-04-03 into >>>> tank/jupiter/var@before-kernel-2017-04-03 >>>> panic: solaris assert: dbuf_is_metadata(db) == arc_is_metadata(buf) >>>> (0x0 == >>>> 0x1), file: >>>> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c, >>>> line: 2007 >>> >>> could you please try to revert commits related to the compressed >>> send and see if >>> that helps? I assume that the sending machine does not have (does >>> not use) the >>> feature while the target machine is capable of the feature. >>> >>> The commits are: r317648 and r317414. Mot that I really suspect >>> that change, >>> but just to eliminate the possibility. >> >> Those commits appear to be the trigger. >> I’ve not changed the sender, but with those reverted I don’t see >> the panic any >> more. > > Thank you for testing. > Do you still have the old kernel / module and the crash dump? > It would interesting to poke around in frame 14. > > This contains the kernel and crash files: https://www.sigsegv.be/files/zfs_recv_kernel_crash.tar.bz2 I was running r318356 at the time of this panic. Regards, Kristof