[Jaunty beta] many ext4-fs errors

Bug #350268 reported by ®om
20
Affects Status Importance Assigned to Milestone
linux (Fedora)
Invalid
Unknown
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

For about one week, I have a lot of ext4 problems, in ubuntu jaunty alpha 6 then jaunty beta.

I had a "file system check failed" during a boot, so I "fsck" it and repaired manually.
It seemed to be ok, but most of the programs were segfaulting very often, and reading some files (.ssh/id_rsa for example) gave an 'IO/Error'.

So I formated and reinstalled ubuntu jaunty alpha 6. It seemed to be ok... until...
I downloaded ubuntu jaunty beta (yesterday), and *once the download is finished* (with wget), i wanted to check the md5. Even if the download was finished, several calls to md5sum gave different results :

a4c05ed77f2ebf111a9740fbfe4a9e55 ubuntu-9.04-beta-desktop-amd64.iso
b6fbb04839d46ef78f823e7f4d82f32f ubuntu-9.04-beta-desktop-amd64.iso
c7efb3c4d26310c27a7989cc3b14fb61 ubuntu-9.04-beta-desktop-amd64.iso
a00cfa5c31d1b9d6c4a0edf151dbcf79 ubuntu-9.04-beta-desktop-amd64.iso

Nothing was writing on the file, and "stat ubuntu-9.04-beta-desktop-amd64.iso" were always giving the same result:
Access: 2009-03-27 08:16:13.506973122 +0100
Modify: 2009-03-24 01:39:08.000000000 +0100
Change: 2009-03-27 08:16:12.807450260 +0100
(it was about 08:35, the download finished at 08:16, so no changes for 20 minutes)

So I thought it could be an ext4 problem.

After a smple reboot, all was ok, and I have the right md5 :
4a9d522d06f118fa72dbd613a02ca43e ubuntu-9.04-beta-desktop-amd64.iso

I reformated, and installed jaunty beta this morning, also using ext4.

But I have still a lot of segfaults (core dumped) on many applications, and I have a lot of EXT4-fs errors
Mar 28 13:39:09 rom-laptop kernel: [ 1674.592845] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98

I attach the result of :
grep EXT4 /var/log/syslog

My kernel is :
$ uname -r
2.6.28-11-generic

Tags: ext4 jaunty
Revision history for this message
®om (rom1v) wrote :
description: updated
description: updated
®om (rom1v)
description: updated
description: updated
Revision history for this message
Philip Muškovac (yofel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux since fs-drivers are in the kernel.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
®om (rom1v) wrote :

The problems seems to be my harddrive. I reinstalled using EXT3, I have still a lot of problems :(

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi rom1v,

Sounds like this might be leaning towards being a hw issue. Please keep us posted if you happen to get a new hard drive and are able to test. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
kaliif (kalev-takkis) wrote :

It does look similar to my conditions. But my files corrupted with both ext3 and ext4 and I'm pretty sure it's not the hd (problems started with jaunty install, hd is new, smartmontools showed no errors)

Revision history for this message
®om (rom1v) wrote :

I said a bit too quickly that the problem was hardware, because jaunty alpha/beta/rc had problems both with EXT3 and EXT4.

As I saw several people having the same problems as me, I reinstalled Intrepid (ext3), and I have no problem at all !

I think there was a regression between jaunty alpha 4 and jaunty alpha 6 (in kernel), everything worked fine about 2 weeks using jaunty alpha 6 EXT4, but after an upgrade, I have all the problems I described, which have persisted even after format/reinstallation.

If you need more information, please ask, I think it's a very critical bug if it is confirmed.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
®om (rom1v) wrote :

Please replace "about 2 weeks using jaunty alpha 6 EXT4, but after an upgrade…" by :
"about 2 weeks using jaunty alpha 4 EXT4, but after an upgrade…" in my previous message.

Carey Underwood (cwillu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Carey Underwood (cwillu) wrote :

Per conversation on irc, waiting for lspci -vvnn, /var/log/kern.log and /etc/fstab

Changed in linux (Fedora):
status: Unknown → Confirmed
Revision history for this message
fuchur (ckellner-gmx) wrote :

same phenomenon here, in case it has not been noted I just want to add that all (r)om, kaliif (according to ubuntuforums) and the fedora user all use 64 bit jaunty.

Revision history for this message
fuchur (ckellner-gmx) wrote :

to be clear about it, i also used the 64 bit jaunty version, but in the meantime i went back to intrepid

Revision history for this message
fuchur (ckellner-gmx) wrote :

Since Jaunty is released, I installed it on a partition on my harddisk, hoping that the released version would work for me.
As soon as I installed a few packages, these file system errors show up again, so I used an intrepid live-cd to fix the errors and than booted to intrepid. As usual, no file system errors in intrepid.

I am providing some of the files requested above:

Revision history for this message
fuchur (ckellner-gmx) wrote :
Revision history for this message
fuchur (ckellner-gmx) wrote :

note that while kern.log and fstab are from the jaunty partition, the result of lspci-vvnn was obtained from intrepid.

Revision history for this message
®om (rom1v) wrote :

After a fresh reinstallation of jaunty final, during an apt-get install :
Write error on output file - write (30 read-only file system)

I will attach the requested files.

Revision history for this message
®om (rom1v) wrote :

During reboot : EXT4-fs error (device sda1): __ext4_get_inode_loc: unable to read inode block - inode=377, block=3941531671

Revision history for this message
®om (rom1v) wrote :
Revision history for this message
®om (rom1v) wrote :
Revision history for this message
®om (rom1v) wrote :
®om (rom1v)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
®om (rom1v) wrote :

I reinstalled Intrepid 64 bits, no problem at all… It is definitely a software problem appeared between jaunty alpha 4 and jaunty alpha 6.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
®om (rom1v) wrote :

I just installed Jaunty 32 bits (instead of 64 bits) EXT4, it seems to work without any problem until now…

Revision history for this message
kikvors (kikvors) wrote :

Same issue on brand new hard drive (320 Gb Western Digital Scorpio Black). I installed 64-bit Jaunty beta/ RC on a new hard drive and got broken apt, segfaults and random loss of data. I returned the hard drive thinking it may be a faulty drive. I just got a replacement for the initial hard drive and installed Jaunty final release. Again I am getting the same issue with broken apt and fsck warnings!

Revision history for this message
kikvors (kikvors) wrote :
Revision history for this message
kikvors (kikvors) wrote :
Revision history for this message
kikvors (kikvors) wrote :
Revision history for this message
kikvors (kikvors) wrote :

I am now pretty certain this has to do with the kernel as the comments in the below bug report reflect exactly my epxeriences after a fresh install of Jaunty 64-bit:

jaunty kernel 2.6.28-11 kernel update renders the system un-usable
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/346691

Revision history for this message
kikvors (kikvors) wrote :

Upgrading to a newer kernel *see links on bug 346691 to get installable debs* fixed my problems.

Revision history for this message
KJ (cortexbuster) wrote :

this is actually a duplicate of bug 346691, since you have about the same hardware config (intel mobo with nvidia gfx etc) as we do.
errors won't occur if you use kernel version 2.6.28-9-generic.
otherwise they will, doenst matter which filesystem you use.
this is a bug in the 2.6.28-11 kernel.

Changed in linux (Fedora):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.