All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vanhorn, Mike" <michael.vanhorn@wright.edu>
To: Phil Turmel <philip@turmel.org>, Mike VanHorn <mr_vanhorn@yahoo.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: multiple disk failures in an md raid6 array
Date: Thu, 11 Apr 2013 20:48:42 +0000	[thread overview]
Message-ID: <CD8C97E6.4113A%michael.vanhorn@wright.edu> (raw)
In-Reply-To: <51671EC0.9000707@turmel.org>

>>
>>
>>
>>Also, Microsoft's mail server from whence my message was
>> originating has been blacklisted on your server, so I am
>> sending this to you from my personal account on Yahoo!.
>
>You really need to fix your server, then, or just use this yahoo
>account for linux-raid.  My server just uses standard SPF validation
>and common dns blacklists.

Well, I have no control over that, as the University is a Microsoft
customer, but it appears it's been cleared up now because things are going
through again.

>Are you already doing weekly scrubs and drive self-tests?

Yes. I have it do a scrub by writing "check" to
/sys/block/md0/md/sync_action from cron.weekly, and I have a weekly script
that runs smart tests, too.

>Do you still have the complete dmesg from the original triple
>failure?

Unfortunately, no. I thought I kept it, but I have either misplaced the
file or just didn't do it like I thought I did.

There has been a reboot since the failure, and sde has magically come back
and seems to be okay, so the only "bad" disk is actually sdj, which was
the space.  However, see my other thread about "Odd --examine output" for
more info; I haven't been able to reassemble the array (and I should have
enough disks) because the metadata doesn't seem to be in the right place.
On /dev/sd[cdefi], there is one set of metadata (from what I believe was
an earlier rendition of the array, such that this data is now invalid) and
on /dev/sd[gh]1, there is a newer set of metadata, the dates for which
correspond with when this array was created. So, I'm thinking that the
metadata is actually on /dev/sd[cdefi]1, but I can't get to it because
those devices don't exist (such that I can't run, for example, mdadm -E
/dev/sdc1, because /dev/sdc1 doesn't exist).

As I stated in the other thread, I am very confused.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanhorn@wright.edu
http://www.cecs.wright.edu/~mvanhorn/





  reply	other threads:[~2013-04-11 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1365607598.94859.YahooMailNeo@web161904.mail.bf1.yahoo.com>
2013-04-11 20:36 ` multiple disk failures in an md raid6 array Phil Turmel
2013-04-11 20:48   ` Vanhorn, Mike [this message]
2013-04-03 13:19 Vanhorn, Mike
2013-04-03 23:33 ` Phil Turmel
2013-04-05  8:25   ` Roy Sigurd Karlsbakk
2013-04-05 12:05     ` Phil Turmel
2013-04-05 17:06       ` Roy Sigurd Karlsbakk

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=CD8C97E6.4113A%michael.vanhorn@wright.edu \
    --to=michael.vanhorn@wright.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=mr_vanhorn@yahoo.com \
    --cc=philip@turmel.org \
    /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.