Date: Tue, 18 Jul 2017 18:47:44 +0200 From: Daniel Genis <daniel@byte.nl> To: =?ISO-8859-1?Q?St=E9phane_Dupille?= <stephane@dupille.org>, =?ISO-8859-1?Q?St=E9phane_Dupille_via_freebsd-stable?= <freebsd-stable@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: Kernel Panic of 10.2-RELEASE Message-ID: <651B3F5F-0856-44B0-A31D-3B5BA4E81F41@byte.nl> In-Reply-To: <B2D01B77-E76E-4E7A-A49F-6FA31E38085D@dupille.org> References: <B2D01B77-E76E-4E7A-A49F-6FA31E38085D@dupille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,=20 Take a look at this commit: https://github=2Ecom/freebsd/freebsd/commit/d9= 9ba5c It might be the issue you're encountering=2E=20 With kind regards,=20 Daniel On 18 July 2017 18:33:02 CEST, "St=C3=A9phane Dupille via freebsd-stable" = <freebsd-stable@freebsd=2Eorg> wrote: >Hello, > >My server is running 10=2E2-RELEASE (yes, I need to upgrade it, but it >works like a charm)=2E Today, I launched this command, as root : ># zfs destroy -r zroot@attic >and the machine crashed : > >Jul 18 18:09:40 penitencier syslogd: kernel boot file is >/boot/kernel/kernel >Jul 18 18:09:40 penitencier kernel: vputx: negative ref count >Jul 18 18:09:40 penitencier kernel: 0xfffff8023037f000: tag zfs, type >VDIR >Jul 18 18:09:40 penitencier kernel: usecount 0, writecount 0, refcount >0 mountedhere 0 >Jul 18 18:09:40 penitencier kernel: flags (VI_FREE) >Jul 18 18:09:40 penitencier kernel: VI_LOCKed lock type zfs: EXCL by >thread 0xfffff8014f242940 (pid 60698, zfs, tid 100747) >Jul 18 18:09:40 penitencier kernel: panic: vputx: negative ref cnt >Jul 18 18:09:40 penitencier kernel: cpuid =3D 1 >Jul 18 18:09:40 penitencier kernel: KDB: stack backtrace: >Jul 18 18:09:40 penitencier kernel: #0 0xffffffff80984ef0 at >kdb_backtrace+0x60 >Jul 18 18:09:40 penitencier kernel: #1 0xffffffff80948aa6 at >vpanic+0x126 >Jul 18 18:09:40 penitencier kernel: #2 0xffffffff80948973 at panic+0x43 >Jul 18 18:09:40 penitencier kernel: #3 0xffffffff809eb7d5 at >vputx+0x2d5 >Jul 18 18:09:40 penitencier kernel: #4 0xffffffff809e4f59 at >dounmount+0x689 >Jul 18 18:09:40 penitencier kernel: #5 0xffffffff81a5fdd4 at >zfs_unmount_snap+0x114 >Jul 18 18:09:40 penitencier kernel: #6 0xffffffff81a62fc1 at >zfs_ioc_destroy_snaps+0xc1 >Jul 18 18:09:40 penitencier kernel: #7 0xffffffff81a61ae0 at >zfsdev_ioctl+0x5f0 >Jul 18 18:09:40 penitencier kernel: #8 0xffffffff80830019 at >devfs_ioctl_f+0x139 >Jul 18 18:09:40 penitencier kernel: #9 0xffffffff8099cde5 at >kern_ioctl+0x255 >Jul 18 18:09:40 penitencier kernel: #10 0xffffffff8099cae0 at >sys_ioctl+0x140 >Jul 18 18:09:40 penitencier kernel: #11 0xffffffff80d4b3e7 at >amd64_syscall+0x357 >Jul 18 18:09:40 penitencier kernel: #12 0xffffffff80d30acb at >Xfast_syscall+0xfb >Jul 18 18:09:40 penitencier kernel: Uptime: 5d6h0m11s > >This is all I found in logs=2E I have only a remote access to this >machine so I have no clue of what was printed on console=2E > >I use zfs on top of geom_eli=2E > >Here is a uname -v : >FreeBSD penitencier=2Edalton-brothers=2Eorg 10=2E2-RELEASE-p9 FreeBSD >10=2E2-RELEASE-p9 #0: Thu Jan 14 01:32:46 UTC 2016 =20 >root@amd64-builder=2Edaemonology=2Enet:/usr/obj/usr/src/sys/GENERIC amd6= 4 > >After rebooting, the machine works well, as far as I can see : >root@penitencier:/var/log # zpool status > pool: zboot > state: ONLINE >scan: scrub repaired 0 in 0h0m with 0 errors on Wed Nov 12 11:20:33 >2014 >config: > > NAME STATE READ WRITE CKSUM > zboot ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > gpt/boot0 ONLINE 0 0 0 > gpt/boot1 ONLINE 0 0 0 > >errors: No known data errors > > pool: zroot > state: ONLINE >scan: resilvered 6,56M in 0h0m with 0 errors on Tue Jul 18 18:13:23 >2017 >config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > da0p4=2Eeli ONLINE 0 0 0 > da1p4=2Eeli ONLINE 0 0 0 > >errors: No known data errors > > >(the pool has been resilvered because I boot once, but put a wrong >passphrase in geli for one of the two drives, so it booted with only >one disk) > >What should I do now ? launch a zfs scrub ? I=E2=80=99m a bit afraid of m= aking >it panic again=2E Should I consider that I got unlucky once ? >(please don=E2=80=99t tell me to upgrade it : I=E2=80=99m currently tryin= g to install a >new server, and I will migrate to it very soon)=2E > >Thanks=2E > >_______________________________________________ >freebsd-stable@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to >"freebsd-stable-unsubscribe@freebsd=2Eorg" --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-stable@freebsd.org Tue Jul 18 22:57:01 2017 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@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 1B6C3DA1C74 for <freebsd-stable@mailman.ysv.freebsd.org>; Tue, 18 Jul 2017 22:57:01 +0000 (UTC) (envelope-from stephane@dupille.org) Received: from mail.nospam.fr.eu.org (saloon.dalton-brothers.org [212.129.29.51]) by mx1.freebsd.org (Postfix) with ESMTP id D488B2B8B for <freebsd-stable@freebsd.org>; Tue, 18 Jul 2017 22:57:00 +0000 (UTC) (envelope-from stephane@dupille.org) Received: from [192.168.1.25] (LStLambert-658-1-7-84.w193-248.abo.wanadoo.fr [193.248.42.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.nospam.fr.eu.org (Postfix) with ESMTPSA id 42CD11065; Tue, 18 Jul 2017 22:56:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dupille.org; s=default; t=1500418587; bh=7Zl3NWVPtHiL5RH+xDaQ8sVTiWk4Nx2KUIl4QbGsgm0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=aiQO1q6riDsXKJHF9Ne02IPe/Aiwk/QvRjLPEk/T+OihBhj3yWjfTYMHNZJ/ifD9j Zf2jeNNWpCGjt+MZvyMV7tbXx2fiipToBORbWW1zeNV45EMD3DL+8SBRW0w86svWDr PTGnfuSWhPIxYN14ghi6KONN42FaEWSq5sBYoG88= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Kernel Panic of 10.2-RELEASE From: =?utf-8?Q?St=C3=A9phane_Dupille?= <stephane@dupille.org> In-Reply-To: <651B3F5F-0856-44B0-A31D-3B5BA4E81F41@byte.nl> Date: Wed, 19 Jul 2017 00:56:27 +0200 Cc: =?utf-8?Q?St=C3=A9phane_Dupille_via_freebsd-stable?= <freebsd-stable@freebsd.org> Content-Transfer-Encoding: quoted-printable Message-Id: <D57DC726-256F-4C8E-BFB3-331C4A070F97@dupille.org> References: <B2D01B77-E76E-4E7A-A49F-6FA31E38085D@dupille.org> <651B3F5F-0856-44B0-A31D-3B5BA4E81F41@byte.nl> To: Daniel Genis <daniel@byte.nl> X-Mailer: Apple Mail (2.3124) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 18 Jul 2017 22:57:01 -0000 > Le 18 juil. 2017 =C3=A0 18:47, Daniel Genis <daniel@byte.nl> a =C3=A9cri= t : >=20 > Hello,=20 Hello, > Take a look at this commit: = https://github.com/freebsd/freebsd/commit/d99ba5c > It might be the issue you're encountering.=20 Yes, it is. Here =E2=80=99s the corresponding PR : = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464 If I understand comments correctly, we have the same issue in 10.3 as = well. So the solution is to avoid destroy snapshots, or upgrade to 11.0. = Or patch the kernel myself. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?651B3F5F-0856-44B0-A31D-3B5BA4E81F41>