*** This bug is a duplicate of bug 53102 ***
https://bugs.launchpad.net/bugs/53102
[Expired for linux-source-2.6.20 (Ubuntu) because there has been no
activity for 60 days.]
--
ext3 data corruption with kernel 2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug
*** This bug is a duplicate of bug 53102 ***
https://bugs.launchpad.net/bugs/53102
** This bug has been marked a duplicate of bug 53102
Ext3 filesystem corruption - data loss
--
ext3 data corruption with kernel 2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this
** Tags added: corruption ext3
--
ext3 data corruption with kernel 2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.20
--
ext3 data corruption with kernel 2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
Hi,
Thanks for your reply. The system is currently running a livecd boot,
since I am trying to rescue as much data as possible. However, I think
that most information is readily available. For instance, the dmesg
output is already shown in the logs I submited, and I have copied it to
this bug
