From: Michael Welsh Duggan <mwd@cert.org>
To: linux-raid@vger.kernel.org
Subject: Re: RAID reconstruction problems
Date: Tue, 02 Sep 2003 21:51:39 -0400 [thread overview]
Message-ID: <tntn0dmwses.fsf@spenser.yellow.cert.org> (raw)
In-Reply-To: 87wucrnb63.fsf@cs.cmu.edu
Sorry about putting the wrong email address on my initial email.
In reply to Donghui Wen, Yes, it was partitioned correctly.
In reply to Bernd Schubert, I have installed mdadm, and am looking
around for some pointers. I am unsure what is going on still. mdadm
reports the follownig for /dev/md1:
/dev/md1:
Version : 00.90.00
Creation Time : Sun Mar 16 21:42:44 2003
Raid Level : raid1
Array Size : 6144704 (5.86 GiB 6.29 GB)
Device Size : 6144704 (5.86 GiB 6.29 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Sep 1 19:48:11 2003
State : dirty, no-errors
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
0 3 65 0 active sync /dev/ide/host0/bus0/target1/lun0/part1
1 0 0 0 sync
2 22 1 2 active /dev/ide/host0/bus1/target0/lun0/part1
UUID : 0e953226:03c91d46:cd00d52f:83a1334e
Events : 0.413
/proc/mdstat reports the following:
md1 : active raid1 ide/host0/bus1/target0/lun0/part1[2]
ide/host0/bus0/target1/lun0/part1[0]
6144704 blocks [2/2] [U_]
I'll play around with it some more, but it anyone recognizes these
symptoms, please reply.
--
Michael Welsh Duggan
(mwd@cert.org)
next prev parent reply other threads:[~2003-09-03 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 3:04 RAID reconstruction problems Michael Welsh Duggan
2003-09-02 16:04 ` Bernd Schubert
2003-09-02 18:29 ` Donghui Wen
2003-09-03 1:51 ` Michael Welsh Duggan [this message]
2003-09-04 17:07 ` Bernd Schubert
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=tntn0dmwses.fsf@spenser.yellow.cert.org \
--to=mwd@cert.org \
--cc=linux-raid@vger.kernel.org \
--cc=mwd@sei.cmu.edu \
/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).