From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony Sheetz <sheetzam@inspire.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
Teck Choon Giam <giamteckchoon@gmail.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: BUG: ext3 corruption in domU
Date: Tue, 2 Jul 2013 14:10:32 -0400 [thread overview]
Message-ID: <20130702181032.GA6303@phenom.dumpdata.com> (raw)
In-Reply-To: <CAP8K4vK5oQTkfg97QqxrDm=4b5+aLNTQUKQYFzA23KbC2ocwJA@mail.gmail.com>
On Fri, Jun 07, 2013 at 02:43:06PM -0400, Anthony Sheetz wrote:
> Not a problem. Just wanted to be sure we weren't a dependency. Thanks
> for your attention!
>
> On Fri, Jun 7, 2013 at 1:10 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Tue, Jun 04, 2013 at 09:41:10AM -0400, Konrad Rzeszutek Wilk wrote:
> >> On Tue, Jun 04, 2013 at 08:55:26AM -0400, Anthony Sheetz wrote:
> >> > On Thu, May 30, 2013 at 2:36 PM, Konrad Rzeszutek Wilk
> >> > <konrad.wilk@oracle.com> wrote:
> >> > > On Wed, May 29, 2013 at 07:53:39AM -0400, Anthony Sheetz wrote:
> >> > >> Is there anything else I can get you at this time to help troubleshoot this?
> >> > >
> >> > > Well, this reminds me of a ext3 bug in the 2.6.32 stable tree that
> >> > > the maintainer of ext3 would not want to backport the fix. It was an
> >> > > bug that caused corruption.
> >> > >
> >> > > If I could just remember the email thread about it.
> >>
> >> Can't recall it, but maybe Teck can?
> >
> >
> > He doesn't seem to respond.
> >
> > Anthony, I have this on my queue to look - so will get to it.
> > Sadly that is not going to happen this week :-(
Installing a new box with Wheezy to try this out. The one thing I could
not find in the thread and in the bug was the guest config. Could you
please reply back with it? Thanks.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-07-02 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 17:39 BUG: ext3 corruption in domU Anthony Sheetz
2013-04-17 13:00 ` Ian Campbell
2013-04-22 12:22 ` Anthony Sheetz
2013-04-22 12:26 ` Ian Campbell
2013-05-22 20:10 ` Konrad Rzeszutek Wilk
2013-05-23 18:19 ` Anthony Sheetz
2013-05-24 14:20 ` Konrad Rzeszutek Wilk
2013-05-28 14:27 ` Anthony Sheetz
2013-05-28 18:02 ` Anthony Sheetz
2013-05-28 18:18 ` Konrad Rzeszutek Wilk
2013-05-28 18:19 ` Anthony Sheetz
2013-05-29 15:15 ` Konrad Rzeszutek Wilk
2013-05-29 11:53 ` Anthony Sheetz
2013-05-30 18:36 ` Konrad Rzeszutek Wilk
2013-06-04 12:55 ` Anthony Sheetz
2013-06-04 13:41 ` Konrad Rzeszutek Wilk
2013-06-07 17:10 ` Konrad Rzeszutek Wilk
2013-06-07 18:43 ` Anthony Sheetz
2013-07-02 18:10 ` Konrad Rzeszutek Wilk [this message]
2013-05-24 17:48 ` Roger Pau Monné
2013-05-28 12:10 ` Anthony Sheetz
2013-05-28 12:14 ` Roger Pau Monné
2013-05-28 18:15 ` Anthony Sheetz
2013-05-29 8:39 ` Ian Campbell
2013-05-06 12:46 ` Anthony Sheetz
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=20130702181032.GA6303@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=giamteckchoon@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sheetzam@inspire.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).