Hi All,
My bacula database (with MyISAM tables) is currently 5.3 GB in size
after only 10 months of use.
Last weekend my File table filled up, which was easily fixed by doing
the following as recommended at
http://www.bacula.org/dev-manual/Catalog_Maintenance.html#SECTION00244
On Thu, 8 Nov 2007, Mike Seda wrote:
Hi All,
My bacula database (with MyISAM tables) is currently 5.3 GB in size
after only 10 months of use.
Last weekend my File table filled up, which was easily fixed by doing
the following as recommended at
On Fri, 17 Aug 2007, Alan Brown wrote:
innodb_data_file_path = ibdata1:26000M;ibdata2:2000M:autoextend
(As I understand it, this should grow the tablespace as needed)
Doh!
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/VolGroupMSSLAY01-LogVolSQL
On Thu, 16 Aug 2007, Drew Bentley wrote:
You'll either need to add more InnoDB by adding more to your
/etc/my.cnf file or convert the tables to use MyISAM. Usually depends
on what MySQL will use as default or if someone else created the
InnoDB space but you can easily add more by editing the
On 8/17/07, Alan Brown [EMAIL PROTECTED] wrote:
On Fri, 17 Aug 2007, Alan Brown wrote:
innodb_data_file_path = ibdata1:26000M;ibdata2:2000M:autoextend
(As I understand it, this should grow the tablespace as needed)
Doh!
FilesystemSize Used Avail Use% Mounted on
On Fri, 17 Aug 2007, Drew Bentley wrote:
Yeah, autoextend for InnoDB seems to have bitten you. I usually never
do this and have monitors to tell me if it's reaching a certain
threshold, as you're probably not even using all of the InnoDB space
allocated, as it's not particularly nice in
On 8/17/07, Alan Brown [EMAIL PROTECTED] wrote:
On Fri, 17 Aug 2007, Drew Bentley wrote:
Yeah, autoextend for InnoDB seems to have bitten you. I usually never
do this and have monitors to tell me if it's reaching a certain
threshold, as you're probably not even using all of the InnoDB
(Have been running mysql and dbchecks last couple of days...)
On Tue, 14 Aug 2007, Drew Bentley wrote:
I've just encountered this message on my system.
I can understand it on MyISAM, but I thought InnoDB had no upper limits.
Does anyone have experience and recovery pointers?
Perhaps
On 8/16/07, Alan Brown [EMAIL PROTECTED] wrote:
(Have been running mysql and dbchecks last couple of days...)
On Tue, 14 Aug 2007, Drew Bentley wrote:
I've just encountered this message on my system.
I can understand it on MyISAM, but I thought InnoDB had no upper limits.
Does anyone
I've just encountered this message on my system.
I can understand it on MyISAM, but I thought InnoDB had no upper limits.
Does anyone have experience and recovery pointers?
-
This SF.net email is sponsored by: Splunk
10 matches
Mail list logo
