On 1/07/2006 10:51 p.m., Neil Brown wrote:
On Saturday July 1, [email protected] wrote:
md: super_written gets error=-5, uptodate=0
messages on the console that didn't seem to want to stop...
'5' == EIO
We try to write the superblock and we get EIO - something wrong somewhere.
What sort of device are we writing to here? What controller, what
driver (if you know), what drives?
The two raid-1 disks are the Seagate ST380817AS SATA disks on the onboard
controller. The motherboard is an Intel D945GNT motherboard. See dmesg..
Can you write to the device without using md?
Yes.
So... When md writes a superblock to this device, it reliably (or
close to reliably) gets EIO. When mkfs writes, it works fine.
Only difference I can think of is still barriers... Does this patch
make any difference?
You will be happy to know that yes, it does make a difference.
Applied to -mm4, RAID-1 now comes up with all arrays in sync and everything
looking good. Tried it twice, and both times raid-1 came up perfectly with
md0 : active raid1 sdc2[1] sda2[0]
24410688 blocks [2/2] [UU]
bitmap: 0/187 pages [0KB], 64KB chunk
for each md.
reuben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
