#1884 Issue `closed`: Partition information recorded is unexpected when disk has 4K block size¶

Labels: bug, fixed / solved / done

rmetrich opened issue at 2018-08-01 08:43:¶

Relax-and-Recover (ReaR) Issue Template¶

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

ReaR version ("/usr/sbin/rear -V"): latest
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): RHEL7
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"): N/A
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): See on AIX/LPAR and PowerNV BareMetal
System architecture (x86 compatible or PPC64/PPC64LE or what excat ARM device): PPC64LE
Description of the issue (ideally so that others can reproduce it):

When the system disk has a 4K block size (both for logical and physical blocks), which happens with IBM harddisks, the partition start/size and disk size computation is broken, causing unexpected values to be recorded (8 times what is expected, 8 being 4096 / 512).

pcahyna commented at 2018-08-01 09:07:¶

Is it related to #1195 ?

jsmeix commented at 2018-08-01 09:17:¶

@schabrolles
I assigned it to you because it can be reproduced with certain IBM disks.

jsmeix commented at 2018-08-01 09:19:¶

See the "ReaR/PPC Disk size issue" mail thread on the rear-devel mailing list
http://lists.relax-and-recover.org/pipermail/rear-devel/2018-July/thread.html

rmetrich commented at 2018-08-01 09:30:¶

@pcahyna indeed, related to #1195

jsmeix commented at 2018-08-07 11:24:¶

With https://github.com/rear/rear/pull/1885 merged
this issue should be sufficiently fixed for now.

Regarding "sufficiently ... for now" see
https://github.com/rear/rear/pull/1885#issuecomment-410725516

[Export of Github issue for rear/rear.]

#1884 Issue closed: Partition information recorded is unexpected when disk has 4K block size¶