MySQL problem, error log posted

[Pocket_Aces]

Hey, Sorry the subject of this thread isn't more descriptive but.. I just don't know what the problem is. I got an error while installing but a google search suggests it isn't important, its the "Warning: asked for 196608 thread stack, but got 126976" thing.

The error log also contains "InnoDB: Error: Write to file ./ibdata1 failed at offset 0 0."
"InnoDB: 8388508 bytes should have been written, only -1 were written"
"InnoDB: Operating system error number 28"
...
"InnoDB: Error number 28 means 'No space left on device'."

So I think this means that my hard drive doesn't have enough space to create the database, correct? This is a problem i've run into before, my hard drive is tiny and I have to be careful to manage space.

IF that is my problem, does anyone have advice on what I can delete to create new space? I barely have anything other than linux and other services on my computer (apache, php, vsftpd), The hard drive is 3.2 gigs. Are there unneccesary services that take up a large amount of space that I don't need? for instance any video or graphic editing utilities or services I don't use?

and if something other than disk space is causing problems, pointing that out would be great too.

thanks,
Pocket Aces

[bwkaz]

Nope, that error means you're out of disk space (if you want to check disk space on your own, df -a is a good command to know ;)).

As for what you can delete... well, it's not my computer, it's yours. :p I don't know what you need and what you don't. I also don't know how you partitioned this disk, so I'm not sure where to look for space that InnoDB could use. You also don't tell which distro you have, so I have absolutely no idea what's installed already. ;) (Not that I automatically would if I did know the distro, either, but it might give some clue. Maybe you could just think back to what you chose during your distro's installation routine?)

However, you can get a 30gig hard drive for $30-40 these days, or thereabouts (I haven't seen any smaller sized drives lately, though -- if you can find one, however, they're probably even less expensive). Why not just do that?

[Pocket_Aces]

I'm using redhat 9. And I plan to get a larger hard drive eventually, hopefully after thanksgiving, but I was hoping to not need to stop everything untill then.

*Re-Edit: I get the following errors when trying to remove the "games and entertainment" and "graphics" packages. I don't want to install anything, but maybe something is checked that I don't know about.

the error is:
"Packages Not Found
The following packages could not be found on your system. Installation cannot continue untill they are installed.
Unlocatable Package Required by
netpbm-progs tetex-latex
imagemagick w3m"

I'll try to figure out where those are coming from, if someone recognizes this I'd really appreciate a response to save some time.

Thanks
Pocket Aces

[Pocket_Aces]

I have an add-on question as well, I did the df -a as you suggested, here was the result:

/dev/hda2 275428 (used) 0 (available) 100%(use%)
/dev/hda1 9324(used) 83208(available) 11%(use%)
none 0 (used) 63028(available) 0%(use%)

If I'm understanding that correctly, is my hard drive partitioned in a horribly inefficient way? That I have a large amount of space in /dev/hda1 and "none" which is unused?

If this is 'bad' how can i correct the problem?

I admittedly know nothing of this, I didn't realize how much harder linux is to use when I started 4 months back, I thought I'd be a pro by now haha.

Becoming more of a newb by the day,
Pocket Aces

[bwkaz]

I don't know what those errors are all about, but as for the other question, it doesn't look like you'll get much space back from changing the partition layout anyway. You've got (about) 90 megs on hda1, and (about) 9 megs of it is used, which is approximately 11%. But for hda2, you've got (about) 275 megs, ALL of which is used. Adding space from hda1 onto hda2 isn't going to help all that much: you only have (about) 83 megs available on hda1.

What would help a lot more is to find the other (about) 2.9 gigs of missing space. Because hda1 + hda2 is only (about) 360 megs, and you said you had a 3.2 gig drive.

[Pocket_Aces]

oops. I wrote the amount wrong. its not 270 megs, its 2.7 gigs, I left out one digit. So there isn't a large missing part of the hard drive.

*edit* I was able to remove two things successfully, still can't get the "graphics" but oh well. It freed up 7% of my hard drive. I uninstalled the mysql rpms, and then re-installed them. I typed "mysql" and got "can't connect to local MySQL server through socket /var/lib/mysql/mysql.sock"

I next typed "mysqld start" and got "warning: asked for 196608 thread stack but got 126976 Fatal error: please read "security" section of the manual to find out how to run mysqld as root! Aborting mysqld: shutdown complete"

I open up the error log and find "error: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 640 pages, max 0 (relevant if non-zero) pages! could not open or create data files. if you tried to add new data files and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files innodb created in this failed attempt. innodb only wrote those files full of zeros, but did not yet use them in any way. but be careful: do not remove old data files which contain your precious data"
"can't init databases"
"aborting"
"innodb warning shutting down a not properly started or created database"
"shutdown complete"
"mysqld ended"

is this still a disk-space issue or is it now a problem with the config file?

Really appreciate the help, once i'm not a moron anymore i'll make sure i help the newbs of the future.

pocket aces

[bwkaz]

Hmm... having never used MySQL or InnoDB before, I'm not sure what's going on.

It looks like it wasn't able to set the size of one of its files to whatever size was configured, though I don't know why that happened (it didn't report an error code or anything). Is your disk full now, after it did that? If so, then I'd still suspect a disk space issue.

[Pocket_Aces]

Still have about 190 megs free on the drive, the databases should only require 15 megs so... I dunno.

I'm wondering if its possible that a file was corrupted when I installed the first time and it is causing the problem now on the new install?

I used rpm -e to get rid of the original bad install. What I'm going to try now is uninstalling this, and then trying to use the database stuff which is on the redhat cds and use "add or remove applications"

Wandering aimlessly through linux:
Pocket Aces