Hi, i have a doubt.
I have an Microsoft Hyper-V Server 2016. On this server its running an Oracle Linux VM with a Oracle Database on top. The Oracle Database its configured to use ASM storage (standalone with local disks, not a RAC Cluster).
Actualy the server phisical disks are old 512 bytes SAS disk (here its Brazil Guys, i bougth a new Dell Poweredge 630 server and Dell send me these old technology disks), not the new 4K disks.
We all know that for database servers, larger blocks/stripe sizes are better for performance, but now im limited by the phisical hardware.
I want to know if i move the already in use VHDXs to a new storage (new local 4k disks or even a better iscsi storage) the linux will automaticly be beneficied by the changes or if i will have to use new VHDXs (or format the old ones) to use the updated phisical disks enhancements?
To exemplify my problems here are some the disks configurations on Hyper-V Server and on the Linux VM
PS C:\Users\administrador.CN> Get-PhysicalDisk | sort-object SlotNumber | select SlotNumber, FriendlyName, Manufacturer,
Model, PhysicalSectorSize, LogicalSectorSize | ft -autosize
SlotNumber FriendlyName Manufacturer Model PhysicalSectorSize LogicalSectorSize
---------- ------------ ------------ ----- ------------------ -----------------
FreeNAS iSCSI Disk FreeNAS iSCSI Disk 131072 512
FreeNAS iSCSI Disk FreeNAS iSCSI Disk 131072 512
DELL PERC H730P Mini DELL PERC H730P Mini 512 512
DELL IDSDM DELL IDSDM 512 512
WD My Passport 0741 WD My Passport 0741 4096 512
PS C:\Users\administrador.CN> exit
C:\Users\administrador.CN>wmic partition get BlockSize, StartingOffset, Name, Index
BlockSize Index Name StartingOffset
512 0 Disco #4, Partição #0 135266304
512 0 Disco #3, Partição #0 33685504
512 1 Disco #3, Partição #1 17408
512 0 Disco #0, Partição #0 1048576
512 1 Disco #0, Partição #1 315621376
512 2 Disco #0, Partição #2 554696704
512 3 Disco #0, Partição #3 85900394496
512 0 Disco #2, Partição #0 135266304
512 1 Disco #2, Partição #1 17408
512 0 Disco #1, Partição #0 4194304Physical Disks on Hyper-V Server
PS C:\Users\administrador.CN> Get-VHD -Path "g:\vhds\*" | FT Path, LogicalSectorSize, PhysicalSectorSize -Autosize Path LogicalSectorSize PhysicalSectorSize ---- ----------------- ------------------ g:\vhds\nostromo-oracle-bin.vhdx 512 4096 g:\vhds\nostromo-oradata01.vhdx 512 4096 g:\vhds\nostromo-oradata02.vhdx 512 4096 g:\vhds\nostromo-oradata03.vhdx 512 4096 g:\vhds\nostromo-oradata04.vhdx 512 4096 g:\vhds\nostromo-redo-ctlvhdx.vhdx 512 4096 g:\vhds\nostromo-root.vhdx 512 4096 g:\vhds\nostromo-swap.vhdx 512 4096
Virtual Disks on the server
[root@nostromo ~]# cat /sys/block/sdh/queue/optimal_io_size 0 [root@nostromo ~]# cat /sys/block/sdh/queue/minimum_io_size 4096 [root@nostromo ~]# cat /sys/block/sdh/queue/physical_block_size 4096 [root@nostromo ~]# cat /sys/block/sdh/queue/max_sectors_kb 512 [root@nostromo ~]# cat /sys/block/sdh/queue/max_hw_sectors_kb 512 [root@nostromo ~]# cat /sys/block/sdh/queue/hw_sector_size 512 [root@nostromo ~]# fdisk -l /dev/sdh | grep "Sector size" WARNING: GPT (GUID Partition Table) detected on '/dev/sdh'! The util fdisk doesn't support GPT. Use GNU Parted. Sector size (logical/physical): 512 bytes / 4096 bytes [root@nostromo ~]# parted -l Model: Msft Virtual Disk (scsi) Disk /dev/sda: 85,9GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 1049kB 2098MB 2097MB fat32 boot 2 2098MB 4195MB 2097MB ext4 3 4195MB 85,9GB 81,7GB ext4 Model: Msft Virtual Disk (scsi) Disk /dev/sdb: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdc: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdd: 215GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 215GB 215GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sde: 215GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 215GB 215GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdf: 34,4GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 1049kB 34,4GB 34,4GB linux-swap(v1) SWAP Model: Msft Virtual Disk (scsi) Disk /dev/sdg: 107GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 1049kB 107GB 107GB ext4 Model: Msft Virtual Disk (scsi) Disk /dev/sdh: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdi: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdj: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary Model: Msft Virtual Disk (scsi) Disk /dev/sdk: 53,7GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start End Size File system Name Sinalizador 1 2097kB 53,7GB 53,7GB primary
Partitions inside Linux VM
Ps.: Sorry about my bad english.