From: "Matthew (RAID)" <RAID@lists.elvey.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Help; question follow-up.
Date: Mon, 12 Jul 2004 16:11:09 -0700 [thread overview]
Message-ID: <1089673869.14408.200223035@webmail.messagingengine.com> (raw)
Apropos
http://marc.theaimsgroup.com/?l=linux-raid&m=108932298006669&w=2
- my first post - Subject:(Can I mark a RAID 1 drive as old? Move it?
SCA hangs) Troubles creating a reliable backup system.
Was my post OT? Too long? Confusing? (Or just no one here felt like
volunteering to answer it?)
Just thought I'd ask before posting to, e.g. news:...linux...hardware.
In brief, the problems I'd love help with (from the Subject) are 3:
Can I mark a RAID 1 drive as old?
(I.e. not 'failed', but rather old, as in older than the other drive(s)
in the raid1 array it's in.)
Move it? I.e. how can I move a drive in a raid array from one drive bay
to another and have the resulting drive letter change not be a problem?
Why is the system failing when I put a drive into the system?
Details in original email at the URL above.
Thinking about buying the O'Reilly RAID book, though I doubt it'll
answer these off-the-beaten-path questions.
--
Mr. Elvey (<firstname>@<lastname>.com)
Ignore me. What follows is a test.
Wondering if the text below triggered the keyword filter (pre- s/v/u) in
my last post:
(Yes, my post appeared twice - wasn't my fault - majordomo rejected my
svbscription confirmation, and I didn't notice until I'd posted. Then
it accepted when I tried again, and I posted again, assuming it wouldn't
accept the post of a non-svbscriber. It accepted both posts, but only
belatedly (or the moderator approved one) Majordomo requires the
confirmation be sent from the svbscriber's address, which is silly; it
has the approval code in it.)
reply other threads:[~2004-07-12 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1089673869.14408.200223035@webmail.messagingengine.com \
--to=raid@lists.elvey.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.