I'd like to perform a reverse bisect to figure out which commit upstream fixes this bug. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for the first kernel version that doesn't have this bug: v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/ v3.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/ You don't have to test every kernel, just up until the kernel that first does not have this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: needs-bisect ** Tags removed: needs-bisect ** Tags added: performing-bisect ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054605 Title: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
