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

[Xen-users] Error: Error creating domain: vbd: Segment phy:/dev/mapper/.. is in writable use


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Erik de Bruijn - BudgetDedicated.com" <Erik@xxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 9 Aug 2005 13:58:35 +0200 (CEST)
  • Delivery-date: Tue, 09 Aug 2005 19:10:38 +0000
  • Importance: Normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Dear all,

Host kernel:
I use LVM to map logical volumes to xen block devices, however with the
snapshot of the August 1st build of 3.0-beta I'm getting the error:

# xm create -c
Using config file "xmdefconfig".
Error: Error creating domain: vbd: Segment
phy:/dev/mapper/88GbIDE-web1_system is in writable use

I don't have the volume mounted in dom0 or other domUs, however it has
been used by the web1 xenU as block device, after which I've destroyed it
and restarted. I've destroyed it since it hung, I could open the console
and saw a getty prompt, but it was irresponsive.

# lvdisplay 88GbIDE/web1_system -v -d
    Using logical volume(s) on command line
  --- Logical volume ---
  LV Name                /dev/88GbIDE/web1_system
  VG Name                88GbIDE
  LV UUID                0RE3XF-0S7p-aFIO-YJ6B-sF4r-siYR-FlWnPy
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                4.77 GB
  Current LE             1221
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0

If I do mount it, it shows   # open = 2, and after unmounting it doesn't
refresh to zero. lvchange --refresh doesn't help either. Nor does making
it readonly for a while help. Renaming them makes them available again,
but this increases "# open 1" to "# open 2" in lvdisplay, while xend
doesn't complain now.

Does the xend block device driver internally use loopback devices or
something? I have this list, and the host doesn't use any loopback
_mountpoints_ nor have I manually issued losetup /dev/loopXX /dev/hdxx.

# looplist # this does something like: losetup /dev/loop{0,end}
/dev/loop0: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop1: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop2: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop3: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop4: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop5: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop6: [c300]:0 (E) offset 1075102556, undefined encryption
/dev/loop7: [c300]:0 (E) offset 1075102556, undefined encryption

A similar host has these loopbacks set:
# looplist
/dev/loop0: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop1: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop2: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop3: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop4: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop5: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop6: [aaabf9b8]:0 () offset 0, none encryption
/dev/loop7: [aaabf9b8]:0 () offset 0, none encryption

-- 
Kind regards,

Erik de Bruijn
BudgetDedicated

www.BudgetDedicated.com | Tel. +31 13 4690625 | Fax. +31 84 2248796 | Mob.
+31 6 21856715 | Adres: Adelaarshorst 9 | Zipcode NL-5042 XE Tilburg



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


 


Rackspace

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