rsync - Dec 2013 - [Bug 10352] New: link-by-hash hardlink-collection maintenance mode

https://bugzilla.samba.org/show_bug.cgi?id=10352

           Summary: link-by-hash hardlink-collection maintenance mode
           Product: rsync
           Version: 3.1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: jimklimov at gmail.com
         QAContact: rsync-qa at samba.org


It is possible that files, for which link-by-hash has created the structured
hardlink directories, would change over time. Of course, this would also change
their hashes.

I propose that a maintenance mode be added to the link-by-hash patch to
discover hash-filenames that no longer match the hash of their contents. One
way would be to incorporate some metadata into the filename of the hash-file
(such as the size which exists there today - maybe add the last modification
timestamp also) and find the hash-filenames whose actual filesystem metadata
does not match the metadata stored in the name. Such files would be candidates
for recalculation of the content hash and subsequent renaming to match both the
current hash value and FS metadata.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=10352

Wayne Davison <wayned at samba.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement

--- Comment #1 from Wayne Davison <wayned at samba.org> 2014-01-19
22:40:48 UTC ---
The idea of the link-by-hash patch was for use on backup servers where files
are never modified in place.  However, perhaps having a way to specify what
info goes into the hash file names would allow someone to do this on their own.
 Ultimately, though, switching over to a filesystem that supports
de-duplicating writes and copy-on-write would be the best bet in the long run.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.