similar to: Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

Hi List, What this means? md: syncing RAID array md0 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum 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:

I'm backing up to a NTFS partition on an external USB drive with dump. I'm seeing failures in /var/log/messages reading sector 0xFFFFFFF that cause the verify pass to fail. Are there any known problems in the USB driver? Kernel via uname -a: Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 i686 i686 i386 GNU/Linux Message reported. (Note the number 268435455,

I'm backing up to a NTFS partition on an external USB drive with dump. I'm seeing failures in /var/log/messages reading sector 0xFFFFFFF that cause the verify pass to fail. Are there any known problems in the USB driver? Kernel via uname -a: Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 i686 i686 i386 GNU/Linux Message reported. (Note the number 268435455,

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

Hi, the problem I am reporting relates to RH Linux 6.0 I have successfully mounted a disk from a windows NT server machine, using smbmount as follows: $ smbmount //machine/service -c 'mount /mnt/NTgroups -u local_owner' -U remote_username and everything looked fine. Now I have just noticed that when "touching" or creating files everything behaves strangely, that is the date is

I just tried this with CentOS 5.3 as well, and got exactly the same symptoms and dmesg output. (As a point of comparison, Ubunu 8.04 on my work laptop is able to access the drive.) Obviously "not detected" is a misapprehension, though I'm puzzled why "lsusb" doesn't show it. The device is there even though the partition table can't be read. ---------- Forwarded

I have an Athlon with about 10 HDDs plugged in, primarily to do Disk2Disk backups. Some drives are PATA, some are SATA, some are USB. A strange concoction, but it's been relatively stable for some 4-5 years, despite numerous upgrades and so on. It's been running CentOS 4 for a long, long time. (years) Recently, I've started to have problems with its stability, and after 2 weeks

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-) hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady

I am running RH 7.3 with kernel 2.4.18-27.7.x. Recently I have added a new 60GB Quantum IDE hard drive to the server. I have set it up as a MASTER on a separate IDE channel. Two partitions on the /dev/hdc are /dev/hdc1, /dev/hdc2 - both using ext3. For more detailed HDD parameters, this is 'hdparm -i /dev/hdc': ----------------- /dev/hdc: Model=IC35L060AVV207-0, FwRev=V22OA66A,

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O

http://bugs.freedesktop.org/show_bug.cgi?id=16033 Summary: [Randr12] DPI calculation ludicrously incorrect Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Dear Massimo, It seems straightforward to use weighted.mean() in a dplyr context library(dplyr) mydf %>% group_by(date_time, type) %>% summarise(vel = weighted.mean(speed, n_vehicles)) Best regards, ir. Thierry Onkelinx Statisticus / Statistician Vlaamse Overheid / Government of Flanders INSTITUUT VOOR NATUUR- EN BOSONDERZOEK / RESEARCH INSTITUTE FOR NATURE AND FOREST Team