search for: sdbi

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

...gy ... ... ... vw-storman2 (3600a0b80004807f80000091248da00ef) dm-0 SUN ,CSM200_R [size=20G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=6][active] \_ 3:0:1:19 sdcc 69:0 [active][ready] \_ 1:0:0:19 sdag 66:0 [active][ready] \_ round-robin 0 [prio=0][enabled] \_ 1:0:1:19 sdbi 67:192 [active][ghost] \_ 3:0:0:19 sdbh 67:176 [active][ghost] ... ... ... multipathd> A Linux fdisk command in the dom0 has the following view of the volume: carrier3:~ # fdisk -l /dev/mapper/vw-storman2 Disk /dev/mapper/vw-storman2: 21.4 GB, 21474836480 bytes 255 heads, 63 sectors/track,...

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

Greetings, Last night I manually unpresented and deleted a LUN (a SAN snapshot) that was presented to one node in a four node RAC environment running OCFS2 v1.4.1-1. The system then rebooted with the following error: Oct 21 16:45:34 ausracdb03 kernel: (27,1):o2hb_write_timeout:166 ERROR: Heartbeat write timeout to device dm-24 after 120000 milliseconds Oct 21 16:45:34 ausracdb03 kernel: