linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Mark A. O'Neil" <mark.a.oneil@Dartmouth.EDU>,
	linux-raid@vger.kernel.org
Subject: Re: Recovery of software RAID5 using FC6 rescue?
Date: Wed, 09 May 2007 20:50:44 +0100	[thread overview]
Message-ID: <87odktydwr.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <4641B1DA.7030607@msgid.tls.msk.ru> (Michael Tokarev's message of "Wed, 09 May 2007 15:34:50 +0400")

On 9 May 2007, Michael Tokarev spake thusly:
> Nix wrote:
>> On 8 May 2007, Michael Tokarev told this:
>>> BTW, for such recovery purposes, I use initrd (initramfs really, but
>>> does not matter) with a normal (but tiny) set of commands inside,
>>> thanks to busybox.  So everything can be done without any help from
>>> external "recovery CD".  Very handy at times, especially since all
>>> the network drivers are here on the initramfs too, so I can even
>>> start a netcat server while in initramfs, and perform recovery from
>>> remote system... ;)
>> 
>> What you should probably do is drop into the shell that's being used to
>> run init if mount fails (or, more generally, if after mount runs it
>
> That's exactly what my initscript does ;)

I thought so. I was really talking to Mark, I suppose.

> chk() {
>   while ! "$@"; do
>     warn "the following command failed:"
>     warn "$*"
>     p="** Continue(Ignore)/Shell/Retry (C/s/r)? "

Wow. Feature-rich :)) I may reused this rather nifty stuff.

>> hasn't ended up mounting anything: there's no need to rely on mount's
>> success/failure status). [...]
>
> Well, so far exitcode has been reliable.

I guess I was being paranoid because I'm using busybox and at various
times the exitcodes of its internal commands have been... unimplemented
or unreliable.

-- 
`In the future, company names will be a 32-character hex string.'
  --- Bruce Schneier on the shortage of company names

  reply	other threads:[~2007-05-09 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 12:27 Linux MD Raid Bug(?) w/Kernel sync_speed_min Option Justin Piszcz
2007-05-08 13:03 ` Neil Brown
2007-05-08 13:13   ` Justin Piszcz
2007-05-08 13:24   ` Justin Piszcz
2007-05-09  9:13     ` Neil Brown
2007-05-08 17:24   ` Recovery of software RAID5 using FC6 rescue? Mark A. O'Neil
2007-05-08 20:04     ` Michael Tokarev
2007-05-09  6:29       ` Nix
2007-05-09 11:34         ` Michael Tokarev
2007-05-09 19:50           ` Nix [this message]
2007-05-16 16:10             ` Mark A. O'Neil

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=87odktydwr.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mark.a.oneil@Dartmouth.EDU \
    --cc=mjt@tls.msk.ru \
    /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).