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

Re: [Xen-users] iscsi initiator on PV DomU problem


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • From: Christopher Chen <muffaleta@xxxxxxxxx>
  • Date: Mon, 9 Mar 2009 07:39:54 -0700
  • Cc: Xen mailinglist <xen-users@xxxxxxxxxxxxxxxxxxx>, Longina Przybyszewska <longina@xxxxxxxxxxxx>
  • Delivery-date: Mon, 09 Mar 2009 07:40:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=P8tk85eG1G76LH1yY9C8cP9/Ty0Ypo/EGq1SzqkkEBKsz6e1WoXdRVjFhykFl2GZ1v oYWdiUiyWJ3c61bKLS8MDYuFKfgxgoQdbPDH1sMbbB3SPav9Xdir86rpEH/tGIFoxcwq txSyDjBg93uNhT3NWhtnkNcaUvAm/k/Xi5BSM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Mar 9, 2009, at 6:30, "Fajar A. Nugraha" <fajar@xxxxxxxxx> wrote:

On Mon, Mar 9, 2009 at 7:56 PM, Longina Przybyszewska
<longina@xxxxxxxxxxxx> wrote:
I have got 300gb iscsi target ( residence on SAN ) which should be directly
bound to domU.
(DomU: PV Ubuntu Hardy Linux 2.6.24-19-xen, Dom0: UbuntuHardy Linux
2.6-24-22-xen).

First of all, I believe you'd get better performance if the initiator
is on dom0 instead of domU.


It comes up as 500gb block device!

========
attempt to access beyond end of device
sda: rw=0, want=976639545, limit=629147647
========

It means domU correctly recognize the block device as 629147647
sectors of 512-bytes long (300GB), but it was asked to get sector
number 976639545.


cfdisk /dev/sda : "Fatal Error: Bad primary partition 0: Partition ends
after end-of-disk"

cfdisk /dev/sda1 : "Disk Driver /dev/sda1, size 500,0 Gb free space"
Then I kan make primary paritions assigned name /dev/sda1p1, /dev/ sda1p2.


Probably because there's already a partition table on that block
device, and it's messed up (maybe because the block the device was
used previously, and then shrinked).

What does "cat /proc/partitions" and "fdisk -l /dev/sda" shows?

If it is indeed messed up partition table, you can use fdisk's extra
functionality to change the number of heads, sectors/tracks, or
cylinders.

If it's a blank target with MBR partition, zeroing the first 512-byte
of the disk (with dd or whatever) should erase existing partition
table and let fdisk work out reasonable parameters. If it's GPT
parition though things can get a little more complicated :)

I've had success with parted, using it to write a msdos label, then zeroing it out. It appears to be smart enough to seek out and destroy rogue gpt superblocks.



Regards,

Fajar

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

_______________________________________________
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®.