From owner-freebsd-fs@FreeBSD.ORG Mon Jul 15 09:51:11 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EA5EB70; Mon, 15 Jul 2013 09:51:11 +0000 (UTC) (envelope-from godders@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id A2C1BC24; Mon, 15 Jul 2013 09:51:11 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l10so6170420qcy.18 for ; Mon, 15 Jul 2013 02:51:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bqPWOLlgO2DSqvvPF54slTA6ermS9eEi494GtoekWZk=; b=TXKAifsNQUfyW+hlWGlP0+FtnICKhuLSK4B28smJzaQOddkP0gf1Iy3EmBu1qKmXn7 xaKUgG50YbHv8Vx8Fd2c5AlL/srrlVBBGrPyy74NE9UYjI7wo6JIEl9FotSVIKimo96U tbwMXK5OecU8MqxPs+uiZ14J9y21CXUk6vmIZIX/j2ybZi67TSK22r4a50ARQbbPo5uS VNIDaUadTBJgwMbOz4m4obnVuDccs7irErHt3VOp2wmJUbBug8scRm5Qw0r9CdWv1Cvz qHMELBusYb4x/+AC0cF5ZkQ4EGz3YMMT3OUjzhNHT7hOZNferAtOS7S7dpWehROzKWvH 7p3w== MIME-Version: 1.0 X-Received: by 10.49.85.4 with SMTP id d4mr50212452qez.10.1373881870442; Mon, 15 Jul 2013 02:51:10 -0700 (PDT) Received: by 10.49.52.65 with HTTP; Mon, 15 Jul 2013 02:51:10 -0700 (PDT) In-Reply-To: <201306110017.r5B0HFct074482@chez.mckusick.com> References: <51B5A277.2060904@FreeBSD.org> <201306110017.r5B0HFct074482@chez.mckusick.com> Date: Mon, 15 Jul 2013 10:51:10 +0100 Message-ID: Subject: Re: leaking lots of unreferenced inodes (pg_xlog files?) From: Dan Thomas To: Kirk McKusick Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, Palle Girgensohn , Jeff Roberson , Julian Akehurst X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 09:51:12 -0000 On 11 June 2013 01:17, Kirk McKusick wrote: > OK, good to have it narrowed down. I will look to devise some > additional diagnostics that hopefully will help tease out the > bug. I'll hopefully get back to you soon. Hi, Is there any news on this issue? We're still running several servers that are exhibiting this problem (most recently, one that seems to be leaking around 10gb/hour), and it's getting to the point where we're looking at moving to a different OS until it's resolved. We have access to several production systems with this problem and (at least from time to time) will have systems with a significant leak on them that we can experiment with. Is there any way we can assist with tracking this down? Any diagnostics or testing that would be useful? Thanks, Dan