From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: emergency recovery
Date: Thu, 10 Apr 2008 08:38:54 +0200 [thread overview]
Message-ID: <ftkclu$t6f$1@ger.gmane.org> (raw)
In-Reply-To: 51c8a7be0804092329i3353055ai6216dc0e6b4066ea@mail.gmail.com
jeff sacksteder <jsacksteder@gmail.com> wrote:
> It is essential that I not make this worse than it is. Is the
Well, this in mind the first thing you should do is taking raw images
from all the component drives before even thinking about any kind of
recovery. Just to make sure you have more than one try when something
goes wrong.
regards
Mario
--
The social dynamics of the net are a direct consequence of the fact that
nobody has yet developed a Remote Strangulation Protocol. -- Larry Wall
next prev parent reply other threads:[~2008-04-10 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 6:29 emergency recovery jeff sacksteder
2008-04-10 6:38 ` Mario 'BitKoenig' Holbe [this message]
2008-04-10 13:08 ` john
2008-04-10 13:17 ` Mario 'BitKoenig' Holbe
2008-04-10 16:09 ` john
2008-04-10 23:13 ` jeff sacksteder
2008-04-10 23:45 ` jeff sacksteder
2008-04-11 14:35 ` Bill Davidsen
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='ftkclu$t6f$1@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).