On Tue, 2013-01-15 at 16:17 +0100, Sven Eckelmann wrote:
> On Tuesday 15 January 2013 17:57:21 Vyacheslav Dubeyko wrote:
> > Could you share more details about your environment? What version of
> > nilfs-utils do you use?
> >
> > Maybe do you have some NILFS2-related error messages in your system log?
> >
> > Or, maybe, reproducing path is more complex as you described?
>
> System running Debian Wheezy (amd64) with linux 3.2.35-2 and nilfs-tools
> 2.1.4-1. The nilfs partition is a secondary partition on a CFCard and is not
> used in normal situations. There are different processes running in the
> background... for example ntpd. There are no interesting infos in the system
> log (unless you are interested in nilfs_cleanerd output saying nothing else
> than "pause"/"sleep"/"0 segments selected to be cleaned"/...).
>
> Following way is a good way to force a similar problem (this is not the way I
> produced it the first time, but it is a possible scenario):
>
> $ cd /nilfs/
> $ ntpdate-debian
> $ date -s @`date +'%s'|awk '{ print $1+9000}'`
> $ for i in `seq 0 300`; do dd if=/dev/zero of=foo$i count=22528; done
> $ sleep 360
> $ ntpdate-debian
> $ touch asd
> $ rm *
> $ date -s @`date +'%s'|awk '{ print $1+10000}'`
> $ mount -o remount /nilfs/
>
> It is a little bit harsh, but a similar thing can easily happen in real world
> with non-monotonic clocks (but the jumps are usually a little smaller).
>
Yes, I can reproduce the issue. But I think that it doesn't make sense
to change something in timestamp policy of GC. Unfortunately, we have
currently only timestamp policy. And I think that it needs to use
another GC policy in the case of such issue. So, the proper fix will be
adding another GC policy.
Anyway, I think that possible time deviation can achieve about minutes
in real life. And probability to encounter such issue in real life very
low. I think so because it is hardly to encounter in real life of
coincidence such factors as (1) to fill a whole volume and then to
remove all files during several minutes and (2) immediately update
system time.
If you do so by the hands then, from my point of view, you know what you
are doing.
As a resume, I think that proper fix of such issue can be adding of
additional GC policies that is not affected by such use-case.
Thanks,
Vyacheslav Dubeyko.
> Kind regards,
> Sven
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
