Displaying 6 results from an estimated 6 matches for "ext4_dirty_inod".
Did you mean:
ext4_dirty_inode
2016 Jul 28
1
ext4 error when testing virtio-scsi & vhost-scsi
...ata
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
[...
2016 Jul 28
1
ext4 error when testing virtio-scsi & vhost-scsi
...ata
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
[...
2016 Apr 13
3
Bug#820862: xen-hypervisor-4.4-amd64: Xen VM on Jessie freezes often with INFO: task jbd2/xvda2-8:111 blocked for more than 120 seconds
...[<ffffffffa0032c52>] ? jbd2_journal_get_write_access+0x22/0x40 [jbd2]
[ 1200.060518] [<ffffffffa009d326>] ? __ext4_journal_get_write_access+0x36/0x80 [ext4]
[ 1200.060528] [<ffffffffa0073558>] ? ext4_reserve_inode_write+0x68/0x90 [ext4]
[ 1200.060539] [<ffffffffa007679b>] ? ext4_dirty_inode+0x3b/0x60 [ext4]
[ 1200.060547] [<ffffffffa00735bf>] ? ext4_mark_inode_dirty+0x3f/0x1d0 [ext4]
[ 1200.060554] [<ffffffffa007679b>] ? ext4_dirty_inode+0x3b/0x60 [ext4]
[ 1200.060558] [<ffffffff811cf682>] ? __mark_inode_dirty+0x172/0x270
[ 1200.060563] [<ffffffff811c1f41>] ?...
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).
2013 May 19
29
[Bug 64774] New: nouveau GF108 kernel crash in optimus mode when enabling external display output
https://bugs.freedesktop.org/show_bug.cgi?id=64774
Priority: medium
Bug ID: 64774
Assignee: nouveau at lists.freedesktop.org
Summary: nouveau GF108 kernel crash in optimus mode when
enabling external display output
QA Contact: xorg-team at lists.x.org
Severity: major
Classification: Unclassified