---------------------------------------- > Date: Tue, 6 Sep 2011 11:55:02 -0700 > From: jeremy@xxxxxxxx > To: tinnycloud@xxxxxxxxxxx > CC: konrad.wilk@xxxxxxxxxx; linux-ext4@xxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx > Subject: Re: [Xen-devel] RE: ext4 BUG in dom0 Kernel 2.6.32.36 > > On 09/06/2011 08:11 AM, MaoXiaoyun wrote: > > > > > Date: Tue, 6 Sep 2011 10:53:47 -0400 > > > From: konrad.wilk@xxxxxxxxxx > > > To: tinnycloud@xxxxxxxxxxx > > > CC: linux-ext4@xxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx; > > jeremy@xxxxxxxx > > > Subject: Re: ext4 BUG in dom0 Kernel 2.6.32.36 > > > > > > On Tue, Sep 06, 2011 at 03:24:14PM +0800, MaoXiaoyun wrote: > > > > > > > > > > > > Hi: > > > > > > > > I've met an ext4 Bug in dom0 kernel 2.6.32.36. (See kernel stack > > below) > > > > > > Did you try the 3.0 kernel? > > No, I am afried the change would be to much for our current env. > > May result in other stable issue. > > So, I want to dig out what really happen. Hopes. > > Another question is whether this is a regression compared to earlier > versions of 2.6.32? Do you know if this problem exists in a non-Xen > environment? > There are some others reports this issue in non-xen env. http://markmail.org/message/ywr4nfgiuvgdcr7y http://www.spinics.net/lists/linux-ext4/msg21066.html The difficulty is I haven't find a efficient way to reproduce it. (Currently it only show in our cluster, redeploy our cluster may cost 3days more. ) > Thanks, > J > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
