Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB
Hi, i extended 16 virtual image disks today by 1000GiB through the GUI and now we have a problem with some of them... 9 of them are shown if "edited" that they have a size of 0GiB and not 16360GiB as expected? 5 of them are not able to be extended either within the VM. we tried to power it off and then on again (not reboot, but actual power off / power on) any suggestions to get out of this weird mode? disks seems as if they have the "old" size within the VM but are shown in oVirt as if they are 0GiB.? They are relying on a posix compliant fs if that makes any difference, and they are thin-provisioned and discard-enabled. Thanks in advance.
title should have said "actual size is +10TB" not 1TB.
On Tue, May 23, 2023 at 2:27 PM <arc@b4restore.com> wrote:
title should have said "actual size is +10TB" not 1TB.
What kind of posix compliant fs? What are its capabilities and limits? Because for example max size of a single file is 16Tb on ext4... and after extension your VM disk file size would go near or after this limit https://access.redhat.com/solutions/1532 Just to be sure you are not hitting a side effect caused by fs instead... HIH, Gianluca
It's IBM Spectrum Scale formerly known as GPFS. the limit for files or filesystems are way beyond any limits within the linux vm so that is definatly not an issue from the GPFS filesystem. The disks are formatted as xfs within the VM so that limit should be 500TiB right? the funny thing is that we have 16 disks attached from the storage domain, some of them extended perfectly fine. others did not, or atleast they dont seem to show it, we got no errors other than the volumes was modified correctly and now some of them are shown with a size in ovirt of 0GiB but are ok within the VM, not extendable within the VM but the original size is still the same. if i click on the storage domain and go to Events i see alot of the below messages : May 23, 2023, 9:37:11 AM Size of the disk 'b4chl407_T1B2_SPS115' was successfully updated to 0 GB by SYSTEM. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:37:11 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:37:11 AM Size of the disk 'b4chl407_T1B2_SPS109' was successfully updated to 0 GB by SYSTEM. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:37:11 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS110' was successfully updated to 16360 GB by SYSTEM. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS113' was successfully updated to 16360 GB by SYSTEM. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS109' was successfully updated to 16360 GB by SYSTEM. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:36:34 AM Size of the disk 'b4chl407_T1B2_SPS115' was successfully updated to 16360 GB by SYSTEM. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:36:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:36:33 AM Size of the disk 'b4chl407_T1B2_SPS114' was successfully updated to 16360 GB by SYSTEM. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:36:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:36:18 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:35:48 AM Size of the disk 'b4chl407_T1B2_SPS106' was successfully updated to 16360 GB by SYSTEM. 3e051b49-b02b-43f3-909c-cebbcfbbaeaa oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:35:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:35:29 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 98f6e3a0-1f03-4aa5-b477-66defeaa5eb1 oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:35:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:34:59 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:34:30 AM Size of the disk 'b4chl407_T1B2_SPS116' was successfully updated to 0 GB by SYSTEM. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:34:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:34:29 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:34:01 AM Size of the disk 'b4chl407_T1B2_SPS112' was successfully updated to 0 GB by SYSTEM. 98f6e3a0-1f03-4aa5-b477-66defeaa5eb1 oVirt May 23, 2023, 9:34:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 98f6e3a0-1f03-4aa5-b477-66defeaa5eb1 oVirt May 23, 2023, 9:34:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:34:00 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:33:59 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:33:30 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:33:00 AM Size of the disk 'b4chl407_T1B2_SPS102' was successfully updated to 16360 GB by SYSTEM. fe3e15e1-0156-4677-aed1-13d00ee9a2d9 oVirt May 23, 2023, 9:32:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:32:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:32:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 651edad8-3876-4f4a-ac5f-f48b42986f31 oVirt May 23, 2023, 9:32:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:32:08 AM Size of the disk 'b4chl407_T1B2_SPS106' was successfully updated to 0 GB by SYSTEM. 3e051b49-b02b-43f3-909c-cebbcfbbaeaa oVirt May 23, 2023, 9:32:08 AM Size of the disk 'b4chl407_T1B2_SPS111' was successfully updated to 0 GB by SYSTEM. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:32:07 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3e051b49-b02b-43f3-909c-cebbcfbbaeaa oVirt May 23, 2023, 9:32:07 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:32:07 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:32:07 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:31:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 12650733-ae5d-4ea5-89aa-08e13a4c16e4 oVirt May 23, 2023, 9:31:37 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:31:08 AM Size of the disk 'b4chl407_T1B2_SPS104' was successfully updated to 16360 GB by SYSTEM. 662ff247-d99a-4864-822c-d8d39005c300 oVirt May 23, 2023, 9:31:08 AM Size of the disk 'b4chl407_T1B2_SPS110' was successfully updated to 0 GB by SYSTEM. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:31:08 AM Size of the disk 'b4chl407_T1B2_SPS114' was successfully updated to 0 GB by SYSTEM. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:31:08 AM Size of the disk 'b4chl407_T1B2_SPS107' was successfully updated to 0 GB by SYSTEM. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:31:07 AM Size of the disk 'b4chl407_T1B2_SPS109' was successfully updated to 0 GB by SYSTEM. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:31:07 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 98f6e3a0-1f03-4aa5-b477-66defeaa5eb1 oVirt May 23, 2023, 9:31:03 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. a88e2dfc-4fa8-47c4-871c-3c69b0c11b1c oVirt May 23, 2023, 9:31:03 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:31:03 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 9e53b06a-c606-4951-bf34-16c7538a297c oVirt May 23, 2023, 9:31:02 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. e027b37a-e59b-411c-8a8c-0b0c494d8eb9 oVirt May 23, 2023, 9:30:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3bf54430-a381-4941-bb6a-bd574d1d71b7 oVirt May 23, 2023, 9:30:33 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 1fb5d5bb-4484-4e09-8b5c-fc98580f6dee oVirt May 23, 2023, 9:30:32 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 6599b34a-2d47-40d8-9b13-32d3fa1b8c58 oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS101' was successfully updated to 16360 GB by SYSTEM. ccea4950-0605-4704-a715-9eb9f15c6295 oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS108' was successfully updated to 0 GB by SYSTEM. 12650733-ae5d-4ea5-89aa-08e13a4c16e4 oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS105' was successfully updated to 0 GB by SYSTEM. 651edad8-3876-4f4a-ac5f-f48b42986f31 oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS102' was successfully updated to 0 GB by SYSTEM. fe3e15e1-0156-4677-aed1-13d00ee9a2d9 oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS115' was successfully updated to 0 GB by SYSTEM. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS103' was successfully updated to 0 GB by SYSTEM. a88e2dfc-4fa8-47c4-871c-3c69b0c11b1c oVirt May 23, 2023, 9:30:03 AM Size of the disk 'b4chl407_T1B2_SPS113' was successfully updated to 0 GB by SYSTEM. bd645bed-60fc-402c-9745-f10aac6f283d oVirt May 23, 2023, 9:30:03 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 3e051b49-b02b-43f3-909c-cebbcfbbaeaa oVirt May 23, 2023, 9:29:32 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 042e4005-5ee9-4568-8097-cf7e91f746cf oVirt May 23, 2023, 9:29:21 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 12650733-ae5d-4ea5-89aa-08e13a4c16e4 oVirt May 23, 2023, 9:29:21 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 651edad8-3876-4f4a-ac5f-f48b42986f31 oVirt May 23, 2023, 9:29:21 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. fe3e15e1-0156-4677-aed1-13d00ee9a2d9 oVirt May 23, 2023, 9:29:21 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. 678b7d5e-10f1-4cf7-88c5-af8b0d074fcf oVirt May 23, 2023, 9:28:51 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. a88e2dfc-4fa8-47c4-871c-3c69b0c11b1c oVirt May 23, 2023, 9:28:51 AM Failed to update VM 'b4chl407' with the new volume size. VM restart is recommended. bd645bed-60fc-402c-9745-f10aac6f283d oVirt We have tried to power off / power on the vm and also just a regular shutdown -r now. nothing seems to update the size correctly.. Br
participants (2)
-
arc＠b4restore.com -
Gianluca Cecchi