linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 0, disks swapped ?
Date: Fri, 17 Oct 2008 16:05:53 +0200	[thread overview]
Message-ID: <gda641$spp$2@ger.gmane.org> (raw)
In-Reply-To: 200810171548.59686.c.baegert-listes@lixium.fr

c.baegert-listes@lixium.fr <c.baegert-listes@lixium.fr> wrote:
> older. The good point of the RAID 1+0 solution is that I just have to repair 
> a raid0 array now. But how ?

That's most likely gone - at least your data is most likely corrupted
after your reiserfsck and rebuild-tree, unless all you did did not write
to the disks (which is not very likely :)).
You could try to recreate the array in the correct order, perhaps you
can get a little back but i think its time to consult your backups,
alone to find out what's corrupted and what's not.


regards
   Mario
-- 
Damit das Mögliche entsteht, muß immer wieder das Unmögliche versucht werden.
                                                  -- Hermann Hesse

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-17 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 11:18 RAID 0, disks swapped ? c.baegert-listes
2008-10-17 12:36 ` Mario 'BitKoenig' Holbe
2008-10-17 13:57   ` c.baegert-listes
2008-10-17 14:01     ` Mario 'BitKoenig' Holbe
2008-10-17 14:07       ` c.baegert-listes
2008-10-17 13:18 ` Bill Davidsen
2008-10-17 13:48   ` c.baegert-listes
2008-10-17 14:05     ` Mario 'BitKoenig' Holbe [this message]
2008-10-17 14:34       ` c.baegert-listes
2008-10-17 17:44         ` Mario 'BitKoenig' Holbe

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='gda641$spp$2@ger.gmane.org' \
    --to=mario.holbe@tu-ilmenau.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).