I believe that the failure only occurs when you intentionally *BREAK* your filesystem by using data=writeback, so a factor of two performance penalty for a protection that is unneeded on the default data=ordered mode is unacceptable to me. At the very least the syncing should only be done if data=writeback is detected, or the syncing and renaming should be delayed until after all packages are unpacked if possible, so that it is only done once.
Leaving this in for lucid release to be on the safe side is probably the right thing to do at this point, but this should be revisited later. -- My computer updates are very slow since latest dpkg update https://bugs.launchpad.net/bugs/537241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
