I've hit similar issues with XFS, and used the not-so-lovely workaround
of setting 'barrier=0' as mount options for that filesystem, which works
great. Not sure if it'd work with ext4 or not.
@Malcolm, do you have a Ticket ID that I can reference in a support
ticket to Citrix?
Side note -
Still there with current precise LTS.
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen
Torsten, this is a XenServer bug and not an Ubuntu bug. No current
release of XenServer is capable of running guests with recent Linux
kernels. A fix is (still) pending from Citrix. If you want an
unofficial fix (a replacement kernel for XenServer dom0, very
unsupported) contact me privately.
Any chance your contact gave a better timeframe than the next point
release, since that was released already twice (6.0.2) and I'm still
seeing the problem here at a most infuriating rate..
Is there some way of making sure that a new VM install won't have any
problems with this? Once the system
The release incorporating this fix is due for release around late July /
early August. The only workaround I know for now is to install a
patched kernel in the XenServer dom0. I have one and you may contact me
by email if you would like a copy, but bear in mind that it is very much
not supported
I should clarify that the timeframe for the XenServer release (6.1) I
gave above is an unofficial, unauthoritative estimate and subject to
alteration by Citrix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This turned out to be a XenServer bug related to the interaction between
blkback and barriers; my contact at Citrix has produced a dom0 kernel
patch which fixes the issue. I'm told the fix will be incorporated in
the next point release of XenServer.
** Changed in: linux (Ubuntu)
Status:
This bug is still present in the 3.2.2-030202 mainline build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications about
This bug is also still present in the 3.3.0-030300rc1 mainline build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage
I looked back into the mailing list archives and there has been a thread
titled: blkfront problem in pvops kernel when barriers enabled. As far
as I understand, this is a problem of the backend driver (which is part
of the host code), offering the barrier method for syncing but then
failing with
I just want to add that I'm encountering this issue with a Debian
Squeeze (Xen: 4.0.1) dom0. I'm using LVM volumes to store my disk images
(phy:/dev/Data/foobar,xvda,w), and have installed the domU using
netinstall. The install works fine, the error only happens when booting
the domU for the first
Same on Lucid with the latest linux-image-virtual-lts-backport-oneiric
3.0.0-13-virtual #22~lucid1-Ubuntu SMP. Disabling barriers works but
since these are suposed to be production ready boxes the only way is to
revert to linux-image-virtual-lts-backport-natty.
--
You received this bug
unfortunatelly, the workaround, which is described above, sometimes wont
work and xen-blkfront is corrupting fs again. But with enabled barries
it is corrupting fs on every second system boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
hi folks, i found a workaround from xen-devel mailing list.
just disable barrier for ext4 by putting
'barrier=0' in your /etc/fstab
line with your root fs should be like this:
/dev/xvdc /blah ext4 errors=remount-ro,barrier=0 0 1
--
You received this bug notification because you are a member of
For the record I've just tested linux-
image-3.2.0-030200rc2-generic_3.2.0-030200rc2.20151435 and the bug
is still present. This is still on XenServer 5.6 SP2; I'll try to test
on a XS 6 install later. (Lucid does work on both versions; the problem
is only with Oneiric.)
Stefan: I hadn't
Malcolm - I believe XenServer 6 is the first version to be certified
with Lucid (10.04) as a DomU. Are you at liberty to test that version
pairing? Then if 11.10 doesn't work as a DomU then we need to have a
look. 11.10 should also work as a Dom0 on XS 6.
--
You received this bug notification
The messages about the barrier fail as such are just informational. The
interesting part to me seems that while xvda and xvdc see the capacity
change message, there is nothing for xvdb. Maybe I missed the info but
it would be interesting to know what kind of mapping is used for the pv
disk
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications
What is your dom0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications about this bug go to:
Konrad: XenServer 5.6 SP2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications about this bug go to:
The bug is present in mainline kernel 3.1rc9.
** Tags removed: kernel-request-3.0.0-11.17 kernel-request-3.0.0-11.18
kernel-request-3.0.0-12.19 kernel-request-3.0.0-12.20 needs-upstream-
testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
Already confirmed on 3.0.0-12.20.
** Changed in: linux
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upstream-testing' tag. This
can be done by
** Summary changed:
- Xen blkfront i/o errors
+ Xen blkfront i/o errors prevent boot in domU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in
25 matches
Mail list logo
