From owner-freebsd-current@FreeBSD.ORG Wed Apr 10 22:16:58 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 458B4CF6 for ; Wed, 10 Apr 2013 22:16:58 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id D14DFE22 for ; Wed, 10 Apr 2013 22:16:57 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id y10so6499505wgg.2 for ; Wed, 10 Apr 2013 15:16:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=b3TVLW4KeaH5MfPvQpVqR/bbA/pH3Abt8EohdDJGQ3A=; b=IyQEqzIfVlQ+suHG6dooeQ7kpxu+qyUURkaiJOpgxwnOH74zWUMG80nkE7Jk56dt+B FDf1vhwJSrZ03vGdGTIiqklxNaCl5t1Wg+fjmDbTUf0rjswgT8J9zFQ4rZ14GEPLu4u/ a4lyNGhjYZyka2f7Hw+XN1tn7vphjK6qYKswCRDdW85Uv+itk3IewhD7rxdf+MvpoWXk 1Q+a66hYLhOJn99KkSKdu7J5niMEjI++J6gdlFvJQom7HbggLiVAL5EJIRTFQgw3OCpq 64RmUiWQPgzCtl9QpKEGrDnbI8kCtdSo/XNfAuVpO4/pYqryLyGFK5SxWNdmUOnggkwv Wu2w== X-Received: by 10.194.3.4 with SMTP id 4mr3743211wjy.53.1365632217000; Wed, 10 Apr 2013 15:16:57 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id o5sm2656279wix.3.2013.04.10.15.16.55 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 10 Apr 2013 15:16:55 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 11 Apr 2013 00:16:52 +0200 From: Baptiste Daroussin To: "Eggert, Lars" Subject: Re: newnfs pkgng database corruption? Message-ID: <20130410221652.GB95891@ithaqua.etoilebsd.net> References: <4C9A5BAE-8607-4E3A-8E69-E3993EA9873F@netapp.com> <20130410080228.GB74304@ithaqua.etoilebsd.net> <2F60DB6E-768F-426C-9BE6-737B144D4776@netapp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VrqPEDrXMn8OVzN4" Content-Disposition: inline In-Reply-To: <2F60DB6E-768F-426C-9BE6-737B144D4776@netapp.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 10 Apr 2013 22:16:58 -0000 --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 10, 2013 at 08:09:42AM +0000, Eggert, Lars wrote: > Hi, >=20 > On Apr 10, 2013, at 10:02, Baptiste Daroussin wrote: > > This can usually happen when a user do not have the nfs lock system sta= rted. > > Are you sure that nfs lock is correctly started? >=20 > with NFSv4, the locking system is integrated with the main protocol, it's= no longer separate. >=20 > > If that is the case, there is anyway a bug in pkgng that should catch t= he > > problem and refuse to operate in such situation, I know sqlite to provi= de a > > mechanism that allow us to be able to catch this, I'm not sure yet to u= se it. >=20 > Not sure about that. >=20 > In case anyone wonders, the corruption is quite substantial: >=20 I think I know why let me a couple of days to test a patch. Unfortunatly your database can't be recovered apparently sqlite has some problems with the locking ystem of nfsv4 and has some workaround. Will you be able to test it? Just to warn you firefox may have the same problem with unbundled sqlite. regards, Bapt --VrqPEDrXMn8OVzN4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFl5NQACgkQ8kTtMUmk6EzFFwCfdYYQ17HvYQDozpgGycNEaUO2 5aIAoKOXq39NbGvfXOzV+Q913F1ZkIcM =PbRH -----END PGP SIGNATURE----- --VrqPEDrXMn8OVzN4--