From: Gedalya <gedalya@gedalya.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: 637234@bugs.debian.org, xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <ijc@hellion.org.uk>
Subject: Re: Re: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
Date: Fri, 26 Aug 2011 18:58:34 -0400 [thread overview]
Message-ID: <4E58251A.8090108@gedalya.net> (raw)
In-Reply-To: <20110826175317.GA5043@dumpdata.com>
> One way to make sure that is not the case is to disable barriers in the
> guest. Meaning in /etc/fstab have something like this:
>
> /dev/xvdc /blah ext4 errors=remount-ro,barrier=0 0 1
That seems to fix it. It was remounting as read only either during the
boot process or immediately after, and now it boots up and seems to stay
up. I'll test laster with a DomU that actually has things running.
This also fixes the reboot problem I noted earlier, init 6 now reboots
the DomU rather than destory it.
>
> The other question is what version of Dom0 are you running? Is it 2.6.32?
> 2.6.39?
squeeze, running linux-image-2.6.32-5-xen-amd64 2.6.32-35
next prev parent reply other threads:[~2011-08-26 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110809180728.2279.11548.reportbug@mail1.gedalya.net>
2011-08-25 6:47 ` Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen Ian Campbell
2011-08-25 7:20 ` Gedalya
2011-08-26 17:53 ` Konrad Rzeszutek Wilk
2011-08-26 22:58 ` Gedalya [this message]
2011-08-29 14:08 ` Konrad Rzeszutek Wilk
2011-09-07 1:51 ` Bug#637234: [Xen-devel] " Ben Hutchings
2011-09-07 12:29 ` Bug#637234: " Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E58251A.8090108@gedalya.net \
--to=gedalya@gedalya.net \
--cc=637234@bugs.debian.org \
--cc=ijc@hellion.org.uk \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.