From owner-freebsd-current@FreeBSD.ORG Fri Apr 12 12:56:17 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8B8CD667 for ; Fri, 12 Apr 2013 12:56:17 +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 745E7661 for ; Fri, 12 Apr 2013 12:56:17 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,462,1363158000"; d="scan'208";a="39852179" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 12 Apr 2013 05:56:11 -0700 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r3CCuBcm011171; Fri, 12 Apr 2013 05:56:11 -0700 (PDT) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.71]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0342.003; Fri, 12 Apr 2013 05:56:10 -0700 From: "Eggert, Lars" To: Rick Macklem Subject: Re: newnfs pkgng database corruption? Thread-Topic: newnfs pkgng database corruption? Thread-Index: AQHONb70L4N2OxTqe06kCtiGiwd7apjQj/yAgABrVACAASIkgIAA5YwA Date: Fri, 12 Apr 2013 12:56:10 +0000 Message-ID: <8A9F25C5-C5E6-4373-85F9-C47642CF1BAE@netapp.com> References: <746529932.761884.1365721847968.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <746529932.761884.1365721847968.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: <2BD9A9B85919E3468B9AB4F14DAED6DC@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: current 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: Fri, 12 Apr 2013 12:56:17 -0000 Hi, On Apr 12, 2013, at 1:10, Rick Macklem wrote: > Well, I have no idea why an NFS server would reply errno 70 if the file > still exists, unless the client has somehow sent a bogus file handle > to the server. (I am not aware of any client bug that might do that. I > am almost suspicious that there might be a memory problem or something > that corrupts bits in the network layer. Do you have TSO enabled for your > network interface by any chance? If so, I'd try disabling that on the > network interface. Same goes for checksum offload.) >=20 > rick > ps: If you can capture packets between the client and server at the > time this error occurs, looking at them in wireshark might be > useful? I will try all of those things. But first, a question that someone who understands pkgng will be able to an= swerr: Is this "fake-pkg" process even running on the NFS mount? The WRKDIR= is /tmp, which is an mfs mount. Lars=