From owner-freebsd-current@FreeBSD.ORG Thu Apr 11 05:52:21 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 55B5C728 for ; Thu, 11 Apr 2013 05:52:21 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 40403141 for ; Thu, 11 Apr 2013 05:52:21 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,453,1363158000"; d="scan'208";a="39370463" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 10 Apr 2013 22:52:20 -0700 Received: from vmwexceht01-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r3B5qKk0008616; Wed, 10 Apr 2013 22:52:20 -0700 (PDT) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.218]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0342.003; Wed, 10 Apr 2013 22:52:19 -0700 From: "Eggert, Lars" To: Rick Macklem Subject: Re: newnfs pkgng database corruption? Thread-Topic: newnfs pkgng database corruption? Thread-Index: AQHONb70L4N2OxTqe06kCtiGiwd7apjQj/yAgABrVAA= Date: Thu, 11 Apr 2013 05:52:19 +0000 Message-ID: <5BA7ADE3-9E79-4F02-813F-C91BBE6FE360@netapp.com> References: <279486232.724924.1365636491154.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <279486232.724924.1365636491154.JavaMail.root@erie.cs.uoguelph.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.116] Content-Type: text/plain; charset="us-ascii" Content-ID: <00A3F91679369F4289333C5A4A9DF880@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "" 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: Thu, 11 Apr 2013 05:52:21 -0000 Hi, On Apr 11, 2013, at 1:28, Rick Macklem wrote: > Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server > replies with that when the file no longer exists. >=20 > File locking doesn't stop a file from being removed, as far as I know. but the file is still there. Lars