From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] EXT3-fs error on Git HEAD
Date: Mon, 29 Jun 2009 09:50:32 +1000 [thread overview]
Message-ID: <20090629095032.f729525f.mle+tools@mega-nerd.com> (raw)
Hi all,
I have a number of Qemu VMs. Over the weekend I updated to the latest
Git head and now two of my VMs (one i386 and one x86-64) are having
disk errors. Strange thing is, my arm VM is working flawlessly.
In the x86-64 VM I get errors like this:
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 405992: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 405989: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 405986: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 405998: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 428975: bad block 244347
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 389303: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 290747: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 290762: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 239599: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 389850: bad block 64
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 389282: bad block 8
EXT3-fs error (device sda1): ext3_xattr_block_get: inode 230699: bad block 8
Any clues?
Cheers,
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
next reply other threads:[~2009-06-28 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 23:50 Erik de Castro Lopo [this message]
2009-06-29 3:42 ` [Qemu-devel] EXT3-fs error on Git HEAD Erik de Castro Lopo
2009-06-29 6:42 ` Filip Navara
2009-06-29 16:27 ` Frank Arnold
2009-06-30 9:07 ` Kevin Wolf
2009-06-30 13:32 ` Frank Arnold
2009-07-10 12:34 ` Andre Przywara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090629095032.f729525f.mle+tools@mega-nerd.com \
--to=mle+tools@mega-nerd.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.