Comment 6 for bug 891277
Revision history for this message
| Shane Hathaway (shane-hathawaymix) wrote Re: [Bug 891277] Re: Files over a certain size get truncated when restored from Trash | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On 11/17/2011 08:14 PM, Paul Everitt wrote:
> Is it safe to say we have some working copies with corrupt files?
Only if people have deleted large files and then undeleted them. This
bug did not break the contents of the archive, it only broke reading
large files from the archive. We can check for affected files as follows:
- Make a list of all file objects with contents larger than 1 MB.
- Compare the length of each of those files with the length of the
archived version. If the length is different, then this bug did not
affect the file. (The bug did *not* truncate files. I think the 4.1 vs.
4.3 MB comment is due to mebibytes vs. megabytes.)
- Compare the md5 sum with the archive. If it's different, flag the file
as possibly broken.
We can do all those steps on staging. If we find any broken files,
restore them from the archive using repozitory 1.0.
I'm guessing we'll find a small number of broken files, if any.
Shane