100GB -- hours.
Yes, with the right parameters on mysqldump, there is no problem of a delay between finishing the dump and building the slave. The critical info is the position in the binlog which corresponds to the point-in-time when the mysqldump was taken. Replication will (eventually) catchup.
If there are dependencies between table, you really ought to dump all the tables, not just the one in question. The need for the binlog position (above) may also necessitate dumping everything (or stopping _all_ writes).
An alternative to hours of downtime is if you already have an LVM (Logical Volume) set up for taking a "snapshot" for backing up the entire filesystem. A snapshot of the filesystem -- taken when mysql is stopped! -- can be loaded on the slave. A small number of tweaks are needed (esp, server_id, CHANGE MASTER).
The discussion of ALTER TABLE could be adapted for copying the table:
http://forums.mysql.com/read.php?22,427374,427627#msg-427627
Edited 1 time(s). Last edit at 07/20/2011 09:52AM by Rick James.