From: Theodore Ts'o <tytso@mit.edu>
To: Zhangfei Gao <zhangfei.gao@gmail.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
target-devel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext4 error when testing virtio-scsi & vhost-scsi
Date: Tue, 12 Jul 2016 12:43:24 -0400 [thread overview]
Message-ID: <20160712164324.GC11020@thunk.org> (raw)
In-Reply-To: <CAMj5BkgSXjD+_GB_VPgizowyyJ1uYxLiKd7ehQmEdVvnuY55cA@mail.gmail.com>
On Tue, Jul 12, 2016 at 03:14:38PM +0800, Zhangfei Gao wrote:
> Some update:
>
> If test with ext2, no problem in iblock.
> If test with ext4, ext4_mb_generate_buddy reported error in the
> removing files after reboot.
>
>
> root@(none)$ rm test
> [ 21.006549] EXT4-fs error (device sda): ext4_mb_generate_buddy:758: group 18
> , block bitmap and bg descriptor inconsistent: 26464 vs 25600 free clusters
> [ 21.008249] JBD2: Spotted dirty metadata buffer (dev = sda, blocknr = 0). Th
> ere's a risk of filesystem corruption in case of system crash.
>
> Any special notes of using ext4 in qemu?
Ext4 has more runtime consistency checking than ext2. So just because
ext4 complains doesn't mean that there isn't a problem with the file
system; it just means that ext4 is more likely to notice before you
lose user data.
So if you test with ext2, try running e2fsck afterwards, to make sure
the file system is consistent.
Given that I'm reguarly testing ext4 using kvm, and I haven't seen
anything like this in a very long time, I suspect the problemb is with
your SCSI code, and not with ext4.
- Ted
next prev parent reply other threads:[~2016-07-12 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 3:23 ext4 error when testing virtio-scsi & vhost-scsi Zhangfei Gao
2016-07-11 4:05 ` Zhangfei Gao
2016-07-12 7:14 ` Zhangfei Gao
2016-07-12 16:43 ` Theodore Ts'o [this message]
2016-07-12 23:03 ` Dave Chinner
2016-07-15 7:55 ` Zhangfei Gao
2016-07-18 1:53 ` Dave Chinner
2016-07-13 7:25 ` Zhangfei Gao
2016-07-19 7:56 ` Zhangfei Gao
2016-07-19 8:21 ` Zhangfei Gao
2016-07-27 7:58 ` Zhangfei Gao
2016-07-27 15:56 ` Jan Kara
2016-07-28 1:29 ` Zhangfei Gao
2016-08-01 2:40 ` Zhangfei Gao
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=20160712164324.GC11020@thunk.org \
--to=tytso@mit.edu \
--cc=kvm@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=target-devel@vger.kernel.org \
--cc=zhangfei.gao@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).