From: Jim Paris <jim@jtan.com>
To: linux-raid@vger.kernel.org
Subject: Re: Call for RAID-6 users
Date: Tue, 27 Jul 2004 14:48:36 -0400 [thread overview]
Message-ID: <20040727184836.GA28494@jim.sh> (raw)
In-Reply-To: <20040727181938.GA28181@jim.sh>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
> Attached is another trace that shows this corruption on a single
> regular file copied with "cp" onto a fresh filesystem.
And here's a trace showing problems even without a filesystem.
Writing data near the end is fatal. This does not happen if I write
to the first 1G of the array.
-jim
[-- Attachment #2: typescript --]
[-- Type: text/plain, Size: 5326 bytes --]
Script started on Tue Jul 27 14:44:26 2004
bucket:~# mdadm --stop /dev/md1
bucket:~# mdadm --zero-superblock /dev/hd[gikmo]2
bucket:~# for i in /dev/hd[gikmo]2 ; do dd if=/dev/zero of=$i bs=1M count=1 ; done
1+0 records in
1+0 records out
1048576 bytes transferred in 0.032001 seconds (32766876 bytes/sec)
1+0 records in
1+0 records out
1048576 bytes transferred in 0.032197 seconds (32567587 bytes/sec)
1+0 records in
1+0 records out
1048576 bytes transferred in 0.032125 seconds (32640483 bytes/sec)
1+0 records in
1+0 records out
1048576 bytes transferred in 0.032064 seconds (32702568 bytes/sec)
1+0 records in
1+0 records out
1048576 bytes transferred in 0.032315 seconds (32448665 bytes/sec)
bucket:~# mdadm --create /dev/md1 --level=6 --chunk=128 --raid-devices=6 missing /dev/hd[gikmo]2
mdadm: array /dev/md1 started.
bucket:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6]
md1 : active raid6 hdo2[5] hdm2[4] hdk2[3] hdi2[2] hdg2[1]
976269312 blocks level 6, 128k chunk, algorithm 2 [6/5] [_UUUUU]
md0 : active raid1 hdo1[5] hdm1[4] hdk1[3] hdi1[2] hdg1[1]
128384 blocks [6/5] [_UUUUU]
unused devices: <none>
bucket:~# dd if=/dev/urandom of=/dev/md1 bs=1M count=100 seek=900000
100+0 records in
100+0 records out
104857600 bytes transferred in 19.095634 seconds (5491182 bytes/sec)
bucket:~# mdadm --stop /dev/md1
bucket:~# mdadm --run /dev/md1
mdadm: failed to run array /dev/md1: Invalid argument
bucket:~# dmesg
md: bind<hdg2>
md: bind<hdi2>
md: bind<hdk2>
md: bind<hdm2>
md: bind<hdo2>
raid6: device hdo2 operational as raid disk 5
raid6: device hdm2 operational as raid disk 4
raid6: device hdk2 operational as raid disk 3
raid6: device hdi2 operational as raid disk 2
raid6: device hdg2 operational as raid disk 1
raid6: allocated 6269kB for md1
raid6: raid level 6 set md1 active with 5 out of 6 devices, algorithm 2
RAID6 conf printout:
--- rd:6 wd:5 fd:1
disk 1, o:1, dev:hdg2
disk 2, o:1, dev:hdi2
disk 3, o:1, dev:hdk2
disk 4, o:1, dev:hdm2
disk 5, o:1, dev:hdo2
md: md1 stopped.
md: unbind<hdo2>
md: export_rdev(hdo2)
md: unbind<hdm2>
md: export_rdev(hdm2)
md: unbind<hdk2>
md: export_rdev(hdk2)
md: unbind<hdi2>
md: export_rdev(hdi2)
md: unbind<hdg2>
md: export_rdev(hdg2)
md: bug in file drivers/md/md.c, line 1513
md: **********************************
md: * <COMPLETE RAID STATE PRINTOUT> *
md: **********************************
md1:
md0: <hdo1><hdm1><hdk1><hdi1><hdg1>
md: rdev hdo1, SZ:00128384 F:0 S:1 DN:5
md: rdev superblock:
md: SB: (V:0.90.0) ID:<65daa413.7da47b48.1e1593ff.5a0a11c8> CT:410564ab
md: L1 S00128384 ND:5 RD:6 md0 LO:0 CS:0
md: UT:410567ad ST:1 AD:5 WD:5 FD:0 SD:0 CSUM:86d6d898 E:0000001c
D 0: DISK<N:0,unknown-block(0,0)(0,0),R:0,S:8>
D 1: DISK<N:1,hdg1(34,1),R:1,S:6>
D 2: DISK<N:2,hdi1(56,1),R:2,S:6>
D 3: DISK<N:3,hdk1(57,1),R:3,S:6>
D 4: DISK<N:4,hdm1(88,1),R:4,S:6>
D 5: DISK<N:5,hdo1(89,1),R:5,S:6>
md: THIS: DISK<N:5,hdo1(89,1),R:5,S:6>
md: rdev hdm1, SZ:00128384 F:0 S:1 DN:4
md: rdev superblock:
md: SB: (V:0.90.0) ID:<65daa413.7da47b48.1e1593ff.5a0a11c8> CT:410564ab
md: L1 S00128384 ND:5 RD:6 md0 LO:0 CS:0
md: UT:410567ad ST:1 AD:5 WD:5 FD:0 SD:0 CSUM:86d6d895 E:0000001c
D 0: DISK<N:0,unknown-block(0,0)(0,0),R:0,S:8>
D 1: DISK<N:1,hdg1(34,1),R:1,S:6>
D 2: DISK<N:2,hdi1(56,1),R:2,S:6>
D 3: DISK<N:3,hdk1(57,1),R:3,S:6>
D 4: DISK<N:4,hdm1(88,1),R:4,S:6>
D 5: DISK<N:5,hdo1(89,1),R:5,S:6>
md: THIS: DISK<N:4,hdm1(88,1),R:4,S:6>
md: rdev hdk1, SZ:00128384 F:0 S:1 DN:3
md: rdev superblock:
md: SB: (V:0.90.0) ID:<65daa413.7da47b48.1e1593ff.5a0a11c8> CT:410564ab
md: L1 S00128384 ND:5 RD:6 md0 LO:0 CS:0
md: UT:410567ad ST:1 AD:5 WD:5 FD:0 SD:0 CSUM:86d6d874 E:0000001c
D 0: DISK<N:0,unknown-block(0,0)(0,0),R:0,S:8>
D 1: DISK<N:1,hdg1(34,1),R:1,S:6>
D 2: DISK<N:2,hdi1(56,1),R:2,S:6>
D 3: DISK<N:3,hdk1(57,1),R:3,S:6>
D 4: DISK<N:4,hdm1(88,1),R:4,S:6>
D 5: DISK<N:5,hdo1(89,1),R:5,S:6>
md: THIS: DISK<N:3,hdk1(57,1),R:3,S:6>
md: rdev hdi1, SZ:00128384 F:0 S:1 DN:2
md: rdev superblock:
md: SB: (V:0.90.0) ID:<65daa413.7da47b48.1e1593ff.5a0a11c8> CT:410564ab
md: L1 S00128384 ND:5 RD:6 md0 LO:0 CS:0
md: UT:410567ad ST:1 AD:5 WD:5 FD:0 SD:0 CSUM:86d6d871 E:0000001c
D 0: DISK<N:0,unknown-block(0,0)(0,0),R:0,S:8>
D 1: DISK<N:1,hdg1(34,1),R:1,S:6>
D 2: DISK<N:2,hdi1(56,1),R:2,S:6>
D 3: DISK<N:3,hdk1(57,1),R:3,S:6>
D 4: DISK<N:4,hdm1(88,1),R:4,S:6>
D 5: DISK<N:5,hdo1(89,1),R:5,S:6>
md: THIS: DISK<N:2,hdi1(56,1),R:2,S:6>
md: rdev hdg1, SZ:00128384 F:0 S:1 DN:1
md: rdev superblock:
md: SB: (V:0.90.0) ID:<65daa413.7da47b48.1e1593ff.5a0a11c8> CT:410564ab
md: L1 S00128384 ND:5 RD:6 md0 LO:0 CS:0
md: UT:410567ad ST:1 AD:5 WD:5 FD:0 SD:0 CSUM:86d6d859 E:0000001c
D 0: DISK<N:0,unknown-block(0,0)(0,0),R:0,S:8>
D 1: DISK<N:1,hdg1(34,1),R:1,S:6>
D 2: DISK<N:2,hdi1(56,1),R:2,S:6>
D 3: DISK<N:3,hdk1(57,1),R:3,S:6>
D 4: DISK<N:4,hdm1(88,1),R:4,S:6>
D 5: DISK<N:5,hdo1(89,1),R:5,S:6>
md: THIS: DISK<N:1,hdg1(34,1),R:1,S:6>
md: **********************************
bucket:~# exit
Script done on Tue Jul 27 14:44:51 2004
next prev parent reply other threads:[~2004-07-27 18:48 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
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 [this message]
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=20040727184836.GA28494@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.