Red Hat Bugzilla – Bug 1021037
IOException: Input/output error during read on /dev/vda
Last modified: 2014-04-30 03:24:44 EDT
Version-Release number of selected component:
libreport version: 2.0.9
cmdline: /usr/bin/python /usr/bin/anaconda
:The following was filed automatically by anaconda:
:anaconda 13.21.195 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.6/site-packages/parted/disk.py", line 213, in commit
: return self.__disk.commit()
: File "/usr/lib64/python2.6/site-packages/parted/decorators.py", line 31, in localeC
: ret = fn(*args, **kwds)
: File "<string>", line 2, in commit
: File "/usr/lib/anaconda/storage/formats/disklabel.py", line 256, in commit
: File "/usr/lib/anaconda/storage/formats/disklabel.py", line 235, in create
: File "/usr/lib/anaconda/storage/deviceaction.py", line 290, in execute
: File "/usr/lib/anaconda/storage/devicetree.py", line 718, in processActions
: File "/usr/lib/anaconda/storage/__init__.py", line 355, in doIt
: File "/usr/lib/anaconda/packages.py", line 110, in turnOnFilesystems
: File "/usr/lib/anaconda/dispatch.py", line 210, in moveStep
: rc = stepFunc(self.anaconda)
: File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
: File "/usr/lib/anaconda/gui.py", line 1476, in setScreen
: File "/usr/lib/anaconda/gui.py", line 1389, in nextClicked
: self.setScreen ()
:IOException: Input/output error during read on /dev/vda
This happened when I created a LV ion virt-manager. Repeatedly.
Solution: Create the LV manually and use that LV in virt-manager. After I did that, the VM installed properly.
On a HP N40L Microserver, with 2x 2TB drives as a RAID1 with a VG spanning the whole 2 TB.
(In reply to Jan Wildeboer from comment #2)
> This happened when I created a LV ion virt-manager. Repeatedly.
> Solution: Create the LV manually and use that LV in virt-manager. After I
> did that, the VM installed properly.
Hi Jan, so just to make sure I'm understanding what happened:
You created a VM with virt-manager, then
tried to create the LV to back the VM's vda with virt-manager, but
when you went to install the guest anaconda threw an exception.
If you create the LV manually and then hand the manually created LV to the VM as vda's backing storage, everything works as expected.
Do I have that right?
Yes, that is correct. It seems to be the (rather confusing) option in the LV creation dialog with Max Capacity versus Allocation.
When I set Max Capacity to something (say 8000 MB), the Allocation stays at 0. And things go wrong. However, I guess I just have to set Allocation to a non-zero value to avoid this problem.
IMHO the allocation field should default to Max Capacity to avoid this problem.
Just tested. And yes. When Allocation is set to a non-zero value, the problem doesn't show up.
Suggestion: Either set Allocation to a fitting non-zero value or (better IMHO) sync Allocation to Max Size, just as we do with memory setting.
At the very least setting Allocation to zero should cause an error as it is a non-working configuration.
This seems to be fixed upstream already using the sync option.
This is fixed upstream with:
Author: Martin Kletzander <firstname.lastname@example.org>
Date: Tue Apr 2 13:51:28 2013 +0200
Don't support sparse logical volumes
*** This bug has been marked as a duplicate of bug 1000980 ***