From: Jim Paris <jim@jtan.com>
To: linux-raid@vger.kernel.org
Subject: Re: Call for RAID-6 users
Date: Mon, 26 Jul 2004 17:38:11 -0400 [thread overview]
Message-ID: <20040726213811.GA17363@jim.sh> (raw)
In-Reply-To: <cds76e$ee7$1@terminus.zytor.com>
> Thus, if you have used RAID-6 and have good or bad experiences, I'd
> like to know them as soon as possible.
Just tried setting up a RAID-6 on a new server, and I'm seeing
complete filesystem corruption.
I have 6 250GB disks, and want them all in the array. I've created it
degraded, with the first disk missing, since that disk temporarily
holds the system.
Using kernel 2.6.7, mdadm 1.6.0, I did something like this:
# mdadm --create /dev/md1 --level=6 --chunk=128 --raid-devices=6 missing /dev/hd{g,i,k,m,o}2
which gives me:
md1 : active raid6 hdo2[5] hdm2[4] hdk2[3] hdi2[2] hdg2[1]
976269312 blocks level 6, 128k chunk, algorithm 2 [6/5] [_UUUUU]
Then created the filesystem:
# mkreiserfs /dev/md1
# reiserfsck /dev/md1 # <-- no errors
# df -H # <-- shows proper size (1 TB)
Then copied the system do it:
# mount /dev/md1 /mnt/root
# cd /mnt/root ; tar --one-file-system -cf - / | tar --preserve -xvf - ; cd /
# umount /mnt/root
# reiserfsck /dev/md1 # <-- many, many errors
There were no errors in dmesg while copying the data to the
filesystem, or while running reiserfsck. The filesystem gives tons of
errors if I try to use it as root. Not sure what else to try. It's
easy to reproduce, and seems to fail the exact same way every time.
I need this server up soon, so I may just settle for RAID5, but I can
keep it around for testing for a few days. Let me know if you'd like
access to the machine.
-jim
next prev parent reply other threads:[~2004-07-26 21:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 23:32 Call for RAID-6 users H. Peter Anvin
2004-07-26 21:38 ` Jim Paris [this message]
2004-07-27 2:05 ` Matthew - RAID
2004-07-27 2:12 ` Jim Paris
2004-07-27 16:40 ` Ricky Beam
2004-07-27 17:20 ` Jim Paris
2004-07-27 18:19 ` Jim Paris
2004-07-27 18:48 ` Jim Paris
2004-07-28 3:09 ` Jim Paris
2004-07-28 8:36 ` David Greaves
2004-07-28 10:02 ` Jim Paris
2004-07-30 15:58 ` H. Peter Anvin
2004-07-30 19:39 ` Jim Paris
2004-07-30 19:45 ` H. Peter Anvin
2004-07-30 21:11 ` maarten van den Berg
2004-07-30 21:38 ` maarten van den Berg
2004-07-31 0:28 ` maarten van den Berg
2004-08-01 13:03 ` Kernel panic, FS corruption Was: " maarten van den Berg
2004-08-01 18:05 ` Jim Paris
2004-08-01 22:10 ` maarten van den Berg
2004-08-05 23:54 ` H. Peter Anvin
2004-08-06 0:19 ` Jim Paris
2004-08-06 0:36 ` H. Peter Anvin
2004-08-06 4:04 ` Jim Paris
2004-08-05 23:51 ` H. Peter Anvin
2004-08-05 23:46 ` H. Peter Anvin
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=20040726213811.GA17363@jim.sh \
--to=jim@jtan.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 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).