For people on [EMAIL PROTECTED], the context is the fact that RAID1
in the md driver uses b_rdev out of a failed I/O request to determine
the site of the failure, and if the underlying device remaps b_rdev -
as do RAID0 and LVM, it gets confused
On Friday May 19, [EMAIL PROTECTED] wrote:
>
On Fri, 19 May 2000, Neil Brown wrote:
> - md2 checks b_rdev to see which device was in error. It gets confused
> because sda12 is not part of md2.
>
> The fix probably involves making sure that b_dev really does refer to
> md0 (a quick look at the code suggests it actually refers to md2!) an
On May 19, [EMAIL PROTECTED] wrote:
> Today one of my four SCSI disks in a RAID 0/1 setup broke. The kernel
> is 2.2.15 with Ingo's raid-2.2.15-A0. The error message says
>
> md: bug in file md.c, line 485
>
> Here are some details:
(deleted)
Yep. This occurred to me only yesterday as
Today one of my four SCSI disks in a RAID 0/1 setup broke. The kernel
is 2.2.15 with Ingo's raid-2.2.15-A0. The error message says
md: bug in file md.c, line 485
Here are some details:
# cat /etc/raidtab
raiddev /dev/md0
raid-level0
nr-raid-disks 2
persistent-su
