[DRBD-user] Read error=-5.

Ben Timby btimby at gmail.com
Mon May 3 21:39:38 CEST 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


I have DRBD 8.3.7 Installed ON CentOS 5.4 x86_64. My setup is fairly
complex, I have 15 SATA disk drives in a software RAID 5, This array
exceeds the maximum volume size for DRBD, so I used LVM2 to cut it in
half. This results in having two DRBD resources (10.4TB each) on top
of two logical volumes. On top of these I then have two more LVM2
volume groups and finally two more logical volumes. I am running EXT4
on top of the logical volumes.

EXT4
   |
LVM2
   |
DRBD
   |
LVM2
   |
RAID
   |
SATA

I have been receiving the following errors from DRBD. They are NOT
accompanied by any other errors from the underlying RAID or SATA
systems.

--
May  2 06:02:08 ragoon6 kernel: block drbd0: p read: error=-5
May  2 06:02:08 ragoon6 kernel: block drbd0: Local READ failed
sec=4211072s size=4096
May  2 06:02:08 ragoon6 kernel: block drbd0: disk( UpToDate -> Failed )
May  2 06:02:08 ragoon6 kernel: block drbd0: Local IO failed in
__req_mod.Detaching...
May  2 06:02:08 ragoon6 kernel: block drbd0: disk( Failed -> Diskless )
May  2 06:02:08 ragoon6 kernel: block drbd0: Notified peer that my
disk is broken.
May  2 06:02:09 ragoon6 kernel: block drbd0: 954 messages suppressed
in /usr/src/redhat/BUILD/drbd-8.3.7/drbd/drbd_req.c:131.
May  2 06:02:09 ragoon6 kernel: block drbd0: Should have called
drbd_al_complete_io(, 138163712), but my Disk seems to have failed :(
May  2 06:02:09 ragoon6 kernel: block drbd0: Should have called
drbd_al_complete_io(, 138163720), but my Disk seems to have failed :(
--

--
May  2 06:37:41 ragoon6 kernel: block drbd1: p read: error=-5
May  2 06:37:41 ragoon6 kernel: block drbd1: Local READ failed
sec=37749432s size=4096
May  2 06:37:41 ragoon6 kernel: block drbd1: disk( UpToDate -> Failed )
May  2 06:37:41 ragoon6 kernel: block drbd1: Local IO failed in
__req_mod.Detaching...
May  2 06:37:41 ragoon6 kernel: block drbd1: disk( Failed -> Diskless )
May  2 06:37:41 ragoon6 kernel: block drbd1: Notified peer that my
disk is broken.
May  2 06:37:42 ragoon6 kernel: block drbd1: Should have called
drbd_al_complete_io(, 11421405240), but my Disk seems to have failed
:(
May  2 06:37:42 ragoon6 kernel: block drbd1: Should have called
drbd_al_complete_io(, 11421405248), but my Disk seems to have failed
:(
May  2 06:37:42 ragoon6 kernel: block drbd1: Should have called
drbd_al_complete_io(, 11421405256), but my Disk seems to have failed
:(
--

I have found out that -5 is EIO. How can I track these errors down and
resolve them?
My assumption is that a read error originating in SATA/RAID system
would be reported by that system as well as by DRBD. Any suggestions
on fixing this?



More information about the drbd-user mailing list