[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Filesystem [/] Full - This sounds bad!
- Subject: Re: [cobalt-users] Filesystem [/] Full - This sounds bad!
- From: "Steven Werby" <steven-lists@xxxxxxxxxxxx>
- Date: Thu Jun 22 15:02:44 2000
Matt Overall <matt@xxxxxxxxxxxx> wrote:
> Have got an email from my RAQ last night politely telling me that it was filesystem
[/] full and that is a bad thing.
Ouch!
> Cobalt implied that by installing mySQL the log files will now be so big that they
will pull the server down, and that I need to
> create a symbolic link from var/logs to home/logs or something to that effect as
the home partition has more space. I am just
> confused to as why I have so much logging anyway! He then went on to say that many
people don;t recover from a filesystem full and
> have to lose all their data!
MySQL has different levels of logging. You can disable them if you like. A smarter
thing would be to configure MySQL to store the logs in your /home partition since
it's a lot larger than the / partition. In fact, to simplify things I typically
install MySQL in the /home partition on the RaQ2s.
> My question is:
> (1)What can I do when/if the server comes back up after my hosting company
generously reboot my machine?
Read up on MySQL logging. Determine what logging you *need*. Some of the logs can
be used in conjunction with the output from mysqldump (the program I hope you're
using to backup your MySQL databases as copying the files themselves will
most_likely_not_work) to rebuild wiped out or corrupted tables.
> (2) Should I start worrying yet?
Yes. You need a plan to monitor your filesystems and take action
before_they_become_full. And if your database data is critical you need a backup and
recovery plan, preferably automated. If you want to do it yourself I'd recommend
getting MySQL by Paul DuBois. If you're looking for outside help there are a few
people on this list who'd probably be able to take on the job, including myself.
Steven Werby {steven-lists@xxxxxxxxxxxx}