From owner-freebsd-fs@FreeBSD.ORG  Wed Nov 28 15:13:51 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 43D783A0;
 Wed, 28 Nov 2012 15:13:51 +0000 (UTC)
 (envelope-from mjguzik@gmail.com)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
 [209.85.212.170])
 by mx1.freebsd.org (Postfix) with ESMTP id 961148FC12;
 Wed, 28 Nov 2012 15:13:50 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id hq7so4843813wib.1
 for <multiple recipients>; Wed, 28 Nov 2012 07:13:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=date:from:to:cc:subject:message-id:references:mime-version
 :content-type:content-disposition:in-reply-to:user-agent;
 bh=A5jhlstTmUpHmRZpe1SJhVlhsyqUR1H72Zgn68IcUks=;
 b=wRkZio3yL2kYFjomzgZ/VmoNtLCKDoBOr7+u8/p+2nkuG0PtEvC+nAxdyAP/QA6Eh2
 iNh7LvgibI/FLFQ3UWJa7bGzLjR+SR6Mq920o+7sJjj0VCQBxp2ii6kRdniYmHQfu7YE
 0VeskJZvudd08L2ojtVgYKxITRsQvLnbw2Cib9SPwQZp8Z5JIX+b6FXaufm2bqoe1wEx
 qd4Ge56dNJQ3ouX4PUwrSiH7AQ04qCwbPxeJDIWwxXGJiNL60Nj5aW8EJmZu2JqQ4uLv
 dQ6JxnHDcszgf64QgUhCJuNa3TRPTvsQqeH+rM2ts0JifGAe6Wopa7kIG/OqWYZUKNsz
 54Fw==
Received: by 10.180.100.132 with SMTP id ey4mr33441340wib.9.1354115624390;
 Wed, 28 Nov 2012 07:13:44 -0800 (PST)
Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net.
 [2001:470:1f08:1f7::2])
 by mx.google.com with ESMTPS id w5sm8334414wiz.10.2012.11.28.07.13.42
 (version=TLSv1/SSLv3 cipher=OTHER);
 Wed, 28 Nov 2012 07:13:43 -0800 (PST)
Date: Wed, 28 Nov 2012 16:13:36 +0100
From: Mateusz Guzik <mjguzik@gmail.com>
To: Boris Astardzhiev <boris.astardzhiev@gmail.com>
Subject: Re: NANDFS eats itself up
Message-ID: <20121128151336.GC17871@dft-labs.eu>
References: <CAP=KkTwX6t=6a_b7osbce5wLXrEEr_ryChAx-G5B24xOQw-q8g@mail.gmail.com>
 <20121128104218.GA17871@dft-labs.eu>
 <CAP=KkTwdh631nrTScuG6v4rdvk8zJMsOPKosc2-WGa3-aWp4EQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAP=KkTwdh631nrTScuG6v4rdvk8zJMsOPKosc2-WGa3-aWp4EQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-fs@freebsd.org, gjb@semihalf.com,
 Grzegorz Bernacki <gber@freebsd.org>, stanislav_galabov@smartcom.bg
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 15:13:51 -0000

On Wed, Nov 28, 2012 at 05:06:12PM +0200, Boris Astardzhiev wrote:
> Yes, I do. I've made this to repeat via a script. The interval between each
> SCP transfer is 100s. I thought it would give just enough time to the fs
> for reclaiming its space back.
> 
> Now I stopped the transfers and doubled the vfs.nandfs.cleaner_segments to
> 10. The fs has no files in it but it reports "~9.6MB" of used space. 4+
> hours later it has NOT changed at all it still reports "~9.6MB" Used.
> 

Now this indeed sounds like a bug. Can you enable debug like this:
# sysctl vfs.nandfs.verbose=0xffffffff

The kernel will start printing a lot of debugging information. With
default configuration of syslog this will end up in /var/log/messages.
Capture something like 30 seconds of output and post it somewhere.

-- 
Mateusz Guzik <mjguzik gmail.com>