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. -- in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4 https://bugs.launchpad.net/bugs/453579 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
