Dear Joshua, the server has been running for 77 days straight. I checked the boot log and saw that it had found errors caused by a hard down on the same partition that has problems now. fsck being done at booting reported that it corrected the errors. Now, however, fsck still reports errors on this partition, reason: hard downing. So it either never fixed the errors or something caused the fs to look like it hadn't been unmounted before shutdown within the last 77 days, although a shutdown never occured. Still I think it's weird that there are only these 6 specific files, MYD and MYI of the same 3 tables, missing. I will try fix the filesystem and see what happens. Thanks for your help!
Sincerely Daniel -----Original Message----- From: Joshua J.Kugler [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 9:41 PM To: Daniel Geske; Jerry; [EMAIL PROTECTED] Subject: Re: problem: Loosing .MYD Files Daniel - This might be a long shot, but since I've actually run into this problem before, here goes: Check your partitions. I had a server on which this very thing happened, and it turned out there were overlapping partitions. This was all fine and dandy until data was written to those overlapping areas, and created BIG problems when fsck was run. It sounds like your server might have gone down "hard" without a proper shut down, and then run fsck upon startup. Check your boot logs. It is also possible that there was severe corruption on the filesystem as a result of the system going down hard, and fsck did a "best guess" fix, which blew away your data. I may be totally off base, but your symptoms at least match what mine were. Hope that helps. j----- k----- On Wednesday 26 February 2003 00:50, Daniel Geske wrote: > No, I didn't do anything at all. The server ran since months without any > problems, and then suddenly this.. > I just found something that may be related: > A program started writing errors to a log file saying it couldn't insert > into one of the tables that is now missing and the log file grew up to 2 > GB. Certainly the mysql problem occured before the disk was full, else the > log couldn't have been written. > > Could mysql delete data files if there's no more diskspace? > > My monitoring server says there have been 1.3GB left on the server at > 18:05. At 18:01 the problem with mysql started. The log ends at 20:13, that > must have been when the monitoring program shut down for a yet unknown > reason, the pid file still exists. > The MySQL server never stopped running. > Now I have 12GB free, 2GB less compared to before the problem occured. > These 2GB are the log of the monitoring program. > Here's the question: who created 10GB of data and where is that data now? > The 10GB pretty sure weren't the 3 missing tables - the entire database > never gets bigger than 1MB. > > To get back running for now, is it OK to 'touch tablen.MYD' to recreate the > missing files. As I said, the frm files still exist. > > Hope to hear from you soon. > > Sincerely, > > Daniel Geske -- Joshua Kugler, Information Services Director Associated Students of the University of Alaska Fairbanks [EMAIL PROTECTED], 907-474-7601 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
