On Fri, Apr 04, 2003 at 01:22:39PM +0700, David Garamond wrote:
i found this on my server log:
mysqld-max: raid.cc:160: my_off_t my_raid_seek(int, long long unsigned int, int, int): Assertion `pos != (~(my_off_t) 0)' failed.
and then mysqld shuts down. i start it again but after a short while the same error appears and mysqld stops again. what does this indicate? a disk failure?
Oh, good. It's not just the machines at Yahoo, then.
I haven't looked into it much yet, but we had a machine hit that a few times. That made me realize that I had been building our MySQL servers with raid support. We don't have any need for it, so I've removed it. But clearly something is funky with the raid code.
I've yet to figure out a way to reproduce the bug. Well, I have't tried very hard either...
Any chance you can? If so, getting it fixed shouldn't be a problem.
we are using 4.0.12, binary RPMs provided at mysql.com. the machine got rebooted and reiserfsck shows some errors. i guess we'll be replacing the disk with another one for now...
after the filesystem is clean, mysqld is still behaving the same. since we could not afford to have any more downtime, i downgraded the installation to 3.23.xx (it's 3.23.54a, not the latest but the RPM files were lying around so i just used them). the system's been running nicely since then. so i guess it's probably the 4.0.x code. that's all i could say for now.
-- dave
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
