I'm using multipath-tools 0.4.7-r2. I have a 5TB disk with a single huge partition in its GPT. Everything works, but my 5TB partition appears as a 1TB partition in /proc/devices. I downloaded source from http://christophe.varoqui.free.fr/ and it appears that the number of sectors in a partition (64-bit number) is being saved into a 32-bit number. Thus the maximum partition size kpartx sees is 1TB. I've modified the source for kpartx, mainly changing "long" to "long long". After those changes my kpartx behaves properly. I've got diffs of the changes made if anybody is interested.
Created attachment 170776 [details] modifications to multipath-tools-0.4.8/kpartx/devmapper.c
Created attachment 170777 [details] modifications to multipath-tools-0.4.8/kpartx/devmapper.h.diff
Created attachment 170778 [details] modifications to multipath-tools-0.4.8/kpartx/gpt.c
Created attachment 170779 [details] modifications to multipath-tools-0.4.8/kpartx/kpartx.c
Created attachment 170780 [details] modifications to multipath-tools-0.4.8/kpartx/kpartx.h
The fix seams to be in upstream git but there's no release after the fix.
Created attachment 190553 [details, diff] Patch that fixes 1-2 TB limit in kpartx This patch was created from the commit to the multipath-tools git tree that fixes the issue, pushed by RedHat. I've used it on my system and confirmed that it fixes the problem. It's essentially the result of cat'ing all of James Tay's patches together, but done a slightly different way.
Created attachment 190554 [details] Ebuild that uses the patch from my previous post This is an ebuild I used on my system that resolved the problem with the 1-2 TB limit in kpartx.
In 0.4.8-r1 now. Upstream needs to stop slacking and cut a release.
