a filesystem fsck on bootup. Here is what I posted on another board
I have a db server its a dual xeon with 2gb ram and a Adaptec 2230SLP with 4 Fujitsu 74GB running in a raid 10 setup and a Western Digital Raptor for a backup drive.
The main os is on the raid array(everything is). I didn't make it so \var\lib\mysql was on the raid array and mount it and have the os on another drive. Now this db server has 2 large databases on it totaling in over 3 million tables and 38gb of space. The server locked up the other night and it was rebooted and so I went to run a check on it when it came up and opened up a screen session and ran "mysqlcheck -rof --all-databases" which I have done many times before nothing unusual. The database was running correctly and the forum was working fine. It usually takes about 6-8 hours to do this and about 2 hours into it I noticed the server was somewhat down but before usually I wouldn't be able to ssh in but I was able to this time. I went and checked the screen session and every table it was checking was saying that it was read only and it was going through all the tables. Going onto the forums that the databases are used for it was throwing up an error saying the sessions table was read only and couldn't write to it. Well I tried to do a shutdown -r now and reboot the server but shutdown just hung I went into top and tried to kill it and couldn't so the server was hard rebooted. It came up and said that there were errors on the drive/raid array and to run a check. Well this has been since sunday on the 11th that it started clearing inodes after running fsck and it has currently cleared around 6 million 19 thousand inodes and counting.
Now after all this my question is do you think my databases are gone? I would hope not since the os was able to load and the server is running its just clearing inodes which means its fixing the file system. I cannot ssh in it is still running now clearing inodes. The thing is its clearing the inodes where the databases are located it seems the inodes for everything else is fine.
so my feeling is the data/databases are still there its just the permissions on them are wrong and it has to do with the inodes to which fsck is fixing now. I mean they were fine and then it said the tables were read only it didn't say they didn't exist that its just read only. I don't know how long this is going to take for the server to fix everthing but its been running since sunday clearing inodes so I take it thats a good thing. Also I was pondering the idea if I could just stop the check and tar up the msql folder even with the wrong permissons and just move them over to another db server that I ordered and is live and reset the permissions there on the new server to what they should be with that mysql database. Will that work?
background is I run a free forum host and there are two db's one for each web server. Each web server is hosting about 30,000 phpbb forums and each forum has about 25 tables so you can do the math on how many tables each db is holding.