NANDFS eats itself up

[Boris Astardzhiev]

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 <mjguzik at gmail.com> 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 <mjguzik gmail.com>
>