It should not happen. Metalink is supposed to use methods to avoid download errors. So they say, at least. I very much doubt I'll ever use it again nor recomend it.
Correct me if I'm wrong, but I don't think http provides for the possibility of checksuming individual chunks of a file. Which would explain the unusually high incidence of corrupt downloads I'm seeing among people using metalink enabled clients to download 10.2. If you download chunks from 50 different mirrors and just one of the mirrors has a corrupted copy, then your entire download will be corrupt, downloading from lots of mirrors greatly increases the chance of a corrupt download. So downloading 4gb isos using a metalink enabled client using lots of mirrors does not seem like a good idea, especially as any single mirror will likely max out whatever consumer bandwidth you have. Bittorrent enables downloads from many sources, but with bittorrent each chunk is checked, so you only have a small amount to re-download on corruption. _ Benjamin Weber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org