Issue while SymLinking a Database

2011-01-02 Thread Adarsh Sharma

Dear all,

I am working on a stable solution for resolving Space Issue of data 
directory of MyISAM tables.
We have a table of 70GB in /hdd-1/mysql_data path and there is 10GB 
space available space in Hard Disk.Now the table expects to grow upto 150Gb.


I have some doubts regarding Symlinking a database. The steps involved 
are :-


1. Shutdown the server.
2. Create a new directory and move your database to new drive.
3. Symlink the database in the original directory and change permissions.

This involves a lot of time to move 70Gb data to new place.

Well this wouldn't be the perfect solution I'm looking for.

Is there any particular solution that requires no server shutdown and 
any client query operations affected and simply put new data into 
another partition.


Would Partitioning is the only rescue operation?

Please help me to find a stable and standardized solution.



Thanks  Regards

Adarsh Sharma

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: Issue while SymLinking a Database

2011-01-02 Thread Suresh Kuna
Hey Adarsh,

If no downtime then the only way is lock with write on the table, move to
the new space, create symlink, flush the table.

Remember, this symlinks will have issues if you execute any maintenance on
these tables which are moved.

Better idea - As the tables are MyISAM, move one database dir one at a time
by locking all tables and create a symlink for the database folder.

On Mon, Jan 3, 2011 at 10:56 AM, Adarsh Sharma adarsh.sha...@orkash.comwrote:

 Dear all,

 I am working on a stable solution for resolving Space Issue of data
 directory of MyISAM tables.
 We have a table of 70GB in /hdd-1/mysql_data path and there is 10GB space
 available space in Hard Disk.Now the table expects to grow upto 150Gb.

 I have some doubts regarding Symlinking a database. The steps involved are
 :-

 1. Shutdown the server.
 2. Create a new directory and move your database to new drive.
 3. Symlink the database in the original directory and change permissions.

 This involves a lot of time to move 70Gb data to new place.

 Well this wouldn't be the perfect solution I'm looking for.

 Is there any particular solution that requires no server shutdown and any
 client query operations affected and simply put new data into another
 partition.

 Would Partitioning is the only rescue operation?

 Please help me to find a stable and standardized solution.



 Thanks  Regards

 Adarsh Sharma

 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com




-- 
Thanks
Suresh Kuna
MySQL DBA