Possible kpartx bug investigation/report

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I'm while I was trying to get a device working on multipath I had
a problem with kpartx. The problem is the following: I mounted an
iSCSI deviec that is exported with block size of 4K. The multipath side works
correctly, the problem arises when kpartx maps the partition contained
in the device. When mounting the partition I get an error saying that the
partition doesn't contain a filesystem. After some digging I found that kpartx calculates a wrong offset and size because it treats the offset and the size as
they was of 512b. I mean that they not get multiplied by 4096 / 512 = 8. By
using dmsetup and multiplying by 8 the offset and size I get a device that
mounts correctly, the same by patching kpartx/gpt.c and adding a
multiplication of offset/size by get_sector_size(fd) / 512.
Since I'm not an expert in this field I cannot state for sure that the problem
is this and doesn't depend on something else like some fault I've done or
a buggy implementation of iSCSI by the NAS I'm using. I then kindly ask if you can help me to determine if this is a kpartx bug or something else so I can get it
working in the correct way or file a bug.

Thanks in advance,
Best regards,
Tarcisio Fedrizzi.

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel


[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux