- Original Message -
From: Adarsh Sharma adarsh.sha...@orkash.com
Dear all,
I have doubt regarding the storage structure for Innodb files :
Our database server has the following paths :
/dev/sda5 69G 35G 32G52% /hdd1-1
/dev/sdb1 274G 225G
From: Adarsh Sharma adarsh.sha...@orkash.com
Johan De Meersman wrote:
Interesting, but why like this instead of simply larger disks or raidsets ?
It's the IT-Admin Issue , I can't question that and we have only disks of
300GB ( SAS ).
Your admin is supposed to provide services that
Johan De Meersman wrote:
From: Adarsh Sharma adarsh.sha...@orkash.com
Johan De Meersman wrote:
Interesting, but why like this instead of simply larger disks or raidsets ?
It's the IT-Admin Issue , I can't question that and we have only disks of 300GB
( SAS ).
Your admin is
- Original Message -
From: Adarsh Sharma adarsh.sha...@orkash.com
Johan De Meersman wrote:
A Heartiest Thanks from my heart for explaining all these things in a
fantastic manner. I agreed with your suggestions but one thing which
isn't explained from your side , as you go deeper in
You should use a simpl data path and create a separate tablespace for each
InnoDB file
innodb_data_file_path=ibdata1:10M:autoextend
innodb_file_per_table
This way, ibdata1 only contains the metadata and MVCC control data for all
InnoDB files and transactions
Awhile back, you ran a query
Dear all,
I have doubt regarding the storage structure for Innodb files :
Our database server has the following paths :
/dev/sda5 69G 35G 32G52% /hdd1-1
/dev/sdb1 274G 225G 36G 87% /hdd2-1
/dev/sdc5 274G 225G 36G 87% /hdd3-1
/dev/sdd5
You have to round the size of the last data file (ibdata4) and add the
new ones.
You can find more information on the manual:
http://dev.mysql.com/doc/refman/5.1/en/innodb-configuration.html
http://dev.mysql.com/doc/refman/5.1/en/adding-and-removing.html
Carlos
On 9/28/2010 12:59 AM, Vokern
--
From: Carlos Proal carlos.pr...@gmail.com
You have to round the size of the last data file (ibdata4) and add the
new ones.
You can find more information on the manual:
http://dev.mysql.com/doc/refman/5.1/en/innodb-configuration.html
2010/9/28 Jangita jang...@jangita.com:
I do not think there is anything wrong with having one huge file is there?
We have one innodb file of 85GB on ext3.
Is there?
but how about the problem on the file has been increasing continuously?
thanks
--
MySQL General Mailing List
For list
On Tue, Sep 28, 2010 at 10:23 AM, Vokern vok...@gmail.com wrote:
2010/9/28 Jangita jang...@jangita.com:
I do not think there is anything wrong with having one huge file is
there?
We have one innodb file of 85GB on ext3.
In and of itself, there is no problem with that. You may, however,
Hi Vokern,
I suggest to have a single ibdata1 file and use *innodb_file_per_table* to
have multiple .ibd tables.
_Krishna
On Tue, Sep 28, 2010 at 11:29 AM, Vokern vok...@gmail.com wrote:
Hello,
Currently I have the setting:
That's a very good point, actually, as that will also immediately free the
space from tables you delete.
My instincts say that it's marginally slower, though; although honestly I
don't have any data to support that. Does anyone have benchmarks about that
?
On Tue, Sep 28, 2010 at 1:26 PM,
2010/9/28 Krishna Chandra Prajapati prajapat...@gmail.com:
Hi Vokern,
I suggest to have a single ibdata1 file and use innodb_file_per_table to
have multiple .ibd tables.
Can I upgrade to innodb_file_per_table smoothly?
thanks.
--
MySQL General Mailing List
For list archives:
Hi Vokern,
On a running MySQL Server enabling *innodb_file_per_table* makes no changes
to the existing tables. The newly created table (innodb) will be affected
and have thier own .ibd and .frm tables.
Although, you can enable smoothly. But it's better to have it from scratch.
So, that you can
On Tue, Sep 28, 2010 at 1:46 PM, Vokern vok...@gmail.com wrote:
Can I upgrade to innodb_file_per_table smoothly?
When you activate it, the db will keep reading and using your existing
innodb datafiles. All new tables will be created using .ibd files.
Converting your existing tables is done
From: Jangita jang...@jangita.com
I do not think there is anything wrong with having one huge file is there?
There is if you're doing incremental back-ups, in which case adding one byte to
that file costs you 50GB of backup space.
You don't have to take insults personally.
restoring the datafile.
That being said, I don't know wether InnoDB files don't get updated metadata
even if no DML happens in them.
You don't have to take insults personally. You can sidestep negative
energy; you can look for the good in others and utilize that good
Hello,
Currently I have the setting:
innodb_data_file_path=ibdata1:10G;ibdata2:10G;ibdata3:10G;ibdata4:10G:autoextend
Because the last file of ibdata4 is very large (more than 50G), if I
want extend the data to more files, for example, ibdata5, ibdata6...
how to do it?
Thanks!
--
MySQL
.
delme is MyISAM. Works fine.
delmeinno is the InnoDB. The original works fine.
ibdata1 and ib_logfile0 are the original InnoDB files. They work fine.
ibdata1_5 and ib_logfile0_5 are the InnoDB files that were copied from
the local box. Yes, i see that these have 'w' permissions for mysql
group
, MySQL 5.
Trying to copy a local /var/lib/mysql/mydata InnoDB.
The problem: After I copy InnoDB files to a remote box, the MySQL server
on the remote box won't restart. Here are the steps I've followed:
1. Stop the local and remote servers
2. Rename the remote ibdata and ib_logfile0 files
3. Copy
Running a local box and a remote box, both with Fedora 6, MySQL 5.
Trying to copy a local /var/lib/mysql/mydata InnoDB.
The problem: After I copy InnoDB files to a remote box, the MySQL server
on the remote box won't restart. Here are the steps I've followed:
1. Stop the local and remote servers
2
Whil Hentzen wrote:
Michael Dykman wrote:
if you see no errors, check your config... are you sure InnoDB is
enabled ?
I can create a new database and add InnoDB tables to it without problems.
Ack, I lied. No error in the /var/lib/mysql, but there IS an error file
in /var/logs, and it
fine.
delmeinno is the InnoDB. The original works fine.
ibdata1 and ib_logfile0 are the original InnoDB files. They work fine.
ibdata1_5 and ib_logfile0_5 are the InnoDB files that were copied from
the local box. Yes, i see that these have 'w' permissions for mysql
group but I can't see why
Well, you're going to need to state how big a record is, what OS
platform you're using, what MySQL version you're using, and exactly
what error message you get when you're trying to insert that 5th
record.
Your my.cnf would help, too.
-Sheeri
On 5/22/06, Eko Budiharto [EMAIL PROTECTED] wrote:
hi,
I still confuse how store very large database with innodb engine in mysql. I
already activate one file per table (that will creates its own file per table
.idb file), but I only can store 4 records only. Do you mind if someone can
tell me how to store very large database with innodb
Hello.
In my opinion, if you're unable to put InnoDB files on different disks
there is no sense to use separate files. Even more - using the raw
partition for InnoDB might increase a performance. See:
http://dev.mysql.com/doc/mysql/en/innodb-raw-devices.html
However, if you prefer
Hello,
I was wondering if anyone had any knowledge to share regarding
creating many 2GB innodb table space files, vs creating a few 100GB
ones.
It has been my habit to create many smaller for several reasons,
including nfs clients/servers or utlities which don't reliably copy/
back
Hi to all,
I'm working with mysql 4.1, the InnoDb files are ~1.5Gb.
The question is: How to compress a inndodb data file?
My InnoDB free space is ~800Mb.
Thanks in advance.
--
Ivan Cachicatari
http://www.latindevelopers.com
--
MySQL General Mailing List
For list archives: http
Ivan,
- Original Message -
From: Latindeveloper [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Sunday, February 20, 2005 10:51 PM
Subject: InnoDB Files
Hi to all,
I'm working with mysql 4.1, the InnoDb files are ~1.5Gb.
The question is: How to compress a inndodb data file
20607 - killed
050112 12:58:38 mysqld restarted
I have tried the copy many times over. Yes I shut the database down
before the copy. I have tried using cp, and pax to do the copies. I
have run an md5sum agains't some of the innodb files comparing source
and destination after copy
Richard,
- Original Message -
From: Richard F. Rebel [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 12, 2005 8:07 PM
Subject: InnoDB files corrupt after copy to another disk???
--=-55yKssoEPEmA1J8GXefY
Content-Type: text/plain
Content-Transfer-Encoding
Hello,
I have had problems with some of our equipment and copying the files
around if they are greater than 2gb (one of our nfs file servers is not
large file safe). Because on occasion I have had to copy InnoDB files
around and hit this problem we have been using 2gb InnoDB files.
Does using
As the person who's asking a question and just had it rejected twice,
here it is again ... sql, query, blah, blah.
I have three InnoDB data files that I've created as time has gone on;
100M, 250M and 1G (autoextend). I would like to create a new data file
on a new raid partition and make it
, January 23, 2003 12:18 PM
To: '[EMAIL PROTECTED]'
Subject: Changing InnoDB files
As the person who's asking a question and just had it rejected twice,
here it is again ... sql, query, blah, blah.
I have three InnoDB data files that I've created as time has gone on;
100M, 250M and 1G (autoextend
On Tue, Jan 14, 2003 at 01:22:32PM +0100, harm wrote:
Hello,
Because I switched some large tables back to myisam from innodb (sorry
Heikki) my innodb datafile has a few gig 'empty'. I would like to reclaim
that space.
Can I expect a problem if I:
- make _all_ innodb tables myisam (And
Hello,
Because I switched some large tables back to myisam from innodb (sorry
Heikki) my innodb datafile has a few gig 'empty'. I would like to reclaim
that space.
Can I expect a problem if I:
- make _all_ innodb tables myisam (And be very sure I changed them all),
- shutdown the dbase,
-
36 matches
Mail list logo
