Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 619005
Summary: | LVMError: lvcreate failed for vg_devel4/lv_swap: Unable to create new logical volume with no extents | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karsten Hopp <karsten> | ||||||
Component: | anaconda | Assignee: | David Cantrell <dcantrell> | ||||||
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 19 | CC: | awilliam, bishop, dan, jonathan, jstodola, vanmeeuwen+fedora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | s390x | ||||||||
OS: | Linux | ||||||||
Whiteboard: | anaconda_trace_hash:9b2eab2753dec5b915fe90df9c48317b8d82f2a475763fc83b72ca8e8e56dd9f | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-05-12 22:07:22 UTC | Type: | --- | ||||||
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: | 467765 | ||||||||
Attachments: |
|
Description
Karsten Hopp
2010-07-28 10:28:41 UTC
Created attachment 434973 [details]
Attached traceback automatically from anaconda.
Created attachment 434976 [details]
Don't try to create a logical partition with size 0
I'm not sure about growable partitions, are they allowed to have an minimum size of 0 ? If so, this patch needs some more work
I ran into this error with a kickstart like: logvol /home --fstype ext3 --name=home --vgname=vg01 [snip] --size 1 --grow --maxsize 5120 I suspect the 'size 1' is below the extent size (32 for me), and is thus rounded down (can we round it up? two birds, one stone) and the resulting parameter passed into the lvcreate is 0. In my case, after seeing this error, I bumped the size of the VMDK and restarted my kickstart. Same issue with 30Gb free, so I'm sure it had enough space to allocate. After adjusting my --size to 32 (mb) initially, the error went away. If I have time later, I'll grovel the code to be sure -- this is just a guess, right now, based on the behaviour, but I'd bet a latte on it. Created attachment 489797 [details]
anaconda 15.25 exception report
Reproducible with anaconda 15.25. When user selects autopartitioning, anaconda creates swap with size 0 MB:
vg_rtt6 37440
lv_root 36928 / ext4
lv_swap 0 swap
lv_boot 500 /boot ext4
Free 12
There is a traceback when writing changes to disks.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 dcantrell marked this as POST on 2011-04-19. The patch was https://www.redhat.com/archives/anaconda-devel-list/2011-April/msg00230.html . So far as I can tell it was never reviewed and pushed. However, the relevant file - pyanaconda/iutil.py - is rather different now, and the 'minswap' stuff no longer exists in anaconda or blivet git that I can see. So I'm pretty sure this bug report is now irrelevant. Karsten, Bishop - if you guys still find this use case relevant, please test it with F18 or an F19 build and file a new bug if it's broken in some other way, but this bug report is just obsolete now, the relevant code no longer exists. |