> > Iirc there was some issue with nilfs_cleanerd and timeshifting (and > here we have cp 305344 10 years before 305343). But I think it was > solved, so maybe you have (old) nilfs-utils without the patch? > > Piotr Szymaniak. I'm not sure. I'm using nilfs tools as provided by ArchLinux package nilfs-utils-2.1.4-1: http://www.archlinux.org/packages/core/i686/nilfs-utils/ That package provides nilfs_cleanerd, mount.nilfs2 and the other nilfs-related tools. The nilfs kernel module (/usr/lib/modules/3.4.7-1-ARCH/kernel/fs/nilfs2/nilfs2.ko.gz) is instead provided by linux 3.4.7-1 package: http://www.archlinux.org/packages/core/i686/linux/ These packages seems up to date. They don't seem to apply any patch though. Anyway I've always had this issue with the system date (since before creating the filesystem): the date gets set by NTP as soon as the system connects to internet, and this didn't ever cause any trouble to the filesystem. -- 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
