From owner-freebsd-fs@FreeBSD.ORG Wed Nov 28 07:51:55 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 BF76B290; Wed, 28 Nov 2012 07:51:55 +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 13EB98FC12; Wed, 28 Nov 2012 07:51:54 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so12713611lah.13 for ; Tue, 27 Nov 2012 23:51:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=DmLPgQb0+n+BA5vw0GeGhXWlKfqRKSuUzjzlhyaHx9s=; b=hMSKlQwkpQey4DhmKQUv6b0Fu1UBG/bBRExGYrALdGISnIcze8X7zpfby5QL/mI6DZ ofelympp7Vckadppfoe96UwCuBIVbrCKw4SRybFQXYZr4wNJ08EVD5PQm7trwWr+GB5w 2nD0USmUQ8a6JANlQFQbqAvS5ciF1bTK5lflls1AGBrA6f02RQN/MZqC+QyGYDYpeBRU I1XQiikJe97Xg2J0rny0xu0kbAjJLPjggwprbw/WpK35vqhGRs636KhO1y1pb2jK1tWQ 3lBdp1gYwekxLmmzCzqgFNu+NJyWO/w7oGFDVGKcEiOUBzDl8R6rSOCapWEWH2gtZDWm 9IDw== MIME-Version: 1.0 Received: by 10.112.27.99 with SMTP id s3mr7649135lbg.81.1354089113926; Tue, 27 Nov 2012 23:51:53 -0800 (PST) Received: by 10.112.4.2 with HTTP; Tue, 27 Nov 2012 23:51:53 -0800 (PST) Date: Wed, 28 Nov 2012 09:51:53 +0200 Message-ID: Subject: NANDFS eats itself up From: Boris Astardzhiev To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: 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 07:51:55 -0000 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. # uname -a: FreeBSD smartcpe 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r243606:243615M: Tue Nov 27 15:34:50 EET 2012 root@freebsd9:/usr/obj/arm.arm/usr/src2/sys/SHEEVAPLUG arm # sysctl vfs.nandfs vfs.nandfs.cleaner_segments: 5 vfs.nandfs.cleaner_interval: 5 vfs.nandfs.cleaner_enable: 1 vfs.nandfs.cps_between_sblocks: 5 vfs.nandfs.max_dirty_segs: 5 vfs.nandfs.sync_interval: 5 vfs.nandfs.verbose: 0 root@smartcpe:/mnt % df -h Filesystem Size Used Avail Capacity Mounted on 10.100.100.34:/usr/sheeva-fs 7.5G 5.9G 1.0G 85% / devfs 1.0k 1.0k 0B 100% /dev /dev/gnand0s.root 31M *896k* 30M 3% /mnt In the beginning the "Used" value was 128k. 4 hours later we have a "Used" value of "2.4MB": root@smartcpe:/mnt % df -h Filesystem Size Used Avail Capacity Mounted on 10.100.100.34:/usr/sheeva-fs 7.5G 5.9G 1.0G 85% / devfs 1.0k 1.0k 0B 100% /dev /dev/gnand0s.root 31M *2.4M* 28M 8% /mnt After 14h30min it has drained even more space - 7.8MB: root@smartcpe:/mnt % df -h Filesystem Size Used Avail Capacity Mounted on 10.100.100.34:/usr/sheeva-fs 7.5G 5.9G 1.0G 85% / devfs 1.0k 1.0k 0B 100% /dev /dev/gnand0s.root 31M *7.8M* 23M 25% /mnt How do I fix this? Greetings, Boris