Hi, Jelle de Jong wrote: > Dear Jean-Pierre, > > I am still testing the dedup plugin, I have issues with rdiff-backup > that the checksum of the source and destination are not the same, but > this can be an issue with rdiff-backup. > > However I did get these messages, but I do not know if they are related > to the dedup plugin? > > Mar 21 06:57:37 backup ntfs-3g[12620]: Record 1582022 has wrong SeqNo > (159 <> 156) > Mar 21 06:57:37 backup ntfs-3g[12620]: Could not decode the type of > inode 1582022 > Mar 21 06:57:37 backup ntfs-3g[12620]: Record 1545290 has wrong SeqNo > (296 <> 295) > Mar 21 06:57:37 backup ntfs-3g[12620]: Could not decode the type of > inode 1545290
These errors are thrown by ntfs-3g proper, not by the deduplication plugin. Inconsistencies have been found in the mentioned files, and they are unlikely to be created by the plugin (which does not have updating support), ... but one never knows. Owing to the inconsistencies, ntfs-3g cannot tell if the said files are plain files, directories, sockets, etc. You have to run chkdsk to fix these inconsistencies, but this can lead to losing data, so before doing that, the parameters of these files should be analyzed to assess the possible damage. Please post the outputs of : ntfsinfo -fvi 1582022 /dev/partition ntfsinfo -fvi 1545290 /dev/partition This must be done as root, replacing /dev/partition by the actual partition path (something like /dev/sdc2) Jean-Pierre > > Kind regards, > > Jelle de Jong ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ ntfs-3g-devel mailing list ntfs-3g-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
