search for: end_request

...---- dmesg -------- astFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved error code) -- (asc=0x02, ascq=0x00) The failed "Read 10" packet command was: "28 00 00 00 34 e7 00 00 20 00 00 00 00 00 00 00 " end_request: I/O error, dev hdb, sector 54172 hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved e...

...---- dmesg -------- astFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved error code) -- (asc=0x02, ascq=0x00) The failed "Read 10" packet command was: "28 00 00 00 34 e7 00 00 20 00 00 00 00 00 00 00 " end_request: I/O error, dev hdb, sector 54172 hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved e...

...rough SCSI device sdd: 321672960 512-byte hdwr sectors (164697 MB) sdd: assuming drive cache: write through (so far this is correct, it's a 160GB drive in the enclosure) (the leading space on the next line is literally there in dmesg) ?sdd:SCSI error : <7 0 0 0> return code = 0x10070000 end_request: I/O error, dev sdd, sector 0 Buffer I/O error on device sdd, logical block 0 SCSI error : <7 0 0 0> return code = 0x10070000 end_request: I/O error, dev sdd, sector 0 Buffer I/O error on device sdd, logical block 0 SCSI error : <7 0 0 0> return code = 0x10070000 end_request: I/O error,...

...efaults 0 0 /dev/xvda3 swap swap defaults 0 0 ** Problem ** While doing some tests writing files in domU I got; # dd if=/dev/zero of=/deleteme bs=1M count=100 100+0 records in 100+0 records out # dd if=/dev/zero of=/tmp/deleteme bs=1M count=100 end_request: I/O error, dev xvda2, sector 366778 end_request: I/O error, dev xvda2, sector 366844 end_request: I/O error, dev xvda2, sector 381116 printk: 8071 messages suppressed. Buffer I/O error on device xvda2, logical block 190558 lost page write due to I/O error on xvda2 end_request: I/O error, dev xvda2...

...ll, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 end_request: I/O error, dev 16:02 (hdc), sector 1834800 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Erro...

...archy across resulted in catastrophic data corruption of the filessytem itself. Manual fsck was needed to fixup the filesystem & there were many very bad errors needing fixing. With this patch applied the DomU sees the I/O failures and kernel logs messages Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 722127 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 730327 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 738527 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 746727 Dec 1 11:02:5...

...SB on a USB 2.0 PCI card, 750 GB /dev/sdf - USB on a USB 2.0 PCI card, 1 TB Here's what I see in the /var/log/messages: May 27 05:08:42 hume ntpd[4844]: kernel time sync enabled 0001 May 27 08:01:01 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 08:01:01 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 08:01:01 hume kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0 May 27 08:01:01 hume kernel: May 27 08:14:27 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 08:14:27 hume kernel: end_request: I/O erro...

...sed in replies. The second time there were no reactions. The patch seems to work for Massimo... Massimo Cetra wrote: > Massimo Cetra ha scritto: >> Hello all, >> >> i ended up with some thiusands of errors after upgrading to 2.6.31.2 >> like this one: >> >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> >> I am using ocfs2 on top of drbd on top of LVM in a KVM guest that uses >> virtio_blk. >&g...

...sed in replies. The second time there were no reactions. The patch seems to work for Massimo... Massimo Cetra wrote: > Massimo Cetra ha scritto: >> Hello all, >> >> i ended up with some thiusands of errors after upgrading to 2.6.31.2 >> like this one: >> >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> end_request: I/O error, dev vda, sector 0 >> >> I am using ocfs2 on top of drbd on top of LVM in a KVM guest that uses >> virtio_blk. >&g...

...opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11242760 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11435969, high=0, low=11435969, sector=11435968 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11435968 hda: dma_intr:...

...d using the partitionted 30GB. The hard drive worked fine for about 2 weeks. Then the following errors occurred: ----------------- Oct 26 04:02:37 lynx kernel: EXT3-fs error (device ide1(22,2)): ext3_get_inode_loc: unable to read inode block - inode=32769 , block=65541 Oct 26 04:02:37 lynx kernel: end_request: I/O error, dev 16:02 (hdc), sector 0 Oct 26 04:02:37 lynx kernel: end_request: I/O error, dev 16:02 (hdc), sector 1048616 Oct 26 04:02:37 lynx kernel: EXT3-fs error (device ide1(22,2)): ext3_get_inode_loc: unable to read inode block - inode=65537 , block=131077 Oct 26 04:02:37 lynx kernel: end_req...

Good day. I''m getting this error: [101017.440858] blkfront: barrier: empty write xvda op failed [101017.440862] blkfront: xvda: barrier or flush: disabled [101017.463438] end_request: I/O error, dev xvda, sector 3676376 [101017.463452] end_request: I/O error, dev xvda, sector 3676376 [101017.463459] Buffer I/O error on device xvda1, logical block 459291 [101017.463464] lost page write due to I/O error on xvda1 It happens in every linux 3.1 rc since rc2 during boot (may be in 3...

...deletions(-) diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c index c483482185b6..eadaea6eb8e2 100644 --- a/fs/fuse/virtio_fs.c +++ b/fs/fuse/virtio_fs.c @@ -208,7 +208,6 @@ static void virtio_fs_free_devs(struct virtio_fs *fs) if (!fsvq->fud) continue; - /* TODO need to quiesce/end_requests/decrement dev_count */ fuse_dev_free(fsvq->fud); fsvq->fud = NULL; } @@ -1022,7 +1021,6 @@ static int virtio_fs_fill_super(struct super_block *sb) if (i == VQ_REQUEST) continue; /* already initialized */ fuse_dev_install(fsvq->fud, fc); - atomic_inc(&fc->dev_coun...

...available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. md: using 128k window, over a total of 2096384 blocks. md: md0: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sda2 disk 1, wo:0, o:1, dev:sdb2 sd 0:0:0:0: SCSI error: return code = 0x06000000 end_request: I/O error, dev sda, sector 451792231 raid1: sda1: rescheduling sector 451792168 sd 0:0:0:0: SCSI error: return code = 0x06000000 end_request: I/O error, dev sda, sector 451792263 raid1: sda1: rescheduling sector 451792200 raid1: sdb1: redirecting sector 451792168 to another mirror raid1: sdb1: red...

...[121567.210133]         6a 7a 72 bf Mar  9 23:57:43 ftp2 kernel: [121567.210140] sd 6:0:0:0: [sdc]  Add. Sense: No additional sense information Mar  9 23:57:43 ftp2 kernel: [121567.210146] sd 6:0:0:0: [sdc] CDB: Write(10): 2a 00 6a 7a 72 bf 00 00 80 00 Mar  9 23:57:43 ftp2 kernel: [121567.210159] end_request: I/O error, dev sdc, sector 1786409663 Mar  9 23:57:43 ftp2 kernel: [121567.210177] sd 6:0:0:0: rejecting I/O to offline device Mar  9 23:57:43 ftp2 kernel: [121567.210186] sd 6:0:0:0: rejecting I/O to offline device Mar  9 23:57:43 ftp2 kernel: [121567.210201] sd 6:0:0:0: rejecting I/O to offline...

...d the host system >> remotely restarted. > > fsck's not good at finding disk errors, it finds filesystem errors. If not fsck then what? > > If it was a real disk issue, you'd expect matching errors in the host > logs. Yes, there are: Mar 9 09:14:13 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:30 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:48 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 I am running an extended SMART test on the drive at the moment. I suspect that the drive is p...

...sde1 /mnt/seagate1 ext3 rw,user,noexec 0 0 /dev/sde2 /mnt/seagate2 ext3 rw,user,noexec 0 0 I copied some data onto /dev/sde1 and went to bed. This morning, I found a clump of kernel messages on the console (lightly edited from /var/log/messages): kernel: end_request: I/O error, dev sde, sector 492896319 kernel: Buffer I/O error on device sde1, logical block 61612032 kernel: EXT3-fs error (device sde1): ext3_readdir: directory #30801921 contains a hole at offset 0 kernel: Aborting journal on device sde1. kernel: end_request: I/O error, dev sde, sector 12655 ke...

...July 4th. > > Yes, 4.9.34 was failing too. And this was actually the worst case, with > I/O error on guest: > > Jul 16 06:01:03 dom0 kernel: [452360.743312] CPU: 0 PID: 28450 Comm: > 12.xvda3-0 Tainted: G O 4.9.34-29.el6.x86_64 #1 > Jul 16 06:01:03 guest kernel: end_request: I/O error, dev xvda3, sector > 9200640 > Jul 16 06:01:03 dom0 kernel: [452360.758931] SLUB: Unable to allocate > memory on node -1, gfp=0x2000000(GFP_NOWAIT) > Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical > block 1150080 > Jul 16 06:01:03 guest kernel:...

...It was moved to the stable repo on July 4th. Yes, 4.9.34 was failing too. And this was actually the worst case, with I/O error on guest: Jul 16 06:01:03 dom0 kernel: [452360.743312] CPU: 0 PID: 28450 Comm: 12.xvda3-0 Tainted: G O 4.9.34-29.el6.x86_64 #1 Jul 16 06:01:03 guest kernel: end_request: I/O error, dev xvda3, sector 9200640 Jul 16 06:01:03 dom0 kernel: [452360.758931] SLUB: Unable to allocate memory on node -1, gfp=0x2000000(GFP_NOWAIT) Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical block 1150080 Jul 16 06:01:03 guest kernel: lost page write due to I/O err...

Hi, I''m running Xen on a Debian Xeon E3110 using the Debian 2.6.26-2-xen kernel. As filesystem for my lvm domU partitions I choosed xfs. I get the following error in kern.log of domU when booting a domU: blkfront: sda2: write barrier op failed blkfront: sda2: barriers disabled end_request: I/O error, dev sda2, sector 0 end_request: I/O error, dev sda2, sector 0 Filesystem "sda2": Disabling barriers, trial barrier write failed Has anybody an idea how to resolve this? Thanks a lot Alexander Maringer _______________________________________________ Xen-users mailing lis...