OOoopppsss! I do mean for recovery/continual backup. I will do it
manually, but basically get all the data on a USB disk and be able to
recover/move it (the data) on another machine, the same machine etc..
I hope I did not just open up a can of worms. We just went live and
this post gave me a rude
Am 21.11.2013 13:51, schrieb Paul Halliday:
> Had a system crash this morning and I can't seem to get mysql back up
> and running. This is the error:
>
> InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
> 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
>
2013/11/21 Reindl Harald
>
> Am 21.11.2013 13:51, schrieb Paul Halliday:
> > Had a system crash this morning and I can't seem to get mysql back up
> > and running. This is the error:
> >
> > InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
> > 18 19 20 21 22 23 24 25 26 27 2
Hello Nick,
On 11/21/2013 10:32 AM, Nick Cameo wrote:
OOoopppsss! I do mean for recovery/continual backup. I will do it
manually, but basically get all the data on a USB disk and be able to
recover/move it (the data) on another machine, the same machine etc..
I hope I did not just open up a can
What is the best way to backup your database. Which are the files that
I need to store on a usb disk
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
It was indeed corruption :/ what a day. I was able to move everything
over to another partition and have managed to get mysql up and running
again. There was a single file I could not, an .idb (the ,.frm is
there). Is it possible to fix this from ibdata or the logs?
Thanks.
On Thu, Nov 21, 2013
Am 21.11.2013 18:59, schrieb Paul Halliday:
> It was indeed corruption :/ what a day. I was able to move everything
> over to another partition and have managed to get mysql up and running
> again. There was a single file I could not, an .idb (the ,.frm is
> there). Is it possible to fix this fr
Hi Joerg et all,
[snip]
> You said this is Solaris.
>
> AFAIK, Solaris uses the same disk area for "/tmp" and paging, so the
> available space for files in "/tmp" may vary even without files being
> manipulated.
>
> I propose you set TMPDIR to point to some other disk area.
We're on Solaris,
Hi Jörg,
On Thursday 29 September 2005 12:09, you wrote:
> Hi Martijn, all!
>
> Martijn van den Burg wrote (reordered)
>
> > On Wednesday 28 September 2005 20:10, Gleb Paharenko wrote:
> >>Martijn van den Burg wrote:
> >>>Hi list,
> >>>
> >>>After the most recent reboot (which we used to increase
Hi Martijn, all!
Martijn van den Burg wrote (reordered)
On Wednesday 28 September 2005 20:10, Gleb Paharenko wrote:
Martijn van den Burg wrote:
Hi list,
After the most recent reboot (which we used to increase the
ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log),
the follo
Hi,
Thanks for your reply.
TMPDIR is not set explicitly, and the first 'fallback' directory in that case
is '/tmp', which is accessible and has enough diskspace. At least, when I
checked this morning.
The error occurred in the night, maybe there were other processes that filled
the directory
Hello.
Maybe some directory doesn't exist in the path where MySQL stores
temporary files. See:
http://dev.mysql.com/doc/mysql/en/temporary-files.html
Martijn van den Burg wrote:
> Hi list,
>
> After the most recent reboot (which we used to increase the
> ulimit/open_files_limit
Reply by me.
How stupid i'm :(
I've finished this warning error problem by adding
4 files --> 3 file each 3 Gbyte and 1 file 500Mbyte
Thx mr. heiiki :D
Sorry
Ady Wicaksono wrote:
|Dear All,
As subject, Actually i've been ever meet this case
when i see :
InnoDB: Error: tablespace size
Ben,
- Original Message -
From: "Ben Kutsch" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, February 15, 2005 1:55 AM
Subject: innodb error 995
Hi I'm running version MySQL 4.0.20a-debug
windows server 2003
on a dedicated database server with an external SCSI RAID
On Thu, 6 Jan 2005 11:30:33 +0200
"Heikki Tuuri" <[EMAIL PROTECTED]> wrote:
> > innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend
>
> You have to add new data files to the end of the line, not to the
> start. Please follow the instructions at
> http://dev.mysql.com/doc/mysql/en/Adding_an
Ian,
- Original Message -
From: "Ian Grant" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 05, 2005 4:47 PM
Subject: Re: InnoDB: Error: tablespace size stored in header is 17024 pages,
Dear Heikki
Many thanks for your reply.
On Mon, 3 J
Dear Heikki
Many thanks for your reply.
On Mon, 3 Jan 2005 20:41:22 +0200
"Heikki Tuuri" <[EMAIL PROTECTED]> wrote:
> are you sure that you copied the complete ibdata1 file to the new
> place? It is strange how 7 MB can be missing from the file end.
I have just checked the tar file I used to do
Ian,
are you sure that you copied the complete ibdata1 file to the new place? It
is strange how 7 MB can be missing from the file end.
What does the old .err log contain? Any message about disk space running
out?
The error below probably has not corrupted your tablespace. Best to run
CHECK TAB
On Tue, 26 Aug 2003, Heikki Tuuri wrote:
> Asif,
>
> now take the old log files from the safe place and put them back! That will
> save your data.
>
> The instructions about changing the size of the log files are the following:
>
> http://www.innodb.com/ibman.html#Adding_and_removing
>
> "
> If yo
y, August 26, 2003 9:03 PM
Subject: Re: InnoDB Error ib_logfile0 of different size
> On Tue, 26 Aug 2003, Victoria Reznichenko wrote:
>
> > Asif Iqbal <[EMAIL PROTECTED]> wrote:
> > > I already have mysql 4.0.13 running with all InnoDB tables. I am
trying to use
> > >
On Tue, 26 Aug 2003, Victoria Reznichenko wrote:
> Asif Iqbal <[EMAIL PROTECTED]> wrote:
> > I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use
> > my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes
> >
> > In my MySQL data directory I have two ib_logfile fil
Asif Iqbal <[EMAIL PROTECTED]> wrote:
> I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use
> my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes
>
> In my MySQL data directory I have two ib_logfile files
>
> -rw-rw 1 mysqlmysql5242880 Aug 26 01:
John,
actually, you should first try
innodb_force_recovery=2
and run CHECK TABLEs.
Regards,
Heikki
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 19, 2003 1:25 AM
Subject: Re: Innodb error
> Jo
John,
what Linux kernel version you are running? Did the first crash occur because
of the same assertion failure?
The InnoDB tablespace is probably corrupt and it asserts in purge or insert
buffer merge.
You can try starting with
innodb_force_recovery=4
in the [mysqld] section of your my.cnf.
Shakeel,
- Original Message -
From: "Shakeel Sorathia" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, November 13, 2002 9:39 PM
Subject: InnoDB: Error: tablespace size stored in header
> Hi, we're using Innodb here and I just upped the number of datafiles
> that
Neil,
- Original Message -
From: ""Neil Malkani"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Saturday, September 07, 2002 7:46 PM
Subject: Innodb error on windows ME platform
> Hi,
>
> I have just installed and setup MySQL unfortunately I do not seem to be
able
> to re
ny people don't
actually know what a steaming pile of crap WinME is.
Matt
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 07, 2002 2:03 PM
Subject: Re: Innodb error on windows ME platform
>
Richard,
- Original Message -
From: ""Richard Harms"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, April 22, 2002 2:32 AM
Subject: InnoDB Error 150, MySQL 4.0.1 alpha & 3.23.49
> Hello,
>
> When attempting to create some tables using the MySQL 4.0.1 alpha and
> 3
28 matches
Mail list logo
