| Summary: | Freeze when editing LVM2 volume in anaconda installer | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter Levart <peter.levart> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dennis, gansalmon, g.kaviyarasu, itamar, jonathan, kernel-maint, madhu.chinakonda, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-22 20:04:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Peter Levart
2012-01-10 14:04:58 UTC
How can I provide additional insight? Should I attach to kernel somehow to see what is the cause of freeze? How? We aren't going to be able to fix the F16 install/livecd images at this point. Do you have the same problem with the F17 Alpha images? Unfortunately I just got new machine this week and had to return the old one (which exhibited this behavior) today. I'm afraid the contents of that disk are already gone by now (will ask tomorrow morning and let you know). I haven't been able to establish the cause of the freeze by now. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. Unfortunately I have no means to test this any more. The disk that exhibited this behavior has been erased. I can't reproduce the problem. |