[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Block script unsafe when starting multiple devices in parallel


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Nathan March <nathan@xxxxxx>
  • Date: Tue, 30 Aug 2011 10:37:14 -0700
  • Delivery-date: Tue, 30 Aug 2011 10:37:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=message-id:date :from:mime-version:to:subject:content-type; q=dns; s=mail; b=YJV trYf13rokwMtBRf1P0qnvbXKy9z5Xzn0r4+4b2vn5vwfLh83x7XDRD2ZmGsXjYy0 HDIre9V4t//GL+60V1ScS0FLijF0YreOd1Ky71lXXJyXPkCSayOfCt1NzcjML+ED fyef31oC5a9b5q9qV9FWnM6538OKSHbcD7r+ueog=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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/swap

Sometime'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

Attachment: block.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.