Christopher Chan
2004-Apr-23 01:52 UTC
2.6.5 and latest Fedora Core 1 kernels cannot handle files over 2.x GB?
A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1634890784, count = 1 EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1667330926, count = 1 EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1852795252, count = 1 EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1752637555, count = 1 ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal has aborted ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb1) in ext3_orphan_del: Journal has aborted EXT3-fs error (device sdb1) in ext3_truncate: Journal has aborted __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data ext3_abort called. EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
Stephen C. Tweedie
2004-Apr-23 11:23 UTC
2.6.5 and latest Fedora Core 1 kernels cannot handle files over 2.x GB?
Hi, Kernels since 2.4 have all been quite happy with files over 2GB. There were even patches for large file support on some 2.2 kernels at one point, though those never got merged upstream. I doubt that's the problem, especially since: On Fri, 2004-04-23 at 02:52, Christopher Chan wrote:> A mysql database file was copied over to a new box running Fedora Core 1. > The kernel was updated to the latest Fedora release. > However mysqld complains about corrupted tables.> The kernel was then updated to 2.6.5 > mysqld still complains about corrupted tables.> EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in > datazone - block = 1634890784, count = 1Your filesystem is corrupt. You need to run e2fsck to fix it up, and check the files against a backup. There's not enough information here to begin to diagnose _why_ they are corrupt, but on 2.4 systems it's bad hardware 99% of the time. "memtest86" is usually a good place to start. Cheers, Stephen