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@xxxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
