Bug 866895
Summary: | Can't reclaim space | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||||||||
Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||
Version: | 18 | CC: | g.kaviyarasu, jonathan, lsatenstein, pschindl, robatino, satellitgo, vanmeeuwen+fedora | ||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||
Last Closed: | 2012-10-23 14:23:00 UTC | Type: | Bug | ||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
Embargoed: | |||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||
Bug Blocks: | 752661 | ||||||||||||||||||||
Attachments: |
|
Description
Kamil Páral
2012-10-16 09:32:16 UTC
Created attachment 628058 [details]
anaconda.log
Created attachment 628059 [details]
ifcfg.log
Created attachment 628060 [details]
program.log
Created attachment 628061 [details]
storage.log
This violates The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria but it's very hard to check, because I don't know how to reproduce. But maybe anaconda developers will see the problem from the logs. Once you've removed the existing partitions, did you click the button above those to autocreate new partitions for the install? That's what you need to do in order to get autopartitioning layout on your disks. Please try that and let us know if it works. I haven't used custom partitioning at all, I used the simplified dialog for reclaiming space. After marking all partitions to be Deleted and hitting Reclaim space, I was told I have plenty space to install Fedora, so I hit Continue, I was taken to the main hub, but partition spoke icon showed an error. I repeated this twice. Ah, ok. Honestly I wasn't even aware of that simplified dialog until last night testing some other things. I think this is similar to a bug I hit last night, and valid. Created attachment 629355 [details]
anaconda.log
I hit the same problem as described in comment 7 Created attachment 629356 [details]
program.log
Created attachment 629357 [details]
storage.log
Created attachment 629358 [details]
syslog
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18 Package anaconda-18.19-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.19-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18 then log in and leave karma (feedback). Since I don't know any way how to reproduce this bug, I can't check it is fixed. If Anaconda developers didn't see anything fishy directly from the logs, let's just close it. I had a previous Linux on the /dev/sdc. I wanted to reclaim space and then continue with the installation. Anaconda does not allow one to reclaim space unless one is using automatic partitioning. (I needed to merge two adjacent partitions) This is the anaconda version that comes with Fedora-Workstation-netinst-x86_64-23_Alpha_TC2.iso Please reopen. I know that the statement, No changes until a "go" to begin installation is activated means that the proposed space reclamation has to be managed until ... that begin installation is activated. I believe this is a low level bug, as I switched to anaconda's live (F2) terminal mode and did my partition merging before returning to anaconda. I was able to merge the partitions without rebooting. If I did not have the knowledge of command line actions, I would have abandoned network-installation mode. (In reply to Leslie Satenstein from comment #17) > I had a previous Linux on the /dev/sdc. I wanted to reclaim space and then > continue with the installation. > > Anaconda does not allow one to reclaim space unless one is using automatic > partitioning. (I needed to merge two adjacent partitions) You can remove partitions in the custom storage spoke. > > This is the anaconda version that comes with > > Fedora-Workstation-netinst-x86_64-23_Alpha_TC2.iso > > Please reopen. I know that the statement, No changes until a "go" to begin > installation is activated means that the proposed space reclamation has to > be managed until ... that begin installation is activated. > > I believe this is a low level bug, as I switched to anaconda's live (F2) > terminal mode and did my partition merging before returning to anaconda. What, exactly, do you believe is the problematic behavior? If you went to the shell and did storage changes there, the only way to have the installer adjust to those changes is through the "rescan" button in the custom storage spoke. > > I was able to merge the partitions without rebooting. > > If I did not have the knowledge of command line actions, I would have > abandoned network-installation mode. Why, exactly? You say you wanted to merge two partitions. Does that mean "remove both and make a new one" or "remove the second and extend the first to occupy the space previously occupied by the second"? Both of these are fairly straightforward to accomplish using the installer. |