Comment 194 for bug 453579
Revision history for this message
| TragicWarrior (bryan-christ) wrote | #194 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Steve, I would hardly call changing the description
from:
"in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4"
to:
"in-place corruption of files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4"
hardly constitutes hijacking. it's not as if we are talking about night and day here. in this case, the original reporter simply didn't know the problem was manifest on smaller files < 512MB. perhaps it is easier to reproduce on larger files, but the evidence now shows that it is a problem on files 45+ MB files.