With the release of RHEL5.1 our company has started the internal testing and evaluation process for deploying and migrating systems to RHEL5. Initial testing is not going particularly well. Part of out internal test suite is a very simple test of running the following iozone command:
#iozone -r 1m -s 1024m -t 8 This basically simply fires up 8 threads of iozone each running the standard benchmarks using a file size of 1GB and a 1MB record size, nothing particularly fancy. The ext3 filesystem used for this particular test is created on an LVM striped volume created across 6 physical LUNS each 300GB in size thus providing approximately 1.8TB of space. Running this command on RHEL5.1 consistently produces errors on the filesystem with messages like the following: EXT3-fs error (device dm-19) in ext3_orphan_del: Journal has aborted EXT3-fs error (device dm-19) in ext3_reserve_inode_write: Journal has aborted __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data attempt to access beyond end of device dm-19: rw=0, want=17247241224, limit=4688363520 attempt to access beyond end of device If we reboot the very same hardware with RHEL4.5, mount the same volume, and run the same test it works perfectly every time. Has anyone else run significant I/O stress test on RHEL5.1 yet? We have not been able to reproduce this issue with non-striped volumes but we're still very early in our testing and are just looking for community feedback before taking up the problem with Redhat. Thanks, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
