Hi Guys,Ran into an issue where losetup was failing, added some logging to it's executions to see (first #'s are parent pid / pid):
32435 / 32438 - losetup -f 32436 / 32439 - losetup -f 32435 / 32438 - Exit code: 0 32435 / 32438 - Output: /dev/loop/10 32436 / 32439 - Exit code: 0 32436 / 32439 - Output: /dev/loop/10 32128 / 32451 - losetup /dev/loop/10 /mnt/xenDisks2/nathanxen2/backup_tmp 31934 / 32452 - losetup /dev/loop/10 /mnt/xenDisks1/nathanxen2/swapSometime's losetup seems to be stuck waiting on something else and since multiple block devices are brought up in parallel, the block script tries to use the same name for multiple loopback devices.
Fix for this is pretty straightforward - should just be letting losetup figure out the device names itself, patch is attached.
- Nathan -- Nathan March<nathan@xxxxxx> Gossamer Threads Inc. http://www.gossamer-threads.com/ Tel: (604) 687-5804 Fax: (604) 687-5806
Description: Text document
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel