Constant checkpointing and cleanerd activity - doesn't play nice with mount --bind ?

[Roman Mamedov <roman-ohbefDXYbNo@public.gmane.org>]

Hello.

I am seeing strange behaviour of nilfs. Namely, a new checkpoint with
significant NBLKINC value is created on every cleanerd step, even though
the file system is not accessed or written to by any apps at the time.
Also, lssu shows that new segments are being continuously appended to
the tail, whereas segments at the top are disappearing.

I am not completely sure, but this might have begun after doing a
bind mount, i.e. `mount --bind /mnt/nilfs/somedir /some/other/dir`.
Timestamp of the first strange checkpoint roughly corresponds to the
time when I did that mount. And when I was trying to unmount it, the
mount point was "busy", and `fuser` reported that the process using it
is nilfs_cleanerd.

Hmm, now I see that `/mnt/nilfs/somedir` also has a zero-sized ".nilfs"
file, just like the root directory of that filesystem. Perhaps this is
the cause of the problem?

My kernel is 2.6.28. Initially, nilfs module and tools were versions
2.0.6, but an upgrade to 2.0.11 did not help.

If it matters, nilfs is created over a LUKS encrypted partition
(/dev/mapper/device).

-- 
With respect,
Roman