From: Dave Chinner <david@fromorbit.com>
To: Zhangfei Gao <zhangfei.gao@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
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: Mon, 18 Jul 2016 11:53:41 +1000 [thread overview]
Message-ID: <20160718015341.GB1922@dastard> (raw)
In-Reply-To: <CAMj5Bkhr3aLTRtb58xsZGwZWchFb95bdZ8NbiLEfG=vmoObxkQ@mail.gmail.com>
On Fri, Jul 15, 2016 at 03:55:20PM +0800, Zhangfei Gao wrote:
> Dear Dave
>
> On Wed, Jul 13, 2016 at 7:03 AM, Dave Chinner <david@fromorbit.com> wrote:
> > On Tue, Jul 12, 2016 at 12:43:24PM -0400, Theodore Ts'o wrote:
> >> 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.
> >
> > It's the same error I reported yesterday for ext3 on 4.7-rc6 when
> > rebooting a VM after it hung.
>
>
> Any link of this error?
http://article.gmane.org/gmane.comp.file-systems.ext4/53792
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-07-18 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMj5BkiVGQ4dAUY+wi-+O4qRdVS6YPiUP2BpsiE5y0r+2AhLgw@mail.gmail.com>
[not found] ` <CAMj5BkiKC2m3PLHvoDWwyj9BQZ-Bg5mD0f1J0kZcpwroH+rR1g@mail.gmail.com>
2016-07-12 7:14 ` ext4 error when testing virtio-scsi & vhost-scsi Zhangfei Gao
2016-07-12 16:43 ` Theodore Ts'o
2016-07-12 23:03 ` Dave Chinner
2016-07-15 7:55 ` Zhangfei Gao
2016-07-18 1:53 ` Dave Chinner [this message]
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=20160718015341.GB1922@dastard \
--to=david@fromorbit.com \
--cc=kvm@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=target-devel@vger.kernel.org \
--cc=tytso@mit.edu \
--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).