Date: Tue, 3 Jun 2014 13:38:24 -0700 (PDT) From: Jim Barker <jbarker@nixlike.com> To: Mark Felder <feld@freebsd.org> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, "owner-freebsd-fs@freebsd.org" <owner-freebsd-fs@freebsd.org> Subject: Re: Solaris 10 zfs bug Message-ID: <1401827904.21523.YahooMailNeo@web121106.mail.ne1.yahoo.com> In-Reply-To: <d0293a7de43d9e8d6c79b00465fca6a6@mail.feld.me> References: <1401814138.84520.YahooMailNeo@web121106.mail.ne1.yahoo.com> <d0293a7de43d9e8d6c79b00465fca6a6@mail.feld.me>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark, I was looking at the timeframes that the core dumps occurred and around that time we were doing some zfs sends to replicate some data on there. So either the snapshot creation, zfs send, or snapshot deletion may have triggered the bug. Jim ________________________________ From: Mark Felder <feld@freebsd.org> To: Jim Barker <jbarker@nixlike.com> Cc: freebsd-fs@freebsd.org; owner-freebsd-fs@freebsd.org Sent: Tuesday, June 3, 2014 1:07 PM Subject: Re: Solaris 10 zfs bug On 2014-06-03 11:48, Jim Barker wrote: > FYI: > > I encountered a bug in Solaris 10 that may also be present in the code > that FreeBSD forked some time ago. This is the forum entry I put up > in case it's relevant. > > https://forums.freebsd.org/viewtopic.php?f=48&t=46716&p=261143#p261143 > > Do you have any details on how to reproduce the panic? That would permit the developers to find the bug in the FreeBSD port of ZFS and fix it. From owner-freebsd-fs@FreeBSD.ORG Tue Jun 3 22:17:17 2014 Return-Path: <owner-freebsd-fs@FreeBSD.ORG> Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFC96364; Tue, 3 Jun 2014 22:17:17 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.feld.me", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 414BC2177; Tue, 3 Jun 2014 22:17:16 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]); by mail.feld.me (OpenSMTPD) with ESMTP id 4e3d3317; Tue, 3 Jun 2014 17:17:13 -0500 (CDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; dþld.me; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:sender; s blargle2; bh=KRVx7zFqLflLvZbekt4u5LT4Grw=; b=wqSrA6+4BZhaBe8J2kF SBI8flRA3L+e7tGQxdKFj3yqJIilMzUVwTjG4hGOfPgnRaoGZAVlDg0cgz66sT6g 44cV2/buAJjq6P+9dMEahmPlK5eCLaHZrvjl08Y3zSsAg2KfBQ0HbFhuMPof9gQe 6xiDlhaCCb1vyIXBlkYJzDKZoZ4r3DVwYV5D1DC7cmK0/r8ZwdEGM69z7jI11ac8 qZfU13Cs78dqnMojN/fxRZUAVRnMvEmLSRp/AxQqnulmbr4ntZqKVC+FIZcGRKVI goCLiyVNOMr/zhmin9co18Kxa3INYxHygTNMlZxSWdAp9bqWRaiMliGK9TBTT/cB HtA=DomainKey-Signature: a=rsa-sha1; c=nofws; dþld.me; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:sender; q dns; s=blargle2; b=vMVcZZmnQOqeiIrfv8OE1EJLR6ksKCna3ZRdMRFQyws1p kb0eAtt+MxVuzbycLdpofzAyyM4ybw3NEhPlvHiGtA3jtQPfG2TIsRjlQpMqZgTI j4PtY3Gi73E9tUKvgiaCDrSiMnoFlB3h+gP2+zfEGCx6QINrb2f3majnqGUrmpUo oF91AUKsrHPZZBBYvaGFqHuGI3lehr2nqQpZL3CcWtJ2p/IuIB4f7n1qRx2KgDqF J1YR9n30GbukZgJ3T05dAEPsedB1v9BJjebBHpsllkBwJAXqb8DEzbRUdD5QY/ZC 8NH6ZgSaPY9hOUIZuJiqHzWN20e9aeJ9FEH+sUUHg=Received: from mail.feld.me (mail.feld.me [66.170.3.6]); by mail.feld.me (OpenSMTPD) with ESMTP id 97855967; Tue, 3 Jun 2014 17:17:13 -0500 (CDT) Received: from feld@feld.me by mail.feld.me (Archiveopteryx 3.2.0) with esmtpa id 1401833832-3794-3791/5/4; Tue, 3 Jun 2014 22:17:12 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Subject: Re: Solaris 10 zfs bug From: Mark Felder <feld@FreeBSD.org> In-Reply-To: <1401827904.21523.YahooMailNeo@web121106.mail.ne1.yahoo.com> Date: Tue, 3 Jun 2014 17:17:10 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <10589F87-04C8-4DD9-A8F3-F2DAB89D0641@FreeBSD.org> References: <1401814138.84520.YahooMailNeo@web121106.mail.ne1.yahoo.com> <d0293a7de43d9e8d6c79b00465fca6a6@mail.feld.me> <1401827904.21523.YahooMailNeo@web121106.mail.ne1.yahoo.com> To: Jim Barker <jbarker@nixlike.com> X-Mailer: Apple Mail (2.1878.2) Sender: feld@feld.me Cc: freebsd-fs@freebsd.org, owner-freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems <freebsd-fs.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/> List-Post: <mailto:freebsd-fs@freebsd.org> List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 03 Jun 2014 22:17:17 -0000 On Jun 3, 2014, at 15:38, Jim Barker <jbarker@nixlike.com> wrote: > Mark, > > I was looking at the timeframes that the core dumps occurred and around that time we were doing some zfs sends to replicate some data on there. So either the snapshot creation, zfs send, or snapshot deletion may have triggered the bug. > I personally do quite a few snapshots and zfs send every 15 minutes on a 9.x server and haven't seen this yet. I'd have figured iXSystems would have hit it while doing QA on their TrueNAS product as well if it was as simple as doing a large amount of send/recv testing. However, it's good to have this documented publicly in case someone does come across a similar issue. Perhaps it could be related to zfs attributes on a particular filesystem? (dedup, compression, etc etc) Thanks for the heads up.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1401827904.21523.YahooMailNeo>
