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:57:32 +0100 [thread overview]
Message-ID: <200401201357.32747.maarten@vbvb.nl> (raw)
In-Reply-To: <400D1DA6.80509@upfrontsystems.co.za>
On Tuesday 20 January 2004 13:23, Jean Jordaan wrote:
> Hi Maarten
>
> > So, maybe mount is right and /mnt/gentoo/raid/ IS actually wrong...?
>
> I.e. the filesystem under RAID is corrupt? This is what I'm afraid of.
Not neccessarily... just that /mnt/gentoo/raid/ is NOT a directory.
First things first. Why don't you try to mount /dev/md0 on /mnt ?
> > So maybe more prudent would be a reiserfsck --check...
>
> Oooh! Looks like something worked .. still can't mount though ..
> should I try --rebuild-tree next? :
That choice is entirely up to you. Please be well aware that such choices may
determine the fate of your data on /dev/md0...!! So better think twice.
Looking at the errors you may want to experiment with the order in which you
assembled the md device. Then you can compare the severity of the errors that
reiserfsck reports. Once you choose rebuild-tree there is NO way back.
But don't ask me, I'm no real expert on these questions. In fact, several
months ago people on this list helped me solve MY raid5 two-disk failure...
good luck
Maarten
> cdimage root # reiserfsck --check /dev/md0
>
> <-------------reiserfsck, 2003------------->
> reiserfsprogs 3.6.8
>
> [...]
> Will read-only check consistency of the filesystem on /dev/md0
> Will put log info to 'stdout'
>
> Do you want to run this program?[N/Yes] (note need to type Yes if you
> do):Yes ###########
> reiserfsck --check started at Tue Jan 20 12:19:38 2004
> ###########
> Replaying journal..
> 0 transactions replayed
> Checking internal tree../ 1 (of 2)/ 1 (of 126)/ 1 (of 153)block 8211:
> The level of the node (25938) is not correct, (1) expected
> the problem in the internal node occured (8211), whole subtree is skipped
> finished
> Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
> Bad nodes were found, Semantic pass skipped
> 1 found corruptions can be fixed only during --rebuild-tree
> ###########
> reiserfsck finished at Tue Jan 20 12:20:11 2004
> ###########
> cdimage root # mount -r -t reiserfs /dev/md0 /mnt/gentoo/raid/
> mount: Not a directory
>
> (Apologies for direct mail but speed is of the essence .. )
next prev parent reply other threads:[~2004-01-20 12:57 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
2004-01-20 12:23 ` Jean Jordaan
2004-01-20 12:57 ` Maarten v d Berg [this message]
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=200401201357.32747.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).