From: NeilBrown <neilb@suse.de>
To: Steve Carlson <stevengcarlson@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 partition set to spare
Date: Sun, 15 Jan 2012 16:18:31 +1100 [thread overview]
Message-ID: <20120115161831.6e46f413@notabene.brown> (raw)
In-Reply-To: <CA+q4O7NjK6Aj3Djs2g+qPu69=knOKvu9=wFy-YLdmw4Fi3k2Gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
On Sat, 14 Jan 2012 15:42:58 -0600 Steve Carlson <stevengcarlson@gmail.com>
wrote:
> On Sat, Dec 31, 2011 at 5:37 PM, Steve Carlson <stevengcarlson@gmail.com> wrote:
> >> On Sat, Dec 31, 2011 at 4:08 AM, Jes Sorensen wrote:
> >> Hi Steve,
> >>
> >> What I meant here is that I would like to see the dmesg output at this
> >> point, to see if there were any read errors reported during the assembly.
> >>
> >>> I also ran extended self tests just to be thorough, and they both came
> >>> back error free. I'm unsure as to whether that puts them in the clear
> >>> for bad sectors though.
> >>
> >> There were read errors in the dmesg output you posted earlier, which is
> >> why I am wary of it.
> >>
> >> Cheers,
> >> Jes
> >
> > Jes,
> >
> > This is /var/log/messages from boot to stopping and reassembling md2.
> > I think this is what you wanted, I'm not sure what more I can give
> > you.
> > http://dl.dropbox.com/u/2776371/raid/mdadm_stop_dmesg_c_mdadm_assemble_var_log_message.txt
> >
> > -Steve
>
>
>
> Hi all,
>
> This is still unresolved. What else could I try short of breaking and
> rebuilding the array?
I don't know how the array could have got in this state. IO errors on a
RAID0 don't mark the devices as faulty.
You would have to explicitly
mdadm /dev/md2 --fail /dev/sdb3
or something like that - and I doubt you did that.
Anyway:
mdadm -S /dev/md2
mdadm -C /dev/md2 -e 0.90 -c 64 -l 0 -n 2 /dev/sda3 /dev/sdb3
should get you going again. All the data should be there except for anything
that the hard drive has decided to keep for itself.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-01-15 5:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 8:21 RAID0 partition set to spare Steve Carlson
2011-12-30 10:58 ` Jes Sorensen
2011-12-31 3:03 ` Steve Carlson
2011-12-31 10:08 ` Jes Sorensen
2011-12-31 23:37 ` Steve Carlson
[not found] ` <CALFpzo6tUc1UrvJj9T1cWtgNyVjBHP89qnZPq8r_9Qz-m=eWog@mail.gmail.com>
2012-01-01 3:44 ` Marcus Sorensen
2012-01-14 21:42 ` Steve Carlson
2012-01-15 5:18 ` NeilBrown [this message]
2012-01-16 8:04 ` Steve Carlson
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=20120115161831.6e46f413@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=stevengcarlson@gmail.com \
/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.