Bug 525953
| Summary: | Failure when partitioning vda disk | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dougal Ballantyne <dougal> | ||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | rawhide | CC: | anaconda-maint-list, gavin, steved, vanmeeuwen+fedora | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | anaconda_trace_hash:c2769d8a22c59e5419b2c4571f14ea34b9d845619faff86515eb34495395676c | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-09-28 13:44:09 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: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 362828 [details]
Attached traceback automatically from anaconda.
There are lots of error messages like the following in your syslog: <3>end_request: I/O error, dev vda, sector 409639 <3>Buffer I/O error on device vda1, logical block 51197 <4>lost page write due to I/O error on vda1 <3>Buffer I/O error on device vda1, logical block 51198 <4>lost page write due to I/O error on vda1 <3>Buffer I/O error on device vda1, logical block 51199 This indicates either a problem with hardware or with the kernel. Can you please attempt to verify this bug and if so, open a new one against the kernel? There's really not much anaconda can do about problems like this, nor is it even very easy to detect them in all the places they can occur. Created attachment 375117 [details]
Attached traceback automatically from anaconda.
Created attachment 397595 [details]
Attached traceback automatically from anaconda.
|
The following was filed automatically by anaconda: anaconda 12.15 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 163, in pvcreate raise LVMError("pvcreate failed for %s" % device) File "/usr/lib/anaconda/storage/formats/lvmpv.py", line 93, in create lvm.pvcreate(self.device) File "/usr/lib/anaconda/storage/deviceaction.py", line 273, in execute options=self.device.formatArgs) File "/usr/lib/anaconda/storage/devicetree.py", line 700, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 230, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems anaconda.id.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 204, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 127, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1201, in nextClicked self.anaconda.dispatch.gotoNext() LVMError: pvcreate failed for /dev/vda2