Re: [Xen-users] repeated domU filesystem corruption

[Peter Viskup <skupko.sk@xxxxxxxxx>]

I was experiencing the same with Ubuntu domU's just some months before.
The only solution was to migrate from EXT4 to EXT3 - that barrier=0 
option didn't helped me.
I am running Xen bundled by Debian - there are some discussions on the 
internet about issues handling of barrier's by Xen.
BR,
--
Peter

On 10/01/2012 03:26 AM, Mark Pryor wrote:
> inline
>
>
>
> ----- Original Message -----
> From: Robert Rust<robert@xxxxxxxxxxxxxxx>
> To: xen-users@xxxxxxxxxxxxx
> Cc:
> Sent: Sunday, September 30, 2012 1:44 PM
> Subject: [Xen-users] repeated domU filesystem corruption
>
> I'm being plagued by repeated corruption of file systems for a few of my DomUs. 
>  I originally thought it was a failing hard drive, so I've replaced the hard 
> drive but my problems continue.  I always end up with the following on the DomU 
> console:
> [177949.345654] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
> [177949.345669] Aborting journal on device xvda2.
>
> I'm using LVMs to house my file systems.  Can anyone help me root out what the 
> cause of this is?  Is it reasonable to blame software for this?
>
> -Robert
> ------------
> If its a newer kernel on recent ubuntu, try adding to fstab options (barrier=0)
>
> # grep barrier /etc/fstab
> /dev/xvda /               ext4    errors=remount-ro,barrier=0 0       1

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users