From owner-freebsd-fs@FreeBSD.ORG Wed Nov 28 15:06:14 2012 Return-Path: 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 7A12DED9; Wed, 28 Nov 2012 15:06:14 +0000 (UTC) (envelope-from boris.astardzhiev@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 992CC8FC15; Wed, 28 Nov 2012 15:06:13 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so13125957lah.13 for ; Wed, 28 Nov 2012 07:06:12 -0800 (PST) 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=z4k0S718ab35UPUhVUBK50rSRwNMqo7xiGft0+AjtJA=; b=Ll/8PSo+1P5AlLLzE5hwpbNKcDrr+wvCvhZztzP9B+3bv4CskL+f8A1Vb93eaNDtp1 A4NAPZHVKYr4BpEh7+LYkJ69ZmhtbFQms8gLzzhnNChdOgdHMGf1hTVVMANV0C+u6Dj1 qgIbfhmGHRoE7AdYkbt3kcp2UnDiqyFOFHvsm1y4zUyMgiOEh7mP8ubAl83dzjIx69w5 AiIJOiL+LzMUCMo3e+XPmh+PKFUSayz2j0kafzfNjDlvs2BIrqIu4JtPjVoCe4gwUBN3 X8TZTws3gsZg6gRvj2RJAcvWTfsp0ybupmdF2sfxF2FQqx0riGxf+vEN+gEn9vyznCT/ sMOg== MIME-Version: 1.0 Received: by 10.112.27.99 with SMTP id s3mr8164429lbg.81.1354115172427; Wed, 28 Nov 2012 07:06:12 -0800 (PST) Received: by 10.112.4.2 with HTTP; Wed, 28 Nov 2012 07:06:12 -0800 (PST) In-Reply-To: <20121128104218.GA17871@dft-labs.eu> References: <20121128104218.GA17871@dft-labs.eu> Date: Wed, 28 Nov 2012 17:06:12 +0200 Message-ID: Subject: Re: NANDFS eats itself up From: Boris Astardzhiev To: Mateusz Guzik Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org, gjb@semihalf.com, Grzegorz Bernacki , stanislav_galabov@smartcom.bg 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: Wed, 28 Nov 2012 15:06:14 -0000 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. On Wed, Nov 28, 2012 at 12:42 PM, Mateusz Guzik wrote: > On Wed, Nov 28, 2012 at 09:51:53AM +0200, Boris Astardzhiev wrote: > > Hi, > > > > I've been playing with the NANDFS implementation in 10.0-CURRENT on a > > SHEEVAPLUG device. So far i've noticed a strange problem having a simple > > test on it. Firstly I have a partition that is 32MBs and it is mounted in > > /mnt (ROOTFS is over NFS). > > > > I've made an repetitive scp transfer of a 2MB file to the /mnt on the > > sheevaplug. After a delay of 100s the file is rm'ed from /mnt and this is > > repeating for quite awhile now. It seems the FS is eating itself up. > > > > It is unclear from your descripion: do you still scp and rm the file? > If so, it may be just that the cleaner is not able to delete data fast > enough. You can increase vfs.nandfs.cleaner_segments and decrease > vfs.nandfs.cleaner_interval to get more cleaning. > > If you are not doing anything on the fs and used space is growing, can > you reproduce that? Preferably on a md based device (just create a file > with dd of the same size and mdconfig -f it). > > -- > Mateusz Guzik >