All of lore.kernel.org
 help / color / mirror / Atom feed
From: andy liebman <andyliebman@aol.com>
To: linux-raid@vger.kernel.org
Subject: Simulating Drive Failure on Mirrored OS drive
Date: Sun, 01 Oct 2006 19:55:07 -0400	[thread overview]
Message-ID: <4520555B.4080000@aol.com> (raw)

Various documents on Mirrored OS Drives suggest you can simulate the 
failure of one of your mirrored pairs by marking one or more partitions 
as "failed" with mdadm.

Indeed when I mark a drive as "failed", if I have the mdadm monitoring 
daemon running, I get an email warning me that my RAIDS are degraded.

Also, I can reboot with only one drive plugged in and the OS comes up 
fine (albeit degraded).

This gives me a REASONABLE degree of confidence that the Mirrored 
Partitions will continue working okay if one drive should fail. However, 
I would like to run a more definitive test.

I tried simply unplugging one drive from its power and from its SATA 
connector. The OS didn't like that at all. My KDE session kept running, 
but I could no longer open any new terminals. I couldn't become root in 
an existing terminal that was already running. And I couldn't SSH into 
the machine.

It was like I had an OS running on only a 1/4th of a cylinder. I 
couldn't even make the OS cleanly shutdown or reboot.

I know that simply unplugging a drive is not the same as a drive failing 
or timing out. But is there a more realistic way to simulate a failure 
so that I can know that the mirror will work when it's needed?

Andy Liebman

             reply	other threads:[~2006-10-01 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 23:55 andy liebman [this message]
2006-10-02  8:02 ` Simulating Drive Failure on Mirrored OS drive David Greaves
2006-10-02 17:54   ` andy liebman
2006-10-02 20:20     ` Michael Tokarev

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=4520555B.4080000@aol.com \
    --to=andyliebman@aol.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.