>>> 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, write-to-disk and perations of the > daemon atomic Creating a ZFS snapshot implicitly writes all pending file data to disk. When the MySQL server was not running, creating a ZFS snapshot should have created a completely perfect copy of all MySQL files. I am going to try this again tomorrow: shutting down MySQL completely, creating a ZFS snapshot, and rsync'ing the snapshot over to the slave server. I did this once before unsuccessfully, but I'll do it one more time just to be sure. -- Tim Gustafson t...@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
