search for: ext4_put_super

Displaying 5 results from an estimated 5 matches for "ext4_put_super".

Did you mean: ext3_put_super
2016 Jul 28
1
ext4 error when testing virtio-scsi & vhost-scsi
...cate: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 se...
2016 Jul 28
1
ext4 error when testing virtio-scsi & vhost-scsi
...cate: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 se...
2016 Jul 27
2
ext4 error when testing virtio-scsi & vhost-scsi
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).
2016 Jul 27
2
ext4 error when testing virtio-scsi & vhost-scsi
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).
2015 May 25
2
fsck failing to notice that the block device was pulled out from under it?
...3145728 size 8192 starting block 147922176) May 25 12:39:51 hier kernel: [79872.773975] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -19 writing to inode 40770076 (offset 3887104 size 4096 starting block 5281717) May 25 12:39:51 hier kernel: [79873.230984] EXT4-fs error (device dm-0): ext4_put_super:790: Couldn't clean up the journal May 25 12:39:51 hier kernel: [79873.230990] EXT4-fs (dm-0): Remounting filesystem read-only May 25 12:39:51 hier kernel: [79873.230992] EXT4-fs (dm-0): previous I/O error to superblock detected May 25 12:44:07 hier kernel: [80128.859704] EXT4-fs (dm-0): recove...