Bugzilla – Bug 127896
Possible number overflow in YaST2 LVM
Last modified: 2006-06-05 15:57:35 UTC
In SuSE 10.0 boxed final, - in the expert partitioner, try to create a LVM larger than 1.9 Tb - it doesn't - it wraps around to a negative number and obviously doesn't create the partition.
Congratulations for the least meaningful bug subject of the year.
Need y2log files from /var/log/YaST2/y2log
The bindings from LibStorage to YCP cannot handle long long ints: For values greater 0xffffffff the swig_sizeK_get of LvmVgInfo returns nil and produces this error message in y2log: [Y2Perl] YPerl.cc(fromPerlScalar):991 Expected integer, got float, SV with TYPE: PVNV, FLAGS: TEMP NOK POK pIOK pNOK pPOK [Y2Perl] YPerl.cc(callInner):336 ... when returning from LibStorage::LvmVgInfo::swig_sizeK_get So not only LVM but all storage containers are affected -> critical for SLES10.
Ugh. There's also some discussion in bug 75798.
Actually two bugs here: - unsigned integers presented as signed - not handling long longs. Both fixed in yast2-perl-bindings-2.13.3.
*** Bug 174795 has been marked as a duplicate of this bug. ***
*** Bug 75798 has been marked as a duplicate of this bug. ***