Re: [Xen-users] repeated domU filesystem corruption

["Fajar A. Nugraha" <list@xxxxxxxxx>]

On Mon, Oct 1, 2012 at 6:17 PM, Robert Rust <robert@xxxxxxxxxxxxxxx> wrote:
> On 10/1/12 2:18 AM, Peter Viskup wrote:
>>
>> 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.
>
>
> I am already running EXT3 volumes, so I have added that option to see if it
> helps.  Since I forgot to include in original post...
> distro: Ubuntu 12.0.4.1 LTS 64-bit
> kernel: 3.2.0-31-generic #50
> Xen package: xen-hypervisor-4.1-amd64         4.1.2-2ubuntu2.2
>
> We'll see if I can go a week without corruption with the barrier=0 option.
> I looked into filing a bug per Fajar's suggestion, but I'm not sure how I'd
> go about gathering the data they want given the nature of Xen (gather data
> in DomU or Dom0?

If the error is in domU, then domU's console (and possibly syslog)
messages is usually helpful

> is gathering the data several hours after the corruption
> occurs acceptable since it's not always immediately apparent?).

Usually you'll be able to speed it up by doing things like:
- sync
- apt-get update
- fio

-- 
Fajar

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