Hello,
I suppose it''s a Xen problem, but it can be an Ext4 problem : just
after
mounting an ext4 partition, I tried to move (mv) a rsnapshot dir from an
ext3 (xvda2) partition to the ext4 (xvda3) one.
Some symbolic links was moved, then there is this error :
Feb 24 13:30:40 sofia kernel: EXT4-fs: mounted filesystem with
ordered data mode.
Feb 24 13:31:35 sofia kernel: blkfront: xvda3: write barrier op failed
Feb 24 13:31:35 sofia kernel: blkfront: xvda3: barriers disabled
Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
sector 50593912
Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
sector 50593912
Feb 24 13:31:35 sofia kernel: Aborting journal on device xvda3:8.
Feb 24 13:31:35 sofia kernel: ext4_abort called.
Feb 24 13:31:35 sofia kernel: EXT4-fs error (device xvda3):
ext4_journal_start_sb: Detected aborted journal
Feb 24 13:31:35 sofia kernel: Remounting filesystem read-only
But I don''t see anything in Xen logs.
Does someone know what is the cause ?
Thanks,
Olivier
PS : I use a 2.6.28.6 kernel, Dom0 and DomU are Debian Lenny 64bit, and
VT is enabled.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Well, in the 2.6.28.7 changelog I found that :
Xen doesn''t report that barriers are not supported until buffer I/O
is
reported as completed, instead of when the buffer I/O is submitted.
Add a check and a fallback codepath to journal_wait_on_commit_record()
to detect this case, so that attempts to mount ext4 filesystems on
LVM/devicemapper devices on Xen guests don''t blow up with an
"Aborting
journal on device XXX"; "Remounting filesystem read-only"
error.
As there is a lot of Ext4 fixes too, I will upgrade my kernel before continue.
Olivier
Olivier B. a écrit :> Hello,
>
> I suppose it''s a Xen problem, but it can be an Ext4 problem : just
> after mounting an ext4 partition, I tried to move (mv) a rsnapshot dir
> from an ext3 (xvda2) partition to the ext4 (xvda3) one.
>
> Some symbolic links was moved, then there is this error :
> Feb 24 13:30:40 sofia kernel: EXT4-fs: mounted filesystem with
> ordered data mode.
> Feb 24 13:31:35 sofia kernel: blkfront: xvda3: write barrier op failed
> Feb 24 13:31:35 sofia kernel: blkfront: xvda3: barriers disabled
> Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
> sector 50593912
> Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
> sector 50593912
> Feb 24 13:31:35 sofia kernel: Aborting journal on device xvda3:8.
> Feb 24 13:31:35 sofia kernel: ext4_abort called.
> Feb 24 13:31:35 sofia kernel: EXT4-fs error (device xvda3):
> ext4_journal_start_sb: Detected aborted journal
> Feb 24 13:31:35 sofia kernel: Remounting filesystem read-only
>
> But I don''t see anything in Xen logs.
> Does someone know what is the cause ?
>
> Thanks,
> Olivier
> PS : I use a 2.6.28.6 kernel, Dom0 and DomU are Debian Lenny 64bit,
> and VT is enabled.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
So I answer, with the last kernel (2.6.28.7) there is no more the problem :
Feb 24 14:20:20 sofia kernel: EXT4-fs: mounted filesystem with
ordered data mode.
Feb 24 14:20:41 sofia kernel: JBD: barrier-based sync failed on
xvda3:8 - disabling barriers
It works very well :)
Olivier
Olivier B. a écrit :> Well, in the 2.6.28.7 changelog I found that :
>
> Xen doesn''t report that barriers are not supported until buffer
I/O is
> reported as completed, instead of when the buffer I/O is submitted.
> Add a check and a fallback codepath to journal_wait_on_commit_record()
> to detect this case, so that attempts to mount ext4 filesystems on
> LVM/devicemapper devices on Xen guests don''t blow up with an
"Aborting
> journal on device XXX"; "Remounting filesystem read-only"
error.
>
> As there is a lot of Ext4 fixes too, I will upgrade my kernel before
> continue.
>
> Olivier
>
>
> Olivier B. a écrit :
>> Hello,
>>
>> I suppose it''s a Xen problem, but it can be an Ext4 problem :
just
>> after mounting an ext4 partition, I tried to move (mv) a rsnapshot
>> dir from an ext3 (xvda2) partition to the ext4 (xvda3) one.
>>
>> Some symbolic links was moved, then there is this error :
>> Feb 24 13:30:40 sofia kernel: EXT4-fs: mounted filesystem with
>> ordered data mode.
>> Feb 24 13:31:35 sofia kernel: blkfront: xvda3: write barrier op
>> failed
>> Feb 24 13:31:35 sofia kernel: blkfront: xvda3: barriers disabled
>> Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
>> sector 50593912
>> Feb 24 13:31:35 sofia kernel: end_request: I/O error, dev xvda3,
>> sector 50593912
>> Feb 24 13:31:35 sofia kernel: Aborting journal on device xvda3:8.
>> Feb 24 13:31:35 sofia kernel: ext4_abort called.
>> Feb 24 13:31:35 sofia kernel: EXT4-fs error (device xvda3):
>> ext4_journal_start_sb: Detected aborted journal
>> Feb 24 13:31:35 sofia kernel: Remounting filesystem read-only
>>
>> But I don''t see anything in Xen logs.
>> Does someone know what is the cause ?
>>
>> Thanks,
>> Olivier
>> PS : I use a 2.6.28.6 kernel, Dom0 and DomU are Debian Lenny 64bit,
>> and VT is enabled.
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users