From: Sevrin Robstad <quack@online.no>
To: linux-raid@vger.kernel.org
Subject: FIXED : brute-force my RAID 5 - just some fsck errors..
Date: Tue, 25 Jul 2006 23:39:03 +0200 [thread overview]
Message-ID: <44C68F77.6020909@online.no> (raw)
I finally got my old RAID-5 up again, after bruteforcing the setup of
it... (A Script that ran "mdadm --create --run -n 6 -l 5 /dev/md0
/dev/1-5 missing;fsck -n -f /dev/md0;mdadm --stop /dev/md0;)
The first run didn't find anything that made sense, but desperately I
ran the same script with -c xx from 4 to 256 and I finally hit jackpot
with one combo and 256kb chunksize.
Most of the RAID is fine, and I'm backing up the whole 1 terrabyte. But
there's some errors on it, fsck reports
"Illegal block #12 (xxx) in inode 95764590."
It's the same from block #12 to block #1035, and same inode.
There's also some multiply-claimed block(s) in some inodes, and some
files that share Inode's.
will fsck fix if I run it without "-n" ? Or will it just we worse ? Or
is it possible that I have done another mistake with some
RAID-parametres ???
Thanx for all help anyway!
Sevrin
reply other threads:[~2006-07-25 21:39 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=44C68F77.6020909@online.no \
--to=quack@online.no \
--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 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).