On Tue, Jun 14, 2016 at 10:54 AM, Michele Marcon <M.Marcon@xxxxxxxxxxxxxx> wrote: > When the garbage collector starts, it will notice that the checkpoint "from the future" is protected and will not remove it. > The problem is that it will not remove subsequent checkpoints (but with timestamp that shouldn't be protected), and therefore there won't be any garbage collection until 2020. > > The only workaround is to manually remove the "future" checkpoints with rmcp. > > Is this a known issue? Thanks! I was bit by the opposite problem on my day to day laptop. I set my time in the past for some hours, then after restoring the correct time, the garbage collector destroyed all the checkpoints from the past. At this point, the FS was screwed. I reported the issue and can't find the patch that fixed it but I guess this is the kind of protection to be expected from my issue, checkpoints from the future can't be cleaned up. Pseudo-References: http://www.spinics.net/lists/linux-nilfs/msg00592.html -- 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
