Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen

To: 637234@bugs.debian.org
Subject: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
From: Gedalya <gedalya@gedalya.net>
Date: Sat, 13 Aug 2011 15:17:35 -0400
Message-id: <[🔎] 4E46CDCF.9000208@gedalya.net>
Reply-to: Gedalya <gedalya@gedalya.net>, 637234@bugs.debian.org
In-reply-to: <handler.637234.B.13129143173146.ack@bugs.debian.org>
References: <[🔎] 20110809180728.2279.11548.reportbug@mail1.gedalya.net> <handler.637234.B.13129143173146.ack@bugs.debian.org>

Confirmed this happens under xen, not under native hardware or vmware.

Reproduced on various xen hosts with both i686-pae and amd64 kernels inDomU.

On a side note: DomU doesn't come back up on a restart, it seems likeit's destroyed and not recreated. Seems like this too was introducedwith linux 3.0.0-1, perhaps a separate bug should be filed?

Reply to:

Follow-Ups:
- Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
  - From: Ben Hutchings <ben@decadent.org.uk>

References:
- Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
  - From: Gedalya <gedalya@gedalya.net>

Prev by Date: Processed: Re: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Next by Date: Bug#637725: linux-image-3.0.0-1-amd64: Xen DomU restore fails with 3.0 kernel
Previous by thread: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
Next by thread: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
Index(es):
- Date
- Thread