From: Jan Kara <jack@suse.cz>
To: Zhangfei Gao <zhangfei.gao@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
"Michael S. Tsirkin" <mst@redhat.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
target-devel@vger.kernel.org, linux-ext4@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: ext4 error when testing virtio-scsi & vhost-scsi
Date: Wed, 27 Jul 2016 17:56:08 +0200 [thread overview]
Message-ID: <20160727155608.GC1659@quack2.suse.cz> (raw)
In-Reply-To: <CAMj5BkifLL=3C5f0VZKhpNmi81em8P5VNupr7d7_aD=uo2Hwow@mail.gmail.com>
Hi!
On Wed 27-07-16 15:58:55, Zhangfei Gao wrote:
> Hi, Michael
>
> I have met ext4 error when using vhost_scsi on arm64 platform, and
> suspect it is vhost_scsi issue.
>
> Ext4 error when testing virtio_scsi & vhost_scsi
>
>
> No issue:
> 1. virtio_scsi, ext4
> 2. vhost_scsi & virtio_scsi, ext2
> 3. Instead of vhost, also tried loopback and no problem.
> Using loopback, host can use the new block device, while vhost is used
> by guest (qemu).
> http://www.linux-iscsi.org/wiki/Tcm_loop
> Test directly in host, not find ext4 error.
>
>
>
> Have issue:
> 1. vhost_scsi & virtio_scsi, ext4
> a. iblock
> b, fileio, file located in /tmp (ram), no device based.
>
> 2, Have tried 4.7-r2 and 4.5-rc1 on D02 board, both have issue.
> Since I need kvm specific patch for D02, so it may not freely to switch
> to older version.
>
> 3. Also test with ext4, disabling journal
> mkfs.ext4 -O ^has_journal /dev/sda
>
>
> Do you have any suggestion?
So can you mount the filesystem with errors=remount-ro to avoid clobbering
the fs after the problem happens? And then run e2fsck on the problematic
filesystem and send the output here?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-07-27 15:56 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
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 [this message]
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=20160727155608.GC1659@quack2.suse.cz \
--to=jack@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=qemu-devel@nongnu.org \
--cc=target-devel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.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).