From: Maarten v d Berg <maarten@vbvb.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Recovering RAID5 array
Date: Tue, 20 Jan 2004 13:10:48 +0100 [thread overview]
Message-ID: <200401201310.48900.maarten@vbvb.nl> (raw)
In-Reply-To: <400D05AC.4030409@upfrontsystems.co.za>
On Tuesday 20 January 2004 11:40, Jean Jordaan wrote:
> Neil,
>
> thank you very much for your help ..
>
> > mdadm -C /dev/md0 -l 5 -n 3 /dev/hda3 missing /dev/hdc3
>
> Did that, once with 'missing' in each place. All I get:
>
> cdimage root # mdadm --create /dev/md0 --raid-devices=3 --level=5
> --spare-devices=0 --chunk=64 missing /dev/hdb3 /dev/hdc3
> mdadm: /dev/hdb3 appears to be part of a raid array:
> level=5 devices=3 ctime=Tue Jan 20 10:35:45 2004
> mdadm: /dev/hdc3 appears to be part of a raid array:
> level=5 devices=3 ctime=Tue Jan 20 10:09:43 2004
> Continue creating array? y
> mdadm: array /dev/md0 started.
> cdimage root # mount -r -t reiserfs /dev/md0 /mnt/gentoo/raid/
> mount: Not a directory
Note that it says "Not a directory". Not something like "can't read
superblock" or "is not a valid block device" or similar errors which would
indicate an error with the md array.
So, maybe mount is right and /mnt/gentoo/raid/ IS actually wrong...?
Furthermore, you're not realizing that reiserfs will try to replay its
transactions when you attempt a mount, even if mounting RO afaik.
So maybe more prudent would be a reiserfsck --check...
Maarten
next prev parent reply other threads:[~2004-01-20 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 6:54 Recovering RAID5 array Jean Jordaan
2004-01-20 6:59 ` Neil Brown
2004-01-20 7:17 ` Jean Jordaan
2004-01-20 8:08 ` Jean Jordaan
2004-01-20 9:59 ` Neil Brown
2004-01-20 10:40 ` Jean Jordaan
2004-01-20 12:10 ` Maarten v d Berg [this message]
2004-01-20 12:23 ` Jean Jordaan
2004-01-20 12:57 ` Maarten v d Berg
2004-01-20 13:28 ` Jean Jordaan
2004-01-20 10:44 ` Jean Jordaan
2004-01-20 7:22 ` Guy
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=200401201310.48900.maarten@vbvb.nl \
--to=maarten@vbvb.nl \
--cc=linux-raid@vger.kernel.org \
--cc=maarten@nebula.vbvb.nl \
/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).