Is there any chance this bug can still affect an ext4 filesystem on a partition that is just slightly under 1TB? I originally experience this bug and, to work around it, re-partitioned my 1.5 TB drive into two partitions. Since then I've not experience any issues until today when I got some corruption out of the blue. I'm wondering if it is possible that the bug still exists with smaller filesystems but only much more infrequenly.
Either way, looking forward to the roll-out of 0.12.5 into lucid-backports so that, if nothing else, I can (somewhat) eliminate the kvm/virtio layer as the source of my problems.
Is there any chance this bug can still affect an ext4 filesystem on a partition that is just slightly under 1TB? I originally experience this bug and, to work around it, re-partitioned my 1.5 TB drive into two partitions. Since then I've not experience any issues until today when I got some corruption out of the blue. I'm wondering if it is possible that the bug still exists with smaller filesystems but only much more infrequenly.
I posted the full details of my "story" here: http:// ubuntuforums. org/showthread. php?t=1570149
Either way, looking forward to the roll-out of 0.12.5 into lucid-backports so that, if nothing else, I can (somewhat) eliminate the kvm/virtio layer as the source of my problems.