[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Filesystem corruptions

On Friday, 20 June 2014, 16:47:04, Patric Hafner | geOps [via Xen] <[hidden email]> wrote:
>[1215379.302679] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
>[1215379.302689] Aborting journal on device xvda2.
>[1215379.304193] EXT3-fs (xvda2): error: ext3_journal_start_sb: Detected
>aborted journal
>[1215379.304200] EXT3-fs (xvda2): error: remounting filesystem read-only
>[1215379.329043] EXT3-fs (xvda2): error: remounting filesystem read-only
>[1215379.329246] EXT3-fs (xvda2): error in ext3_create: IO failure
>[1215379.330502] __journal_remove_journal_head: freeing b_committed_data

Patric, I've seen similar issue few times in the past and it was always some storage access issue. Your guest suddenly lost connection to own virtual disk, was trying to mount it in RO mode but this also failed.Â
What is your storage? Do you have more VMs on the same storage? Any storage related errors on dom0?

- Radek SmigielskiÂ

View this message in context: Re: Filesystem corruptions
Sent from the Xen - User mailing list archive at Nabble.com.
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.