R-Studio and hardlinks issues
Posted: Wed Dec 02, 2015 4:38 pm
In the last several months there were several cases when R-Studio improperly handled hardlinks.
NTFS:
- couple times data extraction from hard links overwrote data on OS drive (admin profile and program data). we haven't seen this recently, so I guess it was already fixed.
- more often we saw our data (admin profile, ...) copied to the destination instead of data from the recovery drive.
HFS:
- data from hard links was ignored during the extraction (flag to extract hardlinks was set).
in the file tree those file/folders were marked, but the upper level folders somehow were not. marking/unmarking files inside hardlinks didn't affect the upper folder status (should be "partial" selection, but was shown as unselected)
may be this has caused the actual issue.
overall we've notices that marking files sometimes create strange effect on the upper folders - in some cases it required to unselect/select files again to set the upper folder status properly (should be "partial", but wrongly shown as "unmarked" of "fully marked").
could you please ask developers to check these issues?
NTFS:
- couple times data extraction from hard links overwrote data on OS drive (admin profile and program data). we haven't seen this recently, so I guess it was already fixed.
- more often we saw our data (admin profile, ...) copied to the destination instead of data from the recovery drive.
HFS:
- data from hard links was ignored during the extraction (flag to extract hardlinks was set).
in the file tree those file/folders were marked, but the upper level folders somehow were not. marking/unmarking files inside hardlinks didn't affect the upper folder status (should be "partial" selection, but was shown as unselected)
may be this has caused the actual issue.
overall we've notices that marking files sometimes create strange effect on the upper folders - in some cases it required to unselect/select files again to set the upper folder status properly (should be "partial", but wrongly shown as "unmarked" of "fully marked").
could you please ask developers to check these issues?