All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Coffman <tony@emitony.com>
To: linux-raid@vger.kernel.org
Subject: Device naming and raid1
Date: Tue, 26 Aug 2008 11:32:54 -0400	[thread overview]
Message-ID: <48B42226.3020702@emitony.com> (raw)

I've have a Centos5 box running a software raid-1 set on a pair of SATA
drives.

The SATA controller or driver has a flaw.
Every 150 days or so, one of the two drives will experience errors and fail.

Subsequent tests always show the drive and cable to be ok.  We bought a
couple of replacement drives before we figured that out :-(

On the last event this weekend, I went searching for a way to get the
raid back online with no host downtime.  I found the technique that
deletes the drive and then brings it back online with a bus scan using
the /sys filesystem delete and rescan entities.

I didn't realize that you could also perform a rescan on a single LUN. 
I'll have to use that next time.

My question - since I've done a delete/rescan bus operation, my device
name and major,minor numbers have changed.

Original
[0:0:0:0]    disk    ATA      ST3250410AS      3.AA  /dev/sdc

Current
[0:0:0:0]    disk    ATA      ST3250410AS      3.AA  /dev/sdc

If I re-add the device to the raid set using the new device name, will
it cause any problems on the next boot?

The drive appears to be fine.  I can read all blocks with no errors. 
Partition table looks ok, etc..

In the future if I rescan just the single LUN, I'm pretty sure I won't
run into again this but I'd like to avoid an outage on this event if
possible.

Thanks and regards,
--Tony


             reply	other threads:[~2008-08-26 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 15:32 Tony Coffman [this message]
2008-08-27 11:11 ` Device naming and raid1 David Lethe
2008-08-27 13:21   ` Tony Coffman
2008-08-27 13:31     ` Sujit Karataparambil
2008-08-27 14:08       ` Sujit Karataparambil
2008-08-27 14:46         ` David Greaves
2008-08-27 14:48         ` Tony Coffman
2008-08-27 13:42     ` Steve Fairbairn

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=48B42226.3020702@emitony.com \
    --to=tony@emitony.com \
    --cc=linux-raid@vger.kernel.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.