I'm going to mark this bug as Invalid (I'm the original reporter)
I've not been able to replicate it on production hardware, and not been
able to replicate it on the hardware where I was originally able to
replicate it with karmic as it existed at release time.
Therefore I can only conclude that the problem was with faulty hardware,
exasperated by a kernel issue that was fixed before karmic was released.
If you are a user still experiencing problems with the ext4 (or any
other) filesystem, including those resulting in fsck errors, then you
don't have the same bug that I reported so should report a new bug.
Don't open this one unless you've snuck into my house and stolen my
laptop <g>
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Karmic)
Status: Triaged => Invalid
** Changed in: linux
Status: New => Invalid
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
