All of lore.kernel.org
 help / color / mirror / Atom feed
From: maarten van den Berg <maarten@vbvb.nl>
To: linux-raid@vger.kernel.org
Subject: two-disk-failure question
Date: Fri, 17 Oct 2003 23:15:56 +0200	[thread overview]
Message-ID: <200310172315.56815.maarten@vbvb.nl> (raw)


Hi List,

I've a problem which unfortunately hit me yesterday.  I have the dreaded 
"two-disk-failure" on a 6 disk raid5 volume.  I read the fine howto chapter 
6.1 at unthought.net and before I start (with somewhat shaking hands... ;-| ) 
I need some clearing up of an issue / question...

Quote:

"To get this to work, you'll need to have an up to date /etc/raidtab - if it 
doesn't EXACTLY match devices and ordering of the original disks this will 
not work as expected, but will most likely completely obliterate whatever 
data you used to have on your disks."

Now I can't be completely absolutely sure I did not -at some point- re-order 
cables and such. So my obvious question is:  Is this step (mkraid --force 
with one of the offline disks defined as failed-disk) destructive, or could I 
(theoretically) experiment endlessly with the order in which the disks are 
defined in /etc/raidtab before I decide to mount it read-write and raidhotadd 
a fresh disk ?

Second question, If one is sufficiently adept at looking at raw disk 
structures (notably the suberblocks), can a human find out which disk is 
which, ie. in which order they DO belong ?

Thanks for any and all help regarding this. I have 400 Gigs at stake here...
:-(

Maarten 

-- 
Yes of course I'm sure it's the red cable. I guarante[^%!/+)F#0c|'NO CARRIER

             reply	other threads:[~2003-10-17 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 21:15 maarten van den Berg [this message]
2003-10-22 16:55 ` two-disk-failure question Ryan B. Lynch

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=200310172315.56815.maarten@vbvb.nl \
    --to=maarten@vbvb.nl \
    --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.