Answer the question
In order to leave comments, you need to log in
Connect > 2TB drive to XenServer 7.0?
There was XenServer 6.5SP1 in which a 3TB disk lived perfectly, on which VDI was created for the entire available volume (~ 2.7 TB). I don't remember exactly how I did it, it was a long time ago. Most likely, it was done in the same way as, for example, it is written here: discussions.citrix.com/topic/262258-vdi-size-limit...
In preparation for the summer, the system disk was replaced in the server, and fresh XenServer was installed there to the heap 7.0. And then a fatal mistake was made: with one command xe sr-create instead of xe sr-introduce the contents of the disk were sent to a better world. Fortunately, nothing that would be a pity to lose.
But all my attempts to create such a disk anew lead to nothing. What I do:
0. In this version of XenServer, for some reason, the /etc/lvm/lvm.conf
parameterglobal / metadata_read_only
for some reason it is set to 1. In the previous version, it was 0. Accordingly, nothing can be done with LVM without setting it to 0. Perhaps they had some reasons for this, so before any operation on LVM, I set this to 0, and then return to 1.
1. Delete everything that exists on the disk. The PBD is detached and destroyed, the SR is destroyed and forgotten, after which the SR disappears from XenServer.
2. Create an empty GPT ( gdisk /dev/sdc
)
3. Find the disk id ( ll /dev/disk/by-id/ | grep sdc
) and create an SR (
xe sr-create content-type=user name-label="3TB Disk 1" shared=false type=lvm device-config:device=/dev/disk/by-id/...
). SR appears in XenCenter, size - 2.7 TB, occupied by 4 MB. # lvcreate -l 100%FREE -n "VHD-"$(uuidgen) VG_XenStorage-...
Logical volume "VHD-..." created.
# xe sr-scan uuid=...
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI ...],
4 MB used of 2794.5 GB total (0 B allocated)
1002 GB used of 2794.5 GB total (1000 GB allocated)
lvs
we find the desired volume, change its size:# lvextend -l +100%FREE VG_XenStorage.../VHD-...
Size of logical volume VG_XenStorage-.../VHD-... changed from 1001.96 GiB (256502 extents) to 2.73 TiB (715393 extents).
Logical volume VHD-... successfully resized.
lvs
we make sure that this is the case. We start xe sr-scan
, after which we return to XenCenter. There we see the following:2794.5 GB used of 2794.5 GB total (1000 GB allocated)
xe vdi-list params=all
says that:virtual-size ( RO): 1073741824000
physical-utilisation ( RO): 3000575721472
vdi-resize
:# xe vdi-resize uuid=... disk-size=3000575721472
Error code: SR_BACKEND_FAILURE_79
Error parameters: , VDI Invalid size [opterr=VDI size cannot exceed 2093051 MB],
Answer the question
In order to leave comments, you need to log in
Try this:
At this point, replace VHD
lvcreate -l 100%FREE -n "VHD-"$(uuidgen) VG_XenStorage-
with LV
lvcreate -l 100%FREE -n "LV-"$(uuidgen) VG_XenStorage-
with of. site
https://github.com/xapi-project/sm/blob/master/dri...
By the way, not directly on the topic, but nonetheless. When a volume is created and the repository is scanned, the disk appears in XenCenter without a name. If it is immediately created at 100% volume, it cannot be renamed. Therefore, it needs to be created in some volume, scanned, renamed, then expanded to 100% and scanned again. And there will be happiness
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question