From: Tyler <pml@dtbb.net>
To: Jonathan Schmidt <jon@impact-ltd.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: raidreconf error (bug)
Date: Sun, 18 Sep 2005 02:12:09 -0700 [thread overview]
Message-ID: <432D2F69.2010007@dtbb.net> (raw)
In-Reply-To: <dgg0la$jlr$1@sea.gmane.org>
Jonathan Schmidt wrote:
>I just thought I'd let everyone know that the problem has been solved by
>reversing the old and new raidtab files in the command line to raidreconf
>(after fixing the bug that causes the immediate abort).
>
>The old 4-disk array is currently running with the filesystem intact. I'll
>go about backing it up now :)
>
>"Jonathan Schmidt" <jon@impact-ltd.ca> wrote in message
>news:dgckbo$her$1@sea.gmane.org...
>
>
>>I just attempted to add a 5th 80GB disk to my RAID-5 array using
>>raidreconf. I previously added a 4th disk 6 months ago using the identical
>>tools with no errors or hiccups whatsoever. Back then, I made a full
>>backup because of all the warnings. This time, I assumed it would work
>>since it did last time, and did not backup the data. You can see where
>>this is going...
>>
>>Here's some of the relevant info:
>>....
>>
>>
>
>
>
>-
>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
>
>
Sweet.. :) I learn something new every day or every week on this list :D
I bet you are feeling like you tempted fate and won this round aren't
you? :P
Regards,
Tyler.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.1/104 - Release Date: 9/16/2005
next prev parent reply other threads:[~2005-09-18 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:08 raidreconf error (bug) Jonathan Schmidt
2005-09-17 2:56 ` Jonathan Schmidt
2005-09-18 9:12 ` Tyler [this message]
2005-09-18 17:43 ` Jonathan Schmidt
2005-09-18 9:20 ` Tyler
2005-09-18 17:47 ` Jonathan Schmidt
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=432D2F69.2010007@dtbb.net \
--to=pml@dtbb.net \
--cc=jon@impact-ltd.ca \
--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).