Hide Forgot
creation of a new volume to replace existing ext3 fails system-config-lvm-1.1.5-8.el5_6.1 How reproducible: reliable reproducible Steps to Reproduce: 1. create a new/replacement partition table using fdisk, on an unused disk 2. create one unformatted ext3 partition spanning the entire drive 3. launch s-c-lvm 4. browse to sdb... s-c-lvm will complain that sdb is uninitialized 5. click the button to initialize lvm 6. check the output that s-c-lvm sends to console: Actual results: s-c-lvm appears to hang for a while and sends a traceback to console Expected results: lvm pv created that spans sdb Additional info: Traceback (most recent call last): File "/usr/share/system-config-lvm/InputController.py", line 664, in on_init_entity if self.initialize_entity(pv) == None: File "/usr/share/system-config-lvm/InputController.py", line 753, in initialize_entity path = self.model_factory.partition_UV(pv) File "/usr/share/system-config-lvm/lvm_model.py", line 717, in partition_UV pv.setPartition((devname, new_part)) File "/usr/share/system-config-lvm/PhysicalVolume.py", line 136, in setPartition self.size = part.getSizeBytes()/1024.0/1024/1024 AttributeError: 'NoneType' object has no attribute 'getSizeBytes'
after s-c-lvm is later closed: parted looks like: GNU Parted 1.8.1 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: WINSYS SF2372 (scsi) Disk /dev/sdb: 2997GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 17.4kB 2859GB 2859GB primary lvm s-c-lvm shows the sdb entity as unitialized s-c-lvm _also_ shows the vg on sdb from a previous installation, which it did not show before.
/dev/ruut should be the vg from a previous installation, with lvs hoom and ruut_vol trying to set the partition type of an lv, from "none" to "ext3", results in an error message displayed in a popup window (manually copied): Creation of filesystem failed. Command attempted: "/sbin/mkfs -t ext3 /dev/ruut/hoom" system error message: could not stat /dev/ruut/hoom -- no such file or directory
My attempt to reproduce your test case failed. I have added new disk to my virtual machine and proceed according to yours comments in #1 but it works for me.
thanks, I'll file a bug with more details if I narrow down the preconditions to something reproducible.
bug 700253 describes a very similar bug, perhaps the only difference is a new package, system-config-lvm-1.1.5-9.el5.
This is the same problem with EFI GPT partition, marking as duplicate. There won't be any support for that but backtraces should no occur any longer. *** This bug has been marked as a duplicate of bug 700253 ***