From: Reuben Farrelly <reuben-lkml@reub.net>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Weird RAID/SATA problem [ once was Re: 2.6.17-mm3 ]
Date: Sat, 01 Jul 2006 23:38:31 +1200 [thread overview]
Message-ID: <44A65EB7.5020201@reub.net> (raw)
In-Reply-To: <17574.21399.979888.127483@cse.unsw.edu.au>
On 1/07/2006 10:51 p.m., Neil Brown wrote:
> On Saturday July 1, reuben-lkml@reub.net 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
next prev parent reply other threads:[~2006-07-01 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060630105401.2dc1d3f3.akpm@osdl.org>
[not found] ` <44A5C1D5.20200@reub.net>
[not found] ` <17573.50871.307879.557218@cse.unsw.edu.au>
[not found] ` <44A5D079.6070505@reub.net>
[not found] ` <17573.55937.866300.638738@cse.unsw.edu.au>
[not found] ` <44A6390E.1030608@reub.net>
[not found] ` <17574.15295.828980.278323@cse.unsw.edu.au>
[not found] ` <44A64BD8.90906@reub.net>
2006-07-01 10:51 ` Weird RAID/SATA problem [ once was Re: 2.6.17-mm3 ] Neil Brown
2006-07-01 11:38 ` Reuben Farrelly [this message]
2006-07-01 12:05 ` Neil Brown
2006-07-01 12:24 ` Reuben Farrelly
2006-07-01 13:28 ` Neil Brown
2006-07-02 0:03 ` Reuben Farrelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A65EB7.5020201@reub.net \
--to=reuben-lkml@reub.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.