>>> as far as i understodd the dameon was NOT down
I tried it both ways.
>> Then what about all the stuff cached in RAM waiting
>> and not yet written to disk?
> exactly this is the problem with making a fs-snapshot
> while mysqld is running - there is no 100% safe way to
> make the snpashot, wr
Am 17.10.2012 18:15, schrieb Rick James:
>
>> as far as i understodd the dameon was NOT down
>
> [Rick James] Then what about all the stuff cached in RAM waiting and not yet
> written to disk?
exactly this is the problem with making a fs-snapshot
while mysqld is running - there is no 100% saf
> as far as i understodd the dameon was NOT down
[Rick James] Then what about all the stuff cached in RAM waiting and not yet
written to disk?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
- Original Message -
> From: "Reindl Harald"
>
> as far as i understodd the dameon was NOT down
>
> a pretty sure indication was his log:
> 121016 10:40:20 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .
Am 17.10.2012 13:30, schrieb Johan De Meersman:
> I agree with the double rsync - I use the same technique - but again, if your
> daemon is down (thus, everything else being equal) a snapshot is just as
> consistent as an rsync, no?
as far as i understodd the dameon was NOT down
a pretty sure
> - Original Message -
> From: "Reindl Harald"
>
> Am 17.10.2012 12:26, schrieb Johan De Meersman:
> >
> > - Original Message -
> >> From: "Reindl Harald"
> >>
> >> i do not trust any FS snapshot in this context
>
> > Why? I am completely unaware of any functional difference
Am 17.10.2012 12:26, schrieb Johan De Meersman:
>
> - Original Message -
>> From: "Reindl Harald"
>>
>> i do not trust any FS snapshot in this context
>
> Why? I am completely unaware of any functional difference between an rsync
> and a snapshot, everything else being equal.
because
- Original Message -
> From: "Reindl Harald"
>
> i do not trust any FS snapshot in this context
Why? I am completely unaware of any functional difference between an rsync and
a snapshot, everything else being equal.
--
Linux Bier Wanderung 2012, now also available in Belgium!
August
On 10/16/2012 4:02 PM, spameden wrote:
2012/10/16 Tim Gustafson
Thanks for all the responses; I'll respond to each of them in turn below:
you can not simply copy a single database in this state
innodb is much more complex like myisam
I know; that's why I rsync'd the entire /var/db/mysql fo
Am 16.10.2012 21:55, schrieb Michael Dykman:
> I'm confused: in the first sentence, you say snapshots are bad (which
> directly contradicts the official MySQL documentation), and in the
> second sentence you say rsync is good. Why would an rsync of a file
> system snapshot not be good enough? B
Also, forgot to say you need to shutdown completely MySQL before rsync'ing
it's data, otherwise your snapshot might be inconsistent thus InnoDB fail.
Also make sure database shutdown was correct in the log.
2012/10/16 Tim Gustafson
> > load data from master never worked for innodb.
>
> And the
2012/10/16 Tim Gustafson
> Thanks for all the responses; I'll respond to each of them in turn below:
>
> > you can not simply copy a single database in this state
> > innodb is much more complex like myisam
>
> I know; that's why I rsync'd the entire /var/db/mysql folder (which
> includes the ib_
> load data from master never worked for innodb.
And the suggested mysqldump command does not work for MyISAM.
Either way, the suggestion is a non-starter. I could "flush tables
with read lock" and then do a mysqldump but again that would take
hours and all the databases would be read-only durin
load data from master never worked for innodb.
On 2012-10-16 3:52 PM, "Tim Gustafson" wrote:
Thanks for all the responses; I'll respond to each of them in turn below:
> you can not simply copy a single database in this state
> innodb is much more complex like myisam...
I know; that's why I rsy
Thanks for all the responses; I'll respond to each of them in turn below:
> you can not simply copy a single database in this state
> innodb is much more complex like myisam
I know; that's why I rsync'd the entire /var/db/mysql folder (which
includes the ib_logfile and ibdata files, as well as al
I have to agree with Harald on this: filesystem snapshots are not an
effective way to clone innodb databases. The rsync-based method
described has worked for me in large scale data situations very
reliably.
- michael dykman
On Tue, Oct 16, 2012 at 3:20 PM, Reindl Harald wrote:
>
>
> Am 16.10.2
Am 16.10.2012 20:18, schrieb Tim Gustafson:
> InnoDB: The log sequence number in ibdata files does not match
> InnoDB: the log sequence number in the ib_logfiles!
> 121016 10:40:20 InnoDB: Database was not shut down normally!
> So, I went back to the master server, backed up the "foo" database
17 matches
Mail list logo
