From: David Greaves <david@dgreaves.com>
To: Mitchell Laks <mlaks@verizon.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: disaster. raid1 drive failure rsync=DELAYED why?? please help
Date: Mon, 14 Mar 2005 09:49:09 +0000 [thread overview]
Message-ID: <42355E15.8060109@dgreaves.com> (raw)
In-Reply-To: <200503140243.25308.mlaks@verizon.net>
Mitchell Laks wrote:
>On Sunday 13 March 2005 10:49 am, David Greave wrote: Many Helpful remarks:
>
>
>David I am grateful that you were there for me.
>
>
No probs - we've all been there!
>My assessment (correct me if I am wrong) is that I have to rethink my
>architecture. As I continue to work with software raid, I likely will have to
>move the postgresql database to a separate partition, so I will not have
>mixing of points of failure.
>
Well, once things are calmer, post your layout and new thinking and I'm
sure people will input.
Amongst other things, mdadm can allow you to keep 1 or more hot spares
in a system that you can 'share' between multiple raid1 mirrors.
This kind of trick (learnt by hanging out here) may be the answer to
muliple failures.
David
PS don't forget the mdadm upgrade.
next prev parent reply other threads:[~2005-03-14 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 4:51 disaster. raid1 drive failure rsync=DELAYED why?? please help Mitchell Laks
2005-03-13 9:49 ` David Greaves
2005-03-13 14:32 ` Mitchell Laks
2005-03-13 15:23 ` David Greaves
2005-03-13 15:49 ` David Greaves
2005-03-14 7:43 ` Mitchell Laks
2005-03-14 9:49 ` David Greaves [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 6:23 Mitchell Laks
2005-03-13 6:45 ` Mitchell Laks
2005-03-13 7:22 Mitchell Laks
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=42355E15.8060109@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=mlaks@verizon.net \
/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).