From owner-freebsd-current@FreeBSD.ORG Mon Apr 7 19:04:03 2014 Return-Path: Delivered-To: freebsd-current@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 68A82E49; Mon, 7 Apr 2014 19:04:03 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C90C17B1; Mon, 7 Apr 2014 19:04:02 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.8/8.14.8) with ESMTP id s37J3rik021837; Mon, 7 Apr 2014 22:03:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua s37J3rik021837 Received: (from kostik@localhost) by tom.home (8.14.8/8.14.8/Submit) id s37J3rQ5021836; Mon, 7 Apr 2014 22:03:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 7 Apr 2014 22:03:53 +0300 From: Konstantin Belousov To: Jeremie Le Hen Subject: Re: panic: LK_RETRY set with incompatible flags (0x200400) or an error occured (11) Message-ID: <20140407190353.GP21331@kib.kiev.ua> References: <20140210205607.GA3783@caravan.chchile.org> <52F94923.60102@FreeBSD.org> <20140211093529.GB3783@caravan.chchile.org> <20140214191858.GC3783@caravan.chchile.org> <52FF59B8.1080206@FreeBSD.org> <20140218131815.GF3783@caravan.chchile.org> <530360C9.9080609@FreeBSD.org> <20140218133951.GG3783@caravan.chchile.org> <53036380.4010002@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NFhhVVeDTkyNvWHh" Content-Disposition: inline In-Reply-To: <53036380.4010002@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-current@FreeBSD.org, Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Mon, 07 Apr 2014 19:04:03 -0000 --NFhhVVeDTkyNvWHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 18, 2014 at 03:43:28PM +0200, Andriy Gapon wrote: > on 18/02/2014 15:39 Jeremie Le Hen said the following: > > On Tue, Feb 18, 2014 at 03:31:53PM +0200, Andriy Gapon wrote: > >> > >> So, VV_ROOT is indeed set in v_vflag. > >> Thank you. > >=20 > > So there's no need for me to reboot with kib's patch, right? >=20 > You better ask kib. I do not see any misbehavior in ZFS code so far. >=20 Returning to this old thread. I need to see the v_vflag of the nullfs vnode, in addition to the zfs vnode' v_vflag. I suspect that nullfs flag is somehow lost, and this is what my patch tried to restore. But please show me the nullfs vnode dump before. --NFhhVVeDTkyNvWHh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTQvaZAAoJEJDCuSvBvK1BD2QP/26RW/qoSWh9JsRrEkQQIzup RsvwrqM1HBzEV6yTClOTqcabvgCHXTWUl0GOtPzepFJgci87jDli9Aqs/zR8BmQo UmLUP7AR/Vl95WIUNsjcvNUBbQupKD26eJD7wM3z6L9VnJNWjoyFrXyyyzwyypmL NMVsfokw5HB8acq65oFAJohTecJ4do4Qnbz5EkHyojjYNpviL9c1z8ADgqPJcsam 5yl0H+QYzBUL9ZBnaPFZJIjuy0hWAkt8aHi8s2KjhlGAfvi2zt8eAyiWVW1aRdGC Bm5ERYD6HP48pXw/riWgThL40gr+edpJ+FA4NJ0FZMiZ6pKS4NjvVMmKbOQGnKuZ GX1B6k8oT9fdacX1lkXzw42LTmLUUfzVqBTDseqduo+Wh+f4z4MF+Abp46qSg3zu d6HywFuG7TkpphPDwrF5Kc/zVpyqRREwGYOYOlzYpNu8sOUcxnUfX1fikqVFQjtv RBjUiXtkqjfjqpm4CXFufaIv4vi9fKlxveYhgl5V5P8F0zaGfWlVPJUGsdftrCQ1 RyPJ8zAi88jn5tjc4naipbbBnN/Mg7qohI5ulLUcySQkrMXpjxzPJFaxcS5RWVJb cYJ7St92Rp0v/8D7qe39ZnmifCLKbeXBeYxlQnOrgxW1vxth3TRxWLjzKA+BMJha ZcO6WI5mreLylCFfmjd7 =1Z/h -----END PGP SIGNATURE----- --NFhhVVeDTkyNvWHh--