-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rar2fs returns wrong timestamp for file using "store identical file as references" feature. #35
Comments
Original issue reported on code.google.com by |
Original issue reported on code.google.com by - _Attachment: [rar2fs-preserve-link-stat.patch](https://storage.googleapis.com/google-code-attachments/rar2fs/issue-35/comment-2/rar2fs-preserve-link-stat.patch)_ |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
* [rar2fs hasse69#37] Fixed a potential memory leak when compiling against libunrar versions prior to 4.2.0. * Fixed a potential memory leak in the collect_files() function. This function is only used when mounting single RAR archives which means it is rather harmless. * Simplified code in function dir_entry_add_hash(). * Changed implementation of utimens * [rar2fs hasse69#35] Fixed a problem with RAR5 stats that were incorrectly inherited for file reference links.
What steps will reproduce the problem?
-oi:0 option scans any size of identical file.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Original issue reported on code.google.com by jyhpsycho on 2014-07-01 11:16:23
The text was updated successfully, but these errors were encountered: