I'm working on reinstalling a homebrew Linux Hardened Repository with Veeam Infrastructure appliance repo.
During installation it terminates with error:
"Found devices with difference in logical sector size"
- sda - 4096
- sdb - 512
Given that modern large HDD (and SDD) hardware has 4Kn block size and for sure is more optimal compared to 512e (emulated), why would Veeam appliance care?
Smaller drives, like OS installation drive often are capped at 512 (native) byte size, I'm forced to change HDD format on the repository disk to 512e which I luckily can do.
But as Linux can handle both sizes I see no technical reason to enforce the same logical block sizes across different disks.
I feel that this should be corrected in future releases
-
dejan.ilic
- Enthusiast
- Posts: 50
- Liked: 5 times
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
-
david.domask
- Product Manager
- Posts: 3406
- Liked: 807 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam Infrastructure appliance unable to handle mixed logical disk sector size in same server
Hi dejan.ilic,
It's not about Linux / Veeam limitation, it's about LVM on the appliance.
LVM doesn't allow mixing of devices with different logical sectors -- you _can_ enable it with a config parameter, but as I understand, it's not recommended.
It's not about Linux / Veeam limitation, it's about LVM on the appliance.
LVM doesn't allow mixing of devices with different logical sectors -- you _can_ enable it with a config parameter, but as I understand, it's not recommended.
David Domask | Product Management: Principal Analyst
-
dejan.ilic
- Enthusiast
- Posts: 50
- Liked: 5 times
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
Re: Veeam Infrastructure appliance unable to handle mixed logical disk sector size in same server
I was using LVM on my homebrew hardened appliance and didnt notice any issues with mixed logical sector sizes (on Redhat Enterprise Linux 9)
But then I had configured my OS disk on a separate LVM volume group /logical volume compared to the repository data disks that was in another VG / LV.
Thats the reason for my surprise when the Veeam Appliance stopped after detecting the two different sizes on the separate disks.
But then I had configured my OS disk on a separate LVM volume group /logical volume compared to the repository data disks that was in another VG / LV.
Thats the reason for my surprise when the Veeam Appliance stopped after detecting the two different sizes on the separate disks.
Who is online
Users browsing this forum: No registered users and 60 guests