On Mon, Aug 2, 2010 at 8:35 PM, Johnny Withers wrote:
>
> Now when i run the same show table status command, the comment field says:
> InnoDB free: 6144 kB
>
> Is that telling me that I only have 6MB of storage left even though I
> increased the table space by 8GB?
>
I seem to recall - but am o
Hi Johnny,
Sorry about that - i just overlooked and the simple way to calculate the
sizes is to query the information_schema table called "tables" for data and
index sizes.
On Tue, Aug 3, 2010 at 8:55 PM, Johnny Withers wrote:
> About the above - it is saying 6144 KB so it is 6.1 GB.
>
> Ar
About the above - it is saying 6144 KB so it is 6.1 GB.
Are you sure? I would think 6144KB = 6.144 MB, or 6144 * 1000 = 6,144,000
bytes.
I think since InnoDB, by default, extends the table space by 8MB increments,
this is reporting the free space in this increment. How can I tell total
remain
Hey john,
Yes you can add it but safe to keep auto-extend at the end and monitor the
disk space as well.
"Now when i run the same show table status command, the comment field says:
InnoDB free: 6144 kB
Is that telling me that I only have 6MB of storage left even though I
increased the table spac
I recently ran out of table space on a production server that had the
following configuration line:
innodb_data_file_path=ibdata1:1G;ibdata2:1G;ibdata3:1G;ibdata4:1G;ibdata5:1G;ibdata6:2G:autoextend:max:8G
Before I changed this line and restarted the server, I ran SHOW TABLE STATUS
LIKE 'table' o
or you may have copied the InnoDB
> tablespace but not the InnoDB log files. "
>
> GOAL: Trying to restore mysql backup on different host
> using InnoDB backup that copes the backed up files to a files sever where I
> pulle them down to the new host
> I place all the MySQL dat
WHY do I see this error when restoring my backup db :
" InnoDB: Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. "
GOAL: Trying to restore mysql backup on different host
using InnoDB backup that copes the backed up files to a f
In the last episode (Jun 15), Ben Clewett said:
> > Are there any reasons why one would NOT use separate ibd files for
> > each table
>
> Fragmentation for one.
>
> A single file can re-use empty space from deleted rows for any added
> rows. A single file can only re-use space from that one
Olaf Stein wrote:
Hi all,
Are there any reasons why one would NOT use separate ibd files for each
table (--innodb_file_per_table). It seems logical to me to separate what
does not belong together logically (different databases), but I as the
shared tablespace is the default I wonder if it has na
> Hi all,
>
> Are there any reasons why one would NOT use separate ibd files for each
> table
Fragmentation for one.
A single file can re-use empty space from deleted rows for any added
rows. A single file can only re-use space from that one file.
Therefore the sum table size will be larger
Hi All,
If you specify one file per table, these files would be created under the
database directory of that particular database . So, the benifit with
respect to IO is negative. To have these files placed in different file
system to get IO benifit, you need to use symbolic links.
Please correct
Hi all,
Are there any reasons why one would NOT use separate ibd files for each
table (--innodb_file_per_table). It seems logical to me to separate what
does not belong together logically (different databases), but I as the
shared tablespace is the default I wonder if it has nay advantages I am no
""Gary Richardson"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Can I pre-create innodb tablespace using something like dd (or any other
> better tool)?
I'm afraid it can't be done that way, because fresh datafile is not simply
an e
Hi,
Can I pre-create innodb tablespace using something like dd (or any other
better tool)?
I have a server that is getting low on innodb table space and I want to add
15GB or so, but I want to minimize downtime. The server is a bit slow and I
estimate it will take around 10-20 minutes or so. I
Hi
I'm running MySQL 4.0.25 on a Linux machine dual xeon 3.0GB Ghz(32 bit)
with 6 GB RAM
the data is connected to a SAN storage
I wander what is the best tablespace configuration (except RAW) of
configuraing?
my configuration is as follows:
innodb_data_file_path=ibdata1:10G;ibdata2:10G;ibdata3
Using SQL : SHOW TABLE STATUS, we could see Innodb free size from inno
db table's comment.
Is there any SQL to know total tablespace size allocated?
--
Regards,
Ady Wicaksono
HP: +628562208680
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http
From: "Andreas Schildbach"
> Is it possible to configure MySQL so that it uses one InnoDB tablespace
> file per database schema, instead of mixing all data into the shared
> tablespace?
No, but you can use a file per table:
http://dev.mysql.com/doc/mysql/en/multiple-tablesp
Hello everyone,
Is it possible to configure MySQL so that it uses one InnoDB tablespace
file per database schema, instead of mixing all data into the shared
tablespace?
I'd like to keep my applications data seperate, and having one file per
application (schema) should make data migrations e
[snip]
I assume that the space of "InnoDB free: 201787392 kB" was resulted from the
dropping of DB_B. Will this chunk be re-used when new data is inserted?
[/snip]
InnoDB tablespace will not shrink when data is removed. The space the you
have from the dropped database will be reused.
Hi, everyone,
I created two databases DB_A and DB_B whose tables were all in
InnoDB. DB_A has data of approximately 500 G, DB_B has data of about
200G. Later I dropped the entire DB_B because it served only purpose of
testing. I noticed that the size of the table files ibdata1 and ibdata2
di
IGN KEY (`proteinOid`) REFERENCES
> `Protein` (`oi
> d`) ON UPDATE CASCADE,
> CONSTRAINT `Alias_ibfk_2` FOREIGN KEY (`aliasGroupOid`) REFERENCES
> `AliasGroup
> ` (`oid`) ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
>
> --
> -Message d'origine-
> De : Jeff Mat
RENCES `AliasGroup
` (`oid`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-Message d'origine-
De : Jeff Mathis [mailto:[EMAIL PROTECTED]
Envoyé : 14 janvier 2005 16:15
À : Duhaime Johanne
Cc : mysql@lists.mysql.com
Objet : Re: actual size of a innodb tablespace
if y
if you issue a "show table status" command from the mysql prompt, you'll
get an estimate of how much free space exists in the files.
Duhaime Johanne wrote:
Hello
Context: innodb per table.
Is it possible to know the actual size of my innodb file? What part of
the initial size (10M: autoexten
Hello
Context: innodb per table.
Is it possible to know the actual size of my innodb file? What part of
the initial size (10M: autoextend) is actually used? I would like to
have an idea of the data space progression? Per database (I have 3).
Thank you in advance
Johanne Duhaime
IRCM
courr
different spindle or set of spindles as your
data file.
-Original Message-
From: Dave Juntgen [mailto:[EMAIL PROTECTED]
Sent: Monday, December 06, 2004 6:30 AM
To: [EMAIL PROTECTED]
Subject: InnoDB tablespace Question.
Hello!
I have what seems to be a trivial question, but have not
Hello!
I have what seems to be a trivial question, but have not been able to
find a definite answer and your help would be greatly appreciated.
Question:
When creating InnoDB table spaces, are there any advantages to using
multi table spaces for each table or is it better to create a few larg
Heiki
Thx... it's work :D
Sorry, one liner
Heikki Tuuri <[EMAIL PROTECTED]> wrote:
Ady,
- Alkuperäinen viesti -
Lähettäjä: "Ady Wicaksono"
Vastaanottaja: "Ady Wicaksono" ; "Heikki Tuuri"
Kopio:
Lähetetty: Friday, September 03,
Ady,
- Alkuperäinen viesti -
Lähettäjä: "Ady Wicaksono" <[EMAIL PROTECTED]>
Vastaanottaja: "Ady Wicaksono" <[EMAIL PROTECTED]>; "Heikki Tuuri"
<[EMAIL PROTECTED]>
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Friday, September 03, 2004 10:41
I try to detect using MC (Midnight Commander) and found that after
;/data4/ibdata25:1802M
it won't write anymore...
I remove these data file and add /ibdata1/ibdata10:1500M and /data1/ibdata11:1500M
I believe, All data below is empty but corrupt :(
data file defintion --
#/data4/ibd
May i know, how could i know which of the data files that InnoDB MySQL engine is not
used ?
Did i i made a mistake when adding table space ?
Heikki Tuuri <[EMAIL PROTECTED]> wrote:
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files in the my.
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files in the my.cnf line :(.
Now you should figure out what are the data files that InnoDB is using, and
remove the end of the innodb_data_file_path line, as well as the unused
ibdata files. Remember t
I have MySQL for heavy duty job .
here is my InnoDB table space definition
innodb_data_file_path =
/data0/ibdata1:10M;/data0/ibdata2:10M;/data0/ibdata3:1082M;/data0/ibdata4:1500M;/data0/ibdata5:1500M;/
data0/ibdata6:1500M;/data0/ibdata7:1500M;/data1/ibdata8:1500M;/data1/ibdata9:1500M;/dat
David Griffiths writes:
>Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when data
>is deleted either.
Actually, Oracle has been able to resize data files since 7.2. It
is usually done with an 'alter tablespace ... coalesce' followed by an
'alter tablespace datafile ... resiz
In article <[EMAIL PROTECTED]>,
Jeff Mathis <[EMAIL PROTECTED]> writes:
> my understanding is that the datafiles are created when the server
> initializes, and this this is the designed and expected behavior. Most
> other database products use a similar model. Your scenario cannot
> happen. You sp
To: [EMAIL PROTECTED]
Subject: Re: InnoDB TableSpace Question
Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when data
is deleted either.
David
Marc Slemko wrote:
>On Tue, 3 Aug 2004 12:42:03 -0400 , David Seltzer <[EMAIL PROTECTED]>
wrote:
>
>
>>Thanks Marc,
Actually, Oracle can shrink or grow datafiles:
ALTER DATABASE DATAFILE '/usr01/oracle/sid/data001' resize 200M;
On Aug 3, 2004, at 15:59, David Griffiths wrote:
Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when
data is deleted either.
David
Marc Slemko wrote:
On Tue, 3 Aug 2004
Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when data
is deleted either.
David
Marc Slemko wrote:
On Tue, 3 Aug 2004 12:42:03 -0400 , David Seltzer <[EMAIL PROTECTED]> wrote:
Thanks Marc,
Is there really no way to reclaim unused space in an InnoDB table space? If
not, why is
On Tue, Aug 03, 2004 at 01:08:58PM -0400, [EMAIL PROTECTED] wrote:
>
> I agree with David. If there is no present way to recover unused
> InnoDB tablespace, then we (as a community) seriously need to create
> a tool to do just that. How have we gone so long without it?
Because it&
;
> jeff
> [EMAIL PROTECTED] wrote:
>> I agree with David. If there is no present way to recover unused
>> InnoDB tablespace, then we (as a community) seriously need to create
>> a tool to do just that. How have we gone so long without it? I always
>> assumed it wa
there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always assumed it was
possible (I guess I have been just lucky enough to not need to do it
yet)
What if, during the
:09 PM
To: David Seltzer
Cc: [EMAIL PROTECTED]
Subject: RE: InnoDB TableSpace Question
I agree with David. If there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always
I agree with David. If there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always assumed it was
possible (I guess I have been just lucky enough to not need to do it
yet
On Tue, 3 Aug 2004 12:42:03 -0400 , David Seltzer <[EMAIL PROTECTED]> wrote:
> Thanks Marc,
>
> Is there really no way to reclaim unused space in an InnoDB table space? If
> not, why is this not considered a tremendous limitation?
Some do consider it a tremendous limitation. It all depends on ho
: [EMAIL PROTECTED]
Subject: Re: InnoDB TableSpace Question
On Tue, 3 Aug 2004 10:07:25 -0400 , David Seltzer <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I've been searching the archives & mysql documentation for a while and I
> can't seem to find an answer to my questio
On Tue, 3 Aug 2004 10:07:25 -0400 , David Seltzer <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been searching the archives & mysql documentation for a while and I
> can't seem to find an answer to my question -
>
> Is there a way to force InnoDB to shrink its filesize? I just dropped a 7GB
> tab
Hi all,
I've been searching the archives & mysql documentation for a while and I
can't seem to find an answer to my question -
Is there a way to force InnoDB to shrink its filesize? I just dropped a 7GB
table, but it hasn't freed up the disk space and I need it back. From what
I've been reading,
Hi, ( hopefully a MySQL developer sees this at some point! )
I am giving InnoDB a good workout before rolling it out onto
production systems, and found a bug in the way the tablespace gets fragmented
when doing basic add/drop of indexes. Below my sig is a series of SQL
commands I used to replicate
Hi,
I need to manage Innodb Tablespace very effectively from my application. To do that I
require clear picture of Innodb tablespace file and its organization. My application
needs to do the following
1. backup/restore of databases
While doing so should calculate the size of source
Hi MySQL ,
I have made a test database for performance testing
and my InnoDb tablespace grew from 1Gig to 8 Gig...
After I dropped that test database, the tablespace
stayed to the same size. How can I "resize" it to its
original size?
=
-
Benoit St-J
At 14:50 +0200 10/25/02, Natale Babbo wrote:
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
It stops getting bigger. :-)
What do you mean by "what happen"? That is, what are the conditions
Message-
From: Natale Babbo [mailto:natale_babbo75@;yahoo.it]
Sent: October 25, 2002 08:51
To: [EMAIL PROTECTED]
Subject: innodb tablespace size
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
Thanks in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 25 October 2002 14:50, Natale Babbo wrote:
> innodb_data_file_path=ibdata1:100M:autoextended:max:200M
>
> anyone knows what happen if the above innodb
> tablespace reach the limit of 200M?
I would assume you will get an e
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
Thanks in advance.
Natale Babbo
sql
__
Mio Yahoo!: personalizza Yahoo! come piace a te
It is very handy with BDB and MyISAM tables to be able to back them
up directly or move them across different machines. If I have
a large database server with gigs of InnoDB tablespace and we need
to move a single database or table to another server it would
require mysqldump and reloading the tables,
54 matches
Mail list logo
