** Attachment added: "syslog-ext4" http://launchpadlibrarian.net/24449383/syslog-ext4
** Description changed: 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 seems to be ok, but most of the programs were segfaulting very often. 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 the file, and "stat ubuntu-9.04-beta-desktop-amd64.iso" gave always 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 maybe it's an ext4 problem, which doesn't gives the right result on a fread()? I don't know. 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 : - [code]grep EXT4 /var/log/syslog[/code] + grep EXT4 /var/log/syslog ** Tags added: ext4 jaunty ** Description changed: 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 seems to be ok, but most of the programs were segfaulting very often. 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 the file, and "stat ubuntu-9.04-beta-desktop-amd64.iso" gave always 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 maybe it's an ext4 problem, which doesn't gives the right result on a fread()? I don't know. 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.27-11-generic ** Description changed: 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 seems to be ok, but most of the programs were segfaulting very often. Reading some files (.ssh/id_rsa for example) gave an 'IO/Error'. + 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 the file, and "stat ubuntu-9.04-beta-desktop-amd64.iso" gave always the same result: + 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 maybe it's an ext4 problem, which doesn't gives the right result on a - fread()? I don't know. + 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.27-11-generic ** Description changed: 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.27-11-generic + 2.6.28-11-generic -- [Jaunty beta] many ext4-fs errors https://bugs.launchpad.net/bugs/350268 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
