Yesterday I was installing a router in which there was OpenVPN service, and had to generate a new certificate, those router seem to have the date/time set differently in a way I have to undo my clock of 4 hours (I am at GMT-4) so the certificate are valid and not from the future and prevent OpenVPN to connect, so I changed the time, did my operations, it took 1 hour, and reverted to my real time using ntp-client. When the protection period expired I noticed in my lssu-gtk that the bands were looking like below: ====|..................===== ===========............... .......=============== ===============
= means used and . unused, as you can see there was a band in the middle which was used then unused space again, the log was not contiguous, I checked lssu and have seen the time was in the future for that middle band, I didn't take care about this and let it do its usual garbage collection, when I came back home and turned on my laptop, it took 30 minutes and started to GC the middle part, 15 minutes later I had some applications starting to segfault for "no actual reason", looked at the log, there was a lot of btree errors in NilFS, so I decided to reboot in single mode to mount the partition again, it complained I was mounting a FS with errors, so I remounted read-only and decided to backup everything. At this point I noticed most of the data on the partition was already corrupt, so I dd'ed /dev/zero, mkfs.nilfs2 and restored everything remembering I should never change date again until further notice! At least I had a backup from yesterday and the only changes I had since are stuff I can acquire elsewhere (backup of router config and certificate I will regenerate and change on router.) I guess nilfs_cleanerd should use the internal sequence number instead of the timestamp which can change to do the garbage collection, is that a good guess? Was that a known issue? I'll take this time to ask, even if it would probably not have fixed the problem, if a fsck.nilfs is underway? _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
