| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAMj5BkgqYq4feie3HVpp673JyFq+SEXRn2YiaO=v_v9RqW_pBw@mail.gmail.com> Date: Thu, 28 Jul 2016 09:29:35 +0800 From: Zhangfei Gao <zhangfei.gao@...il.com> To: Jan Kara <jack@...e.cz> Cc: "Theodore Ts'o" <tytso@....edu>, "Michael S. Tsirkin" <mst@...hat.com>, Nicholas Bellinger <nab@...ux-iscsi.org>, kvm@...r.kernel.org, qemu-devel@...gnu.org, target-devel@...r.kernel.org, linux-ext4@...r.kernel.org, virtualization@...ts.linux-foundation.org Subject: Re: ext4 error when testing virtio-scsi & vhost-scsi Hi, Jan On Wed, Jul 27, 2016 at 11:56 PM, Jan Kara <jack@...e.cz> wrote: > 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? > Tested twice, log pasted. Both using fileio, located in host ramfs /tmp Before e2fsck, umount /dev/sda 1. root@(none)$ mount -o errors=remount-ro /dev/sda /mnt [ 22.812053] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: errors=remount-ro $ rm /mnt/test [ 108.388905] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 108.406930] Aborting journal on device sda-8. [ 108.414120] EXT4-fs (sda): Remounting filesystem read-only [ 108.414847] EXT4-fs error (device sda) in ext4_dirty_inode:5487: IO failure [ 108.423571] EXT4-fs error (device sda) in ext4_free_blocks:4904: Journal has aborted [ 108.431919] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 108.440269] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 108.448568] EXT4-fs error (device sda) in ext4_ext_remove_space:3058: IO failure [ 108.456917] EXT4-fs error (device sda) in ext4_ext_truncate:4657: Corrupt filesystem [ 108.465267] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 108.473567] EXT4-fs error (device sda) in ext4_truncate:4150: IO failure [ 108.481917] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem root@(none)$ e2fsck /dev/sda e2fsck 1.42.9 (28-Dec-2013) /dev/sda is mounted. e2fsck: Cannot continue, aborting. root@(none)$ umount /mnt [ 260.756250] EXT4-fs error (device sda): ext4_put_super:837: Couldn't clean up the journal root@(none)$ umount /mnt e2fsck /dev/sda e2fsck 1.42.9 (28-Dec-2013) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... Superblock needs_recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. /dev/sda: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong for group #1 (32703, counted=8127). Fix<y>? yes Free blocks count wrong for group #2 (32768, counted=31744). Fix<y>? yes Free blocks count wrong (249509, counted=223909). Fix<y>? yes Free inodes count wrong for group #0 (8181, counted=8180). Fix<y>? yes Free inodes count wrong (65525, counted=65524). Fix<y>? yes /dev/sda: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda: 12/65536 files (8.3% non-contiguous), 38235/262144 blocks root@(none)$ 2. root@(none)$ rm /mnt/test [ 71.021484] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 71.044959] Aborting journal on device sda-8. [ 71.052152] EXT4-fs (sda): Remounting filesystem read-only [ 71.052833] EXT4-fs error (device sda) in ext4_dirty_inode:5487: IO failure [ 71.061600] EXT4-fs error (device sda) in ext4_free_blocks:4904: Journal has aborted [ 71.069948] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 71.078296] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 71.086597] EXT4-fs error (device sda) in ext4_ext_remove_space:3058: IO failure [ 71.094946] EXT4-fs error (device sda) in ext4_ext_truncate:4657: Corrupt filesystem [ 71.103296] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem [ 71.111595] EXT4-fs error (device sda) in ext4_truncate:4150: IO failure [ 71.119946] EXT4-fs error (device sda) in ext4_reserve_inode_write:5362: Corrupt filesystem root@(none)$ e2fsck /dev/sda e2fsck 1.42.9 (28-Dec-2013) /dev/sda is mounted. e2fsck: Cannot continue, aborting. root@(none)$ umou nt /mnt/ [ 92.103221] EXT4-fs error (device sda): ext4_put_super:837: Couldn't clean up the journal root@(none)$ umount /mnt/ e2fsck /dev/sda e2fsck 1.42.9 (28-Dec-2013) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... Superblock needs_recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. /dev/sda: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong for group #1 (32703, counted=8127). Fix<y>? yes Free blocks count wrong for group #2 (32768, counted=31744). Fix<y>? yes Free blocks count wrong (249509, counted=223909). Fix<y>? yes Free inodes count wrong for group #0 (8181, counted=8180). Fix<y>? yes Free inodes count wrong (65525, counted=65524). Fix<y>? yes /dev/sda: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda: 12/65536 files (8.3% non-contiguous), 38235/262144 blocks root@(none)$ Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists