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

[Xen-API] how to create SR on the FC/GPT/LVM


  • To: xen-api@xxxxxxxxxxxxx
  • From: Alexander Voropay <alexander.voropay@xxxxxxxxx>
  • Date: Mon, 21 May 2012 20:29:31 +0400
  • Delivery-date: Mon, 21 May 2012 16:29:42 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

Hi!

How to create a new StorageRepository on the FibreChannel device
formatted with GPT partitions and with LVM ?

There is no FC fabric, nor SAN, just a direct PC<-->Storage link
so no "multipath" and other FC magic.

There is a option to create a SR on the HBA via 'xsconsole'.
 Disks and Storage Repositories -->
 Create New Storage Repository -->
 Hardware HBA

Unfortunately, it uses a WHOLE LUN to create single huge SR.

The default "Local storage" on the internal drive is created just as required.
Is it possible to make the same on the external FC drive ?


# xe sr-list
...
uuid ( RO)                : 5940ed5a-dc12-78dd-6b65-912d5f7d189d
          name-label ( RW): Local storage
    name-description ( RW):
                host ( RO): xenserver
                type ( RO): ext
        content-type ( RO): user
...

# xe sr-param-list uuid=5940ed5a-dc12-78dd-6b65-912d5f7d189d
uuid ( RO)                    : 5940ed5a-dc12-78dd-6b65-912d5f7d189d
              name-label ( RW): Local storage
        name-description ( RW):
                    host ( RO): xenserver
      allowed-operations (SRO): forget; VDI.create; VDI.snapshot;
plug; update; destroy; VDI.destroy; scan; VDI.clone; VDI.resize;
unplug
      current-operations (SRO):
                    VDIs (SRO): 7bbaae3a-6524-4413-b58c-0896dc32dc6d;
2d755a28-daf6-4d74-8923-391a5575316a
                    PBDs (SRO): 29ab9a85-6d1c-04a3-1401-d196651bffd9
      virtual-allocation ( RO): 53687091200
    physical-utilisation ( RO): 3093147648
           physical-size ( RO): 580146855936
                    type ( RO): ext
            content-type ( RO): user
                  shared ( RW): false
           introduced-by ( RO): <not in database>
            other-config (MRW): i18n-original-value-name_label: Local
storage; i18n-key: local-storage
               sm-config (MRO): devserial:
scsi-3600605b0040ad5d017221ae3b5903a92
                   blobs ( RO):
     local-cache-enabled ( RO): true
                    tags (SRW):


#  ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root  9 May 21 14:54
scsi-3600144f094cdf1c200004fb6438b0001 -> ../../sdb
lrwxrwxrwx 1 root root 10 May 21 14:54
scsi-3600144f094cdf1c200004fb6438b0001-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Apr 19 18:13
scsi-3600605b0040ad5d017221ae3b5903a92 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr 19 18:13
scsi-3600605b0040ad5d017221ae3b5903a92-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 19 18:13
scsi-3600605b0040ad5d017221ae3b5903a92-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 19 18:13
scsi-3600605b0040ad5d017221ae3b5903a92-part3 -> ../../sda3


The /dev/sda (see 'devserail') is a GPT-labeled drive with LVM on the
/dev/sda3 partition,
not a 'raw' SCSI partition.

# pvs
  PV         VG                                              Fmt  Attr
PSize   PFree
  /dev/sda3  XSLocalEXT-5940ed5a-dc12-78dd-6b65-912d5f7d189d lvm2 a-
548.92G    0
  /dev/sdb1  XSLocalEXT-b8e5421b-0ada-4ee5-a5b5-0fc3d112ccc7 lvm2 a-
  6.00T    0

# lvs
  LV                                   VG
                Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  5940ed5a-dc12-78dd-6b65-912d5f7d189d
XSLocalEXT-5940ed5a-dc12-78dd-6b65-912d5f7d189d -wi-ao 548.92G
  b8e5421b-0ada-4ee5-a5b5-0fc3d112ccc7
XSLocalEXT-b8e5421b-0ada-4ee5-a5b5-0fc3d112ccc7 -wi-a-   6.00T


I can not understand, how SR "Local storage" is binded to the
LogicalVolume "...189d" (not SCSI id).

How to add my new fresh-created LogicalVolume "...ccc7" as a new SR ?



--
-=AV=-

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


 


Rackspace

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