Description of problem: I just tried to install Fedora 18 and it crashed after I hit Begin. I told it to use my old partition layout but reformat everything: /boot sda1 1GB / LVM lv_root 400GB swap LVM lv_swap 8GB The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 390, in lvresize raise LVMError("lvresize failed for %s: %s" % (lv_name, msg)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2603, in resize lvm.lvresize(self.vg.name, self._name, self.size) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 370, in execute self.device.resize() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 323, in processActions action.execute() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 323, in doIt self.devicetree.processActions() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 174, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall turnOnFilesystems(storage) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) LVMError: lvresize failed for lv_root: running lvm lvresize --force -L 400000m --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } vg_tarantula/lv_root failed Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.11 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 686832 [details] File: anaconda-tb
Created attachment 686833 [details] File: anaconda.log
Created attachment 686834 [details] File: environ
Created attachment 686835 [details] File: ifcfg.log
Created attachment 686836 [details] File: packaging.log
Created attachment 686837 [details] File: program.log
Created attachment 686838 [details] File: storage.log
Created attachment 686839 [details] File: syslog
10:08:26,367 INFO program: Running... lvm lvresize --force -L 400000m --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } vg_tarantula/lv_root 10:08:26,405 ERR program: New size (12500 extents) matches existing size (12500 extents) 10:08:26,406 ERR program: Run `lvresize --help' for more information.
(In reply to comment #9) > 10:08:26,367 INFO program: Running... lvm lvresize --force -L 400000m > --config devices { > filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } > vg_tarantula/lv_root > 10:08:26,405 ERR program: New size (12500 extents) matches existing size > (12500 extents) So yes, the message is OK, isn't it? If extent size used is 32m, which, based on the logs it is, I don't see anything wrong here. The resize to that certain size was called on a device with the same existing size... Or is this just about the request for this to be a warning message/clean state instead of an error message/error state?
So has this been fixed in anaconda? I mean if someone uses the same size as existing one, the lvresize gives nonzero return value and an error message that the size requested is the same as existing and so it makes no point to resize... Hence the error state. David?
Moving to anaconda...
(In reply to Jeff Bastian from comment #0) > Description of problem: > I just tried to install Fedora 18 and it crashed after I hit Begin. I told > it to use my old partition layout but reformat everything: You left out the fact that you set about five different sizes for the root lv in the process. I suspect this has been fixed very recently for bug 1027947.